-
-
Notifications
You must be signed in to change notification settings - Fork 262
[ENH] Improve marching cubes mesh extraction with masking support | GEN-12031 #1006
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
Conversation
dc284ad to
901dbed
Compare
|
Hi, I see two problems:
I will take a look and see if I can find the problems. Does it make sense to do this in this pull request now or should I open a new one @Leguark? EDIT: Problem was that the correct sclar values per element were not passed (or stored). I fixed it but put some ToDos because it should probably be done somewhere else. |
|
added it here or in another pr if it is completely independent on the marching cubes code |
I already added a solution for creating the correct MC surfaces. Probably the solution is not in the right place for a final merge, but it does work. I was not able to create the correct mask yet, though I added some ideas and suggestions. |
|
Hi, so I got a working solution now. But I basically did everything "manually" (getting the rigth scalar field values and scalar fields, creating new masks and going through the groups/elements in the right order). @Leguark maybe you can take a look and check where you can simplify and move things for clarity. |
# Description Since the release of gempy v3 we noticed some outliers in the lithology block. These are basically single cells that have a wrong element ID in the lithology block. They generally appear close to surface boundaries and are appearing depending on resolution. This might be caused when mapping sclar field values to int for the lithology block. As I don't think the isse is related to Octrees or DC I opened a new pull request. This issue will cause problems when reintroducing MC as a meshing approach in #1000 and #1006 . For now I added a single example as a test (see screenshot). I will add more examples whe I come across them and have time.  # Checklist - [ ] My code uses type hinting for function and method arguments and return values. - [x] I have created tests which cover my code. - [x] The test code either 1. demonstrates at least one valuable use case (e.g. integration tests) or 2. verifies that outputs are as expected for given inputs (e.g. unit tests). - [ ] New tests pass locally with my changes.



Description
Improved the marching cubes implementation for mesh extraction with proper masking support. The changes include:
Relates to mesh extraction functionality
Checklist
or 2. verifies that outputs are as expected for given inputs (e.g. unit tests).