Skip to content
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.

Sign up for GitHub

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

Jump to bottom

could not run flopy3_MT3DMS_examples.ipynb #466

Closed
mwtoews opened this issue Feb 28, 2019 · 5 comments
Closed

could not run flopy3_MT3DMS_examples.ipynb #466

mwtoews opened this issue Feb 28, 2019 · 5 comments

Comments

@mwtoews
Copy link
Contributor

mwtoews commented Feb 28, 2019

While running autotest_notebooks.py on Python 3.7, a new issue is found. See traceback starting here:
https://travis-ci.org/modflowpy/flopy/jobs/499596952#L1137
@mwtoews mwtoews mentioned this issue Feb 28, 2019
Merged
@langevin-usgs
Copy link
Contributor

This is an intermittent issue that I haven't been able to figure out. For some reason, flopy is having a hard time reading the concentration file, but only some times. I can reproduce it locally sometimes. Strange.

@jtwhite79
Copy link
Contributor

I've got this problem now too on the feature_drt branch I've been working in with py3.7 and the MT3DMS notebook on travis. I fired up a py37 notebook on ubuntu and can run to completion (using a fresh mt3dms builds with gcc7). It is possible to install a travis docker image but I don't have the bandwidth at the mo. Any thoughts?

@mwtoews
Copy link
Contributor Author

mwtoews commented Mar 5, 2019

This issue has nothing to do with flopy or Python. It's with gfortran-compiled mt3dms; see MODFLOW-USGS/mt3d-usgs#46 for a possible fix.

@emorway-usgs
Copy link
Contributor

@mwtoews offered this pull request on the MT3D-USGS repo which has been adopted in the latest release of MT3D-USGS that is now up on the web. Hopefully the initialization of the velocity array in MT3D-USGS fixes this issue. Does that mean that a new MT3D-USGS executable needs to be stored somewhere for the flopy testing to use?

@emorway-usgs emorway-usgs mentioned this issue Mar 14, 2019
Merged
@mwtoews mwtoews mentioned this issue Mar 14, 2019
Merged
@langevin-usgs
Copy link
Contributor

We'll need to update the path to the distribution file. I'll take a look at it.

langevin-usgs added a commit to langevin-usgs/flopy that referenced this issue Mar 14, 2019
@langevin-usgs
fix(build_exes): update to mt3dusgs1.0.01 and mf6.0.4
3655222 
Also attempt a fix for issue modflowpy#466 by initializing the V variable to zero in the mt3d adv package
@langevin-usgs langevin-usgs mentioned this issue Mar 14, 2019
Merged
langevin-usgs pushed a commit that referenced this issue Mar 18, 2019
@emorway-usgs @langevin-usgs
Fix for UZT test problem (#491)
d1dca80 
* Explicit cast to np.array isn't preserved

* Fixes issue in LAK package _init_ routines when only a single lake is active

* Previous alteration worked for one lake, but didn't handle one stage for multiple lakes.  This should account for that condition

* Fix mis-statement

* LMT: Lacking support for keyword 'ALL' following Package_Flows keyword

* Add precision for variable thkmin

* PERLEN variable getting trucated by use of "G" (general form) when number of significant digits was > 4.

* Switching printing of PERLEN in BTN from 10.6G to 10G

* Fix for issue #402 including a new test for checking mtlkt.py

* Remove apostrophe from comment (interferes with Travis build)

* Rename test, another recent commit had the same name

* Remove argument from call to test

* Adding new example notebook for MT3D-USGS that uses SFT, LKT, and UZT, including connections between them

* Fixed a typo, added link for docs/notebook_examples.md in a reasonable section of the document

* An errant capital letter in the new notebook, switched to lowercase

* Removing variable MXUZCON from mtuzt.py.  Variable was in pre-release versions of MT3D-USGS, but didn't make the final cut and was never removed from flopy until now.  Fixes and closes issue #423

* Indexes needed adjusting after removing un-used variable from Item 2 in UZT input file.

* Fixing another index issue brought about by the removal of MXUZCON

* test(t012_test.py): Account for UZT -> UZT2 input file changes

With the release of MT3D-USGS 1.0.1, required UZT input was reduced

#466 and #482

* test(t012_test.py): Adapt flopy src to new UZT2 input requirements

These changes required witth the release of MT3D-USGS 1.0.1

#466 and #482

* docs(releasenotes): update releasenotes with UZT2 fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mwtoews @jtwhite79 @emorway-usgs @langevin-usgs