Skip to content

Commit e0d14c6

Browse files
mjrenomjreno
committed
mf6io readarraygrid baseline
1 parent 210ad4f commit e0d14c6

23 files changed

+578
-7
lines changed

‎doc/mf6io/gwf/chd.tex‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,10 @@
11

22
Input to the Constant-Head (CHD) Package is read from the file that has type ``CHD6'' in the Name File. Any number of CHD Packages can be specified for a single groundwater flow model; however, an error will occur if a CHD Package attempts to make a GWF cell a constant-head cell when that cell has already been designated as a constant-head cell either within the present CHD Package or within another CHD Package.
33

4+
Constant-Head input can be specified using lists or arrays. List-based input for the CHD package is the default, and is described here. Instructions for specifying array-based CHD input are described in the next section.
5+
6+
List-based input offers several advantages over the array-based input for specifying constant heads. 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 constant head for each area. 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 area for the individual constant head entries. Another advantage to using list-based input for specifying constant heads is that boundnames can be specified. Boundnames work with the Observations capability and can be used to sum constant heads for entries with the same boundname. A disadvantage of the list-based input is that one cannot easily assign constant heads to the entire model without specifying a list of model cells. For this reason \mf also supports array-based input for constant heads.
7+
48
In previous MODFLOW versions, it was not possible to convert a constant-head cell to an active cell. Once a cell was designated as a constant-head cell, it remained a constant-head cell until the end of the end of the simulation. In \mf a constant-head cell will become active again if it is not included as a constant-head cell in subsequent stress periods.
59

610
Previous MODFLOW versions allowed specification of SHEAD and EHEAD, which were the starting and ending prescribed heads for a stress period. Linear interpolation was used to calculate a value for each time step. In \mf only a single head value can be specified for any constant-head cell in any stress period. The time-series functionality must be used in order to interpolate values to individual time steps.

‎doc/mf6io/gwf/chdg.tex‎

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
2+
Input to the Constant-Head (CHD) Package is read from the file that has type ``CHD6'' in the Name File. Any number of CHD Packages can be specified for a single groundwater flow model; however, an error will occur if a CHD Package attempts to make a GWF cell a constant-head cell when that cell has already been designated as a constant-head cell either within the present CHD Package or within another CHD Package.
3+
4+
Constant-Head Boundary input can be specified using lists or arrays. Array-based input for the CHD package is activated by providing READARRAYGRID within the OPTIONS block. Instructions for specifying list-based constant-head boundaries is described in the previous section. Array-based input for the CHD package differs from the READASARRAYS based input used by the RCH and EVT array-based input packages. READASARRAYS input arrays define a layer of input data for DIS and DISV based model grids, while READARRAYGRID input arrays define data for the entire model grid. Cells that define no data should contain the DNODATA (3.0E+30) value.
5+
6+
When array-based input is used for constant-heads, the DIMENSIONS block is optional. The array size is determined from the model grid when MAXBOUND is not user defined. When defined, the MAXBOUND dimension represents the maxiumum number of defined constant-head (non-DNODATA) cells found in any stress period. Defining MAXBOUND can reduce the memory footprint of the array-based CHD package especially when the number of constant-heads is sparse and the model grid is large.
7+
8+
In previous MODFLOW versions, it was not possible to convert a constant-head cell to an active cell. Once a cell was designated as a constant-head cell, it remained a constant-head cell until the end of the end of the simulation. In \mf a constant-head cell will become active again if it is not included as a constant-head cell in subsequent stress periods.
9+
10+
Previous MODFLOW versions allowed specification of SHEAD and EHEAD, which were the starting and ending prescribed heads for a stress period. Linear interpolation was used to calculate a value for each time step. In \mf only a single head value can be specified for any constant-head cell in any stress period.
11+
12+
\vspace{5mm}
13+
\subsubsection{Structure of Blocks}
14+
\vspace{5mm}
15+
16+
\noindent \textit{FOR EACH SIMULATION}
17+
\lstinputlisting[style=blockdefinition]{./mf6ivar/tex/gwf-chdg-options.dat}
18+
\lstinputlisting[style=blockdefinition]{./mf6ivar/tex/gwf-chdg-dimensions.dat}
19+
\vspace{5mm}
20+
\noindent \textit{FOR ANY STRESS PERIOD}
21+
\lstinputlisting[style=blockdefinition]{./mf6ivar/tex/gwf-chdg-period.dat}
22+
\packageperioddescription
23+
24+
\vspace{5mm}
25+
\subsubsection{Explanation of Variables}
26+
\begin{description}
27+
\input{./mf6ivar/tex/gwf-chdg-desc.tex}
28+
\end{description}
29+
30+
\vspace{5mm}
31+
\subsubsection{Example Input File}
32+
\lstinputlisting[style=inputfile]{./mf6ivar/examples/gwf-chdg-example.dat}
33+
34+
\vspace{5mm}
35+
\subsubsection{Available observation types}
36+
CHD Package observations are limited to the simulated constant head flow rate (\texttt{chd}). The data required for the CHD Package observation type is defined in table~\ref{table:gwf-chdobstype}. Negative and positive values for an observation represent a loss from and gain to the GWF model, respectively.
37+
38+
\begin{longtable}{p{2cm} p{2.75cm} p{2cm} p{1.25cm} p{7cm}}
39+
\caption{Available CHD Package observation types} \tabularnewline
40+
41+
\hline
42+
\hline
43+
\textbf{Model} & \textbf{Observation type} & \textbf{ID} & \textbf{ID2} & \textbf{Description} \\
44+
\hline
45+
\endhead
46+
47+
\hline
48+
\endfoot
49+
50+
\input{../Common/gwf-chdobs.tex}
51+
\label{table:gwf-chdobstype}
52+
\end{longtable}
53+
54+
\vspace{5mm}
55+
\subsubsection{Example Observation Input File}
56+
\lstinputlisting[style=inputfile]{./mf6ivar/examples/gwf-chdg-example-obs.dat}
57+

