ESMCI / cime

Common Infrastructure for Modeling the Earth
http://esmci.github.io/cime
Other
161 stars 207 forks source link

cesm2.1.5 with cime5.6.49 cloudn't use query_config --compsets #4605

Closed ivaNov-0042 closed 2 months ago

ivaNov-0042 commented 5 months ago

cesm2.1.5 with cime5.6.49 cloudn't use query_config --compsets. the input and output is ` ./query_config --compsets drv

usage: query_config [-h] [-d] [-v] [-s] [--xml] [--compsets [{all,CPL,ATM,LND,ICE,OCN,ROF,GLC,WAV,ESP}]] [--components [{all,mct,drv,datm,satm,xatm,cam,clm,dlnd,slnd,xlnd,cice,dice,sice,xice,pop,nemo,docn,socn,xocn,rtm,mosart,drof,srof,xrof,cism,dglc,sglc,xglc,ww3,dwav,swav,xwav,desp,sesp}]] [--grids] [--machines [{all,current,aleph,arc4,athena,aws-hpc6a,bluewaters,centos7-linux,cheyenne,comet,constance,cori-haswell,cori-knl,daint,eastwind,edison,euler2,euler3,euler4,gaea,grace,hobart,homebrew,izumi,laramie,lawrencium-lr3,lawrencium-lr2,lonestar5,melvin,mira,modex,olympus,pleiades-bro,pleiades-has,pleiades-san,pleiades-ivy,sandia-srn-sems,sandiatoss3,stampede2-skx,stampede2-knl,theia,theta,zeus,ubuntu-latest}]] [--long] query_config: error: argument --compsets: invalid choice: 'drv' (choose from 'all', 'CPL', 'ATM', 'LND', 'ICE', 'OCN', 'ROF', 'GLC', 'WAV', 'ESP') `

jedwards4b commented 5 months ago

drv is a component not a compset:

 ./query_config --components drv

    =========================================
    Notes:
    (1) Time period is first four characters of
    compset name
    =========================================

   COMP_CLASSES         : b'List of component classes supported by this driver'
   COMP_CPL             : b'Name of coupling component'
   FILES_CONFIG_SPEC    : b' master configuration file that specifies all relevant filenames\n    and directories to configure a case'
   CASEROOT             : b'full pathname of case'
   CASETOOLS            : b'Case Tools directory location (derived variable, not in namelists'
   CASEBUILD            : b'Buildconf directory location (derived variable not in namelist)'
   SCRIPTSROOT          : b'Scripts root directory location (setup automatically to $CIMEROOT/scripts- DO NOT EDIT)'
   CIMEROOT             : b'full pathname of CIME source root directory'
   SRCROOT              : b'full pathname of source root directory'
   UTILROOT             : b'Scripts root utils directory location (setup automatically to $CIMEROOT/scripts/Tools - DO NOT EDIT)'
   CASE                 : b'case name'
   CASESTR              : b'case description'
   COMPSET              : b'Component set long name (for documentation only - DO NOT EDIT)'
   GRID                 : b'Model grid - DO NOT EDIT (for experts only)'
   SUPPORTED_BY         : b'current machine name support contact'
   USER                 : b'case user name'
   REALUSER             : b'username of user who created case'
   RUN_TYPE             : b'\n      Determines the model run initialization type.\n      This setting is only important for the initial run of a production run when the\n      CONTINUE_RUN variable is set to FALSE.  After the initial run, the CONTINUE_RUN\n      variable is set to TRUE, and the model restarts exactly using input\n      files in a case, date, and bit-for-bit continuous fashion.\n      Default: startup.\n      -- In a startup run (the default), all components are initialized\n      using baseline states.  These baseline states are set independently by\n      each component and can include the use of restart files, initial\n      files, external observed data files, or internal initialization (i.e.,\n      a cold start). In a startup run, the coupler sends the start date to\n      the components at initialization. In addition, the coupler does not\n      need an input data file.  In a startup initialization, the ocean model\n      does not start until the second ocean coupling (normally the second\n      day).\n      -- In a branch run, all components are initialized using a consistent\n      set of restart files from a previous run (determined by the\n      RUN_REFCASE and RUN_REFDATE variables in env_run.xml).  The case name\n      is generally changed for a branch run, although it does not have to\n      be. In a branch run, setting RUN_STARTDATE is ignored because the\n      model components obtain the start date from their restart datasets.\n      Therefore, the start date cannot be changed for a branch run. This is\n      the same mechanism that is used for performing a restart run (where\n      CONTINUE_RUN is set to TRUE in the env_run.xml) Branch runs are\n      typically used when sensitivity or parameter studies are required, or\n      when settings for history file output streams need to be modified\n      while still maintaining bit-for-bit reproducibility. Under this\n      scenario, the new case is able to produce an exact bit-for-bit restart\n      in the same manner as a continuation run IF no source code or\n      component namelist inputs are modified. All models use restart files\n      to perform this type of run.  RUN_REFCASE and RUN_REFDATE are required\n      for branch runs.\n      To set up a branch run, locate the restart tar file or restart\n      directory for RUN_REFCASE and RUN_REFDATE from a previous run, then\n      place those files in the RUNDIR directory.\n      --- In a hybrid run the model is initialized as a startup, BUT uses\n      initialization datasets FROM A PREVIOUS case.  This\n      is somewhat analogous to a branch run with relaxed restart\n      constraints.  A hybrid run allows users to bring together combinations\n      of initial/restart files from a previous case (specified by\n      RUN_REFCASE) at a given model output date (specified by\n      RUN_REFDATE). Unlike a branch run, the starting date of a hybrid run\n      (specified by RUN_STARTDATE) can be modified relative to the reference\n      case. In a hybrid run, the model does not continue in a bit-for-bit\n      fashion with respect to the reference case. The resulting climate,\n      however, should be continuous provided that no model source code or\n      namelists are changed in the hybrid run.  In a hybrid initialization,\n      the ocean model does not start until the second ocean coupling\n      (normally the second day), and the coupler does a cold start without\n      a restart file.\n    '
   RUN_REFDIR           : b'\n      Reference directory containing RUN_REFCASE data - used for hybrid or branch runs\n    '
   RUN_REFCASE          : b'\n      Reference case for hybrid or branch runs\n    '
   RUN_REFDATE          : b'\n      Reference date for hybrid or branch runs (yyyy-mm-dd)\n    '
   RUN_REFTOD           : b'\n      Reference time of day (seconds) for hybrid or branch runs (sssss)\n    '
   GET_REFCASE          : b'\n      Flag for automatically prestaging the refcase restart dataset.\n      If TRUE, then the refcase data is prestaged into the executable directory\n    '
   RUN_STARTDATE        : b'\n      Run start date (yyyy-mm-dd). Only used for startup or hybrid runs.\n    '
   START_TOD            : b'\n      Run start time-of-day\n    '
   STOP_OPTION          : b'\n      Sets the run length along with STOP_N and STOP_DATE\n    '
   STOP_N               : b'\n      Provides a numerical count for $STOP_OPTION.\n    '
   STOP_DATE            : b'\n      Alternative date yyyymmdd date option, sets the run length with STOP_OPTION and STOP_N\n      negative value implies off\n    '
   REST_OPTION          : b'\n      sets frequency of model restart writes (same options as STOP_OPTION)\n    '
   REST_N               : b'\n      sets model restart writes with REST_OPTION and REST_DATE\n    '
   REST_DATE            : b'\n      Alternative date in yyyymmdd format\n      sets model restart write date with REST_OPTION and REST_N\n    '
   PAUSE_OPTION         : b'\n      Sets the pause frequency along with PAUSE_N\n    '
   PAUSE_N              : b'\n      Provides a numerical count for $PAUSE_OPTION.\n    '
   PAUSE_ACTIVE         : b"\n      Pause the model at times specified by PAUSE_OPTION and PAUSE_N.\n      Components 'pause' by writing a restart file.\n    "
   BARRIER_N            : b'\n      Sets periodic model barriers with BARRIER_OPTION and BARRIER_DATE for synchronization\n    '
   BARRIER_DATE         : b'\n      Alternative date in yyyymmdd format\n      sets periodic model barriers with BARRIER_OPTION and BARRIER_N for synchronization\n    '
   ESP_RUN_ON_PAUSE     : b"\n      ESP component runs after driver 'pause cycle' If any component\n      'pauses' (see PAUSE_OPTION,\n      PAUSE_N and PAUSE_ACTIVE_XXX XML variables),\n      the ESP component (if present) will be run to process the\n      component 'pause' (restart) files and set any required 'resume'\n      signals.  If true, esp_cpl_dt and esp_cpl_offset settings are\n      ignored.  default: false\n    "
   CONTINUE_RUN         : b'\n      A setting of TRUE implies a continuation run\n      When you first begin a branch, hybrid or startup run, CONTINUE_RUN\n      must be set to FALSE. When you successfully run and get a restart\n      file, you will need to change CONTINUE_RUN to TRUE for the remainder\n      of your run. This variable determines if the run is a restart run.\n      Set to FALSE when initializing a startup, branch or hybrid case.\n      Set to TRUE when continuing a run.\n    '
   RESUBMIT             : b'If RESUBMIT is greater than 0, then case will automatically resubmit\n    Enables the model to automatically resubmit a new run.  To get\n    multiple runs, set RESUBMIT greater than 0, then RESUBMIT will be\n    decremented and the case will be resubmitted.  The case will stop automatically\n    resubmitting when the RESUBMIT value reaches 0.\n    Long runs can easily outstrip supercomputer queue time limits. For\n    this reason, a case is usually run as a series of jobs, each\n    restarting where the previous finished.\n    '
   RESUBMIT_SETS_CONTINUE_RUN : b'This flag controls whether the RESUBMIT flag causes\n      CONTINUE_RUN to toggle from FALSE to TRUE.  The default is\n      TRUE.  This flag might be used in conjunction with COMP_RUN_BARRIERS for\n      timing tests.\n    '
   JOB_IDS              : b'List of job ids for most recent case.submit'
   JOB_PRIORITY         : b'job priority for systems supporting this option'
   DOUT_S               : b'Logical to turn on short term archiving.\n    If TRUE, short term archiving will be turned on.'
   SYSLOG_N             : b'system workload snapshot frequency (in seconds, if greater than 0; disabled otherwise)'
   environment_variables : b'The environment variables that will be loaded for this machine'
   BATCH_SYSTEM         : b'The batch system type to use for this machine.'
   env                  : b'The individual environment variable entry for config_machines'
   limits               : b'The limits tag'
   limit                : b'The individual limit variable'
   PERL5LIB             : b'Perl 5 library directory'
   CIME_OUTPUT_ROOT     : b'Output root directory for each machine.\n\t\tBase directory for build and run directories.\n    '
   EXEROOT              : b'Case executable root directory.\n    (executable is $EXEROOT/$MODEL.exe, component libraries are in $EXEROOT/lib)\n    This is where the model builds its executable and by default runs the executable.\n    Note that EXEROOT needs to have enough disk space for the experimental configuration\n    requirements. As an example, a model run can produce more than a terabyte of\n    data during a 100-year run, so you should set EXEROOT to scratch or\n    tmp space and frequently back up the data to a long term archiving storage device\n    For a supported machine, EXEROOT is set in $CIMEROOT/machines/config_machines.xml.\n    For a userdefined machine, EXEROOT must explicitly be set it in env_build.xml.'
   OS                   : b'Operating system - DO NOT EDIT UNLESS for userdefined machine - ignored once Macros has been created.'
   COMPILER             : b'Machine compiler (must match one the supported compilers)\n    Set in $CIMEROOT/machines/config_machines.xml for each supported machine.\n    Must be explicitly set in env_build.xml for userdefined machine.'
   MPILIB               : b'mpi library (must match one of the supported libraries) -\n    ignored once Macros has been created\n    Set in $CIMEROOT/machines/config_machines.xml for each supported machine.\n    Must be explicitly set in env_build.xml for userdefined machine.'
   CALENDAR             : b'calendar type'
   COMP_INTERFACE       : b'use MCT component interface'
   USE_ESMF_LIB         : b'TRUE implies using the ESMF library specified by ESMF_LIBDIR or ESMFMKFILE'
   DEBUG                : b'TRUE implies turning on run and compile time debugging\n      Flag to turn on debugging for run time and compile time.\n      If TRUE, compile-time debugging flags are activated that you can use to verify\n      software robustness, such as bounds checking.\n      Important:: On IBM machines, floating point trapping is not activated for production\n      runs (i.e., non-DEBUG), due to performance penalties associated with turning on these flags.'
   FORCE_BUILD_SMP      : b'TRUE implies always build model for openmp capability\n      If FALSE, component libraries are built with OpenMP capability only if\n      the NTHREADS_ setting for that component is greater than 1 in env_mach_pes.xml.\n      If TRUE, the component libraries are always built with OpenMP capability.'
   SMP_PRESENT          : b'TRUE implies that at least one of the components is built threaded (DO NOT EDIT)'
   USE_PETSC            : b'TRUE implies linking to the PETSc library - set\n    automatically by XXX_USE_PETSC options (do not edit). Flag to turn\n    on linking to the PETSc library. Currently this is used by\n    CLM. This is currently only supported for certain machines.'
   USE_ALBANY           : b'TRUE implies linking to the Albany library - set\n    automatically by XXX_USE_ALBANY options (do not edit). Flag to\n    turn on linking to the Albany library. Currently this is used by\n    MALI. Note that Albany is a C++ library, so setting this\n    variable to TRUE will involve the inclusion of C++ code in the\n    MALI executable. This is currently only supported for certain\n    machines.'
   USE_MOAB             : b'TRUE implies linking to the MOAB library'
   USE_TRILINOS         : b'TRUE implies linking to the trilinos library - set automatically by XXX_USE_TRILINOS options (do not edit)\n      Flag to turn on linking to the trilinos library. Currently this is\n      used by CISM. Note that trilinos is a C++ library, so setting this\n      variable to TRUE will involve the inclusion of C++ code in the model\n      executable. This is currently only supported for certain machines.'
   GMAKE                : b'GNU make command'
   GMAKE_J              : b'Number of processors for gmake'
   BUILD_COMPLETE       : b'Status output: if TRUE, models have been built successfully. (DO NOT EDIT)>'
   SMP_BUILD            : b'Status: smp status of previous build, coded string. (DO NOT EDIT)'
   SMP_VALUE            : b'Status: smp status of current case, coded string (DO NOT EDIT)'
   NINST_BUILD          : b'Status: ninst status of previous build, coded string. (DO NOT EDIT)>'
   NINST_VALUE          : b'Status: ninst status of current case, coded string (DO NOT EDIT)'
   BUILD_STATUS         : b'Status: of prior build. (DO NOT EDIT)'
   OBJROOT              : b'case build directory (set automatically to $EXEROOT, - DO NOT EDIT)'
   LIBROOT              : b'case lib directory (set automatically to $EXEROOT/lib - DO NOT EDIT)'
   INCROOT              : b'case lib include directory (set automatically to $EXEROOT/lib/include - DO NOT EDIT)'
   SHAREDLIBROOT        : b'Shared library root, (set automatically to $EXEROOT - DO NOT EDIT)'
   CHECK_TIMING         : b'logical to diagnose model timing at the end of the run'
   PROFILE_PAPI_ENABLE  : b'Enables the papi hardware counters in gptl\n    The papi library must be included in the build step for\n    this to work.'
   ESMF_LOGFILE_KIND    : b'\n      Determines what ESMF log files (if any) are generated when\n          USE_ESMF_LIB is TRUE.\n      ESMF_LOGKIND_SINGLE: Use a single log file, combining messages from\n          all of the PETs. Not supported on some platforms.\n      ESMF_LOGKIND_MULTI: Use multiple log files -- one per PET.\n      ESMF_LOGKIND_NONE: Do not issue messages to a log file.\n      By default, no ESMF log files are generated.\n    '
   COMP_RUN_BARRIERS    : b'Turns on component barriers for component timing.\n\t  This variable is for testing and debugging only and should never\n\t  be set for a production run.\n    '
   COST_PES             : b'pes or cores used relative to MAX_MPITASKS_PER_NODE for accounting (0 means TOTALPES is valid)'
   ATM_GRID             : b'atmosphere grid - DO NOT EDIT (for experts only)'
   ATM_NX               : b'number of atmosphere cells in i direction - DO NOT EDIT (for experts only)'
   ATM_NY               : b'number of atmosphere cells in j direction - DO NOT EDIT (for experts only)'
   LND_GRID             : b'land grid - DO NOT EDIT (for experts only)'
   LND_NX               : b'number of land cells in i direction - DO NOT EDIT (for experts only)'
   LND_NY               : b'number of land cells in j direction - DO NOT EDIT (for experts only)'
   OCN_GRID             : b'ocn grid - DO NOT EDIT (for experts only)'
   OCN_NX               : b'number of ocn cells in i direction - DO NOT EDIT (for experts only)'
   OCN_NY               : b'number of ocn cells in j direction - DO NOT EDIT (for experts only)'
   ICE_GRID             : b'ice grid (must equal ocn grid) - DO NOT EDIT (for experts only)'
   ICE_NX               : b'number of ice cells in i direction - DO NOT EDIT (for experts only)'
   ICE_NY               : b'number of ice cells in j direction - DO NOT EDIT (for experts only)'
   ICE_NCAT             : b'number of ice thickness categories - DO NOT EDIT (set by CICE configure)'
   ROF_GRID             : b'river runoff (rof) grid'
   ROF_NX               : b'number of rof cells in i direction - DO NOT EDIT (for experts only)'
   ROF_NY               : b'number of rof cells in j direction - DO NOT EDIT (for experts only)'
   GLC_GRID             : b'glacier (glc) grid - DO NOT EDIT (for experts only)'
   GLC_NX               : b'number of glc cells in i direction - DO NOT EDIT (for experts only)'
   GLC_NY               : b'number of glc cells in j direction - DO NOT EDIT (for experts only)'
   WAV_GRID             : b'wave model (wav) grid'
   WAV_NX               : b'number of wav cells in i direction - DO NOT EDIT (for experts only)'
   WAV_NY               : b'number of wav cells in j direction - DO NOT EDIT (for experts only)'
   MASK_GRID            : b'grid mask - DO NOT EDIT (for experts only)'
   PTS_MODE             : b'Operate on only a single point of the global grid  - DO NOT EDIT (for experts only)'
   PTS_LAT              : b'Latitude to find nearest points for points mode (only used if PTS_MODE is TRUE)'
   PTS_LON              : b'Longitude to find nearest points for points mode (only used if PTS_MODE is TRUE)'
   ATM_DOMAIN_FILE      : b'atm domain file'
   ATM_DOMAIN_PATH      : b'path of atm domain file'
   LND_DOMAIN_FILE      : b'lnd domain file'
   LND_DOMAIN_PATH      : b'path of lnd domain file'
   ROF_DOMAIN_FILE      : b'rof domain file'
   ROF_DOMAIN_PATH      : b'path of rof domain file'
   WAV_DOMAIN_FILE      : b'wav domain file'
   WAV_DOMAIN_PATH      : b'path of wav domain file'
   ICE_DOMAIN_FILE      : b'ice domain file'
   ICE_DOMAIN_PATH      : b'path of ice domain file'
   OCN_DOMAIN_FILE      : b'ocn domain file'
   OCN_DOMAIN_PATH      : b'path of ocn domain file'
   GLC_DOMAIN_FILE      : b'glc domain file'
   GLC_DOMAIN_PATH      : b'path of glc domain file'
   ATM2OCN_FMAPNAME     : b'atm2ocn flux mapping file'
   ATM2OCN_FMAPTYPE     : b'atm2ocn flux mapping file decomp type'
   ATM2OCN_SMAPNAME     : b'atm2ocn state mapping file'
   ATM2OCN_SMAPTYPE     : b'atm2ocn state mapping file decomp type'
   ATM2OCN_VMAPNAME     : b'atm2ocn vector mapping file'
   ATM2OCN_VMAPTYPE     : b'atm2ocn vector mapping file decomp type'
   ATM2LND_FMAPNAME     : b'atm2lnd flux mapping file'
   ATM2LND_FMAPTYPE     : b'atm2lnd flux mapping file decomp type'
   ATM2LND_SMAPNAME     : b'atm2lnd state mapping file'
   ATM2LND_SMAPTYPE     : b'atm2lnd state mapping file decomp type'
   ATM2WAV_SMAPNAME     : b'atm2wav state mapping file'
   ATM2WAV_SMAPTYPE     : b'atm2wav state mapping file decomp type'
   OCN2ATM_FMAPNAME     : b'ocn2atm flux mapping file'
   OCN2ATM_FMAPTYPE     : b'ocn2atm flux mapping file decomp type'
   OCN2ATM_SMAPNAME     : b'ocn2atm state mapping file'
   OCN2ATM_SMAPTYPE     : b'ocn2atm state mapping file decomp type'
   LND2ATM_FMAPNAME     : b'lnd2atm flux mapping file'
   LND2ATM_FMAPTYPE     : b'lnd2atm flux mapping file decomp type'
   LND2ATM_SMAPNAME     : b'lnd2atm state mapping file'
   LND2ATM_SMAPTYPE     : b'lnd2atm state mapping file decomp type'
   LND2GLC_FMAPNAME     : b'lnd2glc flux mapping file'
   LND2GLC_FMAPTYPE     : b'lnd2glc flux mapping file decomp type'
   LND2GLC_SMAPNAME     : b'lnd2glc state mapping file'
   LND2GLC_SMAPTYPE     : b'lnd2glc state mapping file decomp type'
   LND2ROF_FMAPNAME     : b'lnd2rof flux mapping file'
   LND2ROF_FMAPTYPE     : b'lnd2rof flux mapping file decomp type'
   ROF2LND_FMAPNAME     : b'rof2lnd flux mapping file'
   ROF2LND_FMAPTYPE     : b'rof2lnd flux mapping file decomp type'
   ROF2OCN_FMAPNAME     : b'rof2ocn flux mapping file - the default value idmap_ignore, if set, will be ignored by buildnml and\n    will generate a runtime error if in fact a file is required for the given compset'
   ROF2OCN_FMAPTYPE     : b'rof2ocn flux mapping file decomp type'
   ROF2OCN_LIQ_RMAPNAME : b'rof2ocn runoff mapping file'
   ROF2OCN_LIQ_RMAPTYPE : b'rof2ocn runoff mapping file decomp type'
   ROF2OCN_ICE_RMAPNAME : b'rof2ocn runoff mapping file'
   ROF2OCN_ICE_RMAPTYPE : b'rof2ocn runoff mapping file decomp type'
   GLC2LND_FMAPNAME     : b'glc2lnd flux mapping file'
   GLC2LND_FMAPTYPE     : b'glc2lnd flux mapping file decomp type'
   GLC2LND_SMAPNAME     : b'glc2lnd state mapping file'
   GLC2LND_SMAPTYPE     : b'glc2lnd state mapping file decomp type'
   GLC2ICE_RMAPNAME     : b'glc2ice runoff mapping file - the default value idmap_ignore, if set, will be ignored by buildnml and\n    will generate a runtime error if in fact a file is required for the given compset'
   GLC2ICE_RMAPTYPE     : b'glc2ice runoff mapping file decomp type'
   GLC2OCN_LIQ_RMAPNAME : b'glc2ocn runoff mapping file for liquid runoff - the default value idmap_ignore, if set, will be ignored by buildnml and\n    will generate a runtime error if in fact a file is required for the given compset'
   GLC2OCN_LIQ_RMAPTYPE : b'glc2ocn runoff mapping file decomp type for liquid runoff'
   GLC2OCN_ICE_RMAPNAME : b'glc2ocn runoff mapping file for ice runoff - the default value idmap_ignore, if set, will be ignored by buildnml and\n    will generate a runtime error if in fact a file is required for the given compset'
   GLC2OCN_ICE_RMAPTYPE : b'glc2ocn runoff mapping file decomp type for ice runoff'
   OCN2WAV_SMAPNAME     : b'ocn2wav state mapping file'
   OCN2WAV_SMAPTYPE     : b'ocn2wav state mapping file decomp type'
   ICE2WAV_SMAPNAME     : b'ice2wav state mapping file'
   ICE2WAV_SMAPTYPE     : b'ice2wav state mapping file decomp type'
   WAV2OCN_SMAPNAME     : b'wav2ocn state mapping file'
   WAV2OCN_SMAPTYPE     : b'wav2ocn state mapping file decomp type'
   VECT_MAP             : b'vector mapping option'
   EPS_FRAC             : b'Error tolerance for differences in fractions in domain checking'
   EPS_AAREA            : b'Error tolerance for differences in atm/land areas in domain checking'
   EPS_AMASK            : b'Error tolerance for differences in atm/land masks in domain checking'
   EPS_AGRID            : b'Error tolerance for differences in atm/land lat/lon in domain checking'
   EPS_OAREA            : b'Error tolerance for differences in ocean/ice lon/lat in domain checking'
   EPS_OMASK            : b'Error tolerance for differences in ocean/ice lon/lat in domain checking'
   EPS_OGRID            : b'Error tolerance for differences in ocean/ice lon/lat in domain checking'
   MACH                 : b'Machine name'
   MACHDIR              : b'Machines directory location'
   RUNDIR               : b'\n      The directory where the executable will be run.\n      By default this is set to EXEROOT/../run.\n      RUNDIR allows you to keep the run directory separate from the build directory\n    '
   NODENAME_REGEX       : b'\n      A regular expression to match machine node names to ACME machine.\n    '
   NODE_FAIL_REGEX      : b'\n      A regular expression to search for an indication that a run failure\n       was caused by a node failure and should therefore be re-attempted.\n    '
   MPIRUN_RETRY_REGEX   : b'\n      A regular expression to search for an indication that a run failure\n      was caused by a known event such as a timeout and should therefore\n      be re-attempted.\n    '
   MPIRUN_RETRY_COUNT   : b'The number of times to reattempt the mpirun command if\n    MPIRUN_RETRY_REGEX is matched but ALLOCATE_SPARE_NODES is False\n    '
   PROXY                : b'\n      Proxy (if any) setting for http_proxy to allow web access on this machine.\n    '
   TEST                 : b'\n      Indicates to case.submit that this is a test case.\n    '
   DIN_LOC_ROOT         : b'\n      The root directory of all CIME and component input data for the selected machine.\n      This is usually a shared disk area.\n      Default values for the target machine are in the\n      $CIMEROOT/machines/config_machines.xml\n    '
   DIN_LOC_ROOT_CLMFORC : b'CLM-specific root directory for CLM type input forcing data\n    This directory will only be used for I (CLM/DATM) compsets and only\n    for datm forcing data that is NOT checked into the svn repository\n    (datasets other than the Qian or single-point forcing).\n    This is usually a shared disk area.\n    Default values for the target machine are in the\n    $CIMEROOT/machines/config_machines.xml'
   DOUT_S_ROOT          : b'Root directory for short term archiving. This directory must be visible to compute nodes.'
   MPI_RUN_COMMAND      : b'override the mpi run command, do not include model executable'
   ALLOCATE_SPARE_NODES : b'Allocate some spare nodes to handle node failures. The system will pick a reasonable number'
   FORCE_SPARE_NODES    : b'Force this exact number of spare nodes to be allocated'
   NTASKS               : b'number of tasks for each component'
   NTASKS_PER_INST      : b'Number of tasks per instance for each component. DO NOT EDIT: Set automatically by case.setup based on NTASKS, NINST and MULTI_DRIVER'
   NTHRDS               : b'number of threads for each task in each component'
   ROOTPE               : b'ROOTPE (mpi task in MPI_COMM_WORLD) for each component'
   MULTI_DRIVER         : b'MULTI_DRIVER mode provides a separate driver/coupler component for each\n    ensemble member.  All components must have an equal number of members.  If\n    MULTI_DRIVER mode is False prognostic components must have the same number\n    of members but data or stub components may also have 1 member. '
   NINST                : b'Number of instances for each component.  If MULTI_DRIVER is True\n    the NINST_MAX value will be used.\n    '
   NINST_LAYOUT         : b'Layout of component instances for each component'
   PSTRID               : b'The mpi global processors stride associated with the mpi tasks for the a component'
   TOTALPES             : b'total number of physical cores used (setup automatically - DO NOT EDIT)'
   MAX_TASKS_PER_NODE   : b'maximum number of tasks/ threads allowed per node '
   MAX_MPITASKS_PER_NODE : b'pes or cores per node for mpitasks '
   COSTPES_PER_NODE     : b'pes or cores per node for accounting purposes '
   PIO_VERSION          : b'PIO library version'
   PIO_CONFIG_OPTS      : b'PIO configure options, see PIO configure utility for details'
   PIO_ASYNC_INTERFACE  : b'TRUE implies perform asynchronous i/o'
   PIO_REARR_COMM_TYPE  : b'pio rearranger communication type'
   PIO_REARR_COMM_FCD   : b'pio rearranger communication flow control direction'
   PIO_REARR_COMM_MAX_PEND_REQ_COMP2IO : b'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 '
   PIO_REARR_COMM_ENABLE_HS_COMP2IO : b'pio rearranger communiation options (comp2io) : TRUE implies enable handshake '
   PIO_REARR_COMM_ENABLE_ISEND_COMP2IO : b'pio rearranger communiation options (comp2io) : TRUE implies enable isend'
   PIO_REARR_COMM_MAX_PEND_REQ_IO2COMP : b'pio rearranger communication max pending requests (io2comp) : -1 implies no bound on max pending requests '
   PIO_REARR_COMM_ENABLE_HS_IO2COMP : b'pio rearranger communiation options (io2comp) : TRUE implies enable handshake'
   PIO_REARR_COMM_ENABLE_ISEND_IO2COMP : b'pio rearranger communiation options (io2comp) : TRUE implies enable isend'
   PIO_DEBUG_LEVEL      : b'pio debug level'
   PIO_BLOCKSIZE        : b'pio blocksize for box decompositions'
   PIO_BUFFER_SIZE_LIMIT : b'pio buffer size limit for pnetcdf output'
   PIO_TYPENAME         : b'pio io type'
   PIO_NETCDF_FORMAT    : b'pio netcdf format (ignored for netcdf4p and netcdf4c)\n    https://www.unidata.ucar.edu/software/netcdf/docs/data_type.html\n    '
   PIO_STRIDE           : b'\n     stride in compute comm of io tasks for each component, if this value is -99 it will\n     be computed based on PIO_NUMTASKS and number of compute tasks\n    '
   PIO_REARRANGER       : b'pio rearranger choice box=1, subset=2 '
   PIO_ROOT             : b'pio root processor relative to component root'
   PIO_NUMTASKS         : b'\n      pio number of io tasks, if this value is -99 it will be computed based on PIO_STRIDE and\n      number of tasks\n    '
   NAME                 : b'Test type name'
   DESC                 : b'Test type descriptor'
   TESTCASE             : b'Testcase short name'
   CASEBASEID           : b'Case base ID'
   IS_FIRST_RUN         : b'Is first run of test'
   TEST_ARGV            : b'Arguments supplied to create_test'
   TEST_TESTID          : b'supplied or computed test id'
   TEST_MEMLEAK_TOLERANCE : b'Expected relative memory usage growth for test'
   TEST_TPUT_TOLERANCE  : b'Expected throughput deviation'
   GENERATE_BASELINE    : b'Whether to generate a baseline'
   COMPARE_BASELINE     : b'Whether to compare the baseline'
   BASEGEN_CASE         : b'The tagname we are comparing baselines against'
   BASECMP_CASE         : b'The tagname we are comparing baselines against'
   BASELINE_ROOT        : b'The directory where baselines are stored'
   BASELINE_NAME_GEN    : b'The tagname we are generating baselines for'
   BASELINE_NAME_CMP    : b'The tagname we are comparing baselines against'
   CLEANUP              : b'Whether to clean the test after it is built/run'
   CCSM_CPRNC           : b'standard full pathname of the cprnc executable'
   CPL_I2O_PER_CAT      : b'determine if per ice thickness category fields are passed from ice to ocean - DO NOT EDIT (set by POP build-namelist)'
   HIST_OPTION          : b'Sets driver snapshot history file frequency (like REST_OPTION)'
   HIST_N               : b'Sets driver snapshot history file frequency (like REST_N)\n    '
   HIST_DATE            : b'yyyymmdd format, sets coupler snapshot history date (like REST_DATE)'
   CPL_DECOMP           : b'Coupler decomposition option.'
   INFO_DBUG            : b'level of debug output, 0=minimum, 1=normal, 2=more, 3=too much'
   CLM_USE_PETSC        : b'TRUE implies CLM is built with support for the PETSc\n      library. The Variably Saturated Flow Model (VSFM) solver in CLM\n      uses the PETSc library. In order to use the VSFM solver, CLM\n      must be built with PETSc support and linking to PETSc must occur\n      when building the ACME executable. This occurs if this variable\n      is set to TRUE. Note that is only available on a limited set of\n      machines/compilers.'
   PRERUN_SCRIPT        : b'External script to be run before model completion'
   POSTRUN_SCRIPT       : b'External script to be run after model completion'
   DATA_ASSIMILATION    : b' Run the external tool pointed to by DATA_ASSIMILATION_SCRIPT after the model run completes '
   DATA_ASSIMILATION_CYCLES : b' Number of model run - data assimilation steps to complete '
   DATA_ASSIMILATION_SCRIPT : b'External script to be run after model completion'
   EXTERNAL_WORKFLOW    : b'whether the case uses an external workflow driver '
   USER_REQUESTED_QUEUE : b'Store user override for queue'
   USER_REQUESTED_WALLTIME : b'Store user override for walltime'
   JOB_QUEUE            : b'The machine queue in which to submit the job.  Default determined in config_machines.xml can be overwritten by testing'
   JOB_WALLCLOCK_TIME   : b'The machine wallclock setting.  Default determined in\n   config_machines.xml can be overwritten by testing.  Format is\n   DD:HH:MM with DD assumed 0 if not present, this is translated to\n   the format specified by walltime format defined in\n   config_batch.xml'
   BATCH_COMMAND_FLAGS  : b'Override the batch submit command this job. Do not include executable or dependencies'
   PROJECT              : b'project for project-sensitive build and run paths, and job scripts'
   CHARGE_ACCOUNT       : b'project to charge in scripts if different from PROJECT'
   MODEL_VERSION        : b'Apparent version of the model used for this case'
   PROJECT_REQUIRED     : b'whether the PROJECT value is required on this machine'

That said I do see a problem with the --compsets argument and will try to address it.

mvertens commented 5 months ago

@jedwards - drv is not exactly a component. And this is where it gets confusing. The mediator is a component - that can be shared among different models. The driver is what determines the evolution of the whole system, runs on all the tasks and normally is not shared between different modeling efforts. Some of the above namelists are driver specific and some are mediator specific. The problem is that we didn't really separate this when we created the mediator xml and namelist settings so this has stayed a bit confusing. Historically, this came from the fact that in cpl7 the driver and the coupler really had no clear separation. In the case of CMEPS - this is no longer the case. I'm happy to discuss this in more detail - but we should probably try to come up with a better separation moving forwards.

github-actions[bot] commented 2 months ago

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] commented 2 months ago

This issue was closed because it has been stalled for 5 days with no activity.