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

Ad_spinup

Hi,

I'm following instructions in the CLM4 User's Guide for doing an AD spinup. I've tried to append "-ad_spinup on" to CLM_CONFIG_OPTS in env_conf.xml, but the xmlchange command recommended by the User's Guide gives an error that -append is an unrecognized argument.

My question is, how can I manually change this using a text editor? Should it be

entry id="CLM_CONFIG_OPTS" value "-bgc cn -ad_spinup on" or
entry id="CLM_CONFIG_OPTS" value "-bgc cn" "-ad_spinup on" or yet something else?

Thanks,

Cindy
 

erik

Erik Kluzek
CSEG and Liaisons
Staff member
Cindy the "-append" mode was added to create_newcase in cesm1_0_3. You could update to it to get it working. Using a text editor you want to have...

entry id="CLM_CONFIG_OPTS" value="-bgc cn -ad_spinup on"

ADD "user_nl_clm" BEFORE configure...

By the way, also make sure you create your "user_nl_clm" file BEFORE configure -- instead of after as the instructions show in order to have it take into affect. The instructions are wrong in that regard and I'm planning on fixing it, but haven't had a chance yet.
 
Hi Erik,

I've run into a few more problems with the AD spinup instructions: As you mentioned, I found that the &clm_inparm command didn't work (still gave monthly history files) if I made it after configuring. So (before seeing your message) I tried changing env_conf.xml to read
"CLM_NAMELIST_OPTS" value ="hist_htfrq=-8760" before configuring.
In this case, no history files were written. However, for both cases, the model reached the LSF run time limit after about 4 to 5 years, not the 20 years recommended in the User's Guide. My questions are:
1) Is it okay to use the CLM_NAMELIST_OPTS as I've done, and if so, why weren't annual history files written?
2) Should I change STOP_N to 4 (nyears) and RESUBMIT to 150, or could there be another reason why the model is running out of time? Aside from what I've mentioned above, I'm following example 4-3 in the User's Guide to the letter.

Thanks,

Cind
 

erik

Erik Kluzek
CSEG and Liaisons
Staff member
Hi Cindy

Actually that should be...

"CLM_NAMELIST_OPTS" value ="hist_nhtfrq=-8760"

(note the n). But, since your run worked I figure you must have got it right. And yes the above would be fine to use in place of the user_nl_clm file. They both end up doing the same thing in the end.

I'm not quite sure why you didn't get any history files. If the number of time-samples is 30, you wouldn't get your history files to close until you run for 30 years. But, you should get a history file for at least the first year. You might want to make sure you control the number of time samples by setting "hist_mfilt=1".

The 20 years at a shot is a guess for run length that makes sense for bluefire, but may NOT be a good guess for a different machine or a different resolution. If your machine is only getting you 4 years at a time, then yes set the run length to 4 with more submissions. I can't think of anything that would really be slowing your run down, unless you are running with DEBUG=TRUE in env_build.
 
Hi Erik,

I successfully ran 601 years following the AD_spinup instructions in Example 4-3, but am having problems with the Exit spinup in Example 4-4. Could there be a problem or typo in this step:

cp /ptmp/nevison/archive/CN_spinup/rest/CN_spinup.*.r*.0601-01-01-00000* /ptmp/nevison/CN_exitspinup

First, there is an extra directory in the path to my spinup restart files: archive/CN_spinup/rest/0601-01-01-00000/ (I see 4 files that the wildcards apply to)

Second, it seems like the files should be copied to ptmp/nevison/CN_exitspinup/run

I tried both ways (with and without the extra run directory), but in both cases the model exited immediately. The main clue in stdout was the following:


The following files were not found, this is informational only
Input Data List Files Found:
/blhome/nevison/cesm1_0_3/scripts/EXcdn2/Buildconf/clm.input_data_list
/blhome/nevison/cesm1_0_3/scripts/EXcdn2/Buildconf/cpl.input_data_list
/blhome/nevison/cesm1_0_3/scripts/EXcdn2/Buildconf/datm.input_data_list
File status unknown: ADcdn3.clm2.r.0601-01-01-00000.nc

Even though all 4 of the above files seem to be in the correct directories as far as I can tell (note that ADcdn3 is the actual name of my 601 year spinup case and EXcdn2 is the actual name of my exit spinup case).

Could there be some missing information in the User's Guide for Example 4-4?

Thanks,

Cindy
 

slevis

Moderator
Staff member
Cindy,

You're probably right about the typos. I'm not sure why the branch didn't work once you corrected those. However, you don't need to start this as a branch. You may start it as a "startup" in which case you'd set finidat instead of nrevsn to the 601 restart file from your ad_spinup run.

Sam
 

erik

Erik Kluzek
CSEG and Liaisons
Staff member
We've updated the User's Guide. Hopefully it fixes the documentation issues with the spinup-procedure that you and others found. Let us know if there is anything else wrong with the procedure.
 
Top