-
Notifications
You must be signed in to change notification settings - Fork 336
Description
Originally posted by @samsrabin in #3422 (comment)
@jedwards4b I think this is related to the problem you alerted me to with ctsm6.1.112.
Generating a
MKSURFDATAESMF_P128x1.f10_f10_mg37.I1850Clm50BgcCrop.derecho_intel
baseline at ctsm5.3.069 givesCaseDocs/lnd_in
withfsurdat
pointing at a file generated during that test (ending incYYMMDD.nc
, where YYMMDD is today's date). Reverting CIME to cime6.1.111 changes it so that the baseline namelist file is saved earlier:CaseDocs/lnd_in
hasfsurdat
pointing at the default file, ending inc240908.nc
.So cime6.1.112 causes the baseline namelist files to be saved later in the process. I think this is actually correct for this particular test, because the test does actually run with the file it generates. But it looks like the namelist comparison is still happening before the
lnd_in
namelist has been updated, so it still has the defaultc240908.nc
file.Fixing this test would require a CIME update that makes it so the namelist comparison happens after the
lnd_in
namelist has been updated—ideally, immediately before the baseline is saved. (We would then end up with a different problem, like what we see for the SUBSETDATA tests here, but that's easily fixable.)Like I said, I think the baseline namelist files being saved later in the process is correct for this particular test. I don't know if that also applies for the E3SM test @jgfouca highlighted as having a related (?) problem.