GMS:Output Control

From XMS Wiki
Revision as of 16:47, 20 March 2014 by Jcreer (talk | contribs) (Enable saving of computed flows for all source/sink objects)
Jump to: navigation, search
The MODFLOW Output Control Dialog.

The Output Control dialog is accessed from the MODFLOW menu. The Output Control dialog contains the following options:

Output Interval Options

The Output Interval section lets you choose which files you want to output and when you want to output the results. By default, GMS instructs MODFLOW to output heads and volume data to both data files and text output files. Drawdown is not output by default.

Global Output File

Choose this option to use the global output file (*.glo). This file contains information about the input files and, during an inverse run using the PES process, will contain information about each iteration. Either the global file, list file, or both must be used with MODFLOW.

List Output File

Choose this option to use the list output file (*.out). This file contains information about the current MODFLOW run. This file will be overwritten during an inverse run using the PES process for each inverse iteration.

*.hff File For Transport

Select this option to output the head and flow file (*.hff) used by MT3DMS to generate the flow fields for transport modeling.

Save Arrays Using Binary Files

Choose this option to save all 2D arrays used as MODFLOW input as binary arrays in external files. If this option is not selected, the 2D arrays are written within the respective files in ASCII format. The binary option results in more files, but uses less disk space. There is also a time savings during running for MODFLOW models with large grids.

Enable saving of computed flows for all source/sink objects

This option allows GMS to create a flow observation for all sources/sinks that were created using the Map→MODFLOW command so that the user can see the computed flux through the group of boundary conditions. If the user is doing a transient simulation then having this option may cause MODFLOW to crash because MODFLOW attempts to allocate more memory than any of us have available. Turning off this option in this situation is the best course of action.