Skip to content

Commit bb4a89a

Browse files
docs(release): minor clarifications in release notes (#1842)
1 parent a178bb1 commit bb4a89a

File tree

2 files changed

+9
-6
lines changed

2 files changed

+9
-6
lines changed

doc/ReleaseNotes/ReleaseNotes.tex

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -228,14 +228,17 @@ \section{Known Issues and Incompatibilities}
228228
\item
229229
If a GWF-GWF Exchange is active, then neither of the connected GWF Models can have an active Viscosity (VSC) Package.
230230

231+
\item
232+
If a GWT-GWT Exchange is active, then constant concentration conditions cannot be assigned on the interface between the two connected models.
233+
231234
\end{enumerate}
232235

233236
In addition to the issues shown here, a comprehensive and up-to-date list is available under the issues tab at \url{https://github.com/MODFLOW-USGS/modflow6}.
234237

235238

236239
% -------------------------------------------------
237240
\section{Distribution File}
238-
The distribution is provided in the form of a compressed zip file. Distributions are available for several different operating systems, including Windows, Mac, and Linux. Distributions are marked with an operating system tag, called ``ostag''. Values for ``ostag'' include ``win64'', ``mac'', and ``linux'', for example. Distribution files for this release are labeled as \texttt{\modflowversion\_[ostag].zip}. Thus, the distribution file for Windows for this release is \texttt{\modflowversion\_win64.zip}.
241+
The MODFLOW~6 distribution is provided in the form of a compressed zip file. Distributions are available for several different operating systems, including Windows, Mac, and Linux. Distributions are marked with an operating system tag, called ``ostag''. Values for ``ostag'' include ``win64'', ``mac'', and ``linux'', for example. Distribution files for the current release are labeled as \texttt{\modflowversion\_[ostag].zip}. Thus, the distribution file for Windows for the current release is \texttt{\modflowversion\_win64.zip}.
239242

240243
It is recommended that no user files are kept in the release directory. If you do plan to put your own files in the release directory, do so only by creating additional subdirectories.
241244

@@ -245,9 +248,9 @@ \section{Installation and Execution}
245248

246249
To make the executable versions of MODFLOW~6 accessible from any directory, the directory containing the executables should be included in the PATH environment variable. Also, if a prior release of MODFLOW~6 is installed on your system, the directory containing the executables for the prior release should be removed from the PATH environment variable.
247250

248-
As an alternative, the executable file, named ``\texttt{mf6.exe}'' on Windows, in the \modflowversion\_[ostag]/bin directory can be copied into a directory already included in the PATH environment variable.
251+
As an alternative, the executable file (named ``\texttt{mf6.exe}'' on Windows or ``\texttt{mf6}'' on Mac and Linux) in the \modflowversion\_[ostag]/bin directory can be copied into a directory already included in the PATH environment variable.
249252

250-
To run MODFLOW~6, simply type \texttt{mf6} in a terminal window. The current working directory must be set to a location where the model input files are located. Upon execution, MODFLOW~6 will immediately look for file with the name \texttt{mfsim.nam} in the current working directory, and will terminate with an error if it does not find this file.
253+
To run MODFLOW~6, simply type \texttt{mf6} in a terminal window. The current working directory must be set to a location where the model input files are located. Upon execution, MODFLOW~6 will immediately look for a file with the name \texttt{mfsim.nam} in the current working directory, and will terminate with an error if it does not find this file.
251254

252255
% -------------------------------------------------
253256
\section{Compiling MODFLOW~6}

doc/ReleaseNotes/develop.tex

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55

66
\underline{NEW FUNCTIONALITY}
77
\begin{itemize}
8-
\item A new Groundwater Energy (GWE) transport model is introduced to the code base for simulating heat transport in the subsurface. GWE Models can be coupled together using a new GWE-GWE Exchange. Additional information for activating the GWE model type within a MODFLOW 6 simulation is available within the mf6io.pdf document. Technical details about the GWE Model are given in the supplemental technical information document (mf6suptechinfo) provided with the release. New example problems have been developed for testing and demonstrating GWE capabilities (in addition to other internal tests that help verify the accuracy of GWE); however, additional changes to the code and input may be necessary in response to user needs and further testing.
8+
\item A new Groundwater Energy (GWE) transport model was added to simulate heat transport in the subsurface. GWE Models can be coupled together using a new GWE-GWE Exchange. Additional information for activating the GWE model type within a MODFLOW 6 simulation is available within the mf6io.pdf document. Technical details about the GWE Model are given in the supplemental technical information document (mf6suptechinfo) provided with the release. New example problems have been developed for testing and demonstrating GWE capabilities (in addition to other internal tests that help verify the accuracy of GWE); however, additional changes to the code and input may be necessary in response to user needs and further testing.
99
\item A new Particle Tracking (PRT) Model was added to simulate forward tracking of particles for Groundwater Flow (GWF) Models. Additional information for activating the PRT model type within a MODFLOW 6 simulation is available within the mf6io.pdf document. Technical details about the PRT Model are given in the supplemental technical information document (mf6suptechinfo) provided with the release. New example problems have been developed for testing and demonstrating PRT capabilities (in addition to other internal tests that help verify the accuracy of PRT); however, additional changes to the code and input may be necessary in response to user needs and further testing.
1010
\item A new capability has been introduced to optionally write user-provided input arrays to external ASCII files. In some cases, such as when the user provides binary files as input, it can be useful to inspect the text representation of that input. Exporting to external ASCII files can be turned on for supported packages by specifying the EXPORT\_ARRAY\_ASCII option. When activated supported variables will be written to files that are named based on the model, package, variable, and layer. Only those arrays specified for the model grid can be exported.
1111
\item Added capability to vary the hydraulic conductivity of the reach streambed (RHK) by stress period in the Streamflow Routing (SFR) package. RHK can be modified by stress period using the BEDK SFRSETTING. RHK can also be defined using a timeseries string in the PACKAGEDATA or PERIOD blocks.
@@ -15,8 +15,8 @@
1515

1616
\underline{EXAMPLES}
1717
\begin{itemize}
18-
\item New examples were added to demonstrate the new Groundwater Energy (GWE) Model. These examples include: danckwerts, geotherm, gwe-prt, and gwe-radial.
19-
\item New examples were added to demonstrate the new Particle Tracking (PRT) Model. These examples include four of the test problems used to demonstrate MODPATH Version 7.
18+
\item Examples were added to demonstrate the new Groundwater Energy (GWE) Model. These examples include: danckwerts, geotherm, gwe-prt, and gwe-radial.
19+
\item Examples were added to demonstrate the new Particle Tracking (PRT) Model. These examples include two of the test problems used to demonstrate MODPATH Version 7.
2020
\end{itemize}
2121

2222
\textbf{\underline{BUG FIXES AND OTHER CHANGES TO EXISTING FUNCTIONALITY}} \\

0 commit comments

Comments
 (0)