Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Defining steady state model not very intuitive. #1308

Open
JoerivanEngelen opened this issue Nov 25, 2024 · 1 comment
Open

Defining steady state model not very intuitive. #1308

JoerivanEngelen opened this issue Nov 25, 2024 · 1 comment
Labels

Comments

@JoerivanEngelen
Copy link
Contributor

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:

  • Still requires you to define a Storage package, where transient is set to false
  • Still requires you to define a time discretization, with a start and end moment

I think we at least require some example to explain this, and possibly improve our API to ease this.

@Huite
Copy link
Contributor

Huite commented Nov 25, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 📯 New
Development

No branches or pull requests

2 participants