These variables CANNOT be modified once case_setup has been invoked without first invoking case_setup -reset NTASKS: the total number of MPI tasks, a negative value indicates nodes rather than tasks. NTHRDS: the number of OpenMP threads per MPI task. ROOTPE: the global mpi task of the component root task, if negative, indicates nodes rather than tasks. PSTRID: the stride of MPI tasks across the global set of pes (for now set to 1) NINST : the number of component instances (will be spread evenly across NTASKS) for example, for NTASKS = 8, NTHRDS = 2, ROOTPE = 32, NINST = 2 the MPI tasks would be placed starting on global pe 32 and each pe would be threaded 2-ways These tasks will be divided amongst both instances (4 tasks each). Note: PEs that support threading never have an MPI task associated with them for performance reasons. As a result, NTASKS and ROOTPE are relatively independent of NTHRDS and they determine the layout of mpi processors between components. NTHRDS is used to determine how those mpi tasks should be placed across the machine. The following values should not be set by the user since they'll be overwritten by scripts: TOTALPES, NTASKS_PER_INST

none integer pes or cores used relative to MAX_MPITASKS_PER_NODE for accounting (0 means TOTALPES is valid) integer total number of physical cores used (setup automatically - DO NOT EDIT) integer maximum number of tasks/ threads allowed per node integer pes or cores per node for mpitasks integer pes or cores per node for accounting purposes logical TRUE,FALSE Allocate some spare nodes to handle node failures. The system will pick a reasonable number integer Force this exact number of spare nodes to be allocated integer 768 768 186 300 768 504 8 256 1 number of tasks for each component integer 768 186 300 768 504 8 256 1 Number of tasks per instance for each component. DO NOT EDIT: Set automatically by case.setup based on NTASKS, NINST and MULTI_DRIVER integer 1 1 1 1 1 1 1 1 1 number of threads for each task in each component integer 0 0 768 0 0 264 256 0 0 ROOTPE (mpi task in MPI_COMM_WORLD) for each component logical TRUE,FALSE MULTI_DRIVER mode provides a separate driver/coupler component for each ensemble member. All components must have an equal number of members. If MULTI_DRIVER mode is False prognostic components must have the same number of members but data or stub components may also have 1 member. integer 1 1 1 1 1 1 1 1 Number of instances for each component. If MULTI_DRIVER is True the NINST_MAX value will be used. char sequential,concurrent concurrent concurrent concurrent concurrent concurrent concurrent concurrent concurrent Layout of component instances for each component integer 1 1 1 1 1 1 1 1 1 The mpi global processors stride associated with the mpi tasks for the a component