feature: Option to Associate Separate IMS Packages for GWF, GWE, GWT models in mfsim.nam #2266
Unanswered
MickeyRush
asked this question in
Q&A
Replies: 1 comment
-
@MickeyRush this can be done with |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The latest MODFLOW release checks for separate IMS packages in GWF-GWE simulations:
ERROR REPORT:
by a different IMS than the GWE model. Furthermore, the IMS specified
for GWF must be listed in mfsim.nam before the IMS for GWE.
As far as I can tell, flopy does not currently have a way to associate separate IMS packages with different models, so the mfsim.nam file ends up like:
BEGIN solutiongroup 1
ims6 ccg_gwf.ims ccg_gwf ccg_gwe
END solutiongroup 1
So far I have been manually editing my mfsim.nam:
BEGIN solutiongroup 1
ims6 ccg_gwf.ims ccg_gwf
ims6 ccg_gwe.ims ccg_gwe
END solutiongroup 1
But it would be nice to have an option in the flopy.mf6.ModflowIms() or flopy.mf6.ModflowGwfgwe() to associate those separate IMS packages with different models. Apologies if it already exists and I missed it.
Beta Was this translation helpful? Give feedback.
All reactions