Add capability to read exodus files with time-varying data #1493
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I have added code to read exodus files with time-varying data.
A field "a" that contains "values" of length T previously returned values[0]. Now, if len(values) > 1, new fields are created such as ["a_time0", "a_time1", ..., "a_timeT"]. This has been implemented for point data and cell data.
I added a unit test for cell_data (not time-dependent), and also for time-varying point_data. The latter was a bit trickier, I couldn't find out how to create time-varying data in the
in_meshobject. So instead, exodus.write, will write the same value for each step. This is just so the unit-test can check that something is being written. This is probably not the best thing to do, but it seems the data cannot be viewed in paraview anyway, so we could consider adding a warning to use xdmf for writing time-dependent data.Thanks for developing this great tool.
Josh