‎doc/mf6io/gwf/drn.tex‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,9 @@
11
Input to the Drain (DRN) Package is read from the file that has type ``DRN6'' in the Name File. Any number of DRN Packages can be specified for a single groundwater flow model.
22

3+
Drain input can be specified using lists or arrays. List-based input for the DRN package is the default, and is described here. Instructions for specifying array-based DRN input are described in the next section.
4+
5+
List-based input offers several advantages over the array-based input for specifying drains. 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 drain for each area. 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 area for the individual drain entries. Another advantage to using list-based input for specifying drains is that boundnames can be specified. Boundnames work with the Observations capability and can be used to sum drains for entries with the same boundname. A disadvantage of the list-based input is that one cannot easily assign drains to the entire model without specifying a list of model cells. For this reason \mf also supports array-based input for drains.
6+
37
\vspace{5mm}
48
\subsubsection{Structure of Blocks}
59
\vspace{5mm}

‎doc/mf6io/gwf/drng.tex‎

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
Input to the Drain (DRN) Package is read from the file that has type ``DRN6'' in the Name File. Any number of DRN Packages can be specified for a single groundwater flow model.
2+
3+
Drain input can be specified using lists or arrays. Array-based input for the DRN package is activated by providing READARRAYGRID within the OPTIONS block. Instructions for specifying list-based drain input is described in the previous section. Array-based input for the DRN package differs from the READASARRAYS based input used by the RCH and EVT array-based input packages. READASARRAYS input arrays define a layer of input data for DIS and DISV based model grids, while READARRAYGRID input arrays define data for the entire model grid. Cells that define no data should contain the DNODATA (3.0E+30) value.
4+
5+
When array-based input is used for drains, the DIMENSIONS block is optional. The array size is determined from the model grid when MAXBOUND is not user defined. When defined, the MAXBOUND dimension represents the maxiumum number of defined drain (non-DNODATA) cells found in any stress period. Defining MAXBOUND can reduce the memory footprint of the array-based DRN package especially when the number of drains is sparse and the model grid is large.
6+
7+
\vspace{5mm}
8+
\subsubsection{Structure of Blocks}
9+
\vspace{5mm}
10+
11+
\noindent \textit{FOR EACH SIMULATION}
12+
\lstinputlisting[style=blockdefinition]{./mf6ivar/tex/gwf-drng-options.dat}
13+
\lstinputlisting[style=blockdefinition]{./mf6ivar/tex/gwf-drng-dimensions.dat}
14+
\vspace{5mm}
15+
\noindent \textit{FOR ANY STRESS PERIOD}
16+
\lstinputlisting[style=blockdefinition]{./mf6ivar/tex/gwf-drng-period.dat}
17+
\packageperioddescription
18+
19+
\vspace{5mm}
20+
\subsubsection{Explanation of Variables}
21+
\begin{description}
22+
\input{./mf6ivar/tex/gwf-drng-desc.tex}
23+
\end{description}
24+
25+
\vspace{5mm}
26+
\subsubsection{Example Input File}
27+
\lstinputlisting[style=inputfile]{./mf6ivar/examples/gwf-drng-example.dat}
28+
29+
\vspace{5mm}
30+
\subsubsection{Available observation types}
31+
Drain Package observations include the simulated drain rates (\texttt{drn}) and the drain discharge that is available for the MVR package (\texttt{to-mvr}). The data required for each DRN Package observation type is defined in table~\ref{table:gwf-drnobstype}. The sum of \texttt{drn} and \texttt{to-mvr} is equal to the simulated drain discharge rate for a drain boundary or group of drain boundaries.
32+
33+
\begin{longtable}{p{2cm} p{2.75cm} p{2cm} p{1.25cm} p{7cm}}
34+
\caption{Available DRN Package observation types} \tabularnewline
35+
36+
\hline
37+
\hline
38+
\textbf{Model} & \textbf{Observation type} & \textbf{ID} & \textbf{ID2} & \textbf{Description} \\
39+
\hline
40+
\endhead
41+
42+
\hline
43+
\endfoot
44+
45+
DRN & drn & cellid or boundname & -- & Flow between the groundwater system and a drain boundary or group of drain boundaries. \\
46+
DRN & to-mvr & cellid or boundname & -- & Drain boundary discharge that is available for the MVR package for a drain boundary or a group of drain boundaries.
47+
\label{table:gwf-drnobstype}
48+
\end{longtable}
49+
50+
\vspace{5mm}
51+
\subsubsection{Example Observation Input File}
52+
\lstinputlisting[style=inputfile]{./mf6ivar/examples/gwf-drng-example-obs.dat}

