Repository navigation
refactor: BaseStructuredSupport extends StructuredGrid3DGeometry - #367
Merged
lachlangrose merged 3 commits intoNov 1, 2026
Conversation
This was referenced Oct 29, 2026
lachlangrose
force-pushed
the
prototype/support-extends-geometry
branch
from
November 1, 2026 05:51
c92c4c7 to
ce48abf
Compare
lachlangrose
changed the base branch from
master
to
refactor/repair-structured-grid-geometry
November 1, 2026 05:51
lachlangrose
force-pushed
the
prototype/support-extends-geometry
branch
from
November 1, 2026 06:08
ce48abf to
34af4ab
Compare
lachlangrose
marked this pull request as ready for review
November 1, 2026 06:11
The support base re-implemented the grid geometry that StructuredGrid3DGeometry already provides. Make it inherit that class and keep only the support-specific parts (constructor taking cell counts, onGeometryChange hook, interpolator link, position-to-cell corner/vertex helpers, element size, vtk). - the geometry setters call a no-op _on_geometry_change() hook; the support maps it to onGeometryChange(), so setter behaviour is unchanged - BoundingBox.structured_grid imports loop_common.supports lazily (supports now import geometry, so the module-level import would be circular) - drop neighbour_global_indexes from the geometry class: it is a finite-difference stencil helper that StructuredGrid already defines for itself, and inheriting it would have added a method that does not apply to TetMesh/P2TetMesh _3d_base_structured.py shrinks by about 330 lines. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…eference Records geometry, node/element arrays, point location (including exact boundary points), value/gradient evaluation, regularisation operators, every geometry setter, onGeometryChange call counts and constructor validation for StructuredGrid, TetMesh and P2TetMesh on three grids, and compares them with a reference generated from master before BaseStructuredSupport was changed to extend StructuredGrid3DGeometry. Mutating the setter hook, the inside() boundary rule or the cell-index clipping each makes the test fail. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
lachlangrose
force-pushed
the
prototype/support-extends-geometry
branch
from
November 1, 2026 06:54
34af4ab to
7078061
Compare
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.
Step 2 of consolidating the structured-grid geometry code:
BaseStructuredSupportnow extendsStructuredGrid3DGeometryinstead of re-implementing the same geometry.Change
BaseStructuredSupport(StructuredGrid3DGeometry, BaseSupport)keeps only the support-specific parts: the constructor (takes cells, the geometry class takes nodes), theonGeometryChangehook, the interpolator link,position_to_cell_corners/_vertices,node_indexes_to_position,element_size,vtk, and its more tolerantcheck_position. About 330 net lines removed from_3d_base_structured.py.nsteps,step_vector,origin,maximum) call a no-op_on_geometry_change()hook; the support maps it toonGeometryChange(), so setter behaviour is unchanged.BoundingBox.structured_gridimportsloop_common.supportslazily:supportsnow importsgeometry, so the module-level import would be circular.neighbour_global_indexesis removed fromStructuredGrid3DGeometry. It is a finite-difference stencil helper thatStructuredGridalready defines for itself, and inheriting it would have added a method that does not apply toTetMesh/P2TetMesh.How I checked behaviour is unchanged
test_structured_support_reference.pyrecords 611 arrays fromStructuredGrid,TetMeshandP2TetMeshon three grids (geometry, nodes/elements, point location including exact corner and face points, value/gradient evaluation, regularisation operators, each setter,onGeometryChangecall counts, constructor validation) and compares them withtests/data/structured_support_reference.npz(316 KB). The reference was generated frommasterbefore this change, so it pins the original behaviour. Regenerate withpython packages/loop_common/tests/test_structured_support_reference.py --update.Mutation checks: dropping the setter hook, making
inside()exclude the boundary, and removing the cell-index clip each make the test fail.packages/loop_common/tests: 183 passedpackages/loop_interpolation/tests: 606 passed, 46 skipped, 2 xfailed (includes the golden tests)tests: 730 passed, 6 skippedKnown and not addressed
step_vectoras integers makes thenstepssetter raise (_step_vector /= change_factorcannot cast to int). Unchanged: behaves the same before and after, and is not pinned by the reference.RectilinearGrid, and moving the remaining support members up.BaseStructuredSupportinternals.🤖 Generated with Claude Code