You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One-line Summary: Put instantaneous and non-inst. fields on separate hist files
6
6
7
7
Purpose and description of changes
8
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
9
+
Following ctsm5.3.018 "Change history time to be the middle of the time bounds"
10
+
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
11
+
10
12
1) two history files per clm, mosart, and rtm history tape:
11
13
tape h0 becomes h0a and h0i
12
14
tape h1 becomes h1a and h1i
@@ -19,7 +21,7 @@ Purpose and description of changes
19
21
...
20
22
rhX becomes rhXa and rhXi
21
23
22
-
The clm handles empty history (and corresponding history restart) files by not generating them, while rtm and mosart give an error. Instead of refactoring rtm and mosart to behave like the clm (out of scope), I have introduced one active instantaneous field in mosart and one in rtm to bypass the "empty file" error.
24
+
The clm handles empty history (and corresponding history restart) files by not generating them, while rtm and mosart give an error. Instead of refactoring rtm and mosart to behave like the clm (considered out of scope), I have introduced one active instantaneous field in mosart and one in rtm to bypass the "empty file" error.
23
25
24
26
Significant changes to scientifically-supported configurations
crop_calendars tests: (tested while in ctsm5.3.058, before updating to ctsm5.3.061)
97
+
crop_calendars tests: (tested while in ctsm5.3.058 and again in ctsm5.3.061)
96
98
derecho ----- OK
97
99
izumi ------- OK
98
100
99
-
ssp tests: (tested while in ctsm5.3.058, before updating to ctsm5.3.061)
101
+
ssp tests: (tested while in ctsm5.3.058 and again in ctsm5.3.061)
100
102
derecho ----- OK
101
103
102
-
hillslope tests: (tested while in ctsm5.3.058, before updating to ctsm5.3.061)
104
+
hillslope tests: (tested while in ctsm5.3.058 and again in ctsm5.3.061)
103
105
derecho ----- OK
104
106
105
-
fire tests: (tested while in ctsm5.3.058, before updating to ctsm5.3.061)
107
+
fire tests: (tested while in ctsm5.3.058 and again in ctsm5.3.061)
106
108
derecho ----- OK
107
109
108
110
Answer changes
109
111
--------------
110
112
111
-
Changes answers relative to baseline: No, but read caveat
112
-
113
-
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.
113
+
Changes answers relative to baseline: No, but read caveat:
114
+
h0 files become h0a (containing non-instantaneous fields) and h0i (containing instantaneous fields):
115
+
- I spot-checked clm, mosart, and rtm files and confirmed no bitwise change in answers.
116
+
- I ran Sam Rabin's comparison tool written specifically to compare hX files against hXa + hXi files:
0 commit comments