‎doc/mf6io/gwf/evt.tex‎

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

33
Evapotranspiration input can be specified using lists or arrays, unless the DISU Package is used. List-based input must be used if discretization is specified using the DISU Package. List-based input for evapotranspiration is the default, and is described here. Instructions for specifying array-based evapotranspiration are described in the next section.
44

5-
List-based input offers several advantages over the array-based input for specifying 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 evapotranspiration rate or extinction depth for each area (perhaps based on vegetation type 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 evapotranspiration entries. Another advantage to using list-based input for specifying evapotranspiration is that boundnames can be specified. Boundnames work with the Observations capability and can be used to sum evapotranspiration rates for entries with the same boundname. A disadvantage of the list-based input is that one cannot easily assign evapotranspiration to the entire model without specifying a list of model cells. For this reason \mf also supports array-based input for evapotranspiration.
5+
List-based input offers several advantages over the array-based input for specifying 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 evapotranspiration rate or extinction depth for each area (perhaps based on vegetation type 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 area for the individual evapotranspiration entries. Another advantage to using list-based input for specifying evapotranspiration is that boundnames can be specified. Boundnames work with the Observations capability and can be used to sum evapotranspiration rates for entries with the same boundname. A disadvantage of the list-based input is that one cannot easily assign evapotranspiration to the entire model without specifying a list of model cells. For this reason \mf also supports array-based input for evapotranspiration.
66

77
ET input is read in list form, as shown in the PERIOD block below. Each line in the PERIOD block defines all input for one cell. Entries following \texttt{cellid}, in order, define the ET surface (\texttt{etss}), maximum ET flux rate (\texttt{etsr}), extinction depth (\texttt{etsx}), all (\texttt{netseg} -- 1) \texttt{pxdp} values, all (\texttt{netseg} -- 1) \texttt{petm} values, all auxiliary variables (if AUXILIARY option is specified), and boundary name (if BOUNDNAMES option is specified).
88

‎doc/mf6io/gwf/ghb.tex‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,9 @@
11
Input to the General-Head Boundary (GHB) Package is read from the file that has type ``GHB6'' in the Name File. Any number of GHB Packages can be specified for a single groundwater flow model.
22

3+
General-Head Boundary input can be specified using lists or arrays. List-based input for the GHB package is the default, and is described here. Instructions for specifying array-based GHB input are described in the next section.
4+
5+
List-based input offers several advantages over the array-based input for specifying general-head boundaries. 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 general-head boundary for each area. 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 area for the individual general-head boundary entries. Another advantage to using list-based input for specifying general-head boundaries is that boundnames can be specified. Boundnames work with the Observations capability and can be used to sum boundary heads for entries with the same boundname. A disadvantage of the list-based input is that one cannot easily assign general-head boundaries to the entire model without specifying a list of model cells. For this reason \mf also supports array-based input for general-head boundaries.
6+
37
\vspace{5mm}
48
\subsubsection{Structure of Blocks}
59
\vspace{5mm}

‎doc/mf6io/gwf/ghbg.tex‎

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
Input to the General-Head Boundary (GHB) Package is read from the file that has type ``GHB6'' in the Name File. Any number of GHB Packages can be specified for a single groundwater flow model.
2+
3+
General-Head Boundary input can be specified using lists or arrays. Array-based input for the GHB package is activated by providing READARRAYGRID within the OPTIONS block. Instructions for specifying list-based general-head boundaries is described in the previous section. Array-based input for the GHB package differs from the READASARRAYS based input used by the RCH and EVT array-based input packages. READASARRAYS input arrays define a layer of input data for DIS and DISV based model grids, while READARRAYGRID input arrays define data for the entire model grid. Cells that define no data should contain the DNODATA (3.0E+30) value.
4+
5+
When array-based input is used for general-head boundaries, the DIMENSIONS block is optional. The array size is determined from the model grid when MAXBOUND is not user defined. When defined, the MAXBOUND dimension represents the maxiumum number of defined general-head boundary (non-DNODATA) cells found in any stress period. Defining MAXBOUND can reduce the memory footprint of the array-based GHB package especially when the number of general-head boundaries is sparse and the model grid is large.
6+
7+
\vspace{5mm}
8+
\subsubsection{Structure of Blocks}
9+
\vspace{5mm}
10+
11+
\noindent \textit{FOR EACH SIMULATION}
12+
\lstinputlisting[style=blockdefinition]{./mf6ivar/tex/gwf-ghbg-options.dat}
13+
\lstinputlisting[style=blockdefinition]{./mf6ivar/tex/gwf-ghbg-dimensions.dat}
14+
\vspace{5mm}
15+
\noindent \textit{FOR ANY STRESS PERIOD}
16+
\lstinputlisting[style=blockdefinition]{./mf6ivar/tex/gwf-ghbg-period.dat}
17+
\packageperioddescription
18+
19+
\vspace{5mm}
20+
\subsubsection{Explanation of Variables}
21+
\begin{description}
22+
\input{./mf6ivar/tex/gwf-ghbg-desc.tex}
23+
\end{description}
24+
25+
\vspace{5mm}
26+
\subsubsection{Example Input File}
27+
\lstinputlisting[style=inputfile]{./mf6ivar/examples/gwf-ghbg-example.dat}
28+
29+
\vspace{5mm}
30+
\subsubsection{Available observation types}
31+
General-Head Boundary Package observations include the simulated general-head boundary flow rates (\texttt{ghb}) and the general-head boundary discharge that is available for the MVR package (\texttt{to-mvr}). The data required for each GHB Package observation type is defined in table~\ref{table:gwf-ghbobstype}. The sum of \texttt{ghb} and \texttt{to-mvr} is equal to the simulated general-head boundary flow rate. Negative and positive values for an observation represent a loss from and gain to the GWF model, respectively.
32+
33+
\begin{longtable}{p{2cm} p{2.75cm} p{2cm} p{1.25cm} p{7cm}}
34+
\caption{Available GHB Package observation types} \tabularnewline
35+
36+
\hline
37+
\hline
38+
\textbf{Stress Package} & \textbf{Observation type} & \textbf{ID} & \textbf{ID2} & \textbf{Description} \\
39+
\hline
40+
\endhead
41+
42+
\hline
43+
\endfoot
44+
45+
\input{../Common/gwf-ghbobs.tex}
46+
\label{table:gwf-ghbobstype}
47+
\end{longtable}
48+
49+
\vspace{5mm}
50+
\subsubsection{Example Observation Input File}
51+
\lstinputlisting[style=inputfile]{./mf6ivar/examples/gwf-ghbg-example-obs.dat}

‎doc/mf6io/gwf/gwf.tex‎

Lines changed: 25 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -112,25 +112,45 @@ \subsection{Viscosity (VSC) Package}
112112
\input{gwf/vsc}
113113

114114
\newpage
115-
\subsection{Constant-Head (CHD) Package}
115+
\subsection{Constant-Head (CHD) Package -- List-Based Input}
116116
\input{gwf/chd}
117117

118118
\newpage
119-
\subsection{Well (WEL) Package}
119+
\subsection{Constant-Head (CHD) Package -- Array-Based Input}
120+
\input{gwf/chdg}
121+
122+
\newpage
123+
\subsection{Well (WEL) Package -- List-Based Input}
120124
\input{gwf/wel}
121125

122126
\newpage
123-
\subsection{Drain (DRN) Package}
127+
\subsection{Well (WEL) Package -- Array-Based Input}
128+
\input{gwf/welg}
129+
130+
\newpage
131+
\subsection{Drain (DRN) Package -- List-Based Input}
124132
\input{gwf/drn}
125133

126134
\newpage
127-
\subsection{River (RIV) Package}
135+
\subsection{Drain (DRN) Package -- Array-Based Input}
136+
\input{gwf/drng}
137+
138+
\newpage
139+
\subsection{River (RIV) Package -- List-Based Input}
128140
\input{gwf/riv}
129141

130142
\newpage
131-
\subsection{General-Head Boundary (GHB) Package}
143+
\subsection{River (RIV) Package -- Array-Based Input}
144+
\input{gwf/rivg}
145+
146+
\newpage
147+
\subsection{General-Head Boundary (GHB) Package -- List-Based Input}
132148
\input{gwf/ghb}
133149

150+
\newpage
151+
\subsection{General-Head Boundary (GHB) Package -- Array-Based Input}
152+
\input{gwf/ghbg}
153+
134154
\newpage
135155
\subsection{Recharge (RCH) Package -- List-Based Input}
136156
\input{gwf/rch}

0 commit comments

Comments
 (0)