"dt limit for stream" error when using custom forcing data in CLM5.0 with datm

[chenyihui]

I'm trying to run CLM5.0 with my own atmospheric forcing data (CMFD) following the GSWP3 format.

However, I encounter the following error when running for only 5 days (Jan 1-5, 2000):
(shr_dmodel_readstrm) file ub: .../Solar/FSDS_..._200001.nc 2
(shr_strdata_advance) ERROR: for stream 1
(shr_strdata_advance) ERROR: dt limit1 334.125000000000
0.125000000000000 1.50000000000000
(shr_strdata_advance) ERROR: dt limit2 20000101 5400 20000101 16200
ERROR: (shr_strdata_advance) ERROR dt limit for stream


The error occurs at the second time step (2000-01-01 01:30 to 04:30).
The data file contains a full month (Jan 2000, 248 time steps, time values 0.0625 to 30.9375),
which should be sufficient for a 5-day simulation.

I've verified that:
- My data files have the correct format (LONGXY, LATIXY, time dimensions)
- Time units are "days since 2000-01-01 00:00:00"
- Time calendar is "noleap"
- The stream files are configured similarly to GSWP3

What could be causing the dt limit error?

Thank you!

 

[slevis]

From what I remember, there are several posts in these Forums about this type of error. Look at how others resolved similar problems in case it helps you.

 

[chenyihui]

From what I remember, there are several posts in these Forums about this type of error. Look at how others resolved similar problems in case it helps you.

Thank you, I have solved the issue. I found that the atmospheric forcing data must cover a full year. Therefore, I regenerated the data and modified the stream from the initial version (Figure 1) to the revised version (Figure 2). In the end, the model ran successfully. (Also, when processing the data, pay attention to the User's guide, which states: "The time-stamps of the data were also adjusted so that they are the beginning of the interval for solar, and the middle for the other two.")