This is the development repository for the USGS MODFLOW 6 Hydrologic Model. The official USGS distribution is available at USGS Release Page.
This repository contains branches of ongoing MODFLOW 6 development. The two main branches in this repository are:
master: the state of the MODFLOW 6 repository corresponding to the last official USGS releasedevelop: the current development version of the MODFLOW 6 program
The develop branch is under active and frequent updates by the MODFLOW development team and other interested contributors. We follow a fork and pull request workflow and require that pull requests pass our test suite before they are considered a possible candidate to merge into develop. The master branch is only updated immediately prior to each new release.
This repository may contain other branches with various levels of development code; however, these branches may be merged into develop or deleted without notice.
This repository's develop branch often contains bug fixes and new features that are not yet part of the official USGS release. Binaries for Linux, macOS and Windows are built from the develop branch and posted to the MODFLOW-USGS/modflow6-nightly-build repository each night. The updated user guide mf6io.pdf is also included, as well as the code.json metadata file.
Software distributions for the current and previous official USGS releases are available here. The current release is also available here from the USGS.
MODFLOW 6 has an extensive suite of example problems that are constructed using the python FloPy package. These example problems are contained in a separate git repository located here. These examples are included in the official USGS MODFLOW 6 distribution, and they are also rendered into online descriptions and jupyter notebooks.
First, follow DEVELOPER.md in order to set up your development environment to build and test MODFLOW 6. The contribution workflow is described in CONTRIBUTING.md.
This repository contains an ./autotest folder with python scripts for building and testing the MODFLOW 6 program and other workflow tasks. The testing workflow relies heavily on several related repositories including:
- modflowpy/pymake
- modflowpy/flopy
- MODFLOW-USGS/modflow6-examples
- MODFLOW-USGS/modflow6-testmodels
- MODFLOW-USGS/modflow6-largetestmodels
- MODFLOW-USGS/executables
- MODFLOW-USGS/modflow-devtools
- Deltares/xmipy
Documentation for the code on the develop branch is automatically developed using Doxygen as part of the MODFLOW 6 Continuous Integration/Continuous Deployment process. Code documentation is available from the GitHub Pages for this repository.
All new MODFLOW 6 functionality in the develop branch can be used directly with flopy; however, the installed version of flopy may need to be updated in order to become aware of new MODFLOW 6 changes. All MODFLOW 6 input is described using "definition files," which are located in the MODFLOW 6 repository under ./doc/mf6io/mf6ivar/dfn. These definition files may be updated on the develop branch as input changes to accommodate new options. The python script ./autotest/update_flopy.py can be run to automatically update the installed version of flopy to work with the develop version of MODFLOW 6. As a note of caution, be aware that running the update_flopy.py script will change the installed version of flopy, which could adversely affect existing MODFLOW 6 flopy scripts.
Instructions for building definition files for new packages are summarized in doc/mf6io/mf6ivar/readme.md.
MODFLOW is a popular open-source groundwater flow model distributed by the U.S. Geological Survey. For 30 years, the MODFLOW program has been widely used by academic researchers, private consultants, and government scientists to accurately, reliably, and efficiently simulate groundwater flow. With time, growing interest in surface and groundwater interactions, local refinement with nested and unstructured grids, karst groundwater flow, solute transport, and saltwater intrusion, has led to the development of numerous MODFLOW versions. Although these MODFLOW versions are often based on the core version (presently MODFLOW-2005), there are often incompatibilities that restrict their use with one another. In many cases, development of these alternative versions has been challenging due to the underlying MODFLOW structure, which was designed for the simulation with a single groundwater flow model using a rectilinear grid.
MODFLOW 6 is the latest core version of MODFLOW. It synthesizes many of the capabilities available in MODFLOW-2005, MODFLOW-NWT, and MODFLOW-LGR. MODFLOW 6 was built on a new object-oriented framework that allows new packages and models to be added, and allows any number of models to be run simultaneously in a single simulation. Model may be coupled sequentially, such as for flow and transport, or the models may be tightly coupled at the matrix level, such as for multiple flow models. MODFLOW 6 presently contains two types of hydrologic models, the Groundwater Flow (GWF) Model and the Groundwater Transport (GWT) Model.
The Groundwater Flow (GWF) Model was the first model to be released in MODFLOW 6. It supports regular MODFLOW grids consisting of layers, rows, and columns, but it also supports more flexible grids that may conform to irregular boundaries or have increased resolution in areas of interest. The GWF Model consists of the original MODFLOW stress packages (CHD, WEL, DRN, RIV, GHB, RCH, and EVT) and four advanced stress packages (MAW, SFR, LAK, and UZF), which have been distilled from their predecessors to contain the most commonly used capabilities. MODFLOW 6 contains a new Water Mover (MVR) Package that can transfer water from provider packages to receiver packages. Providers can be many of the stress and advanced stress packages; receivers can be any of the advanced stress packages. This new capability makes it possible to route water between lakes and streams, route rejected infiltration into a nearby stream, or augment lakes using groundwater pumped from wells, for example. To modernize user interaction with the program, the MODFLOW 6 input structure was redesigned. Within package input files, information is divided into blocks, and informative keywords are used to label numeric data and activate options. This new input structure was designed to make it easier for users to adjust simulation options in an intuitive manner, reduce user input errors, and allow new capabilities to be added without causing problems with backward compatibility.
The GWT model for MODFLOW 6 simulates three-dimensional transport of a single solute species in flowing groundwater. The GWT Model solves the solute transport equation using numerical methods and a generalized CVFD approach, which can be used with regular MODFLOW grids or with unstructured grids. The GWT Model is designed to work with most of the new capabilities released with the GWF Model, including the Newton flow formulation, unstructured grids, advanced packages, and the movement of water between packages. The GWF and GWT Models operate simultaneously during a MODFLOW 6 simulation to represent coupled groundwater flow and solute transport. The GWT Model can also run separately from a GWF Model by reading the heads and flows saved by a previously run GWF Model. The GWT model is also capable of working with the flows from another groundwater flow model, as long as the flows from that model can be written in the correct form to flow and head files.
The following is the general citation for the MODFLOW 6 software.
Citations for specific versions are included with the releases.
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.