ERROR: calendar dates must be increasing, user added atmospheric forcing

[katiemurenbeeld@u_boisestate_edu]

Hi All,

I was able to successfully complete about 4 years of a single point case using CLM-FATES with my own 1-HR WRF climate forcing dataset.

However, when the model attempted to from 1992-01-31 to 1992-02-01 I received this error:

> cat /glade/scratch/katiem/junk_ID_WRF_10yr_test003_1pt_e33b4658_7c065e21/run/atm.log.3421871.chadmin1.ib0.cheyenne.ucar.edu.200730-165836

...
(shr_dmodel_readstrm) file ub: /glade/work/katiem/FATES_data/ID/singlept/WRF/TPQWL/BBEF1pt__clmforc_WRF30d02_c2018_1kmx1km_1992_01_TPQWL.nc 744 (datm_comp_run) atm: model date 19920131 81000s (datm_comp_run) atm: model date 19920131 82800s (shr_stream_verifyTCoord) ERROR: calendar dates must be increasing (shr_stream_verifyTCoord) date(n), date(n+1) = 19920131 19920101 ERROR: (shr_stream_verifyTCoord) ERROR: calendar dates must be increasing...

I've checked the files BBEF1pt__clmforc_WRF30d02_c2018_1kmx1km_1992_01_TPQWL.nc and BBEF1pt__clmforc_WRF30d02_c2018_1kmx1km_1992_02_TPQWL.nc

but I did not find any issues with the dates or times. Any insight would be greatly appreciated!

As a note the time:calendar = "proleptic_gregorian" within these .nc files.

Cheers,
Katie

Background:
machine = Cheyenne
clm release = release-clm5.0.30-79-ge33b4658
externals =
./cime
clean sandbox, on cime5.6.28
./components/cism
clean sandbox, on cism-release-cesm2.1.2_01
./components/cism/source_cism
clean sandbox, on release-cism2.1.03
./components/mosart
clean sandbox, on release-cesm2.0.04
./components/rtm
clean sandbox, on release-cesm2.0.04
./src/fates
clean sandbox, on sci.1.36.0_api.11.2.0
./tools/PTCLM
clean sandbox, on PTCLM2_20200121

 

[oleson]

One possibility is that the forcing is not lining up properly because you have "proleptic_gregorian" encoded within your forcing files, but your "CALENDAR" in env_build.xml is set to "NO_LEAP". Try setting this to "GREGORIAN", clean the build, re-build, and re-start your simulation from the beginning.

 

[katiemurenbeeld@u_boisestate_edu]

Thank you Keith! I will give that a try.

 

[katiemurenbeeld@u_boisestate_edu]

Hi Keith,

That didn't solve the problem. The case still failed moving from Jan 1992 to Feb 1992. I created another test case.

case file path:
/glade/work/katiem/FATES_cases/WRF/junk_ID_WRF_10yr_test005_1pt_e33b4658_7c065e21

bld/run path:
/glade/scratch/katiem/junk_ID_WRF_10yr_test005_1pt_e33b4658_7c065e21/

hist path:
/glade/scratch/katiem/archive/junk_ID_WRF_10yr_test005_1pt_e33b4658_7c065e21/

I'll have a deeper dive into the atmospheric forcing data files I created. Maybe there is a mix up with the times somewhere. Thanks again for your help.

Cheers,
Katie

 

[oleson]

Ok, I see a problem. There is a duplicated file in your solar streams:

BBEF1pt__clmforc_WRF30d02_c2018_1kmx1km_1992_01_Solar.nc
BBEF1pt__clmforc_WRF30d02_c2018_1kmx1km_1992_01_Solar.nc

 

[katiemurenbeeld@u_boisestate_edu]

Oh my gosh! Thank you for catching that. I'll make sure to double check all of the user_datm.streams and make sure there are no other duplicates.

Thank you!