Deltares / Deltares/imod-python
Investigate what to do with boundary conditions with varying layers over time
Open
Nobody has claimed this yet.
performance
- Dominant language
- Python
- Stars
- 41
- Forks
- 12
- Avg merge
- 21h 8m
- Merged PRs (30d)
- 1
Description
Boundary conditions defined in a projectfile can have varying layers over time. That's why parser now allocates all layers for a river package. Perhaps, this can be made more performant.
Contributor guide
No contributing guide indexed for this repository
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 examining the projectfile parser and the river package handling mentioned in the issue, focusing on why it allocates all layers when boundary-condition layers vary over time. Determine the appropriate behavior and measure whether avoiding unnecessary allocation improves performance; done means a decided, validated approach with relevant coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100