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

Specifying path for permament checkpoints #21

Open
alextbradley opened this issue Jun 11, 2021 · 1 comment
Open

Specifying path for permament checkpoints #21

alextbradley opened this issue Jun 11, 2021 · 1 comment
Assignees

Comments

@alextbradley
Copy link
Collaborator

We can specify path for outputs, so seems natrual (and indeed would make things cleaner when running tests and experiments) to also permit path specification for checkpoints

alextbradley added a commit that referenced this issue Jun 15, 2021
added option to specify either of end_time or n_iter_total (or both, provided they're compatible) (#15) and added a path for checkpoint output (#21). Initialized testing of timesteppingParams
@alextbradley
Copy link
Collaborator Author

Previous commit should have rectified this, but leaving this open because these changes haven't yet been implemented in testing

@alextbradley alextbradley self-assigned this Jun 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant