Update develop-ref after dtcenter/MET#2529 and #2148 #2153
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
…use case currently is only available in develop, it will eventually be in latest when the next release is created
* per #1694, moved 4 use cases from s2s to s2s_mjo, updated paths accordingly, and turned on all s2s use cases to test that they all run successfully after the changes * per #1694, fixed paths to s2s_mjo conf files * updated documentation for use cases that were moved from s2s to s2s_mjo * attempt to free up unused disk space in GHA runner environment * moved 4 s2s use cases into s2s_mid_lat * added new model application categories to contrib guide for adding new use cases * per #947, changed convection_allowing_models use cases to short_range * changed which use case tests run to the ones that are failing and added other METdbLoad use case to see if that fails as well * test to determine which files are preventing MySQL database from being created properly * test 2 to determine which files are preventing MySQL database from being created properly * test 3 to see if removing these files is not the cause of the METdbLoad failure * updated references to METdatadb to METdataio since the repository was renamed * fixed typo * changed path to sql file needed to create database because it was moved from METviewer to METdataio * fixed path to sql file that was moved from METviewer to METdataio * removed temporary fix because metdataio conda env was created in the dtcenter/metplus-envs:metdataio Docker image * added note to update path when METviewer Dockerfile changes to reflect METdatadb rename to METdataio, ci-skip-unit-tests * fixed path to METdataio repo * add back commands to free up disk space because issue with METdbLoad use case was likely not related, ci-skip-unit-tests * run all tests with ci-run-all-diff * remove use case group added for testing, ci-skip-all * changed exit code for diff tests to 2 so it is easier to see if a use case test job failed due to an actual failure or due to differences in the output * changed grouping of s2s mid lat use cases to original grouping to prevent warning that artifact contains more than 10,000 files. The 2 WeatherRegime use cases produce a lot of output files, so splitting them up should resolve this warning * per #1694, changed all references to convection allowing models to short range in the Verification Datasets section of the documentation * changed URLs to develop version of documentation to a URL relative to the current version of the documentation to match the quick search links from the METplus User's Guide * per #947, changed references to convection_allowing_model (without the s) to short_range that were missed * updated use case test scripts to rename convection_allowing_models to short_range and added note to alert developers that the list of use cases in the script is not maintained and therefore not complete
…and s2s_mjo. ci-run-all-diff
…mpty string. Previously a False default value was logged as set to empty string
…a default value of False
…or this wrapper is optional and different behavior will be executed if no config file is set
…or this wrapper is optional and different behavior will be executed if no config file is set
…le and replace MET_CONFIG_OVERRIDE variable with TC_PAIRS_MATCH_POINTS
…e cases. ci-run-all-diff
* adding new questions section * changing table config #650 * odd section bullets #650 * adding in the rest of the text but not formatted #650 * first attempt at bullet formatting #650 * fixing errors #650 * fixing errors take 2 #650 * fixing errors take 3 #650 * fixing errors take 4 #650 * fixing errors take 5 #650 * Update systemconfiguration.rst Cleaning up "you" and changing to 3rd person. Except where "you" is referenced by a program example #650 * Update systemconfiguration.rst Taking another stab at making the bullets consistent #650 * creating new getting_started file to house Questions to Consider that was removed from the systemconfiguration file. * moving Running METplus into getting_started file and removing it from the systemconfiguration. #650 * updating index to include new Getting Started chapter #650. * updating index to include new Getting Started chapter take 2 #650. * shortening the chapter name to Installation and Configuration #650 * using updated questions #650 * Made a few formatting/wording changes * Removed text * adding flowchart question and adding periods #650 * bolding files #650 * adding changes John O. recommended. #650 * small John O. change #650 * removing duplicate question #650 * fixing question order #650 * fixing typos Tara requested * answering question 2.1.1.7 * adding Use Case Rules link to 2.1.1.7 * adding proper link to the Add Use Cases in the Contributors Guide * trying to get link to work * trying to get link to work take 2 * trying to get link to work take 3 * trying to get link to work take 4 * removing unnecessary link * fixing punctuation Co-authored-by: Julie Prestopnik <jpresto@ucar.edu>
* changes needed to create v5.0 version of metplus_base docker/conda environment * update metplotpy conda env to use python 3.8 and new package list, then test to see if use cases that use that env still work using the .v5 version * turn on use cases that use metplotpy_env to test new conda env * add .v5 to metplotpy conda env to test that environment * removed cartopy from requirements because cartopy may no longer be needed * changed conda environment used for use case * update conda before building environments * updated instructions and scripts to build python environments using Python 3.8.6 for METplus v5 * updated conda env to include .v5 * updated automated test logic to use new .v5 Docker images that use Conda environments built from Python 3.8.6 * rebuilt gempak and gfdl-tracker docker images to use .v5 extension to be consistent in the automation logic and avoid special behavior for those environments * added note to update OS packages to prevent wget certificate errors * renamed variables to be more clear which path they are actually storing * Updated logic to no longer handle gempak and gfdl-tracker envs differently by excluding the version number. Cleaned up logic to add version number extension to conda environment names as needed * updated scripts to create Docker image containing Conda environment for METdataio (renamed from METdatadb) to use in automated tests for v5 * turn off all use cases * turn on use cases that previously failed * turn off use cases tests that passed * turn off all use cases * per #1566, added explicit version numbers for each Python package that is installed in the Docker Conda environments used for the automated tests to ensure that the same environment will be generated even if the default version of the package differs from the env used to create them
… on develop or main_vX.Y branches because I discovered that the commit message from doing a squash and merge in a pull request will contain any keywords used during development
* per #1713, remove setting of METPLOTPY_BASE env var in each use case config file and instead set it in the global config settings for the automated test environment, ci-run-all-cases * per #1713, added instructions to set METPLOTPY_BASE via [user_env_vars] in the default METplus config file upon install if necessary * per #1713, added documentation to describe METPLOTPY_BASE variable that was added to the defaults.conf file
…r-specific version is preferred over generic OBS_WINDOW_BEGIN/END (#2062)
* updated version number * added release notes * Update docs/Users_Guide/release-notes.rst Co-authored-by: John Halley Gotway <johnhg@ucar.edu> --------- Co-authored-by: John Halley Gotway <johnhg@ucar.edu>
… used if the pre-processing steps are needed
* test dropdowns * Update release-notes.rst Attempting to resolve WARNING * testing dropdowns * adding dropdown menus * testing dropdown remove from warning section * dropdown testing * dropdown menu tests * dropdown menus after the warnings section, the dropdown menu only has one space instead of the normal 2 spaces. If it has 2 spaces, it gets sucked into the warning section. * spaces with warning * no spaces for warning * Update release-notes.rst warning note has to be indented 1 space. Originally it was no spaces but then all of the dropdown menus end up in the warning message. If it's 2 spaces, as is normal, then the warning is indented, which is unnecessary. 1 space is slightly indented and keeps the dropdown menus separate. --------- Co-authored-by: jprestop <jpresto@ucar.edu>
Co-authored-by: Tracy Hertneky <hertneky@seneca.rap.ucar.edu> Co-authored-by: George McCabe <23407799+georgemccabe@users.noreply.github.com>
Co-authored-by: Giovanni Rosa <giovanni.rosa@unimol.it>
* change PROJECT ASSIGNMENT to CYCLE ASSIGNMENT * change PROJECT ASSIGNMENT to CYCLE ASSIGNMENT * change PROJECT ASSIGNMENT to CYCLE ASSIGNMENT * change PROJECT ASSIGNMENT to CYCLE ASSIGNMENT * change PROJECT ASSIGNMENT to CYCLE ASSIGNMENT * change PROJECT ASSIGNMENT to CYCLE ASSIGNMENT * Added paths to ignore --------- Co-authored-by: jprestop <jpresto@ucar.edu>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bugfix in MET to fix fill value and new ARGO use case
Created by @georgemccabe