BHIST restart run error

xiangli · Feb 29, 2024

Dear all,

I'm working on running a hybrid simulation using restart files of a BHIST historical run, but the model reported en error after running about 60 seconds.

Here is the cesm.log:

Here is the atm.log:

Similar errors have been reported in several other threads but it seems that they have not been solved yet.

Run FIST compset in CESM2.2 - error set_time_float_from_date

Greetings, I am trying to run a case using the FHIST compset. ./create_newcase --case $casename --compset FHIST --res f09_f09_mg17 And specifying the date and step tun such as: ./xmlchange RUN_STARTDATE=20100101,STOP_OPTION=ndays,STOP_N=2,DOUT_S=FALSE The case compiles but gives me this...

bb.cgd.ucar.edu

ERROR timeaddmonths(): MM out of range

Hello, I tried running CESM2.1 compset B1850 (after successfully building cesm.exe), but the run crashed with the following error in the cesm.log: ERROR timeaddmonths(): MM out of range set_time_float_from_date: error return from ESMF_TimeSet for set_time_float_from_date ERROR: CHKRC Any...

bb.cgd.ucar.edu

ERROR: CHKRC ERROR timeaddmonths(): MM out of range set_time_float_from_date: error return from ESMF_TimeSet for set_time_float_from_date

您好，我目前正在学习和使用 CESM 模式。我正在运行在大气模式下使用 2000-CM60% CCTS 的案例配置，从设置到编译都没有问题。提交时将报告错误。错误：CHKRC 错误 timeaddmonth（）： MM 超出范围 Set_ Time_ Float_ From_日期：从set_ Time_ Float_ From_日期的时间集ESMF_返回错误我尝试了一些方法，但没有一种方法解决了此错误的问题，因此我想冒昧地寻求您的帮助。如果您熟悉这方面，希望您能帮助我回答此错误的原因以及如何解决它

bb.cgd.ucar.edu

Any suggestions would be greatly appreciated!

Thanks,
Xiang

sacks · Feb 29, 2024

I see that the time values in that file look funny for the first few times: the first 16 time values are:

Code:

 time = 674900.5, 674930, 674959.5, 674990, 675020.5, 675051, 675081.5,
    675112.5, 675143, 675173.5, 675204, 675234.5, 3665.5, 3695, 3724.5, 3755,

but I'm not sure if that's the cause of the error: the file leading to the error in Run FIST compset in CESM2.2 - error set_time_float_from_date seems to have reasonable time values.

I'm going to move this to the atmosphere forum since this problem is arising in CAM. Can you please provide more details about your run setup? See Information to include in help requests for the details we'd like to see in help requests.

xiangli · Feb 29, 2024

sacks said:
I see that the time values in that file look funny for the first few times: the first 16 time values are:

Code:

time = 674900.5, 674930, 674959.5, 674990, 675020.5, 675051, 675081.5, 675112.5, 675143, 675173.5, 675204, 675234.5, 3665.5, 3695, 3724.5, 3755,

but I'm not sure if that's the cause of the error: the file leading to the error in Run FIST compset in CESM2.2 - error set_time_float_from_date seems to have reasonable time values.

I'm going to move this to the atmosphere forum since this problem is arising in CAM. Can you please provide more details about your run setup? See Information to include in help requests for the details we'd like to see in help requests.

Hi Bill,

Thanks for your reply. This is how I did the restart run:

1) ./create_newcase --case /work/xl468/cesm2.1/scratch/case/test_BHIST_240229 --res f19_g17 --compset BHIST --mach duke

2) ./case.setup

3) modify env_run.xml as follows:

Here is where I deposit the restart files:

4) copy user_nl_* files to case directory

5) ./case.build

6) ./case.submit

The restart files and user_nl_* files are from Gary through this thread (Restart files of CESM2.1 experiments).

Below is my CaseStatus:

2024-02-29 10:34:56: case.setup starting

---------------------------------------------------

2024-02-29 10:34:58: case.setup success

---------------------------------------------------

2024-02-29 10:39:26: case.build starting

---------------------------------------------------

CESM version is release-cesm2.1.5

Processing externals description file : Externals.cfg (/hpc/group/hulab/xl468/cesm2.1/my_cesm_sandbox)

Processing externals description file : Externals_CAM.cfg (/hpc/group/hulab/xl468/cesm2.1/my_cesm_sandbox/components/cam)

Processing externals description file : Externals_CISM.cfg (/hpc/group/hulab/xl468/cesm2.1/my_cesm_sandbox/components/cism)

Processing externals description file : Externals_CLM.cfg (/hpc/group/hulab/xl468/cesm2.1/my_cesm_sandbox/components/clm)

Processing externals description file : Externals_POP.cfg (/hpc/group/hulab/xl468/cesm2.1/my_cesm_sandbox/components/pop)

Checking local status of required & optional components: cam, chem_proc, carma, clubb, cosp2, cice, cime, cism, source_cism, clm, fates, mosart, pop, cvmix, marbl, rtm, ww3,

sM ./cime

modified sandbox, b5d9ed98288775632ca71ab0d13af4efde5d9db6 (branch maint-5.6) --> cime5.6.49

./components/cam

clean sandbox, on cam_cesm2_1_rel_60

./components/cam/chem_proc

clean sandbox, on tools/proc_atm/chem_proc/release_tags/chem_proc5_0_03_rel

./components/cam/src/physics/carma/base

clean sandbox, on carma/release_tags/carma3_49_rel

./components/cam/src/physics/clubb

