Skip to content

Commit 67d6a1e

Browse files
authored
doc(mf6io): fix issues in IO guide (#1924)
Fix issues in MF6IO document * resolves #1911 * resolves #1914 * resolves #1915
1 parent f589edf commit 67d6a1e

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

doc/mf6io/gwe/gwe.tex

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
The purpose of the GWE Model is to calculate changes in groundwater temperature in both space and time. Groundwater temperature within an aquifer can change in response to different energy transport processes. These processes include (1) convective (advective) transport of heat with flowing groundwater, (2) the combined hydrodynamic dispersion processes of velocity-dependent mechanical dispersion and conduction (analogous to chemical diffusion), (3) thermal equilibrium with the aquifer matrix, (4) mixing with fluids from groundwater sources and sinks, and (5) direct addition of thermal energy.
44

5-
For GWE, the energy present in the aquifer is assumed to instantaneously equilibrate between the aqueous and solid phase domains. For example, a pulse of heat convecting through an aquifer will be retarded through thermal equilibration with the aquifer material. Conversely, the introduction of cold groundwater into a previously warm region of the aquifer will warmup, at least in part, as energy within the aquifer matrix transfers to the aqueous phase. Unlike GWT, the GWE Model type does not support an immobile domain. The energy that is transferred between the aqeous and solid phases of the groundwater system are tracked in the GWE Model budget.
5+
For GWE, the energy present in the aquifer is assumed to instantaneously equilibrate between the aqueous and solid phase domains. For example, a pulse of heat convecting through an aquifer will be retarded through thermal equilibration with the aquifer material. Conversely, the introduction of cold groundwater into a previously warm region of the aquifer will warm up, at least in part, as energy within the aquifer matrix transfers to the aqueous phase. Unlike GWT, the GWE Model type does not support an immobile domain. The energy that is transferred between the aqeous and solid phases of the groundwater system are tracked in the GWE Model budget.
66

77
This section describes the data files for a \mf Groundwater Energy Transport (GWE) Model. A GWE Model is added to the simulation by including a GWE entry in the MODELS block of the simulation name file. There are three types of spatial discretization approaches that can be used with the GWE Model: DIS, DISV, and DISU. The input instructions for these three packages are not described here in this section on GWE Model input; input instructions for these three packages are described in the section on GWF Model input.
88

doc/mf6io/gwf/ic.tex

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
\vspace{5mm}
44
\subsubsection{Structure of Blocks}
5-
%\lstinputlisting[style=blockdefinition]{./mf6ivar/tex/gwf-ic-options.dat}
5+
\lstinputlisting[style=blockdefinition]{./mf6ivar/tex/gwf-ic-options.dat}
66
\lstinputlisting[style=blockdefinition]{./mf6ivar/tex/gwf-ic-griddata.dat}
77

88
\vspace{5mm}

doc/mf6io/gwf/info_existing_users.tex

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@
7676

7777
\item The CHD Package contains new flexibility. Cells can transition between constant-head cells and active cells during the simulation. This was not allowed in previous MODFLOW versions. Also, the CHD Packages no longer performs linear interpolation between a starting (shead) and ending head (ehead). Only a single head value is provided for each constant-head cell. The capability to linearly interpolate a head value for each time step within a stress period is available through the use of time series.
7878

79-
\item There are two different forms of input for the RCH and EVT Packages: array-based input and list-based input. For models that use DIS Package, the RCH and EVT input can be provided as arrays, which is consistent with previous MODFLOW versions. To use array input, the user must specify the READASARRAYS keyword in the options block. The READASARRAYS option can also be used for models that use the DISV Package. If the READASARRAYS option is not specified, then input to the RCH and EVT Packages is provided in list form. List-based input is the only option supported when the DISU Package is used.
79+
\item There are two different forms of input for the RCH, EVT, SPC, and SPT Packages: array-based input and list-based input. For models that use DIS Package, input for these packages can be provided as arrays, which is consistent with previous MODFLOW versions. To use array input, the user must specify the READASARRAYS keyword in the options block. The READASARRAYS option can also be used for models that use the DISV Package. If the READASARRAYS option is not specified, then input to the aforementioned packages is provided in list form. List-based input is the only option supported when the DISU Package is used.
8080

8181
List-based input offers several advantages over the array-based input for specifying recharge and evapotranspiration. First, multiple list entries can be specified for a single cell. This makes it possible to divide a cell into multiple areas, and assign a different recharge or evapotranspiration rate for each area (perhaps based on land use or some other criteria). In this case, the user would likely specify an auxiliary variable to serve as a multiplier. This multiplier would be calculated by the user and provided in the input file as the fractional cell are for the individual recharge entries. Another advantage to using list-based input for specifying recharge is that ``boundnames'' can be specified. Boundnames work with the Observations capability and can be used to sum recharge or evapotranspiration rates for entries with the same boundname. A disadvantage of the list-based input is that one cannot easily assign recharge or evapotranspiration rates to the entire model without specifying a list of model cells. For this reason \mf also supports array-based input.
8282

0 commit comments

Comments
 (0)