...
Dataset Type | Core File Pattern | Comment |
atm nat mon | *cam.h0* | |
atm nat day | *cam.h1* | |
atm nat 6hr_snap | *cam.h2* | |
atm nat 6hr | *cam.h3* | |
atm nat 3hr_snap | *cam.h2* | BGC-only |
atm nat 3hr | *cam.h4* | |
atm nat 3hr | *cam.h3* | BGC-only |
atm nat day_cosp | *cam.h5* | |
lnd nat mon | *clm2.h0* | |
river nat mon | *mosart.h0* | |
ocn nat mon | *mpaso.hist.am.timeSeriesStatsMonthly.* | these are not “time-series” in the same sense as the post-process “regridded time series” |
ocn nat globalStats | *mpaso.hist.am.globalStats.* | |
ocn nat 5day | *mpaso.hist.am.highFrequencyOutput.* | |
sea-ice nat mon | *mpascice.hist.am.timeSeriesStatsMonthly.* | these are not “time-series” in the same sense as the post-process “regridded time series” |
sea-ice nat day | *mpascice.hist.am.timeSeriesStatsDaily.* | these are not “time-series” in the same sense as the post-process “regridded time series” |
STEP 1: The first step in producing the archive catalog is to run:
...
If instead we discovered that “first” and “last” did not match, we have two possible courses of action. If it is determined that one or the other involves the wrong tar-path, then the list of “tar-path elements to avoid” in the archive_path_mapper_stage2.sh script must be updated to eliminate the incorrect path, and we rerun that script to obtain a new output file. On some occasions this may be needed more than once, in order to determine the intended tar-path to the finalized run.
On the other hand, if the tar-paths are equal, but it seems that variant filenames are found, there are both benign and difficult cases. A benign case exists where the files may have differing generation-dates, but are intended to be part of a a single finalized run, as in
...
You can test the correctness of the “update_Archive_Map” by . . . (to be continued…)