Change component set#
Choose which CLM compset you want to run:
- CLM-BGC:
I2000Clm60BgcCrujra - CLM-BGC Crop:
I2000Clm60BgcCropCrujra - CLM-FATES SP:
I2000Clm60FatesSpCruRsGs
Create a case using the selected compset using f19_f19_mt233 resolution.
Note: You will still need to use the “–run-unsupported” flag.
Check the status of the run after submitting.
Click here for hints
Are you in the right workspace?
Navigate to my_clm_code/cime/scripts before running the ./create.case command
cd /glade/u/home/$USER/code/my_clm_code/cime/scripts
Did you give your new case a new name?
You can create a new case with the command:
NEW_CASE_NAME='i2000_fates.basics'
./create_newcase --case /glade/u/home/$USER/cases/$NEW_CASE_NAME --res RES --compset COMPSET --run-unsupported
Did you navigate to the case directory to set up the case?
You can invoke case set up as follows:
cd /glade/u/home/$USER/cases/i2000_fates.basics
./case.setup
Did you remember to extend the length of the run to 1 month?
./xmlchange STOP_OPTION=nmonths
./xmlchange STOP_N=1
Click here for the solution
Create a new case i2000_fates.basics with the command:
cd /glade/u/home/$USER/code/my_clm_code/cime/scripts
./create_newcase --case /glade/u/home/$USER/cases/i2000_fates.basics --res f19_f19_mt233 --compset I2000Clm60FatesSpCruRsGs --run-unsupported
Case setup:
cd /glade/u/home/$USER/cases/i2000_fates.basics
./case.setup
Change the queue to the ‘tutorial’ queue:
./xmlchange JOB_QUEUE=tutorial --force
Extend the length of the run to 1 month:
./xmlchange STOP_OPTION=nmonths
./xmlchange STOP_N=1
Build and submit:
qcmd -- ./case.build
./case.submit
Check the status:
qstat -u $USER
When the run is completed, look into the archive directory for: i2000_fates.basics.
Check that your archive directory on derecho (The path will be different on other machines):
cd /glade/derecho/scratch/$USER/archive/i2000_fates.basics
ls
Advanced: Comparing the namelist settings#
When you create a case, CLM uses the compset to build the namelist for each component. The namelist, lnd_in, tells CLM which input files to read and which options to turn on. A copy of the final namelist is saved in each case’s CaseDocs/ directory.
Because the compset determines these settings, comparing lnd_in between your two cases shows how the configurations differ. The diff command prints only the lines that differ between two files. Lines starting with < come from the first file and lines starting with > from the second.
Look for differences in:
Input files, such as the surface dataset (
fsurdat), initial conditions (finidat), and parameter file (paramfile)Model options, such as
use_croporuse_fates
For each difference, ask: why would this compset need this setting?
diff ~/cases/i1850_sp.basics/CaseDocs/lnd_in ~/cases/i2000_fates.basics/CaseDocs/lnd_in
Test your understanding#
Where would you look to find out what other compsets are available?
What to the Rs and Gs mean in the FATES compset name?
What atmospheric meteorological forcing data is being used? Are there other options?