You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this is an issue or if I might be missing something, but I'm having trouble turning off a stress package (GHB in this case).
The mf6 input/output manual states:
To turnoff all of the stresses for a stress period, a PERIOD block must be specified with no entries.
I tried doing that with flopy, but the following code creates a GHB package with a None entry in the period block for Period 6. This causes an error when MF6 encounters that None entry. My model is actually a variable density model with salinity, hence the concentration variable.
I've been able to establish that this does not happen when the auxiliary variable is not added. In that case the period block for stress period 6 is empty.
I also tried entering an empty rec-array, but that still yields a period block with a "None" entry:
@dbrakenhoff Confirm that this is a problem. I have a fix though I am going to run a few more tests to verify that it fixes all cases before I submit a PR tomorrow morning. If you want the fix now it is in the mfdatalist.py file on my fork here:
Not sure if this is an issue or if I might be missing something, but I'm having trouble turning off a stress package (GHB in this case).
The mf6 input/output manual states:
I tried doing that with flopy, but the following code creates a GHB package with a None entry in the period block for Period 6. This causes an error when MF6 encounters that None entry. My model is actually a variable density model with salinity, hence the concentration variable.
I've been able to establish that this does not happen when the auxiliary variable is not added. In that case the period block for stress period 6 is empty.
I also tried entering an empty rec-array, but that still yields a period block with a "None" entry:
Thanks in advance for taking a look!
The text was updated successfully, but these errors were encountered: