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

River/Drainage checks while running imod_coupler #185

Open
Huite opened this issue Aug 21, 2023 · 0 comments
Open

River/Drainage checks while running imod_coupler #185

Huite opened this issue Aug 21, 2023 · 0 comments

Comments

@Huite
Copy link
Contributor

Huite commented Aug 21, 2023

Generally, we would want to get the pointer to the river/drainage(/gbh) variables once, then just use them for the rest of the simulation.

However, MODFLOW 6 allows a certain level of dynamism, where the number of the active boundaries may change over time. The maximum number of boundaries is given by MAXBOUND, which determines the amount of memory that is allocated. However, per stress period, the number of boundaries may change, depending on the number of rows in the input. This number is stored in NBOUND.

In general, we do not expect the NBOUND to change over time: the coupler does not support this, because the exchange weights are static. This also means that the NODELIST shouldn't change over time. We could check the NODELIST after every stress period, but this is relatively expensive. A pragmatic change might be to just check the NBOUND variable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant