Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE REQUEST] Turn off writing initial checkpoint file #13

Closed
lizziel opened this issue Feb 28, 2020 · 1 comment
Closed

[FEATURE REQUEST] Turn off writing initial checkpoint file #13

lizziel opened this issue Feb 28, 2020 · 1 comment
Assignees
Labels
category: Feature Request New feature or request
Milestone

Comments

@lizziel
Copy link
Contributor

lizziel commented Feb 28, 2020

Default values in GCHPctm 13.0.0-alpha.2 (and all previous GCHP versions) write a MAPL internal state checkpoint file during the first timestep. At high resolutions this adds significantly to the run-time. We should have the ability to turn off writing this first checkpoint file. It shouldn't be needed since we already have a restart file and the output checkpoint file is written separately at the end of the run.

@lizziel lizziel added the category: Feature Request New feature or request label Feb 28, 2020
@lizziel lizziel added this to the 13.0.0 milestone Oct 21, 2020
@lizziel
Copy link
Contributor Author

lizziel commented Oct 21, 2020

In GCHP 13.0.0 the default of writing periodic checkpoints is turned off. This avoids writing a restart file at simulation start.

Configuring periodic checkpoint writes, either at regular or irregular intervals, is now an option from runConfig.sh. It is always off by default for all newly generated run directories. If periodic checkpoint write is turned on with regular frequency, then a restart will still be written at run-time start. As was the case before this update, it will be filled with zeros. This is due to the location of file write relative to population of internal state in the execution sequence.

Completely avoiding writing a restart filled with zero at run-time start while also have regularly scheduled checkpoint writes is doable. However, it requires setting the checkpoint ref date and time to be just prior to simulation start time, thereby making the interval between start and first checkpoint file shorter than the interval between subsequent checkpoint files. Doing this will require some custom adaptation of runConfig.sh. If you interested in this I encourage you to try it!

@lizziel lizziel closed this as completed Oct 21, 2020
@lizziel lizziel self-assigned this Oct 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: Feature Request New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant