Skip to content

Fix non-contiguous node tags in the Gmsh reader (#96) - #98

Merged
nikoscham merged 1 commit into
mainfrom
fix/Non-contiguous-node-tags-in-gmsh-parser
Oct 28, 2026
Merged

nikoscham merged 1 commit into
mainfrom
fix/Non-contiguous-node-tags-in-gmsh-parser

Conversation

@nikoscham

Copy link
Copy Markdown
Member
  • Gmsh reader: when node tags have gaps (max tag > number of nodes), map each tag to a compact 1-based index and remap element and boundary node references; meshes with contiguous tags are read as before
  • Previously each gap added a disconnected node with an all-zero matrix row, so Jacobi returned NaN and the LU solver failed
  • Tests: add gmshReader unit test (test meshes copied with gaps in their node tags give the same nodes, connectivity and solution)

- Gmsh reader: when node tags have gaps (max tag > number of nodes), map
  each tag to a compact 1-based index and remap element and boundary node
  references; meshes with contiguous tags are read as before
- Previously each gap added a disconnected node with an all-zero matrix
  row, so Jacobi returned NaN and the LU solver failed
- Tests: add gmshReader unit test (test meshes copied with gaps in their
  node tags give the same nodes, connectivity and solution)
@nikoscham nikoscham self-assigned this Oct 28, 2026
@nikoscham nikoscham added the bug Something isn't working label Oct 28, 2026
@nikoscham
nikoscham merged commit 88787c6 into main Oct 28, 2026
2 checks passed
@nikoscham
nikoscham deleted the fix/Non-contiguous-node-tags-in-gmsh-parser branch October 28, 2026 18:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Investigate possible bug when handling non-contiguous node tags in Gmsh parser

1 participant