Add lazy ParaView point-field writer - #857
Draft
hughcars wants to merge 2 commits into
Draft
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.
This is 8/10 in the stacked replacement for #824/#825 and depends on #856. Please review only the diff against that PR.
This adds a standalone
CeedParaViewDataCollectionthat serializes device-evaluated point and cell fields to VTU/PVTU output.Reviewer guidance: Review this independently of FE semantics. The key concerns are the single authoritative refinement lattice, point-major tuple ordering, appended-data offsets, exact tuple counts, MPI piece metadata, and lazy host staging.
Deferred: Nothing registers or invokes this writer until the next PR.
Validation: Exact branch build passed through Spack with unit-test support enabled.