Tetrahedral remeshing sequential refactoring#9559
Open
IasonManolas wants to merge 5 commits into
Open
Conversation
Introduces ElementaryOperation, the interface for a single mesh-editing operation (candidate source, per-candidate execution, name), and ElementaryOperationExecutionSequential, which collects an operation's candidates once and applies each in the order the operation returns them. This is the common scaffolding that the split, collapse, flip and smooth operations are refactored onto in the following commits. It is generic and not yet used by any code path.
…ion framework Replace the split_long_edges() free function with EdgeSplitOperation, an ElementaryOperation whose get_element_source() collects and length- orders the splittable edges (stable_sort, longest first, matching the original bimap ordering) and whose execute_operation() re-validates and splits one edge. Adaptive_remesher::split() now drives it through ElementaryOperationExecutionSequential. Output is unchanged: remeshing a mesh through this path yields a byte-identical result to the previous implementation. Add generic timing/progress reporting to the sequential executor: elapsed time per operation under CGAL_TETRAHEDRAL_REMESHING_VERBOSE and a live per-candidate progress line under CGAL_TETRAHEDRAL_REMESHING_VERBOSE_PROGRESS, replacing the equivalent per-operation reporting the free function used to do itself. The visitor before_split()/after_split() hooks and the CGAL_TETRAHEDRAL_REMESHING_DEBUG diagnostic dumps are preserved.
…on framework Replace the flip_edges() free function with two ElementaryOperations sharing EdgeFlipOperationBase: - InternalEdgeFlipOperation mirrors flip_all_edges(): reset the cell caches, collect the internal edges, and run find_best_flip() on each. - BoundaryEdgeFlipOperation mirrors flipBoundaryEdges(): compute the per-vertex boundary valences once in get_element_source(), then flip each boundary edge on the surface when it lowers the valence cost, updating the valences. Adaptive_remesher::flip() owns a single incident-cells cache and passes it to both operations by reference, running the internal pass, then the boundary pass when boundaries are not protected -- reproducing the map sharing and pass order of the former flip_edges(). The find_best_flip()/flip_on_surface() machinery and the CGAL_TETRAHEDRAL_REMESHING_DEBUG orientation check are unchanged. Remeshing a mesh through this path yields a byte-identical result to the previous implementation.
…operation framework Replace Tetrahedral_remeshing_smoother with Vertex_smoothing_context (smoothing state + setup helpers), VertexSmoothOperationBase (per-vertex helpers), and one ElementaryOperation per pass: ComplexEdgeVertexSmoothOperation, SurfaceVertexSmoothOperation and InternalVertexSmoothOperation. Each get_element_source() accumulates the per-vertex moves and each execute_operation() moves one vertex, mirroring the former smooth_edges_in_complex/on_surfaces/internal_vertices. Adaptive_remesher keeps the context as a persistent member and runs the three operations in the previous order (1D, 2D, 3D) each smoothing step. Remeshing yields a byte-identical result to the previous implementation.
…ration framework Replace the collapse_short_edges() free function with EdgeCollapseOperation. get_element_source() collects and length-orders (shortest first) the collapsible edges once; execute_operation() collapses one edge, skipping those invalidated by an earlier collapse via a should_skip map. Unlike the former dynamic bimap worklist, the candidate list is static: edges that become short during a pass are not re-collapsed in that pass but in the next remeshing iteration. This changes the result (it is not byte-identical), but Dihedral_Angle.Mean is unchanged within noise (+0.024% on bear). The shared collapse_edge()/collapse() helpers now mark invalidated edges through remove_from_bimap (repurposed to set the skip flag); the now-unused update_bimap is removed.
IasonManolas
changed the title
Member
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
2 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.
Summary
This PR refactors the four Tetrahedral Remeshing elementary operations: edge split, edge collapse, edge flip and vertex smoothing onto a common sequential execution framework, developed during GSoC 2025.
Each operation is expressed through a small, uniform interface: collect the candidate elements, then execute the operation on one candidate, driven by a single executor. This separates what each operation does from how the set of operations is executed, and prepares the ground for a parallel executor, which will be added in a follow-up PR on top of the same interface.
This is a structural, behaviour-preserving refactoring; it introduces no new parallelism.
New classes
Commits
Adaptive_remesher runs the operations directly through the sequential executor; the original free functions are replaced.
Behaviour
Scope
To keep the change focused and reviewable, this PR is sequential-only. A follow-up PR will add ElementaryOperationExecutionParallel (with the locking model and the Triangulation_3 generalisations) on top of this interface. No benchmark infrastructure or new CMake options are included here.
Test plan