Issue with Mover Package Implementation in FloPy: Model Error and Manual Fix Required #2313
Replies: 2 comments 1 reply
-
I'm collaborating with @YozeGholami on the same project. To clarify, we have divided the entire lake into two separate parts (i.e., lak1 and lak2), each with a defined outlet. We're using the Mover package to transfer water from the lak1 outlet to lak2. This approach aims to simulate the real hydrological process of the entire lake, where the stage difference between the two parts of the lake is approximately 0.8 meters. Any suggestions are welcome on whether this approach is adaptable or if more reliable methods exist. |
Beta Was this translation helpful? Give feedback.
-
I think you may have to add |
Beta Was this translation helpful? Give feedback.
-
Hi
I am working with a model that contains two lakes, and I want to use the outlet of Lake 1 to flow into Lake 2. To achieve this, I applied the following code for the package data and period data of the Mover package (as shown in Figure 1 in the attachment). This code aligns with FloPy's requirements for defining the Mover package. The code successfully created a recarray for the package data and period data (Figure 2 in the attachment).
I verified this setup in the model's output file (Figure 3 in the attachment), and it matches the specifications of MODFLOW 6 according to the MODFLOW 6 input/output documentation. However, when I ran the model, I encountered an error (Figure 4 in the attachment).
To resolve this issue, I manually modified the input file (Figure 5 in the attachment), after which the model ran successfully. My question is: why did my initial attempt to build the model using FloPy result in an error, and what might have caused the issue with the generated code?
Fig1:
Fig2:
Fig3:
Fig4:
Fig5:
Beta Was this translation helpful? Give feedback.
All reactions