Skip to content

Commit

Permalink
update release notes
Browse files Browse the repository at this point in the history
  • Loading branch information
jdhughes-usgs committed Dec 20, 2024
1 parent 8bd4985 commit f5813b1
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 3 deletions.
2 changes: 1 addition & 1 deletion doc/ReleaseNotes/ReleaseNotes.tex
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@


\renewcommand{\cooperator}
{the \textusgs\ Water Availability and Use Science Program}
{Water Availability and Use Science Program}
\renewcommand{\reporttitle}
{MODFLOW~6 Release Notes}
\renewcommand{\coverphoto}{coverimage.jpg}
Expand Down
1 change: 1 addition & 0 deletions doc/ReleaseNotes/develop.tex
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,7 @@
\item The PRT model now allows more control over vertical particle motion in dry conditions. In addition to the existing DRAPE option, which controls release-time behavior, the PRP package now provides a DRY\_TRACKING\_METHOD option which configures how dry particles (particles in dry cells, or above the water table in partially saturated cells) behave at tracking time. This option is relevant only when the Newton formulation is used, in which case dry cells remain active; otherwise, dry cells are inactive and particles will terminate. See the MF6IO document for a detailed explanation of DRY\_TRACKING\_METHOD.
\item The PRT model's Particle Release Point (PRP) package now provides an option EXIT\_SOLVE\_TOLERANCE which configures the tolerance to use when solving for a particle's exit location from a triangular subcell of an unstructured grid cell. This value is only used for the generalized (ternary) tracking method on vertex grids. A value of 0.00001 is set by default. This value works well for many problems, but the value that strikes the best balance between accuracy and runtime is problem-dependent.
\item The PRT model could write duplicative output, in volumes increasing with the current time step, due to a bug in the output file management logic. This bug has been fixed.
\item CSUB package observations that could use BOUNDNAMES was inconsistent with the input and output guide. CSUB package flow observations are the only observations that can use BOUNDNAMES.
\end{itemize}

%\underline{INTERNAL FLOW PACKAGES}
Expand Down
6 changes: 4 additions & 2 deletions doc/mf6io/mf6ivar/examples/gwf-csub-example-obs.dat
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
BEGIN CONTINUOUS FILEOUT my_model.csub.csv
tcomp3 compaction-cell 1 1 7
ibcensystm0 elastic-compaction nsystm0
ibcinsystm0 inelastic-compaction nsystm0
ibcensystm0 elastic-compaction 2
ibcinsystm0 inelastic-compaction 2
ibcensystm0 elastic-csub nsystm0
ibcinsystm0 inelastic-csum nsystm0
END CONTINUOUS

0 comments on commit f5813b1

Please sign in to comment.