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

Date in cesm

khj

Parisa
Member
Hi all,
I want to run FWscHIST component with f09_f09_mg17 resolution. I only want to run the model for 2017, but I do not know what needs to change in the env-run.xml file.
I would be grateful if you guided me through this.

Thanks in advance
 

altuntas

Alper Altuntas
Moderator
Staff member
You can run the following xmlchange command to change the run date:

Code:
./xmlchange RUN_STARTDATE=2017-01-01

Similarly, you can change the STOP_N and STOP_OPTION variables to adjust your run duration:

Code:
./xmlchange STOP_OPTION=nyears
./xmlchange STOP_N=1
 

nuvolet

Toni Viudez
Member
You can run the following xmlchange command to change the run date:

Code:
./xmlchange RUN_STARTDATE=2017-01-01

Similarly, you can change the STOP_N and STOP_OPTION variables to adjust your run duration:

Code:
./xmlchange STOP_OPTION=nyears
./xmlchange STOP_N=1
I was wondering that:
Code:
./xmlchange RUN_STARTDATE=2017-01-01
could be also use like:
Code:
./xmlchange RUN_STARTDATE=20170101

Thanks
 

khj

Parisa
Member
Thank you very much for your answer.
Is it possible to specify the time step of run the model?For example, is it possible to output the model with a 12-hour time step for one year?
And another question is related to downloading Verdi data to the model. In this case, will the data be downloaded for only one year (for example, only for 2017)?

yours sincerely
 

altuntas

Alper Altuntas
Moderator
Staff member
You can change the coupling timestep of each component using the xmlchange command. To change the coupling timestep of a particular component, say ATM, you can run:

./xmlchange ATM_NCPL=24

The above command sets the atmosphere coupling timestep to 1 hour, since the NCPL_BASE_PERIOD is set to "day" by default.

Additionally, each component has one or more internal timesteps. Similarly, each component has its own way of modifying the history output frequencies. Both the internal timestep(s) and history output frequencies are typically set via user_nl_ files. Please refer to the individual component documentations.

As for the data to be downloaded, I believe the run start date and duration do not limit the amount of data that cime will download. (I might be wrong).
 
Top