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

SSP585 simulation breaks in year 2095

D

demetray

Demetra Yancopoulos
New Member
I am using CESM2.1.3 and running a CMIP6 SSP5-85 simulation (2015-2100) with the component set SSP585_CAM60_CLM50%BGC-CROP-CMIP6DECK_CICE%CMIP6_POP2%ECO%ABIO-DIC_MOSART_CISM2%NOEVOLVE_WW3_BGC%BDRD.

I have been submitting simulations in 3-year chunks. I have successfully run the model through the year 2092 (with restart files for 2093-01-01). At that point, the simulation restarts and runs for a while. However, it randomly stops during this run. In the run directory, files seem to be populated until the date 2095-06-01, but nothing after 2092-12-01 exists in the output files. So, the run never finishes. I can't find any sign of the error in the log files. I am totally stumped.

I have resubmitted the simulation a couple times and the same thing happens.

Any suggestions for where I can look to diagnose the error? Anybody encounter this error before with an SSP5-85 compset? Are there files I should clear out in the case or run directory before resubmitting the simulation?
 
Sort by date Sort by votes
slevis

slevis

Moderator
Staff member
Unless somebody has a different suggestion, I would start by checking whether you have filled some disk space beyond your quota. If not, I would want to know whether the model stops at the same timestep and in the same exact way every time. I might start writing restart files more frequently so as to restart the simulation closer to the point of failure and eventually possibly start adding write statements in the code that may help reveal where the model crashes.
 
Vote Upvote 0 Downvote
D

demetray

Demetra Yancopoulos
New Member
slevis said:
Unless somebody has a different suggestion, I would start by checking whether you have filled some disk space beyond your quota. If not, I would want to know whether the model stops at the same timestep and in the same exact way every time. I might start writing restart files more frequently so as to restart the simulation closer to the point of failure and eventually possibly start adding write statements in the code that may help reveal where the model crashes.
Click to expand...
Thank you for the advice! I have plenty of space left in scratch (and have some other experiments running and storing output there with no problems). I will start by writing the restart files more frequently. What kind of write statements and where should I put them?
 
Vote Upvote 0 Downvote
You must log in or register to reply here.
Top