These variables MAY BE CHANGED ANYTIME during a run. Additional machine speific variables that can be changed during a run are contained in the env_mach_specific file Note1: users SHOULD NOT modify BUILD_COMPETE in env_build.xml this is done automatically by the scripts.

char cesm coupling mode logical TRUE,FALSE determine if per ice thickness category fields are passed from ice to ocean - DO NOT EDIT (set by POP build-namelist) logical TRUE,FALSE add aoflux calculation to runseq char none,CO2A,CO2B,CO2C Activates additional CO2-related fields to be exchanged between components. Possible values are: CO2A: sets the driver namelist variable flds_co2a = .true.; this adds prognostic CO2 and diagnostic CO2 at the lowest model level to be sent from the atmosphere to the land and ocean. CO2B: sets the driver namelist variable flds_co2b = .true.; this adds prognostic CO2 and diagnostic CO2 at the lowest model level to be sent from the atmosphere just to the land, and the surface upward flux of CO2 to be sent from the land back to the atmosphere CO2C: sets the driver namelist variable flds_co2c = .true.; this adds prognostic CO2 and diagnostic CO2 at the lowest model level to be sent from the atmosphere to the land and ocean, and the surface upward flux of CO2 to be sent from the land and the open ocean back to the atmosphere. The namelist variables flds_co2a, flds_co2b and flds_co2c are in the namelist group cpl_flds_inparm. logical TRUE,FALSE Activates DMS fluxes to be sent from ocn to atm. Currently this is only available with BLOM ocean component. logical TRUE,FALSE Activates Bromoform fluxes to be sent from ocn to atm. Currently this is only available with BLOM ocean component. logical TRUE,FALSE Activates N2O fluxes to be sent from ocn to atm. Currently this is only available with BLOM ocean component. logical TRUE,FALSE Activates NH3 fluxes to be sent from ocn to atm. Currently this is only available with BLOM ocean component. char hour,day,year,decade Base period associated with NCPL coupling frequency. This xml variable is only used to set the driver namelist variables, atm_cpl_dt, lnd_cpl_dt, ocn_cpl_dt, ice_cpl_dt, glc_cpl_dt, rof_cpl_dt, wav_cpl_dt, and esp_dt. integer Number of atm coupling intervals per NCPL_BASE_PERIOD. This is used to set the driver namelist atm_cpl_dt, equal to basedt/ATM_NCPL, where basedt is equal to NCPL_BASE_PERIOD in seconds. integer Number of land coupling intervals per NCPL_BASE_PERIOD. This is used to set the driver namelist atm_cpl_dt, equal to basedt/LND_NCPL, where basedt is equal to NCPL_BASE_PERIOD in seconds. integer Number of ice coupling intervals per NCPL_BASE_PERIOD. This is used to set the driver namelist ice_cpl_dt, equal to basedt/ICE_NCPL where basedt is equal to NCPL_BASE_PERIOD in seconds. integer Number of ocn coupling intervals per NCPL_BASE_PERIOD. Thisn is used to set the driver namelist ocn_cpl_dt, equal to basedt/OCN_NCPL where basedt is equal to NCPL_BASE_PERIOD in seconds. integer Number of glc coupling intervals per NCPL_BASE_PERIOD. char glc_coupling_period,yearly Period at which coupler averages fields sent to GLC. This supports doing the averaging to GLC less frequently than GLC is called (i.e., separating the averaging frequency from the calling frequency). This is useful because there are benefits to only averaging the GLC inputs as frequently as they are really needed (yearly for CISM), but GLC needs to still be called more frequently than that in order to support mid-year restarts. Setting GLC_AVG_PERIOD to 'glc_coupling_period' means that the averaging is done exactly when the GLC is called (governed by GLC_NCPL). IMPORTANT: In order to restart mid-year when running with CISM, you MUST specify GLC_AVG_PERIOD = 'yearly'. If using GLC_AVG_PERIOD = 'glc_coupling_period' with CISM, you can only restart on year boundaries. integer Number of rof coupling intervals per NCPL_BASE_PERIOD. This is used to set the driver namelist rof_cpl_dt, equal to basedt/ROF_NCPL where basedt is equal to NCPL_BASE_PERIOD in seconds. integer Number of wav coupling intervals per NCPL_BASE_PERIOD. This is used to set the driver namelist wav_cpl_dt, equal to basedt/WAV_NCPL where basedt is equal to NCPL_BASE_PERIOD in seconds. char TIGHT,OPTION1,OPTION2 OPTION1 (like RASM_OPTION1 in CPL7) runs prep_ocn_avg, BEFORE the aoflux and ocnalb calculations, thereby reducing most of the lags and field inconsistency but still allowing the ocean to run concurrently with the ice and atmosphere. OPTION2 (like CESM1_MOD in CPL7) runs prep_ocn_avg, AFTER the aoflux and ocnalb calculations, thereby permitting maximum concurrency TIGHT (like CESM1_MOD_TIGHT), is a tight coupling run sequence char Extra copies of the component log files will be saved here. char case description char The directory where the executable will be run. By default this is set to EXEROOT/../run. RUNDIR allows you to keep the run directory separate from the build directory char startup,hybrid,branch Determines the model run initialization type. This setting is only important for the initial run of a production run when the CONTINUE_RUN variable is set to FALSE. After the initial run, the CONTINUE_RUN variable is set to TRUE, and the model restarts exactly using input files in a case, date, and bit-for-bit continuous fashion. Default: startup. -- In a startup run (the default), all components are initialized using baseline states. These baseline states are set independently by each component and can include the use of restart files, initial files, external observed data files, or internal initialization (i.e., a cold start). In a startup run, the coupler sends the start date to the components at initialization. In addition, the coupler does not need an input data file. In a startup initialization, the ocean model does not start until the second ocean coupling (normally the second day). -- In a branch run, all components are initialized using a consistent set of restart files from a previous run (determined by the RUN_REFCASE and RUN_REFDATE variables in env_run.xml). The case name is generally changed for a branch run, although it does not have to be. In a branch run, setting RUN_STARTDATE is ignored because the model components obtain the start date from their restart datasets. Therefore, the start date cannot be changed for a branch run. This is the same mechanism that is used for performing a restart run (where CONTINUE_RUN is set to TRUE in the env_run.xml) Branch runs are typically used when sensitivity or parameter studies are required, or when settings for history file output streams need to be modified while still maintaining bit-for-bit reproducibility. Under this scenario, the new case is able to produce an exact bit-for-bit restart in the same manner as a continuation run IF no source code or component namelist inputs are modified. All models use restart files to perform this type of run. RUN_REFCASE and RUN_REFDATE are required for branch runs. To set up a branch run, locate the restart tar file or restart directory for RUN_REFCASE and RUN_REFDATE from a previous run, then place those files in the RUNDIR directory. --- In a hybrid run the model is initialized as a startup, BUT uses initialization datasets FROM A PREVIOUS case. This is somewhat analogous to a branch run with relaxed restart constraints. A hybrid run allows users to bring together combinations of initial/restart files from a previous case (specified by RUN_REFCASE) at a given model output date (specified by RUN_REFDATE). Unlike a branch run, the starting date of a hybrid run (specified by RUN_STARTDATE) can be modified relative to the reference case. In a hybrid run, the model does not continue in a bit-for-bit fashion with respect to the reference case. The resulting climate, however, should be continuous provided that no model source code or namelists are changed in the hybrid run. In a hybrid initialization, the ocean model does not start until the second ocean coupling (normally the second day), and the coupler does a cold start without a restart file. char Reference directory containing RUN_REFCASE data - used for hybrid or branch runs char Reference case for hybrid or branch runs char Reference date for hybrid or branch runs (yyyy-mm-dd) char Reference time of day (seconds) for hybrid or branch runs (sssss) logical TRUE,FALSE Flag for automatically prestaging the refcase restart dataset. If TRUE, then the refcase data is prestaged into the executable directory char Run start date (yyyy-mm-dd). Only used for startup or hybrid runs. integer Run start time-of-day, units are seconds with values from 0 to 86400. char none,never,nsteps,nseconds,nminutes,nhours,ndays,nmonths,nyears,date,end Sets the run length along with STOP_N and STOP_DATE integer Provides a numerical count for $STOP_OPTION. integer Alternative date yyyymmdd date option, sets the run length with STOP_OPTION and STOP_N negative value implies off char none,never,nsteps,nseconds,nminutes,nhours,ndays,nmonths,nyears,date,end sets frequency of model restart writes (same options as STOP_OPTION) integer sets model restart writes with REST_OPTION and REST_DATE char Alternative date in yyyymmdd format sets model restart write date with REST_OPTION and REST_N char Name of the restart pointer file, this can be used to restart from an intermediate restart by appending the restart date and time in format YYYY-MM-DD-SSSSS char none,never,nsteps,nseconds,nminutes,nhours,ndays,nmonths,nyears Sets the pause frequency along with PAUSE_N integer Provides a numerical count for $PAUSE_OPTION. logical TRUE,FALSE Pause the model at times specified by PAUSE_OPTION and PAUSE_N. Components 'pause' by writing a restart file. FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE logical TRUE,FALSE ESP component runs after driver 'pause cycle' If any component 'pauses' (see PAUSE_OPTION, PAUSE_N and PAUSE_ACTIVE_XXX XML variables), the ESP component (if present) will be run to process the component 'pause' (restart) files and set any required 'resume' signals. If true, esp_cpl_dt and esp_cpl_offset settings are ignored. default: false logical TRUE,FALSE A setting of TRUE implies a continuation run When you first begin a branch, hybrid or startup run, CONTINUE_RUN must be set to FALSE. When you successfully run and get a restart file, you will need to change CONTINUE_RUN to TRUE for the remainder of your run. This variable determines if the run is a restart run. Set to FALSE when initializing a startup, branch or hybrid case. Set to TRUE when continuing a run. logical TRUE,FALSE A setting of TRUE implies a continuation run for mediator only integer If RESUBMIT is greater than 0, then case will automatically resubmit Enables the model to automatically resubmit a new run. To get multiple runs, set RESUBMIT greater than 0, then RESUBMIT will be decremented and the case will be resubmitted. The case will stop automatically resubmitting when the RESUBMIT value reaches 0. Long runs can easily outstrip supercomputer queue time limits. For this reason, a case is usually run as a series of jobs, each restarting where the previous finished. logical This flag controls whether the RESUBMIT flag causes CONTINUE_RUN to toggle from FALSE to TRUE. The default is TRUE. This flag might be used in conjunction with COMP_RUN_BARRIERS for timing tests. logical TRUE,FALSE Logical to determine whether run has been submitted with the submit script or not char List of job ids for most recent case.submit char regular,premium,economy job priority for systems supporting this option logical TRUE,FALSE Logical to turn on short term archiving. If TRUE, short term archiving will be turned on. logical TRUE,FALSE Logical to run post-processing analysis tools. If TRUE, post-processing scripts will be run integer system workload snapshot frequency (in seconds, if greater than 0; disabled otherwise) logical TRUE,FALSE Logical to archive all interim restart files, not just those at eor If TRUE, perform short term archiving on all interim restart files, not just those at the end of the run. By default, this value is FALSE. The restart files are saved under the specific component directory ($DOUT_S_ROOT/$CASE/$COMPONENT/rest rather than the top-level $DOUT_S_ROOT/$CASE/rest directory). Interim restart files are created using the REST_N and REST_OPTION variables. This is for expert users ONLY and requires expert knowledge. We will not document this further in this guide. char GNU make command integer Number of processors for gmake logical TRUE,FALSE logical to diagnose model timing at the end of the run logical TRUE,FALSE Enables the papi hardware counters in gptl The papi library must be included in the build step for this to work. char off,low,high,max Determines the verbosity level in ESMF log files "off": no verbosity "low": some verbosity "high": more verbosity "max": all lower 16 bits By default, the verbosity level is set to "off" char Determines the profiling level in ESMF log files by default, it is set to 0 (only run method execution timings) logical TRUE,FALSE Turns on component barriers for component timing. This variable is for testing and debugging only and should never be set for a production run. integer 0,1,2,3,4,5,6,7,8,9 level of debug output, 0=minimum, 1=normal, 2=more, 3=too much logical TRUE,FALSE turns on coupler bit-for-bit reproducibility with varying pe counts logical TRUE,FALSE logical to save timing files in rundir integer Determines number of times profiler is called over the model run period. This sets values for tprof_option and tprof_n that determine the timing output file frequency integer integer indicating maximum detail level to profile. This xml variable is used to set the namelist variable timing_detail_limit. This namelist variable is used by perf_mod (in $CIMEROOT/src/share/timing/perf_mod.F90) to turn timers off and on depending on calls to the routine t_adj_detailf. If in the code a statement appears like t_adj_detailf(+1), then the current timer detail level is incremented by 1 and compared to the time_detail_limit obtained from the namelist. If the limit is exceeded then the timer is turned off. integer Maximum code stack depth of enabled timers. logical TRUE,FALSE Turn on the passing of water isotope fields through the coupler real Latitude of grid location, in single column mode interpolate datasets to this location in single point mode assume all datasets are at this location real Longitude of grid location, in single column mode interpolate datasets to this location in single point mode assume all datasets are at this location char used only if if PTS_LAT and PTS_LON are greater than or equal to 0. If this is the case then if PTS_DOMAINFILE is not equal to UNSET a nearest neighbor search of PTS_DOMAINFILE using PTS_LAT and PTS_LON will be done and the component mesh will have this nearest neighbor value. char lnd domain file char path of lnd domain file char atm mesh file (full pathname) char lnd mesh file (full pathname) char rof mesh file (full pathname) char wav mesh file (full pathname) char ice mesh file (full pahtname) char ocn mesh file (full pathname) char glc mesh file (full pathname) char mask mesh file (full pathname) char lnd2rof flux mapping file char rof2lnd flux mapping file char rof2ocn runoff mapping file char rof2ocn runoff mapping file char ocn2wav state mapping file char wav2ocn state mapping file char Error tolerance for differences in fractions in domain checking real Error tolerance for differences in atm/land areas in domain checking real Error tolerance for differences in atm/land masks in domain checking real Error tolerance for differences in atm/land lat/lon in domain checking real Error tolerance for differences in ocean/ice lon/lat in domain checking real Error tolerance for differences in ocean/ice lon/lat in domain checking real Error tolerance for differences in ocean/ice lon/lat in domain checking char A regular expression to match machine node names to ACME machine. char A regular expression to search for an indication that a run failure was caused by a node failure and should therefore be re-attempted. char Proxy (if any) setting for http_proxy to allow web access on this machine. logical Indicates to case.submit that this is a test case. char The root directory of all CIME and component input data for the selected machine. This is usually a shared disk area. Default values for the target machine are in the $CIMEROOT/machines/config_machines.xml char CLM-specific root directory for CLM type input forcing data This directory will only be used for I (CLM/DATM) compsets and only for datm forcing data that is NOT checked into the svn repository (datasets other than the Qian or single-point forcing). This is usually a shared disk area. Default values for the target machine are in the $CIMEROOT/machines/config_machines.xml char On some systems the filesystem of DIN_LOC_ROOT is not available on compute nodes and data must be staged to a temporary location. If this variable is defined it will be used as the root directory of an inputdata staging area. Default values for the target machine are in the $CIMEROOT/machines/config_machines.xml char Root directory for short term archiving. This directory must be visible to compute nodes. char override the mpi run command, do not include model executable char p2p,coll,default pio rearranger communication type char 2denable,io2comp,comp2io,disable,default pio rearranger communication flow control direction integer pio rearranger communication max pending requests (io2comp) : -2 implies that CIME internally calculates the value ( = 64), -1 implies no bound on max pending requests 0 implies that MPI_ALLTOALL will be used logical TRUE,FALSE pio rearranger communiation options (comp2io) : TRUE implies enable handshake logical TRUE,FALSE pio rearranger communiation options (comp2io) : TRUE implies enable isend integer pio rearranger communication max pending requests (io2comp) : -1 implies no bound on max pending requests logical TRUE,FALSE pio rearranger communiation options (io2comp) : TRUE implies enable handshake logical TRUE,FALSE pio rearranger communiation options (io2comp) : TRUE implies enable isend integer pio debug level integer pio blocksize for box decompositions integer pio buffer size limit for pnetcdf output logical TRUE,FALSE TRUE implies perform asynchronous i/o FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE char pnetcdf,netcdf,netcdf4p,netcdf4c,nothing pio io type pnetcdf pnetcdf pnetcdf pnetcdf pnetcdf pnetcdf pnetcdf pnetcdf pnetcdf char classic,64bit_offset,64bit_data pio netcdf format (ignored for netcdf4p and netcdf4c) https://www.unidata.ucar.edu/software/netcdf/docs/data_type.html 64bit_data 64bit_data 64bit_data 64bit_data 64bit_data 64bit_data 64bit_data 64bit_data 64bit_data integer stride in compute comm of io tasks for each component, if this value is -99 it will be computed based on PIO_NUMTASKS and number of compute tasks $MAX_MPITASKS_PER_NODE $MAX_MPITASKS_PER_NODE $MAX_MPITASKS_PER_NODE $MAX_MPITASKS_PER_NODE $MAX_MPITASKS_PER_NODE $MAX_MPITASKS_PER_NODE $MAX_MPITASKS_PER_NODE $MAX_MPITASKS_PER_NODE $MAX_MPITASKS_PER_NODE integer 1,2 pio rearranger choice box=1, subset=2 2 2 2 2 2 2 2 2 2 integer pio root processor relative to component root 1 1 1 1 1 1 1 1 1 integer pio number of io tasks, if this value is -99 it will be computed based on PIO_STRIDE and number of tasks -99 -99 -99 -99 -99 -99 -99 -99 -99 char External script to be run before model completion char External script to be run after model completion logical TRUE,FALSE Run the external tool pointed to by DATA_ASSIMILATION_SCRIPT after the model run completes FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE integer Number of model run - data assimilation steps to complete char External script to be run after model completion logical TRUE,FALSE whether the case uses an external workflow driver logical TRUE,FALSE if true, all data models are expected to get input sent back from the mediator logical TRUE,FALSE if true, create ESMF PET log files even if there is no error encountered logical TRUE,FALSE Only used for compsets with DATM and [POP or MOM] (currently C, G and J): If true, compute albedos to work with daily avg SW down If false (default), albedos are computed with the assumption that downward solar radiation from the atm component has a diurnal cycle and zenith-angle dependence. This is normally the case when using an active atm component If true, albedos are computed with the assumption that downward solar radiation from the atm component is a daily average quantity and does not have a zenith-angle dependence. This is often the case when using a data atm component. Only used for compsets with DATM and POP (currently C, G and J). NOTE: This should really depend on the datm forcing and not the compset per se. So, for example, whether it is set in a J compset should depend on what datm forcing is used. char off,ocn Only used for compsets with DATM and POP (currently C, G and J): If ocn, ocn provides EP balance factor for precipitation. Provides EP balance factor for precip for POP. A factor computed by POP is applied to precipitation so that precipitation balances evaporation and ocn global salinity does not drift. This is intended for use when coupling POP to a DATM. Only used for C, G and J compsets. Default is off logical TRUE,FALSE If CTSM will set the dust settings in drv_flds_in (TRUE), or if ATM (i.e. CAM) will - DO NOT EDIT (set by compset name) char none,never,nsteps,nseconds,nminutes,nhours,ndays,nmonths,nyears,date,end Sets driver snapshot history file frequency (like REST_OPTION) integer Sets driver snapshot history file frequency (like REST_N) integer yyyymmdd format, sets coupler snapshot history date (like REST_DATE) logical TRUE,FALSE logical that turns on diagnostic budgets for driver real Mechanism for setting the CO2 value in ppmv for CLM if CLM_CO2_TYPE is constant or for POP if OCN_CO2_TYPE is constant. integer 1,3,5,10,36 Number of glacier elevation classes used in CLM. Used by both CLM and the coupler (even if CISM is not running, and only SGLC is used). logical TRUE,FALSE Whether the glacier component feeds back to the rest of the system This affects: (1) Whether CLM updates its areas based on glacier areas sent from GLC (2) Whether GLC sends fluxes (e.g., calving fluxes) to the coupler Note that this is set to TRUE by default for TG compsets - even though there are no feedbacks for TG compsets, this enables extra coupler diagnostics for these compsets. char minus1p8,linear_salt,mushy Freezing point calculation for salt water. char CAM namelist use_case. Provides the use_case option for the CAM build-namelist utility (which is called from $CASEROOT/Buildconf/cam.buildnml). The CAM build-namelist leverages groups of namelist options (use cases) that are often paired with the CAM configure options. These use cases are xml files located in $CIMEROOT/../components/cam/bld/namelist_files/use_cases. In general, this variable should not be modified for supported component sets (compsets). Recommendation: If you want to modify this value for your experiment, use your own user-defined component sets. char CAM specific namelist settings for -namelist option Provides options to the -namelist argument for the CAM build-namelist utility. This should be reserved for component set specification. Users should modify CAM namelists only via the $CASEROOT/user_nl_cam file. char Tuning parameters and initial conditions should be optimized for what CLM model version and what meteorlogical forcing combination? Options for all combinations of CLM physics and atm forcing are given. The buildnml and namelist_defaults will narrow it down to the ones that have been tuned. The buildnml will also warn you if a tuning combination is based on another set. Atm forcing options: CRUJRA2024 CRUv7 GSWP3 CAM4.0 CAM5.0 CAM6.0 CAM7.0 QIAN (not tuned) 1PT (not tuned) NLDAS2 (not tuned) ERA5 (not tuned) Other atm forcing options are invalid to run CLM and will result in an error. clm5_0_cam6.0,clm5_0_cam7.0,clm5_0_cam5.0,clm5_0_cam4.0,clm5_0_GSWP3v1,clm5_0_CRUJRA2024,clm5_0_CRUv7,clm5_0_QIAN,clm5_0_1PT,clm5_0_NLDAS2,clm5_0_ERA5,clm4_5_CRUv7,clm4_5_GSWP3v1,clm4_5_QIAN,clm4_5_cam6.0,clm4_5_cam7.0,clm4_5_cam5.0,clm4_5_cam4.0,clm4_5_1PT,clm4_5_NLDAS2,clm4_5_ERA5,clm6_0_CRUv7,clm6_0_GSWP3v1,clm6_0_CRUJRA2024,clm6_0_cam6.0,clm6_0_cam7.0,clm6_0_cam5.0,clm6_0_cam4.0,clm6_0_QIAN,clm6_0_1PT,clm6_0_NLDAS2,clm6_0_ERA5 char clm4_5,clm5_0,clm6_0 Overall physics version to use. This sets the default values for many different namelist options. This is typically set by the compset. char clm,nwp Sets CLM default namelist options related to model configuration. clm: Configuration used for climate applications (CLM) nwp: Configuration used for numerical weather prediction applications char standard,fast Sets CLM default namelist options related to model structure. standard: Standard model structure, allowing for more subgrid heterogeneity, deeper soil, etc., at the cost of slower speeds. fast: Simplified model structure, achieving faster speeds at the cost of less subgrid heterogeneity, shallower soil, etc. char CLM namelist use_case. Determines the use-case that will be sent to the CLM build-namelist utility. This is normally set by the component set. This is an advanced flag and should only be used by expert users. char CLM build-namelist options char constant,diagnostic,prognostic Determines how CLM will determine where CO2 is set. If value is constant, it will be set to CCSM_CO2_PPMV, if value is either diagnostic or prognostic, the atmosphere model MUST send it to CLM. CLM_CO2_TYPE is normally set by the specific compset, since it HAS to be coordinated with settings for the atmospheric model. Do not modify this variable. If you want to modify for your experiment, use your own user-defined component set This is an advanced flag and should only be used by expert users. char CLM-specific namelist settings for -namelist option in the CLM build-namelist. CLM_NAMELIST_OPTS is normally set as a compset variable and in general should not be modified for supported compsets. It is recommended that if you want to modify this value for your experiment, you should use your own user-defined component sets via using create_newcase with a compset_file argument. This is an advanced flag and should only be used by expert users. char on,sasu,off Turn on any settings for accellerating the model spinup. SASU is to run the Semi-Analytic Spin-Up with the CN soil matrix method. char Resolution name for user-created resolutions. This is especially used for single point and regional resolutions created via subset_data from the global datasets. This should be set when you use CLM_USRDAT as the grid to create_newcase. The default value is UNSET. For NEON cases, this can be set to either NEON or NEON.PRISM, the latter of which would use PRISM precipitation instead of the default NEON precipitation. NEON cases then also use the variable NEONSITE to specify the exact site. PLUMBER cases use the variable PLUMBER2SITE to specify the exact site. char Directory name for user-created surface, landuse, and datm datasets. This is used as an argument in user_mods namelists (e.g. user_nl_clm, user_nl_datm_streams) generated with the subset_data script. Users should modify this variable (in shell_commands or elsewhere) to set the location of user-created data. The default value is UNSET. char on,off Flag to the CLM build-namelist command to force CLM to do a cold start (finidat will be set to blanks). A value of on forces the model to spin up from a cold-start (arbitrary initial conditions). Setting this value in the xml file will take precedence over any settings for finidat in the $CASEROOT/user_nl_clm file. char ABBY,BLAN,CPER,DEJU,GRSM,HEAL,KONA,LENO,NIWO,ONAQ,PUUM,SERC,SRER,TALL,TREE,WOOD, BARR,BONA,DCFS,DELA,GUAN,JERC,KONZ,MLBS,NOGP,ORNL,RMNP,SJER,STEI,TEAK,UKFS,WREF, BART,CLBJ,DSNY,HARV,JORN,LAJA,MOAB,OAES,OSBS,SCBI,SOAP,STER,TOOL,UNDE,YELL, NEON_PRECIP.ABBY,NEON_PRECIP.BLAN,NEON_PRECIP.CPER,NEON_PRECIP.DEJU,NEON_PRECIP.GRSM, NEON_PRECIP.HEAL,NEON_PRECIP.KONA,NEON_PRECIP.LENO,NEON_PRECIP.NIWO,NEON_PRECIP.ONAQ, NEON_PRECIP.PUUM,NEON_PRECIP.SERC,NEON_PRECIP.SRER,NEON_PRECIP.TALL,NEON_PRECIP.TREE, NEON_PRECIP.WOOD,NEON_PRECIP.BARR,NEON_PRECIP.BONA,NEON_PRECIP.DCFS,NEON_PRECIP.DELA, NEON_PRECIP.GUAN,NEON_PRECIP.JERC,NEON_PRECIP.KONZ,NEON_PRECIP.MLBS,NEON_PRECIP.NOGP, NEON_PRECIP.ORNL,NEON_PRECIP.RMNP,NEON_PRECIP.SJER,NEON_PRECIP.STEI,NEON_PRECIP.TEAK, NEON_PRECIP.UKFS,NEON_PRECIP.WREF,NEON_PRECIP.BART,NEON_PRECIP.CLBJ,NEON_PRECIP.DSNY, NEON_PRECIP.HARV,NEON_PRECIP.JORN,NEON_PRECIP.LAJA,NEON_PRECIP.MOAB,NEON_PRECIP.OAES, NEON_PRECIP.OSBS,NEON_PRECIP.SCBI,NEON_PRECIP.SOAP,NEON_PRECIP.STER,NEON_PRECIP.TOOL, NEON_PRECIP.UNDE,NEON_PRECIP.YELL, PRISM_PRECIP.ABBY,PRISM_PRECIP.BLAN,PRISM_PRECIP.CPER,PRISM_PRECIP.GRSM, PRISM_PRECIP.KONA,PRISM_PRECIP.LENO,PRISM_PRECIP.NIWO,PRISM_PRECIP.ONAQ, PRISM_PRECIP.SERC,PRISM_PRECIP.SRER,PRISM_PRECIP.TALL,PRISM_PRECIP.TREE, PRISM_PRECIP.WOOD,PRISM_PRECIP.DCFS,PRISM_PRECIP.DELA,PRISM_PRECIP.JERC, PRISM_PRECIP.KONZ,PRISM_PRECIP.MLBS,PRISM_PRECIP.NOGP,PRISM_PRECIP.ORNL, PRISM_PRECIP.RMNP,PRISM_PRECIP.SJER,PRISM_PRECIP.STEI,PRISM_PRECIP.TEAK, PRISM_PRECIP.UKFS,PRISM_PRECIP.WREF,PRISM_PRECIP.BART,PRISM_PRECIP.CLBJ, PRISM_PRECIP.DSNY,PRISM_PRECIP.HARV,PRISM_PRECIP.JORN,PRISM_PRECIP.MOAB, PRISM_PRECIP.OAES,PRISM_PRECIP.OSBS,PRISM_PRECIP.SCBI,PRISM_PRECIP.SOAP, PRISM_PRECIP.STER,PRISM_PRECIP.UNDE,PRISM_PRECIP.YELL, Name of site for NEON tower data char v1,v2,v3,latest Version id of Neon data char AR-SLu,AT-Neu,AU-ASM,AU-Cow,AU-Cpr,AU-Ctr,AU-Cum,AU-DaP,AU-DaS,AU-Dry,AU-Emr,AU-Gin,AU-GWW,AU-How,AU-Lit, AU-Otw,AU-Rig,AU-Rob,AU-Sam,AU-Stp,AU-TTE,AU-Tum,AU-Whr,AU-Wrr,AU-Ync,BE-Bra,BE-Lon,BE-Vie,BR-Sa3,BW-Ma1,CA-NS1, CA-NS2,CA-NS4,CA-NS5,CA-NS6,CA-NS7,CA-Qcu,CA-Qfo,CA-SF1,CA-SF2,CA-SF3,CH-Cha,CH-Dav,CH-Fru,CH-Oe1,CN-Cha,CN-Cng, CN-Dan,CN-Din,CN-Du2,CN-HaM,CN-Qia,CZ-wet,DE-Bay,DE-Geb,DE-Gri,DE-Hai,DE-Kli,DE-Meh,DE-Obe,DE-Seh,DE-SfN,DE-Tha, DE-Wet,DK-Fou,DK-Lva,DK-Ris,DK-Sor,DK-ZaH,ES-ES1,ES-ES2,ES-LgS,ES-LMa,ES-VDA,FI-Hyy,FI-Kaa,FI-Lom,FI-Sod,FR-Fon, FR-Gri,FR-Hes,FR-LBr,FR-Lq1,FR-Lq2,FR-Pue,GF-Guy,HU-Bug,ID-Pag,IE-Ca1,IE-Dri,IT-Amp,IT-BCi,IT-CA1,IT-CA2,IT-CA3, IT-Col,IT-Cpz,IT-Isp,IT-Lav,IT-LMa,IT-Mal,IT-MBo,IT-Noe,IT-Non,IT-PT1,IT-Ren,IT-Ro1,IT-Ro2,IT-SR2,IT-SRo,JP-SMF, NL-Ca1,NL-Hor,NL-Loo,PL-wet,PT-Esp,PT-Mi1,PT-Mi2,RU-Che,RU-Fyo,RU-Zot,SD-Dem,SE-Deg,UK-Gri,UK-Ham,UK-PL3,US-AR1, US-AR2,US-ARM,US-Aud,US-Bar,US-Bkg,US-Blo,US-Bo1,US-Cop,US-FPe,US-GLE,US-Goo,US-Ha1,US-Ho1,US-KS2,US-Los,US-Me2, US-Me4,US-Me6,US-MMS,US-MOz,US-Myb,US-Ne1,US-Ne2,US-Ne3,US-NR1,US-PFa,US-Prr,US-SP1,US-SP2,US-SP3,US-SRG,US-SRM, US-Syv,US-Ton,US-Tw4,US-Twt,US-UMB,US-Var,US-WCr,US-Whs,US-Wkg,ZA-Kru,ZM-Mon, Name of site for PLUMBER tower data char prognostic,prescribed,thermo_only Option to the CICE configure utility for the -mode argument (default is prognostic) char CICE configure options, see CICE configure utility for details. It is recommended that if you want to modify this value for your experiment, you should use your own user-defined component sets via using create_newcase with a compset_file argument. This is an advanced flag and should only be used by expert users. char CICE specific namelist settings for -namelist option char prescribed,sst_aquap1,sst_aquap2,sst_aquap3,sst_aquap4,sst_aquap5,sst_aquap6,sst_aquap7,sst_aquap8,sst_aquap9,sst_aquap10,sst_aquapfile,som,som_aquap,sst_aquap_constant,interannual,cplhist,multilev,multilev_dom,multilev_cplhist DOCN mode. The data ocean component (DOCN) always returns SSTs to the driver. The atmosphere/ocean fluxes are computed in the coupler. Therefore, the data ocean model does not compute fluxes like the data ice model. DOCN has two distinct modes of operation. It can run as a pure data model, reading in ocean SSTs (normally climatological) from input datasets, performing time/spatial interpolations, and passing these to the coupler. Alternatively, DOCN can compute updated SSTs by running as a slab ocean model where bottom ocean heat flux convergence and boundary layer depths are read in and used with the atmosphere/ocean and ice/ocean fluxes obtained from the driver. --- A setting of prescribed assumes the only field in the input stream is SST. It also assumes the SST is in Celsius and must be converted to Kelvin. All other fields are set to zero except for ocean salinity, which is set to a constant reference salinity value. Normally the ice fraction data is found in the same data files that provide SST data to the data ocean model. They are normally found in the same file because the SST and ice fraction data are derived from the same observational data sets and are consistent with each other. --- Settings of som (slab ocean model) or som_aquap (aquaplanet slab ocean) are prognostic modes which compute a prognostic sea surface temperature and a freeze/melt potential (surface Q-flux) used by the sea ice model. This calculation requires an external SOM forcing data file that includes ocean mixed layer depths and bottom-of-the-slab Q-fluxes. Scientifically appropriate bottom-of-the-slab Q-fluxes are normally ocean resolution dependent and are derived from the ocean model output of a fully coupled CCSM run. Note that while this mode runs out of the box, the default SOM forcing file is not scientifically appropriate and is provided for testing and development purposes only. Users must create scientifically appropriate data for their particular application. A tool is available to derive valid SOM forcing. --- A setting of sst_aquapN (where "N" is an integer index value) is a type of prescribed SST mode used specifically for an aquaplanet setup in which global SSTs correspond to an analytic form set by the index value. Currently, indices for 10 SST profiles are supported [e.g., index 3 corresponds to the "QOBS" profile of Neale and Hoskins (2001, Atmos. Sci. Lett.)]. With source code modifications, it is possible for users to create their own analytic SST distributions and match them to indices 11 or greater. real Sets globally constant SST value char Sets SOM aquaplanet file char Prescribed SST and ice coverage stream name. Sets SST and ice coverage stream name. This is only used when DOCN_MODE=prescribed. char Prescribed SST and ice coverage data file name. Sets SST and ice coverage data file name. This is only used when DOCN_MODE=prescribed. char directory for coupler history data mode (only used for CPLHIST mode) char case name for coupler history data mode (only used for CPLHIST mode) integer Simulation year corresponding to DOCN_CPLHIST_YR_START. A common usage is to set this to RUN_STARTDATE. With this setting, the forcing in the first year of the run will be the forcing of year DOCN_CPLHIST_YR_START. Another use case is to align the calendar of transient forcing with the model calendar. For example, setting DOCN_CPLHIST_YR_ALIGN=DOCN_CPLHIST_YR_START will lead to the forcing calendar being the same as the model calendar. The forcing for a given model year would be the forcing of the same year. This would be appropriate in transient runs where the model calendar is setup to span the same year range as the forcing data. integer starting year to loop data over integer ending year to loop data over logical TRUE,FALSE If set to true, than docn restarts will not be read on a continuation run. char none or colon deliminted string of import fields that DOCN will advertise char Prescribed SST and ice coverage mesh file name. Sets SST and ice coverage grid file name for prescribed runs. This is only used when DOCN_MODE=prescribed. integer The model year that corresponds to SSTICE_YEAR_START on the data file. Prescribed SST and ice coverage data will be aligned so that the first year of data corresponds to SSTICE_YEAR_ALIGN in the model. For instance, if the first year of prescribed data is the same as the first year of the model run, this should be set to the year given in RUN_STARTDATE. If SSTICE_YEAR_ALIGN is later than the model's starting year, or if the model is run after the prescribed data ends (as determined by SSTICE_YEAR_END), the default behavior is to assume that the data from SSTICE_YEAR_START to SSTICE_YEAR_END cyclically repeats. This behavior is controlled by the "taxmode" stream option; see the data model documentation for more details. This is only used when DOCN_MODE=prescribed. integer The first year of data to use from SSTICE_DATA_FILENAME. This is the first year of prescribed SST and ice coverage data to use. For example, if a data file has data for years 0-99, and SSTICE_YEAR_START is 10, years 0-9 in the file will not be used. This is only used when DOCN_MODE=prescribed. integer The last year of data to use from SSTICE_DATA_FILENAME. This is the last year of prescribed SST and ice coverage data to use. For example, if a data file has data for years 0-99, and value is 49, years 50-99 in the file will not be used. This is only used when DOCN_MODE=prescribed. logical TRUE,FALSE If warnings in namelist setttings from buildnml should be ignored or not char Simulation year to start from -- build-namelist options (currently not used) char noevolve NOEVOLVE mode is used in CESM as follows. In typical runs, CISM is not evolving; CLM computes the surface mass balance (SMB) and sends it to CISM, but CISM’s ice sheet geometry remains fixed over the course of the run. In these runs, CISM serves two roles in the system: logical Whether to include the Greenland Ice Sheet in this DGLC simulation This should generally be set at create_newcase time (via the compset). In principle it can be changed later, but great care is needed to change a number of other variables to be consistent (GLC_GRID, GLC_DOMAIN_MESH and possibly others). logical Whether to include the Antarctica Ice Sheet in this DGLC simulation This should generally be set at create_newcase time (via the compset). In principle it can be changed later, but great care is needed to change a number of other variables to be consistent (GLC_GRID, GLC_DOMAIN_MESH and possibly others). logical TRUE,FALSE If set to true, than dglc restarts will not be read on a continuation run.