Hi,
I am running cesm with active ocean/ice components and forced by atmospheric reanalysis (JRA). The ocean grid is tx0.1v3.
resolution: TL319_t13
compset: 2000_DATM%JRA_SLND_CICE_POP2_DROF%JRA_SGLC_SWAV
cesmtag: cesm2.1.4-rc.08
I have finished 34 years without any issues but for some reason my latest restart run stopped midway into the run. I do my restart runs in two-year chunks and the latest run stopped exactly at the end of year 1. The error appears to be related to the dtlimit value corresponding to the TArcFactor data stream. Here is the output from the last part of the atm.log file:
Here are the dtlimit values in the datm_in file in the run/ folder:
I ran ncdump on the CORE2.t_10.ArcFactor.T62.1997-2004.nc file. It has 98 timestamps which span a period of 8 years. What I don't understand is why the run is failing now after running for 34 years.
Have other users seen this kind of error in their simulations?
I am running cesm with active ocean/ice components and forced by atmospheric reanalysis (JRA). The ocean grid is tx0.1v3.
resolution: TL319_t13
compset: 2000_DATM%JRA_SLND_CICE_POP2_DROF%JRA_SGLC_SWAV
cesmtag: cesm2.1.4-rc.08
I have finished 34 years without any issues but for some reason my latest restart run stopped midway into the run. I do my restart runs in two-year chunks and the latest run stopped exactly at the end of year 1. The error appears to be related to the dtlimit value corresponding to the TArcFactor data stream. Here is the output from the last part of the atm.log file:
Code:
(datm_comp_run) atm: model date 2831231 81600s
(datm_comp_run) atm: model date 2831231 82200s
(datm_comp_run) atm: model date 2831231 82800s
(datm_comp_run) atm: model date 2831231 83400s
(datm_comp_run) atm: model date 2831231 84000s
(datm_comp_run) atm: model date 2831231 84600s
(datm_comp_run) atm: model date 2831231 85200s
(datm_comp_run) atm: model date 2831231 85800s
(datm_comp_run) atm: model date 2840101 0s
(shr_dmodel_readstrm) file ub: /ihesp/obs_root/inputdata/ocn/jra55/v1.3_noleap/JRA.v1.3.swdn.TL319.1997.171019.nc 2
(shr_dmodel_readstrm) file ub: /ihesp/obs_root/inputdata/ocn/jra55/v1.3_noleap/JRA.v1.3.q_10.TL319.1997.171019.nc 2
(shr_dmodel_readstrm) file ub: /ihesp/obs_root/inputdata/ocn/jra55/v1.3_noleap/JRA.v1.3.slp.TL319.1997.171019.nc 2
(shr_dmodel_readstrm) file ub: /ihesp/obs_root/inputdata/ocn/jra55/v1.3_noleap/JRA.v1.3.t_10.TL319.1997.171019.nc 2
(shr_dmodel_readstrm) file ub: /ihesp/obs_root/inputdata/ocn/jra55/v1.3_noleap/JRA.v1.3.u_10.TL319.1997.171019.nc 2
(shr_dmodel_readstrm) file ub: /ihesp/obs_root/inputdata/ocn/jra55/v1.3_noleap/JRA.v1.3.v_10.TL319.1997.171019.nc 2
(shr_dmodel_readstrm) file ub: /ihesp/obs_root/inputdata/atm/datm7/CORE2/CORE2.t_10.ArcFactor.T62.1997-2004.nc 2
(shr_strdata_advance) ERROR: for stream 9
(shr_strdata_advance) ERROR: dt limit1 19345.0000000000
14.0000000000000 1.50000000000000
(shr_strdata_advance) ERROR: dt limit2 2840101 0 2840115
0
ERROR: (shr_strdata_advance) ERROR dt limit for stream
Here are the dtlimit values in the datm_in file in the run/ folder:
Code:
dtlimit = 1.5, 1.5, 1.5, 1.5, 1.5, 1.5, 1.5, 1.5, 1.5, 1.5
I ran ncdump on the CORE2.t_10.ArcFactor.T62.1997-2004.nc file. It has 98 timestamps which span a period of 8 years. What I don't understand is why the run is failing now after running for 34 years.
Have other users seen this kind of error in their simulations?