Go to file
Hughes, J.D ac526a0d6b
refactor(autotests): update build_exe.py to use pymake updates (#484)
update build_exe.py to use pymake updates. Define environments so notebooks 
and scripts are run in a separate environment with python 3.7 to prevent travis 
timeouts.
2019-03-16 10:30:13 -04:00
autotest refactor(autotests): update build_exe.py to use pymake updates (#484) 2019-03-16 10:30:13 -04:00
docs refactor(autotests): update build_exe.py to use pymake updates (#484) 2019-03-16 10:30:13 -04:00
examples refactor(autotests): update build_exe.py to use pymake updates (#484) 2019-03-16 10:30:13 -04:00
flopy refactor(autotests): update build_exe.py to use pymake updates (#484) 2019-03-16 10:30:13 -04:00
.gitignore Clean up of pre-commit hook to reflect changes in README.md. Added a few FAQ notebooks. Update __authors__ in main __init__.py. Commit also closes #338 2018-05-22 16:55:23 -04:00
.travis.yml refactor(autotests): update build_exe.py to use pymake updates (#484) 2019-03-16 10:30:13 -04:00
CODE_OF_CONDUCT.md Updates for code.usgs.gov 2018-05-22 11:30:42 -04:00
CONTRIBUTING.md docs: update documentation (#417) 2018-10-17 08:42:41 -04:00
DISCLAIMER.md refactor(autotests): update build_exe.py to use pymake updates (#484) 2019-03-16 10:30:13 -04:00
LICENSE Initial commit 2014-12-14 11:50:55 -05:00
LICENSE.md Updates for code.usgs.gov 2018-05-22 11:30:42 -04:00
MANIFEST.in Added the definition files to MANIFEST.in. These dfn files need to be explicitly mentioned so that they are included in the installation. 2017-12-17 07:48:37 -05:00
README.md refactor(autotests): update build_exe.py to use pymake updates (#484) 2019-03-16 10:30:13 -04:00
_config.yml Set theme jekyll-theme-minimal 2018-05-22 13:20:51 -04:00
builddistribution.py Modification to builddistribution.py 2015-07-31 12:44:53 -04:00
code.json refactor(autotests): update build_exe.py to use pymake updates (#484) 2019-03-16 10:30:13 -04:00
pre-commit.py fix(typos): Corrected many typos scattered throughout the code (#455) 2019-01-31 11:21:35 -06:00
pre-commit.sh Added pre-commit files 2017-07-12 15:44:05 -04:00
requirements.travis.txt Refactor epsgRef to use JSON file in platform independent location (#422) 2018-10-31 09:29:03 -04:00
requirements27.travis.txt ci(.travis.yml): Drop Python 3.4, add Python 3.7 (#461) 2019-02-28 05:49:57 -05:00
setup.py feat(mf6 plotting/exporting): generalized plotting and exporting code to work both with mf2005 and mf6 (#462) 2019-03-02 07:35:38 -04:00

README.md

flopy3

Version 3.2.10 develop — build 60

Build Status PyPI Version Coverage Status

Introduction

FloPy includes support for MODFLOW 6, MODFLOW-2005, MODFLOW-NWT, MODFLOW-USG, and MODFLOW-2000. Other supported MODFLOW-based models include MODPATH (version 6 and 7 (beta)), MT3DMS, MT3D-USGS, and SEAWAT.

For general modeling issues, please consult a modeling forum, such as the MODFLOW Users Group. Other MODFLOW resources are listed in the MODFLOW Resources section.

Contributing

Bug reports, code contributions, or improvements to the documentation are welcome from the community. Prior to contributing, please read up on our guidelines for contributing and then check out one of our issues in the hotlist: community-help.

Documentation

FloPy code documentation is available at http://modflowpy.github.io/flopydoc/

Getting Started

Frequently asked questions

Tutorials

Additional jupyter Notebook Examples

Python Script Examples

If You Get Stuck

FloPy usage has been growing rapidly, and as the number of users has increased, so has the number of questions about how to use FloPy. We ask our users to carefully consider the nature of their problem and seek help in the appropriate manner.

Questions

For questions related to how to do something with FloPy, we ask our users to submit the question to Stack Overflow and assign the flopy tag. Many of our recent questions have been related to MODFLOW or Python, and the Flopy developers cannot always respond to these inquiries.

Bugs

If you think you have discovered a bug in FloPy in which you feel that the program does not work as intended, then we ask you to submit a Github issue.

FloPy Supported Packages

A list of supported packages in FloPy is available in docs/supported_packages.md on the github repo.

FloPy Model Checks

A table of the supported and proposed model checks implemented in FloPy is available in docs/model_checks.md on the github repo.

FloPy Changes

A summary of changes in each FloPy version is available in docs/version_changes.md on the github repo.

Installation

Python versions:

FloPy requires Python 2.7 or Python 3.3 (or higher)

Dependencies:

FloPy requires NumPy 1.9 (or higher) and enum34 for Python 2.7 or Python 3.3.

For base and Anaconda Python distributions:

To install FloPy type:

pip install flopy

or

conda install -c conda-forge flopy

To update FloPy type:

pip install flopy --upgrade

or

conda update -c conda-forge flopy

To uninstall FloPy type:

pip uninstall flopy

or

conda uninstall flopy

Installing from the git repository:

Current Version of FloPy:

To install the current version of FloPy from the git repository type:

pip install https://github.com/modflowpy/flopy/zipball/master

To update your version of FloPy with the current version from the git repository type:

pip install https://github.com/modflowpy/flopy/zipball/master --upgrade

Development version of FloPy:

To install the latest development version of FloPy from the git repository type:

pip install https://github.com/modflowpy/flopy/zipball/develop

To update your version of FloPy with the latest development version from the git repository type:

pip install https://github.com/modflowpy/flopy/zipball/develop --upgrade

Optional Method Dependencies:

Additional dependencies to use optional FloPy helper methods are listed below.

Method Python Package
.plot() matplotlib >= 1.4
.plot_shapefile() matplotlib >= 1.4 and Pyshp >= 1.2
.to_shapefile() Pyshp >= 1.2
.export(*.shp) Pyshp >= 1.2
.export(*.nc) netcdf4 >= 1.1 and python-dateutil >= 2.4
.export(*.tif) rasterio
.export(*.asc) in flopy.utils.reference SpatialReference class scipy.ndimage
.interpolate() in flopy.utils.reference SpatialReference class scipy.interpolate
.interpolate() in flopy.mf6.utils.reference StructuredSpatialReference class scipy.interpolate
.get_dataframes() in flopy.utils.mflistfile ListBudget class pandas >= 0.15
.get_dataframes() in flopy.utils.observationfile ObsFiles class pandas >= 0.15
.get_dataframes() in flopy.utils.sfroutputfile ModflowSfr2 class pandas >= 0.15
.get_dataframes() in flopy.utils.util_list MfList class pandas >= 0.15
.get_dataframes() in flopy.utils.zonebud ZoneBudget class pandas >= 0.15
.pivot_keyarray() in flopy.mf6.utils.arrayutils AdvancedPackageUtil class pandas >= 0.15
._get_vertices() in flopy.mf6.utils.binaryfile_utils MFOutputRequester class pandas >= 0.15
.get_dataframe() in flopy.mf6.utils.mfobservation Observations class pandas >= 0.15
.df() in flopy.modflow.mfsfr2 SfrFile class pandas >= 0.15
.time_coverage() in flopy.export.metadata acc class - used if available pandas >= 0.15
.loadtxt() in flopy.utils.flopyio - used if available pandas >= 0.15

How to Cite

Citation for FloPy:

Bakker, M., Post, V., Langevin, C. D., Hughes, J. D., White, J. T., Starn, J. J. and Fienen, M. N., 2016, Scripting MODFLOW Model Development Using Python and FloPy: Groundwater, v. 54, p. 733739, doi:10.1111/gwat.12413.

Software/Code citation for FloPy:

Bakker, M., Post, V., Langevin, C.D., Hughes, J.D., White, J.T., Starn, J.J., and Fienen, M.N., 2019, FloPy v3.2.10 — develop: U.S. Geological Survey Software Release, 15 March 2019, http://dx.doi.org/10.5066/F7BK19FH

MODFLOW Resources

Disclaimer

This software is preliminary or provisional and is subject to revision. It is being provided to meet the need for timely best science. The software has not received final approval by the U.S. Geological Survey (USGS). No warranty, expressed or implied, is made by the USGS or the U.S. Government as to the functionality of the software and related material nor shall the fact of release constitute any such warranty. The software is provided on the condition that neither the USGS nor the U.S. Government shall be held liable for any damages resulting from the authorized or unauthorized use of the software.