-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable use of create_test workflow #45
Enable use of create_test workflow #45
Conversation
This begins steps to use the workflow in CIME. A section now exists for EarthWorks specific tests and such compsets should include the '-EW' postfix.
This first test is a 5 day (default length) "smoke-test", using 1 Derecho node, nuopc coupled, on the 480km grid.
TODOs:
|
Some info about tests can be found in the CIME Documentation: https://esmci.github.io/cime/versions/master/html/users_guide/testing.html#testname-syntax |
These tests ensure that the other EarthWorks compsets aren't affected by a PR including FHS94, FKESSLER, QPC6, F2000climo at 120km. A few compilers are checked for compatability. Checking smoke tests of these runs should help catch many reversions or issues.
This makes use of some syntatic sugar to make sure the FHS94 and FKESSLER don't try to use 'vcoords' files for ncdata. Asking for 'mpasa120z32_mpasa120' sets 'nlev' to 32 (instead of 30 which is the default).
All 120km runs came in under these new limits. This change should help ew-pr tests get through the Derecho queue more quickly.
This change should reduce the overall cost of running the ew-pr test category by doing wide testing for the least and most complicated compsets. The NVHPC compilers are used for every compset since EarthWorks depends on it and NVHPC testing of these compsets isn't commonly done.
9e53029
to
4627564
Compare
Add EarthWorks equivalents of the B2000 and F2000climo compsets that use MPAS-O and MPAS-SI instead.
@@ -0,0 +1,2 @@ | |||
|
|||
config_cvmix_kpp_use_theory_wave = .true. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dazlich should this variable be set true only under certain conditions (like FullyCoupled at 120km), or do you think this should be true for any EW mpas-o compset? I can create a PR for the second case easily.
I’ve got an outside opinion that it should be generally true.
|
The various
|
To test these changes:
Example commands to run the git clone -b feature/ew-cime-testing https://github.com/gdicker1/EarthWorks
cd EarthWorks && ./manage_externals/checkout_externals
qcmd -A <ew_proj_key> -- ./cime/scripts/create_test--xml-testlist cime_config/testlist_earthworks.xml \
-i /glade/campaign/univ/ucsu0085/inputdata/ --project <ew_proj_key> \
--test-root ${SCRATCH}/ew_pr_tests --xml-category ew-pr
# This will block while builds and other steps finish
cd ${SCRATCH}/ew_pr_tests
./cs.status.* |
These are initial tests that serve as a starting point. More should be added in the future. The 'ew-ver' test added should work for what is described on the CESM website for held-suarez. This is a 1200 day forward run of the FHS94 compset with the 120km 32 level MPAS-A grid. See "https://www.cesm.ucar.edu/models/simple/held-suarez" The 'ew-rel' tests are starting with FullyCoupled-EW runs on 120, 60, 30, and 15km grids. These tests are "exact restart" tests that run forward for 11 days, write a restart on day 6, and then restarts with half the number of tasks to reach the same 11 day mark.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gdicker1 - I've tested this with
./create_test --xml-testlist ../../cime_config/testlist_earthworks.xml --xml-compiler intel --xml-category ew-pr --project UCSU0085
This creates two cases, FHS94 and FULLYCOUPLED. Both build through compilation. FHS94 also runs, FULLYCOUPLED fails trying to find seaice/ocean data that doesn't exist in the campaign inputdata directory.
Judging by your command and comment I assume you mean the CESM input data on Campaign? Since I haven't figured out how to add EW as a model within CIME, we will keep getting that (CESM) location by default. @dazlich, could you try adding (Or go into the specific test, run |
@gdicker1 Doh, of course - I am still getting up to speed on 'create_test' |
B2000-EW I would have liked to called this CHAOS2000, CHAOS standing for Coupled Hexagonal Atmosphere Ocean and Seaice since that's what the coupled mpas components on a quasi-uniform grid essentially is. ;-) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, the test I tried before works now adding the --inputdata option.
Huh, I thought B2000 was already a compset (could still be, for all I know). I think CHAOS2000 is such a better name! If this is a vote, mine goes to CHAOS2000 instead :D |
Actually, I don’t see B2000 when I do a query_config, but other B-cases have CICE and either POP or MOM.
I choose the B2000-EW name since I set the bcs like GHG to cyclic 2000.
On May 20, 2024, at 4:01 PM, G. Dylan Dickerson ***@***.***> wrote:
** Caution: EXTERNAL Sender **
B2000-EW
I would have liked to called this CHAOS2000, CHAOS standing for Coupled Hexagonal Atmosphere Ocean and Seaice since that's what the coupled mpas components on a quasi-uniform grid essentially is. ;-)
Huh, I thought B2000 was already a compset (could still be, for all I know). I think CHAOS2000 is such a better name! If this is a vote, mine goes to CHAOS2000 instead :D
—
Reply to this email directly, view it on GitHub<#45 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADS3XWHEHB6DCHGW44A7WYLZDJXD3AVCNFSM6AAAAABHRB5AB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRRGI4DMMZXGI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to add, I ran the entire ew-ver and ew-rel suites with the --no-build option and they all pass.
My intel/fullycoupled ew-pr ran out of time.
@dazlich, thank you. I'll update the FullyCoupled category, it'll only hurt the queue-length for these tests. When you have a sec, could you just make sure the sub-PRs make sense (i.e. pass visual inspection)? |
@gdicker1 I've had a look at the sub-PRs and they all look good to me! |
I think B2000 is a compset, rings a bell. I vote for CHAOS2000!
…On Mon, May 20, 2024 at 4:01 PM G. Dylan Dickerson ***@***.***> wrote:
B2000-EW
I would have liked to called this CHAOS2000, CHAOS standing for Coupled
Hexagonal Atmosphere Ocean and Seaice since that's what the coupled mpas
components on a quasi-uniform grid essentially is. ;-)
Huh, I thought B2000 was already a compset (could still be, for all I
know). I think CHAOS2000 is such a better name! If this is a vote, mine
goes to CHAOS2000 instead :D
—
Reply to this email directly, view it on GitHub
<#45 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZ2GWBNFBDYN7E76JXTSX43ZDJXD3AVCNFSM6AAAAABHRB5AB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRRGI4DMMZXGI>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
|
Remove the hyphen characters from the names (because test names will be confusing enough, already). Also, since there is no B2000 compset, rename to the Coupled, Hexagonal, Atmosphere, Ocean, and Seaice 2000 (CHAOS2000) compset.
674173a
to
7e8bd39
Compare
Big Boss rejected that name when I proposed it for our CSU model 20 years ago
On May 21, 2024, at 7:21 AM, areanddee ***@***.***> wrote:
I think B2000 is a compset, rings a bell. I vote for CHAOS2000!
|
Enable use of create_test workflow. Add definitions of compsets and tests so that typical EarthWorks cases can be run as CIME tests instead. Also include changes to externals that helps auto-select timesteps and coupling intervals based on resolution.
Add definitions of compsets and tests so that typical EarthWorks cases can be run as CIME tests instead.
Testing instructions (in this thread): #45 (comment)