NERSC performance archiving for multiple projects

[sarats]

E3SM/cime_config/machines/config_machines.xml

Line 155 in d1388dd

<SAVE_TIMING_DIR_PROJECTS>e3sm,m3411,m3412</SAVE_TIMING_DIR_PROJECTS>

We can use a wildcard like '*' but that probably would capture a lot of experiments from non-E3SM project members.
We need to think if we would still like to capture all E3SM runs on Perlmutter.

Otherwise, we need to update the list of projects with any others that we wish to archive.

The incremental cost of allowing additional projects to be archived is proportional to the number of jobs they plan to run. At this stage, I want to evaluate this on a case by case basis.

[sarats]

Will add m4259 that is used by ImPACTS SciDAC project
cc @vanroekel

[darincomeau]

m1199 for the E3SM-Arctic simulations under the HiLAT-RASM project would be great to have.
cc: @milenaveneziani

[sarats]

Other projects that were requested.

m3520 cc: @bishtgautam RDycore SciDAC

m4048 from @beharrop

Wei Cheng is the PI. It's an RGMA project looking at ECS sensitivity to ocean heat transport and cloud feedbacks using the slab ocean configuration of E3SM with a cloud-locking capability

[sarats]

m3312 cc: @whannah1 PI & topic?

@ndkeen Do you know the topics and PIs for m3411 and m3412 (existing)?

[sarats]

One aspect to consider is the performance archive location and ability for users in some of these projects to write to that location.

Currently, it's set to
<SAVE_TIMING_DIR>/global/cfs/cdirs/e3sm</SAVE_TIMING_DIR>

We ought to consider a world-writable location in that case.