|
1 | 1 | =============================================================== |
| 2 | +Tag name: ctsm5.3.062 |
| 3 | +Originator(s): slevis (Samuel Levis,UCAR/TSS,303-665-1310) |
| 4 | +Date: Thu 03 Jul 2025 12:23:00 PM MDT |
| 5 | +One-line Summary: Put instantaneous and non-inst. fields on separate hist files |
| 6 | + |
| 7 | +Purpose and description of changes |
| 8 | +---------------------------------- |
| 9 | + Following ctsm5.3.018 "Change history time to be the middle of the time bounds" the current change intends to prevent confusion associated with the time corresponding to instantaneous history fields by putting them on separate files than non-instantaneous fields. The result is |
| 10 | + 1) two history files per clm, mosart, and rtm history tape: |
| 11 | + tape h0 becomes h0a and h0i |
| 12 | + tape h1 becomes h1a and h1i |
| 13 | + ... |
| 14 | + tape hX becomes hXa and hXi |
| 15 | + |
| 16 | + 2) two history restart files per history restart tape: |
| 17 | + rh0 becomes rh0a and rh0i |
| 18 | + rh1 becomes rh1a and rh1i |
| 19 | + ... |
| 20 | + rhX becomes rhXa and rhXi |
| 21 | + |
| 22 | + The clm could and still can handle not generating history (and corresponding history restart) files when empty. The rtm and mosart could not handle not generating empty files. Instead of refactoring rtm and mosart (out of scope), I introduced one active instantaneous field in mosart and one in rtm. |
| 23 | + |
| 24 | +Significant changes to scientifically-supported configurations |
| 25 | +-------------------------------------------------------------- |
| 26 | + |
| 27 | +Does this tag change answers significantly for any of the following physics configurations? |
| 28 | +(Details of any changes will be given in the "Answer changes" section below.) |
| 29 | + |
| 30 | + [Put an [X] in the box for any configuration with significant answer changes.] |
| 31 | + |
| 32 | +[ ] clm6_0 |
| 33 | + |
| 34 | +[ ] clm5_0 |
| 35 | + |
| 36 | +[ ] ctsm5_0-nwp |
| 37 | + |
| 38 | +[ ] clm4_5 |
| 39 | + |
| 40 | + |
| 41 | +Bugs fixed |
| 42 | +---------- |
| 43 | +List of CTSM issues fixed (include CTSM Issue # and description) [one per line]: |
| 44 | + Resolves #1059 Don't allow inst. fields and averaged fields to be on the same history file |
| 45 | + Resolves ESCOMP/RTM#32 |
| 46 | + Resolves ESCOMP/MOSART#52 |
| 47 | + |
| 48 | +Notes of particular relevance for users |
| 49 | +--------------------------------------- |
| 50 | +Caveats for users (e.g., need to interpolate initial conditions): |
| 51 | + History tapes have new extensions, e.g. h0 becomes h0a and h0i |
| 52 | + History restart tapes have new extensions, e.g. rh0 becomes rh0a and rh0i |
| 53 | + |
| 54 | +Changes to documentation: |
| 55 | + Not, yet: |
| 56 | + - clm documentation |
| 57 | + - Adam Phillips' cmip documentation |
| 58 | + |
| 59 | +Substantial timing or memory changes: |
| 60 | +[e.g., check PFS test in the test suite and look at timings, if you |
| 61 | +expect possible significant timing changes] |
| 62 | + |
| 63 | + |
| 64 | +Testing summary: |
| 65 | +---------------- |
| 66 | + |
| 67 | + [PASS means all tests PASS; OK means tests PASS other than expected fails.] |
| 68 | + |
| 69 | + build-namelist tests (if CLMBuildNamelist.pm has changed): |
| 70 | + |
| 71 | + derecho - PASS |
| 72 | + |
| 73 | + python testing (if python code has changed; see instructions in python/README.md; document testing done): |
| 74 | + |
| 75 | + derecho - PASS |
| 76 | + |
| 77 | + regular tests (aux_clm: https://github.com/ESCOMP/CTSM/wiki/System-Testing-Guide#pre-merge-system-testing): |
| 78 | + |
| 79 | + derecho ----- OK |
| 80 | + izumi ------- OK |
| 81 | + |
| 82 | + fates tests: (-c fates-sci.1.84.0_api.40.0.0-ctsm5.3.061 -g fates-sci.1.84.0_api.40.0.0-ctsm5.3.062) |
| 83 | + derecho ----- OK |
| 84 | + izumi ------- OK |
| 85 | + |
| 86 | + any other testing (give details below): |
| 87 | + |
| 88 | + ctsm_sci (-c ctsm_sci-ctsm5.3.059 -g ctsm_sci-ctsm5.3.062) |
| 89 | + derecho ---- FAIL and I will open an issue and mark EXPECTED FAILURE as the problem originates in ctsm5.3.060 |
| 90 | + |
| 91 | + mosart tests: (-c mosart1.1.08-ctsm5.3.061 -g mosart1.1.09-ctsm5.3.062) |
| 92 | + derecho ----- OK |
| 93 | + izumi ------- OK |
| 94 | + |
| 95 | + rtm tests: (-c rtm1_0_86-ctsm5.3.061 -g rtm1_0_87-ctsm5.3.062) |
| 96 | + derecho ----- OK |
| 97 | + izumi ------- OK |
| 98 | + |
| 99 | + crop_calendars tests: (tested while in ctsm5.3.058, before updating to ctsm5.3.061) |
| 100 | + derecho ----- OK |
| 101 | + izumi ------- OK |
| 102 | + |
| 103 | + ssp tests: (tested while in ctsm5.3.058, before updating to ctsm5.3.061) |
| 104 | + derecho ----- OK |
| 105 | + |
| 106 | + hillslope tests: (tested while in ctsm5.3.058, before updating to ctsm5.3.061) |
| 107 | + derecho ----- OK |
| 108 | + |
| 109 | + fire tests: (tested while in ctsm5.3.058, before updating to ctsm5.3.061) |
| 110 | + derecho ----- OK |
| 111 | + |
| 112 | +Answer changes |
| 113 | +-------------- |
| 114 | + |
| 115 | +Changes answers relative to baseline: No, but read caveat |
| 116 | + |
| 117 | + Caveat: h0 files become h0a (containing non-instantaneous fields) and h0i (containing instantaneous fields). I spot-checked clm, mosart, and rtm files and confirmed no bitwise change in answers. |
| 118 | + |
| 119 | +Other details |
| 120 | +------------- |
| 121 | +List any git submodules updated (cime, rtm, mosart, cism, fates, etc.): |
| 122 | + mosart1.1.08 --> mosart1.1.09 |
| 123 | + rtm1_0_86 --> rtm1_0_87 |
| 124 | + |
| 125 | +Pull Requests that document the changes (include PR ids): |
| 126 | + https://github.com/ESCOMP/ctsm/pull/2445 |
| 127 | + https://github.com/ESCOMP/MOSART/pull/117 |
| 128 | + https://github.com/ESCOMP/RTM/pull/61 |
| 129 | + |
| 130 | +=============================================================== |
| 131 | +=============================================================== |
2 | 132 | Tag name: ctsm5.3.061 |
3 | 133 | Originator(s): slevis (Samuel Levis,UCAR/TSS,303-665-1310) |
4 | 134 | Date: Thu 26 Jun 2025 11:28:43 AM MDT |
|
0 commit comments