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

CESM is aborted abruptly during the running

CESM_freshmen

Tony
New Member
I'm a freshman in the CESM. The version is 2.1.3.
I have successfully done the X-test.
When I was running the BHIST scenario, I could successfully compile and submit the jobs. However, the running is aborted abnormally. There is little information in log file. I don't know how to fix it. Could anyone help me?
The process of running is as follows:
./create_newcase --case /public/home/Apps/cesm_example --res f19_g17 --compset BHIST --machine admin
cd /public/home/Apps/cesm_example
./case.setup
./case.build
./case.submit
The versions of my CESM and log files during running are attached below.
 

Attachments

  • version.log.txt
    8.4 KB · Views: 2
  • atm.log.txt
    413.5 KB · Views: 1
  • cpl.log.txt
    87.5 KB · Views: 2
  • glc.log.txt
    19.5 KB · Views: 1
  • ice.log.txt
    68.6 KB · Views: 1
  • lnd.log.txt
    204.8 KB · Views: 2
  • ocn.log.txt
    976.4 KB · Views: 1
  • rof.log.txt
    36.2 KB · Views: 1
  • wav.log.txt
    19.3 KB · Views: 1

nusbaume

Jesse Nusbaumer
CSEG and Liaisons
Staff member
Hi Tony,

I didn't see anything in your provided log files that indicate that an error has occurred. Did the model produce a cesm.log file? If so then it might help to include that here. Along with that, did your batch system produce an output file? It may be in your case directory with a name like run.<case_name>.o12345. If so then passing that along as well might help.

Finally, you could try an intermediate configuration like FHIST to see if that runs (or not).

Thanks, and have a great day!

Jesse
 

nusbaume

Jesse Nusbaumer
CSEG and Liaisons
Staff member
Hi Tony,

I forgot to mention that another option may be to try the run with debugging switched on. This can be done by running the following commands in your case directory:

Code:
./xmlchange DEBUG=TRUE
./case.build --clean-all
./case.build
./case.submit

Please note that running with debug flags on will cause your simulation to run noticeably slower, but if there is a model failure then it can sometimes produce a meaningful log message even when the standard model setup fails to do so.

Anyways, I hope that helps, and good luck!

Jesse
 
Top