ERROR: (shr_strdata_advance) ERROR dt limit for stream

[jack]

Hi，
Now, I use my own atmospheric forcing with 3 hr tempornal resolution to force CLM model. All of the forcing (i.e. Precip, Solar and tphwl) was time stamped at the beginng of 3 hour period (i.e., the first time sample stamped at time zero), the offset in Precip and Solar stream is -5400, I want to run for one year(2016), I set all of year 2016 in user_datm file, like:
<fileNames>
28 solar-2016-01.nc
29 solar-2016-02.nc
30 solar-2016-03.nc
31 solar-2016-04.nc
32 solar-2016-05.nc
33 solar-2016-06.nc
34 solar-2016-07.nc
35 solar-2016-08.nc
36 solar-2016-09.nc
37 solar-2016-10.nc
38 solar-2016-11.nc
39 solar-2016-12.nc
40 </fileNames>
41 <offset>
42 -5400
43 </offset>

and use:

./xmlchange DATM_CLMNCEP_YR_START=2016
./xmlchange DATM_CLMNCEP_YR_END=2016
./xmlchange DATM_CLMNCEP_YR_ALIGN=2016
./xmlchange STOP_OPTION=nyears
./xmlchange STOP_N=1
./xmlchange RUN_STARTDATE=2016-01-01

However, when ./case.submit, error shows:

250 (shr_strdata_advance) ERROR: for stream 1
251 (shr_strdata_advance) ERROR: for stream 1
252 (shr_strdata_advance) ERROR: dt limit1 0.25000000000000000 0.12500000000000000 1.5000000000000000
253 (shr_strdata_advance) ERROR: dt limit2 20160101 5400 20160101 16200
254 ERROR: (shr_strdata_advance) ERROR dt limit for stream
255 (shr_strdata_advance) ERROR: dt limit1 0.25000000000000000 0.12500000000000000 1.5000000000000000
256 (shr_strdata_advance) ERROR: dt limit2 20160101 5400 20160101 16200
257 ERROR: (shr_strdata_advance) ERROR dt limit for stream

(1) If I add one forcing file (e.g., solar-2017-01.nc) at the end of stream file, this problem will not occur, but I'm not sure is this reasonable. Do you have any suggestion?

(2) If I just want to run for one month (e.g., June 2016), does the following command works?
./xmlchange DATM_CLMNCEP_YR_START=2016
./xmlchange DATM_CLMNCEP_YR_END=2016
./xmlchange DATM_CLMNCEP_YR_ALIGN=2016
./xmlchange STOP_OPTION=nmonths
./xmlchange STOP_N=1
./xmlchange RUN_STARTDATE=2016-06-01

 

[oleson]

(1) The fact that it fixes the problem likely means that it is using the first time sample from the 2017-01.nc file for interpolation, at the beginning of the simulation. An alternative is to set the "taxmode" to "extend" instead of "cycle". That would extend the first time sample in the 2016-01.nc file back in time. Either way is probably fine since this is probably just happening for the first few model timesteps. You can look at the atm.log file to see exactly what time samples and files are being read in in each case.

(2) That should work.

There is some good information on the data models here, including the datm:

Data Models — CIME master documentation

 

[jack]

(1) The fact that it fixes the problem likely means that it is using the first time sample from the 2017-01.nc file for interpolation, at the beginning of the simulation. An alternative is to set the "taxmode" to "extend" instead of "cycle". That would extend the first time sample in the 2016-01.nc file back in time. Either way is probably fine since this is probably just happening for the first few model timesteps. You can look at the atm.log file to see exactly what time samples and files are being read in in each case.

(2) That should work.

There is some good information on the data models here, including the datm:

Data Models — CIME master documentation

thanks a lot