...
Before starting a long production run, it is highly recommended to perform a few short tests to verify:
The model starts without errors.
The model produces BFB (bit-for-bit) results after a restart.
The model produces BFB results when changing PE layout.
(1) can spare you from a considerable amount of frustration. Imagine submitting a large job on a Friday afternoon, only to discover Monday morning that the job started to run on Friday evening and died within seconds because of a typo in a namelist variable or input file.
...
You can ask questions about zppy on https://github.com/E3SM-Project/zppy/discussions/categories/general
Install zppy
If you haven't already, check out the zppy repo in <code_source_dir>. Go to https://github.com/E3SM-Project/zppy . Get path to clone by clicking the green "Code" button. Run git clone <path>.
Load the E3SM unified environment. For Chrysalis, this is: source /lcrc/soft/climate/e3sm-unified/load_latest_e3sm_unified_chrysalis.sh. Commands for other machines, and installation guide for development version of zppy can be found at https://e3sm-project.github.io/zppy/_build/html/main/getting_started.html
...
Log into Globus, using your NERSC credentials: https://www.globus.org/
(Left hand side): Transfer from
<the machine's DTN> <simulations_dir>/<case_name>/zstashClick enter on path and "select all" on left-hand side
Transfer to
NERSC DTN /global/cfs/cdirs/e3sm/<username>/E3SMv2/<case_name>Notice we're using
cfsrather thanscratchon Cori
Click enter on the path
Click “Transfer & Sync Options” in the center.
Choose:
“sync - only transfer new or changed files” (choose “modification time is newer” in the dropdown box)
“preserve source file modification times”
“verify file integrity after transfer”
For “Label This Transfer”: “zstash <case_name> <machine name> to NERSC”
Click "Start" on the left hand side.
You should get an email from Globus when the transfer is completed. (On Chrysalis, for 165 years of data, this transfer takes ~13 hours).
...