Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

run error with calendar dates

xgao304

Member
I am running the compset "2000_DATM%CRUv7_CLM50%BGC_SICE_SOCN_SROF_SGLC_SWAV" at a single point. The forcing I am using
is the CRU-JRA v2.2 (1901-2020), but I processed the data into the format compatible with those used for cesm. Here is the list of command and setting:

./create_newcase --case hvd --compset 2000_DATM%CRUv7_CLM50%BGC_SICE_SOCN_SROF_SGLC_SWAV --res hcru_hcru --machine svante --compiler intel --run-unsupported

RUN_STARTDATE: 1901-01-01
DATM_CLMNCEP_YR_ALIGN: 1901
DATM_CLMNCEP_YR_START: 1901
DATM_CLMNCEP_YR_END: 1920

I am able to generate the output for 4 years and 10 months, then I got this ERROR: (shr_stream_verifyTCoord) ERROR: calendar dates must be increasing.

The atm.log.* file indicates that the error comes from solar radiation with these weird date(n) and date(n+1)

(shr_dmodel_readstrm) close : /net/fs05/d1/cesm2/inputdata/atm/datm7/atm_forcing.datm7.crujra/Solar6Hrly/clmforc.cruncep.V7.c2016.0.5d.Solr.1905-11.nc
(shr_dmodel_readstrm) open : /net/fs05/d1/cesm2/inputdata/atm/datm7/atm_forcing.datm7.crujra/Solar6Hrly/clmforc.cruncep.V7.c2016.0.5d.Solr.1905-12.nc
(shr_dmodel_readstrm) file ub: /net/fs05/d1/cesm2/inputdata/atm/datm7/atm_forcing.datm7.crujra/Solar6Hrly/clmforc.cruncep.V7.c2016.0.5d.Solr.1905-12.nc 1
(datm_comp_run) atm: model date 19051130 66600s
(datm_comp_run) atm: model date 19051130 68400s
(datm_comp_run) atm: model date 19051130 70200s
(datm_comp_run) atm: model date 19051130 72000s
(datm_comp_run) atm: model date 19051130 73800s
(datm_comp_run) atm: model date 19051130 75600s
(shr_stream_verifyTCoord) ERROR: calendar dates must be increasing
(shr_stream_verifyTCoord) date(n), date(n+1) = 19051213 19051201

I processed the data in a consistent way. I tested with cycling with another 20 years of forcing data, eg. 1911-1930, the 20-year run can be completed successfully. I also examined the solar radiation data for 1905-12, but the data looks fine to me.

Is there any way to diagnose which part went wrong?

Thanks,


Xiang
 

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I would check the values of the time variable on the 1905-12 file to make sure they are monotonically increasing, and also check the units attribute for the time variable to make sure it is appropriate. Also, it's not clear if it is the solar file that has the problem, I'd check the other forcing files as well (precip, temperature, etc.).
 

xgao304

Member
Thanks for the information. I found the problem. I was focusing on the solar files, but it turned out that the problem comes from the precipitation.
 

icetea

Yue Cheng
New Member
Thanks for the information. I found the problem. I was focusing on the solar files, but it turned out that the problem comes from the precipitation.
Hello, I am currently facing some difficulties with calendar dates must be increasing. Earlier, you mentioned that you had a similar problem and were able to resolve it. Would you be able to provide me with any insight or guidance on how I can approach this particular issue? Thank you in advance for your time and help.
 
Top