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
The issue is caused by the user-defined package name pname="storm", which raises this error:
gwf.modeltime# AttributeError: modeltime
note that modeltime is a property that is expected to be available.
Changing pname to other values, like pname="strm" allows normal operation. The package name should not influence the behavior of flopy. It seems that flopy might have confused "storm" with an unrelated and unused "sto" package.
Observed with Windows and Linux. Flopy version 3.7.0.dev0 (current development), and with several other older releases back to flopy-3.4.3 (i.e. this isn't new). This not an issue with the mf6 executable.
The text was updated successfully, but these errors were encountered:
* fix(get_package and model_time): #2117, #2118
get_package now allows you to get package only by name or type, instead of always searching for a package both by name and type
model_time displays the correct steady state array and no longer gets confused if packages are named similar to the package type it is searching for
* fix(resolve merge conflict)
---------
Co-authored-by: scottrp <45947939+scottrp@users.noreply.github.com>
A short version of the bug is demonstrated with:
showing the output before and after adding a troubling package name:
The issue is caused by the user-defined package name
pname="storm"
, which raises this error:note that
modeltime
is a property that is expected to be available.Changing
pname
to other values, likepname="strm"
allows normal operation. The package name should not influence the behavior of flopy. It seems that flopy might have confused "storm" with an unrelated and unused "sto" package.Observed with Windows and Linux. Flopy version 3.7.0.dev0 (current development), and with several other older releases back to flopy-3.4.3 (i.e. this isn't new). This not an issue with the mf6 executable.
The text was updated successfully, but these errors were encountered: