Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improvement on Overlap Check Tool #797

Open
pshriwise opened this issue Feb 19, 2022 · 0 comments
Open

Improvement on Overlap Check Tool #797

pshriwise opened this issue Feb 19, 2022 · 0 comments

Comments

@pshriwise
Copy link
Member

pshriwise commented Feb 19, 2022

The overlap check tool currently uses a number of points along triangle edges to detect if a piece of the edge exists in more than one DAGMC volume (IC excluded). The number of points along an edge can be changed as an argument to the program, but there will always be gaps and the number of rays fired by the program increases with the number of points requested.

A more robust way to approach this would be to fire rays along the triangle edge to detect intersections with any volumes that are not the parent volumes of the current surface(s) the edge belongs to. This will check for overlaps along the entire edge and the number of rays fired by the program will now be fixed based on the number of triangle edges. To make sure an intersection isn't ignored due to triangle normals we'll either have to fire two rays (one traveling in each direction of the edge) or specify the orientation of desired intersections to the ray tracing kernel -- hopefully the latter to save time.

Note: checking that the triangle vertices are not in another volume via the point containment check is still important to detect fully embedded volumes.

@pshriwise pshriwise changed the title O Improvement on Overlap Check Tool Feb 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant