Skip to content

Commit c6d00ed

Browse files
mjrenomjreno
committed
clearly distinguish between layer and grid array-based input
1 parent a624461 commit c6d00ed

File tree

8 files changed

+21
-21
lines changed

8 files changed

+21
-21
lines changed

‎doc/mf6io/gwf/chdg.tex‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
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 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.
4+
Constant-Head Boundary input can be specified using lists or grid arrays. Grid 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.
55

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 maximum 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.
6+
When grid array-based input is used for constant-head boundaries, the DIMENSIONS block is optional. The input array size is determined from the model grid. Cells that define no data should contain the DNODATA (3.0E+30) value. When defined, the MAXBOUND dimension represents the maximum number of defined constant-head boundary (non-DNODATA) cells found in any stress period. Defining MAXBOUND can reduce the memory footprint of the grid array-based CHD package, especially when the input grid arrays are sparse and the model grid is large.
77

88
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.
99

‎doc/mf6io/gwf/drng.tex‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
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. 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.
3+
Drain input can be specified using lists or grid arrays. Grid 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.
44

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 maximum 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.
5+
When grid array-based input is used for the drain package, the DIMENSIONS block is optional. The input array size is determined from the model grid. Cells that define no data should contain the DNODATA (3.0E+30) value. When defined, the MAXBOUND dimension represents the maximum number of defined drain (non-DNODATA) cells found in any stress period. Defining MAXBOUND can reduce the memory footprint of the grid array-based DRN package, especially when the input grid arrays are sparse and the model grid is large.
66

77
\vspace{5mm}
88
\subsubsection{Structure of Blocks}

‎doc/mf6io/gwf/evta.tex‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
Input to the Evapotranspiration (EVT) Package is read from the file that has type ``EVT6'' in the Name File. Any number of EVT Packages can be specified for a single groundwater flow model. All single-valued variables are free format.
22

3-
Evapotranspiration input can be specified using lists or arrays. Array-based input for evapotranspiration is activated by providing READASARRAYS within the OPTIONS block. Instructions for specifying list-based evapotranspiration is described in the previous section. Array-based input for evapotranspiration provides a similar approach for providing evapotranspiration rates as previous MODFLOW versions. Array-based input for evapotranspiration can be used only with the DIS and DISV Packages. Array-based input for evapotranspiration cannot be used with the DISU Package.
3+
Evapotranspiration input can be specified using lists or layer arrays. Layer array-based input for evapotranspiration is activated by providing READASARRAYS within the OPTIONS block. Instructions for specifying list-based evapotranspiration is described in the previous section. Layer array-based input for evapotranspiration provides a similar approach for providing evapotranspiration rates as previous MODFLOW versions. Layer array-based input for evapotranspiration can be used only with the DIS and DISV Packages. Layer array-based input for evapotranspiration cannot be used with the DISU Package.
44

5-
When array-based input is used for evapotranspiration, the DIMENSIONS block should not be specified. The array size is determined from the model grid. Segmented evapotranspiration cannot be used with the READASARRAYS option.
5+
When layer array-based input is used for evapotranspiration, the DIMENSIONS block should not be specified. The array size is determined from the model grid. Segmented evapotranspiration cannot be used with the READASARRAYS option.
66

77
\vspace{5mm}
88
\subsubsection{Structure of Blocks}

‎doc/mf6io/gwf/ghbg.tex‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
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. 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.
3+
General-Head Boundary input can be specified using lists or grid arrays. Grid 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.
44

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 maximum 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.
5+
When grid array-based input is used for general-head boundaries, the DIMENSIONS block is optional. The input array size is determined from the model grid. Cells that define no data should contain the DNODATA (3.0E+30) value. When defined, the MAXBOUND dimension represents the maximum number of defined general-head boundary (non-DNODATA) cells found in any stress period. Defining MAXBOUND can reduce the memory footprint of the grid array-based GHB package, especially when the input grid arrays are sparse and the model grid is large.
66

77
\vspace{5mm}
88
\subsubsection{Structure of Blocks}

‎doc/mf6io/gwf/gwf.tex‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -116,55 +116,55 @@ \subsection{Constant-Head (CHD) Package -- List-Based Input}
116116
\input{gwf/chd}
117117

118118
\newpage
119-
\subsection{Constant-Head (CHD) Package -- Array-Based Input}
119+
\subsection{Constant-Head (CHD) Package -- Grid Array-Based Input}
120120
\input{gwf/chdg}
121121

122122
\newpage
123123
\subsection{Well (WEL) Package -- List-Based Input}
124124
\input{gwf/wel}
125125

126126
\newpage
127-
\subsection{Well (WEL) Package -- Array-Based Input}
127+
\subsection{Well (WEL) Package -- Grid Array-Based Input}
128128
\input{gwf/welg}
129129

130130
\newpage
131131
\subsection{Drain (DRN) Package -- List-Based Input}
132132
\input{gwf/drn}
133133

134134
\newpage
135-
\subsection{Drain (DRN) Package -- Array-Based Input}
135+
\subsection{Drain (DRN) Package -- Grid Array-Based Input}
136136
\input{gwf/drng}
137137

138138
\newpage
139139
\subsection{River (RIV) Package -- List-Based Input}
140140
\input{gwf/riv}
141141

142142
\newpage
143-
\subsection{River (RIV) Package -- Array-Based Input}
143+
\subsection{River (RIV) Package -- Grid Array-Based Input}
144144
\input{gwf/rivg}
145145

146146
\newpage
147147
\subsection{General-Head Boundary (GHB) Package -- List-Based Input}
148148
\input{gwf/ghb}
149149

150150
\newpage
151-
\subsection{General-Head Boundary (GHB) Package -- Array-Based Input}
151+
\subsection{General-Head Boundary (GHB) Package -- Grid Array-Based Input}
152152
\input{gwf/ghbg}
153153

154154
\newpage
155155
\subsection{Recharge (RCH) Package -- List-Based Input}
156156
\input{gwf/rch}
157157

158158
\newpage
159-
\subsection{Recharge (RCH) Package -- Array-Based Input}
159+
\subsection{Recharge (RCH) Package -- Layer Array-Based Input}
160160
\input{gwf/rcha}
161161

162162
\newpage
163163
\subsection{Evapotranspiration (EVT) Package -- List-Based Input}
164164
\input{gwf/evt}
165165

166166
\newpage
167-
\subsection{Evapotranspiration (EVT) Package -- Array-Based Input}
167+
\subsection{Evapotranspiration (EVT) Package -- Layer Array-Based Input}
168168
\input{gwf/evta}
169169

170170
\newpage

‎doc/mf6io/gwf/rcha.tex‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11

22
Input to the Recharge (RCH) Package is read from the file that has type ``RCH6'' in the Name File. Any number of RCH Packages can be specified for a single groundwater flow model.
33

4-
Recharge input can be specified using lists or arrays. Array-based input for recharge is activated by providing READASARRAYS within the OPTIONS block. Instructions for specifying list-based recharge is described in the previous section. Array-based input for recharge provides a similar approach for providing recharge rates as previous MODFLOW versions. Array-based input for recharge can be used only with the DIS and DISV Packages. Array-based input for recharge cannot be used with the DISU Package.
4+
Recharge input can be specified using lists or layer arrays. Layer array-based input for recharge is activated by providing READASARRAYS within the OPTIONS block. Instructions for specifying list-based recharge is described in the previous section. Layer array-based input for recharge provides a similar approach for providing recharge rates as previous MODFLOW versions. Layer array-based input for recharge can be used only with the DIS and DISV Packages. Layer array-based input for recharge cannot be used with the DISU Package.
55

6-
When array-based input is used for recharge, the DIMENSIONS block should not be specified. The array size is determined from the model grid.
6+
When layer array-based input is used for recharge, the DIMENSIONS block should not be specified. The array size is determined from the model grid.
77

88
\vspace{5mm}
99
\subsubsection{Structure of Blocks}

‎doc/mf6io/gwf/rivg.tex‎

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

3-
River input can be specified using lists or arrays. Array-based input for the RIV package is activated by providing READARRAYGRID within the OPTIONS block. Instructions for specifying list-based river input is described in the previous section. Array-based input for the RIV 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.
3+
River input can be specified using lists or grid arrays. Grid array-based input for the RIV package is activated by providing READARRAYGRID within the OPTIONS block. Instructions for specifying list-based river input is described in the previous section.
44

5-
When array-based input is used for the river package, 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 maximum number of defined river (non-DNODATA) cells found in any stress period. Defining MAXBOUND can reduce the memory footprint of the array-based RIV package especially when the number of river cells is sparse and the model grid is large.
5+
When grid array-based input is used for the river package, the DIMENSIONS block is optional. The input array size is determined from the model grid. Cells that define no data should contain the DNODATA (3.0E+30) value. When defined, the MAXBOUND dimension represents the maximum number of defined river (non-DNODATA) cells found in any stress period. Defining MAXBOUND can reduce the memory footprint of the grid array-based RIV package, especially when the input grid arrays are sparse and the model grid is large.
66

77
\vspace{5mm}
88
\subsubsection{Structure of Blocks}

‎doc/mf6io/gwf/welg.tex‎

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

3-
Well input can be specified using lists or arrays. Array-based input for the WEL package is activated by providing READARRAYGRID within the OPTIONS block. Instructions for specifying list-based wells is described in the previous section. Array-based input for the WEL 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.
3+
Well input can be specified using lists or grid arrays. Grid array-based input for the WEL package is activated by providing READARRAYGRID within the OPTIONS block. Instructions for specifying list-based well input is described in the previous section.
44

5-
When array-based input is used for wells, 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 maximum number of defined well (non-DNODATA) cells found in any stress period. Defining MAXBOUND can reduce the memory footprint of the array-based WEL package especially when the number of wells is sparse and the model grid is large.
5+
When grid array-based input is used for the well package, the DIMENSIONS block is optional. The input array size is determined from the model grid. Cells that define no data should contain the DNODATA (3.0E+30) value. When defined, the MAXBOUND dimension represents the maximum number of defined well (non-DNODATA) cells found in any stress period. Defining MAXBOUND can reduce the memory footprint of the grid array-based WEL package, especially when the input grid arrays are sparse and the model grid is large.
66

77
\vspace{5mm}
88
\subsubsection{Structure of Blocks}

0 commit comments

Comments
 (0)