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

CLM case "BGC_spinup" run error

demibing

New Member
Hello everyone,

I've been encountering an issue while trying to practise the "BGC_spinup" case on the website https://escomp.github.io/ctsm-docs/versions/release-clm5.0/html/users_guide/running-special-cases/Spinning-up-the-biogeochemistry-BGC-spinup.html
When I submit case "BGC_spinup", the system displays follow messanges:

Setting resource.RLIMIT_STACK to -1 from (8388608, -1)
Creating component namelists
Calling /clm5.0/cime/src/components/data_comps/datm/cime_config/buildnml
Calling /clm5.0/cime_config/buildnml
Calling /clm5.0/cime/src/components/stub_comps/sice/cime_config/buildnml
Calling /clm5.0/cime/src/components/stub_comps/socn/cime_config/buildnml
Calling /clm5.0/components/mosart//cime_config/buildnml
Running /clm5.0/components/cism//cime_config/buildnml
Calling /clm5.0/cime/src/components/stub_comps/swav/cime_config/buildnml
Calling /clm5.0/cime/src/components/stub_comps/sesp/cime_config/buildnml
Calling /clm5.0/cime/src/drivers/mct/cime_config/buildnml
Finished creating component namelists
Checking that inputdata is available as part of case submission
Setting resource.RLIMIT_STACK to -1 from (-1, -1)
Loading input file list: 'Buildconf/cism.input_data_list'
Loading input file list: 'Buildconf/cpl.input_data_list'
Loading input file list: 'Buildconf/datm.input_data_list'
Loading input file list: 'Buildconf/mosart.input_data_list'
Loading input file list: 'Buildconf/clm.input_data_list'
Check case OK
submit_jobs case.run
Submit job case.run
Submitting job script sbatch --time 96:00:00 -p compute .case.run --resubmit
Submitted job id is 407
Submit job case.st_archive
Submitting job script sbatch --time 0:20:00 -p compute --dependency=afterok:407 case.st_archive --resubmit
Submitted job id is 408
Submitted job case.run with id 407
Submitted job case.st_archive with id 408


Unfortunately, I couldn't identify the specific problem based on the prompt provided by the system. So I check the casestatus, and the system show follow messages:

2023-06-14 16:33:58: xmlchange success <command> ./xmlchange CLM_ACCELERATED_SPINUP=on </command>
---------------------------------------------------
2023-06-14 16:34:14: case.setup starting
---------------------------------------------------
2023-06-14 16:34:15: case.setup success
---------------------------------------------------
2023-06-14 16:34:31: case.build starting
---------------------------------------------------
2023-06-14 16:38:27: case.build success
---------------------------------------------------
2023-06-14 16:41:06: xmlchange success <command> ./xmlchange RESUBMIT=3,STOP_N=50,STOP_OPTION=nyears,STOP_DATE=02010101 </command>
---------------------------------------------------
2023-06-14 16:41:40: case.submit starting
---------------------------------------------------
2023-06-14 16:41:45: case.submit success case.run:405, case.st_archive:406
---------------------------------------------------
2023-06-14 16:41:46: case.run starting
---------------------------------------------------
2023-06-14 16:41:51: model execution starting
---------------------------------------------------
2023-06-14 16:41:52: model execution success
---------------------------------------------------
2023-06-14 16:41:52: case.run error
ERROR: RUN FAIL: Command 'mpirun -n 80 clm5.0/cime/scripts/BGC_spinup/BGC_spinup/bld/cesm.exe >> cesm.log.$LID 2>&1 ' failed
See log file for details: clm5.0/cime/scripts/BGC_spinup/BGC_spinup/run/cesm.log.405.230614-164146


Has anyone else experienced a similar issue or can offer guidance on how to resolve this error? Any assistance or suggestions would be greatly appreciated.

Thank you in advance for your help!"
 

oleson

Keith Oleson
CSEG and Liaisons
Staff member
You will need to look at the log files to determine the error, e.g., clm5.0/cime/scripts/BGC_spinup/BGC_spinup/run/cesm.log.405.230614-164146
 

demibing

New Member
"Thank you for getting back to me. I've checked the log files and I'm wondering if the error message 'timeaddmonths(): MM out of range' indicates the source of the problem. Could you please advise on how to fix this issue?
 

Attachments

  • cesm.log.405.230614-164146.txt
    33 KB · Views: 3

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I don't recognize that error message so I grepped for "timeaddmonths" in release-cesm2.1.3 and got:

cime/src/share/esmf_wrf_timemgr/ESMF_TimeMod.F90: CALL timeaddmonths( time, MM, ierr )
cime/src/share/esmf_wrf_timemgr/ESMF_TimeMod.F90: ! PRINT *,'DEBUG: ESMF_TimeSet(): back from timeaddmonths'
cime/src/share/esmf_wrf_timemgr/ESMF_TimeMod.F90: SUBROUTINE timeaddmonths( time, MM, ierr )
cime/src/share/esmf_wrf_timemgr/ESMF_TimeMod.F90: CALL wrf_message( 'ERROR timeaddmonths(): MM out of range' )
cime/src/share/esmf_wrf_timemgr/ESMF_TimeMod.F90: END SUBROUTINE timeaddmonths

Which doesn't make any sense to me since you are running a CLM5 spinup, not sure why the esmf_wrf time manager is being called.
Not sure what to suggest other than we might be able to help further if you provide the information requested here:

 
Top