-
|
CTSM manages the tests for CESM prealpha, prebeta and aux_cime_baselines tests in our testlist -- what is the philosophy for what tests should be in that list? The current list has largely been maintained moving forward as is. So it would be good to revisit what's in the list. Some guidance we've had here are the following:
In general the prealpha test list is run more often so it should be smaller, and with lower resolutions and shorter simulations. The prebeta should also exercise the standard resolution used for coupled simulations (right now ne30pg3). The aux_cime_baseline testlist is run nightly as a standard part of CESM testing. As such it should be a fairly short testlist. Examples of "3" is the MKSURFDATAESMF test. Examples of "2" are the PTSMODE tests and fire-emission, dry-deposition tests that ensure that SCAM and CAM-Chem tests in CAM and CESM are more likely to continue working. I think the above principles make sense to me and we should retain most of this. We can probably reduce some of the tests in "5" and "6".and let the aux_clm testlist take care of more of the obscure testing. We certainly should reevaluate "2" and make sure we are covering CESM and CAM tests for B and F testcases in the I case framework for CTSM. We should also evaluate if anything else is needed for "4" we do want to maintain mpi-serial tests here for example. And I wonder if we should for example add the FUNITCTSM test for prebeta. |
Beta Was this translation helpful? Give feedback.
Answered by
ekluzek
May 23, 2025
Replies: 10 comments 4 replies
-
|
Adding a CESM requirement here. For CESM testing there is a desire to NOT require any specific python environment. Which means that testing for our tools or for example the MKSURFDATAESMF can NOT be done. We also need a way for CESM testing to ensure that the following matrix of case types build:
Which amounts to 32 build options, with four less because we don't do izumi_nag with DEBUG==FALSE (so 28). So to show all the combinations:
I don't think izumi_nag works with threading? nvhpc has been problematic, so we probably just need the full MPI threaded off options. mpi-serial with threads is not a usual use-case so it's a lower priority. It is a useful case for mizuRoute though. This could just be checking that a pure stub case builds for CESM for a lot of these. In terms of CTSM priority the list might be something like:
So making sure the top 5 options in the list are covered would be good, although that means a minimum of 10 tests. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Using the above as guidance I want to suggest the following points for guidance:
Some examples of "2" above:
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Notes from SE meeting today:
|
Beta Was this translation helpful? Give feedback.
Answer selected by
ekluzek
-
|
Here are the current 192 CESM tests for cesm3_0_beta06 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Splitting into the categories they divide out like this:
54 DEBUG tests: included the following clm I cases: for ne30, ne30pg3, f09, and f10, 1850/2000 (These tests should all be done for Clm60) 73 DEBUG==FALSE: Including these clm I cases (all f10) (Remove the till tests?) -- yes! (see below)
10 DEBUG tests: including these clm I cases (all f10)
3 DEBUG tests Note: There are NO DEBUG==FALSE tests! So we should add some.
10 tests: Including these clm I cases (f10 and f19)
21 tests: Include these I cases...
21 tests: Include these I cases... Note: There are NO DEBUG==FALSE tests! (so add some)
1 test: ERP_P64x2_D_Ld5.f10_f10_mg37.I2000Clm50Sp.derecho_gnu.clm-default Note: There are NO DEBUG FALSE tests (so add some)
3 tests: No I cases
No tests for any of these, which is fine because there isn't an important use case for nvhpc or for mpi-serial with threading. The later might be useful for debugging a full MPI library problem, but doesn't need to be regularly tested. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
From SE meeting today:
|
Beta Was this translation helpful? Give feedback.
-
|
The test types for the I cases split out into this list: DAE We should also include these because they are sensitive to changes in cime: SSPMATRIX Also include
|
Beta Was this translation helpful? Give feedback.
2 replies
-
|
In a disscussion with @briandobbins and @wwieder on May/30th we planned on these things:
|
Beta Was this translation helpful? Give feedback.
-
|
SE meeting today:
|
Beta Was this translation helpful? Give feedback.
-
|
Here's the current list of CAM tests in aux_cam that include CTSM (non PORT or AQUAPLANET tests, as well as KESSLER, FADIAB, FHS94, FTJ16): Compsets include: 1850, 2000, 2010, and Hist
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Note, that #3374 talks about adding ERR and IRT tests. Here we mention that there is an ERR in place. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Some checks of compliance to these guidelines could eventually be added to the script proposed at PR #2979. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
We went through this at the CTSM Software meeting this morning, and there's agreement with the guidelines. It's assigned to me to turn this into issues that we can complete so we have the appropriate coverage for CESM tests. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
This is the list of notes on changes to make that I note from the discussion above:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using the above as guidance I want to suggest the following points for guidance: