-
Notifications
You must be signed in to change notification settings - Fork 318
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.
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
MXUZCON is no longer a part of UZT input #423
Comments
jdhughes-usgs
pushed a commit
that referenced
this issue
Oct 30, 2018
* 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
PR #425 fixed this |
langevin-usgs
pushed a commit
that referenced
this issue
Mar 18, 2019
* 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
MXUZCON was included in the early MT3D-USGS development, about the time when the UZT class was being developed for flopy, but it didn't make the final cut in the published MT3D-USGS code and needs to be removed from the class.
The text was updated successfully, but these errors were encountered: