Add nodeTags and eleTags to VTKHDF recorder HDF5 output#1
Draft
Add nodeTags and eleTags to VTKHDF recorder HDF5 output#1
Conversation
Co-authored-by: amnp95 <92498292+amnp95@users.noreply.github.com> Agent-Logs-Url: https://github.com/amnp95/OpenSees/sessions/3a39f871-69a9-4f02-b1aa-bb59467125c3
Copilot created this pull request from a session on behalf of
amnp95
March 24, 2026 00:33
View session
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
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.
VTKHDF recorder stored node/element tags only as in-memory structures, making it impossible for external tools (e.g., ParaView) to map sequential indices back to original OpenSees node/element IDs.
Changes
Constructor: Unconditionally create
PointData/nodeTagsandCellData/eleTags(1D int, chunked) alongside their correspondingSteps/PointDataOffsets/nodeTagsandSteps/CellDataOffsets/eleTagsoffset tracking datasets.writeMesh(): WritetheNodeTagsandtheEleTagsonce when the mesh is initialized — tags are constant so they are never re-written on domain changes or subsequent steps.writeStep(): Append offset0to both offset datasets at every time step. Since the data is written once and never changes, all steps point to the beginning of the arrays.Resulting HDF5 structure