Hack integration from real use case
Open
Nobody has claimed this yet.
type: new
- Dominant language
- C++
- Stars
- 287
- Forks
- 109
- Avg merge
- 4d 41m
- Merged PRs (30d)
- 5
Description
Clean integration of hacks:
- solver part
- avoid zero or negative values in the porosity model: add check value lower than a min value set by user / and maybe add a warning
- give access to the user to more hypre configuration values (to be able to optimize/tune solver more precislty the solver)
- outputs:
- https://github.com/GEOS-DEV/GEOS/issues/2636 But the ids of cells from merged ranks are not guaranteed to be consistent over time. How to deal with that ? (use globalToLocalMap as an index ?)
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 reviewing the solver and outputs requirements in this issue, then read linked issue #2636. Clarify how user-configured porosity minimums and additional hypre settings should work, and determine how merged-rank cell IDs can remain usable over time, possibly via globalToLocalMap.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- hpc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100