Is your feature request related to a problem? Please describe.
We have nice cleanup methods for boundary condition packages, but not for static packages. This requires users now to come up with their own fixes.
Describe the solution you'd like
From the top of my mind:
DIS/DISV
- Set
idomain cells with thickness == 0 (or smaller than some tolerance limit) from 1 to -1
top needs to be masked with idomain > 0 of the first layer
bottom needs to be masked with a dataset that is shifted across the layer dim, so that underlying active cells still have a top
I'm not entirely sure about 1. and 2., as they can result in confusing results. idomain is normally treated in the codebase as the single source of truth. "Fixing" it is a bit dodgy.
NPF
- Mask all k-values smaller than 0.0
- Mask everything where idomain <= 0
- Enforce
icelltype as integer
I'm not so sure about 3, as it could result potentially in suprising results due to floating point precision errors.
STO
- Mask everything where idomain <= 0
IC
- Fill missing values with a laplace interpolation
- Mask everything where idomain <= 0
Is your feature request related to a problem? Please describe.
We have nice cleanup methods for boundary condition packages, but not for static packages. This requires users now to come up with their own fixes.
Describe the solution you'd like
From the top of my mind:
DIS/DISV
idomaincells with thickness == 0 (or smaller than some tolerance limit) from 1 to -1topneeds to be masked with idomain > 0 of the first layerbottomneeds to be masked with a dataset that is shifted across the layer dim, so that underlying active cells still have a topI'm not entirely sure about 1. and 2., as they can result in confusing results.
idomainis normally treated in the codebase as the single source of truth. "Fixing" it is a bit dodgy.NPF
icelltypeas integerI'm not so sure about 3, as it could result potentially in suprising results due to floating point precision errors.
STO
IC