IN PROGRESS
...
readonly CASE_NAME=${CHECKOUT}.${DESCRIPTOR}.${RESOLUTION}.${MACHINE}: the case name is a unique identifier for the simulation. It is constructed from variables defined above. If there is no risk of ambiguity, the machine name can be dropped:CASE_NAME=${CHECKOUT}.${DESCRIPTOR}.${RESOLUTION}.
...
readonly OLD_EXECUTABLE="": this is a somewhat risky option that allows you to re-use a pre-existing executable. This is not recommended because it breaks provenance.
...
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 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.
...
Running short tests
The type of run to perform is controlled by the script variable run.
You should typically perform at least two short test tests (two different layouts, with and without restart).
...
Logs being compressed to .gz files is one of the last steps before the job is done and will indicate sucessful completion of the segment. less <log>.gz will let you directly look at a gzipped log.
Short Term Archiving
By default, E3SM will store all output files under the run/ sub-directory. For long simulations, there could 10,000s to 100,000s output files. Having so many files in a single directory can be very impractical, slowing down simple operations like ls to a crawl. CIME includes a short-term archiving utility that will neatly organize output files into a separate archive/ sub-directory.
Short term archiving can be accomplished with the following steps. This can be done while the model is still running.
...
Post-Processing with zppy (needs update)
To post-process a model run, do the following steps. Note that to post-process up to year n, then you must have short-term archived up to year n.
...