[BUG] Outliers in gempy v3

[javoha]

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.
• 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.

[graphite-app]

Graphite Automations

"Add gempy label" took an action on this PR • (03/26/25)

1 label was added to this PR based on Miguel de la Varga's automation.

[AlexanderJuestel]

Yeah, I have noticed that issue as well. Had some additional lith ids there suddenly

[javoha]

Yeah, I have noticed that issue as well. Had some additional lith ids there suddenly

Hi @AlexanderJuestel, just to make sure - did you encounter completely new IDs? So far I have only seen existing elements out of place (like in the screenshot above).

[AlexanderJuestel]

I have actually encountered new IDs

[Leguark]

Thanks for opening this. This makes so much easier to chase these things. For now I mark it as draft since it is not meant to be reviewed.