ccchang3@illinois_edu
New Member
Dear the CISM/CESM community:
I tried to do a branch run based on the CMIP6 CESM2 piControl restart files.
I start the run from year 0301-01-01, and I used CESM2.1.0 B1850 f09_g17 compset.
However, I got a problem that seems to be related to CISM time manager, see the following error message from glc.log.11421111.bw.200727-130911:
(time_manager) glc date 0001-dec-27, 0.000000E+00 sec
(time_manager) glc date 0001-dec-28, 0.000000E+00 sec
(time_manager) glc date 0001-dec-29, 0.000000E+00 sec
(time_manager) glc date 0001-dec-30, 0.000000E+00 sec
(time_manager) glc date 0001-dec-31, 0.000000E+00 sec
* FATAL ERROR : (glad_main.F90:650) Valid_inputs cannot be .false. if trying
to do a mass balance time step
*******************************************************************************
Finished logging at 2020-07-27 13:22:50.307
*******************************************************************************
In my env_run.xml, I set GLC_AVG_PERIOD="yearly".
Interesting, when I set GLC_AVG_PERIOD='glc_coupling_period', the run can be integrated. However, the CISM seems to failed in generating a restart file at the end of the mid year.
Can anyone help me with this issue?
I really appreciate.
Sincerely,
Jay
I tried to do a branch run based on the CMIP6 CESM2 piControl restart files.
I start the run from year 0301-01-01, and I used CESM2.1.0 B1850 f09_g17 compset.
However, I got a problem that seems to be related to CISM time manager, see the following error message from glc.log.11421111.bw.200727-130911:
(time_manager) glc date 0001-dec-27, 0.000000E+00 sec
(time_manager) glc date 0001-dec-28, 0.000000E+00 sec
(time_manager) glc date 0001-dec-29, 0.000000E+00 sec
(time_manager) glc date 0001-dec-30, 0.000000E+00 sec
(time_manager) glc date 0001-dec-31, 0.000000E+00 sec
* FATAL ERROR : (glad_main.F90:650) Valid_inputs cannot be .false. if trying
to do a mass balance time step
*******************************************************************************
Finished logging at 2020-07-27 13:22:50.307
*******************************************************************************
In my env_run.xml, I set GLC_AVG_PERIOD="yearly".
Interesting, when I set GLC_AVG_PERIOD='glc_coupling_period', the run can be integrated. However, the CISM seems to failed in generating a restart file at the end of the mid year.
Can anyone help me with this issue?
I really appreciate.
Sincerely,
Jay