<?xml version="1.0"?>
<file id="env_run.xml" version="2.0">
  <header>
    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.
    </header>
  <group id="run_desc">
    <entry id="CASESTR" value="UNSET">
      <type>char</type>
      <desc>case description</desc>
    </entry>
    <entry id="RUNDIR" value="$CIME_OUTPUT_ROOT/$CASE/run">
      <type>char</type>
      <desc>
      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
    </desc>
    </entry>
  </group>
  <group id="run_begin_stop_restart">
    <entry id="RUN_TYPE" value="branch">
      <type>char</type>
      <valid_values>startup,hybrid,branch</valid_values>
      <desc>
      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.
    </desc>
    </entry>
    <entry id="RUN_REFDIR" value="ccsm4_init">
      <type>char</type>
      <desc>
      Reference directory containing RUN_REFCASE data - used for hybrid or branch runs
    </desc>
    </entry>
    <entry id="RUN_REFCASE" value="N1850_f19_tn14_20190621">
      <type>char</type>
      <desc>
      Reference case for hybrid or branch runs
    </desc>
    </entry>
    <entry id="RUN_REFDATE" value="1701-01-01">
      <type>char</type>
      <desc>
      Reference date for hybrid or branch runs (yyyy-mm-dd)
    </desc>
    </entry>
    <entry id="RUN_REFTOD" value="00000">
      <type>char</type>
      <desc>
      Reference time of day (seconds) for hybrid or branch runs (sssss)
    </desc>
    </entry>
    <entry id="GET_REFCASE" value="FALSE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>
      Flag for automatically prestaging the refcase restart dataset.
      If TRUE, then the refcase data is prestaged into the executable directory
    </desc>
    </entry>
    <entry id="RUN_STARTDATE" value="0001-01-01">
      <type>char</type>
      <desc>
      Run start date (yyyy-mm-dd). Only used for startup or hybrid runs.
    </desc>
    </entry>
    <entry id="START_TOD" value="0">
      <type>integer</type>
      <desc>
      Run start time-of-day
    </desc>
    </entry>
    <entry id="STOP_OPTION" value="nyears">
      <type>char</type>
      <valid_values>none,never,nsteps,nstep,nseconds,nsecond,nminutes,nminute,nhours,nhour,ndays,nday,nmonths,nmonth,nyears,nyear,date,ifdays0,end</valid_values>
      <desc>
      Sets the run length along with STOP_N and STOP_DATE
    </desc>
    </entry>
    <entry id="STOP_N" value="50">
      <type>integer</type>
      <desc>
      Provides a numerical count for $STOP_OPTION.
    </desc>
    </entry>
    <entry id="STOP_DATE" value="-999">
      <type>integer</type>
      <desc>
      Alternative date yyyymmdd date option, sets the run length with STOP_OPTION and STOP_N
      negative value implies off
    </desc>
    </entry>
    <entry id="REST_OPTION" value="nyears">
      <type>char</type>
      <valid_values>none,never,nsteps,nstep,nseconds,nsecond,nminutes,nminute,nhours,nhour,ndays,nday,nmonths,nmonth,nyears,nyear,date,ifdays0,end</valid_values>
      <desc>
      sets frequency of model restart writes (same options as STOP_OPTION)
    </desc>
    </entry>
    <entry id="REST_N" value="10">
      <type>integer</type>
      <desc>
      sets model restart writes with REST_OPTION and REST_DATE
    </desc>
    </entry>
    <entry id="REST_DATE" value="$STOP_DATE">
      <type>char</type>
      <desc>
      Alternative date in yyyymmdd format
      sets model restart write date with REST_OPTION and REST_N
    </desc>
    </entry>
    <entry id="PAUSE_OPTION" value="never">
      <type>char</type>
      <valid_values>none,never,nsteps,nstep,nseconds,nsecond,nminutes,nminute,nhours,nhour,ndays,nday,nmonths,nmonth,nyears,nyear</valid_values>
      <desc>
      Sets the pause frequency along with PAUSE_N
    </desc>
    </entry>
    <entry id="PAUSE_N" value="0">
      <type>integer</type>
      <desc>
      Provides a numerical count for $PAUSE_OPTION.
    </desc>
    </entry>
    <entry id="PAUSE_ACTIVE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>
      Pause the model at times specified by PAUSE_OPTION and PAUSE_N.
      Components 'pause' by writing a restart file.
    </desc>
      <values>
        <value compclass="ATM">FALSE</value>
        <value compclass="CPL">FALSE</value>
        <value compclass="OCN">FALSE</value>
        <value compclass="WAV">FALSE</value>
        <value compclass="GLC">FALSE</value>
        <value compclass="ICE">FALSE</value>
        <value compclass="ROF">FALSE</value>
        <value compclass="LND">FALSE</value>
      </values>
    </entry>
    <entry id="BARRIER_N" value="1">
      <type>char</type>
      <desc>
      Sets periodic model barriers with BARRIER_OPTION and BARRIER_DATE for synchronization
    </desc>
    </entry>
    <entry id="BARRIER_DATE" value="-999">
      <type>char</type>
      <desc>
      Alternative date in yyyymmdd format
      sets periodic model barriers with BARRIER_OPTION and BARRIER_N for synchronization
    </desc>
    </entry>
    <entry id="ESP_RUN_ON_PAUSE" value="FALSE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>
      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
    </desc>
    </entry>
    <entry id="CONTINUE_RUN" value="FALSE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>
      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.
    </desc>
    </entry>
    <entry id="RESUBMIT" value="1">
      <type>integer</type>
      <desc>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.
    </desc>
    </entry>
    <entry id="RESUBMIT_SETS_CONTINUE_RUN" value="TRUE">
      <type>logical</type>
      <desc>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.
    </desc>
    </entry>
    <entry id="JOB_IDS" value="case.run:332948, case.st_archive:332949">
      <type>char</type>
      <desc>List of job ids for most recent case.submit</desc>
    </entry>
    <entry id="BARRIER_OPTION" value="never">
      <type>char</type>
      <valid_values>none,never,nsteps,nstep,nseconds,nsecond,nminutes,nminute,nhours,nhour,ndays,nday,nmonths,nmonth,nyears,nyear,date,ifdays0,end</valid_values>
      <desc>
      sets frequency of full model barrier (same options as STOP_OPTION) for synchronization with BARRIER_N and BARRIER_DATE
    </desc>
    </entry>
  </group>
  <group id="run_data_archive">
    <entry id="DOUT_S" value="TRUE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>Logical to turn on short term archiving.
    If TRUE, short term archiving will be turned on.</desc>
    </entry>
    <entry id="SYSLOG_N" value="900">
      <type>integer</type>
      <desc>system workload snapshot frequency (in seconds, if greater than 0; disabled otherwise)</desc>
    </entry>
    <entry id="DOUT_S_SAVE_INTERIM_RESTART_FILES" value="TRUE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>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 TRUE.
    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.</desc>
    </entry>
    <entry id="COMPRESS_ARCHIVE_FILES" value="TRUE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>Logical  compress/convert  archive files to netcdf-4</desc>
    </entry>
  </group>
  <group id="build_def">
    <entry id="GMAKE" value="gmake">
      <type>char</type>
      <valid_values/>
      <desc>GNU make command</desc>
    </entry>
    <entry id="GMAKE_J" value="8">
      <type>integer</type>
      <valid_values/>
      <desc>Number of processors for gmake</desc>
    </entry>
  </group>
  <group id="run_flags">
    <entry id="CHECK_TIMING" value="TRUE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>logical to diagnose model timing at the end of the run</desc>
    </entry>
    <entry id="PROFILE_PAPI_ENABLE" value="FALSE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>Enables the papi hardware counters in gptl
    The papi library must be included in the build step for
    this to work.</desc>
    </entry>
    <entry id="ESMF_LOGFILE_KIND" value="ESMF_LOGKIND_NONE">
      <type>char</type>
      <valid_values>ESMF_LOGKIND_SINGLE,ESMF_LOGKIND_MULTI,ESMF_LOGKIND_MULTI_ON_ERROR,ESMF_LOGKIND_NONE</valid_values>
      <desc>
      Determines what ESMF log files (if any) are generated when
          USE_ESMF_LIB is TRUE.
      ESMF_LOGKIND_SINGLE: Use a single log file, combining messages from
          all of the PETs. Not supported on some platforms.
      ESMF_LOGKIND_MULTI: Use multiple log files -- one per PET.
      ESMF_LOGKIND_NONE: Do not issue messages to a log file.
      By default, no ESMF log files are generated.
    </desc>
    </entry>
    <entry id="COMP_RUN_BARRIERS" value="FALSE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>Turns on component barriers for component timing.
	  This variable is for testing and debugging only and should never
	  be set for a production run.
    </desc>
    </entry>
    <entry id="CPL_DECOMP" value="0">
      <type>integer</type>
      <valid_values>0,1,2,3,4,5,6</valid_values>
      <desc>Coupler decomposition option.</desc>
    </entry>
    <entry id="INFO_DBUG" value="1">
      <type>integer</type>
      <valid_values>0,1,2,3</valid_values>
      <desc>level of debug output, 0=minimum, 1=normal, 2=more, 3=too much</desc>
    </entry>
    <entry id="DRV_THREADING" value="FALSE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>Turns on component varying thread control in the driver.
    Used to set the driver namelist variable "drv_threading".</desc>
    </entry>
    <entry id="SAVE_TIMING" value="FALSE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>logical to save timing files in rundir</desc>
    </entry>
    <entry id="TPROF_TOTAL" value="0">
      <type>integer</type>
      <desc>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
    </desc>
    </entry>
    <entry id="TIMER_DETAIL" value="2">
      <type>integer</type>
      <desc>
      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.




    </desc>
    </entry>
    <entry id="TIMER_LEVEL" value="4">
      <type>integer</type>
      <desc>Maximum code stack depth of enabled timers.</desc>
    </entry>
    <entry id="BFBFLAG" value="TRUE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>turns on coupler bit-for-bit reproducibility with varying pe counts</desc>
    </entry>
    <entry id="FLDS_WISO" value="FALSE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>Turn on the passing of water isotope fields through the coupler</desc>
    </entry>
  </group>
  <group id="run_domain">
    <entry id="PTS_MODE" value="FALSE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>Operate on only a single point of the global grid  - DO NOT EDIT (for experts only)</desc>
    </entry>
    <entry id="PTS_LAT" value="-999.99">
      <type>real</type>
      <desc>Latitude to find nearest points for points mode (only used if PTS_MODE is TRUE)</desc>
    </entry>
    <entry id="PTS_LON" value="-999.99">
      <type>real</type>
      <desc>Longitude to find nearest points for points mode (only used if PTS_MODE is TRUE)</desc>
    </entry>
    <entry id="ATM_DOMAIN_FILE" value="domain.lnd.fv1.9x2.5_tnx1v4.170609.nc">
      <type>char</type>
      <desc>atm domain file</desc>
    </entry>
    <entry id="ATM_DOMAIN_PATH" value="$DIN_LOC_ROOT/share/domains">
      <type>char</type>
      <desc>path of atm domain file</desc>
    </entry>
    <entry id="LND_DOMAIN_FILE" value="domain.lnd.fv1.9x2.5_tnx1v4.170609.nc">
      <type>char</type>
      <desc>lnd domain file</desc>
    </entry>
    <entry id="LND_DOMAIN_PATH" value="$DIN_LOC_ROOT/share/domains">
      <type>char</type>
      <desc>path of lnd domain file</desc>
    </entry>
    <entry id="ROF_DOMAIN_FILE" value="UNSET">
      <type>char</type>
      <desc>rof domain file</desc>
    </entry>
    <entry id="ROF_DOMAIN_PATH" value="$DIN_LOC_ROOT/share/domains">
      <type>char</type>
      <desc>path of rof domain file</desc>
    </entry>
    <entry id="WAV_DOMAIN_FILE" value="UNSET">
      <type>char</type>
      <desc>wav domain file</desc>
    </entry>
    <entry id="WAV_DOMAIN_PATH" value="$DIN_LOC_ROOT/share/domains">
      <type>char</type>
      <desc>path of wav domain file</desc>
    </entry>
    <entry id="ICE_DOMAIN_FILE" value="domain.ocn.tnx1v4.170606.nc">
      <type>char</type>
      <desc>ice domain file</desc>
    </entry>
    <entry id="ICE_DOMAIN_PATH" value="$DIN_LOC_ROOT/share/domains">
      <type>char</type>
      <desc>path of ice domain file</desc>
    </entry>
    <entry id="OCN_DOMAIN_FILE" value="domain.ocn.tnx1v4.170606.nc">
      <type>char</type>
      <desc>ocn domain file</desc>
    </entry>
    <entry id="OCN_DOMAIN_PATH" value="$DIN_LOC_ROOT/share/domains">
      <type>char</type>
      <desc>path of ocn domain file</desc>
    </entry>
    <entry id="GLC_DOMAIN_FILE" value="UNSET">
      <type>char</type>
      <desc>glc domain file</desc>
    </entry>
    <entry id="GLC_DOMAIN_PATH" value="$DIN_LOC_ROOT/share/domains">
      <type>char</type>
      <desc>path of glc domain file</desc>
    </entry>
    <entry id="ATM2OCN_FMAPNAME" value="cpl/cpl6/map_fv1.9x2.5_to_tnx1v4_aave_da_170609.nc">
      <type>char</type>
      <desc>atm2ocn flux mapping file</desc>
    </entry>
    <entry id="ATM2OCN_FMAPTYPE" value="X">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>atm2ocn flux mapping file decomp type</desc>
    </entry>
    <entry id="ATM2OCN_SMAPNAME" value="cpl/cpl6/map_fv1.9x2.5_to_tnx1v4_patch_170609.nc">
      <type>char</type>
      <desc>atm2ocn state mapping file</desc>
    </entry>
    <entry id="ATM2OCN_SMAPTYPE" value="X">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>atm2ocn state mapping file decomp type</desc>
    </entry>
    <entry id="ATM2OCN_VMAPNAME" value="cpl/cpl6/map_fv1.9x2.5_to_tnx1v4_patch_170609.nc">
      <type>char</type>
      <desc>atm2ocn vector mapping file</desc>
    </entry>
    <entry id="ATM2OCN_VMAPTYPE" value="X">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>atm2ocn vector mapping file decomp type</desc>
    </entry>
    <entry id="ATM2LND_FMAPNAME" value="idmap">
      <type>char</type>
      <desc>atm2lnd flux mapping file</desc>
    </entry>
    <entry id="ATM2LND_FMAPTYPE" value="X">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>atm2lnd flux mapping file decomp type</desc>
    </entry>
    <entry id="ATM2LND_SMAPNAME" value="idmap">
      <type>char</type>
      <desc>atm2lnd state mapping file</desc>
    </entry>
    <entry id="ATM2LND_SMAPTYPE" value="X">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>atm2lnd state mapping file decomp type</desc>
    </entry>
    <entry id="ATM2WAV_SMAPNAME" value="idmap">
      <type>char</type>
      <desc>atm2wav state mapping file</desc>
    </entry>
    <entry id="ATM2WAV_SMAPTYPE" value="Y">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>atm2wav state mapping file decomp type</desc>
    </entry>
    <entry id="OCN2ATM_FMAPNAME" value="cpl/cpl6/map_tnx1v4_to_fv1.9x2.5_aave_da_170609.nc">
      <type>char</type>
      <desc>ocn2atm flux mapping file</desc>
    </entry>
    <entry id="OCN2ATM_FMAPTYPE" value="Y">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>ocn2atm flux mapping file decomp type</desc>
    </entry>
    <entry id="OCN2ATM_SMAPNAME" value="cpl/cpl6/map_tnx1v4_to_fv1.9x2.5_aave_da_170609.nc">
      <type>char</type>
      <desc>ocn2atm state mapping file</desc>
    </entry>
    <entry id="OCN2ATM_SMAPTYPE" value="Y">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>ocn2atm state mapping file decomp type</desc>
    </entry>
    <entry id="LND2ATM_FMAPNAME" value="idmap">
      <type>char</type>
      <desc>lnd2atm flux mapping file</desc>
    </entry>
    <entry id="LND2ATM_FMAPTYPE" value="Y">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>lnd2atm flux mapping file decomp type</desc>
    </entry>
    <entry id="LND2ATM_SMAPNAME" value="idmap">
      <type>char</type>
      <desc>lnd2atm state mapping file</desc>
    </entry>
    <entry id="LND2ATM_SMAPTYPE" value="Y">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>lnd2atm state mapping file decomp type</desc>
    </entry>
    <entry id="LND2GLC_FMAPNAME" value="idmap">
      <type>char</type>
      <desc>lnd2glc flux mapping file</desc>
    </entry>
    <entry id="LND2GLC_FMAPTYPE" value="X">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>lnd2glc flux mapping file decomp type</desc>
    </entry>
    <entry id="LND2GLC_SMAPNAME" value="idmap">
      <type>char</type>
      <desc>lnd2glc state mapping file</desc>
    </entry>
    <entry id="LND2GLC_SMAPTYPE" value="X">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>lnd2glc state mapping file decomp type</desc>
    </entry>
    <entry id="LND2ROF_FMAPNAME" value="lnd/clm2/mappingdata/maps/1.9x2.5/map_1.9x2.5_nomask_to_0.5x0.5_nomask_aave_da_c120522.nc">
      <type>char</type>
      <desc>lnd2rof flux mapping file</desc>
    </entry>
    <entry id="LND2ROF_FMAPTYPE" value="X">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>lnd2rof flux mapping file decomp type</desc>
    </entry>
    <entry id="ROF2LND_FMAPNAME" value="lnd/clm2/mappingdata/maps/1.9x2.5/map_0.5x0.5_nomask_to_1.9x2.5_nomask_aave_da_c120709.nc">
      <type>char</type>
      <desc>rof2lnd flux mapping file</desc>
    </entry>
    <entry id="ROF2LND_FMAPTYPE" value="Y">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>rof2lnd flux mapping file decomp type</desc>
    </entry>
    <entry id="ROF2OCN_FMAPNAME" value="cpl/cpl6/map_r05_to_tnx1v4_e1000r300_170609.nc">
      <type>char</type>
      <desc>rof2ocn flux mapping file - the default value idmap_ignore, if set, will be ignored by buildnml and
    will generate a runtime error if in fact a file is required for the given compset</desc>
    </entry>
    <entry id="ROF2OCN_FMAPTYPE" value="Y">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>rof2ocn flux mapping file decomp type</desc>
    </entry>
    <entry id="ROF2OCN_LIQ_RMAPNAME" value="cpl/cpl6/map_r05_to_tnx1v4_e1000r300_170609.nc">
      <type>char</type>
      <desc>rof2ocn runoff mapping file</desc>
    </entry>
    <entry id="ROF2OCN_LIQ_RMAPTYPE" value="Y">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>rof2ocn runoff mapping file decomp type</desc>
    </entry>
    <entry id="ROF2OCN_ICE_RMAPNAME" value="cpl/cpl6/map_r05_to_tnx1v4_e1000r300_170609.nc">
      <type>char</type>
      <desc>rof2ocn runoff mapping file</desc>
    </entry>
    <entry id="ROF2OCN_ICE_RMAPTYPE" value="Y">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>rof2ocn runoff mapping file decomp type</desc>
    </entry>
    <entry id="GLC2LND_FMAPNAME" value="idmap">
      <type>char</type>
      <desc>glc2lnd flux mapping file</desc>
    </entry>
    <entry id="GLC2LND_FMAPTYPE" value="Y">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>glc2lnd flux mapping file decomp type</desc>
    </entry>
    <entry id="GLC2LND_SMAPNAME" value="idmap">
      <type>char</type>
      <desc>glc2lnd state mapping file</desc>
    </entry>
    <entry id="GLC2LND_SMAPTYPE" value="Y">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>glc2lnd state mapping file decomp type</desc>
    </entry>
    <entry id="GLC2ICE_RMAPNAME" value="idmap_ignore">
      <type>char</type>
      <desc>glc2ice runoff mapping file - the default value idmap_ignore, if set, will be ignored by buildnml and
    will generate a runtime error if in fact a file is required for the given compset</desc>
    </entry>
    <entry id="GLC2ICE_RMAPTYPE" value="Y">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>glc2ice runoff mapping file decomp type</desc>
    </entry>
    <entry id="GLC2OCN_LIQ_RMAPNAME" value="idmap_ignore">
      <type>char</type>
      <desc>glc2ocn runoff mapping file for liquid runoff - the default value idmap_ignore, if set, will be ignored by buildnml and
    will generate a runtime error if in fact a file is required for the given compset</desc>
    </entry>
    <entry id="GLC2OCN_LIQ_RMAPTYPE" value="Y">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>glc2ocn runoff mapping file decomp type for liquid runoff</desc>
    </entry>
    <entry id="GLC2OCN_ICE_RMAPNAME" value="idmap_ignore">
      <type>char</type>
      <desc>glc2ocn runoff mapping file for ice runoff - the default value idmap_ignore, if set, will be ignored by buildnml and
    will generate a runtime error if in fact a file is required for the given compset</desc>
    </entry>
    <entry id="GLC2OCN_ICE_RMAPTYPE" value="Y">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>glc2ocn runoff mapping file decomp type for ice runoff</desc>
    </entry>
    <entry id="OCN2WAV_SMAPNAME" value="idmap">
      <type>char</type>
      <desc>ocn2wav state mapping file</desc>
    </entry>
    <entry id="OCN2WAV_SMAPTYPE" value="Y">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>ocn2wav state mapping file decomp type</desc>
    </entry>
    <entry id="ICE2WAV_SMAPNAME" value="idmap">
      <type>char</type>
      <desc>ice2wav state mapping file</desc>
    </entry>
    <entry id="ICE2WAV_SMAPTYPE" value="Y">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>ice2wav state mapping file decomp type</desc>
    </entry>
    <entry id="WAV2OCN_SMAPNAME" value="idmap">
      <type>char</type>
      <desc>wav2ocn state mapping file</desc>
    </entry>
    <entry id="WAV2OCN_SMAPTYPE" value="X">
      <type>char</type>
      <valid_values>X,Y</valid_values>
      <desc>wav2ocn state mapping file decomp type</desc>
    </entry>
    <entry id="VECT_MAP" value="cart3d">
      <type>char</type>
      <valid_values>none,npfix,cart3d,cart3d_diag,cart3d_uvw,cart3d_uvw_diag</valid_values>
      <desc>vector mapping option</desc>
    </entry>
    <entry id="EPS_FRAC" value="1.0e-02">
      <type>char</type>
      <desc>Error tolerance for differences in fractions in domain checking</desc>
    </entry>
    <entry id="EPS_AAREA" value="9.0e-07">
      <type>real</type>
      <desc>Error tolerance for differences in atm/land areas in domain checking</desc>
    </entry>
    <entry id="EPS_AMASK" value="1.0e-13">
      <type>real</type>
      <desc>Error tolerance for differences in atm/land masks in domain checking</desc>
    </entry>
    <entry id="EPS_AGRID" value="1.0e-12">
      <type>real</type>
      <desc>Error tolerance for differences in atm/land lat/lon in domain checking</desc>
    </entry>
    <entry id="EPS_OAREA" value="1.0e-01">
      <type>real</type>
      <desc>Error tolerance for differences in ocean/ice lon/lat in domain checking</desc>
    </entry>
    <entry id="EPS_OMASK" value="1.0e-06">
      <type>real</type>
      <desc>Error tolerance for differences in ocean/ice lon/lat in domain checking</desc>
    </entry>
    <entry id="EPS_OGRID" value="1.0e-02">
      <type>real</type>
      <desc>Error tolerance for differences in ocean/ice lon/lat in domain checking</desc>
    </entry>
  </group>
  <group id="run_din">
    <entry id="NODENAME_REGEX" value="UNSET">
      <type>char</type>
      <desc>
      A regular expression to match machine node names to ACME machine.
    </desc>
    </entry>
    <entry id="NODE_FAIL_REGEX">
      <type>char</type>
      <desc>
      A regular expression to search for an indication that a run failure
       was caused by a node failure and should therefore be re-attempted.
    </desc>
    </entry>
    <entry id="MPIRUN_RETRY_REGEX">
      <type>char</type>
      <desc>
      A regular expression to search for an indication that a run failure
      was caused by a known event such as a timeout and should therefore
      be re-attempted.
    </desc>
    </entry>
    <entry id="MPIRUN_RETRY_COUNT" value="0">
      <type>integer</type>
      <desc>The number of times to reattempt the mpirun command if
    MPIRUN_RETRY_REGEX is matched but ALLOCATE_SPARE_NODES is False
    </desc>
    </entry>
    <entry id="PROXY" value="UNSET">
      <type>char</type>
      <desc>
      Proxy (if any) setting for http_proxy to allow web access on this machine.
    </desc>
    </entry>
    <entry id="TEST" value="FALSE">
      <type>logical</type>
      <desc>
      Indicates to case.submit that this is a test case.
    </desc>
    </entry>
    <entry id="DIN_LOC_ROOT" value="/cluster/shared/noresm/inputdata">
      <type>char</type>
      <desc>
      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
    </desc>
    </entry>
    <entry id="DIN_LOC_ROOT_CLMFORC" value="UNSET">
      <type>char</type>
      <desc>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</desc>
    </entry>
  </group>
  <group id="run_dout">
    <entry id="DOUT_S_ROOT" value="/cluster/work/users/$USER/archive/$CASE">
      <type>char</type>
      <desc>Root directory for short term archiving. This directory must be visible to compute nodes.</desc>
    </entry>
    <entry id="DOUT_L_ROOT" value="/projects/NS2345K/noresm/cases">
      <type>char</type>
      <desc>Root directory for long term archiving.</desc>
    </entry>
    <entry id="DOUT_L_HOSTNAME" value="login.nird.sigma2.no">
      <type>char</type>
      <desc>hostname for longterm archiving.</desc>
    </entry>
  </group>
  <group id="run_mpi">
    <entry id="MPI_RUN_COMMAND" value="UNSET">
      <type>char</type>
      <desc>override the mpi run command, do not include model executable</desc>
    </entry>
  </group>
  <group id="run_pio">
    <entry id="PIO_ASYNC_INTERFACE" value="FALSE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>TRUE implies perform asynchronous i/o</desc>
    </entry>
    <entry id="PIO_REARR_COMM_TYPE" value="p2p">
      <type>char</type>
      <valid_values>p2p,coll,default</valid_values>
      <desc>pio rearranger communication type</desc>
    </entry>
    <entry id="PIO_REARR_COMM_FCD" value="2denable">
      <type>char</type>
      <valid_values>2denable,io2comp,comp2io,disable,default</valid_values>
      <desc>pio rearranger communication flow control direction</desc>
    </entry>
    <entry id="PIO_REARR_COMM_MAX_PEND_REQ_COMP2IO" value="0">
      <type>integer</type>
      <valid_values/>
      <desc>pio rearranger communication max pending requests (comp2io) : 0 implies that CIME internally calculates the value ( = max(64, 2 * PIO_NUMTASKS) ), -1 implies no bound on max pending requests </desc>
    </entry>
    <entry id="PIO_REARR_COMM_ENABLE_HS_COMP2IO" value="TRUE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>pio rearranger communiation options (comp2io) : TRUE implies enable handshake </desc>
    </entry>
    <entry id="PIO_REARR_COMM_ENABLE_ISEND_COMP2IO" value="FALSE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>pio rearranger communiation options (comp2io) : TRUE implies enable isend</desc>
    </entry>
    <entry id="PIO_REARR_COMM_MAX_PEND_REQ_IO2COMP" value="64">
      <type>integer</type>
      <valid_values/>
      <desc>pio rearranger communication max pending requests (io2comp) : -1 implies no bound on max pending requests </desc>
    </entry>
    <entry id="PIO_REARR_COMM_ENABLE_HS_IO2COMP" value="FALSE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>pio rearranger communiation options (io2comp) : TRUE implies enable handshake</desc>
    </entry>
    <entry id="PIO_REARR_COMM_ENABLE_ISEND_IO2COMP" value="TRUE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>pio rearranger communiation options (io2comp) : TRUE implies enable isend</desc>
    </entry>
    <entry id="PIO_DEBUG_LEVEL" value="0">
      <type>integer</type>
      <desc>pio debug level</desc>
    </entry>
    <entry id="PIO_BLOCKSIZE" value="-1">
      <type>integer</type>
      <desc>pio blocksize for box decompositions</desc>
    </entry>
    <entry id="PIO_BUFFER_SIZE_LIMIT" value="-1">
      <type>integer</type>
      <desc>pio buffer size limit for pnetcdf output</desc>
    </entry>
    <entry id="PIO_TYPENAME">
      <type>char</type>
      <valid_values>netcdf,pnetcdf</valid_values>
      <desc>pio io type</desc>
      <values>
        <value compclass="ATM">pnetcdf</value>
        <value compclass="CPL">pnetcdf</value>
        <value compclass="OCN">pnetcdf</value>
        <value compclass="WAV">pnetcdf</value>
        <value compclass="GLC">pnetcdf</value>
        <value compclass="ICE">pnetcdf</value>
        <value compclass="ROF">pnetcdf</value>
        <value compclass="LND">pnetcdf</value>
        <value compclass="ESP">pnetcdf</value>
      </values>
    </entry>
    <entry id="PIO_NETCDF_FORMAT">
      <type>char</type>
      <valid_values>classic,64bit_offset,64bit_data</valid_values>
      <desc>pio netcdf format (ignored for netcdf4p and netcdf4c)
    https://www.unidata.ucar.edu/software/netcdf/docs/data_type.html
    </desc>
      <values>
        <value compclass="ATM">64bit_offset</value>
        <value compclass="CPL">64bit_offset</value>
        <value compclass="OCN">64bit_offset</value>
        <value compclass="WAV">64bit_offset</value>
        <value compclass="GLC">64bit_offset</value>
        <value compclass="ICE">64bit_offset</value>
        <value compclass="ROF">64bit_offset</value>
        <value compclass="LND">64bit_offset</value>
        <value compclass="ESP">64bit_offset</value>
      </values>
    </entry>
    <entry id="PIO_STRIDE">
      <type>integer</type>
      <desc>
     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
    </desc>
      <values>
        <value compclass="ATM">$MAX_MPITASKS_PER_NODE</value>
        <value compclass="CPL">$MAX_MPITASKS_PER_NODE</value>
        <value compclass="OCN">$MAX_MPITASKS_PER_NODE</value>
        <value compclass="WAV">$MAX_MPITASKS_PER_NODE</value>
        <value compclass="GLC">$MAX_MPITASKS_PER_NODE</value>
        <value compclass="ICE">$MAX_MPITASKS_PER_NODE</value>
        <value compclass="ROF">$MAX_MPITASKS_PER_NODE</value>
        <value compclass="LND">$MAX_MPITASKS_PER_NODE</value>
        <value compclass="ESP">$MAX_MPITASKS_PER_NODE</value>
      </values>
    </entry>
    <entry id="PIO_REARRANGER">
      <type>integer</type>
      <valid_values>1,2</valid_values>
      <desc>pio rearranger choice box=1, subset=2 </desc>
      <values>
        <value>$PIO_VERSION</value>
        <value compclass="ATM">$PIO_VERSION</value>
        <value compclass="CPL">$PIO_VERSION</value>
        <value compclass="OCN">$PIO_VERSION</value>
        <value compclass="WAV">$PIO_VERSION</value>
        <value compclass="GLC">$PIO_VERSION</value>
        <value compclass="ICE">$PIO_VERSION</value>
        <value compclass="ROF">$PIO_VERSION</value>
        <value compclass="LND">$PIO_VERSION</value>
        <value compclass="ESP">$PIO_VERSION</value>
      </values>
    </entry>
    <entry id="PIO_ROOT">
      <type>integer</type>
      <desc>pio root processor relative to component root</desc>
      <values>
        <value compclass="ATM">1</value>
        <value compclass="CPL">1</value>
        <value compclass="OCN">1</value>
        <value compclass="WAV">1</value>
        <value compclass="GLC">1</value>
        <value compclass="ICE">1</value>
        <value compclass="ROF">1</value>
        <value compclass="LND">1</value>
        <value compclass="ESP">1</value>
      </values>
    </entry>
    <entry id="PIO_NUMTASKS">
      <type>integer</type>
      <desc>
      pio number of io tasks, if this value is -99 it will be computed based on PIO_STRIDE and
      number of tasks
    </desc>
      <values>
        <value compclass="ATM">-99</value>
        <value compclass="CPL">-99</value>
        <value compclass="OCN">-99</value>
        <value compclass="WAV">-99</value>
        <value compclass="GLC">-99</value>
        <value compclass="ICE">-99</value>
        <value compclass="ROF">-99</value>
        <value compclass="LND">-99</value>
        <value compclass="ESP">-99</value>
      </values>
    </entry>
  </group>
  <group id="run_coupling">
    <entry id="CPL_I2O_PER_CAT" value="FALSE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>determine if per ice thickness category fields are passed from ice to ocean - DO NOT EDIT (set by POP build-namelist)</desc>
    </entry>
    <entry id="CCSM_BGC" value="CO2_DMSB">
      <type>char</type>
      <valid_values>none,CO2A,CO2B,CO2C,CO2_DMSA,CO2_DMSB</valid_values>
      <desc>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.
    </desc>
    </entry>
    <entry id="NCPL_BASE_PERIOD" value="day">
      <type>char</type>
      <valid_values>hour,day,year,decade</valid_values>
      <desc>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.</desc>
    </entry>
    <entry id="ATM_NCPL" value="48">
      <type>integer</type>
      <desc>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.</desc>
    </entry>
    <entry id="LND_NCPL" value="$ATM_NCPL">
      <type>integer</type>
      <desc>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.</desc>
    </entry>
    <entry id="ICE_NCPL" value="$ATM_NCPL">
      <type>integer</type>
      <desc>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.</desc>
    </entry>
    <entry id="OCN_NCPL" value="24">
      <type>integer</type>
      <desc>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.</desc>
    </entry>
    <entry id="GLC_NCPL" value="$ATM_NCPL">
      <type>integer</type>
      <desc>Number of glc coupling intervals per NCPL_BASE_PERIOD.</desc>
    </entry>
    <entry id="GLC_AVG_PERIOD" value="yearly">
      <type>char</type>
      <valid_values>glc_coupling_period,yearly</valid_values>
      <desc>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.
    </desc>
    </entry>
    <entry id="ROF_NCPL" value="8">
      <type>integer</type>
      <desc>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.</desc>
    </entry>
    <entry id="WAV_NCPL" value="$ATM_NCPL">
      <type>integer</type>
      <desc>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.</desc>
    </entry>
    <entry id="CPL_SEQ_OPTION" value="RASM_OPTION1">
      <type>char</type>
      <valid_values>CESM1_ORIG,CESM1_ORIG_TIGHT,CESM1_MOD,CESM1_MOD_TIGHT,RASM_OPTION1,RASM_OPTION2</valid_values>
      <desc>
      Coupler sequencing option. This is used to set the driver namelist variable cpl_seq_option.
      CESM1_ORIG is the cesm1.1 implementation.
      CESM1_MOD includes a cesm1.3 mod that swaps ocean merging and atm/ocn flux
      computation.
      RASM_OPTION1 runs prep ocean before the ocean coupling reducing
      most of the lags and field inconsistency but still allowing the ocean to run
      concurrently with the ice and atmosphere.
      RASM_OPTION2 is similar to RASM_OPTION1
      but sequences the ice model, prep ocean and ocean model in that order.  The
      ocean model loses some of the concurrency with the ice model.
      CESM1_ORIG_TIGHT and CESM1_MOD_TIGHT are consistent with the old variables
      ocean_tight_coupling = true in the driver.  That namelist is gone and the
      cpl_seq_option flags take it's place.
      TIGHT coupling makes no sense with the OPTION5 and OPTION6 flags.
    </desc>
    </entry>
  </group>
  <group id="run_drv_history">
    <entry id="HIST_OPTION" value="never">
      <type>char</type>
      <valid_values>none,never,nsteps,nstep,nseconds,nsecond,nminutes,nminute,nhours,nhour,ndays,nday,nmonths,nmonth,nyears,nyear,date,ifdays0,end</valid_values>
      <desc>Sets driver snapshot history file frequency (like REST_OPTION)</desc>
    </entry>
    <entry id="HIST_N" value="-999">
      <type>integer</type>
      <valid_values/>
      <desc>Sets driver snapshot history file frequency (like REST_N)
    </desc>
    </entry>
    <entry id="HIST_DATE" value="-999">
      <type>integer</type>
      <valid_values/>
      <desc>yyyymmdd format, sets coupler snapshot history date (like REST_DATE)</desc>
    </entry>
    <entry id="AVGHIST_OPTION" value="never">
      <type>char</type>
      <valid_values>none,never,nsteps,nstep,nseconds,nsecond,nminutes,nminute,nhours,nhour,ndays,nday,nmonths,nmonth,nyears,nyear,date,ifdays0,end</valid_values>
      <desc>Sets driver average history file frequency (like REST_OPTION)</desc>
    </entry>
    <entry id="AVGHIST_N" value="-999">
      <type>char</type>
      <valid_values/>
      <desc>Sets driver average history file frequency (like REST_N)</desc>
    </entry>
    <entry id="AVGHIST_DATE" value="-999">
      <type>integer</type>
      <valid_values/>
      <desc>yyyymmdd format, sets driver average history date (like REST_DATE)</desc>
    </entry>
  </group>
  <group id="external_tools">
    <entry id="PRERUN_SCRIPT">
      <type>char</type>
      <desc>External script to be run before model completion</desc>
    </entry>
    <entry id="POSTRUN_SCRIPT">
      <type>char</type>
      <desc>External script to be run after model completion</desc>
    </entry>
    <entry id="DATA_ASSIMILATION">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc> Run the external tool pointed to by DATA_ASSIMILATION_SCRIPT after the model run completes </desc>
      <values>
        <value compclass="ATM">FALSE</value>
        <value compclass="CPL">FALSE</value>
        <value compclass="OCN">FALSE</value>
        <value compclass="WAV">FALSE</value>
        <value compclass="GLC">FALSE</value>
        <value compclass="ICE">FALSE</value>
        <value compclass="ROF">FALSE</value>
        <value compclass="LND">FALSE</value>
      </values>
    </entry>
    <entry id="DATA_ASSIMILATION_CYCLES" value="1">
      <type>integer</type>
      <valid_values/>
      <desc> Number of model run - data assimilation steps to complete </desc>
    </entry>
    <entry id="DATA_ASSIMILATION_SCRIPT">
      <type>char</type>
      <valid_values/>
      <desc>External script to be run after model completion</desc>
    </entry>
  </group>
  <group id="run_component_cpl">
    <entry id="CPL_ALBAV" value="FALSE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>
      Only used for compsets with DATM and POP (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.
    </desc>
    </entry>
    <entry id="CPL_EPBAL" value="off">
      <type>char</type>
      <valid_values>off,ocn</valid_values>
      <desc>
      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
    </desc>
    </entry>
    <entry id="COSZ_AVG" value=".true.">
      <type>char</type>
      <valid_values>.true.,.false.</valid_values>
      <desc>
      Default is false and true for N* cpmpsets, controls value of ALB_COSZ_AVG
    </desc>
    </entry>
    <entry id="OCN_FLUX_SCHEME" value="1">
      <type>integer</type>
      <valid_values>0,1,2</valid_values>
      <desc>
      Default is false and true for N* cpmpsets, controls value of FLUX_SCHEME
    </desc>
    </entry>
  </group>
  <group id="run_budgets">
    <entry id="BUDGETS" value="TRUE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>logical that turns on diagnostic budgets for driver</desc>
    </entry>
  </group>
  <group id="run_co2">
    <entry id="CCSM_CO2_PPMV" value="284.32">
      <type>real</type>
      <valid_values/>
      <desc>
      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.
    </desc>
    </entry>
  </group>
  <group id="run_glc">
    <entry id="GLC_NEC" value="10">
      <type>integer</type>
      <valid_values>0,1,3,5,10,36</valid_values>
      <desc>Number of glacier elevation classes used in CLM.
    0 implies no glacier_mec (glacier multiple elevation classes)
    landunit in CLM. 0 is only valid for CLM40.
    Used by both CLM and the coupler (even if CISM is not running, and only SGLC is used).</desc>
    </entry>
    <entry id="GLC_TWO_WAY_COUPLING" value="FALSE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>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.</desc>
    </entry>
  </group>
  <group id="run_physics">
    <entry id="TFREEZE_SALTWATER_OPTION" value="mushy">
      <type>char</type>
      <valid_values>minus1p8,linear_salt,mushy</valid_values>
      <desc>Freezing point calculation for salt water.</desc>
    </entry>
  </group>
  <group id="run_component_cam">
    <entry id="CAM_NML_USE_CASE" value="1850_cam6_noresm">
      <type>char</type>
      <valid_values/>
      <desc>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/atm/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.</desc>
    </entry>
    <entry id="CAM_NAMELIST_OPTS" value=" co2_cycle_rad_passive=.true.   co2_cycle_rad_passive=.true.,dms_source='ocean_flux' ">
      <type>char</type>
      <valid_values/>
      <desc>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.</desc>
    </entry>
  </group>
  <group id="run_component_clm">
    <entry id="LND_TUNING_MODE" value="clm5_0_cam6.0">
      <type>char</type>
      <desc>Tuning parameters and initial conditions should be optimized for what CLM model version and what meteorlogical forcing combination?
    </desc>
      <valid_values>clm4_0_CRUv7,clm4_0_GSWP3v1,clm5_0_cam6.0,clm5_0_GSWP3v1,clm5_0_CRUv7,clm4_5_CRUv7,clm4_5_GSWP3v1,clm4_5_cam6.0</valid_values>
    </entry>
    <entry id="CLM_NML_USE_CASE" value="1850_control">
      <type>char</type>
      <desc>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.</desc>
    </entry>
    <entry id="CLM_BLDNML_OPTS" value="-bgc bgc -crop">
      <type>char</type>
      <desc>CLM build-namelist options</desc>
    </entry>
    <entry id="CLM_CO2_TYPE" value="diagnostic">
      <type>char</type>
      <valid_values>constant,diagnostic,prognostic</valid_values>
      <desc>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.</desc>
    </entry>
    <entry id="CLM_NAMELIST_OPTS">
      <type>char</type>
      <desc>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.</desc>
    </entry>
    <entry id="CLM_ACCELERATED_SPINUP" value="off">
      <type>char</type>
      <valid_values>on,off</valid_values>
      <desc>Turn on any settings for accellerating the model spinup.
    </desc>
    </entry>
    <entry id="CLM_USRDAT_NAME" value="UNSET">
      <type>char</type>
      <desc>Dataset name for user-created datasets. This is used as the argument
      in Buildconf/clm.buildnml to build-namelist -clm_usr_name. An example of
      such a dataset would be 1x1pt_boulderCO_c090722. The default value is UNSET.
      This is an advanced flag and should only be used by expert users.</desc>
    </entry>
    <entry id="CLM_FORCE_COLDSTART" value="off">
      <type>char</type>
      <valid_values>on,off</valid_values>
      <desc>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_clm_clm file.</desc>
    </entry>
  </group>
  <group id="run_component_micom">
    <entry id="MICOM_COUPLING" value="full">
      <type>char</type>
      <valid_values>full,partial</valid_values>
      <desc>Determine surface freshwater and heat forcing settings.
      The full option yields settings that are appropriate for coupling to an
      active atmospheric model (e.g., a B-type compset). The partial option yields
      settings that are appropriate for coupling to a data atmospheric model
      (e.g., a C or G-type compset). The create_newcase command selects the
      appropriate setting for this variable based on the specified compset.
      Users should NOT EDIT this setting.</desc>
    </entry>
    <entry id="MICOM_RIVER_NUTRIENTS" value="TRUE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>Optional input of riverine nutrients. Requires module ecosys</desc>
    </entry>
    <entry id="MICOM_N_DEPOSITION" value="TRUE">
      <type>logical</type>
      <valid_values>TRUE,FALSE</valid_values>
      <desc>Optional nitrogen deposition. Requires module ecosys</desc>
    </entry>
    <entry id="MICOM_N_DEP_FILE" value="ndep_CMIP6_1850.nc">
      <type>char</type>
      <valid_values>ndep_CMIP6_1850.nc,ndep_tnx1v4_185001-201412.nc,UNSET</valid_values>
      <desc>File name for nitrogen deposition data. Requires module ecosys</desc>
    </entry>
  </group>
  <group id="run_component_mosart">
    <entry id="MOSART_SIMYR" value="1850">
      <type>char</type>
      <valid_values/>
      <desc>MOSART build-namelist options</desc>
    </entry>
  </group>
</file>
