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

Basic questin about cesm2.1.3

JaeSeung-Yoon

New Member
Hi all,
I am doing CESM2.1.3 for the first time.
I have what must be a very basic question about the CESM2.1.3

1. ./create_newcase --case /home/jsyoon/MODEL/CESM/cesm2.1.3/cases/Atest.f19_g17_rx1 --compset A --res f19_g17_rx1 --machine hanul
2. ./xmchange STOP_OPTION=nyears,STOP_N=5,RESUBMIT=19,RUN_TYPE=startup,CONTINUE_RUN=FALSE
I received a message from "CaseStatus" saying "st_archive success"
As a result, I confirmed that *.bin and *.nc files were created in the "./run" directory. Is this a normal result?
If so, how do I change files *.bin to *.nc or *.grib?

Thank you in advance.
 

sur23beeb

ST
Member
Really appreciate your prompt response. I was thinking about this some more yesterday and thought the reason it continued from 0265-03 even with continue_run=.false is step #3, where I ran ./case.build. I think because I rebuilt the case, cesm probably treated the 0265-03 restart file as the beginning of the branch run, even though the branch began two months earlier at 0265-01. If 0265-03 is treated as the beginning of the branch run, then continue_run=.false. is the proper setting and there are no errors.

The run that started at 0265-03 ran for a month and I started another run, now ongoing, from 0265-04 (without any new ./case.build) but this time I used continue_run=.true.. It is quite likely (I think) that if I had left continue_run=.false., the continuation run from 0265-04 would have thrown an error.

Does this explanation make sense?
 
Top