-
Notifications
You must be signed in to change notification settings - Fork 116
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
EXG only containing MVR with NEXG 0 doesn't work #2025
Labels
Comments
Nice find! This is an interesting edge case that we will definitely further investigate. Will let you know what possible next steps are. Thanks for reporting @tandreasr |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
while further testing the parallel capabilities of MF6 I found another error connected to splitting a model into subdomains.
Please have a look a the following screenshot:
The original model without any exchanges contained a Mover between two MAW wells located in Subdomain 3 (provider) and 10 (receiver) respectively.
When splitting the original model (test020_NT_EI from https://github.com/MODFLOW-USGS/modflow6-testmodels/tree/master/mf6)
into subdomains this mover obviously has to be moved into a new exchange (File exg_3_10.exg)
This exchange does contain the mover only, because no direct borders do exist between subdomain 3 and 10 - therefore NEXG 0.
This leads to the following error (serial and parallel mode):
ERROR REPORT:
My guess is that you haven't had such a case yet? (which in my opinion should be acceptible)
What do you think?
Here is the splitted model producing the error:
_usgs.zip
Best regards
Andreas
The text was updated successfully, but these errors were encountered: