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

Add support for restart files #7

Open
rcarson3 opened this issue Mar 24, 2020 · 2 comments
Open

Add support for restart files #7

rcarson3 opened this issue Mar 24, 2020 · 2 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@rcarson3
Copy link
Member

For large simulations, the ability to restart the simulations is vital.

We need to be able to save out the mesh, velocity field, current time step, end-time step state variables, and end-time step stress state. All the other data can be recovered from our initial data files. In order to do this we'll need to help expand some of the MFEM data collections for this purpose. Currently, the various data collections do not support saving out or loading QuadratureFunction data which is needed for the state variable and stress states.

Conduit and ADIOS2 data collections might be our best bet to get these fields implemented.

@rcarson3 rcarson3 added enhancement New feature or request help wanted Extra attention is needed labels Mar 24, 2020
@rcarson3
Copy link
Member Author

rcarson3 commented May 2, 2020

One possible way to support this now would be potentially to save the quadrature data off using an L2 FiniteElementSpace GridFunction of the same order as the QuadratureFunction using the SidreDataCollections. This assumes that when things are saved off that the L2 data isn't projected back to the nodal points but instead stays at the quadrature values. The one thing would be when things are reloaded we may not be able to guarantee that the QuadratureSpace will be correctly restored when things are reloaded.

@rcarson3
Copy link
Member Author

So this should be really easy once PR# LLNL/axom#433 is pulled in. Afterwards, we just have to load back-up the desired cycle for the user, and we'll be off to the races :) Also, the PR there actually supports QF themselves, so we know everything is at quadrature points for our state variables. Although, we might have to wait on a subsequent PR that I'll write within MFEM as well for everything to be in-place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant