-
Notifications
You must be signed in to change notification settings - Fork 52
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
Support time navigation #325
Comments
The data from previous times steps is discarded when a new time step is received, so going back is not supported at this point. One way to control the timestep updates is to enable the auto-pause mode by pressing ctrl+space before pressing space. In this mode pressing space advances one time step and auto-pauses. Pressing ctrl+space simply toggles the auto-pause mode. |
Time navigation will be a useful extension, but it will require new infrastructure and significantly more memory than the current approach (which essentially holds a single instance at a time). When the data comes by socket, that memory can increase quite significantly... I am not sure we want to do that (ping @justinlaughlin). |
I agree that I don't think we'd want to support this by socket, but it would be a very sensible feature for saved data. I believe the I think the proper way to implement this would be through something like As a holdover solution - another possible option is to save the time-steps by filename and use Edit: Actually, as I think about it a bit more, maybe it wouldn't be so bad to support this by socket for small problems; this could be kept at a manageable-level through a default memory limit. |
MFEM supports ParaView, VisIt and other (including Sidre) through |
When a simulation has multiple time steps, is it possible to navigate backward and forward in time? When pressing the space bar, the animation starts and I haven't seen in the doc or help a shortcut to control the playback.
Attached is an example of a saved session obtained by running the mfem ex10
glvis-saved.0001.zip
The text was updated successfully, but these errors were encountered: