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

What to save in checkpoints? #419

Open
landinjm opened this issue Jan 29, 2025 · 0 comments
Open

What to save in checkpoints? #419

landinjm opened this issue Jan 29, 2025 · 0 comments
Assignees

Comments

@landinjm
Copy link
Contributor

There is some decisions we have to make when saving checkpoints. Currently we save the triangulation, all solution fields, the time, and the increment. If old solution fields are stored, those should also be saved.

We may want to include some more runtime parameters such as:

  • Element degree
  • Boundary conditions

Additionally, certain fields may not need to be saved. AUXILIARY and TIME_INDEPENDENT and determined at each step entirely by other fields.

@fractalsbyx @zachcroft @david-montiel-t thoughts?

@landinjm landinjm mentioned this issue Feb 4, 2025
19 tasks
@landinjm landinjm self-assigned this Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant