-
Notifications
You must be signed in to change notification settings - Fork 211
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'jgfouca/cime/refactor_provenance' (PR #1436)
Refactor provenance saving The logic associated with the env_run.xml variables SAVE_TIMING and SAVE_TIMING_DIR, used to decide when and where to archvie performance data and related provenance, was inadvertently modified in the transition between CIME2 and CIME5. Also, the CIME5.3 merge inadvertently mixed up provenance data archiving with other performance data collection-related actions. The restored logic is as follows: a) If SAVE_TIMING is TRUE, then, at the completion of a job, the timing subdirectory in the job run directory is renamed timing.$lid, and then tarred and gzipped (and the original timing.$lid directory is removed). An empty file named timing.$lid.saved is created in the timing subdirectory of the case directory to flag that this occurred. Also, if SAVE_TIMING_DIR points to an existing directory in which a directory named performance_archive already exists or can be created, then the performance data and some system, job, and case provenance data are copied to the performance_archive. If SAVE_TIMING_DIR does not point to such a directory or contains the string 'UNSET', then this performance data and provenance archiving does not occur. A system-specific default for SAVE_TIMING_DIR is typically set in cime/config/acme/machines/config_machines.xml. If not set there, then the default for SAVE_TIMING_DIR is 'UNSET'. b) If SAVE_TIMING is FALSE, then the timing directory in the job run directory is not renamed. Also SAVE_TIMING_DIR is ignored and performance data and provenance are not archived. Fixes #1421 [BFB]
- Loading branch information
Showing
5 changed files
with
66 additions
and
52 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters