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
{{ message }}
Repository navigation
Example, user_nl_datm_streams file for anomaly forcing for NUOPC coupler #1730
Since the Anomaly Forcing (AF) data are all monthly and normally you want the different variables to be coordinated together, this could be changed so that all variables were on one file and you only use two streams to manage the data. That would cut down on the number of changes you have to add to the user_nl_datm_streams file.
@wwieder the gswp3 data ranges 1901-2014, so I think that year_first=2015 won't work and that you just pick the range of years that you want to cycle for the rest of the run (eg 1991-2010).
Activity
ekluzek commentedon Jun 3, 2022
OK I think I've reproduced the above case with the following changes:
ekluzek commentedon Jun 3, 2022
Since the Anomaly Forcing (AF) data are all monthly and normally you want the different variables to be coordinated together, this could be changed so that all variables were on one file and you only use two streams to manage the data. That would cut down on the number of changes you have to add to the user_nl_datm_streams file.
slevis-lmwg commentedon Jun 6, 2022
Thank you @ekluzek
I will try your changes in #1654
wwieder commentedon Jun 6, 2022
@ekluzek if we're running with GSWP3 should
year_firstandyear_align=2015?slevis-lmwg commentedon Jun 6, 2022
@wwieder the gswp3 data ranges 1901-2014, so I think that
year_first=2015won't work and that you just pick the range of years that you want to cycle for the rest of the run (eg 1991-2010).wwieder commentedon Jun 6, 2022
The SSP370 compset defaults to
DATM_YR_START=2001(in env_run.xml), and cycles over data from 2001-2014 (inCaseDocs/datm_streams)But I think we want the
year_firstandyear_aligninuser_nl_datm_streams(above) to be 2015? e.g.Again, this would be specific for GSWP3 runs.
wwieder commentedon Jun 6, 2022
Now that I"m looking more carefully at datm_streams...
Does this for the year first and year align look right for presaero in a simulation starting in 2015 that's using anomaly forcing @ekluzek?
my case is here
/glade/work/wwieder/ctsm/flexLeafCN/cime/scripts/ctsm51d074_2deg_GSWP3V1_ssp370_cnSlope0
slevis-lmwg commentedon Jun 6, 2022
I see what you mean, and I think you're right.
ekluzek commentedon Jun 23, 2022
We have this example working, so I'm closing.
21 remaining items
wwieder commentedon Aug 26, 2022
Thanks for clearing this up!
wwieder commentedon Sep 1, 2022
Once the cdeps issue is resolved I suggest we close this issue and move the 'correct' answer to discussion.