Skip to content

Conversation

@gunney1
Copy link
Contributor

@gunney1 gunney1 commented Jan 2, 2026

Summary

  • This PR is a feature
  • It does the following:
    • Implement 18-tet decomposition for a hex for clipping.

The 18-tet decomposition should reduce work compared to the default 24-tet decomposition, because it generates fewer tets. If a hex face has 4 coplanar vertices, there will be degenerate tets, so we check for them. For on-going performance evaluation, we are supporting both decompositions for now.

This change is part of the bigger change for improving mesh clipping performance.

For backward compatibility and on-going evaluation of using 18 tets,
the 24-tet decomposition is still supported.  The choice is in the
compile-time parameter NUM_TETS_PER_HEX.
@gunney1 gunney1 added this to the FY26 January Release milestone Jan 2, 2026
@gunney1 gunney1 self-assigned this Jan 2, 2026
@gunney1 gunney1 added Quest Issues related to Axom's 'quest' component Performance Issues related to code performance labels Jan 2, 2026
Copy link
Contributor

@Arlie-Capps Arlie-Capps left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your work on this, @gunney1 .

@gunney1 gunney1 merged commit ffda074 into develop Jan 6, 2026
15 checks passed
@gunney1 gunney1 deleted the feature/gunney/18-tets-per-hex branch January 6, 2026 18:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Performance Issues related to code performance Quest Issues related to Axom's 'quest' component

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants