Fix for stitch_meshes() with NodeElem surface#4334
Merged
jwpeterson merged 6 commits intolibMesh:develfrom Nov 21, 2025
Merged
Conversation
This was broken when libMesh#4283 was merged.
To do the conversion, first ncdump the file to text:
$LIBMESH_DIR/bin/ncdump foo.e > foo.txt
Edit the resulting text file so that it does not contain any features
not supported by older Exodus files. For example:
:file_size = 1LL ; --> :file_size = 1 ;
int64 ns_prop1(num_node_sets) ; --> int ns_prop1(num_node_sets) ;
Then ncgen with the -k '64-bit offset' option:
$LIBMESH_DIR/bin/ncgen foo.txt -k '64-bit offset' -o foo.e
The ncdump and ncgen commands are located in the bin/ directory of
your libmesh installation.
roystgnr
approved these changes
Nov 21, 2025
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
3 participants
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.
When #4283 was merged, the
NodeElemcheck got moved into a side loop, which didn't make any sense. This caused one of our internal tests to break, so I have now made that case into a small libmesh unit test so we can hopefully avoid this issue in the future.