-
Notifications
You must be signed in to change notification settings - Fork 9
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
FILTER: Label Triangle Geometry and Remove Flagged Triangles Filters #842
FILTER: Label Triangle Geometry and Remove Flagged Triangles Filters #842
Conversation
Very quick glance at the code I think the Dynamic List array is going to have issues when Out-of-Core comes around. We cross that bridge when we get there. |
Yea the problem is that it's embedded throughout the geometry APIs, so if we want to remove it. It should really be a separate PR rather than be integrated into this one. |
2431de3
to
c98c094
Compare
c98c094
to
9aa3b33
Compare
9aa3b33
to
2da3f07
Compare
…gacyUUIDMapping.hpp, and 6 more files
* Placeholder update on LabelTriangleGeometryTest using reverse_triangle_winding data instead to ensure that the filter can execute.
Signed-off-by: Michael Jackson <mike.jackson@bluequartz.net>
2da3f07
to
eef4306
Compare
Added an example pipeline, updated the STL_Models archive which broke the combine_stl_models test. Other branches/PRs are going to break during testing until this gets merged. |
Signed-off-by: Michael Jackson <mike.jackson@bluequartz.net>
b772c4a
to
21f084a
Compare
…lueQuartzSoftware#842) Signed-off-by: Michael Jackson <mike.jackson@bluequartz.net> Co-authored-by: Matthew Marine <matthew.marine@bluequartz.net> Co-authored-by: Michael Jackson <mike.jackson@bluequartz.net>
Naming Conventions
Naming of variables should descriptive where needed. Loop Control Variables can use
i
if warranted. Most of these conventions are enforced through the clang-tidy and clang-format configuration files. See the filesimplnx/docs/Code_Style_Guide.md
for a more in depth explanation.Filter Checklist
The help file
simplnx/docs/Porting_Filters.md
has documentation to help you port or write new filters. At the top is a nice checklist of items that should be noted when porting a filter.Unit Testing
The idea of unit testing is to test the filter for proper execution and error handling. How many variations on a unit test each filter needs is entirely dependent on what the filter is doing. Generally, the variations can fall into a few categories:
Code Cleanup