...
CUSTOM CASE_NAME
set case_name = ${machine}.${tag_name}.${job_name}.${resolution}
:${tag_name}.${job_name}.${resolution}.${machine}
is also used.Note that
job_name
(seeBASIC INFO ABOUT RUN
) typically has two parts (separated by period), socase_name
will actually have five four parts.If you are comparing the same case across different machines, add
${machine}
:${machine}.${tag_name}.${job_name}.${resolution}
or${tag_name}.${job_name}.${resolution}.${machine}
.
PROCESSOR CONFIGURATION
set processor_config = S
:S
,M
,L
sizes, amongst other specified in the "EXPLANATION FOR OPTIONS ABOVE:" section. UseS
for short tests. Full simulations should useL
. The size determines how many nodes will be used. The exact number of nodes will differ amongst machines.
...
readonly CASE_NAME=${CHECKOUT}.${DESCRIPTOR}.${MACHINE}
: sets the case name. This will look like20210205.v2_test02.piControl.ne30pg2_EC30to60E2r2.chrysalis
using the example values on this page.If you are not comparing the same case on different machines, you can exclude the add
.${MACHINE}
:${CHECKOUT}.${DESCRIPTOR}.${MACHINE}
part.
# Set paths
readonly CODE_ROOT="${HOME}/E3SM/code/${CHECKOUT}"
: where the E3SM code will be checked out.readonly CASE_ROOT="/lcrc/group/e3sm/${USER}/E3SM_simulations/${CASE_NAME}"
: where the results will go. The directory${CASE_NAME}
will be in<simulations_dir>
.
...