Sanity checks of external mesh in building connectivity maps
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 287
- Forks
- 109
- Avg merge
- 4d 41m
- Merged PRs (30d)
- 5
Description
What is the requested feature?
As a user, I cannot have GEOX crashing when the loaded external mesh does not fulfill the GEOSX expectations.
As a user I expect a meaningful error.
The user of GEOSX is typically not the one who generated the mesh and does not know the criteria.
GEOSX dumps the invalid mesh celles/faces/edges/points in a file.
The MeshDoctor is a first step, but the final check must be in the code, when the mesh datastructures are built.
No sanity check is done to protect GEOSX from bad input.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the mesh data-structure construction used when building connectivity maps; the issue does not name a file or test. Determine how invalid external mesh cells, faces, edges, and points should be detected and reported, with completion requiring a meaningful error and dumped invalid elements instead of a crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100