GMS:Unsupported MODFLOW Features
|Building a MODFLOW Model|
|Map to MODFLOW|
|Packages Supported in GMS|
|Saving a MODFLOW Simulation|
|Importing MODFLOW Files|
|Unsupported MODFLOW Features|
|MODFLOW Display Options|
|MODFLOW Post-Processing Viewing Options|
|Reading a MODFLOW Simulation|
|Flow:||BCF6, HUF, LPF, UPW|
GMS supports all standard MODFLOW versions. For a list of input files and packages supported in each version see here.
- MODFLOW-88 (import only)
- MODFLOW-96 (import only)
- MODFLOW-USG Transport
- MODFLOW 6
The unsupported MODFLOW versions include:
Beginning with GMS 6.5 the following processes are not supported:
- PES (This process is not needed since GMS uses PEST for parameter estimation)
- SEN (This process is not needed since GMS uses PEST for parameter estimation)
- See Packages Supported in GMS. All other packages are unsupported (but we are always working on adding support for more packages). For any package not currently supported in GMS, the file associated with that package will be ignored when the model is imported. However, GMS keeps track of unsupported packages it encounters when reading the name file and, when the project is saved, GMS lists the unsupported packages in the name file and copies the unsupported package files from the old directory to the new directory. Unsupported package files can be edited and removed using the Name File dialog.
The following MODFLOW options are not supported:
- GMS does not support models that use the XSECTION option on line 1 of the BA6 file.
- Quasi-3D confining bed (GMS 6.5.x and before)
- File formats: GMS 6.5.x (and earlier versions) can read most regularly formatted files but MODFLOW supports more formatting options than GMS does. Beginning with version 7.0, MODFLOW is used to import non-GMS MODFLOW simulations (thus, all MODFLOW formats can be imported).
MODFLOW 2000 introduced the concept of parameters as native input to MODFLOW. Starting with version 6.5, GMS no longer writes out native MODFLOW parameters (except when clusters are defined) and the use of the MODFLOW PES process is not available from within GMS. Even when native MODFLOW files are exported from GMS, native MODFLOW parameters are not used (except when clusters are defined) and instead the parameter starting values are written. However, GMS still supports PEST and users may create parameters in the GMS interface as they have been able to do previously. Parameters are created in GMS by assigning a "key" value (usually a negative number) to a MODFLOW input. When MODFLOW is running and calls our external routine to read in the HDF5 a check is made in the data that is read from the HDF5 file. If one of the parameter "key" values is found in the data then the parameter value is substituted into the array or list.
By adopting this approach it was much easier to support transient parameters and very large sets of pilot points.
Also, adopting this approach allows GMS users to use parameters with the BCF package. This feature is not available with the MODFLOW PES process. Other unsupported parameter options:
- HFB, SFR (GMS 7.0.x and before)
- STR, CHD (GMS 6.5.x and before)
- Multiple clusters for array based parameters (GMS 6.5.x and before)
- Parameter Instances (GMS 6.5.x and before)
GMS – Groundwater Modeling System
|Modules:||2D Grid • 2D Mesh • 2D Scatter Point • 3D Grid • 3D Mesh • 3D Scatter Point • Boreholes • GIS • Map • Solid • TINs • UGrids|
|Models:||FEFLOW • FEMWATER • MODAEM • MODFLOW • MODPATH • mod-PATH3DU • MT3DMS • MT3D-USGS • PEST • PHT3D • RT3D • SEAM3D • SEAWAT • SEEP2D • T-PROGS • ZONEBUDGET|