clean sandbox, on vendor_clubb_r8099_n03

./components/cam/src/physics/cosp2/src

clean sandbox, on v2.1.4cesm

./components/cice

clean sandbox, on cice5_cesm2_1_1_20231220

./components/cism

clean sandbox, on cism-release-cesm2.1.2_04

./components/cism/source_cism

clean sandbox, on release-cism2.1.04

./components/clm

clean sandbox, on release-clm5.0.37

./components/clm/src/fates

clean sandbox, on sci.1.30.0_api.8.0.0

./components/mosart

clean sandbox, on release-cesm2.0.04

./components/pop

clean sandbox, on pop2_cesm2_1_rel_n15

./components/pop/externals/CVMix

clean sandbox, on v0.93-beta

./components/pop/externals/MARBL

clean sandbox, on cesm2.1-n00

./components/rtm

clean sandbox, on release-cesm2.0.04

./components/ww3

clean sandbox, on ww3_181001

2024-02-29 10:54:53: case.build success

---------------------------------------------------

2024-02-29 10:57:35: case.submit starting

---------------------------------------------------

2024-02-29 10:57:48: case.submit success case.run:4228706, case.st_archive:4228707

---------------------------------------------------

2024-02-29 10:58:20: case.run starting

---------------------------------------------------

2024-02-29 10:58:35: model execution starting

---------------------------------------------------

2024-02-29 10:59:26: model execution success

---------------------------------------------------

2024-02-29 10:59:26: case.run error

ERROR: RUN FAIL: Command 'mpirun -np 192 /work/xl468/cesm2.1/scratch/test_BHIST_240229/bld/cesm.exe >> cesm.log.$LID 2>&1 ' failed

See log file for details: /work/xl468/cesm2.1/scratch/test_BHIST_240229/run/cesm.log.4228706.240229-105820

---------------------------------------------------

Thanks,
Xiang

xiangli · Mar 1, 2024

sacks said:
I see that the time values in that file look funny for the first few times: the first 16 time values are:

Code:

time = 674900.5, 674930, 674959.5, 674990, 675020.5, 675051, 675081.5, 675112.5, 675143, 675173.5, 675204, 675234.5, 3665.5, 3695, 3724.5, 3755,

but I'm not sure if that's the cause of the error: the file leading to the error in Run FIST compset in CESM2.2 - error set_time_float_from_date seems to have reasonable time values.

I'm going to move this to the atmosphere forum since this problem is arising in CAM. Can you please provide more details about your run setup? See Information to include in help requests for the details we'd like to see in help requests.

Hi Bill,

I found the time value in this file (/inputdata/atm/cam/tracer_cnst/tracer_cnst_halons_3D_L70_1849-2015_CMIP6ensAvg_c180927.nc) looks strange:

Is there something wrong with this input file for BHIST?

Thanks,
Xiang

strandwg · Mar 1, 2024

The values for "time" aren't important since the model uses "date" for the time interpolation needed.
However, the zeroes for "time" often indicate an incomplete file. Can you check the file size of your local copy of

tracer_cnst_halons_3D_L70_1849-2015_CMIP6ensAvg_c180927.nc

It should be 17700928924 bytes.

xiangli · Mar 1, 2024

strandwg said:
The values for "time" aren't important since the model uses "date" for the time interpolation needed.
However, the zeroes for "time" often indicate an incomplete file. Can you check the file size of your local copy of

tracer_cnst_halons_3D_L70_1849-2015_CMIP6ensAvg_c180927.nc

It should be 17700928924 bytes.

Hi Gary,

Yes, I think my file is not complete, which is only 1102881040 bytes.

I'm trying to know how to update my check_input_data script.

Thanks,
Xiang

xiangli · Mar 1, 2024

Hi Jim,

@jedwards

As Gary pointed out, my /inputdata/atm/cam/tracer_cnst/tracer_cnst_halons_3D_L70_1849-2015_CMIP6ensAvg_c180927.nc is incomplete. I guess that is probably why my BHIST case would fail (error messages shown in #1). Is this related to my check_input_data script?

Thanks,
Xiang

strandwg · Mar 1, 2024

xiangli said:
Hi Jim,

@jedwards

As Gary pointed out, my /inputdata/atm/cam/tracer_cnst/tracer_cnst_halons_3D_L70_1849-2015_CMIP6ensAvg_c180927.nc is incomplete. I guess that is probably why my BHIST case would fail (error messages shown in #1). Is this related to my check_input_data script?

Thanks,
Xiang

It's more likely your allocated disk space is full and so input datafiles cannot be transferred completely. Check and make sure where you're trying to run CESM has ample space available.

xiangli · Mar 1, 2024

strandwg said:
It's more likely your allocated disk space is full and so input datafiles cannot be transferred completely. Check and make sure where you're trying to run CESM has ample space available.

Hi Gary,

Exactly! Now I downloaded the complete file and got past the error!

Thanks,
Xiang

BHIST restart run error

xiangli

Xiang Li

Member

Run FIST compset in CESM2.2 - error set_time_float_from_date

ERROR timeaddmonths(): MM out of range

ERROR: CHKRC ERROR timeaddmonths(): MM out of range set_time_float_from_date: error return from ESMF_TimeSet for set_time_float_from_date

sacks

Bill Sacks

CSEG and Liaisons

xiangli

Xiang Li

Member

xiangli

Xiang Li

Member

strandwg

Moderator

xiangli

Xiang Li

Member

xiangli

Xiang Li

Member

strandwg

Moderator

xiangli

Xiang Li

Member