[ENH/WIP] Adding first test to implement marching cubes

[Leguark]

Description

Implementing marching cubes

Relates to

Checklist

• My code uses type hinting for function and method arguments and return values.
• I have created tests which cover my code.
• 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.

[Leguark]

• [WIP] Adding masking to marching cubes #1006
• [FEATURE] Add mesh extraction module using marching cubes algorithm #1005
• [ENH/WIP] Adding first test to implement marching cubes #1000 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Leguark]

To keep working in this PR you just need to checkout this branch and push the changes

Step I: Monolithic code extracting meshes

@javoha as far I understood you pretty much have this code. Just add it in the test so we can later extract the functions that we will need to put somewhere else and find out the data structures that we will need

Step II: Extracting functions and data classes and place them in the right location @Leguark

[javoha]

Hi,
so I added the MC code to the test. It is probably more convoluted that it needds to be because I did a bunch of things to account for multiple elements in single structural groups (using the same scalar fields) and also some code to reorder to match the structural frame order.

[Leguark]

great thanks. I will take a look at simplifying it as I extract code into functions and put it in the right location. I will try to come around this week.

[Leguark]

Merge activity

• Mar 23, 4:11 AM EDT: A user started a stack merge that includes this pull request via Graphite.
• Mar 23, 4:11 AM EDT: A user merged this pull request with Graphite.