You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that we've made Storage required because the alternative is worse: if storage is omitted, MF6 automatically assumes steady-state. At least one user made the mistake where they thought they'd made a transient model, but it was running sequential steady-state. Including storage makes everything explicit.
MODFLOW 6 also has explicit time duration and time stamps (as floats), so it's not just xarray requirements for the start and end time.
Fixes#1381
# Description
Upon receiving simulation ``times`` with string "steady-state"
``Well.from_imod5_data`` now assumes the simulation is steady-state and
well rates should be averaged.
This brings well rates of packages a lot closer to what iMOD5 produces
in the water balance for steady-state simulations.
``GroundwaterFlowModel.from_imod5_data`` sets ``times`` arg for
``Well.from_imod5_data`` to ``"steady-state"`` if no Storage package is
present in the projectfile.
I opted for this for now as we currently lack of a clear API to
construct steady-state simulations. See also #1308.
After talks with @tessodk, we concluded that it currently is not so intuitive to define a steady state model MODFLOW6 in iMOD Python, as it:
I think we at least require some example to explain this, and possibly improve our API to ease this.
The text was updated successfully, but these errors were encountered: