GMS:MODFLOW Post-Processing Viewing Options: Difference between revisions
From XMS Wiki
Jump to navigationJump to search
No edit summary |
(typo) |
||
| (19 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{MODFLOW Links}} | {{MODFLOW Links}} | ||
In addition to generating and editing the MODFLOW input files, GMS can also be used for post-processing the solution files computed by MODFLOW. The solution files computed by MODFLOW include head, drawdown, and CCF files. By default, the head and CCF files are automatically generated. The output options are controlled in the MODFLOW [[GMS:Output Control|''Output Control'' dialog]]. | In addition to generating and editing the MODFLOW input files, GMS can also be used for post-processing the solution files computed by MODFLOW. The solution files computed by MODFLOW include head, drawdown, and CCF (Cell-to-Cell Flow) files. By default, the head and CCF files are automatically generated. The output options are controlled in the MODFLOW [[GMS:Output Control|''Output Control'' dialog]]. | ||
==No-Flow and Dry Cells== | ==No-Flow and Dry Cells== | ||
| Line 6: | Line 6: | ||
When a MODFLOW simulation is solved, MODFLOW writes out a head or drawdown value for every cell of the finite difference grid to the solution files. However, some of the cells are either outside the problem domain or they have gone dry during the course of the simulation. These cells are flagged by MODFLOW in the output file by writing special values for the cells. The value assigned to inactive cells is the No flow head value specified in the [[GMS:Global Options/Basic Package|''Global Options/Basic Package'' dialog]]. The value assigned to cells which have gone dry is the Head assigned to dry cells value defined in the [[GMS:BCF Package|BCF]], [[GMS:LPF Package|LPF]] or [[GMS:HUF Package|HUF]] package dialogs. If the MODFLOW data are in memory when the solution is read in, GMS will automatically use the No flow head and Head assigned to dry cells values to define active/inactive cells for post-processing. | When a MODFLOW simulation is solved, MODFLOW writes out a head or drawdown value for every cell of the finite difference grid to the solution files. However, some of the cells are either outside the problem domain or they have gone dry during the course of the simulation. These cells are flagged by MODFLOW in the output file by writing special values for the cells. The value assigned to inactive cells is the No flow head value specified in the [[GMS:Global Options/Basic Package|''Global Options/Basic Package'' dialog]]. The value assigned to cells which have gone dry is the Head assigned to dry cells value defined in the [[GMS:BCF Package|BCF]], [[GMS:LPF Package|LPF]] or [[GMS:HUF Package|HUF]] package dialogs. If the MODFLOW data are in memory when the solution is read in, GMS will automatically use the No flow head and Head assigned to dry cells values to define active/inactive cells for post-processing. | ||
===Cell Summary Text File=== | ===Cell Summary Text File=== | ||
When a MODFLOW solution is imported into GMS there is an option to generate a "cell summary" text file. This file lists the time, stress period, time step and the number of active, inactive, dry and flooded cells. Two examples are shown below. | When a MODFLOW solution is imported into GMS there is an [[GMS:Preferences#MODFLOW|option]] to generate a "cell summary" text file. This file lists the time, stress period, time step and the number of active, inactive, dry and flooded cells. If the file exists then it will be added to the MODFLOW solution in the Project Explorer and the file can be opened in a text editor from GMS. The file is in *.csv format so that spreadsheet programs can easily read and format the file into columns. Two examples are shown below. | ||
Example 1 | '''Example 1'''<br> | ||
Time, SP, TS, Active, Inactive, Dry, Flooded | Time, SP, TS, Active, Inactive, Dry, Flooded | ||
0.0, 1, 1, 10642, 4463, 1, 0 | 0.0, 1, 1, 10642, 4463, 1, 0 | ||
0.0264713484794, 2, 1, 10642, 4463, 1, 0 | 0.0264713484794, 2, 1, 10642, 4463, 1, 0 | ||
0.0661783739924, 2, 2, 10642, 4463, 1, 0 | 0.0661783739924, 2, 2, 10642, 4463, 1, 0 | ||
0.1257389187813, 2, 3, 10642, 4463, 1 | 0.1257389187813, 2, 3, 10642, 4463, 1, 0 | ||
'''Example 2'''<br> | |||
Date/Time, Time, SP, TS, Active, Inactive, Dry, Flooded | |||
11/16/1985 12:00:00 AM, 46.0, 1, 1, 4831, 1329, 0, 1431 | |||
1/1/1986 12:00:00 AM, 92.0, 1, 2, 4831, 1329, 0, 1431 | |||
3/1/1986 12:00:00 AM, 151.0, 2, 1, 4831, 1329, 0, 0 | |||
3/8/1986 3:00:00 PM, 158.625, 3, 1, 4831, 1329, 0, 0 | |||
The active cells include all cells with an IBOUND value not equal to 0 and cells that have had the IBOUND change to nonzero during the model run (this can occur if the rewetting option is used in the flow package). The inactive cells include cells with IBOUND=0 as well as cells that are set to IBOUND=0 while the simulation was running (Some versions of MODFLOW will do this to dry cells; MODFLOW-NWT does not inactivate dry cells). The dry cells include cells that have the value of HDRY assigned to them or cells where the head is below the bottom elevation of the cell (Note with MODFLOW-NWT a dry cell can still be active.). The flooded cells include cells where (1) the head is above the top elevation of the cell, (2) the cell is not in a layer with a confined layer type defined in the flow package, and (3) the cell is the highest active cell in the vertical column of cells. | The active cells include all cells with an IBOUND value not equal to 0 and cells that have had the IBOUND change to nonzero during the model run (this can occur if the rewetting option is used in the flow package). The inactive cells include cells with IBOUND=0 as well as cells that are set to IBOUND=0 while the simulation was running (Some versions of MODFLOW will do this to dry cells; MODFLOW-NWT does not inactivate dry cells). The dry cells include cells that have the value of HDRY assigned to them or cells where the head is below the bottom elevation of the cell (Note with MODFLOW-NWT a dry cell can still be active.). The flooded cells include cells where (1) the head is above the top elevation of the cell, (2) the cell is not in a layer with a confined layer type defined in the flow package, and (3) the cell is the highest active cell in the vertical column of cells. | ||
==Layer Contours== | ==Layer Contours== | ||
In most cases, the best way to display computed head and drawdown is with layer contours. Layer contours are generated by selecting the '' | In most cases, the best way to display computed head and drawdown is with layer contours. Layer contours are generated by selecting the ''Contours'' option in the ''3D Grid'' tab of the ''Display Options'' dialog. This option is automatically turned on whenever a MODFLOW solution is read into GMS. The '''Mini-Grid Toolbar''', which is part of the [[GMS:Toolbars|Tool Palettes]], can be used to switch between layers. | ||
==Viewing Computed Fluxes== | ==Viewing Computed Fluxes== | ||
| Line 41: | Line 38: | ||
=====Calibration Targets and Statistics===== | =====Calibration Targets and Statistics===== | ||
For objects with an observed flow, a [[GMS:Calibration Targets| | For objects with an observed flow, a [[GMS:Calibration Targets|calibration target]] can be plotted on the object. The calibration target provides a graphical representation of the calibration error. Calibration targets are described in section 14.5. The display of flow calibration targets is turned on by selecting the '''Display Options''' command in the ''Feature Objects'' menu when the local source/sink coverage is the active coverage. | ||
=====Flow Budget for Selected Cells===== | =====Flow Budget for Selected Cells===== | ||
| Line 51: | Line 48: | ||
If a CCF file has been imported as described above, a vector plot can be generated to illustrate the flow field computed by MODFLOW. The CCF file contains flows through each of the cell walls in the grid, i.e., the flow from each cell to each of its six surrounding cells. | If a CCF file has been imported as described above, a vector plot can be generated to illustrate the flow field computed by MODFLOW. The CCF file contains flows through each of the cell walls in the grid, i.e., the flow from each cell to each of its six surrounding cells. | ||
Vectors are generated by right-clicking on the CCF file in the Project Explorer and selecting the '''CCF→Velocity Vectors''' command. The cell top and bottom elevations as well as the porosity are used when calculating the velocity vectors. Therefore, for GMS to compute the vectors, a MODFLOW simulation must exist in GMS. Although porosity is not an input to a MODFLOW model, the porosity can be specified per cell, using the cell properties dialog, whenever a MODFLOW simulation exists. | Vectors are generated by right-clicking on the CCF file [[File:CCF Dataset Active.svg|16 px]] in the Project Explorer and selecting the '''CCF→Velocity Vectors''' command. The cell top and bottom elevations as well as the porosity are used when calculating the velocity vectors. Therefore, for GMS to compute the vectors, a MODFLOW simulation must exist in GMS. Although porosity is not an input to a MODFLOW model, the porosity can be specified per cell, using the cell properties dialog, whenever a MODFLOW simulation exists. | ||
The vectors are computed by reading the CCF file to get the net flow through each grid cell face. Each component of the velocity vector is computed by dividing the flow through the cell face by the saturated area of the face multiplied by the porosity. For example, the I, J, K direction components of the vector are calculated as follows: | The vectors are computed by reading the CCF file to get the net flow through each grid cell face. Each component of the velocity vector is computed by dividing the flow through the cell face by the saturated area of the face multiplied by the porosity. For example, the ''I'', ''J'', ''K'' direction components of the vector are calculated as follows: | ||
<!--*<math> vector_{i} = \dfrac { flow_{i} }{ (saturated_{Area_{i}}) (porosity) } </math> | <!--*<math> vector_{i} = \dfrac { flow_{i} }{ (saturated_{Area_{i}}) (porosity) } </math> | ||
*<math> vector_{j} = \dfrac { flow_{j} }{ (saturated_{Area_{j}}) (porosity) } </math> | *<math> vector_{j} = \dfrac { flow_{j} }{ (saturated_{Area_{j}}) (porosity) } </math> | ||
| Line 72: | Line 69: | ||
'''Prior to version 8.2.''' | '''Prior to version 8.2.''' | ||
To generate a vector dataset from the CCF file, right-click on the CCF dataset in the | To generate a vector dataset from the CCF file, right-click on the CCF dataset [[File:CCF Dataset Active.svg|16 px]] in the Project Explorer and select the '''Generate vectors''' command from the pop up menu. A flow vector is generated at each cell center by computing a vector sum of the flows through the six walls of the cell. The resulting vectors can be plotted by selecting the [[GMS:Vectors|''Vectors'']] option in the [[GMS:3D Grid Module|''3D Grid Display'' Options]] dialog. | ||
==Viewing the Printed Output File== | ==Viewing the Printed Output File== | ||
Two types of output are produced by MODFLOW: a printed output file and a set of solution files (head, drawdown, CCF). Before reading in the solution files, it is often useful to examine the printed output file. In some cases, MODFLOW may crash or not complete its run successfully. Determine if the run was completed successfully by viewing the printed output file. When viewing the file, check to make sure that a solution was output for all stress periods and time steps | Two types of output are produced by MODFLOW: a printed output file and a set of solution files (head, drawdown, CCF). Before reading in the solution files, it is often useful to examine the printed output file. In some cases, MODFLOW may crash or not complete its run successfully. Determine if the run was completed successfully by viewing the printed output file. When viewing the file, check to make sure that a solution was output for all stress periods and time steps that were expected. In some cases MODFLOW will also output to the listing file a description of any problems which may have occurred. | ||
GMS provides two ways to view the text files produced by MODFLOW and the other analysis codes: | GMS provides two ways to view the text files produced by MODFLOW and the other analysis codes: | ||
#When a solution is read into GMS, the text output files are placed into the data tree. Double-clicking on their file icons in the [[GMS:Project Explorer|Project Explorer]] will bring up the text files in a text editor. | #When a solution is read into GMS, the text output files are placed into the data tree. Double-clicking on their file icons [[File:External Text File Icon.svg|14 px]] in the [[GMS:Project Explorer|Project Explorer]] will bring up the text files in a text editor. | ||
#Any text file can be viewed by selecting the '''Edit File''' command in the ''File'' menu. A File Browser appears and the selected file is opened in a text editor. | #Any text file can be viewed by selecting the '''Edit File''' command in the ''File'' menu. A File Browser appears and the selected file is opened in a text editor. | ||
{{Navbox GMS}} | {{Navbox GMS}} | ||
[[Category:MODFLOW]] | [[Category:MODFLOW|Post]] | ||
[[Category:Equations|M]] | [[Category:Equations|M]] | ||
