https://www.xmswiki.com/api.php?action=feedcontributions&user=Dharker&feedformat=atomXMS Wiki - User contributions [en]2024-03-29T07:29:30ZUser contributionsMediaWiki 1.39.0https://www.xmswiki.com/index.php?title=SMS:ADH_SMS_13.2_and_Earlier&diff=122609SMS:ADH SMS 13.2 and Earlier2017-04-25T22:23:36Z<p>Dharker: /* External Links */ Fixed Broken Links</p>
<hr />
<div>"ADH is a state-of-the-art ADaptive Hydraulics Modeling system developed by the [http://adh.usace.army.mil/new_webpage/main/main_page.htm Coastal and Hydraulics Laboratory (CHL), ERDC, USACE], and is capable of handling both saturated and unsaturated groundwater, overland flow, three-dimensional Navier-Stokes flow, and two- or three-dimensional shallow water problems." [https://adh.usace.army.mil/]<br />
<br />
Information about the ADH model can be found at the [https://adh.usace.army.mil/new_webpage/main/main_page.htm ADaptive Hydraulics Modeling HomePage]. <br />
<br />
The ADH model can be added to a [http://www.aquaveo.com/software/sms-pricing paid edition] of SMS.<br />
[[Category:Link to Store]]<br />
<br />
==Graphical Interface== <br />
ADH makes use of a variety of dialog boxes which can be accessed through the ''ADH'' menu.<br />
===ADH Menu===<br />
* [[SMS:ADH Boundary Condition Assignment|Assign BC]] &ndash; When a node or arc is selected, brings up a dialog where boundary condition parameters can be assigned.<br />
* [[SMS:ADH Bed Layers Assignment|Assign Bed Layers]] &ndash; Brings up a dialog to assign bed layer specifications.<br />
* Assign Consolidations<br />
* [[SMS:ADH Material Properties|Material Properties]] &ndash; Brings up a dialog where material properties are defined.<br />
* [[SMS:ADH Hot Start Initial Conditions | Hot Start Initial Conditions]] &ndash; Brings up a dialog to define the initial condition dataset to start a simulation.<br />
* [[SMS:ADH Time Series|Time Series Data]] &ndash; Brings up a ''Time Series'' dialog.<br />
* [[SMS:Model Checker|Model Check]] &ndash; Launches the model check process.<br />
* [[SMS:ADH Model Control | Model Control]] &ndash; Brings up the ''Model Control'' dialog where model run parameters are set.<br />
* [[SMS:ADH Sediment Library Control|Sediment Library Control]] &ndash; Brings up a dialog where sediment properties can be defined.<br />
* [[SMS:ADH Run Model | Run Model]] &ndash; Launches the model check, pre-ADH model wrapper, and ADH model wrapper.<br />
* Read ADH Solution &ndash; Opens ADH solution files.<br />
<br />
[[Category:SMS Menus|A]]<br />
<br />
===Files=== <br />
An ADH simulation is defined using three main files: mesh geometry (*.3dm), boundary conditions (*.bc), and hot start conditions (*.hot). ADH expects a 3-dimensional mesh geometry since it can solve 3D models, but SMS will only interface the 2D capabilities and will therefore only read and write 2D entities in the *.3dm file. A generic SMS mesh geometry file (*.2dm) can be used by ADH if the extension is changed to *.3dm. To facilitate handling the ADH files, SMS creates a simulation file (*.sim) which lists the individual files. Opening the *.sim will load the ADH files in SMS.<br />
<br />
Each file is a card based text file that can be viewed and edited by a text editor (i.e. Notepad). <br />
* [[SMS:2D Mesh Files *.2dm | Mesh geometry file (*.2dm/*.3dm)]] <br />
* [[SMS:ADH Boundary Condition File Cards | Boundary condition file (*.bc)]] <br />
* [[SMS:ADH Hot Start File| Hot start file (*.hot)]] <br />
* [[SMS:ADH Boat Definition File Cards | Boat definition file (*.bt)]]<br />
<br />
==Functionality==<br />
ADH can address a range of modeling application, including:[http://adh.usace.army.mil/new_webpage/main/adh_overview.htm] <br />
*Design of approach channel improvements<br />
*Guardwall porting design<br />
*Design of a fish passage structure through an existing spillway<br />
*Velocity field calculations during different stages of construction<br />
*Overall effects of sedimentation due to the proposed work.<br />
*Evaluating the effects of multiple projects constructed within a river reach to support objectives for both navigation and ecosystem restoration.<br />
*Salinity intrusion analysis in conjunction with system changes.<br />
*Impacts of navigation channel design changes on ship passage by supplying hydrodynamic results.<br />
*Effects of vessel traffic on hydrodynamics, salinity, and sedimentation with the use of simulating vessel movement in the model.<br />
*Flood inundation by use of dynamic and continuous wetting/drying fronts.<br />
<br />
==Using the Model / Practical Notes== <br />
* [[SMS:ADH Sediment Transport and Bed Layers|Sediment Transport and Bed Layers]]<br />
* [[SMS:ADH Time Series|Time Series]]<br />
* [[SMS:ADH Wind Stations|Wind Stations]]<br />
<br />
===ADH String Structures===<br />
ADH uses string structures to assign properties to entities. The following table describes the relation between the string structures and SMS structures.<br />
{|class="wikitable" <br />
|+'''ADH to SMS (Reading)''' <br />
!colspan="2"|ADH String Structure <br />
!width="300"|SMS Structure <br />
|-<br />
|rowspan="2" width="150"|NDS with DB card<br />
|width="150"|and only 1 node ID <br />
|Node with boundary condition (BC) <br />
|-<br />
|and 2 or more node IDs <br />
|Nodestring with BC <br />
|-<br />
|colspan="2"|EGS with NB card (and possibly FLX card) <br />
<br />
|Nodestring with BC (and flux output) <br />
|-<br />
|colspan="2"|MDS with FLX card <br />
<br />
|Nodestring with flux output <br />
|-<br />
|colspan="2"|MTS with MP cards <br />
<br />
|Material with properties <br />
|}<br />
<br />
<br />
{|class="wikitable"<br />
|+'''SMS to ADH (Writing)''' <br />
!colspan="3"|SMS Structure <br />
<br />
!width="400"|ADH String Structure <br />
|-<br />
|colspan="3"|Node with BC (Dirichlet)<br />
<br />
|NDS (only 1 node ID) with DB card <br />
|-<br />
|rowspan="5" width="100"|Nodestring <br />
|rowspan="2" width="100"|with Natural BC <br />
|rowspan="2" width="100"|with flux output <br />
|EGS with NB and FLX cards <br />
|-<br />
|EGS with NB card <br />
|-<br />
|rowspan="2"|with Dirichlet BC <br />
|rowspan="2"|with flux output <br />
|NDS (2 or more node IDs) with DB card, and MDS with FLX card <br />
|-<br />
|NDS (2 or more node IDs) with DB card <br />
|-<br />
|colspan="2"|with flux output <br />
<br />
|MDS with FLX card <br />
|-<br />
|colspan="3"|Material with properties <br />
|MTS with MP cards<br />
|}<br />
<br />
==Case Studies / Sample Problems== <br />
The following ADH simulation files have been provided by [http://chl.erdc.usace.army.mil/ CHL] to test ADH and the SMS interface capabilities. Additional test cases will be posted here as the interface can successfully read, write, and run the ADH model from within SMS.<br />
<br />
SMS 10.1 Development version using ADH rev #3669 dated August 2007: <br />
* '''[http://sms.aquaveo.com/ADH-bayousorrel.zip Bayou_Sorrel]''' &ndash; Uses the <font color="green">NB OVL</font> and <font color="green">NB OTW</font> boundary condition cards. Includes two materials on a complex mesh.<br />
* '''[http://sms.aquaveo.com/ADH-pool5.zip Pool5]''' &ndash; Uses the <font color="green">NB OVL</font> and <font color="green">NB OTW</font> boundary condition cards. Includes two inflows with one outflow and four materials on a complex mesh.<br />
* '''[http://sms.aquaveo.com/ADH-nb_dis.zip nb dis]''' &ndash; Tests the <font color="green">NB DIS</font> boundary card on a straight flume.<br />
* '''[http://sms.aquaveo.com/ADH-op_bt.zip op bt]''' &ndash; Tests the <font color="green">OP BT</font> card which includes the vessel movement library. This test case contains a boat definition file (*.bt).<br />
* '''[http://sms.aquaveo.com/ADH-db_lde.zip db lde]''' &ndash; Tests the <font color="green">DB LDE</font> pressure lid card on a straight flume.<br />
* '''[http://sms.aquaveo.com/ADH-db_ldh.zip db ldh]''' &ndash; Tests the <font color="green">DB LDH</font> pressure lid card on a straight flume.<br />
* '''[http://sms.aquaveo.com/ADH-db_lid.zip db lid]''' &ndash; Tests the <font color="green">DB LID</font> pressure lid card on a straight flume.<br />
<br />
==External Links==<br />
*[https://web-beta.archive.org/web/20161122222013/https://adh.usace.army.mil/new_webpage/main/main_page.htm ADH Website]<br />
*[https://web-beta.archive.org/web/20161124030716/https://adh.usace.army.mil/new_webpage/documentation/AdH_Manual_Hydrodynamic-Version4.5.pdf ADH Manual]<br />
*[https://web-beta.archive.org/web/20170221125651/https://adh.usace.army.mil/new_webpage/documentation/decision_tree.pdf ADH Model Troubleshooting Flowchart]<br />
<br />
==Related Topics==<br />
*[[SMS:SMS Models|SMS Models]]<br />
<br />
{{Template:Navbox SMS}}<br />
<br />
[[Category:ADH|A]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=SMS:SRH-2D_Errors&diff=122596SMS:SRH-2D Errors2017-04-19T22:10:54Z<p>Dharker: fixed recently added error title</p>
<hr />
<div>This is a list of known error messages produced by [[SMS:SRH-2D|SRH-2D]]. These errors will appear during the model run.<br />
<br />
==List of Error Messages==<br />
The first three columns in the table are sortable. Simply click the small arrows on the right side of the column header to sort in ascending or descending order.<br />
<br />
The columns in the table include:<br />
* '''Location''' indicates whether the error occurs in the SRH-2D Preprocessor or in SRH-2D itself.<br />
* '''Error Code''' gives the Error Code (if any).<br />
* '''Error Text from Model''' gives the full text of the error message. Errors that do not produce any error text will have "no text" in this field.<br />
* '''Description''' gives more details about the error.<br />
* '''Solution''' gives steps necessary to correct the issue.<br />
<br />
{| class="wikitable sortable" style="border:1px solid black;"<br />
! style="width:5%;" | Location<br />
! style="width:5%;" | Error Code<br />
! style="width:25%;" | Error Text from Model<br />
! style="width:25%;" class="unsortable" | Description<br />
! style="width:40%;" class="unsortable" | Solution<br />
<!-- Use the following as a template to add new entries<br />
|-<br />
| location<br />
| code<br />
| text<br />
| description<br />
| solution<br />
--><br />
|-<br />
| SRH-2D<br />
| 1<br />
| Stopped in uti_qwin_xyplot.f90 TIME_SIMU <br />
| Inconsistent time control<br />
| The end time is prior to the start time in the model control. Adjust so it is later than the start time.<br />
|-<br />
| PreSRH-2D<br />
| 1<br />
| unable to open srhhydro file! <br />
| Unable to open srhhydro file<br />
| The path length for the SMS project is too long. Therefore, the SRH-2D preprocessor could not read the exported files from SMS. Reduce the path length to less than 300 characters.<br />
|-<br />
| PreSRH-2D<br />
| 1<br />
| Element ID is not consecutive<br />
| The mesh element ID's have been mismatched since some mesh nodes were modified and not renumbered (which causes SMS to automatically update the mesh element ID's)<br />
| The mesh nodes needs to be renumbered using the Renumber command under the Nodes menu in the Mesh module<br />
|-<br />
| SRH-2D<br />
| <br />
| No cells cover an obstruction in structure_obstruction.f90<br />
| Obstruction feature area of influence does not cover the centroid of at least one element<br />
| The "Obstruction Width/Diameter:" value in the ''Obstructions Properties'' dialog is set to "0" and/or an obstruction arc is positioned just beyond half the width/diameter defined in the properties from the centroid of a mesh element. <br />
|-<br />
| SRH-2D<br />
| 5<br />
| Stopped in structure_culvert.f90 ICELL error#5<br />
| BC arc mesh snapping does not match inactive material zone snapping<br />
| Some paired arc 1D structures require an "unassigned" material zone between the structure arcs. If the material zone snapping does not match the BC arc snapping, there will be element inactivity problems at the face of the structure. <br />
|-<br />
| SRH-2D<br />
| <br />
| <br />
| More than 99 obstructions exist<br />
| SRH-2D has a built in limit to how many obstructions can be included in a model. Currently this limit is 99. Reduce the number of obstructions to 99 or fewer.<br />
|-<br />
| SRH-2D<br />
| <br />
| a face cannot be found given two mesh points<br><br />
Two points are: 7262 591<br><br />
Check your mesh node list; you may do this using _SIF.dat file directly!<br />
| Errors from final_touch.f90 **** on MONITOR LINE#2<br><br />
Monitor line nodestring not snapped correctly<br />
| When the monitor line is snapped to the mesh as a nodestring, the nodestring does not have a continuous string of nodes but rather skips a node so that the nodestring crosses the middle of the element diagonally. This is a bug that has been fixed.<br />
|-<br />
| SRH-2D<br />
| <br />
| <br />
| If you specify a ''z'' elevation to a bridge arc that is too high in the structures exercise, SRH doesn't run.<br />
| bug<br />
|-<br />
| SRH-2D<br />
| 2<br />
| ALL INLET cells are dry from bc_mdot2.f90! Code may have blow up due to input errors or too-large time-step.<br />
| All material polygons unassigned<br />
| This occurs when none of the materials have been assigned to the material polygons. Also occurs when all material polygons covering the inflow BC are inactive.<br />
|-<br />
| SRH-2D<br />
| <br />
| FATAL ERROR The code diverged; further reduction of time step would help the convergence!<br />
| Too large of a time step<br />
| Reduce the size of the time steps<br />
|-<br />
| <br />
| <br />
| No mesh that matches the scalar set.<br />
| No mesh that matches the scalar set.<br />
| Nodes &#x7C; Renumber. It is a good idea after you are done editing your mesh to renumber the nodes, to make sure SMS and SRH-2D have the same numbers on every node.<br />
|-<br />
| <br />
| <br />
| <br />
| WSE error directly under the bridge in the form of waves oscillating through the channel<br />
| Use larger, quadrilateral elements in the area of deep flow (as you have found). This means that the piers need to be switched to obstructions<br />
|-<br />
| <br />
| <br />
| The following coverage(s) have an unsupported type and will be converted to area property: Mat_Test" error message<br />
| Mat_Test" error message<br />
| Opening a map file with out an accompanying project file. If the coverage type is under Model (which the .map file provided indicated it was) then the type is stored in the project file so that error will appear when opening just the .map file.<br />
|-<br />
| SRH-2D<br />
| <br />
| Exit code 0<br />
| Exit code 0<br />
| SRH-2D has stopped or finished (whether "successfully executed" or not), adjust the parameters to make converge if not succesfully executed<br />
|-<br />
| <br />
| 1<br />
| Error code 1<br />
| srhmat file does not exist<br />
| File didn't export successfully, Make sure assigned materials in the materials coverage, possibly too many monitoring lines (20 or less okay)<br />
|-<br />
| SRH-2D<br />
| <br />
| a face cannot be found given two mesh points<br><br />
Two points are: 7262 591<br />
Check your mesh node list; you may do this using _SIF.dat file directly!<br />
| Errors from final_touch.f90 on MONITOR LINE#2<br />
| rebuild the arcs<br />
|-<br />
| PreSRH-2D<br />
| <br />
| forrtl: severe (157): Program Exception - access violation<br />
| <br />
| Set up file location Preferences to the correct location for SRH-Pre<br />
|-<br />
| SRH-2D<br />
| 4<br />
| All INLET cells are dry sets are dry from bc_mdot2.f90! Code may have blow up (sic) due to input errors or too-large time-step. <br />
| <br />
| This problem typically arises because the polygons that you have given for the obstructions do not overlap any element centroids. The problem can be solved by refining the elements in the area of the obstructions until the obstruction polygon is well represented by elements whose centroids lie within the spatial extent of the polygons.<br />
|-<br />
| PreSRH-2D<br />
| <br />
| MESH-UNIT: Enter one of the following options for the unit of the mesh<br />
| Mesh unit error<br />
| SRH requires that vertical and horizontal units be in either meters or U.S survey feet<br />
|-<br />
| SRH-2D<br />
| 8<br />
| Inconsistent cell ID in mesh_connectivity: maybe due to wrong nodestring<br />
| <br />
| Possibly due to overlapping elements<br />
|-<br />
| PreSRH-2D<br />
| <br />
| a face cannot be found given two mesh points<br><br />
Two points are: 38383 38494<br />
Check your mesh node list; you may do this using _SIF.dat file directly!<br />
| Errors from final touch.f90 on MONITOR LINE#2<br><br />
Inconsistent or disconnected nodestring for a monitor line<br />
| This was caused by having a monitoring line run across a large "hole" in the mesh. The hole was large enough that we were not snapping the monitor line to a valid nodestring.<br />
|-<br />
| PreSRH-2D<br />
| 1<br />
| Stopped in add_nbdf.90 DIS<br />
| Issue with BC nodestrings<br />
| In this case, this issue was from a bug where SMS was exporting the nodestring in the SRHGEOM file incorrectly for two HY8 culvert arcs. SMS was essentially writing the same string of nodes for both the upstream and downstream culvert arcs.<br />
|-<br />
| SRH-2D<br />
| 1<br />
| Stopped in face_wd.f90 PRESS#1<br />
| Issue with Pressure Flow BC and "Piers"<br />
| In this problem, SRH2D did not allow holes in the mesh that represented bridge piers within the Pressure flow zone. This is only a problem in SMS v.12.1 and the SRH executable supplied with it. SMS 12.2 and the SRH executable supplied with it now allows holes in the mesh within Pressure zones. The same error will also be shown if an "unassigned" material type is specified in the pressure zone, again this is only a problem in SMS v12.1 and the SRH exe supplied with it, 12.2 allows "unassigned" material types in the pressure flow zone.<br />
|-<br />
| SRH-2D<br />
| <br />
| Program Stopped as Mesh is different in RST file<br><br />
One of the following is different:<br><br />
Ncell Nvert Nface Nclfc Nclvt in RESTART file<br><br />
do not match those in the input file<br><br />
Ncell Nvert Nface Nclfc Nclvt<br><br />
in restart file are: 13604 7374 20977 41693 41693<br><br />
in casename.GRD file are: 15459 8277 23735 47225<br><br />
Mesh topology has to be the same for irest>=1 or init_method=3<br />
| Using a restart file that was created with another mesh<br />
| Restart files can only be used with simulations using the exact same mesh.<br />
|-<br />
| PreSRH-2D<br />
| <br />
| Could not find a mesh cell which contains the monitoring point! Check if you have the right input of (X Y) coordinates for a monitoring points<br />
| Monitor Point Outside of Mesh<br />
| Monitor point must be somewhere within a mesh element.<br />
|-<br />
| SRH-2D<br />
| 6940<br />
| <br />
| <br />
| Ensure that areas upstream of the upstream culvert location and areas downstream of the downstream culvert location have a valid material type assigned.<br />
|}<br />
<br />
==Related Topics==<br />
* [[SMS:SRH-2D|SRH-2D]]<br />
* [[SMS:Bugfixes|SMS Bugfixes]]<br />
<br />
<br />
{{Navbox SMS}}<br />
<br />
[[Category:SRH-2D|Errors]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=SMS:SRH-2D_Errors&diff=122595SMS:SRH-2D Errors2017-04-19T22:09:56Z<p>Dharker: Added element ID error</p>
<hr />
<div>This is a list of known error messages produced by [[SMS:SRH-2D|SRH-2D]]. These errors will appear during the model run.<br />
<br />
==List of Error Messages==<br />
The first three columns in the table are sortable. Simply click the small arrows on the right side of the column header to sort in ascending or descending order.<br />
<br />
The columns in the table include:<br />
* '''Location''' indicates whether the error occurs in the SRH-2D Preprocessor or in SRH-2D itself.<br />
* '''Error Code''' gives the Error Code (if any).<br />
* '''Error Text from Model''' gives the full text of the error message. Errors that do not produce any error text will have "no text" in this field.<br />
* '''Description''' gives more details about the error.<br />
* '''Solution''' gives steps necessary to correct the issue.<br />
<br />
{| class="wikitable sortable" style="border:1px solid black;"<br />
! style="width:5%;" | Location<br />
! style="width:5%;" | Error Code<br />
! style="width:25%;" | Error Text from Model<br />
! style="width:25%;" class="unsortable" | Description<br />
! style="width:40%;" class="unsortable" | Solution<br />
<!-- Use the following as a template to add new entries<br />
|-<br />
| location<br />
| code<br />
| text<br />
| description<br />
| solution<br />
--><br />
|-<br />
| SRH-2D<br />
| 1<br />
| Stopped in uti_qwin_xyplot.f90 TIME_SIMU <br />
| Inconsistent time control<br />
| The end time is prior to the start time in the model control. Adjust so it is later than the start time.<br />
|-<br />
| PreSRH-2D<br />
| 1<br />
| unable to open srhhydro file! <br />
| Unable to open srhhydro file<br />
| The path length for the SMS project is too long. Therefore, the SRH-2D preprocessor could not read the exported files from SMS. Reduce the path length to less than 300 characters.<br />
|-<br />
| PreSRH-2D<br />
| 1<br />
| Element ID is not consecutive in rd_srh_v3_0!<br />
| The mesh element ID's have been mismatched since some mesh nodes were modified and not renumbered (which causes SMS to automatically update the mesh element ID's)<br />
| The mesh nodes needs to be renumbered using the Renumber command under the Nodes menu in the Mesh module<br />
|-<br />
| SRH-2D<br />
| <br />
| No cells cover an obstruction in structure_obstruction.f90<br />
| Obstruction feature area of influence does not cover the centroid of at least one element<br />
| The "Obstruction Width/Diameter:" value in the ''Obstructions Properties'' dialog is set to "0" and/or an obstruction arc is positioned just beyond half the width/diameter defined in the properties from the centroid of a mesh element. <br />
|-<br />
| SRH-2D<br />
| 5<br />
| Stopped in structure_culvert.f90 ICELL error#5<br />
| BC arc mesh snapping does not match inactive material zone snapping<br />
| Some paired arc 1D structures require an "unassigned" material zone between the structure arcs. If the material zone snapping does not match the BC arc snapping, there will be element inactivity problems at the face of the structure. <br />
|-<br />
| SRH-2D<br />
| <br />
| <br />
| More than 99 obstructions exist<br />
| SRH-2D has a built in limit to how many obstructions can be included in a model. Currently this limit is 99. Reduce the number of obstructions to 99 or fewer.<br />
|-<br />
| SRH-2D<br />
| <br />
| a face cannot be found given two mesh points<br><br />
Two points are: 7262 591<br><br />
Check your mesh node list; you may do this using _SIF.dat file directly!<br />
| Errors from final_touch.f90 **** on MONITOR LINE#2<br><br />
Monitor line nodestring not snapped correctly<br />
| When the monitor line is snapped to the mesh as a nodestring, the nodestring does not have a continuous string of nodes but rather skips a node so that the nodestring crosses the middle of the element diagonally. This is a bug that has been fixed.<br />
|-<br />
| SRH-2D<br />
| <br />
| <br />
| If you specify a ''z'' elevation to a bridge arc that is too high in the structures exercise, SRH doesn't run.<br />
| bug<br />
|-<br />
| SRH-2D<br />
| 2<br />
| ALL INLET cells are dry from bc_mdot2.f90! Code may have blow up due to input errors or too-large time-step.<br />
| All material polygons unassigned<br />
| This occurs when none of the materials have been assigned to the material polygons. Also occurs when all material polygons covering the inflow BC are inactive.<br />
|-<br />
| SRH-2D<br />
| <br />
| FATAL ERROR The code diverged; further reduction of time step would help the convergence!<br />
| Too large of a time step<br />
| Reduce the size of the time steps<br />
|-<br />
| <br />
| <br />
| No mesh that matches the scalar set.<br />
| No mesh that matches the scalar set.<br />
| Nodes &#x7C; Renumber. It is a good idea after you are done editing your mesh to renumber the nodes, to make sure SMS and SRH-2D have the same numbers on every node.<br />
|-<br />
| <br />
| <br />
| <br />
| WSE error directly under the bridge in the form of waves oscillating through the channel<br />
| Use larger, quadrilateral elements in the area of deep flow (as you have found). This means that the piers need to be switched to obstructions<br />
|-<br />
| <br />
| <br />
| The following coverage(s) have an unsupported type and will be converted to area property: Mat_Test" error message<br />
| Mat_Test" error message<br />
| Opening a map file with out an accompanying project file. If the coverage type is under Model (which the .map file provided indicated it was) then the type is stored in the project file so that error will appear when opening just the .map file.<br />
|-<br />
| SRH-2D<br />
| <br />
| Exit code 0<br />
| Exit code 0<br />
| SRH-2D has stopped or finished (whether "successfully executed" or not), adjust the parameters to make converge if not succesfully executed<br />
|-<br />
| <br />
| 1<br />
| Error code 1<br />
| srhmat file does not exist<br />
| File didn't export successfully, Make sure assigned materials in the materials coverage, possibly too many monitoring lines (20 or less okay)<br />
|-<br />
| SRH-2D<br />
| <br />
| a face cannot be found given two mesh points<br><br />
Two points are: 7262 591<br />
Check your mesh node list; you may do this using _SIF.dat file directly!<br />
| Errors from final_touch.f90 on MONITOR LINE#2<br />
| rebuild the arcs<br />
|-<br />
| PreSRH-2D<br />
| <br />
| forrtl: severe (157): Program Exception - access violation<br />
| <br />
| Set up file location Preferences to the correct location for SRH-Pre<br />
|-<br />
| SRH-2D<br />
| 4<br />
| All INLET cells are dry sets are dry from bc_mdot2.f90! Code may have blow up (sic) due to input errors or too-large time-step. <br />
| <br />
| This problem typically arises because the polygons that you have given for the obstructions do not overlap any element centroids. The problem can be solved by refining the elements in the area of the obstructions until the obstruction polygon is well represented by elements whose centroids lie within the spatial extent of the polygons.<br />
|-<br />
| PreSRH-2D<br />
| <br />
| MESH-UNIT: Enter one of the following options for the unit of the mesh<br />
| Mesh unit error<br />
| SRH requires that vertical and horizontal units be in either meters or U.S survey feet<br />
|-<br />
| SRH-2D<br />
| 8<br />
| Inconsistent cell ID in mesh_connectivity: maybe due to wrong nodestring<br />
| <br />
| Possibly due to overlapping elements<br />
|-<br />
| PreSRH-2D<br />
| <br />
| a face cannot be found given two mesh points<br><br />
Two points are: 38383 38494<br />
Check your mesh node list; you may do this using _SIF.dat file directly!<br />
| Errors from final touch.f90 on MONITOR LINE#2<br><br />
Inconsistent or disconnected nodestring for a monitor line<br />
| This was caused by having a monitoring line run across a large "hole" in the mesh. The hole was large enough that we were not snapping the monitor line to a valid nodestring.<br />
|-<br />
| PreSRH-2D<br />
| 1<br />
| Stopped in add_nbdf.90 DIS<br />
| Issue with BC nodestrings<br />
| In this case, this issue was from a bug where SMS was exporting the nodestring in the SRHGEOM file incorrectly for two HY8 culvert arcs. SMS was essentially writing the same string of nodes for both the upstream and downstream culvert arcs.<br />
|-<br />
| SRH-2D<br />
| 1<br />
| Stopped in face_wd.f90 PRESS#1<br />
| Issue with Pressure Flow BC and "Piers"<br />
| In this problem, SRH2D did not allow holes in the mesh that represented bridge piers within the Pressure flow zone. This is only a problem in SMS v.12.1 and the SRH executable supplied with it. SMS 12.2 and the SRH executable supplied with it now allows holes in the mesh within Pressure zones. The same error will also be shown if an "unassigned" material type is specified in the pressure zone, again this is only a problem in SMS v12.1 and the SRH exe supplied with it, 12.2 allows "unassigned" material types in the pressure flow zone.<br />
|-<br />
| SRH-2D<br />
| <br />
| Program Stopped as Mesh is different in RST file<br><br />
One of the following is different:<br><br />
Ncell Nvert Nface Nclfc Nclvt in RESTART file<br><br />
do not match those in the input file<br><br />
Ncell Nvert Nface Nclfc Nclvt<br><br />
in restart file are: 13604 7374 20977 41693 41693<br><br />
in casename.GRD file are: 15459 8277 23735 47225<br><br />
Mesh topology has to be the same for irest>=1 or init_method=3<br />
| Using a restart file that was created with another mesh<br />
| Restart files can only be used with simulations using the exact same mesh.<br />
|-<br />
| PreSRH-2D<br />
| <br />
| Could not find a mesh cell which contains the monitoring point! Check if you have the right input of (X Y) coordinates for a monitoring points<br />
| Monitor Point Outside of Mesh<br />
| Monitor point must be somewhere within a mesh element.<br />
|-<br />
| SRH-2D<br />
| 6940<br />
| <br />
| <br />
| Ensure that areas upstream of the upstream culvert location and areas downstream of the downstream culvert location have a valid material type assigned.<br />
|}<br />
<br />
==Related Topics==<br />
* [[SMS:SRH-2D|SRH-2D]]<br />
* [[SMS:Bugfixes|SMS Bugfixes]]<br />
<br />
<br />
{{Navbox SMS}}<br />
<br />
[[Category:SRH-2D|Errors]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:MODFLOW-USG&diff=122474GMS:MODFLOW-USG2017-04-17T21:21:29Z<p>Dharker: /* External Files */ Added Input and Output Description PDF Link</p>
<hr />
<div>{{MODFLOW Links}}<br />
<br />
{{hide in print|Starting at GMS version 10.0, GMS supports MODFLOW-USG.}} MODFLOW-USG is a version of MODFLOW based on finite volume calculations, thus allowing for many different types of grid cells. This allows the model grid to more accurately match the model domain and be more efficiently refined in areas where more accuracy is desired.<br />
<br />
MODFLOW-USG models are built using unstructured grids, or [[GMS:UGrid Module|UGrids]], which are a new (as of GMS 10.0) type of geometric object that can handle the wide variety of cell types supported by MODFLOW-USG.<br />
<br />
The MODFLOW-USG model is included with all [http://www.aquaveo.com/software/gms-pricing paid editions] of GMS.<br />
[[Category:Link to Store]]<br />
<br />
== Choosing MODFLOW Version ==<br />
<br />
{{only in print|[[Image:Switching_MF2K5.jpg|200px|none|thumb|left|MODFLOW Global Option Dialog]]}}<br />
Only MODFLOW-USG is supported when using unstructured grids. MODLFOW-USG can also be used for a model using a [[GMS:3D_Grid_Module|3D grid]]. Choosing to use MODFLOW-USG is done in the [[GMS:Global_Options/Basic_Package|''MODFLOW Global Options'' dialog]]. With a 3D grid at any time the user can switch from one MODFLOW version to another.<br />
{{hide in print|[[Image:Switching_MF2K5.jpg|300px|none|thumb|left|''MODFLOW Global Option'' dialog]]}}<br />
<br />
==Unsupported Features==<br />
Previous to GMS 10.1 there was no support for the following MODFLOW-USG features, though the CLN and GNC packages and the import feature are now supported in current versions of GMS.<br />
#Packages/processes<br />
#*CLN Process<br />
#*GNC Package<br />
#Older versions of GMS cannot read MODFLOW-USG files written by any non-GMS software. This is because there was no standard way to define the unstructured grid geometry. GMS writes a *.VTU ([http://www.vtk.org/VTK/img/file-formats.pdf Visualization Toolkit] Unstructured Grid) file with the MODFLOW files to define the grid geometry. In GMS 10.1 and later versions a model that was created outside of GMS can be imported as long as there is either a *.vtu file (VTK unstructured grid file) or a *.gsf file ([http://www.pesthomepage.org/getfiles.php?file=gwutil_c.pdf Grid Specification File]) present to define the grid geometry because the MODFLOW-USG native input files do not include locations of the grid nodes ([https://answers.usgs.gov/ unfortunately]).<br />
<br />
Additionally, PEST-ASP is currently unsupported in MODFLOW-USG<br />
<br />
==MODFLOW-USG Files==<br />
<br />
Here are tables of some of the available Input and Output files for MODFLOW-USG.<br />
<br />
* For more information on these files see the manual<br />
<br />
{| class="wikitable" <br />
|+'''Required Input Files'''<br />
!width="40" align="center"|Name<br />
!width="250" align="center"|Description<br />
|-<br />
|MFN||MODFLOW Name File<br />
|-<br />
|GLO||Global Listing File<br />
|-<br />
|DIS||Discretization File<br />
|-<br />
|OC||Process Output Control Option File<br />
|-<br />
|BA6||Basic Package Global Options File<br />
|-<br />
|}<br />
<br />
{| class="wikitable" <br />
|+'''Solver Package File'''<br />
!width="40" align="center"|Name<br />
!width="250" align="center"|Description<br />
|-<br />
|SMS||Sparse Matrix Solver<br />
|-<br />
|}<br />
<br />
{| class="wikitable" <br />
|+'''Input Flow Package Files'''<br />
!width="40" align="center"|Name<br />
!width="250" align="center"|Description<br />
|-<br />
|BCF||Block-Centered Flow<br />
|-<br />
|LPF||Layer Property Flow<br />
|-<br />
|}<br />
<br />
{| class="wikitable" <br />
|+'''Optional Package Files'''<br />
!width="40" align="center"|Name<br />
!width="250" align="center"|Description<br />
|-<br />
|CHD||Time-Variant Specified-Head<br />
|-<br />
|DRN||Drain<br />
|-<br />
|EVT||Evapotranspiration<br />
|-<br />
|GAG||Gage<br />
|-<br />
|GHB||General Head Boundary<br />
|-<br />
|GNC||Ghost Node Correction<br />
|-<br />
|HFB||Horizontal Flow Barrier<br />
|-<br />
|LAK||Lake<br />
|-<br />
|RCH||Recharge<br />
|-<br />
|RIV||River<br />
|-<br />
|SFR||Streamflow-Routing<br />
|-<br />
|STR||Stream-Routing<br />
|-<br />
|SUB||Subsidence<br />
|-<br />
|WEL||Process Well<br />
|-<br />
|}<br />
<br />
{| class="wikitable" <br />
|+'''Observation Input Files'''<br />
!width="40" align="center"|Name<br />
!width="250" align="center"|Description<br />
|-<br />
|OBS||Main Observation Process Input<br />
|-<br />
|DROB||Drain Observation<br />
|-<br />
|CHOB||Constant-Head Flow Observation Input<br />
|-<br />
|}<br />
<br />
{| class="wikitable"<br />
|+'''Output Files'''<br />
!align="center" width="50"|Name<br />
!width="350"|Description<br />
|-<br />
|MFS||MODFLOW Super File<br />
|-<br />
|MFW||GMS MODFLOW World File<br />
|-<br />
|MFR||GMS MODFLOW Result Index File<br />
|-<br />
|PRJ||Projection<br />
|-<br />
|CSV||Cell Summary Comma Separated Value Excel<br />
|-<br />
|HFF||Head and Flow File Link to MT3DMS<br />
|-<br />
|H5||Hierarchal Data Format (HDF5) Array & List Data<br />
|-<br />
|M2P||MODFLOW Pest<br />
|-<br />
|PARAM||Parameter Information<br />
|-<br />
|}<br />
<br />
{| class="wikitable"<br />
|+'''Output Results Files'''<br />
!align="center" width="50"|Name<br />
!width="350"|Description<br />
|-<br />
|CCF||Cell-to-Cell Aquifer Flow<br />
|-<br />
|CCF2||Cell-to-Cell Stream Reach Outflow<br />
|-<br />
|DRW||Drawdown<br />
|-<br />
|GLO||Global Listing<br />
|-<br />
|HED||Head Output<br />
|-<br />
|OUT||Output<br />
|-<br />
|VTU||Visualization Toolkit Unstructured Grid<br />
|-<br />
|}<br />
<br />
{| class="wikitable"<br />
|+'''Output Data Exchange Files'''<br />
!align="center" width="50"|Name<br />
!width="350"|Description<br />
|-<br />
|_W||Weighted Residuals<br />
|-<br />
|_WW||Weighted Equivalents & Weighted Observation<br />
|-<br />
|_WS||Weighted Residuals and Simulated Equivalents<br />
|-<br />
|_R||Unweighted Residuals<br />
|-<br />
|_OS||Observed Values and Simulated Equivalents<br />
|-<br />
|_B||Data Exchange File<br />
|-<br />
|_NM||Weighted Residuals and Probability Plotting<br />
|-<br />
|}<br />
<br />
==External Files==<br />
*[http://pubs.usgs.gov/tm/06/a45/pdf/tm6-A45.pdf MODFLOW-USG Manual 2013]<br />
*[https://water.usgs.gov/ogw/mfusg/mfusg.1_3.zip Zip folder containing MODFLOW-USG v. 1.3 Input and Output Descriptions PDF]<br />
<br />
==See also==<br />
*[[GMS:Map_to_MODFLOW#MODFLOW-USG|Map &rarr; MODFLOW-USG]]<br />
*[[GMS:MODFLOW-USG Observations|MODFLOW-USG Observations]]<br />
<br />
{{Navbox GMS}}<br />
[[Category:MODFLOW]]<br />
[[Category:MODFLOW Dialogs]]<br />
[[Category:MODFLOW-USG]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:Importing_an_MT3DMS_Simulation&diff=122311GMS:Importing an MT3DMS Simulation2017-04-13T21:07:17Z<p>Dharker: Added example.</p>
<hr />
<div>It is often necessary to import an MT3DMS simulation that was not generated by GMS. Since GMS uses the standard MT3DMS file format, this is not a problem in most cases. However, there are a few steps and precautions that should be taken.<br />
<br />
===File Formats===<br />
GMS uses the standard MT3DMS file formats described in the MT3DMS documentation (Zheng, 1998). The files being imported must match these formats exactly. If the files were generated for a version of MT3DMS that uses a different set of file formats, the files will need to be edited before they can be successfully imported to GMS.<br />
<br />
===CON File===<br />
The source code of MT3DMS was changed to create a *.con concentration file instead of the default *.ucn file. GMS can read either the *.con or *.ucn file. The *.con file is written in the [[GMS:Dataset_Files#Binary_Dataset_Files|GMS binary dataset format]]. Both can be imported without an MT3DMS super file by changing the file extension to *.hed in the properties and then creating a text file with the same name in the same folder and changing that file's extension to *.mfn. GMS can then pull in this *.mfn file using the Read Solution command in the MODFLOW menu which will pull in the concentration values as if it were an output head MODFLOW dataset (e.g. example1.con -> example1.hed, then create text file example1.mfn to pull in).<br />
<br />
===Importing Super Files===<br />
GMS uses an MT3DMS super file to organize the files used by an MT3DMS simulation. This file is not a standard MT3DMS file. One approach to importing an externally defined simulation is to create an MT3DMS super file containing the names of the files used in the simulation using a text editor.<br />
<br />
<br />
{{Navbox GMS}}<br />
[[Category:MT3DMS]]<br />
[[Category:Importing Data|MT3D]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:Importing_an_MT3DMS_Simulation&diff=122310GMS:Importing an MT3DMS Simulation2017-04-13T21:05:43Z<p>Dharker: Added info on pulling in con and ucn files per a customer request</p>
<hr />
<div>It is often necessary to import an MT3DMS simulation that was not generated by GMS. Since GMS uses the standard MT3DMS file format, this is not a problem in most cases. However, there are a few steps and precautions that should be taken.<br />
<br />
===File Formats===<br />
GMS uses the standard MT3DMS file formats described in the MT3DMS documentation (Zheng, 1998). The files being imported must match these formats exactly. If the files were generated for a version of MT3DMS that uses a different set of file formats, the files will need to be edited before they can be successfully imported to GMS.<br />
<br />
===CON File===<br />
The source code of MT3DMS was changed to create a *.con concentration file instead of the default *.ucn file. GMS can read either the *.con or *.ucn file. The *.con file is written in the [[GMS:Dataset_Files#Binary_Dataset_Files|GMS binary dataset format]]. Both can be imported without an MT3DMS super file by changing the file extension to *.hed in the properties and then creating a text file with the same name in the same folder and changing that file's extension to *.mfn. GMS can then pull in this *.mfn file using the Read Solution command in the MODFLOW menu which will pull in the concentration values as if it were an output head MODFLOW dataset.<br />
<br />
===Importing Super Files===<br />
GMS uses an MT3DMS super file to organize the files used by an MT3DMS simulation. This file is not a standard MT3DMS file. One approach to importing an externally defined simulation is to create an MT3DMS super file containing the names of the files used in the simulation using a text editor.<br />
<br />
<br />
{{Navbox GMS}}<br />
[[Category:MT3DMS]]<br />
[[Category:Importing Data|MT3D]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=SMS:BOUSS-2D&diff=122256SMS:BOUSS-2D2017-04-12T21:41:54Z<p>Dharker: Fixed broken link to website</p>
<hr />
<div>{{SMS Infobox Model |<br />
|name= BOUSS-2D<br />
|model_type= Boussinesq Wave Model for Coastal Regions and Harbors.<br />
|developer= <br />
[http://www-personal.umich.edu/~onwogu/index.html Okey George Nawogu, Ph.D.] <br /> <br />
[http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=Persons;56 Zeki Demirbilek, Ph.D.]<br />
|web_site= [https://web-beta.archive.org/web/20090820113026/http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=Software;23 BOUSS-2D web site]<br />
|tutorials= <br />
General Section <br><br />
* Data Visualization<br />
* Observation<br />
Models Section <br><br />
* BOUSS-2D<br />
Several sets of sample problems and case studies are available. These include:<br /> <br />
* [[SMS:BOUSS-2D#Test_Cases|Aquaveo sample problems]]<br />
* Model Validataion cases from the BOUSS-2D technical report<br />
}}<br />
<br />
BOUSS-2D is a comprehensive model for simulating the propagation and tranformation of waves in coastal regions and harbors based on a time-domain solution of Boussinesq-type equations. It is based on Boussinesq-type equations derived by Okey Nwogu and has been under development since 1993. The equations are depth-integrated for the conservation of mass and momentum for nonlinear waves propagating in shallow and intermediate water depths.<br />
<br />
The BOUSS-2D model can be added to a [http://www.aquaveo.com/software/sms-pricing paid edition] of SMS.<br />
[[Category:Link to Store]]<br />
<br />
== Functionality ==<br />
BOUSS-2D computes nearshore wave fields including mean wave heights, mean current direction, mean water level breaking<br />
and transient representation of water levels, currents, and wave breaking.<br />
<br />
BOUSS-2D is a comprehensive numerical model for simulating the propagation and transformation of waves in coastal regions and harbors based on a time-domain solution of Boussinesq-type equations. The governing equations are uniformly valid from deep to shallow water and can simulate most of the phenomena of interest in the nearshore zone and harbor basins including:<br />
* Reflection/diffraction near structures<br />
* Energy dissipation due to wave breaking and bottom friction<br />
* Cross-spectral energy transfer due to nonlinear wave-wave interactions<br />
* Breaking-induced longshore and rip currents<br />
* Wave-current interaction<br />
* Wave interaction with porous structures<br />
<br />
The governing equations in BOUSS-2D are solved in the time domain with a finite-difference method. Input waves may be periodic (regular) or non-periodic (irregular), and both unidirectional or multi-directional sea states may be simulated. Waves propagating out of the computation domain are either absorbed in damping layers or allowed to leave the domain freely. The SI engineering units are used in BOUSS-2D calculations.<br />
<br />
=== Output Options === <br />
See ''Output Options'' in the [[SMS:BOUSS-2D Simulations#Output Options|BOUSS-2D Simulations]] article.<br />
<br />
===Saving BOUSS-2D===<br />
When completing a ''File'' | '''Save As...''' command, the following files get saved in the *.sms<br />
<br />
* *.mat referenced to new save location<br />
* *.map referenced to new save location<br />
* Damping files saved to temp folder<br />
* *.par referenced to new save location<br />
* *.sol referenced to original save location unless rerun<br />
* *.h5 referenced to new save location<br />
<br />
== Using the Model / Practical Notes ==<br />
BOUSS-2D can be applied to a wide variety of coastal and ocean engineering problems, including complex wave transformation over small coastal regions (1-5 km), wave agitation and harbor resonance studies, wave breaking over submerged obstacles, breaking-induced nearshore circulation patterns, wave-current interaction near tidal inlets, infra-gravity wave generation by groups of short waves, and wave transformation around artificial islands.<br />
<br />
As with many numerical models, BOUSS-2D can terminate or crash due to numerical instabilities. These are usually caused by problems related to the grid, the boundary conditions, or model parameters. The following lists describe common causes of instability and methods to correct them.<br />
<br />
=== Instability due to the grid/geometry ===<br />
* Model stability requires a low Courant number throughout the domain. SMS computes an approximate maximum time step to maintain a Courant number below 0.5. In some cases, it is desired to lower the time step even more. Additionally, some may want to truncate the computational domain to areas with depth above a specified minimum. Another option is to increase resolution by using smaller computational cells. Either of these options increase run time, so before applying them, look at the other causes of instability.<br />
* Abrupt changes in elevation from one cell to another in the computational domain could result in instabilities. It may be helpful to smooth the grid. (A smoothing command is available by right clicking on the grid object in the project explorer in the SMS interface.)<br />
* Computation nodes surrounded on three or four sides by land may be created during the grid creation process. These "isolated" cells may become unstable and generally don't have an impact on the wave climate. They can be converted to land cells.<br />
<br />
=== Instability due to the boundary conditions ===<br />
* Generally, avoid placing damping or porosity layers along structures and shorelines.<br />
* Wave makers are more stable on the edges of the domain. Therefore, generally speaking, the wave maker should be placed on the boundary of the domain in constant (or nearly constant) depth water. (The SMS interface offers to extend the grid and transition to constant depth if a wave maker is created in a location with more that 20% variation in depth.) This is especially true in real world applications where reflected waves are of no concern. Also, when simulating large waves, the greater stability of external wavemakers may be required.<br />
* Wave makers should be placed far enough from shore to avoid interaction between the wave maker and reflecting waves. This is because the external boundary behind the wave maker is treated as a vertical wall.<br />
* Exceptions, or applications in which internal wavemakers (i.e. wavemakers placed inside the domain) are recommended include:<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
* In applications with significant reflections from structures inside the computational domain. When reflected are caused by coastlines, structures, or bathymetry (reflected wave sources), the simulated seastate will become less uniform spatially, and the simulation may not reach a steady-state condition. The resulting wave field in such simulations will generally consist of nodes and anti-nodes that resemble a standing wave pattern, where waves appear to be bouncing back and forth inside the domain. If reflected waves cannot escape through boundaries of the modeling domain (or are constrained to exit the domain), a steady-state condition technically cannot be reached irrespective of the length of simulation. When reflected waves intercept external wavemakers, the extremes (lows and highs) in the calculated wavefield may keep building and can eventually lead to model instabilities.<br />
* Internal wavemakers should be used for finite domains and especially for limited area physical modeling studies, and with the above specified guidance.<br />
</blockquote><br />
* If wavemakers are placed on the interior of the domain, they should cross the entire domain to avoid potential "end effects", and have a damping layer placed behind (on the seaward side of) the internal wavemakers to absorb reflected waves. There should also be a gap (at least one non-damped cell) between the internal wavemaker and the damping layer located offshore. <br />
* [[Image:Damping Reflection Relationship-Fig 5- BOUSS-2D Technical Report.png|400px|right|Relationship between damping coefficient and width and reflection]]In the absence of laboratory or field data to calibrate damping and porous layers for an application, consider multiple simulations with a range of damping widths and/or coefficients. This graph from BOUSS-2D's technical report illustrates the variation of effective reflectivity given various damping coefficients and damping layer widths. To use this graph:<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
* Compute L (the wavelength for the incident wave).<br />
* Select a w/L ratio. Use this ratio to compute w (damping width).<br />
* Select an expected reflection percentage. Follow a horizontal line for this percentage on plot to intersect the graph for selected w/L ratio. Read associated damping coefficient from plot.<br />
* Note that the reflection coefficient is very sensitive to a change in damping coefficient when the coefficient is small (< 0.3) and much less sensitive when the coefficient is larger.<br />
* This process may require the damping parameters be changed when different wave conditions are considered.<br />
* It should be observed that this plot is for normally incident waves. Different reflection coefficients would be obtained for obliquely incident waves.<br />
</blockquote><br />
* Damping layers should be 5-10 cells wide.<br />
<br />
=== Instability due to model parameters ===<br />
* The model includes a Smagorinsky term to account for subgrid turbulence. If the turbulence is known, it is expected this term can be left at the default (0.0), however, it may be increased to increase stability. (This should be done with caution. Remember, don't suppress the wiggles, they are trying to say something.)<br />
<br />
==Test Cases==<br />
* '''[http://sms.aquaveo.com/BOUSS2D-test1-internal_wavemaker.zip Test 1]''' &ndash; Simple test demonstrating the use of an internal wavemaker.<br />
<br />
== External Links ==<br />
* [http://www.dtic.mil/cgi-bin/GetTRDoc?AD=ADA400294 BOUSS-2D User Manual]<br />
* CHL BOUSS-2D website [http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=Software;23]<br />
* May 2007 ERDC/CHL CHETN-I-73 Infra-Gravity Wave Input Toolbox (IGWT): User’s Guide [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-i-73.pdf]<br />
* May 2005 ERDC/CHL CHETN-I-70 BOUSS-2D Wave Model in SMS: 2. Tutorial with Examples [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-i-70.pdf]<br />
* Mar 2005 ERDC/CHL CHETN-I-69 BOUSS-2D Wave Model in the SMS: 1. Graphical Interface [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-i-69.pdf]<br />
* Aug 2011 Tsunami Modeling Example Study - A Joint Hydraulic/Structural Methodology for the Rehabilitation of the Crescent City Marina [http://dx.doi.org/10.1061/41190(422)28]<br />
* Apr 2014 Tsunami Modeling Article [http://www.nwyachting.com/2014/04/rebuilt-to-withstand-tsunami-crescent-city-inner-harbor-is-open/]<br />
<br />
== Related Topics ==<br />
* [[SMS:BOUSS-2D_Graphical_Interface|BOUSS-2D Graphical Interface]]<br />
* [[SMS:Cartesian Grid Module|Cartesian Grid Module]]<br />
* [[SMS:BOUSS-2D Files|BOUSS-2D Files]]<br />
* [[SMS:BOUSS-2D Graphical Interface|BOUSS-2D Model Control Dialog]] <br />
* [[SMS:BOUSS-2D Calculators|BOUSS-2D Calculators]]<br />
* [[SMS:CGWAVE|CGWAVE]]<br />
* [[SMS:SMS Models|SMS Models page]]<br />
* [[SMS:Spectral Energy|Spectral Energy]]<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
[[Category:Wave Modeling]]<br />
[[Category:BOUSS-2D]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=SMS:BOUSS-2D&diff=122255SMS:BOUSS-2D2017-04-12T21:41:03Z<p>Dharker: /* External Links */ Updated broken manual link</p>
<hr />
<div>{{SMS Infobox Model |<br />
|name= BOUSS-2D<br />
|model_type= Boussinesq Wave Model for Coastal Regions and Harbors.<br />
|developer= <br />
[http://www-personal.umich.edu/~onwogu/index.html Okey George Nawogu, Ph.D.] <br /> <br />
[http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=Persons;56 Zeki Demirbilek, Ph.D.]<br />
|web_site= [http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=Software;23 BOUSS-2D web site]<br />
|tutorials= <br />
General Section <br><br />
* Data Visualization<br />
* Observation<br />
Models Section <br><br />
* BOUSS-2D<br />
Several sets of sample problems and case studies are available. These include:<br /> <br />
* [[SMS:BOUSS-2D#Test_Cases|Aquaveo sample problems]]<br />
* Model Validataion cases from the BOUSS-2D technical report<br />
}}<br />
<br />
BOUSS-2D is a comprehensive model for simulating the propagation and tranformation of waves in coastal regions and harbors based on a time-domain solution of Boussinesq-type equations. It is based on Boussinesq-type equations derived by Okey Nwogu and has been under development since 1993. The equations are depth-integrated for the conservation of mass and momentum for nonlinear waves propagating in shallow and intermediate water depths.<br />
<br />
The BOUSS-2D model can be added to a [http://www.aquaveo.com/software/sms-pricing paid edition] of SMS.<br />
[[Category:Link to Store]]<br />
<br />
== Functionality ==<br />
BOUSS-2D computes nearshore wave fields including mean wave heights, mean current direction, mean water level breaking<br />
and transient representation of water levels, currents, and wave breaking.<br />
<br />
BOUSS-2D is a comprehensive numerical model for simulating the propagation and transformation of waves in coastal regions and harbors based on a time-domain solution of Boussinesq-type equations. The governing equations are uniformly valid from deep to shallow water and can simulate most of the phenomena of interest in the nearshore zone and harbor basins including:<br />
* Reflection/diffraction near structures<br />
* Energy dissipation due to wave breaking and bottom friction<br />
* Cross-spectral energy transfer due to nonlinear wave-wave interactions<br />
* Breaking-induced longshore and rip currents<br />
* Wave-current interaction<br />
* Wave interaction with porous structures<br />
<br />
The governing equations in BOUSS-2D are solved in the time domain with a finite-difference method. Input waves may be periodic (regular) or non-periodic (irregular), and both unidirectional or multi-directional sea states may be simulated. Waves propagating out of the computation domain are either absorbed in damping layers or allowed to leave the domain freely. The SI engineering units are used in BOUSS-2D calculations.<br />
<br />
=== Output Options === <br />
See ''Output Options'' in the [[SMS:BOUSS-2D Simulations#Output Options|BOUSS-2D Simulations]] article.<br />
<br />
===Saving BOUSS-2D===<br />
When completing a ''File'' | '''Save As...''' command, the following files get saved in the *.sms<br />
<br />
* *.mat referenced to new save location<br />
* *.map referenced to new save location<br />
* Damping files saved to temp folder<br />
* *.par referenced to new save location<br />
* *.sol referenced to original save location unless rerun<br />
* *.h5 referenced to new save location<br />
<br />
== Using the Model / Practical Notes ==<br />
BOUSS-2D can be applied to a wide variety of coastal and ocean engineering problems, including complex wave transformation over small coastal regions (1-5 km), wave agitation and harbor resonance studies, wave breaking over submerged obstacles, breaking-induced nearshore circulation patterns, wave-current interaction near tidal inlets, infra-gravity wave generation by groups of short waves, and wave transformation around artificial islands.<br />
<br />
As with many numerical models, BOUSS-2D can terminate or crash due to numerical instabilities. These are usually caused by problems related to the grid, the boundary conditions, or model parameters. The following lists describe common causes of instability and methods to correct them.<br />
<br />
=== Instability due to the grid/geometry ===<br />
* Model stability requires a low Courant number throughout the domain. SMS computes an approximate maximum time step to maintain a Courant number below 0.5. In some cases, it is desired to lower the time step even more. Additionally, some may want to truncate the computational domain to areas with depth above a specified minimum. Another option is to increase resolution by using smaller computational cells. Either of these options increase run time, so before applying them, look at the other causes of instability.<br />
* Abrupt changes in elevation from one cell to another in the computational domain could result in instabilities. It may be helpful to smooth the grid. (A smoothing command is available by right clicking on the grid object in the project explorer in the SMS interface.)<br />
* Computation nodes surrounded on three or four sides by land may be created during the grid creation process. These "isolated" cells may become unstable and generally don't have an impact on the wave climate. They can be converted to land cells.<br />
<br />
=== Instability due to the boundary conditions ===<br />
* Generally, avoid placing damping or porosity layers along structures and shorelines.<br />
* Wave makers are more stable on the edges of the domain. Therefore, generally speaking, the wave maker should be placed on the boundary of the domain in constant (or nearly constant) depth water. (The SMS interface offers to extend the grid and transition to constant depth if a wave maker is created in a location with more that 20% variation in depth.) This is especially true in real world applications where reflected waves are of no concern. Also, when simulating large waves, the greater stability of external wavemakers may be required.<br />
* Wave makers should be placed far enough from shore to avoid interaction between the wave maker and reflecting waves. This is because the external boundary behind the wave maker is treated as a vertical wall.<br />
* Exceptions, or applications in which internal wavemakers (i.e. wavemakers placed inside the domain) are recommended include:<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
* In applications with significant reflections from structures inside the computational domain. When reflected are caused by coastlines, structures, or bathymetry (reflected wave sources), the simulated seastate will become less uniform spatially, and the simulation may not reach a steady-state condition. The resulting wave field in such simulations will generally consist of nodes and anti-nodes that resemble a standing wave pattern, where waves appear to be bouncing back and forth inside the domain. If reflected waves cannot escape through boundaries of the modeling domain (or are constrained to exit the domain), a steady-state condition technically cannot be reached irrespective of the length of simulation. When reflected waves intercept external wavemakers, the extremes (lows and highs) in the calculated wavefield may keep building and can eventually lead to model instabilities.<br />
* Internal wavemakers should be used for finite domains and especially for limited area physical modeling studies, and with the above specified guidance.<br />
</blockquote><br />
* If wavemakers are placed on the interior of the domain, they should cross the entire domain to avoid potential "end effects", and have a damping layer placed behind (on the seaward side of) the internal wavemakers to absorb reflected waves. There should also be a gap (at least one non-damped cell) between the internal wavemaker and the damping layer located offshore. <br />
* [[Image:Damping Reflection Relationship-Fig 5- BOUSS-2D Technical Report.png|400px|right|Relationship between damping coefficient and width and reflection]]In the absence of laboratory or field data to calibrate damping and porous layers for an application, consider multiple simulations with a range of damping widths and/or coefficients. This graph from BOUSS-2D's technical report illustrates the variation of effective reflectivity given various damping coefficients and damping layer widths. To use this graph:<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
* Compute L (the wavelength for the incident wave).<br />
* Select a w/L ratio. Use this ratio to compute w (damping width).<br />
* Select an expected reflection percentage. Follow a horizontal line for this percentage on plot to intersect the graph for selected w/L ratio. Read associated damping coefficient from plot.<br />
* Note that the reflection coefficient is very sensitive to a change in damping coefficient when the coefficient is small (< 0.3) and much less sensitive when the coefficient is larger.<br />
* This process may require the damping parameters be changed when different wave conditions are considered.<br />
* It should be observed that this plot is for normally incident waves. Different reflection coefficients would be obtained for obliquely incident waves.<br />
</blockquote><br />
* Damping layers should be 5-10 cells wide.<br />
<br />
=== Instability due to model parameters ===<br />
* The model includes a Smagorinsky term to account for subgrid turbulence. If the turbulence is known, it is expected this term can be left at the default (0.0), however, it may be increased to increase stability. (This should be done with caution. Remember, don't suppress the wiggles, they are trying to say something.)<br />
<br />
==Test Cases==<br />
* '''[http://sms.aquaveo.com/BOUSS2D-test1-internal_wavemaker.zip Test 1]''' &ndash; Simple test demonstrating the use of an internal wavemaker.<br />
<br />
== External Links ==<br />
* [http://www.dtic.mil/cgi-bin/GetTRDoc?AD=ADA400294 BOUSS-2D User Manual]<br />
* CHL BOUSS-2D website [http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=Software;23]<br />
* May 2007 ERDC/CHL CHETN-I-73 Infra-Gravity Wave Input Toolbox (IGWT): User’s Guide [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-i-73.pdf]<br />
* May 2005 ERDC/CHL CHETN-I-70 BOUSS-2D Wave Model in SMS: 2. Tutorial with Examples [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-i-70.pdf]<br />
* Mar 2005 ERDC/CHL CHETN-I-69 BOUSS-2D Wave Model in the SMS: 1. Graphical Interface [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-i-69.pdf]<br />
* Aug 2011 Tsunami Modeling Example Study - A Joint Hydraulic/Structural Methodology for the Rehabilitation of the Crescent City Marina [http://dx.doi.org/10.1061/41190(422)28]<br />
* Apr 2014 Tsunami Modeling Article [http://www.nwyachting.com/2014/04/rebuilt-to-withstand-tsunami-crescent-city-inner-harbor-is-open/]<br />
<br />
== Related Topics ==<br />
* [[SMS:BOUSS-2D_Graphical_Interface|BOUSS-2D Graphical Interface]]<br />
* [[SMS:Cartesian Grid Module|Cartesian Grid Module]]<br />
* [[SMS:BOUSS-2D Files|BOUSS-2D Files]]<br />
* [[SMS:BOUSS-2D Graphical Interface|BOUSS-2D Model Control Dialog]] <br />
* [[SMS:BOUSS-2D Calculators|BOUSS-2D Calculators]]<br />
* [[SMS:CGWAVE|CGWAVE]]<br />
* [[SMS:SMS Models|SMS Models page]]<br />
* [[SMS:Spectral Energy|Spectral Energy]]<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
[[Category:Wave Modeling]]<br />
[[Category:BOUSS-2D]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=WMS:Where_Can_I_Get_Data%3F&diff=122254WMS:Where Can I Get Data?2017-04-12T20:33:06Z<p>Dharker: Removed broken links to aquaveo hosted pages</p>
<hr />
<div>(Click on ''italicized links'' to see a Flash instructional file)<br />
<br />
Aquaveo maintains a website with useful links to locations that distribute geospatial data such as DEM, land use, soils, images, and other data useful for hydrologic modeling. The website is periodically updated by Aquaveo employees. There are hundreds, if not thousands, of sites with geospatial data that are useful for modeling in WMS, but we have tried to distill from these the most significant sites. However, if you are aware of sites that might be more valuable, or as valuable, please contact technical support and let us know.<br />
<br />
Visit the [[GSDA:GSDA| GeoSpatial Data Acquisition (GSDA)]] website now for further help with downloading and preparing digital data for use in WMS.<br />
<br />
<br />
==Related Topics==<br />
* [[WMS:WMS|Getting Started]]<br />
<br />
<br />
{{WMSMain}}<br />
<br />
[[Category:Importing Data|W]]<br />
[[Category:WMS General Information|W]]<br />
[[Category:External Links]]<br />
<br />
{{stub}}</div>Dharkerhttps://www.xmswiki.com/index.php?title=WMS:Where_Can_I_Get_Data%3F&diff=122253WMS:Where Can I Get Data?2017-04-12T20:31:32Z<p>Dharker: removed outdated reference to BYU students</p>
<hr />
<div>(Click on ''italicized links'' to see a Flash instructional file)<br />
<br />
Aquaveo maintains a website with useful links to locations that distribute geospatial data such as DEM, land use, soils, images, and other data useful for hydrologic modeling. The website is periodically updated by Aquaveo employees. There are hundreds, if not thousands, of sites with geospatial data that are useful for modeling in WMS, but we have tried to distill from these the most significant sites. However, if you are aware of sites that might be more valuable, or as valuable, please contact technical support and let us know.<br />
<br />
Visit the [[GSDA:GSDA| GeoSpatial Data Acquisition (GSDA)]] website now for further help with downloading and preparing digital data for use in WMS.<br />
<br />
<br />
''[http://www.ems-i.com/WMS/captivate/DownloadDEM.html Download DEMs from the USGS NED site]''<br />
<br />
''[http://www.ems-i.com/WMS/captivate/SSURGO.html Download SSURGO data]''<br />
<br />
<br />
==Related Topics==<br />
* [[WMS:WMS|Getting Started]]<br />
<br />
<br />
{{WMSMain}}<br />
<br />
[[Category:Importing Data|W]]<br />
[[Category:WMS General Information|W]]<br />
[[Category:External Links]]<br />
<br />
{{stub}}</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:Automated_Parameter_Estimation&diff=122098GMS:Automated Parameter Estimation2017-04-03T22:53:26Z<p>Dharker: Noted availability of PEST</p>
<hr />
<div>{{MODFLOW Links}}<br />
{{Infobox Calibration}}<br />
An important part of any groundwater modeling exercise is the [[GMS:Model Calibration|model calibration]] process. In order for a groundwater model to be used in any type of predictive role, it must be demonstrated that the model can successfully simulate observed aquifer behavior. Calibration is a process wherein certain parameters of the model such as recharge and hydraulic conductivity are altered in a systematic fashion and the model is repeatedly run until the computed solution matches field-observed values within an acceptable level of accuracy.<br />
<br />
One of the tools provided in GMS for is automated parameter estimation. With automated parameter estimation, an external utility, sometimes called an "inverse model", is used to iteratively adjust a set of [[GMS:Parameters|parameters]] and repeatedly launch the model until the computed output matches field-observed values. Parameter estimation is used in conjunction with the [[GMS:Observations#Point Observations|point observations]] and the [[GMS:Observations#Flow Observations|flow observations]] and is available for all MODFLOW versions that come with GMS except for [[GMS:MODFLOW-LGR|MODFLOW-LGR]].<br />
<br />
Automated parameter estimation is supported in GMS for the [[GMS:MODFLOW|MODFLOW]] simulations using [[GMS:PEST|PEST]] a general purpose parameter estimation utility developed by John Doherty of Watermark Computing. <br />
<br />
Inverse models should only be used carefully and with a full understanding of the assumptions, equations, and methods involved. It is suggested that the user read the available documentation on the inverse model being used. Only the steps involved in setting up an inverse model are described in this document.<br />
<br />
==Basic Steps==<br />
The basic steps involved in using an inverse model for parameter estimation are follows:<br />
<br />
=== 1. Create a Working MODFLOW Model ===<br />
The first step is to create a MODFLOW model and run a simulation. Before launching the inverse model, it's necessary to have a MODFLOW model that successfully converges and it's necessary to determine a good set of starting values for the parameters. Once there is a solution it is also a good idea to copy the computed heads from the solution to the starting heads array. This ensures that as the inverse model modifies the parameters and runs MODFLOW repeatedly, it is more likely that MODFLOW will quickly converge each time it is launched.<br />
<br />
=== 2. Enter the Observations ===<br />
Once there is a working MODFLOW model, enter the head and flux observations. [[GMS:Observations#Point Observations|Head observations]] are entered as points using an observation coverage in the Map module. [[GMS:Observations#Flow Observations|Flow observations]] are assigned directly to arcs and polygons in source/sink coverages. Each of the observations is assigned a [[GMS:Observations#Observation Weights|weight]] that is saved to the inverse input files.<br />
<br />
=== 3. Turn on the Inverse Model ===<br />
Select an inverse model. Bring up the [[GMS:Global Options/Basic Package|''Global Options'']] dialog and select either the Parameter Estimation or Stochastic Inverse Model button depending on whether a stochastic simulation is being run.<br />
<br />
=== 4. Parameterize the model ===<br />
The next step is to parameterize the model. See the [[GMS:Parameters#Parameterizing_the_model|Parameters]] page for more details.<br />
<br />
=== 5. Create a Parameter List ===<br />
The next step is to create the parameter list. See the [[GMS:Parameters#Create_a_parameter_list|Parameters]] page for details.<br />
<br />
=== 6. Set parameter estimation options ===<br />
Once the parameter list is set up, the user may wish to edit the general [[GMS:PEST Dialog|''Parameter Estimation'']] options. These options include the output control and convergence criteria.<br />
<br />
=== 7. Edit the Group Weight Multipliers ===<br />
The [[GMS:Observations#Group Weight Multipliers|group weight multipliers]] can be edited to adjust the relative weight of the head and flux observations.<br />
<br />
=== 8. Edit the PEST ASP Package ===<br />
Edit the MODFLOW [[GMS:PEST ASP Package|PEST ASP Package]] if necessary in order to ensure a stable solution.<br />
<br />
=== 9. Save and Run MODFLOW Model ===<br />
Once all of the inverse model options have been set, the next step is to save the MODFLOW model using the '''Save''' or '''Save As''' command in the ''File'' menu. Next, run MODFLOW and the inverse model will run with MODFLOW. The inverse model will then be launched in a separate window or the model wrapper in which the user should see information relating to the MODFLOW runs and the status of the objective function. Depending on the problem, the inverse model may take anywhere from several minutes to several hours (or days) to run to completion. When the inverse process is completed successfully, GMS automatically launches a MODFLOW forward run with the optimal values computed by the inverse model. Thus, the solution will reflect the optimal values computed by the inverse model.<br />
<br />
=== 10. Viewing the Optimal values ===<br />
When the inverse model is finished, it writes out a text file containing the set of parameter values corresponding to the minimum calibration error. These values can be viewed with the '''Import Optimal Values''' button. This copies the optimal parameter values to the ''Starting Value'' field in the ''Parameter List''.<br />
<br />
==Sensitivity Analysis==<br />
At each PEST iteration, PEST computes the sensitivities of each of the parameters. This information is available in the "''model''.sen" file (where ''model'' is the name of the MODFLOW model). PEST records the composite sensitivity and the relative composite sensitivity of each parameter in this file. This information is useful in determining which parameters have the greatest effect on the model as well as which parameters have the least effect on the model. Thus, the "insensitive" parameters can be removed or held constant in a subsequent PEST run.<br />
<br />
For a more detailed description of parameter sensitivity see section 5.3.2 of the PEST manual.<br />
<br />
==PEST Dialog==<br />
Options affecting parameter estimation can be changed via the [[GMS:PEST Dialog|''PEST'' dialog]].<br />
<br />
==Parallel PEST==<br />
<br />
The PEST model can be run with parallel processing across one or multiple machines with the Parallel PEST Utility. Running across multiple machines requires setup outside of GMS with PSLAVE. More information about Parallel PEST can be found in the [http://www.pesthomepage.org/getfiles.php?file=newpestman1.pdf PEST Manual Part I] starting on page 222 from the [http://www.pesthomepage.org/Downloads.php PEST Downloads page].<br />
<br />
==See also==<br />
<br />
[[GMS:Model Calibration|Model Calibration]]<br />
<br />
{{Navbox GMS}}<br />
[[Category:MODFLOW]]<br />
[[Category:Calibration]]<br />
[[Category:PEST]]<br />
[[Category:Parameters]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:SEAWAT&diff=122097GMS:SEAWAT2017-03-31T20:58:17Z<p>Dharker: Noted type of head values output by v4 and v2 per a customer's questions</p>
<hr />
<div>{{Infobox Model |<br />
|name= SEAWAT<br />
|model_type= 3D Flow and Transport Model<br />
|developer= [https://water.usgs.gov/ogw/seawat/ USGS]<br />
|documentation= [http://gmsdocs.aquaveo.com/seawatv4.pdf SEAWAT Manual]<br />
|tutorials= [[GMS:Tutorials#Models|SEAWAT Tutorials]]<br />
}}<br />
<br />
SEAWAT is a three dimensional variable density groundwater flow and transport model developed by the USGS based on [[GMS:MODFLOW|MODFLOW]] and [[GMS:MT3DMS|MT3DMS]]. SEAWAT v4 is based on MODFLOW 2000 and MT3DMS 5.2. SEAWAT includes two additional packages: Variable-Density Flow (VDF) and Viscosity (VSC). A complete description of SEAWAT is beyond the scope of this reference manual. It is assumed that the reader has a basic knowledge of SEAWAT and has read the SEAWAT documentation.<br />
<br />
GMS supports SEAWAT as a pre- and post-processor. The interface to SEAWAT relies on the interface to MODFLOW and MT3DMS. The input data for SEAWAT is generated by GMS and saved to a set of files including a MODFLOW model, an MT3D model if transport is used, and a SEAWAT model pointing to the MODFLOW and MT3D model's package files. These files are then read by SEAWAT and executed, and real/actual head values are output by SEAWAT v4 (whereas SEAWAT v2 outputs equivalent freshwater heads). SEAWAT uses the MODFLOW and MT3D interfaces for boundary condition display and for post-processing which explains why many of the output files are saved as MODFLOW or MT3DMS files as shown in the ''Output Files'' table below.<br />
<br />
The SEAWAT model can be added to a [http://www.aquaveo.com/software/gms-pricing paid edition] of GMS.<br />
[[Category:Link to Store]]<br />
<br />
==SEAWAT Files==<br />
<br />
Below are tables of some of the available input and output files for SEAWAT.<br />
<br />
* For more information on these files see their respective MODFLOW, MT3DMS, and SEAWAT manuals<br />
<br />
{| class="wikitable" <br />
|+'''Input Files'''<br />
!width="40" align="center"|Name<br />
!width="250" align="center"|Description<br />
|-<br />
|SWN||SEAWAT Name Control File<br />
|-<br />
|VDF||SEAWAT Variable-Density Flow Process Input File<br />
|-<br />
|VSC||SEAWAT Viscosity Package Input File<br />
|-<br />
|GLO||MODFLOW Global Listing File<br />
|-<br />
|OUT||MODFLOW Output File<br />
|-<br />
|HED||MODFLOW HDF5 Head File<br />
|-<br />
|CCF||MODFLOW Cell-to-Cell Flow File<br />
|-<br />
|LMT||MODFLOW Link-MT3DMS Package<br />
|-<br />
|OBS||MODFLOW Main Observation Process input file<br />
|-<br />
|CHOB||MODFLOW Constant-Head Flow Observation Input File<br />
|-<br />
|ASP||MODFLOW Advanced Spacial Parameterization File<br />
|-<br />
|DIS||MODFLOW Discretization File<br />
|-<br />
|BA6||MODFLOW Basic Package<br />
|-<br />
|LPF||MODFLOW Layer Property Flow Package<br />
|-<br />
|OC||MODFLOW Process Output Control Option<br />
|-<br />
|RCH||MODFLOW Recharge Package<br />
|-<br />
|WEL||MODFLOW Process Well Package<br />
|-<br />
|CHD||MODFLOW Time-Variant Specified-Head Package<br />
|-<br />
|PCG||MODFLOW Preconditioned Conjugate-Gradient Package<br />
|-<br />
|BTN||MT3DMS Basic Transport Package<br />
|-<br />
|ADV||MT3DMS Advection Package<br />
|-<br />
|SSM||MT3DMS Sink/Source Mixing Package<br />
|-<br />
|GCG||MT3DMS Generalized Conjugate-Gradient Solver Package<br />
|}<br />
<br />
{| class="wikitable"<br />
|+'''Output Files'''<br />
!align="center" width="50"|Name<br />
!width="350"|Description<br />
|-<br />
|CBB||SEAWAT Binary Cell-By-Cell Flow File<br />
|-<br />
|HDS||SEAWAT Head File<br />
|-<br />
|LIST||SEAWAT List File<br />
|-<br />
|GLO||SEAWAT Global Listing File<br />
|-<br />
|_W||MODFLOW Weighted Residuals Data Exchange File<br />
|-<br />
|_WW||MODFLOW Weighted Equivalents & Weighted Observation<br />
|-<br />
|_WS||MODFLOW Weighted Residuals and Simulated Equivalents<br />
|-<br />
|_R||MODFLOW Unweighted Residuals Data Exchange File<br />
|-<br />
|_OS||MODFLOW Observed Values and Simulated Equivalents File<br />
|-<br />
|_B||MODFLOW Data Exchange File<br />
|-<br />
|_NM||MODFLOW Weighted Residuals and Probability Plotting file<br />
|-<br />
|OUT||MODFLOW Output File<br />
|-<br />
|CCF||MODFLOW Cell-to-Cell Flow File<br />
|-<br />
|GLO||MODFLOW Global Listing File<br />
|-<br />
|HED||MODFLOW HDF5 Head File<br />
|-<br />
|UCN||MT3DMS Unformatted Concentration File<br />
|-<br />
|CNF||MT3DMS Spatial Configuration File<br />
|-<br />
|P00||Unsuccessful Termination Error File<br />
|-<br />
|}<br />
<br />
==Importing a SEAWAT Simulation==<br />
An existing SEAWAT v4 model can be imported into GMS by opening the name file which must have a ".nam" extension. Upon opening the name file, GMS uses the name file to determine if the simulation is MODFLOW-2000, MODFLOW-2005, or a SEAWAT simulation based on the packages included. <br />
<br />
Once the import is complete, if the model includes transport packages or the VDF or VSC packages then a SEAWAT model is automatically created inside GMS. <br />
<br />
If the model only includes MODFLOW packages, then the SEAWAT model needs to be created by enabling the SEAWAT model interface by selecting ''SEAWAT'' in the ''Model Interfaces'' dialog available under the [[GMS:Edit Menu|''Edit'']] menu, and then selecting '''New Simulation''' under the [[GMS:SEAWAT Commands|''SEAWAT'']] menu.<br />
<br />
==SEAWAT Links==<br />
<br />
*[[GMS:Building a SEAWAT Model|Building a SEAWAT Model]]<br />
*[[GMS:SEAWAT Global Options Dialog|SEAWAT Global Options Dialog]]<br />
*[[GMS:SEAWAT Packages|SEAWAT Packages]]<br />
*[[GMS:MODFLOW with HDF5|MODFLOW with HDF5]]<br />
<br />
==SEAWAT External Links==<br />
* [http://water.usgs.gov/ogw/seawat/ SEAWAT website]<br />
<br />
<br />
{{Navbox GMS}}<br />
<br />
<br />
[[Category:SEAWAT]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:SEAWAT&diff=121959GMS:SEAWAT2017-03-29T22:47:03Z<p>Dharker: linked seawat webpage</p>
<hr />
<div>{{Infobox Model |<br />
|name= SEAWAT<br />
|model_type= 3D Flow and Transport Model<br />
|developer= [https://water.usgs.gov/ogw/seawat/ USGS]<br />
|documentation= [http://gmsdocs.aquaveo.com/seawatv4.pdf SEAWAT Manual]<br />
|tutorials= [[GMS:Tutorials#Models|SEAWAT Tutorials]]<br />
}}<br />
<br />
SEAWAT is a three dimensional variable density groundwater flow and transport model developed by the USGS based on [[GMS:MODFLOW|MODFLOW]] and [[GMS:MT3DMS|MT3DMS]]. SEAWAT v4 is based on MODFLOW 2000 and MT3DMS 5.2. SEAWAT includes two additional packages: Variable-Density Flow (VDF) and Viscosity (VSC). A complete description of SEAWAT is beyond the scope of this reference manual. It is assumed that the reader has a basic knowledge of SEAWAT and has read the SEAWAT documentation.<br />
<br />
GMS supports SEAWAT as a pre- and post-processor. The interface to SEAWAT relies on the interface to MODFLOW and MT3DMS. The input data for SEAWAT is generated by GMS and saved to a set of files including a MODFLOW model, an MT3D model if transport is used, and a SEAWAT model pointing to the MODFLOW and MT3D model's package files. These files are then read by SEAWAT and executed. SEAWAT uses the MODFLOW and MT3D interfaces for boundary condition display and for post-processing which explains why many of the output files are saved as MODFLOW or MT3DMS files as shown in the ''Output Files'' table below.<br />
<br />
The SEAWAT model can be added to a [http://www.aquaveo.com/software/gms-pricing paid edition] of GMS.<br />
[[Category:Link to Store]]<br />
<br />
==SEAWAT Files==<br />
<br />
Below are tables of some of the available input and output files for SEAWAT.<br />
<br />
* For more information on these files see their respective MODFLOW, MT3DMS, and SEAWAT manuals<br />
<br />
{| class="wikitable" <br />
|+'''Input Files'''<br />
!width="40" align="center"|Name<br />
!width="250" align="center"|Description<br />
|-<br />
|SWN||SEAWAT Name Control File<br />
|-<br />
|VDF||SEAWAT Variable-Density Flow Process Input File<br />
|-<br />
|VSC||SEAWAT Viscosity Package Input File<br />
|-<br />
|GLO||MODFLOW Global Listing File<br />
|-<br />
|OUT||MODFLOW Output File<br />
|-<br />
|HED||MODFLOW HDF5 Head File<br />
|-<br />
|CCF||MODFLOW Cell-to-Cell Flow File<br />
|-<br />
|LMT||MODFLOW Link-MT3DMS Package<br />
|-<br />
|OBS||MODFLOW Main Observation Process input file<br />
|-<br />
|CHOB||MODFLOW Constant-Head Flow Observation Input File<br />
|-<br />
|ASP||MODFLOW Advanced Spacial Parameterization File<br />
|-<br />
|DIS||MODFLOW Discretization File<br />
|-<br />
|BA6||MODFLOW Basic Package<br />
|-<br />
|LPF||MODFLOW Layer Property Flow Package<br />
|-<br />
|OC||MODFLOW Process Output Control Option<br />
|-<br />
|RCH||MODFLOW Recharge Package<br />
|-<br />
|WEL||MODFLOW Process Well Package<br />
|-<br />
|CHD||MODFLOW Time-Variant Specified-Head Package<br />
|-<br />
|PCG||MODFLOW Preconditioned Conjugate-Gradient Package<br />
|-<br />
|BTN||MT3DMS Basic Transport Package<br />
|-<br />
|ADV||MT3DMS Advection Package<br />
|-<br />
|SSM||MT3DMS Sink/Source Mixing Package<br />
|-<br />
|GCG||MT3DMS Generalized Conjugate-Gradient Solver Package<br />
|}<br />
<br />
{| class="wikitable"<br />
|+'''Output Files'''<br />
!align="center" width="50"|Name<br />
!width="350"|Description<br />
|-<br />
|CBB||SEAWAT Binary Cell-By-Cell Flow File<br />
|-<br />
|HDS||SEAWAT Head File<br />
|-<br />
|LIST||SEAWAT List File<br />
|-<br />
|GLO||SEAWAT Global Listing File<br />
|-<br />
|_W||MODFLOW Weighted Residuals Data Exchange File<br />
|-<br />
|_WW||MODFLOW Weighted Equivalents & Weighted Observation<br />
|-<br />
|_WS||MODFLOW Weighted Residuals and Simulated Equivalents<br />
|-<br />
|_R||MODFLOW Unweighted Residuals Data Exchange File<br />
|-<br />
|_OS||MODFLOW Observed Values and Simulated Equivalents File<br />
|-<br />
|_B||MODFLOW Data Exchange File<br />
|-<br />
|_NM||MODFLOW Weighted Residuals and Probability Plotting file<br />
|-<br />
|OUT||MODFLOW Output File<br />
|-<br />
|CCF||MODFLOW Cell-to-Cell Flow File<br />
|-<br />
|GLO||MODFLOW Global Listing File<br />
|-<br />
|HED||MODFLOW HDF5 Head File<br />
|-<br />
|UCN||MT3DMS Unformatted Concentration File<br />
|-<br />
|CNF||MT3DMS Spatial Configuration File<br />
|-<br />
|P00||Unsuccessful Termination Error File<br />
|-<br />
|}<br />
<br />
==Importing a SEAWAT Simulation==<br />
An existing SEAWAT v4 model can be imported into GMS by opening the name file which must have a ".nam" extension. Upon opening the name file, GMS uses the name file to determine if the simulation is MODFLOW-2000, MODFLOW-2005, or a SEAWAT simulation based on the packages included. <br />
<br />
Once the import is complete, if the model includes transport packages or the VDF or VSC packages then a SEAWAT model is automatically created inside GMS. <br />
<br />
If the model only includes MODFLOW packages, then the SEAWAT model needs to be created by enabling the SEAWAT model interface by selecting ''SEAWAT'' in the ''Model Interfaces'' dialog available under the [[GMS:Edit Menu|''Edit'']] menu, and then selecting '''New Simulation''' under the [[GMS:SEAWAT Commands|''SEAWAT'']] menu.<br />
<br />
==SEAWAT Links==<br />
<br />
*[[GMS:Building a SEAWAT Model|Building a SEAWAT Model]]<br />
*[[GMS:SEAWAT Global Options Dialog|SEAWAT Global Options Dialog]]<br />
*[[GMS:SEAWAT Packages|SEAWAT Packages]]<br />
*[[GMS:MODFLOW with HDF5|MODFLOW with HDF5]]<br />
<br />
==SEAWAT External Links==<br />
* [http://water.usgs.gov/ogw/seawat/ SEAWAT website]<br />
<br />
<br />
{{Navbox GMS}}<br />
<br />
<br />
[[Category:SEAWAT]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=SMS:PTM&diff=121958SMS:PTM2017-03-29T21:38:00Z<p>Dharker: /* PTM Coverages */ Linked the PTM Files page</p>
<hr />
<div>{{SMS Infobox Model |<br />
|name= PTM<br />
|model_type= Lagrangian particle tracker designed to allow simulating particle transport processes.<br />
|developer= <br />
Neil J. MacDonald, Ph.D. <br /> <br />
Michael H. Davies, M.Sc., Ph.D., P.Eng. <br /> <br />
[http://www.coldwater-consulting.com Coldwater Consulting Ltd]<br />
|web_site= [https://web-beta.archive.org/web/20151031123850/http://el.erdc.usace.army.mil/dots/doer/ptm.html PTM web site]<br />
|tutorials= <br />
Models Section<br />
* PTM (Pending)<br />
}}<br />
<br />
The Particle Tracking Model (PTM) is a Lagrangian particle tracker designed to allow simulating particle transport processes. PTM is funded through two US Army Corps of Engineers Engineering Research and Development Center (ERDC) research programs, the Coastal Inlets Research Program (CIRP) and the Dredging Operations and Environmental Research (DOER) Program.<br />
<br />
The PTM model can be added to a [http://www.aquaveo.com/software/sms-pricing paid edition] of SMS.<br />
[[Category:Link to Store]]<br />
<br />
==Functionality==<br />
PTM has been developed for application to dredging and coastal projects including dredged material dispersion and fate, sediment pathway and fate, and constituent transport. The model contains algorithms that appropriately represent transport, settling, deposition, mixing, and resuspension processes in nearshore wave/current conditions. It uses waves and currents developed through other models and input directly to PTM as forcing functions.<br />
<br />
===Using the Model / Practical Notes===<br />
* The horizontal and vertical coordinates used for all PTM input files must be in meters. [[Geographic_Coordinate_System|Geographic Coordinates]] cannot be used since it is a latitude/longitude system defined in decimal degrees.<br />
* If last step trap is checked, the traps will not become active until the last time step.<br />
<br />
==How do I use PTM?==<br />
The SMS [[SMS:Tutorials|tutorials]] are a good place to start learning to use SMS and associated models. A tutorial is available for PTM.<br />
<br />
== Graphical Interface == <br />
SMS provides a graphical interface that is designed to visualize the projects being created, easily modify project parameters, and view the solutions produced by the PTM model. See [[SMS:PTM Graphical Interface|PTM Graphical Interface]] for more information.<br />
<br />
The [[SMS:PTM Graphical Interface|PTM Graphical Interface]] contains tools to create and edit an PTM simulation. The simulation consists of a geometric definition of the sources, traps, and a set of numerical parameters. The parameters define the hydrodynamic input and options pertinent to the model.<br />
<br />
The interface is accessed by selecting the [[SMS:Particle Module|Particle Module]] and setting the current model to PTM. If a simulation has already been created or an existing simulation read, the particle object will exist in the [[SMS:Project Explorer|Project Explorer]] and selecting that object will make the Particle module active and set the model to PTM. See the [[SMS:Particle Module|Particle Module]] documentation for guidance on visualizing results.<br />
<br />
The interface consists of the [[SMS:Particle Module Menus|Particle Module Menus]] and [[SMS:Particle Module#Particle Module Tools|tools]] augmented by the [[SMS:PTM Graphical Interface#PTM Menu|PTM Menu]]. See [[SMS:PTM Graphical Interface|PTM Graphical Interface]] for more information.<br />
<br />
===PTM Menu===<br />
The ''PTM'' menu becomes active when a PTM model coverage has been created. For more information see [[SMS:PTM Graphical Interface|PTM Graphical Interface]].<br />
<br />
===Tools===<br />
PTM sources and traps are created in the [[SMS:Map Module|Map Module]] as [[SMS:Feature Objects Types|feature objects]] using the [[SMS:Map Module Tools|Map Module Tools]].<br />
<br />
[[Category:SMS Tools|PTM]]<br />
<br />
===PTM Coverages===<br />
In the SMS interface, two types of [[SMS:Coverages|coverages]] can be applied to a PTM simulation. These include:<br />
* [[SMS:PTM Sources|PTM Source/Trap Coverage]] &ndash; Used to define input for a PTM simulation. <br />
* [[SMS:PTM Gage Coverage|PTM Gage Coverage]] &ndash; Used to view time series of output data computed by the PTM engine.<br />
[[Category:SMS Coverages|P]]<br />
<br />
==PTM Files==<br />
See the [[SMS:PTM Files|PTM Files]] page for a list of input and output files with a brief description.<br />
<br />
==Theoretical Basis / Mathematical Details==<br />
Please refer to the model developer provided documentation listed in the [[SMS:PTM#External Links|external links]] section.<br />
<br />
==Numeric Engine Background==<br />
Please refer to the model developer provided documentation listed in the [[SMS:PTM#External Links|external links]] section.<br />
<br />
== General Steps to Build a PTM Model ==<br />
# Open SMS<br />
# Although not required, it is generally easier to visualize the model if reading in the hydrodynamic solution<br />
# Convert the horizontal and vertical coordinates to meters. PTM cannot be run in [[Geographic Coordinate System|Geographic Coordinates]] since it is a latitude/longitude system defined in decimal degrees.<br />
# Switch to the [[SMS:Map Module|Map Module]]<br />
# Create a PTM type [[SMS:Coverages|coverage]]<br />
# Create [[SMS:PTM_Sources|sources]] and [[SMS:PTM Traps|traps]] using feature [[SMS:Feature Objects Types#Points|points]], [[SMS:Feature Objects Types#Arcs|arcs]], and [[SMS:Feature Objects Types#Polygons|polygons]]<br />
# [[SMS:Particle Module|Switch to the Particle Module]]<br />
# Use the [[SMS:PTM Graphical Interface#PTM Menu|''PTM'' menu]] to create a new PTM simulation<br />
# Use the [[SMS:PTM Graphical Interface#PTM Menu|''PTM'' menu]] to open the [[SMS:PTM_Model_Control|''PTM Model Control'' dialog]]<br />
## Specify input and output parameters in the model control<br />
## Click on the '''Create input file(s) from data''' button to create a [[SMS:PTM Sediment File|native sediment file]], and hydrodynamic input files if needed. You may use mesh, water surface elevation, and velocity data from another model (ADCIRC, ADH, RMA2) to create the necessary fort.15 and/or *.h5 file.<br />
# Save the simulation<br />
# Use the [[SMS:PTM Graphical Interface#PTM Menu|''PTM'' menu]] to perform a [[SMS:PTM Graphical Interface#PTM Model Check|model check]]<br />
# Use the [[SMS:PTM Graphical Interface#PTM Menu|''PTM'' menu]] to run PTM<br />
<br />
== General Post-Processing Steps ==<br />
# Use the [[SMS:Particle Module Display Options|''display options'']] to visualize the results<br />
# Use the [[SMS:Data Calculator|''Data Calculator'']] or [[SMS:Particle Module Create Datasets|''Create Datasets'']] dialog to create particle datasets<br />
# Create a [[SMS:Cartesian_Grid_Module|Cartesian Grid]] and use the [[SMS:Particle Module Compute Grid Datasets|''Create Grid Datasets'']] dialog to create Cartesian grid datasets<br />
# Review the [[SMS:PTM Files#Output Files|Trap Output files]] in an ASCII file viewer<br />
<br />
==External Links==<br />
* U.S. Army Corps of Engineers DOER PTM website [https://web-beta.archive.org/web/20151031123850/http://el.erdc.usace.army.mil/dots/doer/ptm.html]<br />
* 2005 ERDC TN-DOER-D4 Particle Tracking Model (PTM) in the SMS: I. Graphical Interface [http://smsdocs.aquaveo.com/PTM_DOERD4.PDF]<br />
* 2005 ERDC TN-DOER-D5 Particle Tracking Model (PTM): II. Overview of Features and Capabilities [https://web-beta.archive.org/web/20150914221305/http://el.erdc.usace.army.mil/elpubs/pdf/doerd5.pdf]<br />
* 2005 ERDC TN-DOER-D6 Particle Tracking Model (PTM) in the SMS: III. Tutorial with Examples [http://smsdocs.aquaveo.com/PTM_DOERD6.PDF]<br />
* 2006 ERDC/CHL TR-06-20 PTM: Particle Tracking Model Report 1: Model Theory, Implementation, and Example Applications [https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0ahUKEwjCtbn1vobRAhUFrlQKHYI6C9gQFggaMAA&url=http%3A%2F%2Fwww.dtic.mil%2Fcgi-bin%2FGetTRDoc%3FAD%3DADA455437&usg=AFQjCNEP98xgnAnCZ6-Xnpb5lwRYyRoY2Q&bvm=bv.142059868,d.cGw]<br />
* 2008 ERDC/CHL CHETN-IV-71 Particle Tracking Model (PTM) in the SMS 10: IV. Link to Coastal Modeling System [https://www.researchgate.net/profile/Alan_Zundel/publication/228703967_Particle_Tracking_Model_PTM_in_the_SMS_10_IV_Link_to_Coastal_Modeling_System/links/0912f509526ef1aacc000000.pdf]<br />
* 2007 The Particle Tracking Model: Description and Processes [https://web-beta.archive.org/web/20090821060228/http://el.erdc.usace.army.mil/dots/doer/pdf/LackeyandMcDonald_2007.pdf]<br />
* Application of the Particle Tracking Model to Predict the Farfield Fate of:<br />
** 2007 Sediment Suspended by Nearshore Dredging and Placement, Brunswick, GA [https://web-beta.archive.org/web/20090821060140/http://el.erdc.usace.army.mil/dots/doer/pdf/GAILANIetal_2008.pdf]<br />
** 2008 Dredged Suspended Sediment at the Willamette River [https://web-beta.archive.org/web/20090821060112/http://el.erdc.usace.army.mil/dots/doer/pdf/LackeyandSmith_2008.pdf]<br />
* 2009 Assessment of Dredging-Induced Sedimentation on Winter Flounder Spawning habitat [https://web-beta.archive.org/web/20090821060202/http://el.erdc.usace.army.mil/dots/doer/pdf/LackeyKimClarke_WEDA.pdf]<br />
* Humboldt Bay PTM with CMS-Flow Quadtree Grid [http://cirp.usace.army.mil/techtransfer/workshops/nap12/Presentation/PTM_022112.pdf]<br />
* 2012 Use of the PTM with CMS Quadtree Grids[http://acwc.sdp.sirsi.net/client/search/asset/1006682]<br />
[[Category:Needs Update]] <!--Links don't work--><br />
<br />
==Related Topics==<br />
*[[SMS:Particle Module|Particle Module]]<br />
*[[SMS:Mesh Module|Mesh Module]]<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
<br />
[[Category:SMS Particle|P]]<br />
[[Category:PTM|P]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=SMS:PTM_Files&diff=121957SMS:PTM Files2017-03-29T21:26:00Z<p>Dharker: /* Input Files */ Removed mistaken blockquote fixed version note</p>
<hr />
<div>Input and Output files for [[SMS:PTM|PTM]].<br />
<br />
== Input Files ==<br />
===Required files===<br />
<br />
* '''[[SMS:PTM Control File|Program Control File]]''' (*.pcf) &ndash; Run time instruction for the model.<br />
* '''Mesh file''' &ndash; Bathymetry and boundary information for the model.<br />
PTM Version 1.0 supports [[SMS:ADCIRC|ADCIRC]] compatible three-noded triangular finite element mesh files ([[SMS:ADCIRC Mesh|fort.14 or .grd]]). SMS contains tools to convert mesh files to this format.<br />
* '''Hydrodynamic input file''' &ndash; Time varying water surface elevation and depth-averaged velocities.<br />
Versions of SMS including 9.2 and later supports XMDF (*.h5) format hydrodynamic files. SMS contains tools to convert mesh output files to this format.<br />
* '''[[SMS:PTM Sediment File|Native sediment file]]''' &ndash; Native sediments over the domain defined by the mesh file.<br />
<br />
===Optional files===<br />
<br />
* '''[[SMS:PTM Source File|Sediment source file]]''' &ndash; The sediment sources in the simulation.<br />
* '''[[SMS:PTM Trap File|Trap file]]''' (*.trap) &ndash; Locations where information about the simulation should be extracted.<br />
* '''[[SMS:PTM Wave File|Wave file(s)]]''' &ndash; Time varying information about the wave field.<br />
* '''Wave breaking file(s)''' &ndash; Time varying information about wave breaking.<br />
* '''[[SMS:PTM Boundary Condition File|PTM Boundary Condition file]]''' &ndash; Describes the wet/dry interface.<br />
<br />
== Output Files ==<br />
The output files use the name given after the keyword :OUTPUT_PREFIX in the [[SMS:PTM Control File|program control file]] and are appended with the following endings:<br />
* '''Mapping Output File''' (*_maps.h5) &ndash; Behavior of the flow and native sediments over the whole domain incremented by time.<br />
* '''Parcel Data File''' (*_particles.h5) &ndash; Parcel information incremented by time.<br />
* '''Echo file''' (*_input.out) &ndash; ASCII file echoing the input parameters of the simulation.<br />
* '''Neighbor file''' (*.neighbors) &ndash; Contains mesh connectivity information. Once generated, can be specified as an input file to avoid regenerating for subsequent simulations with a given mesh. If the mesh changes, the neighbor file should be regenerated.<br />
* '''Trap Count File''' (*_count.out) &ndash; Contains the time and ID of particles entering a trap<br />
* '''Trap Residency File''' (*_residency.out) &ndash; Contains the time particles enter and exit a trap and the total time spent in the trap.<br />
<br />
==Related Topics==<br />
* [[SMS:PTM|PTM]]<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
<br />
[[Category:PTM|F]]<br />
[[Category:SMS File Formats|P]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=SMS:PTM_Files&diff=121956SMS:PTM Files2017-03-29T21:10:37Z<p>Dharker: /* Optional files */ added file extension</p>
<hr />
<div>Input and Output files for [[SMS:PTM|PTM]].<br />
<br />
== Input Files ==<br />
===Required files===<br />
<br />
* '''[[SMS:PTM Control File|Program Control File]]''' (*.pcf) &ndash; Run time instruction for the model.<br />
* '''Mesh file''' &ndash; Bathymetry and boundary information for the model.<br />
PTM Version 1.0 supports [[SMS:ADCIRC|ADCIRC]] compatible three-noded triangular finite element mesh files ([[SMS:ADCIRC Mesh|fort.14 or .grd]]). SMS contains tools to convert mesh files to this format.</blockquote><br />
* '''Hydrodynamic input file''' &ndash; Time varying water surface elevation and depth-averaged velocities.<br />
The SMS 9.2 interface to PTM Version 1.0 supports XMDF (*.h5) format hydrodynamic files. SMS contains tools to convert mesh output files to this format.<br />
* '''[[SMS:PTM Sediment File|Native sediment file]]''' &ndash; Native sediments over the domain defined by the mesh file.<br />
<br />
===Optional files===<br />
<br />
* '''[[SMS:PTM Source File|Sediment source file]]''' &ndash; The sediment sources in the simulation.<br />
* '''[[SMS:PTM Trap File|Trap file]]''' (*.trap) &ndash; Locations where information about the simulation should be extracted.<br />
* '''[[SMS:PTM Wave File|Wave file(s)]]''' &ndash; Time varying information about the wave field.<br />
* '''Wave breaking file(s)''' &ndash; Time varying information about wave breaking.<br />
* '''[[SMS:PTM Boundary Condition File|PTM Boundary Condition file]]''' &ndash; Describes the wet/dry interface.<br />
<br />
== Output Files ==<br />
The output files use the name given after the keyword :OUTPUT_PREFIX in the [[SMS:PTM Control File|program control file]] and are appended with the following endings:<br />
* '''Mapping Output File''' (*_maps.h5) &ndash; Behavior of the flow and native sediments over the whole domain incremented by time.<br />
* '''Parcel Data File''' (*_particles.h5) &ndash; Parcel information incremented by time.<br />
* '''Echo file''' (*_input.out) &ndash; ASCII file echoing the input parameters of the simulation.<br />
* '''Neighbor file''' (*.neighbors) &ndash; Contains mesh connectivity information. Once generated, can be specified as an input file to avoid regenerating for subsequent simulations with a given mesh. If the mesh changes, the neighbor file should be regenerated.<br />
* '''Trap Count File''' (*_count.out) &ndash; Contains the time and ID of particles entering a trap<br />
* '''Trap Residency File''' (*_residency.out) &ndash; Contains the time particles enter and exit a trap and the total time spent in the trap.<br />
<br />
==Related Topics==<br />
* [[SMS:PTM|PTM]]<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
<br />
[[Category:PTM|F]]<br />
[[Category:SMS File Formats|P]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=SMS:PTM_Files&diff=121955SMS:PTM Files2017-03-29T21:07:10Z<p>Dharker: Standardized formatting of lists of files for readability</p>
<hr />
<div>Input and Output files for [[SMS:PTM|PTM]].<br />
<br />
== Input Files ==<br />
===Required files===<br />
<br />
* '''[[SMS:PTM Control File|Program Control File]]''' (*.pcf) &ndash; Run time instruction for the model.<br />
* '''Mesh file''' &ndash; Bathymetry and boundary information for the model.<br />
PTM Version 1.0 supports [[SMS:ADCIRC|ADCIRC]] compatible three-noded triangular finite element mesh files ([[SMS:ADCIRC Mesh|fort.14 or .grd]]). SMS contains tools to convert mesh files to this format.</blockquote><br />
* '''Hydrodynamic input file''' &ndash; Time varying water surface elevation and depth-averaged velocities.<br />
The SMS 9.2 interface to PTM Version 1.0 supports XMDF (*.h5) format hydrodynamic files. SMS contains tools to convert mesh output files to this format.<br />
* '''[[SMS:PTM Sediment File|Native sediment file]]''' &ndash; Native sediments over the domain defined by the mesh file.<br />
<br />
===Optional files===<br />
<br />
* '''[[SMS:PTM Source File|Sediment source file]]''' &ndash; The sediment sources in the simulation.<br />
* '''[[SMS:PTM Trap File|Trap file]]''' &ndash; Locations where information about the simulation should be extracted.<br />
* '''[[SMS:PTM Wave File|Wave file(s)]]''' &ndash; Time varying information about the wave field.<br />
* '''Wave breaking file(s)''' &ndash; Time varying information about wave breaking.<br />
* '''[[SMS:PTM Boundary Condition File|PTM Boundary Condition file]]''' &ndash; Describes the wet/dry interface.<br />
<br />
== Output Files ==<br />
The output files use the name given after the keyword :OUTPUT_PREFIX in the [[SMS:PTM Control File|program control file]] and are appended with the following endings:<br />
* '''Mapping Output File''' (*_maps.h5) &ndash; Behavior of the flow and native sediments over the whole domain incremented by time.<br />
* '''Parcel Data File''' (*_particles.h5) &ndash; Parcel information incremented by time.<br />
* '''Echo file''' (*_input.out) &ndash; ASCII file echoing the input parameters of the simulation.<br />
* '''Neighbor file''' (*.neighbors) &ndash; Contains mesh connectivity information. Once generated, can be specified as an input file to avoid regenerating for subsequent simulations with a given mesh. If the mesh changes, the neighbor file should be regenerated.<br />
* '''Trap Count File''' (*_count.out) &ndash; Contains the time and ID of particles entering a trap<br />
* '''Trap Residency File''' (*_residency.out) &ndash; Contains the time particles enter and exit a trap and the total time spent in the trap.<br />
<br />
==Related Topics==<br />
* [[SMS:PTM|PTM]]<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
<br />
[[Category:PTM|F]]<br />
[[Category:SMS File Formats|P]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=Annotations&diff=121875Annotations2017-03-28T20:46:24Z<p>Dharker: /* North Arrows */ included folder location</p>
<hr />
<div>{{TOCright}}<br />
Annotations can be added to a project to provide notes and clarification. The Annotations application is included in all paid editions of [http://www.aquaveo.com/software/gms-pricing GMS] and [http://www.aquaveo.com/software/sms-pricing SMS].<br />
[[Category:Link to Store]]<br />
==Annotation Objects==<br />
The GMS and SMS applications contain tools to annotate the data in an application for presentations, animations and screen shots.<br />
<br />
These tools (annotation objects)are accessed through the Annotations Module and include:<br />
* Images<br />
* North Arrows<br />
* Scale Bars<br />
* Text<br />
* Lines<br />
* Ovals<br />
* Rectangles<br />
<br />
==Screen vs World Space Layers==<br />
All annotation layers either contain objects referenced to world or screen coordinates. Objects referenced to world coordinates will change size and position on the screen with the underlying data. This is useful to identify specific locations in the model such as peir locations. Objects associated with screen coordinates do not move on the screen with the underlying data. This is useful for titles, legends such as north arrows and scale bars, and logos. Some types of annotations can only be created in screen space layers. These include North Arrows, Images, and scale bars.<br />
<br />
When the first annotation object created, the program will ask which type of layer (screen or world space) to create and add the object to. Create additional layers by right-clicking on the "[[File:Annotations Folder Icon.png]] Annotation Data" item and selecting '''Create Screen Space Layer''' or '''Create World Space Layer'''. Layers are differentiated by their icons in the Project Explorer: [[File:Annotations Screen Icon.png]] for screen space layers or [[File:Annotations World Icon.png]] for world space layers.<br />
<br />
If multiple layers exist, any newly created annotation object will be placed in the "current" layer.<br />
<br />
[[Image:AnnotationTree.jpg|border]]<br />
<br />
==Annotation Object Attributes==<br />
The extents of annotation objects defined by a frame. Initially define this frame when creating the annotation object by left-clicking at any point on the screen and dragging a rectangle with the mouse (left button still down). The display will show the frame while dragging with the mouse. (Points and lines defining degenerate frames are not allowed.) <br />
<br />
When creating a annotation, if the frame is too big for the window, it will be resized appropriately. Annotations can't be resized or moved even partially outside of the borders of the window. If, through a quick mouse drag, resizing a annotation causes the cursor to land outside the window, the annotation will be redrawn to take up all the window space in that direction. <br />
<br />
This frame bounds the region of the screen where the object will appear with the modeling data. Interact with the object by interacting with its frame and specifying its attributes or properties (see the section on selection below). The frame anchors the annotation object on the screen. This anchoring defines both the size and position of the object. The x-location, y-location, x-size and y-size are all defined independently as either a pixel value or percentage of the screen. <br />
<br />
The horizontal position can be set from the left edge, the right edge or the center of the object. If positioning the left edge, the object position is defined relative to the left edge of the screen. If positioning the right edge, the object position is defined relative to the right edge of the screen. If positioning the center of the object, the object position is defined relative to the horizontal center of the screen.<br />
<br />
For example, the left side of the frame may be specified as 100 pixels from the left edge of the screen. Alternatively, specify that the right edge of the frame should be 10% of screen width from the right edge. Finally, specify that the center of the object is 100 pixels to the right of the center of the screen.<br />
<br />
The vertical position and sizes of the object are similarly specified in the anchoring attribute of the object.<br />
<br />
All annotation objects also have attributes. The specific attributes depend on the type of object. The attributes define color, line thickness, fill properties, associated images, etc.<br />
<br />
==Screen Space Images==<br />
[[File:AnnoImageProperties.png|thumb|280 px|The ''Image Properties'' dialog showing the ''Image'' tab]]<br />
A screen space image is simply a graphics icon mapped to the screen. A typical application would be to display a company, department, or municipality logo next to the numeric model being displayed in the graphics window. Image file formats currently supported include the following: [https://en.wikipedia.org/wiki/BMP_file_format BMP], [https://en.wikipedia.org/wiki/GIF GIF], [https://en.wikipedia.org/wiki/JPEG JPG/JPEG], [https://en.wikipedia.org/wiki/Portable_Network_Graphics PNG], [https://en.wikipedia.org/wiki/MrSID SID], and [https://en.wikipedia.org/wiki/Tagged_Image_File_Format TIF/TIFF].<br />
<br />
To add a screen space image, use the '''Add Annotation Image''' tool and click anywhere in the graphics window. Use the ''Open'' dialog to select and add the desired image. Dragging a box in the graphics window will fit the image to he box size.<br />
<br />
Using the '''Select Annotation Objects''' tool, the image attributes can be changed by right-clicking on the image and selecting the '''Properties''' command. This will bring up an ''Image Properties'' dialog with two tabs where the following options can be used: <br />
<br />
'''''Image Tab'''''<br />
<br />
This tab gives the general image properties.<br />
*''Fixed aspect ratio'' *ndash; Assigns whether the image is being displayed as a scaled (distorted object), scaled based on its original aspect ratio, or locked at another aspect ratio.<br />
*'''Revert to Original Aspect Ratio''' &ndash; Returns the image to the aspect ratio it had when it was added to the project.<br />
* ''Transparency Options'' &ndash; These options allow for an image to be redrawn with a transparency.<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
*''Use transparency'' &ndash; When checked it will cause the image to be redrawn with the most used color in the image. Clicking the transparency checkbox to the off state causes the image to be redrawn with no transparency.<br />
*''Specify color'' &ndash; If checked, it will activate the color button and the color button will have the latest chosen image color painted on it or the most used color in the image, if it has not been activated before. Clicking on the down arrow part of the color button causes a color popup to be displayed with swaths of the 40 most used colors in the image or all the colors in the image, if the image has less than 40 colors. Clicking on one of those colors will cause the image to be redrawn with that color made transparent in the image. <br />
*''Tolerance'' &ndash; This edit field allows for variation in the matching of the red, green and blue components. The tolerance field ranges in allowable values from 0.0 to 1.0. 0.0 means the red, green and blue components must exactly match. Values higher than 0.0 indicate the degree of variation from the given color. <br />
</blockquote><br />
[[File:AnnoImageProp Anchor.png|thumb|280 px|The ''Image Properties'' dialog showing the ''Anchor'' tab]]<br />
'''''Anchor Tab'''''<br />
<br />
This tab handles options for the size and positioning of the image. <br />
*''Horizontal''<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
*''Anchor'' &ndash; The options here determine which direct to move image when moving or resizing the image along the x-axis. Options include "Left", "Center", and "Right". "Left" will offset from the left edge of the image or resize from the left edge. "Right" will use the right edge of the image. "Center" determines the horizontal center of the image and uses that for moving along the x-axis or resizing along the x-axis.<br />
*''Offset'' &ndash; Moves the image along the x-axis based on the selected anchor type.<br />
*''Size'' &ndash; Increases or decreases the image size along the x-axis based on the selected anchor type.<br />
</blockquote><br />
*''Vertical''<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
*''Anchor'' &ndash; The options here determine which direct to move image when moving or resizing the image along the y-axis. Options include "Top", "Middle", and "Bottom". "Top" will offset from the top edge of the image or resize from the top edge. "Bottom" will use the bottom edge of the image. "Middle" determines the vertical center of the image and uses that for moving along the y-axis or resizing along the y-axis.<br />
*''Offset'' &ndash; Moves the image along the y-axis based on the selected anchor type.<br />
*''Size'' &ndash; Increases or decreases the image size along the y-axis based on the selected anchor type.<br />
</blockquote><br />
<br />
==Scale Bars==<br />
A scale bar occupies a fixed size of the screen to display the relative size of the objects in the simulation. Define the minimum width of the scale bar section (in pixels), along with a minimum and maximum height of the scale (also in pixels). The XMS application adds a "Units" label (meters in the image shown below) and labels for the model distance related to the scale divisions.<br />
<br />
[[Image:Scale.jpg|border|150px]]<br />
<br />
The program will compute a well conditioned number to use as the scale increment that fits in the specified scale bar extents.<br />
<br />
[[File:ScaleBar Scale.png|thumb|280 px|The ''Scale Bar Properties'' dialog showing the ''Scale Bar'' tab]]<br />
Using the '''Create Scale Bar''' [[File:Tool ScaleBar.png]] tool, draw a box in the graphics window to indicated the initial size of the scale bar. The ''Scale Bar Properties'' dialog will appear. This dialog can be reached later by right-clicking on the scale bar and selecting the '''Properties''' command.<br />
<br />
In the ''Scale Bar Properties'' dialog, attributes of the scale bar include:<br />
*''Units'' &ndash; Options in "Meters", "U.S. Survey Feet", and "International Feet".<br />
*''Font'' &ndash; Selecting this button bring ups the ''Font'' dialog where the font type, style, and size are selected. The arrow next to the button will bring up a color picker where the font color can be chosen.<br />
*''Text spacing'' &ndash; The minimum spacing between distance labels.<br />
*''Min division width'' &ndash; The minimum division width (in pixels). The XMS application determines the number of divisions based on the minimum divisiion width and the width of the frame.<br />
* ''Background'' &ndash; Opts to fill behind the scale bar with the background color or another color.<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
*''Fill behind'' &ndash; Toggles on or off the option to create a colored field behind the scale bar.<br />
*''Background color'' &ndash; Sets the background color as the same background color selected in for the graphics window in the ''Display Options'' dialog.<br />
*''Other color'' &ndash; Clicking this button will bring up a ''Color'' dialog where a larger selection of colors can be chosen. The arrow next to the button will bring up a color picker with a preset number of color options.<br />
</blockquote><br />
*''Anchor'' tab &ndash; This is identical to the ''Anchor'' tab in the ''Image Properties'' dialog.<br />
<br />
==North Arrows==<br />
[[Image:North-arrow.jpg|left|50 px]]<br />
<br />
North arrow objects consist of automatically rotating screen space images. When an XMS application is installed, at least one default north arrow image will be included in the application's home directory, and many are included in the SMS "SupportFiles" folder. Create or download as many north arrow icons as desired. These icons are displayed at the specified location (anchored with the standard options), but will rotate as the view direction changes so that the "up" direction of the icon always aligns with the "North" or positive "Y" direction.<br />
<br />
A north arrow object is added by using the '''Create North Arrow''' [[File:Tool NorthArrow.png]] tool. Properties for a north arrow objects are set in the ''North Arrow Properties'' dialog. This dialog has the the same options as the ''Image Properties'' dialog.<br />
<br />
==Text==<br />
[[File:TextProperties.png|thumb|300 px|The ''Text Properties'' dialog]]<br />
Text can be created in world or screen space layers.<br />
<br />
Enter text by clicking in the graphics window with the '''Create Text''' [[File:Tool CreateText.png]] tool active. This will bring up the ''Text Properties'' dialog. In this dialog, the attributes for the text object can be defined.<br />
<br />
The following text attributes can be set:<br />
*''Text'' &ndash; Options for specifying the text to be displayed and font style.<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
*''Text'' &ndash; Field where the text to be displayed is entered.<br />
* '''Font''' &ndash; Selecting this button bring ups the ''Font'' dialog where the font type, style, and size are selected. The arrow next to the button will bring up a color picker where the font color can be chosen.<br />
* '''Color''' &ndash; Another method for selecting the font color. Clicking this button will bring up a ''Color'' dialog where a larger selection of colors can be chosen. The arrow next to the button will bring up a color picker identical to the one above.<br />
</blockquote><br />
* ''Background'' &ndash; Fill behind the text with the background color or another color.<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
*''Background color'' &ndash; Sets the background color as the same background color selected in for the graphics window in the ''Display Options'' dialog.<br />
*''Other color'' &ndash; Activates color button identical to the one in the ''Text'' section.<br />
</blockquote><br />
* ''Border'' &ndash; Contains option for defining a border around the text object.<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
*''Draw border'' &ndash; Activates a border around the entire text object. The color button allows changing the border color.<br />
*''Specifed thickness'' &ndash; Activates the option to change the border thickness. The default border thickness is 1 pixel. <br />
</blockquote><br />
<br />
==Lines/Arrows==<br />
[[File:LineProperties.png|thumb|285 px|The ''Line Properties'' dialog]]<br />
Create lines or arrows using the '''Create Line''' [[File:Tool LineAnno.png]] tool. Lines/arrows can be created in screen or world space layers. Lines can be straight or curved. Click once to start a line. Click again to curve the line. Double-click or hit enter to complete a line. Once the line has been completed, the ''Line Properties'' dialog will appear. This dialog can also be accessed by right-clicking on the line and selecting the '''Properties''' command.<br />
<br />
In the ''Line Properties'' dialog, the attributes available for lines and arrows include:<br />
* ''Line'' &ndash; Attributes for a line include:<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
*''Dashed'' &ndash; Sets the line as an evenly spaced dashed line. The length of each dash and the length of each space is a set value that cannot be changed at this time.<br />
*''Solid'' &ndash; Specifies the line as a solid line.<br />
*''Width'' &ndash; Specified the line width.<br />
*''Line Color'' &ndash; Clicking this button will bring up a ''Color'' dialog where a larger selection of colors can be chosen. The arrow next to the button will bring up a color picker with preset color options.<br />
</blockquote><br />
* ''Arrowheads'' &ndash; This section has option for making the line into an arrow.<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
* Location &ndash; Drop menu that defines where the arrow head will be placed on the line. "None" will leave off arrowheads. "Begin" places the arrowhead where the line was started when created. "End" placed the arrowhead where the line terminated during creation. "Both" places an arrowhead at the start and end of the line.<br />
*''Length'' &ndash; Defines the length of the arrowhead. The point of the arrowhead will not go past the start or end point of the line. Increasing the size will move arrowhead further up or down the line.<br />
*''Width'' &ndash; Defines the arrowhead width. The arrowhead width will be equally divided along either side of the line.<br />
</blockquote><br />
*''Preview'' &ndash; Shows what the line or arrow will look like the current selected options. Options are not applied until the '''OK''' button is clicked.<br />
<br />
==Rectangles and Ovals==<br />
{{Anchor|Rectangles|Ovals}}<br />
[[File:Rectangle-OvalProperties.png|thumb|280 px|The ''Rectangle/Oval Properties'' dialog]]<br />
Create rectangles by dragging a box with '''Create Rectangle''' [[File:Tool Rectangle.png]] tool active and create ovals with the '''Create Oval''' [[File:Tool Oval.png]] tool active. Rectangles or ovals can be created in world or screen space layers. <br />
<br />
After designating where the rectangle or oval will be drawn, the ''Rectangle/Oval Properties'' dialog will appear. This is the same dialog for both rectangles and ovals. It can also be accessed by right-clicking on the rectangle or oval and selecting the '''Properties''' command.<br />
<br />
IN the ''Rectangle/Oval Properties'' dialog, the attributes for rectangles and ovals include:<br />
* ''Line'' &ndash; Attributes for a line around the rectangle or oval. Option include:<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
*''Dashed'' &ndash; Sets the line as an evenly spaced dashed line. The length of each dash and the length of each space is a set value that cannot be changed at this time.<br />
*''Solid'' &ndash; Specifies the line as a solid line.<br />
*''Width'' &ndash; Specified the line width.<br />
*''Line Color'' &ndash; Clicking this button will bring up a ''Color'' dialog where a larger selection of colors can be chosen. The arrow next to the button will bring up a color picker with preset color options.<br />
</blockquote><br />
* ''Fill''<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
*''Fill'' &ndash; Designates that the area of the rectangle or oval will have a solid color. This activates a color button like the one in the ''Line'' section.<br />
*''No fill'' &ndash; Designates that the area of the rectangle or oval will be empty.<br />
</blockquote><br />
<br />
== Selection ==<br />
The '''Select Annotation Object''' [[File:Tool SelectAnnoObject.png]] tool is used to select and set attributes for annotation objects. This requires that objects exist to be selected. In this case when using this tool and left-clicking in the annotation object, the object frame will be drawn around the annotation. In addition to the frame, the XMS application displays grab handles on the corners and edges of the frame. Modify the rectangular shape of the annotation by dragging one of the grab handles and changes the position of the object by dragging the annotation (click at any point in the object interior).<br />
<br />
Right-clicking on annotation object will produce a menu with the following commands:<br />
* '''Delete''' &ndash; Removes the annotation object.<br />
* '''Duplicate''' &ndash; Creates a copy of the annotation object on the same annotation layer.<br />
* '''Properties''' &ndash; Brings up the properties dialog for the selected object.<br />
<br />
== Viewing Annotations At Specific Time Intervals ==<br />
<br />
Available in SMS v11.1 and higher, annotations can be setup to be viewed at specific time intervals. This feature is currently under development in GMS. To setup annotations so they only are displayed at specified time intervals do the following:<br />
<br />
# Right-click on the Annotation layer in the tree then select '''Properties...'''. <br />
# This dialog will display the ''Annotation Layer Properties'' dialog.<br />
# Check the ''Apply time range'' checkbox<br />
# Modify the "begin" and "end" time controls to specify the range for when annotations are visible.<br />
# Click '''Ok'''.<br />
<br />
Annotations will not be displayed when the specified time range is active. This applies to data in the graphics window and film loops.<br />
<br />
==See also==<br />
* [[GMS:GMS|GMS]]<br />
* [[SMS:SMS|SMS]]<br />
* [[SMS:Layout|Layout of the Graphical Interface]]<br />
<br />
<br />
{{Navbox SMS Tools}}<br />
<br />
<br />
[[Category:GMS Models]]<br />
[[Category:SMS Modules]]<br />
[[Category:WMS Models]]<br />
[[Category:Tools]]<br />
[[Category:Numerical Models|A]]<br />
[[Category:Annotations]]<br />
[[Category:Annotation Dialogs]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=SMS:RMA2&diff=121866SMS:RMA22017-03-24T23:01:09Z<p>Dharker: /* External Links */ fixed another broken link</p>
<hr />
<div>{| align ="right"<br />
|-<br />
|{{SMS Infobox Model |<br />
|name= RMA2<br />
|model_type= Two-dimensional depth averaged finite element hydrodynamic numerical model. Computes water surface elevations and horizontal velocity components for subcritical, free-surface flow in two dimensional flow fields.<br />
|developer= <br />
Resource Management Associates <br><br />
United States Army Corps of Engineers (USACE)<br />
|web_site= [https://web-beta.archive.org/web/20121116041614/http://chl.erdc.usace.army.mil:80/rma2 Archived RMA2 web site]<br />
|tutorials= <br />
General Section<br />
* Mesh Editing<br />
* Observation<br />
* Overview<br />
* Sensitivity<br />
Models Section<br />
* RMA2<br />
* RMA2 Steering<br />
}}<br />
|}<br />
<br />
RMA2 is a 1D/2D hydrodynamic model using the finite element method. RMA2 was written by Ian King and is maintained by the [http://www.erdc.usace.army.mil/ Army Corp of Engineers Engineering Resource Development Center (ERDC)]. RMA2 has been applied to multi-dimensional problems since the mid 1970s. As such, it was one of the first widely used multi-dimensional hydrodynamics engine applied to riverine and estuarine applications. The current interface to RMA2 in the [[SMS:SMS|Surface-water Modeling System]] originated as a program named FastTABS.<br />
<br />
The RMA2 model can be added to a [http://www.aquaveo.com/software/sms-pricing paid edition] of SMS.<br />
[[Category:Link to Store]]<br />
<br />
== Functionality ==<br />
RMA2 has these capabilities:<br />
* Compute water levels and velocities for a [[SMS:Mesh_Module|2D mesh]] structure<br />
* [[SMS:Mesh_Module#1D_elements|1D elements]] (trapezoidal shape)<br />
* [[SMS:RMA2_1D_Control_Structures|1D flow control structures]]<br />
* Allow elements to wet and dry<br />
* 2D structures are permitted in version 4.50 or higher (US Army Corps of Engineers employees only)<br />
* Account for effects of the earth's rotation ([[SMS:RMA2_Material_Properties#Coriolis |Coriolis effect]])<br />
<br />
* Accepts a wide variety of boundary conditions including:<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
* Discharge by node/element/ or line<br />
* Tidal radiation boundary conditions by line<br />
* Discharge as a function of elevation by line<br />
* Water surface elevation along a line<br />
* Apply [[SMS:RMA2_Material_Properties#Wind|wind stress]] either<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
* Uniformly over the model domain; constant or time-varying<br />
* As a storm; front or tropical cyclonic event (time-varying)<br />
</blockquote></blockquote><br />
* Read an [[SMS:STWAVE|STWAVE]] radiation stress file to incorporate wave induced currents<br />
<br />
* Identify errors in the computational mesh specification<br />
* Accept either English or standard SI units<br />
* Restart (Hotstart) the simulation from a prior RMA2 run and continue<br />
* Account for [[SMS:RMA2_Material_Properties#Marsh_porosity|Marsh Porosity]] wetting and drying (wetlands)<br />
<br />
* Employ either direct or automatic dynamic assignment of [[SMS:RMA2_Material_Properties#Roughness|Manning's n-value]] by water depth<br />
* Employ user selectable manual or automatically assigned turbulent exchange coefficients<br />
* Compute flow across continuity check lines.<br />
* [[SMS:RMA2 Menu#RMA2 Revisions|Revisions]] within a time step (both coefficients and/or boundary conditions)<br />
<br />
== Using the Model / Practical Notes ==<br />
* [[SMS:RMA2 Spindown|RMA2 Spindown Steering (Incremental Loading)]]<br />
* RMA2 2D Control structures are only available to employees of the US Army Corps of Engineers.<br />
* The TABS models are built to expire after a set date. The latest version can be downloaded from the [http://www.aquaveo.com/ Software Updates section of the Aquaveo website].<br />
* According to the RMA2 model documentation, "Because of lack of experience in using storms in a simulation, including storms in simulations remains experimental."<br />
* Boundary condition time series curves are resampled by the model based on the time step. If changing the time step, re-enter the time series curve since SMS will automatically resample the curve and resampling the curve multiple times may result in a loss of important information.<br />
<br />
== Graphical Interface == <br />
SMS provides a graphical interface that is designed to visualize the projects being created, easily modify project parameters, and view the solutions produced by the RMA2 model. See [[SMS:RMA2 Graphical Interface|RMA2 Graphical Interface]] for more information.<br />
<br />
The [[SMS:RMA2 Graphical Interface|RMA2 Graphical Interface]] contains tools to create and edit an RMA2 simulation. The simulation consists of a geometric definition of the model domain (the mesh) and a set of numerical parameters. The parameters define the boundary conditions and options pertinent to the model.<br />
<br />
The interface is accessed by selecting the [[SMS:Mesh Module|2D Mesh Module]] and setting the current model to RMA2. If a mesh has already been created for a RMA2 simulation or an existing simulation read, the mesh object will exist in the [[SMS:Project Explorer|Project Explorer]] and selecting that object will make the 2D Mesh module active and set the model to RMA2. See the [[SMS:Mesh Module|Mesh Module]] documentation for guidance on building and editing meshes as well as visualizing mesh results.<br />
<br />
The interface consists of the [[SMS:2D Mesh_Module_Menus|2D Mesh Module Menus]] and [[SMS:2D Mesh Module Tools|tools]] augmented by the [[SMS:RMA2 Menu|RMA2 Menu]]. See [[SMS:RMA2 Graphical Interface|RMA2 Graphical Interface]] for more information.<br />
<br />
== Saving RMA2 ==<br />
When completing the ''File'' | '''Save As...''' command, the following files get saved in the *.sms<br />
<br />
* *.mat referenced to new save location<br />
* *.sim referenced to new save location<br />
<br />
== Related Topics == <br />
*[[SMS:SMS_Models|SMS Models Page]]<br />
*[[SMS:TABS|TABS Models]]<br />
*[[SMS:RMA4|RMA4 ]]<br />
* [[SMS:Nodal Transition (Marsh Porosity) Dialog|Nodal Transition Dialog]]<br />
* [[SMS:Roughness Options Dialog|Roughness Options Dialog]]<br />
* [[SMS:Rainfall Values Dialog|Rainfall Values Dialog]]<br />
<br />
== External Links ==<br />
* CHL RMA2 Website [https://web-beta.archive.org/web/20121116041614/http://chl.erdc.usace.army.mil:80/rma2]<br />
* CHL RMA2 Frequently Asked Questions [http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=ARTICLES;365]<br />
* Users Guide To RMA2 WES Version 4.5 [http://smsdocs.aquaveo.com/rma2.pdf]<br />
* Users Guide to RMA2 Version 4.35 [https://web-beta.archive.org/web/20121116041614/http://chl.erdc.usace.army.mil/Media/3/2/8/rma2_435hlp.zip]<br />
* MERGAVE &ndash; Utility for Merging RMA2 Solution Files [https://web-beta.archive.org/web/20090817111348/http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=ARTICLES!427]<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
<br />
[[Category:SMS 2D Mesh|R]]<br />
[[Category:TABS|R]]<br />
[[Category:RMA2|R]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=SMS:RMA2&diff=121865SMS:RMA22017-03-24T23:00:30Z<p>Dharker: Fixed broken links</p>
<hr />
<div>{| align ="right"<br />
|-<br />
|{{SMS Infobox Model |<br />
|name= RMA2<br />
|model_type= Two-dimensional depth averaged finite element hydrodynamic numerical model. Computes water surface elevations and horizontal velocity components for subcritical, free-surface flow in two dimensional flow fields.<br />
|developer= <br />
Resource Management Associates <br><br />
United States Army Corps of Engineers (USACE)<br />
|web_site= [https://web-beta.archive.org/web/20121116041614/http://chl.erdc.usace.army.mil:80/rma2 Archived RMA2 web site]<br />
|tutorials= <br />
General Section<br />
* Mesh Editing<br />
* Observation<br />
* Overview<br />
* Sensitivity<br />
Models Section<br />
* RMA2<br />
* RMA2 Steering<br />
}}<br />
|}<br />
<br />
RMA2 is a 1D/2D hydrodynamic model using the finite element method. RMA2 was written by Ian King and is maintained by the [http://www.erdc.usace.army.mil/ Army Corp of Engineers Engineering Resource Development Center (ERDC)]. RMA2 has been applied to multi-dimensional problems since the mid 1970s. As such, it was one of the first widely used multi-dimensional hydrodynamics engine applied to riverine and estuarine applications. The current interface to RMA2 in the [[SMS:SMS|Surface-water Modeling System]] originated as a program named FastTABS.<br />
<br />
The RMA2 model can be added to a [http://www.aquaveo.com/software/sms-pricing paid edition] of SMS.<br />
[[Category:Link to Store]]<br />
<br />
== Functionality ==<br />
RMA2 has these capabilities:<br />
* Compute water levels and velocities for a [[SMS:Mesh_Module|2D mesh]] structure<br />
* [[SMS:Mesh_Module#1D_elements|1D elements]] (trapezoidal shape)<br />
* [[SMS:RMA2_1D_Control_Structures|1D flow control structures]]<br />
* Allow elements to wet and dry<br />
* 2D structures are permitted in version 4.50 or higher (US Army Corps of Engineers employees only)<br />
* Account for effects of the earth's rotation ([[SMS:RMA2_Material_Properties#Coriolis |Coriolis effect]])<br />
<br />
* Accepts a wide variety of boundary conditions including:<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
* Discharge by node/element/ or line<br />
* Tidal radiation boundary conditions by line<br />
* Discharge as a function of elevation by line<br />
* Water surface elevation along a line<br />
* Apply [[SMS:RMA2_Material_Properties#Wind|wind stress]] either<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
* Uniformly over the model domain; constant or time-varying<br />
* As a storm; front or tropical cyclonic event (time-varying)<br />
</blockquote></blockquote><br />
* Read an [[SMS:STWAVE|STWAVE]] radiation stress file to incorporate wave induced currents<br />
<br />
* Identify errors in the computational mesh specification<br />
* Accept either English or standard SI units<br />
* Restart (Hotstart) the simulation from a prior RMA2 run and continue<br />
* Account for [[SMS:RMA2_Material_Properties#Marsh_porosity|Marsh Porosity]] wetting and drying (wetlands)<br />
<br />
* Employ either direct or automatic dynamic assignment of [[SMS:RMA2_Material_Properties#Roughness|Manning's n-value]] by water depth<br />
* Employ user selectable manual or automatically assigned turbulent exchange coefficients<br />
* Compute flow across continuity check lines.<br />
* [[SMS:RMA2 Menu#RMA2 Revisions|Revisions]] within a time step (both coefficients and/or boundary conditions)<br />
<br />
== Using the Model / Practical Notes ==<br />
* [[SMS:RMA2 Spindown|RMA2 Spindown Steering (Incremental Loading)]]<br />
* RMA2 2D Control structures are only available to employees of the US Army Corps of Engineers.<br />
* The TABS models are built to expire after a set date. The latest version can be downloaded from the [http://www.aquaveo.com/ Software Updates section of the Aquaveo website].<br />
* According to the RMA2 model documentation, "Because of lack of experience in using storms in a simulation, including storms in simulations remains experimental."<br />
* Boundary condition time series curves are resampled by the model based on the time step. If changing the time step, re-enter the time series curve since SMS will automatically resample the curve and resampling the curve multiple times may result in a loss of important information.<br />
<br />
== Graphical Interface == <br />
SMS provides a graphical interface that is designed to visualize the projects being created, easily modify project parameters, and view the solutions produced by the RMA2 model. See [[SMS:RMA2 Graphical Interface|RMA2 Graphical Interface]] for more information.<br />
<br />
The [[SMS:RMA2 Graphical Interface|RMA2 Graphical Interface]] contains tools to create and edit an RMA2 simulation. The simulation consists of a geometric definition of the model domain (the mesh) and a set of numerical parameters. The parameters define the boundary conditions and options pertinent to the model.<br />
<br />
The interface is accessed by selecting the [[SMS:Mesh Module|2D Mesh Module]] and setting the current model to RMA2. If a mesh has already been created for a RMA2 simulation or an existing simulation read, the mesh object will exist in the [[SMS:Project Explorer|Project Explorer]] and selecting that object will make the 2D Mesh module active and set the model to RMA2. See the [[SMS:Mesh Module|Mesh Module]] documentation for guidance on building and editing meshes as well as visualizing mesh results.<br />
<br />
The interface consists of the [[SMS:2D Mesh_Module_Menus|2D Mesh Module Menus]] and [[SMS:2D Mesh Module Tools|tools]] augmented by the [[SMS:RMA2 Menu|RMA2 Menu]]. See [[SMS:RMA2 Graphical Interface|RMA2 Graphical Interface]] for more information.<br />
<br />
== Saving RMA2 ==<br />
When completing the ''File'' | '''Save As...''' command, the following files get saved in the *.sms<br />
<br />
* *.mat referenced to new save location<br />
* *.sim referenced to new save location<br />
<br />
== Related Topics == <br />
*[[SMS:SMS_Models|SMS Models Page]]<br />
*[[SMS:TABS|TABS Models]]<br />
*[[SMS:RMA4|RMA4 ]]<br />
* [[SMS:Nodal Transition (Marsh Porosity) Dialog|Nodal Transition Dialog]]<br />
* [[SMS:Roughness Options Dialog|Roughness Options Dialog]]<br />
* [[SMS:Rainfall Values Dialog|Rainfall Values Dialog]]<br />
<br />
== External Links ==<br />
* CHL RMA2 Website [http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=Software;14]<br />
* CHL RMA2 Frequently Asked Questions [http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=ARTICLES;365]<br />
* Users Guide To RMA2 WES Version 4.5 [http://smsdocs.aquaveo.com/rma2.pdf]<br />
* Users Guide to RMA2 Version 4.35 [https://web-beta.archive.org/web/20121116041614/http://chl.erdc.usace.army.mil/Media/3/2/8/rma2_435hlp.zip]<br />
* MERGAVE &ndash; Utility for Merging RMA2 Solution Files [https://web-beta.archive.org/web/20090817111348/http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=ARTICLES!427]<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
<br />
[[Category:SMS 2D Mesh|R]]<br />
[[Category:TABS|R]]<br />
[[Category:RMA2|R]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=SMS:RMA4&diff=121864SMS:RMA42017-03-24T22:49:46Z<p>Dharker: Fixed broken link</p>
<hr />
<div>{{SMS Infobox Model |<br />
|name= RMA4<br />
|model_type= Finite element water quality transport numerical model in which the depth concentration distribution is assumed uniform. It computes concentrations for up to 6 constituents, either conservative or non-conservative, within the computational mesh domain.<br />
|developer= <br />
Resource Management Associates <br><br />
United States Army Corps of Engineers (USACE)<br />
|web_site= [https://web-beta.archive.org/web/20130420050019/http://chl.erdc.usace.army.mil/rma4 Archived RMA4 web site]<br />
|tutorials= <br />
General Section<br />
* Mesh Editing<br />
* Observation<br />
* Overview<br />
* Sensitivity<br />
Models Section<br />
* RMA4<br />
}}<br />
<br />
<br />
RMA4 is a finite element water quality transport numerical model. RMA4 was designed to simulate the depth-average advection / diffusion process in an aquatic environment. The model can be used for the evaluation of any conservative substance that is either dissolved in the water or may be assumed to be neutrally buoyant within the water column. The model is also used for investigating the physical processes of migration and mixing of a soluble substance in reservoirs, rivers, bays, estuaries and coastal zones. The model is useful for evaluation of the basic processes or for defining the effectiveness of remedial measures. For most applications, the model utilizes the depth-averaged hydrodynamics from [[SMS:RMA2|RMA2]]. The input hydrodynamics solution can be either a steady state or a dynamic simulation and is used to compute particle dispersions.<br />
<br />
The RMA4 model can be added to a [http://www.aquaveo.com/software/sms-pricing paid edition] of SMS.<br />
[[Category:Link to Store]]<br />
<br />
== Functionality ==<br />
RMA4 has been applied to:<br />
* Define horizontal salinity distribution.<br />
* Trace temperature effects from power plants<br />
* Calculate residence times of harbors or basins<br />
* Optimize the placement of outfalls<br />
* Identify critical area for oil spills or other pollutants spread<br />
* Monitor water quality criterion within game and fish habitats<br />
* Determine the limits of salinity intrusion<br />
* Perform flushing analysis<br />
* Turbidity monitoring<br />
* SMS does not support BOD/DO modeling with RMA4 because of issues with RMA4.<br />
<br />
== Using the Model / Practical Notes ==<br />
* RMA4 includes support of the SI card which controls what units the engine will use. If SI is set to 0, the model runs with English units. If it is set to 1, the model runs in metric units. SMS saves the SI card based on the coordinate system (projection) specified. However, it is recommended that metric units be used for RMA4. This applies to the hydrodynamics that are fed into RMA4 as well.<br />
* RMA4 is more sensitive to mass gain/loss than [[SMS:RMA2|RMA2]] across large closed boundary angles. The suggested minimum boundary angle between any two adjacent elements is 10°. This becomes a very great concern, as this applies simply to the wet/dry interface and not to the outer mesh boundary.<br />
* RMA4 should not be used to evaluate highly volatile materials such as gasoline, nor materials that do not mix with water, such as oil. Although RMA4 has been used to measure temperature effects from such locations as power plant discharges, this is not a recommended application. Although the documentation claims to be able to model up to 6 constituents, the SMS developers have never had success with more than a single constituent at a time. Multiple constituents require multiple boundary condition files, each with values for one of the constituents. Multiple constituents can be named and joined through the [[SMS:Data Calculator|''Data Calculator'']] and exported to a single file for future use.<br />
* Card order matters. The RMA4 run control and full print files are very helpful for determining what options are being used.<br />
* The TABS models are built to expire after a set date. The latest version can be downloaded from the [http://www.aquaveo.com/ Software Updates section of the Aquaveo website].<br />
<br />
== Graphical Interface == <br />
SMS provides a graphical interface that is designed to visualize the projects being created, easily modify project parameters, and view the solutions produced by the RMA4 model. See [[SMS:RMA4 Graphical Interface|RMA4 Graphical Interface]] for more information.<br />
<br />
==Saving RMA4==<br />
When completing the ''File'' | '''Save As...''' command, the following files get saved in the *.sms:<br />
* *.mat referenced to new save location<br />
* *.mat referenced to new save location<br />
* *.qsl referenced to new save location (RMA4 solution file)<br />
* *.sol referenced to new save location and original location (RMA2 solution file)<br />
<br />
==RMA4 Files==<br />
Input and Output files for [[SMS:RMA4|RMA4]].<br />
<br />
'''''Input Files'''''<br />
* Hydrodynamic Solution (usually an [[SMS:RMA2|RMA2]] *.sol file with a path name less than 67 characters long)<br />
* RMA4 Run Control (Boundary Condition) input (*.trn)<br />
* [[SMS:GFGEN|GFGEN]] Output Geometry (*.bin)<br />
<br />
'''''Output Files'''''<br />
* Transport Solution (*.qsl)<br />
* Full Print Listing File (*.ot3)<br />
[[Category:SMS File Formats|R]]<br />
<br />
== Related Topics ==<br />
*[[SMS:SMS Models|SMS Models Page]]<br />
*[[SMS:TABS|TABS Models]]<br />
*[[SMS:RMA2|RMA2]]<br />
<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
<br />
[[Category:SMS 2D Mesh]]<br />
[[Category:TABS|RMA4]]<br />
[[Category:RMA4|RMA4]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:PEST_ASP_Package&diff=121863GMS:PEST ASP Package2017-03-24T21:54:10Z<p>Dharker: Noted that it's needed to turn the package on first</p>
<hr />
<div>{{MODFLOW Links}}<br />
{{hide in print|'''''Prior to version 9.0 this command and dialog were called "Convergence Options".'''''}}<br />
<br />
When performing [[GMS:Automated Parameter Estimation|automated parameter estimation]], a set of optimal parameter values can only be found if [[GMS:MODFLOW|MODFLOW]] produces a stable solution for all iterations. One of the things that can cause problems with the inverse model is cells going dry. The dry cell flag that is written to the head array can cause instability in the inverse model, and thus it will not converge. When such problems occur, a successful run may be achieved by turning on some convergence options that have been added to the GMS version of MODFLOW by John Doherty. The PEST-ASP package is available in MODFLOW-2000, -2005, -NWT, and -LGR, but not in MODFLOW-USG (which uses an entirely different discretization). Once the package is selected in the MODFLOW Global Options [[GMS:MODFLOW Packages Supported in GMS|Packages dialog]] the PEST ASP options are accessed via the '''''PEST ASP Package''''' (Advanced Spatial Parameterization) command in the ''MODFLOW'' Optional Packages menu. The options are as follows:<br />
[[File:PEST-ASP.jpg|thumb|400 px|Example of the MODFLOW ''PEST-ASP Options'' dialog.]]<br />
==Do Not Stop on Non-Convergence==<br />
<br />
The ''Do not stop ...'' option is used for transient simulations. When this option is on, if the MODFLOW model does not converge for a particular time step, it continues to the next time step rather than aborting.<br />
<br />
==Assign Bottom Elevation to Dry Cells==<br />
<br />
During a normal MODFLOW run, if a cell goes dry, the HDRY value assigned in the BCF package is assigned to the cell. The default value for HDRY is -888. At each iteration of the inverse model run (each time a MODFLOW solution is found), the inverse model interpolates the computed head values to the observation points and computes the residual error. This error is factored into the objective function. If the head at a cell near an observation point suddenly switches from a normal head value to -888, an extreme discontinuity is introduced to the objective function and the inverse model may not be able to converge. This problem can be avoided by turning on the ''Assign bottom elevation to dry cells'' option. If this option is on, the bottom elevation associated with the cell is assigned as the head value for the cell.<br />
<br />
==Prevent Cell Drying==<br />
<br />
The ''Prevent Cell Drying'' option does not allow a cell in the bottom layer to go dry. The head is not allowed to drop below the value corresponding to the specified minimum saturated thickness. Additional instruction is provided by Richard Winston and in a [http://pubs.er.usgs.gov/usgspubs/ofr/ofr91536 USGS Open-File]:<br />
<br />
:Use of the wetting capability can cause serious problems with convergence. There are several methods to avoid this. <br />
<br />
:#If a cell should never become wet, make it an inactive cell rather than a variable head cell. <br />
:#Adjust the value of the wetting threshold in WETDRY. (Higher is more stable but may be less accurate.) <br />
:#Decide which neighbors will be checked to decide if a cell should be wetted using WETDRY. Often it is better to allow only the cell beneath the dry cell to rewet it.<br />
:#Use IHDWET to determine which equation is used to specify the head in newly wetted cells.<br />
:#Can vary the wetting factor WETFCT. <br />
:#In steady-state conditions, adjust initial conditions to values that are close to the user's best guess of the final conditions to improve stability. <br />
:#Choose a different solver. The SIP, PCG1, and PCG2 solvers will work with the wetting capability. The SOR solver doesn't work well with the wetting capability. Note that cells can not change between wet and dry during the inner iterations of the PCG1 and PCG2 solvers. The PCG1 solver is no longer included in the USGS version of MODFLOW.<br />
:#When using the PCG2 solver, set RELAX in the range of 0.97 to 0.99 to avoid zero divide and non-diagonally dominant matrix errors. (However, this is an infrequent cause of instability. If such an error occurs, PCG2 prints an error message in the output file and aborts the simulation.)<br />
:#When using the PCG2 solver, set DAMP to a value between 0 and 1. <br />
:#Unrealistically high conductances on boundary cells can contribute to instability. Check the conductances in the Drain, River, Reservoir, Lake, Stream, and General-Head Boundary packages. In the Evapotranspiration check the EVT Flux Stress[i] and EVT Extinction Depth which together control the conductance of evapotranspiration cells. <br />
<br />
:The two most important variables that affect stability are the wetting threshold and which neighboring cells are checked to determine if a cell should be wetted. Both of these are controlled through WETDRY. It is often useful to look at the output file and identify cells that convert repeatedly from wet to dry. Try raising the wetting threshold for those cells. It may also be worthwhile looking at the boundary conditions associated with dry cells. <br />
<br />
:Sometimes cells will go dry in a way that will completely block flow to a sink or from a source. After that happens, the results are unlikely to be correct. It's always a good idea to look at the flow pattern around cells that have gone dry to see whether the results are reasonable.<br />
<br />
==See also==<br />
<br />
*[[GMS:MODFLOW#Post Processing|Post Processing]]<br />
<br />
*[[GMS:MODFLOW Packages Supported in GMS#Solver Packages|Solver Packages]]<br />
<br />
<br />
{{Navbox GMS}}<br />
[[Category:MODFLOW]]<br />
[[Category:MODFLOW Packages]]<br />
[[Category:MODFLOW Dialogs]]<br />
[[Category:External Links]]<br />
[[Category:PEST|ASP]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:PEST_ASP_Package&diff=121862GMS:PEST ASP Package2017-03-24T21:48:58Z<p>Dharker: noted where in modflow menu it's found</p>
<hr />
<div>{{MODFLOW Links}}<br />
{{hide in print|'''''Prior to version 9.0 this command and dialog were called "Convergence Options".'''''}}<br />
<br />
When performing [[GMS:Automated Parameter Estimation|automated parameter estimation]], a set of optimal parameter values can only be found if [[GMS:MODFLOW|MODFLOW]] produces a stable solution for all iterations. One of the things that can cause problems with the inverse model is cells going dry. The dry cell flag that is written to the head array can cause instability in the inverse model, and thus it will not converge. When such problems occur, a successful run may be achieved by turning on some convergence options that have been added to the GMS version of MODFLOW by John Doherty. The PEST-ASP package is available in MODFLOW-2000, -2005, -NWT, and -LGR, but not in MODFLOW-USG (which uses an entirely different discretization). These options are accessed via the '''''PEST ASP Package''''' (Advanced Spatial Parameterization) command in the ''MODFLOW'' Optional Packages menu. The options are as follows:<br />
[[File:PEST-ASP.jpg|thumb|400 px|Example of the MODFLOW ''PEST-ASP Options'' dialog.]]<br />
==Do Not Stop on Non-Convergence==<br />
<br />
The ''Do not stop ...'' option is used for transient simulations. When this option is on, if the MODFLOW model does not converge for a particular time step, it continues to the next time step rather than aborting.<br />
<br />
==Assign Bottom Elevation to Dry Cells==<br />
<br />
During a normal MODFLOW run, if a cell goes dry, the HDRY value assigned in the BCF package is assigned to the cell. The default value for HDRY is -888. At each iteration of the inverse model run (each time a MODFLOW solution is found), the inverse model interpolates the computed head values to the observation points and computes the residual error. This error is factored into the objective function. If the head at a cell near an observation point suddenly switches from a normal head value to -888, an extreme discontinuity is introduced to the objective function and the inverse model may not be able to converge. This problem can be avoided by turning on the ''Assign bottom elevation to dry cells'' option. If this option is on, the bottom elevation associated with the cell is assigned as the head value for the cell.<br />
<br />
==Prevent Cell Drying==<br />
<br />
The ''Prevent Cell Drying'' option does not allow a cell in the bottom layer to go dry. The head is not allowed to drop below the value corresponding to the specified minimum saturated thickness. Additional instruction is provided by Richard Winston and in a [http://pubs.er.usgs.gov/usgspubs/ofr/ofr91536 USGS Open-File]:<br />
<br />
:Use of the wetting capability can cause serious problems with convergence. There are several methods to avoid this. <br />
<br />
:#If a cell should never become wet, make it an inactive cell rather than a variable head cell. <br />
:#Adjust the value of the wetting threshold in WETDRY. (Higher is more stable but may be less accurate.) <br />
:#Decide which neighbors will be checked to decide if a cell should be wetted using WETDRY. Often it is better to allow only the cell beneath the dry cell to rewet it.<br />
:#Use IHDWET to determine which equation is used to specify the head in newly wetted cells.<br />
:#Can vary the wetting factor WETFCT. <br />
:#In steady-state conditions, adjust initial conditions to values that are close to the user's best guess of the final conditions to improve stability. <br />
:#Choose a different solver. The SIP, PCG1, and PCG2 solvers will work with the wetting capability. The SOR solver doesn't work well with the wetting capability. Note that cells can not change between wet and dry during the inner iterations of the PCG1 and PCG2 solvers. The PCG1 solver is no longer included in the USGS version of MODFLOW.<br />
:#When using the PCG2 solver, set RELAX in the range of 0.97 to 0.99 to avoid zero divide and non-diagonally dominant matrix errors. (However, this is an infrequent cause of instability. If such an error occurs, PCG2 prints an error message in the output file and aborts the simulation.)<br />
:#When using the PCG2 solver, set DAMP to a value between 0 and 1. <br />
:#Unrealistically high conductances on boundary cells can contribute to instability. Check the conductances in the Drain, River, Reservoir, Lake, Stream, and General-Head Boundary packages. In the Evapotranspiration check the EVT Flux Stress[i] and EVT Extinction Depth which together control the conductance of evapotranspiration cells. <br />
<br />
:The two most important variables that affect stability are the wetting threshold and which neighboring cells are checked to determine if a cell should be wetted. Both of these are controlled through WETDRY. It is often useful to look at the output file and identify cells that convert repeatedly from wet to dry. Try raising the wetting threshold for those cells. It may also be worthwhile looking at the boundary conditions associated with dry cells. <br />
<br />
:Sometimes cells will go dry in a way that will completely block flow to a sink or from a source. After that happens, the results are unlikely to be correct. It's always a good idea to look at the flow pattern around cells that have gone dry to see whether the results are reasonable.<br />
<br />
==See also==<br />
<br />
*[[GMS:MODFLOW#Post Processing|Post Processing]]<br />
<br />
*[[GMS:MODFLOW Packages Supported in GMS#Solver Packages|Solver Packages]]<br />
<br />
<br />
{{Navbox GMS}}<br />
[[Category:MODFLOW]]<br />
[[Category:MODFLOW Packages]]<br />
[[Category:MODFLOW Dialogs]]<br />
[[Category:External Links]]<br />
[[Category:PEST|ASP]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:MODFLOW&diff=121861GMS:MODFLOW2017-03-24T20:54:51Z<p>Dharker: Added original MODFLOW name for an fyi</p>
<hr />
<div>{{Infobox Model |<br />
|name= MODFLOW <br />
|model_type= 3D, cell-centered finite-difference, saturated flow model, steady state and transient analysis <br />
|versions= MODFLOW-88*, MODFLOW-96*, MODFLOW-2000, [[GMS:MODFLOW-2005|MODFLOW-2005]], [[GMS:MODFLOW-NWT|MODFLOW-NWT]], [[GMS:MODFLOW-LGR|MODFLOW-LGR]], [[GMS:MODFLOW-USG|MODFLOW-USG]]<br />* import only<br /><br />
|developer= USGS, [http://water.usgs.gov/nrp/gwsoftware/modflow2000/MFDOC/]<br />
|documentation=<br />
[http://gmsdocs.aquaveo.com/mf2k_flowprocess.pdf MF2K Flow Process]<br /> <br />
[http://gmsdocs.aquaveo.com/mf2005_flowprocess.pdf MF2005 Flow Process]<br /><br />
[http://gmsdocs.aquaveo.com/MF_NWT.pdf MF NWT]<br /><br />
[http://gmsdocs.aquaveo.com/MF-LGR.pdf MF-LGR]<br /><br />
[http://gmsdocs.aquaveo.com/MF-LGR-mult.pdf MF-LGR-mult]<br /><br />
[http://gmsdocs.aquaveo.com/MF-LGR-SFR.pdf MF-LGR-SFR]<br /><br />
[http://gmsdocs.aquaveo.com/tm6-A45.pdf MODFLOW-USG]<br /><br />
|tutorials= [[GMS:Tutorials#Models|MODFLOW Tutorials]]<br />
|packages= '''Flow:''' [[GMS:BCF_Package|BCF6]], [[GMS:HUF_Package|HUF]], [[GMS:LPF_Package|LPF]], [[GMS:UPW_Package|UPW]]<br /><br />
'''Solvers:''' [[GMS:DE4_Package|DE4]], [[GMS:GMG_Package|GMG]], [[GMS:NWT_Package|NWT]], [[GMS:PCG_Package|PCG]], [[GMS:LMG_Package|SAMG]], [[GMS:SIP_Package|SIP]], [[GMS:SSOR_Package|SOR]]<br /><br />
'''Other:''' [[GMS:Global_Options/Basic_Package|BAS6]], [[GMS:CHD_Package|CHD1]], [[GMS:CLN Process|CLN]],[[GMS:DRN_Package|DRN1]], [[GMS:DRT_Package|DRT1]], [[GMS:EVT_Package|EVT1]], [[GMS:ETS_Package|ETS1]], [[GMS:GAGE_Package|GAGE]], [[GMS:GHB_Package|GHB1]], [[GMS:GNC_Package|GNC]], [[GMS:HFB_Package|HFB1]], [[GMS:HUF_Package|HUF]], [[GMS:LAK_Package|LAK3]], [[GMS:MNW1_Package|MNW1]], [[GMS:MNW2_Package|MNW2]], [[GMS:MODFLOW#Output_Control|OUT1]], [[GMS:RCH_Package|RCH1]], [[GMS:RIV_Package|RIV1]], [[GMS:STR/SFR_Packages|SFR2]], [[GMS:STR/SFR_Packages|STR1]], [[GMS:SUB_Package|SUB1]], [[GMS:SWI_Package|SWI2]], [[GMS:WEL_Package|WEL1]], [[GMS:UZF_Package|UZF1]]<br />
}}<br />
{{MODFLOW Links}}<br />
GMS includes a comprehensive graphical interface to the groundwater model MODFLOW. MODFLOW (originally called the Modular Three-Dimensional Finite-Difference Ground-Water Flow Model) is a 3D, cell-centered, finite difference, saturated flow model developed by the United States Geological Survey (McDonald & Harbaugh, 1988). MODFLOW can perform both steady state and transient analyses and has a wide variety of boundary conditions and input options. In GMS, MODFLOW can work with the 3D Grid module and 3D UGrid module.<br />
<br />
GMS supports MODFLOW as a pre- and post-processor. The input data for MODFLOW are generated by GMS and saved to a set of files. These files are read by MODFLOW when MODFLOW is launched from the [[GMS:MODFLOW Commands|''MODFLOW'' menu]]. The output from MODFLOW is then imported to GMS for post-processing.<br />
<br />
A special version of MODFLOW is distributed with GMS. This version of MODFLOW is the same as the version distributed by the USGS except for a few minor changes primarily related to file input including reading input data from HDF5 files. These changes are clearly marked in the code. For more information see [[GMS:MODFLOW with HDF5 | MODFLOW with HDF5]].<br />
<br />
To learn more about using MODFLOW in GMS, please refer to the available [[GMS:Tutorials#Models|tutorials]].<br />
<br />
More information about MODFLOW is available from the [http://water.usgs.gov/nrp/gwsoftware/modflow2000/MFDOC/ USGS].<br />
<br />
The MOFLOW model is included with all [http://www.aquaveo.com/software/gms-pricing editions] of GMS, including the community version.<br />
[[Category:Link to Store]]<br />
<br />
==MODFLOW Versions==<br />
GMS supports all standard MODFLOW versions. For a list of input files and packages supported in each version see [http://water.usgs.gov/ogw/modflow/MODFLOW-2005-Guide/index.html?input_files_supported_in_vario.htm here].<br />
* [http://water.usgs.gov/software/MODFLOW-88/ MODFLOW-88] (import only)<br />
* [http://water.usgs.gov/software/MODFLOW-96/ MODFLOW-96] (import only)<br />
* [http://water.usgs.gov/nrp/gwsoftware/modflow2000/Guide/index.html MODFLOW-2000]<br />
* [[GMS:MODFLOW-2005|MODFLOW-2005]]<br />
* [[GMS:MODFLOW-NWT|MODFLOW-NWT]]<br />
* [[GMS:MODFLOW-LGR|MODFLOW-LGR]]<br />
* [[GMS:MODFLOW-USG|MODFLOW-USG]]<br />
<br />
==Pre-Processing==<br />
*[[GMS:MODFLOW_Commands|MODFLOW Menu Overview]]<br />
*[[GMS:Importing MODFLOW Files|Importing MODFLOW Files]]<br />
*[[GMS:Building a MODFLOW Model|Building a MODFLOW Model]]<br />
*[[GMS:Saving and Reading a MODFLOW Simulation|Saving a MODFLOW Simulation]]<br />
*[[GMS:Parameters|Parameters]]<br />
*[[GMS:Stochastic Modeling|Stochastic Modeling with MODFLOW]]<br />
*[[GMS:Interpolate_to_MODFLOW_Layers|Interpolate to MODFLOW Layers]]<br />
*[[GMS:MODFLOW Packages Supported in GMS|Packages Supported in GMS]]<br />
*[[GMS:Unsupported MODFLOW Features|Unsupported MODFLOW Features]]<br />
<br />
==Post-Processing==<br />
*[[GMS:MODFLOW Display Options|MODFLOW Display Options]]<br />
*[[GMS:MODFLOW Post-Processing Viewing Options|MODFLOW Post-Processing Viewing Options]]<br />
*[[GMS:Saving and Reading a MODFLOW Simulation|Reading a MODFLOW Simulation]]<br />
<br />
==MODFLOW Documentation==<br />
*[http://water.usgs.gov/ogw/modflow/ MODFLOW website]<br />
*[http://water.usgs.gov/nrp/gwsoftware/modflow2000/Guide/index.html Online guide to MODFLOW-2000]<br />
*[http://water.usgs.gov/ogw/modflow/MODFLOW-2005-Guide/ Online guide to MODFLOW-2005]<br />
*[http://water.usgs.gov/ogw/modflow-lgr/MODFLOW-LGR-Guide/ Online guide to MODFLOW-LGR]<br />
*[http://water.usgs.gov/ogw/modflow-nwt/MODFLOW-NWT-Guide/ Online guide to MODFLOW-NWT]<br />
*[http://gmsdocs.aquaveo.com/modflow88I.pdf MODFLOW 88I]<br /> <br />
*[http://gmsdocs.aquaveo.com/modflow88II.pdf MODFLOW 88II]<br /> <br />
*[http://gmsdocs.aquaveo.com/modflow96I.pdf MODFLOW 96I]<br /> <br />
*[http://gmsdocs.aquaveo.com/modflow96II.pdf MODFLOW 96II]<br /> <br />
*[http://gmsdocs.aquaveo.com/mf2k_calibration.pdf MF2K Calibration]<br /> <br />
*[http://gmsdocs.aquaveo.com/mf2k_flowprocess.pdf MF2K Flow Process]<br /> <br />
*[http://gmsdocs.aquaveo.com/mf2k_huf.pdf MF2K HUF]<br /> <br />
*[http://gmsdocs.aquaveo.com/mf2k_lmg.pdf MF2K LMG]<br /> <br />
*[http://gmsdocs.aquaveo.com/mf2k_lmt.pdf MF2K LMT]<br /> <br />
*[http://gmsdocs.aquaveo.com/mf2k_obssenspeprocess.pdf MF2K Observation, Sensitivity, and Parameter-Estimation Processes]<br /><br />
*[http://gmsdocs.aquaveo.com/mf2005_flowprocess.pdf MF2005 Flow Process]<br /><br />
*[http://gmsdocs.aquaveo.com/MF_NWT.pdf MF NWT]<br /><br />
*[http://gmsdocs.aquaveo.com/tm6-A45.pdf MF USG]<br /><br />
*[http://water.usgs.gov/ogw/mfusg/mfusg.1_3.zip MODFLOW-USG 1.3 Manual] in doc folder<br /><br />
<br />
<br />
{{Navbox GMS}}<br />
[[Category:MODFLOW]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=SMS:RiverFlow2D&diff=121817SMS:RiverFlow2D2017-03-23T23:33:48Z<p>Dharker: Noted 12.1 and later versions</p>
<hr />
<div>{{SMS Infobox Model |<br />
|name= RiverFlow2D<br />
|model_type= 2D current and sediment transport simulation.<br />
|developer= Dr. Reinaldo Garcia<br />
|web_site= [http://hydronia.net/computer-models-software hydronia.net]<br />
|tutorials= <br />
General Section<br />
* Data Visualization<br />
* Mesh Editing<br />
* Observation<br />
}}<br />
<br />
RiverFlow2D is a hydrodynamic, mobile bed model for rivers and estuaries that uses a stable and powerful finite element method to compute high resolution flood hydraulics, including supercritical and subcritical flows over dry or wet river beds. Use of flexible triangular mesh allows resolving the flow field, sediment transport and bed elevation changes around key features in complex river environments. RiverFlow2D (formally written as RiverFLO 2D or RiverFLO-2D) has been applied on numerous river projects worldwide including large rivers in the United States, South America, Europe and Asia. <br />
<br />
SMS 12.1 and later versions do not come packaged with installation files or a license for RiverFlow2D (unlike SMS 11.2), but can still run RiverFlow2D with the Generic Model Interface. Installation files, licensing, and technical support for RiverFlow2D in SMS 12.1 and later are only provided through its parent company [http://www.hydronia.com/riverflow2d/ Hydronia] ([mailto:support@hydronia.com support@hydronia.com]).<br />
<br />
==Functionality==<br />
Features<br />
*Flexible triangular finite element meshes<br />
*Mesh refinement to resolve complex river features<br />
*Supercritical and subcritical flow<br />
*Steady and time-dependent flow<br />
*Mobile-bed sediment transport<br />
*Numerically stable explicit solution scheme<br />
*Dry-wet bed capability not requiring initially wet elements<br />
*Parallelized code for multiple-core processor computers<br />
*Documented input ASCII, free format files<br />
*Comprehensive ASCII output files<br />
*Graphical output in a variety of formats<br />
<br />
==Using the Model / Practical Notes==<br />
<br />
The RiverFlow2D installation package includes several executable files. To connect SMS to the numeric engine:<br />
# Select the '''Preferences''' command from the ''Edit'' menu<br />
# Click on the ''File Locations'' tab in the [[SMS:Preferences| ''Preferences'']] dialog<br />
# In the ''Model Executables'' area, scroll down to the ''Generic'' line and click on the button on the right side. A dialog to select the executable will appear.<br />
# Browse to the RiverFlow2D program folder and select the RiverFlow2D program.<br />
# Click the '''Open''' button to select the file and the '''OK''' button to close the ''preferences'' dialog.<br />
<br />
==RiverFlow2D Components==<br />
In RiverFlow2D there are different supported components that can be specified by selecting the nodestring or element and assigning a Component or Boundary Condition to them. These options are not used is this tutorial but are available for other simulations. Here is an overview of the different options:<br />
<br />
====Nodestring====<br />
*'''''Exterior Boundary Condition''''': Allows users to specify one of the supported exterior boundary conditions. See the RiverFlow2D manual for more details for the different boundary condition types. This is normally done through the model but can be assigned directly to a nodestring.<br />
*'''''Interior Boundary Condition''''': Allows users to specify a stage-discharge rating table along an internal line in the model. More details are in the RiverFlow2D documentation<br />
*'''''Weir''''': A weir may be defined across a nodestring to have RiverFlow2D use the weir equation to calculate the flow from the upstream elements to the downstream.<br />
<br />
====Element====<br />
*'''''Pier''''': Pier locations at the centroid of the element may be specified and RiverFlow2D will simulate them using the drag equation. Users may also simulate a pier by representing it with a polygon and turning the meshing option off in the polygon attributes in the model.<br />
*'''''Source/Sink''''': The user may provide a hydrograph to simulate a point inflow or outflow. The Source/Sink location is the centroid of the element it is assigned to.<br />
*'''''Culvert Inlet''''': A culvert can be defined be selecting an inlet and outlet element and specifying the culvert parameters in the ''Culvert Inlet'' dialog. The culvert parameters are then set depending on the culvert component type option.<br />
*'''''Culvert Outlet''''': The outlet location of the culvert. The only parameter in this component is the name of the culvert specified in the ''Culvert Inlet'' dialog. This allows specifying multiple culverts. All other parameters are set in the ''Culvert Inlet'' dialog.<br />
<br />
==Graphical Interface==<br />
RiverFlow2D uses the [[SMS:Generic_Model_Graphical_Interface|Generic Model Graphical Interface]] which allows users to construct the grid, assign model parameters and boundary conditions based on a template provided by the RiverFlow2D developers, and view the output of an analysis.<br />
<br />
===Global Parameters===<br />
The 2DM file for RiverFlow2D has been set up with the following options in the ''Global Parameters'' dialog:<br />
*''Control Data'' &ndash; Sets the model run control parameters like run time and time step duration. Users may switch from a steady state model to a transient model and the associated parameters will be displayed and Boundary Condition options will update automatically. The initial conditions of the model can also be specified here.<br />
*''Sediment Control'' &ndash; Displays one of the different sediment discharge formulas supported. After selecting the method, the required inputs are displayed.<br />
*''Rainfall/Evaporation'' &ndash; Defines time varying rainfall and evaporation data. The RiverFlow2D model assumes that this rainfall or evaporation is constant over the entire model.<br />
*''Graphic Output Options'' &ndash; Contains the parameters that can be set for the graphical output plots that are generated while RiverFlow2D is running. These plots are useful to view potential problems so as to not have to wait until the model converges to see any major issues.<br />
*''Component Controls'' &ndash; Allows turning on and off the different specified components. Instead of deleting, for example, a set of piers, the user can simply turn the pier flag on and off to run the simulation with and without the effects of the piers.<br />
The options in the ''Global Parameters'' dialog can be changed using the [[SMS:Generic_Model_Graphical_Interface|Generic Model Graphical Interface]].<br />
<br />
==Modeling hints for RiverFlow2D ==<br />
* In the model parameters, RiverFlow2D supports a ''Variable Time step'' option. When this is on, the user must specify a multiplier. Experience has shown that users may need to try various values for this multiplier in order to get proper mass conservation.<br />
* The global parameter group ''Graphic Output Options'' causes the engine to launch a separate window during analysis to provide graphical feedback of its progress.<br />
<br />
==Reading Legacy Projects into SMS==<br />
An existing RiverFlow2D project consists of the following files:<br />
* *.dat &ndash; basic input data<br />
* *.fed &ndash; geometry<br />
* *.ifl &ndash; boundary conditions in open countours<br />
* *.hvt &ndash; water surface elevation vs. time<br />
* *.qvt &ndash; flow rate vs. time<br />
* *.plt &ndash; plot options<br />
* *.sed &ndash; sediment data<br />
* *.tba &ndash; list of boundary nodes<br />
<br />
Aquaveo does not currently have a utility to convert these files directly to SMS format. In order to work with data from this project in the SMS environment follow these steps:<br />
<br />
'''Mesh Data'''<br />
*Open the *.fed file in a file editing program such as Notepad ++. <br />
*Copy and paste the data into Microsoft Excel.<br />
*In Excel, click on the ''data'' menu and select '''Text to Columns'''. <br />
*Then select '''Fixed Width'''. This will divide the data into individual columns. Click '''next''' twice, then '''finish'''. <br />
*Most projects are only concerned with the data in the first three columns so delete the data in the other columns. <br />
*Delete one more sets of data now. Scroll down and notice that the data changes. This is because it switches from mesh data to element data. Delete the element data so only the mesh data remains. <br />
*Do a file 'Save as' and save the file as a comma delimited (*.csv) file. Click '''Ok''', then click '''No'''. The file is now ready to be read into SMS. <br />
*When reading the file into SMS, use the Import Wizard. In the ''Import Wizard'', make sure the file is set to ''Delimited'' and click '''Next'''. <br />
*Change the ''SMS data type'' to ''mesh'', then click '''Finish'''.<br />
*Once read into SMS, delete the undesired elements.<br />
<br />
'''Nodestring Boundary Conditions'''<br />
*Open the *.hvt file in a file editor and copy and paste the data into Excel. Click on the ''data'' menu and select '''Text to Columns'''. Then select ''Fixed Width''. Click '''next''' twice, then '''Finish'''. <br />
*Repeat the above step for the *.qvt file. The data in these files are now ready to be copied and pasted into SMS and assigned as boundary conditions in their respective nodestrings. <br />
<br />
'''Control Data'''<br />
<br />
The *.dat file does not need to be converted<br />
*Open the *.dat file into the Argus One RiverFlow2D engine. Note the data that appears. <br />
*In SMS, click on the ''RiverFlow2D'' menu and click ''Global Parameters''. Click on the ''Control Data'' tab and record the data from the *.dat file in the RiverFlow2D engine. <br />
<br />
'''Remaining Files'''<br />
<br />
These files are also read into the Argus One RiverFlow2D engine, and the data from there can be manually recorded in SMS under their respective tabs in ''RiverFlow2D'' | '''Global parameters'''.<br />
<br />
==Case Studies / Sample Problems==<br />
=== Hoh River Washington ===<br />
This [http://www.aquaveo.com/software/sms-learning-tutorials tutorial] is distributed with RiverFlow2D and includes a typical riverine application and floodplain.<br />
<br />
==External Links==<br />
* [http://www.hydronia.net www.hydronia.net]<br />
* [http://smstutorials-11.2.aquaveo.com/SMS_RiverFLO-2D.pdf SMS 11.2 RiverFLO-2D Tutorial PDF]<br />
<br />
==Related Topics==<br />
* [[SMS:Generic_Mesh_Model|Generic Model Interface]]<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
<br />
[[Category:SMS 2D Mesh|R]]<br />
[[Category:RiverFlow2D|R]]<br />
[[Category:Generic Interface|R]]<br />
[[Category:Archived]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=WMS:TOPAZ&diff=119973WMS:TOPAZ2017-02-20T21:57:10Z<p>Dharker: Defined DEDNM initialism</p>
<hr />
<div>The Topographic Parameterization Program (TOPAZ) was developed by the USDA-ARS (United States Department of Agriculture: Agricultural Research Service) National Agricultural Water Quality Laboratory under the direction of Dr. Jurgen Garbrecht. TOPAZ is a public domain program that is distributed free of charge to interested persons. A modified version of the program is distributed with WMS for the purpose of computing flow directions and flow accumulations for use in basin delineation with DEMs. However, TOPAZ is capable of further DEM elevation processing, including raster smoothing, basin and stream delineation and ordering, and development of other watershed parameters. If interested in obtaining the latest, complete version of TOPAZ, visit the USDA-ARS website ([http://www.ars.usda.gov/main/main.htm here]]) and click on TOPAZ.<br />
<br />
After obtaining the complete TOPAZ program, WMS is capable of writing an input file for the primary TOPAZ module DEDNM (Digital Elevation Drainage Network Model). DEDNM requires as input a file containing the elevations (must be named DEDNM.INP) and a control file named DNMCNT.INP.<br />
<br />
TOPAZ crashes if the file name is 60 characters or longer.<br />
<br />
==Computing Flow Data with TOPAZ==<br />
This command will save the current DEM elevations to a TOPAZ formatted input file along with a TOPAZ control file and then start the TOPAZ program. When TOPAZ is finished WMS will automatically read the flow directions (FLOVEC.DAT) and flow accumulations (UPAREA.DAT) computed by [[WMS:TOPAZ|TOPAZ]]. <br />
<br />
Because WMS is communicating with TOPAZ through disk files, specify the directory where WMS/TOPAZ perform this interaction. If the specified directory has an unusually long name TOPAZ may have some difficulties. In such cases, specify a directory with a shorter character string length.<br />
<br />
TOPAZ assumes that all depressions are a function of a lack of resolution in the DEM data and therefore it is not possible to delineate the watershed of a closed basin unless having identified the DEM cell of a natural depression to be a Depression Point from the [[WMS:DEM Point Attributes|''DEM Point Attributes'']].<br />
<br />
TOPAZ also creates a file named RELIEF.DAT that has the elevations of the depressionless or filled DEM. TOPAZ (and most grid-based delineation algorithms) assumes that any depression in the DEM is a result of inadequate resolution and not a natural depression. This is true for most depressions, but means that basins for natural depressions cannot be determined. However, with WMS, it is possible to define a low point in a natural depression as such and then WMS will flag it so that TOPAZ does not fill the depression and the drainage computed. This is done using the [[WMS:DEM Point Attributes|''DEM Point Attributes'']] dialog prior to running TOPAZ.<br />
<br />
==Exporting a TOPAZ Input File==<br />
The '''Export TOPAZ File''' command is provided for those who wish to use TOPAZ for purposes outside of what WMS needs (the flow direction and accumulation files). This format should be close to the public domain version of TOPAZ, but may be slightly out of date.<br />
<br />
<br />
==Related Topics==<br />
* [[WMS:Importing Flow Directions and Accumulations|Flow Directions and Accumulations]]<br />
* [[WMS:DEM Basins|Defining Basins]]<br />
* [[WMS:References|References]]<br />
<br />
<br />
{{Template:WMSMain}}<br />
[[Category:DEM|T]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=WMS:TOPAZ&diff=119819WMS:TOPAZ2017-02-16T23:55:42Z<p>Dharker: Used initialism</p>
<hr />
<div>The Topographic Parameterization Program (TOPAZ) was developed by the USDA-ARS (United States Department of Agriculture: Agricultural Research Service) National Agricultural Water Quality Laboratory under the direction of Dr. Jurgen Garbrecht. TOPAZ is a public domain program that is distributed free of charge to interested persons. A modified version of the program is distributed with WMS for the purpose of computing flow directions and flow accumulations for use in basin delineation with DEMs. However, TOPAZ is capable of further DEM elevation processing, including raster smoothing, basin and stream delineation and ordering, and development of other watershed parameters. If interested in obtaining the latest, complete version of TOPAZ, visit the USDA-ARS website ([http://www.ars.usda.gov/main/main.htm here]]) and click on TOPAZ.<br />
<br />
After obtaining the complete TOPAZ program, WMS is capable of writing an input file for DEDNM (the primary TOPAZ module). DEDNM requires as input a file containing the elevations (must be named DEDNM.INP) and a control file named DNMCNT.INP.<br />
<br />
TOPAZ crashes if the file name is 60 characters or longer.<br />
<br />
==Computing Flow Data with TOPAZ==<br />
This command will save the current DEM elevations to a TOPAZ formatted input file along with a TOPAZ control file and then start the TOPAZ program. When TOPAZ is finished WMS will automatically read the flow directions (FLOVEC.DAT) and flow accumulations (UPAREA.DAT) computed by [[WMS:TOPAZ|TOPAZ]]. <br />
<br />
Because WMS is communicating with TOPAZ through disk files, specify the directory where WMS/TOPAZ perform this interaction. If the specified directory has an unusually long name TOPAZ may have some difficulties. In such cases, specify a directory with a shorter character string length.<br />
<br />
TOPAZ assumes that all depressions are a function of a lack of resolution in the DEM data and therefore it is not possible to delineate the watershed of a closed basin unless having identified the DEM cell of a natural depression to be a Depression Point from the [[WMS:DEM Point Attributes|''DEM Point Attributes'']].<br />
<br />
TOPAZ also creates a file named RELIEF.DAT that has the elevations of the depressionless or filled DEM. TOPAZ (and most grid-based delineation algorithms) assumes that any depression in the DEM is a result of inadequate resolution and not a natural depression. This is true for most depressions, but means that basins for natural depressions cannot be determined. However, with WMS, it is possible to define a low point in a natural depression as such and then WMS will flag it so that TOPAZ does not fill the depression and the drainage computed. This is done using the [[WMS:DEM Point Attributes|''DEM Point Attributes'']] dialog prior to running TOPAZ.<br />
<br />
==Exporting a TOPAZ Input File==<br />
The '''Export TOPAZ File''' command is provided for those who wish to use TOPAZ for purposes outside of what WMS needs (the flow direction and accumulation files). This format should be close to the public domain version of TOPAZ, but may be slightly out of date.<br />
<br />
<br />
==Related Topics==<br />
* [[WMS:Importing Flow Directions and Accumulations|Flow Directions and Accumulations]]<br />
* [[WMS:DEM Basins|Defining Basins]]<br />
* [[WMS:References|References]]<br />
<br />
<br />
{{Template:WMSMain}}<br />
[[Category:DEM|T]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=WMS:TOPAZ&diff=119818WMS:TOPAZ2017-02-16T23:54:51Z<p>Dharker: fixed small spelling error</p>
<hr />
<div>The Topographic Parameterization Program (TOPAZ) was developed by the USDA-ARS (United States Department of Agriculture: Agricultural Research Service) National Agricultural Water Quality Laboratory under the direction of Dr. Jurgen Garbrecht. TOPAZ is a public domain program that is distributed free of charge to interested persons. A modified version of the program is distributed with WMS for the purpose of computing flow directions and flow accumulations for use in basin delineation with DEMs. However, TOPAZ is capable of further DEM elevation processing, including raster smoothing, basin and stream delineation and ordering, and development of other watershed parameters. If interested in obtaining the latest, complete version of TOPAZ, visit the United States Department of Agriculture's (USDA) Agricultural Research Service website ([http://www.ars.usda.gov/main/main.htm here]]) and click on TOPAZ.<br />
<br />
After obtaining the complete TOPAZ program, WMS is capable of writing an input file for DEDNM (the primary TOPAZ module). DEDNM requires as input a file containing the elevations (must be named DEDNM.INP) and a control file named DNMCNT.INP.<br />
<br />
TOPAZ crashes if the file name is 60 characters or longer.<br />
<br />
==Computing Flow Data with TOPAZ==<br />
This command will save the current DEM elevations to a TOPAZ formatted input file along with a TOPAZ control file and then start the TOPAZ program. When TOPAZ is finished WMS will automatically read the flow directions (FLOVEC.DAT) and flow accumulations (UPAREA.DAT) computed by [[WMS:TOPAZ|TOPAZ]]. <br />
<br />
Because WMS is communicating with TOPAZ through disk files, specify the directory where WMS/TOPAZ perform this interaction. If the specified directory has an unusually long name TOPAZ may have some difficulties. In such cases, specify a directory with a shorter character string length.<br />
<br />
TOPAZ assumes that all depressions are a function of a lack of resolution in the DEM data and therefore it is not possible to delineate the watershed of a closed basin unless having identified the DEM cell of a natural depression to be a Depression Point from the [[WMS:DEM Point Attributes|''DEM Point Attributes'']].<br />
<br />
TOPAZ also creates a file named RELIEF.DAT that has the elevations of the depressionless or filled DEM. TOPAZ (and most grid-based delineation algorithms) assumes that any depression in the DEM is a result of inadequate resolution and not a natural depression. This is true for most depressions, but means that basins for natural depressions cannot be determined. However, with WMS, it is possible to define a low point in a natural depression as such and then WMS will flag it so that TOPAZ does not fill the depression and the drainage computed. This is done using the [[WMS:DEM Point Attributes|''DEM Point Attributes'']] dialog prior to running TOPAZ.<br />
<br />
==Exporting a TOPAZ Input File==<br />
The '''Export TOPAZ File''' command is provided for those who wish to use TOPAZ for purposes outside of what WMS needs (the flow direction and accumulation files). This format should be close to the public domain version of TOPAZ, but may be slightly out of date.<br />
<br />
<br />
==Related Topics==<br />
* [[WMS:Importing Flow Directions and Accumulations|Flow Directions and Accumulations]]<br />
* [[WMS:DEM Basins|Defining Basins]]<br />
* [[WMS:References|References]]<br />
<br />
<br />
{{Template:WMSMain}}<br />
[[Category:DEM|T]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=WMS:TOPAZ&diff=119817WMS:TOPAZ2017-02-16T23:54:17Z<p>Dharker: Defined initialism</p>
<hr />
<div>The Topographic Parameterization Program (TOPAZ) was developed by the USDA-ARS (United States Department of Agriculture: Agricultural Research Services) National Agricultural Water Quality Laboratory under the direction of Dr. Jurgen Garbrecht. TOPAZ is a public domain program that is distributed free of charge to interested persons. A modified version of the program is distributed with WMS for the purpose of computing flow directions and flow accumulations for use in basin delineation with DEMs. However, TOPAZ is capable of further DEM elevation processing, including raster smoothing, basin and stream delineation and ordering, and development of other watershed parameters. If interested in obtaining the latest, complete version of TOPAZ, visit the United States Department of Agriculture's (USDA) Agricultural Research Service website ([http://www.ars.usda.gov/main/main.htm here]]) and click on TOPAZ.<br />
<br />
After obtaining the complete TOPAZ program, WMS is capable of writing an input file for DEDNM (the primary TOPAZ module). DEDNM requires as input a file containing the elevations (must be named DEDNM.INP) and a control file named DNMCNT.INP.<br />
<br />
TOPAZ crashes if the file name is 60 characters or longer.<br />
<br />
==Computing Flow Data with TOPAZ==<br />
This command will save the current DEM elevations to a TOPAZ formatted input file along with a TOPAZ control file and then start the TOPAZ program. When TOPAZ is finished WMS will automatically read the flow directions (FLOVEC.DAT) and flow accumulations (UPAREA.DAT) computed by [[WMS:TOPAZ|TOPAZ]]. <br />
<br />
Because WMS is communicating with TOPAZ through disk files, specify the directory where WMS/TOPAZ perform this interaction. If the specified directory has an unusually long name TOPAZ may have some difficulties. In such cases, specify a directory with a shorter character string length.<br />
<br />
TOPAZ assumes that all depressions are a function of a lack of resolution in the DEM data and therefore it is not possible to delineate the watershed of a closed basin unless having identified the DEM cell of a natural depression to be a Depression Point from the [[WMS:DEM Point Attributes|''DEM Point Attributes'']].<br />
<br />
TOPAZ also creates a file named RELIEF.DAT that has the elevations of the depressionless or filled DEM. TOPAZ (and most grid-based delineation algorithms) assumes that any depression in the DEM is a result of inadequate resolution and not a natural depression. This is true for most depressions, but means that basins for natural depressions cannot be determined. However, with WMS, it is possible to define a low point in a natural depression as such and then WMS will flag it so that TOPAZ does not fill the depression and the drainage computed. This is done using the [[WMS:DEM Point Attributes|''DEM Point Attributes'']] dialog prior to running TOPAZ.<br />
<br />
==Exporting a TOPAZ Input File==<br />
The '''Export TOPAZ File''' command is provided for those who wish to use TOPAZ for purposes outside of what WMS needs (the flow direction and accumulation files). This format should be close to the public domain version of TOPAZ, but may be slightly out of date.<br />
<br />
<br />
==Related Topics==<br />
* [[WMS:Importing Flow Directions and Accumulations|Flow Directions and Accumulations]]<br />
* [[WMS:DEM Basins|Defining Basins]]<br />
* [[WMS:References|References]]<br />
<br />
<br />
{{Template:WMSMain}}<br />
[[Category:DEM|T]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=WMS:GSSHA_Digital_Dams&diff=119752WMS:GSSHA Digital Dams2017-02-15T23:34:44Z<p>Dharker: /* Modification */ Clarified using depression masks by request of a customer</p>
<hr />
<div>Digital dams occur where a stream leaves a cell at or near a corner. Since flow occurs between adjacent cells and not between diagonal cells, the stream leaving at the cell corner leaves behind two stream banks adjacent to the flowing cell. These two stream banks block the overland flow, which can create numerical instabilities and will pool up the flowing water behind the banks. WMS now has several ways to visualize and adjust digital dams in the overland flow plane.<br />
<br />
===Visualization===<br />
WMS now has two ways to visualize digital dams. These options are accessible on the ''2D Grid'' tab of the ''Display Options'' dialog. Toggle on the ''Digital Dams'' option to have WMS identify digital dams is by looking for cells that are lower than their four neighbors. The cells that meet this criterion will be identified with a small square marker in the middle of the cell. <br />
<br />
The second method of visualization is employed by toggling on the ''Flow Vectors'' option in the ''2D Grid'' tab of the ''Display Options'' dialog. WMS displays flow direction arrows between cells based only on the differences in cell elevation. GSSHA computes overland flow based on the hydraulic grade surface, but this is often approximately equal to the elevation surface. A digital dam occurs when all four flow direction arrows indicate flow only coming into cell and not leaving the cell. <br />
<br />
:[[Image:GSSHA_flow_vectors.png]]<br />
<br />
A grid is shown with flow vectors (blue arrow) and digital dam markers (black squares). The flow vectors show the direction of flow between adjacent cells. The digital dam markers indicate cells where all four neighboring cells are higher in elevation.<br />
<br />
A method to help visualize the computational flow surface where the digital dams are is to turn on the ''Blocked Cells'' option in the'' 2D Grid display options''. Blocked cells treat each grid as a planar surface and draw them as such. A vertical line is drawn connecting the cell corners. Blocked cells are often used in combination with cell-filled contours.<br />
<br />
:[[Image:GSSHA_Cell_Fill_Block_Style_Digital_Dams.jpg]]<br />
<br />
The cells can be drawn in a block style that affords greater visualization of the computational surface. The black squares indicate cells where digital dams exist. The cells in this diagram are also cell filled, meaning that the cell is colored in one color based on the elevation of the center of the cell.<br />
<br />
===Modification===<br />
<br />
There are two ways in WMS of fixing digital dams. <br />
<br />
The first method is to run the CleanDam algorithm found in the ''GSSHA'' | '''Clean Digital Dams...''' menu command. CleanDam slightly alters the cell elevations in order to fix the digital dams. A summary of the CleanDam results can be viewed before closing the ''WMS Model Wrapper'' dialog. WMS automatically reads in the new elevations and replaces the existing elevation dataset.<br />
<br />
WMS can define a ''Depression Mask'' polygon in a GSSHA type coverage that masks cells contained within the polygon designated as a "Depression Mask" polygon type in the [[WMS:GSSHA Feature Polygons|Polygon Attributes dialog]]. The elevations of the cells located inside a depression mask polygon are not altered when the CleanDam program is run from WMS. There is a [[WMS:2D Grid Display Options|2D grid display option]] to display the 2D grid cells located within depression mask polygons.<br />
<br />
The other method of correcting any remaining digital dams is to manually adjust the cell elevations. Sometimes changing the grid resolution can help initially eliminate digital dams.<br />
<br />
==Related Topics==<br />
* [[WMS:GSSHA|GSSHA Overview]]<br />
* [[WMS:2D Grid Display Options|2D Grid Display Options]]<br />
<br />
{{GSSHAMain<br />
<br />
|PLinks=<br />
* [http://gsshawiki.com/index.php?title=Pre-Processing:Watershed_Delineation_and_Grid_Construction Watershed Delinieation and Grid Construction]<br />
** [http://gsshawiki.com/index.php?title=Pre-Processing:Editing_the_grid_to_correct_elevation_errors Editing the Grid to Correct Elevation Errors]<br />
<br />
|GUMLinks=<br />
* [http://gsshawiki.com/index.php?title=General_Considerations:General_Considerations General Considerations]<br />
** [http://gsshawiki.com/index.php?title=General_Considerations:Elevation_Map Elevation Map]<br />
<br />
|TutLinks=<br />
* [http://gsshawiki.com/index.php?title=Tutorials:3_Fixing_Digital_Dams Fixing Digital Dams]<br />
<br />
}}<br />
<br />
[[Category:GSSHA|D]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:MODFLOW-NWT&diff=119619GMS:MODFLOW-NWT2017-02-14T23:15:41Z<p>Dharker: /* External Links */ Changed 'Manual' to more accurate 'Online Guide'</p>
<hr />
<div>{{MODFLOW Links}}<br />
<br />
{{hide in print|Starting at GMS version 8.2, GMS supports MODFLOW-NWT.}} MODFLOW-NWT is a version of MODFLOW based on [[GMS:MODFLOW-2005|MODFLOW-2005]] that provides a different formulation of the groundwater flow equation designed to solve models that are non-linear due to unconfined cells or non-linear boundary conditions.<br />
<br />
== Choosing MODFLOW Version ==<br />
<br />
{{only in print|[[Image:Switching_MF2K5.jpg|200px|none|thumb|left|MODFLOW Global Option Dialog]]}}<br />
Choosing to use MODFLOW 2000, MODFLOW 2005, or MODFLOW-NWT is done in the [[GMS:Global_Options/Basic_Package|MODFLOW Global Options Dialog]]. At any time you can switch from one to the other.<br />
{{hide in print|[[Image:Switching_MF2K5.jpg|300px|none|thumb|left|MODFLOW Global Option Dialog]]}}<br />
<br />
== Changes to MODFLOW 2005 ==<br />
<br />
Source code differences between MODFLOW 2005 and MODFLOW-NWT.<br />
<br />
# '''UPW Package'''<br />
#* The [[GMS:UPW Package|Upstream Weighting package]] (UPW) is the flow package used with MODFLOW-NWT. The UPW package is only used with the [[GMS:NWT Package|NWT Solver Package]].<br />
# '''NWT Solver'''<br />
#* MODFLOW-NWT contains the [[GMS:NWT Package|NWT solver package]]. The NWT solver must be used when using the [[GMS:UPW Package|UPW flow package]].<br />
# '''WEL Package'''<br />
#* The WEL package was modified to add an option to decrease the pumping rate as the head drops below a user-specified percentage of cell thickness. The new option is called PHIRAMP.<br />
# '''SFR Package'''<br />
#* The SFR package is modified to avoid removing water from dry cells and to calculate derivatives for the Newton formulation.<br />
# '''UZF Package'''<br />
#* The UZF package is modified to avoid removing water from dry cells and to calculate derivatives for the Newton formulation.<br />
# '''Other Packages'''<br />
#* Poor input values for other packages can result in convergence failure. For example, an EVT extinction depth below the cell bottom elevation can result water being improperly removed from a dry cell.<br />
<br />
==MODFLOW-NWT Files==<br />
<br />
Here are tables of some of the available Input and Output files for MODFLOW-NWT. Note: MODFLOW will produce the LMT and HFF files even if transport is turned off.<br />
<br />
* For more information on these files see the [http://water.usgs.gov/ogw/modflow-nwt/MODFLOW-NWT-Guide/index.html? manual]<br />
<br />
{| class="wikitable" <br />
|+'''Required Input Files'''<br />
!width="40" align="center"|Name<br />
!width="250" align="center"|Description<br />
|-<br />
|MFN||MODFLOW Name File<br />
|-<br />
|GLO||Global Listing File<br />
|-<br />
|DIS||Discretization File<br />
|-<br />
|OC||Process Output Control Option File<br />
|-<br />
|BA6||Basic Package Global Options File<br />
|-<br />
|}<br />
<br />
{| class="wikitable" <br />
|+'''Solver Package File'''<br />
!width="40" align="center"|Name<br />
!width="250" align="center"|Description<br />
|-<br />
|DE4||Direct<br />
|-<br />
|GMG||Geometric Multi-Grid<br />
|-<br />
|LMG||Link Algebraic Multi-Grid<br />
|-<br />
|NWT||Newton<br />
|-<br />
|PCG||Preconditioned Conjugate-Gradient<br />
|-<br />
|SIP||Strongly Implicit Procedure<br />
|-<br />
|}<br />
<br />
{| class="wikitable" <br />
|+'''Input Flow Package Files'''<br />
!width="40" align="center"|Name<br />
!width="250" align="center"|Description<br />
|-<br />
|BCF||Evapotranspiration Segments<br />
|-<br />
|HUF||Evapotranspiration<br />
|-<br />
|LPF||Layer Property Flow<br />
|-<br />
|UPW||Unsaturated-Zone Flow<br />
|-<br />
|}<br />
<br />
{| class="wikitable" <br />
|+'''Optional Package Files'''<br />
!width="40" align="center"|Name<br />
!width="250" align="center"|Description<br />
|-<br />
|ASP||PEST Advanced Spacial Parameterization<br />
|-<br />
|CHD||Time-Variant Specified-Head<br />
|-<br />
|DRN||Drain<br />
|-<br />
|DRT||Drain Return<br />
|-<br />
|EVT||Evapotranspiration<br />
|-<br />
|ETS||Evapotranspiration Segments<br />
|-<br />
|GAG||Gage<br />
|-<br />
|GHB||General Head Boundary<br />
|-<br />
|HFB||Horizontal Flow Barrier<br />
|-<br />
|LAK||Lake<br />
|-<br />
|RCH||Recharge<br />
|-<br />
|RIV||River<br />
|-<br />
|SFR||Streamflow-Routing<br />
|-<br />
|STR||Stream-Routing<br />
|-<br />
|SUB||Subsidence<br />
|-<br />
|SWI||Seawater Intrusion<br />
|-<br />
|UZF||Unsaturated-Zone Flow<br />
|-<br />
|WEL||Process Well<br />
|-<br />
|}<br />
<br />
{| class="wikitable" <br />
|+'''Observation Input Files'''<br />
!width="40" align="center"|Name<br />
!width="250" align="center"|Description<br />
|-<br />
|OBS||Main Observation Process Input<br />
|-<br />
|DROB||Drain Observation<br />
|-<br />
|CHOB||Constant-Head Flow Observation Input<br />
|-<br />
|}<br />
<br />
{| class="wikitable"<br />
|+'''Output Files'''<br />
!align="center" width="50"|Name<br />
!width="350"|Description<br />
|-<br />
|MFS||MODFLOW Super File<br />
|-<br />
|MFW||GMS MODFLOW World File<br />
|-<br />
|MFR||GMS MODFLOW Result Index File<br />
|-<br />
|PRJ||Projection<br />
|-<br />
|CSV||Cell Summary Comma Separated Value Excel<br />
|-<br />
|HFF||Head and Flow File Link to MT3DMS<br />
|-<br />
|H5||Hierarchal Data Format (HDF5) Array & List Data<br />
|-<br />
|LMT||Link Modular Transport (MT3DMS)<br />
|-<br />
|M2P||MODFLOW Pest<br />
|-<br />
|PARAM||Parameter Information<br />
|-<br />
|}<br />
<br />
{| class="wikitable"<br />
|+'''Output Results Files'''<br />
!align="center" width="50"|Name<br />
!width="350"|Description<br />
|-<br />
|CCF||Cell-to-Cell Aquifer Flow<br />
|-<br />
|CCF2||Cell-to-Cell Stream Reach Outflow<br />
|-<br />
|DRW||Drawdown<br />
|-<br />
|GLO||Global Listing<br />
|-<br />
|HED||Head Output<br />
|-<br />
|OUT||Output<br />
|-<br />
<br />
{| class="wikitable"<br />
|+'''Output Package Files'''<br />
!align="center" width="50"|Name<br />
!width="350"|Description<br />
|-<br />
|MNW||Multi-Node Well<br />
|-<br />
|MNW2||Multi-Node Well Version 2<br />
|-<br />
|MNWI||Multi-Node Well Information<br />
|-<br />
|SWIBUD||Seawater Intrusion Package Budget<br />
|-<br />
|SWIZETA||Sewater Intrusion Package Zeta Surface<br />
|-<br />
<br />
{| class="wikitable"<br />
|+'''Output Data Exchange Files'''<br />
!align="center" width="50"|Name<br />
!width="350"|Description<br />
|-<br />
|_W||Weighted Residuals<br />
|-<br />
|_WW||Weighted Equivalents & Weighted Observation<br />
|-<br />
|_WS||Weighted Residuals and Simulated Equivalents<br />
|-<br />
|_R||Unweighted Residuals<br />
|-<br />
|_OS||Observed Values and Simulated Equivalents<br />
|-<br />
|_B||Data Exchange File<br />
|-<br />
|_NM||Weighted Residuals and Probability Plotting<br />
|-<br />
|}<br />
<br />
==External Links==<br />
<br />
*[http://water.usgs.gov/ogw/modflow-nwt/MODFLOW-NWT-Guide/index.html? MODFLOW-NWT Online Guide]<br />
<br />
{{Navbox GMS}}<br />
[[Category:MODFLOW]]<br />
[[Category:MODFLOW Dialogs]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:STR/SFR_Packages&diff=119617GMS:STR/SFR Packages2017-02-14T23:06:34Z<p>Dharker: /* The SFR Package Dialog */ Noted SFR limitations in GMS with optional parameters</p>
<hr />
<div>{{MODFLOW Links}}<br />
The Stream (written STR or STR1) and Streamflow-Routing (SFR2) packages are used to simulate the interaction between surficial streams and the groundwater. These packages are somewhat similar to the [[GMS:RIV Package|River package]] in that water can move from the stream to the aquifer or from the aquifer to the stream depending on the relative differences in the stream stage and the water table elevations. However, unlike the River package, flow is routed through the stream. For the STR package, simple channel hydraulics and Manning's equation are used to compute the stage in the stream. The SFR package has more sophisticated hydraulics and routing options.<br />
<br />
==Stream Network==<br />
<br />
When either the STR or SFR package is used, a complete, ordered stream network must be defined as shown in the following figure.<br />
<br />
:[[Image:stream.png|thumb|none|400 px|Ordered stream network used by the STR or SFR packages]]<br />
<br />
A stream network is composed of reaches and segments. A reach is the portion of a stream that lies inside a single cell. A single cell may contain multiple reaches. A segment is a group of reaches that forms one section of the stream. The reaches within a segment are always numbered from upstream to downstream. The segments should also be numbered from upstream to downstream.<br />
<br />
The incoming flowrate may only be defined for the topmost segments (segments 1, 4, and 6 in the above figure) and is typically entered as a positive value to represent the amount of flow in the stream channel. Flow is then routed and combined to get the incoming flowrate for the other segments. An exception to this is a diversion such as the canal at segment #2 in the above figure. In this case the flowrate into the diversion should be specified. The flow to the diversion would be subtracted from the flow coming out of segment #1 and whatever is left over would be routed to segment #3.<br />
<br />
===Defining Streams===<br />
Unlike other packages in GMS, a stream network cannot be created by selecting cells in the grid and manually assigning values to the cells. Due to the complex nature of the input and the requirement that the data be ordered in a specific fashion, a stream network can only be created using a series of Stream Arcs in the [[GMS:Map Module|Map module]]. The cell-by-cell values are automatically created and properly ordered when the [[GMS:Map to MODFLOW|'''Map &rarr; MODFLOW''']] command is selected.<br />
<br />
There are some restrictions on the STR and SFR conceptual models:<br />
*STR and SFR stream arcs cannot both exist in the same coverage because of the stream numbering issues.<br />
*All STR (or SFR) arcs must be in one coverage. There cannot be two or more coverages to represent the stream network.<br />
*SFR &ndash; All downstream streams must be diversions except for one. The variable OUTSEG is the segment number of the downstream segment that is not a diversion.<br />
*SFR &ndash; If the current segment has the diversion flag set then IUPSEG is the id of the upstream segment.<br />
<br />
==Set Arc Directions From Stream Data==<br />
Right-clicking on a coverage containing STR streams shows a ''Set Arc Directions From Stream Data'' menu item. This operation will cause all stream arcs to point downhill based on the elevation of the top of the river sediments as defined at the nodes.<br />
<br />
==STR Package==<br />
[[File:MODFLOW STR Package.png|thumb|400 px|The ''MODFLOW Stream (STR) Package'' dialog]]<br />
In the input file for the STR package, each reach is assigned the following values:<br />
<br />
*ijk indices of cell<br />
<br />
*segment ID<br />
<br />
*reach ID<br />
<br />
*stage (typically starting stage)<br />
<br />
*conductance<br />
<br />
*conductance factor (multipled by the conductance during parameter estimation)<br />
<br />
*Elevation of the bottom of the streambed<br />
<br />
*Elevation of the top of the streambed<br />
<br />
Each segment is assigned the following values:<br />
<br />
*incoming flow (for top segments and diversions)<br />
<br />
*width<br />
<br />
*slope<br />
<br />
*roughness coefficient<br />
<br />
*IDs of tributaries (upstream segments)<br />
<br />
*ID of upstream segment (for diversions only)<br />
<br />
When Manning's equation is used to route the flow through the network, the stream channels are assumed to have a rectangular cross section.<br />
<br />
When the '''Map &rarr; MODFLOW''' command is selected, GMS automatically does the following: classifies all of the cells beneath the streams as reaches, builds segments, numbers the reaches and segments, and assigns the appropriate values to the reaches and segments. These values defined at the nodes are linearly interpolated across the arcs when the model is converted. The slope assigned to reaches is computed by dividing the difference in the streambed top elevations at the ends of the arc by the arc length multiplied by the sinuosity factor. <br />
<br />
===The STR Package Dialog===<br />
Once the '''Map &rarr; MODFLOW''' command is selected and the stream data have been assigned to the grid cells, the data can be viewed and some of the input values can be edited using the ''Stream Package'' dialog. The options for the ''Stream Package'' dialog include:<br />
<br />
==== Calculate Stage====<br />
:The ''Calculate stage'' toggle is used to specify whether the Stream package should compute the stages (specified stages are initial values only) or whether the specified stages should be used directly.<br />
<br />
==SFR Package==<br />
[[File:MODFLOW SFR2 Package.png|thumb|400 px|The ''MODFLOW Stream (SFR2) Package'' dialog]]<br />
Support for the SFR2 package was added at GMS version 7.0.<br />
<br />
===The SFR Package Dialog===<br />
Once the '''Map &rarr; MODFLOW''' command is selected and the stream data have been assigned to the grid cells, the data can be viewed and some of the input values can be edited using the ''SFR Package'' dialog. Stream segments and reaches cannot be created in the ''SFR Package'' dialog&mdash;creation can only be done via the '''Map &rarr; MODFLOW''' command. The ''SFR Package'' dialog has two spreadsheets, one showing stream segments and one showing stream reaches. For a further explanation of the columns in each spreadsheet, refer to the [http://water.usgs.gov/nrp/gwsoftware/modflow2000/MFDOC/sfr.htm Online Guide to MODFLOW]. Note: GMS does not currently support the optional parameters ISFROPT, NSTRAIL, ISUZN, and NSFRSETS which are all defaulted to zero by GMS.<br />
<br />
====ISTCB2 info====<br />
If the ''Save ISTCB2 info to *.istcb2 text file'' option is on, MODFLOW will save more stream related data to a text file which has the same prefix as the other MODFLOW files and a "*.istcb2" extension. This text file will be displayed in the MODFLOW Solution in the [[GMS:Project Explorer|Project Explorer]] when the solution is imported. The data in this file includes information on "inflows and outflows from each reach; on stream depth, width, and streambed conductance; and on head difference and gradient across the streambed."<br />
<br />
If the ''Save ISTCB2 info to *.istcb2 text file'' option is off, streamflow out of each reach will be saved to the CCF file if the ''Save cell by cell flow terms to *.ccf file'' is on in the ''[[GMS:Output_Control|Output Control]]'' dialog.<br />
<br />
Starting at GMS 9.0, this information is saved to a second CCF file that will appear in the solution as "CCF2". This is so that the stream flow out of each reach is not included in the flows in and out of the aquifer in the [[GMS:Zone_Budget|flow budget]]. The total stream flow out of each reach is displayed at the bottom of the flow budget.<br />
<br />
===== STREAMFLOW_OUT dataset =====<br />
<br />
The stream flow out of each reach is stored in the ccf file under the heading STREAMFLOW_OUT. GMS can convert data in the CCF file to 3D grid datasets that can be contoured by right-clicking on the CCF file in the ''Project Explorer'' and using the ''CCF &rarr; Datasets'' command. If in the ccf file multiple flows are listed for the same cell, GMS sums them so that there is only one value for each cell in the resulting dataset. With most data this makes sense because the data represents the total flow into our out of the aquifer due to the BC (wells, river etc). The STREAMFLOW_OUT data is treated the same way, but in this case it doesn't make sense to sum the values because they don't represent flow to or from the aquifer. The problem becomes evident wherever there is more than one stream reach in a cell, which happens wherever a stream segment begins/ends in a cell. The STREAMFLOW_OUT dataset value will be the sum of all the reaches in the cell, which can make it appear as if much more water is flowing down the stream than there should be in that cell. If using SFR2, the user should save the istcb2 data as a text file (described above) which lists the streamflow out of each segment and reach separately. Despite this problem, the STREAMFLOW_OUT dataset can still be useful for contouring and display purposes.<br />
<br />
==Documentation==<br />
<br />
* [http://pubs.usgs.gov/of/1988/0729/report.pdf STR Package Documentation] 1989<br />
* [http://pubs.usgs.gov/tm/2006/tm6A13/pdf/tm6a13.pdf SFR2 Package Documentation] April 2010<br />
<br />
<br />
{{Navbox GMS}}<br />
[[Category:MODFLOW]]<br />
[[Category:MODFLOW-USG]]<br />
[[Category:MODFLOW Packages]]<br />
[[Category:MODFLOW Dialogs]]<br />
[[Category:External Links]]<br />
[[Category:Needs Update]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:PEST_Dialog&diff=119614GMS:PEST Dialog2017-02-14T20:54:44Z<p>Dharker: /* Max number of iterations (NOPTMAX) */ Spell fix corrected to American spelling</p>
<hr />
<div>{{MODFLOW Links}}<br />
{{Infobox Calibration}}<br />
[[File:PEST ParameterEstimation.jpg|thumb|The ''PEST'' parameter estimation dialog]]<br />
The ''Parameter Estimation'' dialog (''MODFLOW'' | '''Parameter Estimation''') allows the editing of inverse modeling options that are specific to PEST. This dialog is available when ''Parameter Estimation'' option is chosen as the [[GMS:Global Options/Basic Package|''Run'' option]] in the [[GMS:Global Options/Basic Package|''Global Options\Basic Package'']] dialog.<br />
<br />
==Max number of iterations (NOPTMAX)==<br />
This value (NOPTMAX) sets the maximum number of optimization iterations that PEST is permitted to undertake on a particular parameter estimation run. To ensure that PEST termination is triggered by other criteria, more indicative of parameter convergence to an optimal set or of the futility of further processing, set this variable very high. A value of 20 to 30 is often appropriate.<br />
<br />
If NOPTMAX is set to 0, PEST will not calculate the Jacobian matrix. Instead it will terminate execution after just one model run. This setting can thus be used when calculating the objective function corresponding to a particular parameter set and/or to inspect observation residuals corresponding to that parameter set.<br />
<br />
If NOPTMAX is set to –1, PEST will terminate execution immediately after it has calculated the Jacobian matrix for the first time. The parameter covariance, correlation coefficient and eigenvector matrices will be written to the run record file, and parameter sensitivities will be written to the sensitivity file; these are based on the initial parameter set supplied in the PEST control file.<br />
<br />
==Max number of iterations with no improvement (NPHINORED)==<br />
If PEST has failed to lower the objective function over NPHINORED successive iteration it will terminate execution. A value of 3 or 4 is often suitable for this variable.<br />
<br />
==Advanced Options==<br />
===Max number of relative convergence iterations (NPHISTP); Relative convergence limit (PHIREDSTP)===<br />
If, in the course of the parameter estimation process, there have been NPHISTP optimisation iterations for which<br />
<br />
(Φi - Φmin )/Φi ≤ PHIREDSTP (4.6)<br />
<br />
(Φi being the objective function value at the end of the i’th optimisation iteration and Φmin being the lowest objective function achieved to date), PEST will consider that the optimisation process is at an end.<br />
<br />
For many cases 4 and 0.01 are suitable values for NPHISTP and PHIREDSTP respectively. However, be careful not to set NPHISTP too low if the optimal values for some parameters are near or at their upper or lower bounds. In this case it is possible that the magnitude of the parameter upgrade vector may be curtailed over one or a number of optimisation iterations to ensure that no parameter value overshoots its bound. The result may be smaller reductions in the objective function than would otherwise occur.<br />
<br />
===Max number of relative parameter change iterations (NRELPAR); Relative parameter change criterion (RELPARSTP)===<br />
If the magnitude of the maximum relative parameter change between optimisation iterations is less than the Relative Parameter Change Criterion (RELPARSTP) over Max # of Relative Parameter Change Iterations (NRELPAR) successive iterations, PEST will cease execution.<br />
<br />
All adjustable parameters, whether they are relative-limited or factor-limited, are involved in the calculation of the maximum relative parameter change. RELPARSTP is a real variable for which a value of 0.01 is often suitable. NRELPAR is an integer variable; a value of 2 or 3 is normally satisfactory.<br />
<br />
Max relative parameter change per iteration<br />
This (RELPARMAX) is the maximum relative change that a parameter is allowed to undergo between optimisation iterations.<br />
<br />
===Max factor parameter change per iteration (FACPARMAX)===<br />
This value is the maximum factor change that a parameter is allowed to undergo during an iteration.<br />
<br />
===Run-time matrix options===<br />
Select these options if wanting these arrays written to external files. These arrays will also be written to the PEST output file (*.rec).<br />
<br />
===Measurement obj func upper limit (PHIMLIM)===<br />
This is the upper limit of the measurement objective function (i.e., the upper level of model-to-measurement misfit) that is tolerable when trying to minimise the regularisation objective function Φr.<br />
<br />
===Measurement obj func accept. level (PHIMACCEPT)===<br />
This is the acceptable level for the measurement objective function that PEST uses to change its method of calculating the Marquardt Lamdas (see PEST documentation).<br />
<br />
Normally PHIMACCEPT should be about 5% to 10% greater than PHIMLIM. However if PEST is performing well, the user may wish to make it closer to PHIMLIM than this. In choosing the best parameter set at any stage of the optimisation process (for recording in the parameter value file) PEST looks at all parameter sets for which it has carried out model runs up to that point in the process. If any of these runs have resulted in an objective function less than PHIMACCEPT, it then searches from among these runs for the parameter set which gave rise to the lowest regularisation objective function. If PHIMACCEPT is set too close to PHIMLIM, PEST’s selection of the best parameter set may be restricted somewhat, for there may be some parameter sets for which the measurement objective function Φm is just above PHIMACCEPT but for which Φr is quite low. Alternatively, if PHIMACCEPT is set too large, then PEST might not try hard enough to reduce Φm to Φmi, preferring instead to work within the weaker constraint set by PHIMACCEPT. When working in regularisation mode, PEST prints out Φr and Φm for every parameter upgrade attempt. It will be apparent from this information whether PHIMACCEPT has been set correctly.<br />
<br />
===FRACPHIM===<br />
PEST ignores the value supplied for FRACPHIM unless it is greater than zero. A value of between zero and 1.0 (but normally less than about 0.3) can be supplied for this variable if the user is unsure what value to use for PHIMLIM. See the PEST documentation.<br />
<br />
===Automatic user intervention (AUI)===<br />
When the optimization process undertaken by PEST appears to be going nowhere, the situation can often be remedied by selectively withdrawing certain parameters (normally the most insensitive ones) from the parameter estimation process. This process has been automated in PEST using the AUI option. For more information on AUI see the PEST documentation (section 5.7 of the PEST manual).<br />
<br />
It should be noted that use of the SVD process in PEST is usually more effective than AUI as the SVD process removes insensitive parameters.<br />
<br />
==Parallel PEST==<br />
<br />
GMS allows running PEST in parallel on a single machine to take advantage of multiple cores with the Parallel PEST Utility. This can greatly speed up the PEST runs.<br />
*''Specify number of slaves''<br />
*:"Slaves" refers to the separate processes that will be run in parallel. Specify the number of slaves or, if not specified, GMS will automatically determine the number of cores available on the machine and use that for the number of slaves.<br />
*''Specify slave directory''<br />
*:By default, GMS uses the system temp directory as the slave directory. However, a user may specify a different folder for the files that are used by the slaves. If the specified slave directory is invalid then GMS will use the system temp directory.<br />
*''Parallel PEST wait time''<br />
*:The wait time is the amount of time that PEST will pause at certain strategic places in their communication. Normally the default value should work fine. However, if either PEST reports a sharing violation on the hard drive then increase the value of the wait time.<br />
<br />
The PEST model can also be run with parallel processing across multiple machines with setup outside of GMS with PSLAVE. More information about Parallel PEST can be found in the [http://www.pesthomepage.org/getfiles.php?file=newpestman1.pdf PEST Manual] starting on page 222 from the [http://www.pesthomepage.org/Downloads.php PEST Downloads page].<br />
<br />
==SVD (Singular Value Decomposition)==<br />
<br />
The ''Use SVD'' toggle is available to turn on the SVD functionality in PEST. For a more complete explanation of SVD, see the [http://gmsdocs.aquaveo.com/pest.pdf PEST manual] in section 8.4. The inputs to the SVD process can be edited by selecting the '''SVD Options''' button.<br />
<br />
The SVD process analyzes the parameters that are currently part of the parameter estimation process and removes parameters that are not helping to solve the problem. The user can limit the number of parameters used by specifying a maximum number of singular values (MAXSING) or by specifying EIGTHRESH. By default MAXSING is set to 1000 and EIGTRESH to 1E-7, so that the number of parameters will be limited by the value of EIGTHRESH.<br />
*MAXSING &ndash; maximum number of singular values to include in the inversion process.<br />
*EIGTHRESH &ndash; a ratio of the lowest to highest parameter eigen value (a value of 1E-7 is usually sufficient). <br />
*EIGWRITE &ndash; controls output written to the *.svd file by PEST. When the value is 1 a more verbose file is written that can become quite large. By default the value of EIGWRITE is set to 0.<br />
<br />
==SVD-Assist==<br />
<br />
The ''Use SVD-Assist'' toggle turns on the SVD-Assist process for PEST. This process is particularly advantageous for models that have hundreds or thousands of parameters (such as pilot points). SVD-Assist involves 3 basic steps.<br />
#First, PEST runs MODFLOW once for every parameter in order to compute a matrix. This information is used to create super parameters that are combinations of the parameters originally specified.<br />
#Second, SVDAPREP is run to create a new PEST control file. The options for SVDAPREP are entered by selecting the '''SVD-Assist Options''' button. For more information on each of these options see the PEST manual in section 8.5.4.2. The most important option entered is the ''Specify # super param'' and this is set to ''No'' by default. When this option is set to ''No'', then the information written to the *.svd file will be used to specify the number of super parameters.<br />
#Third, PEST runs using the new control file written by SVDAPREP. This should result in significantly fewer model runs for each PEST iteration. This often results in an order of magnitude reduction in the number of runs required for each PEST iteration.<br />
<br />
==Tikhonov Regularization==<br />
<br />
Tikhonov Regularization (prior information for pilot points). This section of the dialog allows the user to select the method for include Tikhonov regularization in the PEST run. If neither option is turned on then regularization will not be included in the PEST run.<br />
<br />
The first option, ''Preferred homogeneous regularization'', is the option that GMS has always supported with pilot points. When using this option, prior information equations are included that impose a homogeneity constraint on the pilot points. This means that in absence of other information, pilot points that are near to one another should have about the same value.<br />
<br />
*Prior information power factor<br />
*:This is used to change the weight applied to the prior information equations for the pilot points. A value of 1 is normally sufficient. The prior information equations impose a homogeneity constraint on the pilot points. This means that in absence of other information, pilot points that are near to one another should have about the same value. When the prior information equations are created GMS will compute an inverse distance weight between each pilot point and all other pilot points for a given parameter. This weight is then raised to the power of the ''Prior information power factor'' and assigned to the equation for a given pair of points. So to increase the homogeneity constraint (assign a higher weight to the prior information equation), the user should decrease this value. To decrease the homogeneity constraint (assign a lower weight to the prior information equation), the user should increase this value.<br />
<br />
The second option, ''Preferred value regularization'', is a new option beginning with GMS version 8.0. When this option is used, prior information equations are included that constrain the pilot points near their starting values. Using this option the user can give a set of starting values to the pilot points based on field data or professional judgment. PEST will only change those values if necessary to calibrate the model.<br />
<br />
Also new in GMS 8.0, parameters of different types (HK, RCH) are put into different regularization groups. According to John Doherty, this helps differentiate weighting amongst pertinent prior information equations.<br />
<br />
==See also==<br />
<br />
[[GMS:Model Calibration|Model Calibration]]<br />
<br />
{{Navbox GMS}}<br />
[[Category:MODFLOW]]<br />
[[Category:Calibration]]<br />
[[Category:Calibration Dialogs]]<br />
[[Category:GMS Dialogs|P]]<br />
[[Category:PEST]]<br />
[[Category:Needs Update]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=System_Requirements&diff=119300System Requirements2017-02-08T21:51:29Z<p>Dharker: Added term 'software' for search engine optimization</p>
<hr />
<div>System requirements for GMS, SMS and WMS software.<br />
<br />
== Windows 10 ==<br />
Windows 10 is supported in GMS 10.0, SMS 12.1, WMS 10.0 and greater versions only.<br />
<br />
{| class="wikitable"<br />
! Component !! Minimum Required !! Recommended<br />
|-<br />
| '''RAM''' || 4 GB || 8 GB or greater<br />
|-<br />
| '''CPU'''<br />
|colspan="2"| XMS software is CPU intensive. We recommend the fastest CPU your budget allows.<br />
|-<br />
| '''Hard Disk Free Space'''<br />
|| 2 GB || 4 GB or greater<br />
|-<br />
| '''Graphics Card'''<br />
| '''For all display features to be enabled, OpenGL 1.5 or higher must be supported.'''<br />
| The use of a dedicated graphics card is strongly recommended. Integrated graphics cards are often problematic.<br />
|-<br />
| '''Minimum Resolution'''<br />
||1920x1080<br />
||1920x1080 or greater<br />
|}<br />
<br />
== Windows 8 ==<br />
Windows 8 may have compatibility issues with XMS software. It is recommended to upgrade to Windows 10.<br />
<br />
{| class="wikitable"<br />
! Component !! Minimum Required !! Recommended<br />
|-<br />
| '''RAM''' || 4 GB || 8 GB or greater<br />
|-<br />
| '''CPU'''<br />
|colspan="2"| XMS software is CPU intensive. We recommend the fastest CPU your budget allows.<br />
|-<br />
| '''Hard Disk Free Space'''<br />
|| 2 GB || 4 GB or greater<br />
|-<br />
| '''Graphics Card'''<br />
| '''For all display features to be enabled, OpenGL 1.5 must be supported.'''<br />
| The use of a dedicated graphics card is strongly recommended. Integrated graphics cards are often problematic.<br />
|-<br />
| '''Minimum Resolution'''<br />
||1920x1080<br />
||1920x1080 or greater<br />
|}<br />
<br />
== Windows 7<ref>Windows 7 is supported in GMS 7.0, SMS 10.1 and greater versions only.</ref> ==<br />
Windows 7 is supported in GMS 7.0, SMS 10.1, WMS 8.3 and greater versions only.<br />
<br />
{| class="wikitable"<br />
! Component !! Minimum Required !! Recommended<br />
|-<br />
| '''RAM''' || 4 GB || 8 GB or greater<br />
|-<br />
| '''CPU'''<br />
|colspan="2"| XMS software is CPU intensive. We recommend the fastest CPU your budget allows.<br />
|-<br />
| '''Hard Disk Free Space'''<br />
|| 2 GB || 4 GB or greater<br />
|-<br />
| '''Graphics Card'''<br />
| '''For all display features to be enabled, OpenGL 1.5 must be supported.'''<br />
| The use of a dedicated graphics card is strongly recommended. Integrated graphics cards are often problematic.<br />
|-<br />
| '''Minimum Resolution'''<br />
||1920x1080<br />
||1920x1080 or greater<br />
|}<br />
<br />
== Notes ==<br />
* There may be display problems when running over a remote desktop. This can usually be fixed by restarting the software after beginning/ending a remote desktop session. Remote Desktop cannot be used with single-user/standalone locks, only with network locks.<br />
* Always download and install the latest drivers from your graphics card vendor. Graphics card problems are often due to using the wrong or outdated drivers. See [[Graphics Card Troubleshooting]] for instructions on how to download and install graphics card drivers. If continuing to experience problems after updating a graphics card drivers, contact [http://www.aquaveo.com/technical-support/ support].<br />
<br />
==See also==<br />
* [[Graphics Card Troubleshooting]]<br />
<br />
== External Links ==<br />
* [http://support.microsoft.com/kb/190900 Description of the DirectX Diagnostic Tool]<br />
<br />
[[Category:General Information|System]]<br />
[[Category:External Links]]<br />
[[Category:Support]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=WMS:Release_Notes_WMS&diff=119077WMS:Release Notes WMS2017-02-03T23:10:45Z<p>Dharker: /* Intermediate release WMS 8.1.3 &ndash; November 4, 2008 */ Spell fix</p>
<hr />
<div>{{TOCright}}<br />
== Important Note ==<br />
'''If you download and install the latest update and your software maintenance has expired, you will not be able to run WMS. Please make sure your WMS maintenance license has not expired before downloading. You can determine your maintenance expiration date by selecting the ''[[WMS:Help Menu|Help | Register]]'' command from WMS. You can renew your maintenance by visiting [http://www.aquaveo.com Aquaveo's web page] or by contacting a sales representative. Prices and other information about renewing your license are available on the [http://www.aquaveo.com/wms-pricing WMS Pricing Page]. The latest update to WMS can be downloaded [http://www.aquaveo.com/downloads?tab=3#TabbedPanels here].'''<br />
<br />
=WMS 10.1 Bugfixes=<br />
==Intermediate Release WMS 10.1.11 - Release October 11, 2016==<br />
*09106 Problem importing .cmt files in the GSSHA mapping table editor<br />
*09112 Problem setting contour values in contour options dialog<br />
*09108 Problem downloading vector soils data from georgia<br />
*09066 WMS doesn't seem to be computing the Culvert Analysis<br />
*09072 Crash When Deleting 2D Grid<br />
*09082 Crash importing TIF<br />
*09026 Channel Arc Error in GSSHA Tutorial<br />
*08982 Crash when bringing up help with no internet connection or bad connection to xmswiki.com<br />
*08532 Ground Elevations not Being assigned to Nodes in EPA-NET Model Interface<br />
*08961 Problem retaining data in an EPANET model<br />
<br />
==WMS 10.1.10 - Release June 07, 2016==<br />
*[[WMS:What%27s_new_in_WMS_version_10.1|Full release]]<br />
<br />
==WMS 10.1.7 (Beta) - Release January 18, 2016==<br />
*[[WMS:What%27s_new_in_WMS_version_10.1|Beta release]]<br />
<br />
=WMS 10.0 Bugfixes=<br />
==Intermediate Release 10.0.12 &ndash; February 8, 2015==<br />
*08570 - Duplicated 1D 2D BCs and Links Coverages have "linked" BC Attributes<br />
*08579 - Nodes not Renumbered in Merged Coverages<br />
*08474 - WMS crashes after right clicking on Terrain Data sub menu item.<br />
*08400 - Link Icon not Created in the Correct Location for 1D Schematic<br />
*08421 - TOPAZ is reporting error about elevation values that is inaccurate<br />
*08131 - Problem saving HMS rainfall from WMS 10.0<br />
* Other RegWiz Problems<br />
<br />
==Intermediate Release 10.0.11 &ndash; September 16, 2015==<br />
*8132 - current projection has changed to object projection in basic HMS modeling tutorial<br />
*8134 - Edit | Current Projection needs to be replaced in the tutorials<br />
*8182 - WMS not exporting rainfall correctly for MODCLARK gridded precipitation<br />
*8179 - SMPDBK Flood Conversion<br />
*8124 - TC values not calculated<br />
*7996 - Strange error message when creating duplicate solution names in the project explorer<br />
*8022 - Bogus Flow Values message after computing basin data twice<br />
*7995 - Crash when creating new HY-12 Structure<br />
*8001 - .xys file Not Importing<br />
*8053 - HEC HMS Channel Routing Parameters not exported<br />
*8007 - WMS Crashes When Opening flood.wpr.<br />
*8013 - WMS Crashes When Opening Run1.wms<br />
*8014 - WMS crashes when clicking River Tools | Map -> 1D Schematic in the main menu.<br />
*8004 - MODRAT Interface Schematic - Tutorial needs updating for changes in the detention basin calculator<br />
*8020 - Add option to calibrate to Total Suspended Solids (TSS) at interior points in the GSSHA interface<br />
*0542 - Training slides need to be updated to discuss concepts intoroduced by the new DEM Delineation tutorial<br />
*4052 - Interface to create automated calibration files when the model is calibrated to one or more internal points<br />
*4762 - Replace WMS FHWA calculators with the Hydraulic Toolbox calculators (40 hours)<br />
*4833 - The project explorer needs an horizontal scroll bar and problems with the vertical scroll bar<br />
*5900 - Check into reading data into WMS from the national map viewer<br />
*5898 - Is there a way WMS could download the data on the national map viewer?<br />
*6120 - Test HMS 4.0 with WMS 9.1<br />
*7987 - NCDC Climate data web services used in WMS are being phased out<br />
*7597 - WMS dev can't access NSS_v6.mdb<br />
*8002 - Problem importing DEM in WMS 10.0 and later versions<br />
*8003 - Problem assigning index maps to mapping tables when there are different scenarios<br />
*7906 - Box culvert dimensions save incorrectly<br />
*7943 - Backwater cards not saving<br />
*7907 - GSSHA depth grid not saving/exporting correctly for import into ArcMap<br />
<br />
==Intermediate Release 10.0.10 &ndash; May 6 2015==<br />
<br />
*Merged revision(s) 35575 from devproj/trunk/Dev: Fixed issue 0008002: Problem importing DEM in WMS 10.0 and later versions. This problem was caused by SVN revision 33257. Revision 33257 changed how we handle the Y-resolution so it's not a...<br />
<br />
==Intermediate Release 10.0.9 &ndash; Feb 23 2015==<br />
<br />
*Merged revision(s) 33350 from devproj/trunk/Dev: * Fix problem with assigning GSSHA lake cells when the lake outlet node is downstream from an embankment edge on the grid ........ <br />
*Merged revision(s) 32899 from devproj/trunk/Dev: Fix problems with WMS GSSHA tutorial tests--when running multiple GSSHA scenarios, the mapping tables were using the same memory in each of the scenarios instead of making a new copy for each...<br />
*Merged revision(s) 35539 from devproj/trunk/Dev: Fixed issue 0007943: Backwater cards not saving. See bug report for information about bugfix. ........ <br />
*Merged revision(s) 35516 from devproj/trunk/Dev: Fixed issue 0007907: GSSHA depth grid not saving/exporting correctly for import into ArcMap. See bug report for more information. ........ <br />
*Merged revision(s) 35514 from devproj/trunk/Dev: Fixed issue 0007906: Box culvert dimensions save incorrectly ........ <br />
*Merged revision(s) 35355 from devproj/trunk/Dev: Fixed issue 0007959: Multiple Items Being Selected When Creating New Materials in the Materials Data Dialog. See bug report for more information. ........ <br />
*Merged revision(s) 35321 from devproj/trunk/Dev: Fixed a problem with the rainfall grid and other grids (land use, soil type) not being displayed if the display option to display these grids is turned on. Also the option to display these g...<br />
*Merged revision(s) 35294 from devproj/trunk/Dev: Fixed a problem with the grid control (spreadsheets) not copying/pasting values correctly after you have clicked on a toggle or a button. ........ <br />
*Merged revision(s) 34934 from devproj/trunk/Dev: Added dao.dll to WMS installation to fix a problem with NSS; Changed the bin.bat file so this file is also included in the 64 bit version. ........ <br />
*Merged revision(s) 34894 from devproj/trunk/Dev: Fixed issue 0007849: Selecting TIN Dataset Properties or View values Causes Crash: Bring up error message if no vertices exist that are associated with the selected dataset. ........ <br />
*Merged revision(s) 34885 from devproj/trunk/Dev: Fix a problem with not saving the GSSHA Overbank Flow and the Overland Backwater options in the GSSHA channel routing options dialog. We were not saving these values out correctly when the u...<br />
*Merged revision(s) 34880 from devproj/trunk/Dev: Fixed issue #0007877: Problem computing storage capacity curve. If a user sets the base elevation to be below the bottom-most elevation in the basin, the hydraulic toolbox would always be in...<br />
*Merged revision(s) 34342 from devproj/trunk/Dev: Get the CORINE Land Cover Europe dataset working (they added "2000" onto the end of the name...this caused it not to work). ........ <br />
*Renamed all the model build files to get rid of the "_" that was causing errors with the automated builds.<br />
*Updated version numbers for WMS, HY8, and Hydraulic Toolbox (associated with WMS 10.0)<br />
<br />
==Intermediate Release 10.0.8 &ndash; Jan 28 2015==<br />
<br />
<br />
* Merged several revisions...some changes from revision 32779 and previous related revisions to convert the GSSHA model pointers to shared pointers. * Also added the Tikhonov option for the GSSHA model that was added to the dev version. * A...<br />
*0007561: Renaming a Project Explorer item fails if mouse moved <br />
*Update HY12, Hydraulic Toolbox, and HY8 version numbers so these are updated when you install WMS.<br />
<br />
==Intermediate Release 10.0.7 &ndash; Nov 13 2014==<br />
<br />
*Merged revision(s) 33893 from devproj/trunk/Dev: Commented out the ASTER web service from our program-defined options since it's no longer reliable (when we upgrade to Global Mapper 16 we will add the ASTER GDEM v2 web service in place of t...<br />
*Merged revision(s) 33870 from devproj/trunk/Dev: Fixed crash associated with issue 0007666: Save/Export HMS model files crashes WMS See bug report for more information. ........ <br />
*0007574: Saving static image does not replace existing file. <br />
*0007574: Saving static image does not replace existing file. <br />
*Merged revision(s) 33360 from devproj/trunk/Dev: Fixed problems with WMS corrupting files after changes to the map, TIN, or scatter data because of the changes to the project-on-the-fly code. ........ <br />
*Merged revision(s) 33268 from devproj/trunk/Dev/WMS/APP/source/Hydrology/GSSHA/casc2d.cpp: Fixed issue 0007564: Arc Info Grid Is Different Than Original Grid See bug report for more information. ........ <br />
*Merged revision(s) 33248 from devproj/trunk/Dev: Work on issue 0007634: CE-QUAL-W2 Problems: See bug report for more information. ........ <br />
*Merged revision(s) 33189-33190 from devproj/trunk/Dev: Fixed issue 0007594: Link/Node data results displayed at -999.99 for nodes within GSSHA reservoirs. See bug report for more information. ........ Fixed issue 0007594: Link/Node data re...<br />
*Merged revision(s) 33054 from devproj/trunk/Dev: Fixed some problems with showing HGL/EGL Plots in the HY12 interface. Some nodes were not shown as part of the plot if they had gutter inlets but no access holes. Also, if you selected mult...<br />
*Merged revision(s) 33039 from devproj/trunk/Dev: Fixed a problem with contours not showing up, caused by SVN check-in 33002 ........ <br />
*Merged revision(s) 33008 from devproj/trunk/Dev: Fixed issue 0007589: WMS crashes when mapping land use shapefile to coverage in Hydrologic Modeling Wizard See bug report for more information. ........ <br />
*Merged revision(s) 33002 from devproj/trunk/Dev: Fixed issue 0007324: WMS crashes when selecting a DEM in the Project Explorer Cleaned up some functions that had potential issues. ........<br />
<br />
==Intermediate Release 10.0.6 &ndash; Aug 6, 2014==<br />
<br />
*Merged revision(s) 32988 from devproj/trunk/Dev: Fix issue 0007432: GSSHA index map not recognized by mapping tables if deleted and recreated Also fixed other related issues and crashes related to deleting index maps and other GSSHA model d...<br />
*Merged revision(s) 32947 from devproj/trunk/Dev: Fixed contour label issues and Bug 0007456: Placing One or More Contour Labels Inside of a Triangle Causes WMS to Crash<br />
*Merged revision(s) 32912 from devproj/trunk/Dev: Fixed bug 0007478: WMS 10.0 crashes when deleting rainfall depth in GSSHA precipitation dialog This was a simple fix, just needed to check on the return value of GetItemData to make sure it w...<br />
*Merged revision(s) 32906 from devproj/trunk/Dev: * Fix problems with mapping multiple shapefile attributes to a single coverage. You can map multiple shapefiles to a single coverage in WMS, but apparently not in SMS or GMS. Why not in SMS...<br />
*Merged revision(s) 32869 from devproj/trunk/Dev: Update version of GSSHA we use with WMS 10.0 ........ <br />
*Merged revision(s) 32863 from devproj/trunk/Dev: Fixed issue 0007469: Problem with TR-55 tabular hydrograph method ........ <br />
*Merged revision(s) 32510 from devproj/trunk/Dev: Fixed a problem with the GSSHA model checker finding incorrect errors. ........ <br />
*Merged revision(s) 32125 from devproj/trunk/Dev: Fix problems with exporting rain gage information to HMS 4.0. The rain gages need to be ALL CAPS in the HMS meteorology file so they are in the same (upper) case as the gages in the HMS gage...<br />
*Merged revision(s) 32016 from devproj/trunk/Dev: Removed unused dialogs and fixed some dialogs with radio buttons so the radio buttons work correctly. ........ <br />
*Ignore files<br />
*Update All FHWA Projects to Use Boost 1.55<br />
*Merged revision(s) 31669 from devproj/trunk/Dev: Fix Filename Issues in HY12: change how file names are managed in the HY12 interface-- -clean up how all the filenames are handled with HY12 to make sure everything is saved to the project di...<br />
*Update Hydraulic Toolbox 4.2 Version number for update<br />
*Merged revision(s) 31577 from devproj/trunk/Dev: Fix "ripraap" spelling errors to "riprap" ........ <br />
*Merged revision(s) 31571-31573 from devproj/trunk/Dev: Add 32-bit gssha.exe to WMS bin directory. ........ Add 64-bit gssha.exe to WMS bin directory. ........ Add 32 and 64-bit gssha.exe to WMS bin directories. ........ <br />
*Updated the HydraulicToolbox/Desktop Reference Guide.pdf based on the latest version from Bart<br />
*Merged revision(s) 31486 from devproj/trunk/Dev: HY12 Redesign: Interface Bug Fixes: Remove Extra Lines in the HY12 Properties Dialog ........ <br />
*Merged revision(s) 31448 from devproj/trunk/Dev: Fixed issue 0007264: WMS crashes when editing GSSHA embankment arc: See bug report for more information. ........<br />
<br />
==Intermediate Release 10.0.5 &ndash; July 17, 2014==<br />
<br />
*Update HY8 7.31 Version Number for WMS 10.0 release update.<br />
<br />
==Intermediate Release 10.0.4 &ndash; June 12 2014==<br />
<br />
*Update HY8 version number so the HY8 build gets updated with the WMS 10.0 beta release.<br />
*Update HY8 so it no longer has AOP analysis included in the interface (the code is still there, we just took out AOP).<br />
*Merged revision(s) 31141 from devproj/trunk/Dev: Implement Inset model and related boundary conditions. ........ <br />
*Merged revision(s) 30939-30940 from devproj/trunk/Dev: Changed the SWMM Sanitary Code so it is a separate module from the normal SWMM module. ........ Reverted revision(s) 30939 from devproj/trunk/Dev/WMS/APP/source/wmspass.cpp: Changed the...<br />
*Merged revision(s) 30820 from WMS/WMS_10.0/trunk: Rename the Hydraulic Toolbox for testing ........ <br />
*Rename the Hydraulic Toolbox for testing<br />
*Updated HY12, HY8, and Hydraulic Toolbox solution filenames.<br />
*Updated the WMS 10.0 Release solution name and version numbers and changed the name of the release executables.<br />
*Branch WMS 10.0 from Dev<br />
*Try to fix errors<br />
*Identify specific header files that are including too much - Most WMS files using shared/mfc/mfcstuff.h. <br />
*Update HY8 version number to update build that's installed with installation.<br />
*Fix problems with HY8 bringing up the wrong dialogs from WMS. The indices associated with the command line arguments were wrong so I updated them.<br />
*0007083: Warning Notification for Licenses Expiring Soon - fix null crash when no license exists.<br />
*Fix problem from GUI tests that caused HMS to not run when writing gridded rainfall data.<br />
*WMS::HY8::AOP Unit Test Fix<br />
*Fixed a spelling error in the GSSHA dialogs.<br />
*WMS::HY8::AOP Made more fixes to AOP, based on results of going through an example<br />
*WMS::HY8::AOP Bug fixes<br />
*WMS::HY8::AOP Bug fixes<br />
*WMS::HY8::AOP Ripped out the Rock/Sediment gradations and put in a generic one. Also updated the culvert 'thalwegs' to include embedment depth and listed the steps. added file I/O and reports for the gradations. Also an embedment check.<br />
*AHGW SourceGrid license, and Boost license.<br />
*Added an attempted fix for a shared code SNAFU that messed up units when reading in previously-saved projection information from the WMS project file.<br />
*Fixed the MODRAT interface so WMS writes the correct output filenames and so MODRAT writes/WMS reads the output files correctly. See bug report 0007166 and SVN check-in 30366 for related changes<br />
*Fixed GUI test problem with WMS not writing out the HMS version number, which apparently is required when running HMS 4.0 or later.<br />
*Upgrade to Boost 1.55 and signals2<br />
*kmz.h missing xmscore::Pt3d prefix.<br />
*Add DLL's to WMS 64-bit version and update DLL and EXE file descriptions in .bat file<br />
*Fixed a bug with WMS crashing when shutting down after pulling the tree window off the mainframe, resizing, and then re-attaching the window.<br />
*Fixed issue 0007129: Problems Scrolling Side to Side in project Explorer (See bug report for more information)<br />
*Attempt to fix issue 0007175: Problem running NSS models in WMS Dev<br />
*Missing forward declaration for display atts (EDispAttLine). Can cause compile errors elsewhere without this.<br />
*Added an error message when delineating basins and no outlets exist.<br />
*Fixed issue 0007162: Delineate Basins Wizard should delineate the watershed - not launch the Hydrologic Modeling Wizard (See bug report for more information)<br />
*Fixed bug 0007166: Error running simulation when changing MODRAT executable file (See bug report for more information)<br />
*Moved SetState to protected and switched all calls to it to SetStatePropogate like in SMS.<br />
*0003072: Setup mesa for 64-bit - Get Mesa from its own 32 or 64-bit folder.<br />
*Fixed issue 0007168: GSSHA Rainfall Time Inconsistency (See bug report for more information)<br />
*Fixed issue 0007176: Problem saving GSSHA Storm Drain coverage (See bug report for more information)<br />
*0007083: Warning Notification for Licenses Expiring Soon - Show days remaining after 5 if both licenses will expire.<br />
*WMS::HY8 Allow the user to select the errors.<br />
*0007083: Warning Notification for Licenses Expiring Soon<br />
*Fixes for project explorer state not matching displayed state when projects are loaded in GMS & WMS.<br />
*WMS::HY8 change version to force a build<br />
*Adjustments to fix bugs discovered in AOP<br />
*Add GSSHA options for outputting point overland depth and water surface elevation information.<br />
*Common GIS module - Make sure all 3 programs read files as defined in the design doc - Hide new GIS. General GM file type. World file and zip file readers/complainers. Fix CanGlobalMapperOpenFile. Move GIS to shared. <br />
* Added static and rating curve lake options to detention basins defined at feature nodes and polygon lakes. * Added a rating curve spreadsheet dialog so users can input and edit rating curves for detention basins/lakes. * Added map and GSS...<br />
*Common GIS module - Make sure all 3 programs read files as defined in the design doc - GMS, SMS, and WMS. Shared GM reader. Only jpg so far.<br />
*Force a rebuild on HY8<br />
*WMS::HY8 Add some commandline arguments to allow HY-8 to disable crossing input<br />
*WMS::HY8 Add some commandline arguments to allow HY-8 to disable crossing input<br />
*Remove test code for calls to ComputeClippedPoints function.<br />
*Committed changes to demio.cpp for debugging release 32 version.<br />
*Separated out two dialog files from flineatt.cpp (I need to modify them and the code's all messed up) and modified seGetSelectedFeaturePoints to use a vector instead of malloc'ing memory. Cleaned up some code. Fixed a problem with feature...<br />
*Added more GIS mapping for the dynamic model interface.<br />
*BUGFIX: Fix to state functionality in shapefile ETreeItems for WMS<br />
*Fixed problem with GSSHA crashing when exporting stochastic data files.<br />
*Fix for WMS ETreeItem state based on messages from Chris and comparison with WMS 9.1<br />
*Moving tree_enum and troot_enum into xms namespace for SMS and WMS.<br />
*Allow HY-8 to run with an exceptionally tall roadway in commandline. Still need to allow it to be entered, get past the data checks, and modify the interface for it.<br />
*Added arc-specific OVERBANK and BACKWATER channel card options to GSSHA file I/O and user interface. Check to see if these options are set on any of the arcs when entering the project channel data dialog and when exporting the GSSHA projec...<br />
*Fixing WMS Checkboxes I think.<br />
* Clean up lots of code (move classes out of globals.h) * Fix a problem with the stream smoothing dialog that does not display a plot if one of the groundwater datasets is not defined.<br />
*Fix for BUG# 0007125<br />
*Update for fix to bug 0006856: WMS hangs when reading project<br />
*Unification of tree icons across products.<br />
*Update the EPA SWMM executable file directory to the default installation folder for the new version.<br />
*Added code to read/write the Depth Varying Overland Flow Roughness mapping tables (GSSHA), ROUGH_EXP to/from the GSSHA .cmt file.<br />
*Common GIS module - Make sure all 3 programs read files as defined in the design doc - GMS has optional new GIS, image reader for FILE_JPG to FILE_KMZ_VECTOR, default GM reader, merge GMS into shared file types, adapt unit tests to merged t...<br />
*WMS::HY8::AOP Updates for bugs that were noticed in a sprint meeting; Also update of the version number to force a build.<br />
*Fixed root display oder for WMS.<br />
*Cleaned up some more GSSHA code.<br />
*Moved ETreeItem state functionality to be all new state functionality from SMS. All statements within #ifndef statements for the new state functionality should either be commented out, deleted, or migrated to the new state functionality. C...<br />
*Fix Errors in WMS build<br />
*Cleaned up code in casc2d.h (removed headers and moved stuff to .cpp files) and made GSSHA parent/child model dialog resizable.<br />
*WMS::HY8::AOP Fix an bigger issue with Units, also update the version number and force a new build<br />
*WMS::HydraulicToolbox Update version number to force a new build/install<br />
*Update NSS version number and database.<br />
*Common GIS module - Make sure all 3 programs read files as defined in the design doc - Change WMS to not use new GIS, but use new common enumeration.<br />
*Added GSSHA model check to determine if cells containing rating curve BC's have adjacent cells marked as receiving cells.<br />
*Fixed a problem with too many options showing up in the Compute Topaz step of the Hydrologic Modeling Wizard. Needed to reset the combo box before it's set up.<br />
*WMS::HY8::SRH Add new commandline arguments for HY8, to run within SMS. Allow SMS to call for a crossing just knowing the GUID, not the index, if it doesn't exist, create one.<br />
<br />
=WMS 9.1 Bugfixes=<br />
==Intermediate Release 9.1.12 &ndash; May 6, 2014==<br />
#Fixed the WMS 2D grid cell traversal algorithms to handle line segments that begin and end outside the bounds of the 2D grid or the active cells on the 2D grid.<br />
#Fixed the HY8 Crossing Discharge Data dialog to get the hydrograph whether it's defined at the outlet or at the basin associated with the outlet.<br />
#Fixed WMS so circular stream arcs do not cause WMS to crash when selecting File | New or when shutting down.<br />
#Fixed a problem where Mapping Shapefile causes crash<br />
#Fixed a Crash when reading in a map file<br />
#Fixed a bug with reading tailwater curve ratings of a different length<br />
#Fixed some reading issues<br />
#Fixed an issue to Update Culvert Info if reading an older file<br />
<br />
==Intermediate Release 9.1.10 &ndash; November 22, 2013==<br />
WMS 9.1.10 has been posted on Aquaveo's web site. The best place to obtain the update is from the download link on Aquaveo's web site at [http://www.aquaveo.com/downloads?tab=3#TabbedPanels http://www.aquaveo.com/downloads]. The following revisions have been made to this version:<br />
<br />
* 26787; Author: cdickson; Date: Thursday, November 21, 2013 9:09:05 AM; Message: Web form option for getting license from the license manager - WMS9.1<br />
* 26719; Author: csmemoe; Date: Monday, November 18, 2013 2:47:37 PM; Message: Removed failing test assert that isn't necessary. Only needs to test vertical units. (See SVN revision 24750)<br />
* 26713; Author: csmemoe; Date: Monday, November 18, 2013 12:06:36 PM; Message: Merged revision(s) 26712 from devproj/trunk/Dev: Changed WMS so it reads and saves whether each coverage is visible. <br />
* 26557; Author: csmemoe; Date: Monday, November 11, 2013 9:43:46 AM; Message: Merged revision(s) 26550 from devproj/trunk/Dev/WMS/APP/source/display/mapdraw.cpp: Fixed problems with framing image and getting max/min world coordinates when a rain gage coverage exists. Also cleaned up some of the setmap code to specify const parameters a little better. <br />
* 26542; Author: csmemoe; Date: Friday, November 08, 2013 11:27:03 AM; Message: Merged revision(s) 26541 from devproj/trunk/Dev: Fixed some issues with the TR-55 computation dialog caused by my check-in yesterday--the incorrect cells were getting set to read-only. Also the Fp value was not showing up in the dialog. Cleaned up some code. <br />
* 26535; Author: csmemoe; Date: Thursday, November 07, 2013 5:46:46 PM; Message: Merged revision(s) 26534 from devproj/trunk/Dev: Try to fix a problem with the TR55 window crashing in the dev release version when it first comes up. <br />
* Revision: 26508; Author: csmemoe; Date: Wednesday, November 06, 2013 5:34:24 PM; Message: Merged revision(s) 26505 from devproj/trunk/Dev: Fixed text attribute strings in compute GIS attributes dialog. <br />
* Revision: 26363; Author: csmemoe; Date: Wednesday, October 30, 2013 6:10:51 PM; Message: Merged revision(s) 26361 from devproj/trunk/Dev: Fixed problems importing HEC-RAS geometry files-did not read Manning's roughness correctly from these files. Also cleaned up lots of the shared/rivmod code. <br />
* 26237; Author: csmemoe; Date: Friday, October 25, 2013 2:37:18 PM; Message: Update WMS Release Version number<br />
* Revision: 26226; Author: csmemoe; Date: Friday, October 25, 2013 10:27:42 AM; Message: Fixed issue 0006656: Helpstrings for "Compute Time Area Curve" button and "Compute Parameters &ndash; Basin Data" button are switched<br />
* 26216; Author: csmemoe; Date: Thursday, October 24, 2013 5:57:48 PM; Message: Merged revision(s) 26137 from devproj/trunk/Dev: WMS::HY-8 Fix for help PDF Help (replaces temporary check) <br />
* Revision: 26215; Author: csmemoe; Date: Thursday, October 24, 2013 5:55:15 PM; Message: Merged revision(s) 26205 from devproj/trunk/Dev: Fixed problems with plot menus not coming up in HY12 plot dialogs and in detention basin storage capacity curve dialog. <br />
* 26019; Author: csmemoe; Date: Tuesday, October 15, 2013 1:48:30 PM; Message: Merged revision(s) 26017 from devproj/trunk/Dev: Fixed issue 0002019: Problem reading HEC-RAS solution for WMS Dev and HEC-RAS 4.1, fixed a problem running HEC-RAS from WMS, changed the stochastic modeling code so it does not require user interaction, and fixed stochastic modeling code so HEC-1 runs do not depend on the length of the path name to the HEC-1 input file. Also fixed a crash when running floodplain delineation after a stochastic run and a crash when exiting WMS. <br />
* 25976; Author: csmemoe; Date: Friday, October 11, 2013 1:47:00 PM; Message: Merged revision(s) 25975 from devproj/trunk/Dev: Fix problem with joining SSURGO data when you have "spatial" somewhere in the path of the shapefile other than under the base directory containing the shapefile data. <br />
* 25968; Author: csmemoe; Date: Friday, October 11, 2013 9:57:08 AM; Message: Merged revision(s) 25946, 25967 from devproj/trunk/external_libs: <br />
*#Add user_online_sources.xml file to specify online sources that are not available in Global Mapper by default (Added FEMA flood map web services).<br />
*#Added FEMA flood maps to list of possible web services.<br />
*#Merged revision(s) 25965 from devproj/trunk/Dev:<br />
*#Added FEMA flood maps to list of possible web services.<br />
* 25940; Author: csmemoe; Date: Thursday, October 10, 2013 9:55:26 AM; Message: Merged revision(s) 25935 from devproj/trunk/Dev: Added support for Web Feature Services (WFS) to global mapper web services. Handle reading vector data from OGC WFS services. <br />
* 25911; Author: csmemoe; Date: Tuesday, October 08, 2013 4:04:38 PM; Message: Merged revision(s) 25909 from devproj/trunk/Dev: Fixed crashes when exporting riprap profiles to a report. <br />
* 25892; Author: csmemoe; Date: Tuesday, October 08, 2013 9:50:54 AM; Merged revision(s) 25876 from devproj/trunk/Dev/WMS/APP/source/display/displayopt.cpp: Added option to display cross section ID's and display options. <br />
* 25803; Author: csmemoe; Date: Wednesday, October 02, 2013 9:25:47 PM; Message: Fixed an error caused by a merge<br />
* 25798; Author: csmemoe; Date: Wednesday, October 02, 2013 5:45:55 PM; Message: Merged revision(s) 25797 from devproj/trunk/Dev/WMS/APP/source/Hydrology/GSSHA/casc2d.cpp: Fix a problem with reading solution files when not running a calibration and maintain code that correctly reads calibration solution files. <br />
* 25657; Author: ejones; Date: Thursday, September 26, 2013 11:12:38 AM; Message: Merged revision(s) 25656 from devproj/trunk/Dev/WMS/APP/bin/modrat: Fixed a bug in Modrat with generating a hydraulic parameter table used for channel routing <br />
* 25518; Author: csmemoe; Date: Wednesday, September 18, 2013 3:32:23 PM; Message: Merged revision(s) 25517 from devproj/trunk/Dev: Cleaned up some code in ocmodels.cpp-determining what Tree Mapping does. <br />
* 25487; Author: csmemoe; Date: Tuesday, September 17, 2013 4:20:31 PM; Message: Fixed a problem with images that were not displayed being checked in the project explorer window.<br />
* 25240; Author: csmemoe; Date: Friday, September 06, 2013 9:25:10 AM; Message: Merged revision(s) 25239 from devproj/trunk/Dev: Fixed issue 0006424: WMS not saving user defined DEM names <br />
* 25226; Author: csmemoe; Date: Thursday, September 05, 2013 3:04:31 PM; Message: Merged revision(s) 25223 from devproj/trunk/Dev/WMS/APP/source/Hydrology/GSSHA/casc2d.h: Fixed issue 0006481: Error Opening Summary File in Gssha Calibration (tut 57) and cleaned up lots of code related to solutions, etc. <br />
* 25207; Author: csmemoe; Date: Wednesday, September 04, 2013 4:54:01 PM; Message: Merged revision(s) 25206 from devproj/trunk/Dev: Fixed issue 0006287: Difference between 32 and 64 bit version in tut63. Also added capability to print out link/node names in detailed report file for selected links nodes. <br />
* 25139; Author: csmemoe; Date: Tuesday, September 03, 2013 8:21:44 AM; Message: Updated the HY-8 7.30 version number.<br />
* 25012; Author: csmemoe; Date: Monday, August 26, 2013 10:48:44 AM; Message: Update WMS 9.1.x version number.<br />
* 25011; Author: csmemoe; Date: Monday, August 26, 2013 10:47:16 AM; Message: Update hydraulic toolbox 4.0.x version number.<br />
* 24964; Author: csmemoe; Date: Friday, August 23, 2013 1:44:47 PM; Message: Merged revision(s) 24951 from devproj/trunk/Dev/WMS/APP/source/Feature/fcoverage.cpp: Added support to automatically map the global land use and soil shapefile data to map module feature object data. <br />
* 24933; Author: csmemoe; Date: Thursday, August 22, 2013 6:35:07 PM; Message: Merged revision(s) 24932 from devproj/trunk/Dev: Fixed problem with virtual earth map locater tool showing up in the ocean if you have the Hydrologic modeling wizard up. <br />
* 24925; Author: csmemoe; Date: Thursday, August 22, 2013 4:28:55 PM; Message: Merged revision(s) 24924 from devproj/trunk/Dev: Fixed WMS so it sets the main channel slope if the string "main channel slope" or other possible names are found in the NSS parameter description. ........<br />
* 24912; Author: csmemoe; Date: Thursday, August 22, 2013 2:58:36 PM; Message: Merged revision(s) 24908 from devproj/trunk/Dev: Added USA Topo maps to the main online data dialogs so you don't have to click on the Advanced button. <br />
* 24911; Author: csmemoe; Date: Thursday, August 22, 2013 2:56:01 PM; Message: Merged revision(s) 23041 from devproj/trunk/Dev: Fixed problem with web services that did not allow downloading data from http://xmswiki.com/xms/WebServiceCatalog <br />
* 24886; Author: ejones; Date: Thursday, August 22, 2013 11:50:04 AM ;Message: Fixes for Modrat Cross Section WorkMerged revision(s) 24871-24883 from devproj/trunk/Dev/WMS:<br />
*# Rectangular cases are now matching closely!<br />
*# Fixes for Modrat Cross Section Work<br />
*# Fixes for Modrat Cross Section Work<br />
*# Fixes for Modrat Cross Section Work<br />
* 24862; Author: csmemoe; Date: Wednesday, August 21, 2013 5:21:42 PM; Message: Fixed WMS 9.1 to be able to read online images with colons and other unacceptable characters in the filename.<br />
* 24859; Author: csmemoe; Date: Wednesday, August 21, 2013 5:08:10 PM; Message: Handle online images with unauthorized characters in the filename (\/:*?"<>|) and handled exceptions in online images without crashing.<br />
* 24848; Author: csmemoe; Date: Wednesday, August 21, 2013 2:35:31 PM; Message: Fixed a crash when getting data from map or when using the Get Data tool if you select an option from the "Advanced" button in the Online Data dialog. Also fixed a problem with characters that cannot be used in filenames when using this button.<br />
* 24747; Author: csmemoe; Date: Monday, August 19, 2013 3:00:59 PM; Message: Merged revision(s) 24743 from devproj/trunk/Dev: Fixed problem that caused vertical units to change when selecting the Virtual Earth map locater tool. See issue 0006240: After setting the current projection vertical units to feet from meters (Tutorial 62)<br />
* 24683; Author: csmemoe; Date: Thursday, August 15, 2013 5:51:31 PM; Message: Merged revision(s) 24682 from devproj/trunk/Dev: Updated QuickPDF Unlock Code to permanent license code (until we upgrade global mapper and there's a new version of QuickPDF included with GM).<br />
<br />
==Intermediate Release 9.1.7 &ndash; August 13, 2013==<br />
WMS 9.1.7 has been posted on Aquaveo's web site. The best place to obtain the update is from the download link on Aquaveo's web site at [http://www.aquaveo.com/downloads?tab=3#TabbedPanels http://www.aquaveo.com/downloads]. The following known bugs have been fixed in this version:<br />
<br />
Id-Date Submitted-Updated-Summary<br />
* 6464-7/31/2013-8/7/2013-Hydrograph timing messed up when exporting HEC-HMS hydrographs with a SWMM input file<br />
* 6456-7/26/2013-8/7/2013-Problem reading NRCS data from soil files<br />
* 6471-8/2/2013-8/5/2013-Crash when saving TIN to grid format<br />
* 6463-7/31/2013-8/5/2013-wmsdss.exe crashes when reading HEC-HMS solution<br />
<br />
==Intermediate Release 9.1.6 &ndash; July 18, 2013==<br />
WMS 9.1.6 has been posted on Aquaveo's web site. The best place to obtain the update is from the download link on Aquaveo's web site at [http://www.aquaveo.com/downloads?tab=3#TabbedPanels http://www.aquaveo.com/downloads]. The following known bugs have been fixed in this version:<br />
<br />
Id-Date Submitted-Updated-Summary<br />
<br />
* 5001-4/19/2012-6/25/2013-The HSPF dialog doesn't close after you define the parameters for Snow and Water.<br />
* 6219-5/9/2013-6/18/2013-"In Tutorial 10, HEC-1 is unable to open input file."<br />
* 6129-4/11/2013-6/18/2013-Problem running HEC1 on computers at NHI training course<br />
* 6165-4/24/2013-6/18/2013-HEC-1 File Name and Path limitations (from Scott Hogan @ FHWA)<br />
* 6068-3/21/2013-6/18/2013-HEC-1 Fails to load input files with a filepath >80 characters<br />
* 6314-6/6/2013-6/14/2013-Bug computing storage from DEM when vertical units are in meters<br />
* 6053-3/18/2013-6/13/2013-Two Time Computation Saving Permissibility<br />
* 6204-5/6/2013-6/13/2013-Intermediate tests failing<br />
* 6286-5/28/2013-6/13/2013-Default Selection in 64-bit version HEC-1 Unit Hydrograph Methods window Bug (Watershed Modeling - MaricopaNSS)<br />
* 6250-5/17/2013-6/12/2013-Lines extend when you select the Hydrological modeling module (Tut 15)<br />
* 6289-5/28/2013-6/11/2013-Crash when mapping shapefile to features<br />
* 6239-5/16/2013-6/11/2013-The Peak & Volume Boxes are read only when they should be editable (Automated Calibration Tutorial 58)<br />
* 6057-3/19/2013-5/7/2013-Hydrolic Modeling Dialog Crashes on NULL Values<br />
* 6130-4/11/2013-5/3/2013-Rational Method Interface tutorial has problems<br />
* 6201-5/3/2013-5/3/2013-WMS Crashes in Tutorial 4 Section 6.1<br />
* 6184-4/29/2013-5/3/2013-Problem renumbering storm/tile drains in WMS 9.1<br />
* 6178-4/29/2013-5/3/2013-Documentation missing step (W_20)<br />
* 6193-5/1/2013-5/2/2013-Problems with the units in tutorial 36<br />
* 6194-5/2/2013-5/2/2013-"Message box pops up that says ""Error: No links found"" after saving GSSHA project file (Tutorial 46)"<br />
* 6183-4/29/2013-5/1/2013-Problem assigning groundwater BC to streams in GSSHA model<br />
* 6182-4/29/2013-5/1/2013-"Problems reading, writing, and editing files for the Multi Layer Green and Ampt (MLGA) method in WMS 9.1"<br />
* 6166-4/24/2013-5/1/2013-Problem Trimming DEM<br />
* 6176-4/29/2013-4/30/2013-WMS crashes on changing Point Display step for DEM<br />
* 6117-4/9/2013-4/18/2013-Cryptic Error code message when online image servers are down<br />
* 6016-3/7/2013-3/13/2013-"Selecting ""Show Dates"" in User Hyetograph dialog changes time interval in dss files"<br />
* 6032-3/12/2013-3/12/2013-Problem reading ArcInfo and GRASS ascii flow directions and accumulations<br />
* 6027-3/8/2013-3/11/2013-Deleting a point takes a very long time<br />
* 6010-3/7/2013-3/8/2013-WMS crashes you try to view scatter dataset properties<br />
* 6011-3/7/2013-3/8/2013-Opening *.hdr file created in ArcGIS crashes WMS<br />
* 6012-3/7/2013-3/8/2013-WMS crashes when click OK on XY Series Editor when defining a hydraulic structure<br />
* 6000-3/6/2013-3/7/2013-"WMS reverts back to same ""All"" row when you change it in HMS properties dialog"<br />
* 6013-3/7/2013-3/7/2013-CE-QUAL top layer widths less than the widths of the Segments<br />
* 4496-12/15/2011-3/7/2013-"Unable to read a CAD file, probably Shared Code issue"<br />
* 4530-1/3/2012-3/7/2013-Problem getting online images when using remote desktop<br />
* 4531-1/3/2012-3/7/2013-Problem with registration of a static image created from an online image<br />
* 4538-1/4/2012-3/7/2013-The 'Setup All Precip Events' button does not work<br />
* 4580-1/12/2012-3/7/2013-WMS not responding<br />
* 4649-1/31/2012-3/7/2013-DEV - WMS freezes when converting online image to GeoTIFF<br />
* 4683-2/7/2012-3/7/2013-Oblique view zooming issue with GSSHA solution<br />
* 4690-2/8/2012-3/7/2013-Importing CMT file in WMS 8.4 does not import all data<br />
* 4694-2/9/2012-3/6/2013-Can't import more than 1 GeoTIFF DEM at a time<br />
* 4703-2/10/2012-3/6/2013-"Update ""Images"" menu in the Map Data menu items"<br />
* 4757-2/22/2012-3/6/2013-WMS fails to save a CAD file for hydrologic modeling tree data<br />
* 4761-2/23/2012-3/6/2013-Problem reading TIN datasets after computing using the data calculator<br />
* 4552-1/6/2012-3/6/2013-GSSHA makes computer run out of memory when running a constituent transport simulation<br />
* 5984-3/4/2013-3/6/2013-Problem with Getting Online Maps when only CAD data is defined<br />
* 5982-3/4/2013-3/5/2013-DXF and DWG files display problem: Thick lines<br />
* 5082-5/7/2012-3/5/2013-Channel Calculator issue<br />
* 5092-5/8/2012-3/5/2013-msvcr71.dll error when running wmstopaz.exe<br />
* 5518-9/26/2012-3/5/2013-Save project crash with GeoPDF with cropped collar<br />
* 5552-10/5/2012-3/5/2013-WMS is unable to write to the worldfile unless images are stored in the project directory<br />
* 5572-10/11/2012-3/4/2013-Check long term simulation tutorial and calibration tutorial to see if everything is working fine with WMS 9.0<br />
* 5601-10/18/2012-3/1/2013-Problem displaying flow paths and moving basin labels<br />
* 5495-9/18/2012-3/1/2013-Unable to download many of the soil and land use options in WMS<br />
* 5605-10/18/2012-3/1/2013-WMS is not creating frames for the .AVI animations for GSSHA solutions<br />
* 5713-11/28/2012-2/28/2013-"When adding new polygon, all previous colors are reset"<br />
* 5826-1/15/2013-2/28/2013-WMS doesn't create Routing Hotstart File when option is checked on<br />
* 1140-7/10/2009-2/27/2013-Join SSURGO data doesn't work when adding a custom attribute before joining<br />
* 5062-5/3/2012-2/27/2013-freeze when changing all arcs in a GSSHA coverage to a different type<br />
* 3952-8/10/2011-2/26/2013-Selected crossing/crossing name not saved<br />
* 4189-9/29/2011-2/25/2013-Support .las and .dtm file formats.<br />
* 5902-2/6/2013-2/25/2013-Problem reading solutions as 2D scattered data from HEC-RAS GIS files<br />
<br />
==[[WMS:What's new in WMS version 9.1|Release 9.1]]/Intermediate Release 9.1.4 &ndash; February 22, 2013==<br />
WMS 9.1.4 has been posted on Aquaveo's web site. The best place to obtain the update is from the download link on Aquaveo's web site at [http://www.aquaveo.com/downloads?tab=3#TabbedPanels http://www.aquaveo.com/downloads]. The following known bugs have been fixed in this version:<br />
<br />
Bug ID Date Submitted&ndash;Date Updated&mdash;Summary<br />
<br />
* 5867 1/30/2013&ndash;2/22/2013&mdash;Crash when running the OC Rational method<br />
* 5866 1/30/2013&ndash;2/22/2013&mdash;HEC-HMS files exported from WMS freeze up after selecting sub basins<br />
* 4117 9/12/2011&ndash;2/21/2013&mdash;Error when loading GSSHA solution in Contaminants tutorial<br />
* 5945 2/19/2013&ndash;2/19/2013&mdash;The '''Edit...''' button in the Culvert and Site Data section in the HY8 Modeling Wizard is missing<br />
* 5944 2/19/2013&ndash;2/19/2013&mdash;WMS crashes when navigating through the HY8 modeling wizard<br />
* 5846 1/22/2013&ndash;2/19/2013&mdash;Print out error information when running the OC rational method<br />
* 5868 1/30/2013&ndash;2/19/2013&mdash;The Crest Elevation is not saved in the ''Crossing Data'' dialog<br />
* 5874 1/31/2013&ndash;2/19/2013&mdash;Save curve number and other report files to Temp directory instead of current directory<br />
* 5888 2/1/2013&ndash;2/19/2013&mdash;WMS 9.1 reports a missing resource when renumbering a MODRAT tree<br />
* 5941 2/18/2013&ndash;2/19/2013&mdash;Incremental Data Checkbox does not show up in Figure 4-3 of GSSHA Nexrad tutorial<br />
* 5856 1/24/2013&ndash;2/15/2013&mdash;Add capability to compute layer widths less than 5 meters in the CE-QUAL-W2 Layer Editor<br />
* 5901 2/6/2013&ndash;2/14/2013&mdash;Add the .sdf extension to the list of filters that can be read when importing an HEC-RAS GIS file<br />
* 5918 2/7/2013&ndash;2/13/2013&mdash;WMS crashes when trying to acces HY-8<br />
* 5930 2/13/2013&ndash;2/13/2013&mdash;Issue with Drainage Coverage '''Tree | Find''' tool<br />
* 5903 2/6/2013&ndash;2/13/2013&mdash;Problem reading floodplain boundary into WMS<br />
* 5904 2/6/2013&ndash;2/12/2013&mdash;Problem extracting cross sections if you have a cross section point that coincides with a TIN vertex<br />
* 5923 2/11/2013&ndash;2/11/2013&mdash;Problem with extra pipes associated with a superlink arc when building a GSSHA storm/tile drain model<br />
* 5905 2/6/2013&ndash;2/8/2013&mdash;Check adding storm/tile drain pipes without connecting them directly to a channel at the downstream end<br />
* 5897 2/5/2013&ndash;2/8/2013&mdash;WMS crashes when assigning reach routing for OC Rational model<br />
* 4477 12/12/2011&ndash;2/7/2013&mdash;Online Map issues<br />
* 4437 12/6/2011&ndash;2/7/2013&mdash;Add options to download online vector data through Global Mapper<br />
* 4435 12/6/2011&ndash;2/7/2013&mdash;Fix problem with online image taking a long time to load after zooming or panning<br />
* 4410 11/30/2011&ndash;2/7/2013&mdash;Outlet issues<br />
* 4337 11/9/2011&ndash;2/7/2013&mdash;More than one plot is selected to be generetaded when using the channel calculator<br />
* 5909 2/6/2013&ndash;2/6/2013&mdash;Crash when reading LandXML file<br />
* 4312 11/2/2011&ndash;2/5/2013&mdash;Right clicking to access ''Display Options'' should select the correct module first<br />
* 4281 10/25/2011&ndash;2/5/2013&mdash;Crash in GSSHA Land use change #2 tutorial<br />
* 4246 10/17/2011&ndash;2/5/2013&mdash;Problems in the HY8 modeling wizard that should be addressed (from Jim)<br />
* 4207 10/6/2011&ndash;2/4/2013&mdash;Bug with approximate total number of points in ''Import DEM'' dialog<br />
* 4202 10/5/2011&ndash;2/4/2013&mdash;Tin Triangles not Displaying when option to display triangles is checked<br />
* 4200 10/5/2011&ndash;2/4/2013&mdash;Crop Collar not working<br />
* 4181 9/29/2011&ndash;2/4/2013&mdash;Recompute All Stations should also delete the river hydraulic schematic<br />
* 4138 9/15/2011&ndash;2/1/2013&mdash;WMS using Outlet IDs instead of Outlet Names in ''SWMM'' dialog<br />
* 5749 12/7/2012&ndash;2/1/2013&mdash;0005734: Share the app name and registry path stuff<br />
* 5745 12/6/2012&ndash;2/1/2013&mdash;Problem computing water surface elevations using the channel calculator<br />
* 4077 9/2/2011&ndash;1/31/2013&mdash;Cell elevation text does not match setting<br />
* 4021 8/22/2011&ndash;1/31/2013&mdash;Contour values do not exactly match DEM values<br />
* 4011 8/19/2011&ndash;1/31/2013&mdash;Problems with node boundary contitions in GSSHA<br />
* 3984 8/15/2011&ndash;1/31/2013&mdash;DEM Display Issues<br />
* 3972 8/12/2011&ndash;1/31/2013&mdash;Memory issue continues after project is closed<br />
* 3969 8/12/2011&ndash;1/31/2013&mdash;''GSSHA'' Menu not displayed<br />
* 3968 8/12/2011&ndash;1/31/2013&mdash;Not all DEM points display<br />
* 3967 8/12/2011&ndash;1/31/2013&mdash;Contours displaying wrong<br />
* 3962 8/11/2011&ndash;1/31/2013&mdash;Pipe Flow scatter data not working properly<br />
* 3931 8/9/2011&ndash;1/31/2013&mdash;DXF/DWG files not exporting<br />
* 3890 8/2/2011&ndash;1/31/2013&mdash;Linked outlets and nodes not saved in WMS<br />
* 3888 8/2/2011&ndash;1/31/2013&mdash;WMS Duplicates SWMM hydraulic schematic<br />
* 3887 8/2/2011&ndash;1/31/2013&mdash;Cannot delete Hydraulic Schematic data<br />
* 3869 7/28/2011&ndash;1/31/2013&mdash;Adding an embankment to a DEM does not seem to impact flow directions<br />
* 3833 7/20/2011&ndash;1/31/2013&mdash;Cannot enter reach and reservoir routing at same node in HEC-HMS<br />
* 3822 7/19/2011&ndash;1/31/2013&mdash;Problem displaying stream height cylinders in oblique view (WMS)<br />
* 3817 7/15/2011&ndash;1/31/2013&mdash;Redistributed stream display problem<br />
* 3816 7/15/2011&ndash;1/31/2013&mdash;Big letters displayed on button instead of symbol<br />
* 3815 7/15/2011&ndash;1/31/2013&mdash;Link numbers do not stay aligned with links<br />
* 3814 7/15/2011&ndash;1/31/2013&mdash;Vertices appear as nodes<br />
* 3806 7/14/2011&ndash;1/31/2013&mdash;2D scatter set will not duplicate<br />
* 3801 7/13/2011&ndash;1/30/2013&mdash;HY12 Tutorial Issues<br />
* 3673 6/15/2011&ndash;1/30/2013&mdash;WMS writing wrong rainfall card for EPA SWMM tutorial<br />
* 3605 6/1/2011&ndash;1/30/2013&mdash;gssha crashes before it finishes running when using the green and ampt infiltration option<br />
* 3600 6/1/2011&ndash;1/30/2013&mdash;Shared tests failing in WMS but passing in SMS.<br />
* 5834 1/17/2013&ndash;1/30/2013&mdash;Flows not being computed for MODRAT model<br />
* 3538 5/18/2011&ndash;1/29/2013&mdash;Limiting Number of Cross sections in Simplified Dam Break Model<br />
* 3493 5/9/2011&ndash;1/29/2013&mdash;Cannot register MPICH2 without a password<br />
* 3228 3/10/2011&ndash;1/29/2013&mdash;Compile error when running the shared build<br />
* 3100 2/10/2011&ndash;1/29/2013&mdash;contours not updating when making large change in specified interval<br />
* 2905 12/22/2010&ndash;1/29/2013&mdash;Multiple Tc arcs generated<br />
* 2615 9/29/2010&ndash;1/29/2013&mdash;MODRAT burned simulation not incrementing soil number<br />
* 5782 12/26/2012&ndash;1/29/2013&mdash;Add Custom1 copy protection option to WMS 9.1 and Dev<br />
* 2594 9/21/2010&ndash;1/25/2013&mdash;Digital dams, 2D grid flow vectors, and elevations not updating when you adjust 2D grid elevations<br />
* 2578 9/14/2010&ndash;1/25/2013&mdash;WMS crashes when converting DEM to TIN after editing TOPAZ generated streams<br />
* 2577 9/14/2010&ndash;1/25/2013&mdash;WMS crashes when reversing directions of a stream network<br />
* 2566 9/9/2010&ndash;1/25/2013&mdash;The ''Cross Section Attributes'' dialog gives bogus help strings<br />
* 2558 9/9/2010&ndash;1/25/2013&mdash;CAD file (.dwg) saved out from TIN tutorial does not open in AutoCAD 2008<br />
* 2555 9/9/2010&ndash;1/25/2013&mdash;Feature Request for georeferenced PDFs<br />
* 2553 9/8/2010&ndash;1/25/2013&mdash;WMS crashes when inserting breaklines<br />
* 2547 9/7/2010&ndash;1/25/2013&mdash;WMS displays an image in previous view, even when previous view is oblique<br />
* 2426 7/21/2010&ndash;1/25/2013&mdash;Printing in WMS 8.3 not as clear as 8.0<br />
* 2259 5/26/2010&ndash;1/25/2013&mdash;Error Selecting Polygons<br />
* 2254 5/26/2010&ndash;1/25/2013&mdash;wms 8.3 BUG - opening jpeg when language is korean<br />
* 2243 5/24/2010&ndash;1/25/2013&mdash;convert dem to filtered TIN crash<br />
* 2131 4/23/2010&ndash;1/25/2013&mdash;Error building pyramids<br />
* 2238 5/20/2010&ndash;1/25/2013&mdash;Problem swapping edges or inserting breaklines on TINs<br />
* 2232 5/19/2010&ndash;1/25/2013&mdash;In MODRAT when you input a hydrograph it only uses the first 1500 minutes of the hydrograph.<br />
* 2180 5/4/2010&ndash;1/25/2013&mdash;DEM contours to feature objects crash in WMS 8.3<br />
* 2219 5/13/2010&ndash;1/24/2013&mdash;Crash when closing WMS after reading stochastic GSSHA solution<br />
* 2124 4/22/2010&ndash;1/24/2013&mdash;Issue reading an image file<br />
* 2081 4/14/2010&ndash;1/24/2013&mdash;WMS often exports duplicate points in HEC-RAS cross-sections when using bank arcs<br />
* 2053 4/7/2010&ndash;1/24/2013&mdash;After running the SMPDBK model some of the output data is inconsistent.<br />
* 2049 4/6/2010&ndash;1/24/2013&mdash;Hydrologic Modeling Tree display<br />
* 2018 3/29/2010&ndash;1/24/2013&mdash;Terraserver (MSRMaps) issue<br />
* 2017 3/29/2010&ndash;1/24/2013&mdash;Cropping collar problem with TIFFs in WMS 8.3<br />
* 2016 3/29/2010&ndash;1/24/2013&mdash;Problems reading JPEG and TIFF Images in WMS 8.3<br />
* 2015 3/29/2010&ndash;1/24/2013&mdash;area calculation of basins<br />
* 1987 3/15/2010&ndash;1/24/2013&mdash;Closed bracket in WMS title bar moves one space while panning in WMS<br />
* 1985 3/12/2010&ndash;1/24/2013&mdash;HMS Interface does not include kinematic wave reach routing for rectanglular or triangular channels<br />
* 1943 3/3/2010&ndash;1/24/2013&mdash;SWMM link and node information not saved<br />
* 1859 2/3/2010&ndash;1/24/2013&mdash;WMS 8.2 not able to save the 3 DEMs<br />
* 1823 1/25/2010&ndash;1/24/2013&mdash;Unable to rename Cross section reach name<br />
* 1779 1/15/2010&ndash;1/24/2013&mdash;Crop &ndash; Uncrop Collar not working on jpeg<br />
* 1751 1/5/2010&ndash;1/24/2013&mdash;''Delineate Basins Wizard'' shifts the TOPAZ stream network<br />
* 1743 1/4/2010&ndash;1/24/2013&mdash;NSS not showing correct regions for Utah<br />
* 1742 1/4/2010&ndash;1/24/2013&mdash;HEC-1 will not run while an image is loaded<br />
* 1673 12/3/2009&ndash;1/24/2013&mdash;The SetItemData function changed from taking a DWORD to DWORD_PTR. 64-bit issue<br />
* 1249 7/31/2009&ndash;1/23/2013&mdash;Importing multiple USGS DTED DEMs of varying resolutions creates problems<br />
* 1239 7/30/2009&ndash;1/23/2013&mdash;NSS reports 0% error for all simulations<br />
* 1238 7/30/2009&ndash;1/23/2013&mdash;Change tutorial files installation path to \My Documents instead of \Program Files<br />
* 1232 7/29/2009&ndash;1/23/2013&mdash;GSSHA wiki, Tutorial 3 Fixing Digital Dams, Display Options Crash<br />
* 1214 7/23/2009&ndash;1/23/2013&mdash;The shapefile "basins.shp" does not display properly in the Chapter 2, Maricopa County tutorial.<br />
* 1171 7/15/2009&ndash;1/23/2013&mdash;Problem writing a KMZ animation file from WMS 8.2<br />
* 1151 7/13/2009&ndash;1/23/2013&mdash;The run1.wpr file located on 'files' is more complete than the Volume 3, Chapter 4, Stochasic Modeling tutorials calls for.<br />
* 1142 7/10/2009&ndash;1/23/2013&mdash;Need better way of assigning HYDGRP parameters when joining SSURGO data<br />
* 1089 6/29/2009&ndash;1/23/2013&mdash;Process combined index map using land use and soil maps instead of coverages<br />
* 1029 6/11/2009&ndash;1/23/2013&mdash;Deleting arcs takes a long time (because of UpdateVertToArcMap in feConvertVertexToNode)<br />
* 982 5/29/2009&ndash;1/23/2013&mdash;NFF Error in 8.0 and previous &ndash; Charles Lutter<br />
* 894 5/5/2009&ndash;1/22/2013&mdash;NEXRAD radar rainfall division by 0 error<br />
* 872 4/29/2009&ndash;1/22/2013&mdash;MODRAT does not compute any ordinates for hydrographs<br />
* 861 4/28/2009&ndash;1/22/2013&mdash;Problem displaying image in GIS module with ArcObjects enabled<br />
* 859 4/28/2009&ndash;1/22/2013&mdash;WMS not responding when extracting cross-sections from this TIN<br />
* 651 3/4/2009&ndash;1/22/2013&mdash;Crash when converting from drainage to a 1-D hydr. centerline coverage<br />
* 632 2/27/2009&ndash;1/22/2013&mdash;WMS Printing Text Bug<br />
* 618 2/26/2009&ndash;1/22/2013&mdash;SWMM hydrauilc schematic data is not saved to or read from the wms or wpr project file<br />
* 551 2/6/2009&ndash;1/22/2013&mdash;Using the default GSSHA *.cmt file to generate initial parameters<br />
* 550 2/6/2009&ndash;1/22/2013&mdash;Verify GSSHA smooth streams to thalweg data is working correctly<br />
* 539 2/6/2009&ndash;1/22/2013&mdash;WMS creates duplicate feature arcs when converting this CAD file to Feature Arcs<br />
* 427 1/13/2009&ndash;1/22/2013&mdash;Change all *.wpr files in the WMS 8.2 tutorials to *.wms files<br />
* 275 12/3/2008&ndash;1/22/2013&mdash;One too many discharge curves shown in reservoir storage capacity window for MODRAT<br />
* 256 11/24/2008&ndash;1/22/2013&mdash;Adding and retrieving diversions messes up tree item display when panning<br />
* 251 11/21/2008&ndash;1/18/2013&mdash;Interpolation error message in detention basin calculator<br />
* 212 11/12/2008&ndash;1/18/2013&mdash;There is a heap corruption (writing beyond the bounds of allocated memory) when running through the TINs tutorial-difficult fix<br />
* 198 11/10/2008&ndash;1/18/2013&mdash;CAD&rarr;TIN command not working for Bowman Dam CAD file<br />
* 197 11/10/2008&ndash;1/18/2013&mdash;CAD file displays in WMS 8.0 but not WMS 8.1<br />
* 838 4/22/2009&ndash;1/18/2013&mdash;The projection dialog needs to be larger- or at least be resizable<br />
* 117 10/16/2008&ndash;1/18/2013&mdash;pon Completion of the second step or the Volume 6, Chapter 3 Tutorial (NEXRAD), WMS Crashes.<br />
* 285 12/8/2008&ndash;1/18/2013&mdash;Optimize drawing the soil and land use legends<br />
* 187 11/6/2008&ndash;1/18/2013&mdash;Problem importing infiltration parameters from saved GSSHA projects<br />
* 172 10/31/2008&ndash;1/18/2013&mdash;Vanishing WMS Bug<br />
* 5796 1/4/2013&ndash;1/18/2013&mdash;allow more than 300 rows of data in HEC-HMS XY series windows<br />
* 5794 1/4/2013&ndash;1/18/2013&mdash;CN doesn't update in TR-55 when a project with a computed CN is added<br />
* 5808 1/8/2013&ndash;1/18/2013&mdash;Stream link numbers don't refresh<br />
* 5830 1/15/2013&ndash;1/17/2013&mdash;Letter "e" is missing in the word "Select" for Select grid column<br />
* 5742 12/5/2012&ndash;1/17/2013&mdash;Problem getting NED DEM data for Hawaiian Islands<br />
* 5813 1/10/2013&ndash;1/14/2013&mdash;Several bugs related to the OC Rational method<br />
* 5783 12/28/2012&ndash;1/11/2013&mdash;GIS to feature objects wizard doesn't transfer land use names<br />
* 5784 12/28/2012&ndash;1/10/2013&mdash;rename "Level2" option in GIS to feature objects wizard<br />
* 4467 12/9/2011&ndash;1/10/2013&mdash;The WDM file can't be read when trying to define external sources when using HSPF.<br />
* 5579 10/12/2012&ndash;1/9/2013&mdash;It takes a long time to read WMS Map files<br />
* 4837-3/13/2012&ndash;1/8/2013&mdash;Make sure all the tutorials (especially the first few) have the correct directories where the files are located<br />
* 5415 8/20/2012&ndash;1/4/2013&mdash;Changed to culvert parameters not saved<br />
* 5530 10/1/2012&ndash;1/3/2013&mdash;(Your horizontal and vertical units are inconsistent)-message for some tutorials<br />
* 5731 11/30/2012&ndash;12/27/2012&mdash;Crash when trying to run an OC Rational simulation<br />
* 5571 10/11/2012&ndash;12/27/2012&mdash;Possible problem reading solutions from multiple scenarios<br />
* 5712 11/28/2012&ndash;12/26/2012&mdash;WMS only updates the CELL ID when you select cells in a GSSHA model<br />
* 5554 10/8/2012&ndash;12/14/2012&mdash;WMS does not recognize MODRAT project file or MODRAT solution file<br />
* 5565 10/10/2012&ndash;12/14/2012&mdash;Add an option to modify the active dataset for more than one cell on your 2D grid<br />
* 5570 10/11/2012&ndash;12/13/2012&mdash;Problem with tutorial 55: GSSHA Overland Flow<br />
* 5592 10/15/2012&ndash;12/13/2012&mdash;Transition to new CheckForVersion function for version checking<br />
* 5604 10/18/2012&ndash;12/12/2012&mdash;Color fill contour method is not working for displaying GSSHA solutions<br />
* 5608 10/19/2012&ndash;12/12/2012&mdash;Issue with computing the CN for a TR55 model<br />
* 5610 10/19/2012&ndash;12/12/2012&mdash;Problem downloading data when using UTM coordinates with units of feet<br />
* 5607 10/19/2012&ndash;12/11/2012&mdash;Problem downloading data when using State Plane coordinates<br />
* 5700 11/19/2012&ndash;12/10/2012&mdash;The fields for Point #3 are not active in the Register Image dialog<br />
* 5744 12/6/2012&ndash;12/10/2012&mdash;Problem Merging TINs<br />
* 5750 12/7/2012&ndash;12/10/2012&mdash;The XY Series editor is causing WMS to crash<br />
* 5706 11/20/2012&ndash;12/6/2012&mdash;The crossings calculated by HY8 are not shown in the HY8 wizard in WMS<br />
* 5678 11/9/2012&ndash;12/3/2012&mdash;Problem with numbering WMS soil IDs<br />
* 5656 11/6/2012&ndash;12/3/2012&mdash;Use the same shared code to determine resolution when using the get data tools or when exporting/converting raster data<br />
* 5655 11/6/2012&ndash;11/30/2012&mdash;Create export and conversion options for all types of raster data<br />
* 5569 10/11/2012&ndash;11/30/2012&mdash;Fix dialog tab ordering<br />
* 5654 11/6/2012&ndash;11/28/2012&mdash;Use the same shared code when converting or exporting online or static raster data to another format<br />
* 5653 11/6/2012&ndash;11/21/2012&mdash;Share the ''Get Online Maps'' dialog with the '''Get Data''' tools in webservices.cpp<br />
* 4949 4/4/2012&ndash;11/16/2012&mdash;clicking the define button in the HSPF segments dialogue takes a very long time to open<br />
* 5084 5/7/2012&ndash;11/16/2012&mdash;Implement computing GSSHA index maps using land use and soil type grids (8 hours)<br />
* 5551 10/5/2012&ndash;11/6/2012&mdash;Can't compute flow directions and accumulations in GSSHA Tutorial<br />
* 5550 10/5/2012&ndash;11/6/2012&mdash;Missing Information in the Landuse ID box<br />
* 5563 10/9/2012&ndash;11/6/2012&mdash;WMS is crashing when using Hydraulic Toolbox to generate Storage Discharge Curves<br />
* 5561 10/9/2012&ndash;11/6/2012&mdash;WMS crashes when using the ''Importing USGS DEMs'' dialog<br />
* 5213 6/20/2012&ndash;11/6/2012&mdash;We need to move the tutorials to live with our code.<br />
* 5526 9/27/2012&ndash;11/6/2012&mdash;Share GMS' options to convert online data to static data (24 hours)<br />
* 5594 10/15/2012&ndash;11/2/2012&mdash;Show the Teigha version in the WMS '''Help | About''' command<br />
* 5593 10/15/2012&ndash;11/2/2012&mdash;Add Lat/Lon coordinates at the bottom of the WMS window, similar to GMS<br />
* 5595 10/15/2012&ndash;11/2/2012&mdash;Remove the Quick Tour from the ''WMS Help'' menu<br />
* 5624 10/25/2012&ndash;10/31/2012&mdash;HY-12 is not building<br />
* 5583 10/12/2012&ndash;10/31/2012&mdash;A separate coverage is created when converting CAD objects<br />
* 5577 10/11/2012&ndash;10/31/2012&mdash;The vertical units are changed when reading in a DEM with *.asc extension<br />
* 4795 3/5/2012&ndash;10/30/2012&mdash;HEC time of concentration not converted from min to hr<br />
* 585 2/13/2009&ndash;10/30/2012&mdash;Error when trying to run HSPF<br />
* 4937 4/2/2012&ndash;10/30/2012&mdash;"Could not open WDM file" error during HSPF tutorial<br />
* 5615 10/22/2012&ndash;10/25/2012&mdash;When saving a file in WMS, the *.hyd file can't be created after running the hydraulic toolbox<br />
* 5146 5/31/2012&ndash;10/23/2012&mdash;The time series data editor is not working<br />
* 5002 4/20/2012&ndash;10/23/2012&mdash;Menu command to read a GEoTIFF DEM<br />
* 5467 9/6/2012&ndash;10/22/2012&mdash;WMS crashes if a feature point is created where a point already exists<br />
* 5093 5/9/2012&ndash;10/22/2012&mdash;WMS crashes when you close the program if you're using a storm drain FHWA coverage<br />
* 5472 9/7/2012&ndash;10/19/2012&mdash;Problems with mapping attributes from storm drain shapefile to storm drain coverage (submitted by Nate Dye)<br />
* 5474 9/7/2012&ndash;10/18/2012&mdash;TOPAZ does not run on computers with the Microsoft visual studio 2005 redistributable package<br />
* 5496 9/18/2012&ndash;10/17/2012&mdash;WMS has a hard time downloading certain types of elevation data from Web Services<br />
* 5221 6/21/2012&ndash;10/17/2012&mdash;WMS shows no graphics for lexington.dwg<br />
* 5511 9/24/2012&ndash;10/17/2012&mdash;Need to frame after reading a *.dgn file (maybe *.dwg file also)<br />
* 5512 9/24/2012&ndash;10/17/2012&mdash;Crash in '''DEM | Point Attributes''' for multiple cells<br />
* 4390 11/23/2011&ndash;10/17/2012&mdash;QC Testing &ndash; HY-12 Tutorial errors<br />
* 5033 4/25/2012&ndash;10/17/2012&mdash;The channel calculator opens up when you click '''Create Stage Point'''<br />
* 5529 9/28/2012&ndash;10/2/2012&mdash;Convert to Static Image is not working<br />
<br />
=WMS 9.0 Bugfixes=<br />
==[[WMS:What's new in WMS version 9.0|Release 9.0]]/Intermediate Release 9.0.8 &ndash; October 5, 2012==<br />
WMS 9.0.8 has been posted on Aquaveo's web site. The best place to obtain the update is from the download link on Aquaveo's web site at [http://www.aquaveo.com/downloads?tab=3#TabbedPanels http://www.aquaveo.com/downloads]. The following known bugs have been fixed in this version:<br />
<br />
Bug ID Date Submitted&mdash;Updated-Summary<br />
<br />
* 5399 8/15/2012&ndash;9/28/2012&mdash;WMS should read in HEC-RAS water surface elevations from *.geo files<br />
* 5492 9/17/2012&ndash;9/27/2012&mdash;WMS 9.0 freezes when attempting to load a GeoTIFF with land use data<br />
* 5447 8/31/2012&ndash;9/26/2012&mdash;Texture Mapping Behavior<br />
* 5389 8/13/2012&ndash;9/26/2012&mdash;Duplicate TINs option is messed up<br />
* 5390 8/13/2012&ndash;9/25/2012&mdash;Problem adding points to a TIN<br />
* 4828 3/9/2012&ndash;9/13/2012&mdash;Texture mapping does not work<br />
* 5383 8/9/2012&ndash;9/13/2012&mdash;Contours lines turn themselves back on when you adjust a node of a texture mapped tin<br />
* 5388 8/13/2012&ndash;9/13/2012&mdash;Crash when converting a 2D scatter file to a TIN<br />
* 5411 8/17/2012&ndash;9/13/2012&mdash;crash when downloading from web<br />
* 5439 8/30/2012&ndash;9/12/2012&mdash;Problem running GSSHA when max-min/NUM_INTERP for a break point cross section > 1.0<br />
* 5440 8/30/2012&ndash;9/12/2012&mdash;WMS crashes when you double click on multiple basins in a row<br />
* 5461 9/5/2012&ndash;9/12/2012&mdash;Option to Export Image<br />
* 5462 9/5/2012&ndash;9/12/2012&mdash;WMS crashes when trying to change the attributes of an arc created outside a GSSHA grid<br />
* 5465 9/6/2012&ndash;9/11/2012&mdash;WMS progress bar stays at zero when loading some GeoTiff files<br />
* 5302 7/18/2012&ndash;9/10/2012&mdash;Warning message remains on screen after WMS finishes writing files for HMS<br />
* 5199 6/13/2012&ndash;9/5/2012&mdash;WMS crashes after closing the Channel Calculations dialog<br />
* 5201 6/14/2012&ndash;8/30/2012&mdash;WMS crashes after closing the GSSHA Contaminants dialog<br />
* 5212 6/20/2012&ndash;8/30/2012&mdash;crash when defining a detention basin<br />
* 5224 6/25/2012&ndash;8/30/2012&mdash;NSS crashes when the user enter a basin area of zero and presses the compute results button<br />
* 5424 8/24/2012&ndash;8/29/2012&mdash;There is an error message when trying to export a GIS file WMS 9.0x64<br />
* 5251 7/2/2012&ndash;8/27/2012&mdash;Handle data outside of selected bounds for the Get Data command (6 Hours)<br />
* 5253 7/2/2012&ndash;8/23/2012&mdash;Check Defining Cross Section D and Z values (6 Hours)<br />
* 5265 7/6/2012&ndash;8/21/2012&mdash;Problem with assigning mapping table values from a GSSHA mapping table file (again)<br />
* 5272 7/11/2012&ndash;8/20/2012&mdash;drainage basin display options button does not resize with display options window<br />
* 5304 7/20/2012&ndash;8/20/2012&mdash;crash when selecting a basin, exiting, and then selecting the basin again<br />
* 5308 7/20/2012&ndash;8/20/2012&mdash;WMS crashes when trying to select a basin<br />
* 5309 7/20/2012&ndash;8/17/2012&mdash;WMS freezes when attempting to load a project file<br />
* 5311 7/20/2012&ndash;8/16/2012&mdash;extracted cross sections are different when using TIN and DEM<br />
* 5340 7/27/2012&ndash;8/16/2012&mdash;WMS freezes when reading in a GSSHA solution<br />
* 5325 7/24/2012&ndash;8/16/2012&mdash;input hydrograph file not written correctly in MODRAT project<br />
* 5338 7/26/2012&ndash;8/15/2012&mdash;WMS crashes/freezes when trying to convert from shapefile to feature objects<br />
* 5324 7/23/2012&ndash;8/14/2012&mdash;WMS crashes after closing the HGL and EGL profiles window<br />
* 5195 6/13/2012&ndash;7/24/2012&mdash;Need a way to import storm drain attributes from a shapefile to WMS storm drain module<br />
* 5143 5/31/2012&ndash;6/22/2012&mdash;contour legend not included in print out<br />
* 5113 5/16/2012&ndash;6/22/2012&mdash;WMS partially freezes when saving a file in the Hydrologic Modeling Module<br />
* 5114 5/16/2012&ndash;6/22/2012&mdash;Image files for bug report 5113.<br />
* 5104 5/11/2012&ndash;6/21/2012&mdash;Crash when viewing land use attribute legend<br />
* 5021 4/23/2012&ndash;6/21/2012&mdash;The Define... button in the Detention Basin Hydrograph Routing dialog doesn't work<br />
* 5145 5/31/2012&ndash;6/20/2012&mdash;Problem with units when defining HEC-1 reservoir data<br />
* 5141 5/30/2012&ndash;6/18/2012&mdash;WMS crashes when you close the Channel Analysis dialog<br />
* 5103 5/11/2012&ndash;6/18/2012&mdash;Extra quotes added at the end of a weir (and possibly other structures) when launching the detention basin calculator from WMS<br />
* 4816 3/7/2012&ndash;6/18/2012&mdash;WMS Crash converting DEM to 2d grid<br />
* 5131 5/22/2012&ndash;6/12/2012&mdash;WMS cannot export Thiessen Polygons to shape file if the raingage type is set to HEC<br />
* 4829 3/9/2012&ndash;6/11/2012&mdash;Convert all triangle functions (such as gmComputeCircumcircle) to use shared triangle functions instead of WMS functions<br />
* 4846 3/14/2012&ndash;6/7/2012&mdash;Problem with canceling getting data using web services<br />
* 4850 3/14/2012&ndash;6/6/2012&mdash;Problem getting DEM data for really large areas<br />
* 4971 4/12/2012&ndash;6/6/2012&mdash;WMS partially freezes when when trying to define storage capacity data<br />
* 4847 3/14/2012&ndash;6/6/2012&mdash;-Bogus % Complete number in progress bar<br />
* 4843 3/13/2012&ndash;6/4/2012&mdash;Crash in Basic Feature Objects tutorial-setting soil attributes<br />
* 4963 4/6/2012&ndash;5/30/2012&mdash;HY-8 Wizard storage-capacity issue<br />
* 5024 4/24/2012&ndash;5/18/2012&mdash;Select/Zoom Hydrologic Tree Elements<br />
* 4946 4/4/2012&ndash;5/16/2012&mdash;Check the segment renumbering for CE-QUAL-W2<br />
* 4990 4/18/2012&ndash;5/16/2012&mdash;Create Feature Point option in Single Point Reprojection dialog doesn't work<br />
* 4994 4/18/2012&ndash;5/15/2012&mdash;Cannot save HEC-RAS model without a cross-section database without getting errors<br />
* 4997 4/18/2012&ndash;5/15/2012&mdash;Crash when saving NSS project<br />
* 5041 4/26/2012&ndash;5/11/2012&mdash;The Clean Up Model button in the GSSHA wizard is not working<br />
* 5046 4/27/2012&ndash;5/11/2012&mdash;An additional (0,0) point is created when creating cross sections<br />
* 5028 4/24/2012&ndash;5/8/2012&mdash;Option to change to metric units<br />
* 5054 5/1/2012&ndash;5/8/2012&mdash;WMS crashes when you close the Constituent Mass window<br />
* 5026 4/24/2012&ndash;5/7/2012&mdash;DEM doesn't overlap<br />
* 5015 4/23/2012&ndash;5/7/2012&mdash;DEM and georeferenced image don't overlap<br />
* 4855 3/15/2012&ndash;5/7/2012&mdash;WMS crashes when color filling soils polygons<br />
* 5039 4/26/2012&ndash;5/3/2012&mdash;WMS crashes when you try to compute basin data (2)<br />
* 5014 4/23/2012&ndash;5/3/2012&mdash;WMS crashes when you try to compute basin data<br />
* 5020 4/23/2012&ndash;5/3/2012&mdash;WMS crashes when trying to change the projection for the DEM<br />
* 5036 4/25/2012&ndash;5/3/2012&mdash;WMS crashes when you try to reproject a DEM<br />
* 4845 3/14/2012&ndash;5/2/2012&mdash;Fix link in DEM Delineation tutorial: Section 4.4<br />
* 4849 3/14/2012&ndash;5/1/2012&mdash;Specify toggle box has changed to "Set" toggle box in the Reprojection dialog<br />
* 4883 3/21/2012&ndash;4/24/2012&mdash;HY8UnitsConversion.cpp and possibly other files are in 2 places<br />
* 4872 3/19/2012&ndash;4/19/2012&mdash;The coverage type and attributes are changed when opening .map files<br />
* 4995 4/18/2012&ndash;4/18/2012&mdash;WMS is not automatically updating the Energy Slope for routing.<br />
* 4858 3/15/2012&ndash;4/18/2012&mdash;WMS can't find cross-section database<br />
* 4868 3/19/2012&ndash;4/18/2012&mdash;WMS crashes/freezes when trying to open a *.map file<br />
* 4579 1/12/2012&ndash;4/17/2012&mdash;Add global mapper as an option for elevation file I/O<br />
* 4884 3/21/2012&ndash;4/12/2012&mdash;Concentration Points are not shown in the Orange County Rational Method &ndash; Tree Mapping dialog<br />
* 4916 3/29/2012&ndash;4/12/2012&mdash;Add option to prevent values from being overirdden when computing basin data<br />
* 4936 4/2/2012&ndash;4/9/2012&mdash;crash when trying to convert TIN to DEM<br />
* 4926 3/30/2012&ndash;4/9/2012&mdash;WMS crashes when trying to assign precipitation info<br />
* 4873 3/19/2012&ndash;4/6/2012&mdash;There is a problem loading HEC-RAS data<br />
* 4760 2/23/2012&ndash;4/5/2012&mdash;crash when using the "GIS Data &rarr; Dataset" button for a GSSHA model<br />
* 4938 4/2/2012&ndash;4/4/2012&mdash;WMS crashes if you try to close the 'Select Orange County GIS losses output file' dialog<br />
* 4814 3/7/2012&ndash;4/4/2012&mdash;Index maps can't be created when using Data Calculator<br />
* 4314 11/2/2011&ndash;3/29/2012&mdash;Add option to reverse the zoom direction of the mouse wheel<br />
* 4697 2/9/2012&ndash;3/23/2012&mdash;Crash when loading in multiple DEMs<br />
* 4786 3/1/2012&ndash;3/23/2012&mdash;Advanced DEM delineation tutorial issue<br />
* 4712 2/13/2012&ndash;3/23/2012&mdash;Hydraulic Toolbox and WMS link is broken<br />
* 4674 2/6/2012&ndash;2/29/2012&mdash;Problems with TIN breaklines<br />
* 4469 12/9/2011&ndash;2/29/2012&mdash;Converting TIN to DEM results in bad data points<br />
* 4677 2/6/2012&ndash;2/28/2012&mdash;freeze when trying to import GSSHA precipitation gage file<br />
* 4661 2/1/2012&ndash;2/28/2012&mdash;OC Hydrograph GIS tutorial has the wrong title<br />
* 4536 1/4/2012&ndash;2/28/2012&mdash;WMS in not properly creating the radarrain and radargrid *.dss files for HEC-HMS<br />
* 4561 1/9/2012&ndash;2/27/2012&mdash;WMS is not properly creating the .dss file for HEC-HMS<br />
* 4570 1/10/2012&ndash;2/27/2012&mdash;WMS crashes when trying to change display options for index maps<br />
* 4645 1/30/2012&ndash;2/24/2012&mdash;Improper Unit<br />
* 4664 2/2/2012&ndash;2/24/2012&mdash;WMS crashes while clicking "Next Hydrograph Station" button<br />
* 4667 2/2/2012&ndash;2/24/2012&mdash;WMS writing wrong Overland BC code<br />
* 4678 2/7/2012&ndash;2/22/2012&mdash;Slow printing when using an online image<br />
* 4474 12/9/2011&ndash;2/22/2012&mdash;WMS in not properly creating the *.dss file for HEC-HMS<br />
* 4318 11/2/2011&ndash;2/21/2012&mdash;HEC-HMS tutorial needs to be fixed<br />
* 4412 11/30/2011&ndash;2/17/2012&mdash;WMS crashes when trying to change the display options for TINs<br />
* 3578 5/26/2011&ndash;2/17/2012&mdash;HMS Properties Spreadsheet loses scroll location after entering Basin Data Tc dialog<br />
* 4723 2/15/2012&ndash;2/15/2012&mdash;Saving as a google earth file does not work correctly.<br />
* 4082 9/2/2011&ndash;2/13/2012&mdash;A single DEM appears twice in the project explorer.<br />
* 3651 6/10/2011&ndash;2/13/2012&mdash;SCE file not found in GSSHA automatic calibration<br />
* 4078 9/2/2011&ndash;2/13/2012&mdash;HSPF dialog takes a long time to appear<br />
* 4376 11/17/2011&ndash;2/10/2012&mdash;Crash when importing EPA SWMM file<br />
* 4266 10/21/2011&ndash;2/6/2012&mdash;DEM Does not default to correct coordinate system (projection) when importing<br />
* 4265 10/21/2011&ndash;1/26/2012&mdash;Problem finding cross section database in attached file<br />
* 4413 11/30/2011&ndash;1/26/2012&mdash;Web data not downloading<br />
<br />
==Release 9.0 Beta &ndash; January 24, 2012==<br />
WMS 9.0 Beta has been posted on Aquaveo's web site. The best place to obtain the update is from the download link on Aquaveo's web site at [http://www.aquaveo.com/downloads?tab=3#TabbedPanels http://www.aquaveo.com/downloads]. A list of significant new features is located [[WMS:What%27s_new_in_WMS_version_9.0|here]]. The following known bugs have been fixed in this version:<br />
<br />
Bug ID Date Submitted&mdash;Updated-Summary<br />
* 4280 10/25/2011&ndash;1/24/2012&mdash;Problem with GSSHA stream arc file I/O in *.cif file<br />
* 4279 10/25/2011&ndash;1/24/2012&mdash;Problem with GSSHA overland boundary condition in *.cmt file<br />
* 4491 12/14/2011&ndash;1/20/2012&mdash;The check box in the All row in the properties dialog doesn't work<br />
* 4489 12/14/2011&ndash;1/18/2012&mdash;HY-8 Shapes crash<br />
* 4390 11/23/2011&ndash;1/18/2012&mdash;QC Testing &ndash; HY-12 Tutorial errors<br />
* 4520 1/3/2012&ndash;1/18/2012&mdash;Crash when trying to create HY-12 structure<br />
* 4307 11/1/2011&ndash;1/17/2012&mdash;Images tutorial needs to be fixed<br />
* 4308 11/1/2011&ndash;1/16/2012&mdash;DEM Basics tutorial needs to be fixed<br />
* 4311 11/2/2011&ndash;1/16/2012&mdash;DEM Delineation Tutorial needs to be fixed<br />
* 4313 11/2/2011&ndash;1/16/2012&mdash;Advanced DEM Delination Tutorial needs to be fixed<br />
* 4436 12/6/2011&ndash;1/13/2012&mdash;Extract elevation data from the Global Mapper online elevation data options instead of from the USGS seamless site<br />
* 4087 9/6/2011&ndash;1/11/2012&mdash;Gridded gage coverage display issues<br />
* 4157 9/22/2011&ndash;1/10/2012&mdash;Material not saved in "Land Poly Atts" window<br />
* 4421 12/1/2011&ndash;1/9/2012&mdash;Date/Time Display on the Hydrograph Plot window<br />
* 4494 12/15/2011&ndash;1/9/2012&mdash;WMS crashes while trying to read GSSHA solution<br />
* 4501 12/19/2011&ndash;1/6/2012&mdash;Minor HY-8 tutorial issue<br />
* 4431 12/6/2011&ndash;1/5/2012&mdash;Fix problem with WMS framing if you have an online map and you download a DEM from online data<br />
* 4518 12/29/2011&ndash;1/5/2012&mdash;New Tool for contouring based on a selected area needs a name<br />
* 4432 12/6/2011&ndash;1/5/2012&mdash;Add a forward and back view button to the WMS interface in the static tools, similar to the buttons in HydroDesktop<br />
* 4528 1/3/2012&ndash;1/4/2012&mdash;Soil erosion parameters in cmt file is saved incorrectly<br />
* 4433 12/6/2011&ndash;12/30/2011&mdash;Add an option to convert online images to a normal (static) image in the map module<br />
* 4443 12/6/2011&ndash;12/14/2011&mdash;Add elevation data site to GSDA site<br />
* 4434 12/6/2011&ndash;12/14/2011&mdash;Create a separate non-global-mapper interface for accessing online images<br />
* 4451 12/6/2011&ndash;12/12/2011&mdash;Make the MODRAT renumber selection dialog modeless<br />
* 4423 12/1/2011&ndash;12/9/2011&mdash;GSSHA Overland Boundary Condition<br />
* 4199 10/5/2011&ndash;12/7/2011&mdash;Crop Collar and Uncrop Collar commands not active<br />
* 4379 11/18/2011&ndash;12/7/2011&mdash;WMS crashes when tryring to crop the collar of an image<br />
* 4446 12/6/2011&ndash;12/7/2011&mdash;Remove or fix Crop Collars in WMS (4 hours)<br />
* 4086 9/6/2011&ndash;12/6/2011&mdash;NEXRAD MODClark Tutorial Issues<br />
* 4139 9/16/2011&ndash;12/5/2011&mdash;Only one point shows up when loading WMS project with MODRAT model<br />
* 4194 10/3/2011&ndash;12/2/2011&mdash;Contours for TIN-> DEM Conversion not displaying at all<br />
* 4089 9/6/2011&ndash;12/1/2011&mdash;Hydrologic tree does not appear<br />
* 4128 9/14/2011&ndash;12/1/2011&mdash;WMS crashes section 8.1 "Orange County Unit Hydrograph &ndash; GIS" tutorial.<br />
* 4096 9/7/2011&ndash;11/30/2011&mdash;NSS not registered<br />
* 4102 9/8/2011&ndash;11/30/2011&mdash;HEC-1 does not run after adding a diversion<br />
* 4127 9/13/2011&ndash;11/30/2011&mdash;Mean basin slope not assigned for some equations in NSS<br />
* 4071 9/1/2011&ndash;11/29/2011&mdash;WMS 8.4.21 crashes when trying to load GSSHA project file<br />
* 4211 10/7/2011&ndash;11/29/2011&mdash;Crash when trying to load *.gdm file<br />
* 4204 10/6/2011&ndash;11/29/2011&mdash;Crash when trying to smooth streams<br />
* 4240 10/14/2011&ndash;11/28/2011&mdash;GSSHA crash when running long term richard's infiltration simulation<br />
* 4225 10/12/2011&ndash;11/28/2011&mdash;Rewrite the code that displays the embankment cells in a GSSHA project<br />
* 4198 10/5/2011&ndash;11/22/2011&mdash;Updates to the Data Calculator<br />
* 4272 10/24/2011&ndash;11/11/2011&mdash;Time Series Editor<br />
* 4271 10/24/2011&ndash;11/11/2011&mdash;Time Series Editor, Split time series for GSSHA<br />
* 3638 6/7/2011&ndash;11/8/2011&mdash;Assertion when going to HY-12 Junction data<br />
* 4057 8/29/2011&ndash;11/8/2011&mdash;Modifying soil input field in the MODRAT Job Control changes rain input field<br />
* 3637 6/7/2011&ndash;11/8/2011&mdash;HY-12 Structure types are not sorted correctly for links<br />
* 4161 9/23/2011&ndash;11/1/2011&mdash;MODRAT Tc values greater than 30 minutes capped at 30 minutes without a warning<br />
* 4168 9/26/2011&ndash;10/31/2011&mdash;Problem with Use Thalweg Data command in the GSSHA Stream Profile Editor<br />
* 4191 9/30/2011&ndash;10/31/2011&mdash;Input hydro graph loses data if has more than 300 time steps.<br />
* 3977 8/12/2011&ndash;10/28/2011&mdash;Tc value does not appear where it should<br />
* 3963 8/11/2011&ndash;10/27/2011&mdash;WMS crashes when I include pipe node in/out flow<br />
* 4009 8/18/2011&ndash;10/26/2011&mdash;WMS crashes when clicking depth solution<br />
* 4062 8/30/2011&ndash;10/26/2011&mdash;OC Rational Tutorial Won't Run<br />
* 3697 6/22/2011&ndash;10/25/2011&mdash;WMS 8.4 does not save re-projection<br />
* 3738 7/5/2011&ndash;10/24/2011&mdash;Window is not big enough for text<br />
* 3978 8/12/2011&ndash;10/24/2011&mdash;Must save WMS project before calculating CN<br />
* 4094 9/7/2011&ndash;10/21/2011&mdash;Uninstallation of WMS 8.4 does not work<br />
* 3981 8/15/2011&ndash;10/21/2011&mdash;WMS 8.4.19 crashes in SMPDBK tutorial<br />
* 4007 8/18/2011&ndash;10/20/2011&mdash;Crash when creating an arc attached to outlet<br />
* 3644 6/9/2011&ndash;10/20/2011&mdash;Issue with storm/tile drains<br />
* 3886 8/2/2011&ndash;10/14/2011&mdash;Rational solution not saved in EPA SWMM file unless certain contitions met<br />
* 3889 8/2/2011&ndash;10/14/2011&mdash;Node and link elevations not saved in WMS<br />
* 3912 8/8/2011&ndash;10/14/2011&mdash;WMS not saving invert elevations for SWMM interface.<br />
* 3946 8/10/2011&ndash;10/14/2011&mdash;WMS not reading in Link and Node elevations or names from EPA SWMM file<br />
* 3947 8/10/2011&ndash;10/14/2011&mdash;WMS not reading link and node names from xpSWMM file.<br />
* 4205 10/6/2011&ndash;10/11/2011&mdash;Input hydro graph truncated for modrat simulation<br />
* 4080 9/2/2011&ndash;10/3/2011&mdash;Problem with saving EPA-SWMM data<br />
* 3648 6/9/2011&ndash;9/23/2011&mdash;WMS 8.4 crashes when you select Remove Flat Triangles<br />
* 3680 6/16/2011&ndash;9/16/2011&mdash;include build number at end of WMS in "Help | About" dialog<br />
* 3722 6/30/2011&ndash;9/15/2011&mdash;Updating Tutorial<br />
* 3832 7/20/2011&ndash;9/15/2011&mdash;Map to Hydrologic Model option not working in Detention Basin Editor<br />
* 4081 9/2/2011&ndash;9/14/2011&mdash;Changes to GSSHA .cmt file for WMS 9.0<br />
* 3985 8/15/2011&ndash;9/12/2011&mdash;GSSHA calibration Parameter replacement issue<br />
* 4035 8/25/2011&ndash;9/12/2011&mdash;Add the OVERLAND_BACKWATER card to the WMS GSSHA interface<br />
* 4108 9/8/2011&ndash;9/9/2011&mdash;WMS becomes unresponsive when working with a CE-QUAL-W2 control file<br />
* 3703 6/24/2011&ndash;9/7/2011&mdash;GSSHA modeling basics infiltration tutorial bug<br />
* 3611 6/2/2011&ndash;9/6/2011&mdash;Add the GMS unit test debug dialog to shared code and share it with WMS<br />
* 3403 4/13/2011&ndash;9/1/2011&mdash;Problem computing overbank flow when running GSSHA (likely a GSSHA bug or potential problem)<br />
* 3671 6/15/2011&ndash;8/31/2011&mdash;Hydraulic Toolbox Tutorial quick fixes for Eric or Richard (2 hours)<br />
* 3324 3/29/2011&ndash;8/31/2011&mdash;Problem with MODRAT Soil file definition<br />
* 3601 6/1/2011&ndash;8/31/2011&mdash;Font settings lost on some display options in dev.<br />
* 3481 5/4/2011&ndash;8/30/2011&mdash;Cropping collar using right click menu not working properly<br />
* 2997 1/20/2011&ndash;8/30/2011&mdash;error about HEC programs during WMS 8.4 install<br />
* 3569 5/25/2011&ndash;8/30/2011&mdash;MODRAT-GIS Tutorial Issues<br />
* 3440 4/25/2011&ndash;8/29/2011&mdash;Review Spatial rainfall tutorials<br />
* 3441 4/25/2011&ndash;8/29/2011&mdash;Review MODRAT tutorials<br />
* 3378 4/6/2011&ndash;8/25/2011&mdash;Plots not showing up in OC rational method GIS tutorial<br />
* 3414 4/18/2011&ndash;8/25/2011&mdash;Error when running OC Rational Tutorial<br />
* 2805 11/19/2010&ndash;8/23/2011&mdash;Unable to write Area-Reduction Factor in GSSHA mapping table file<br />
* 3402 4/12/2011&ndash;8/23/2011&mdash;Area reduction GSSHA table not included in WMS<br />
* 3494 5/9/2011&ndash;8/23/2011&mdash;Could we add a new tool that would contour a given area?<br />
* 3810 7/15/2011&ndash;8/22/2011&mdash;"Could not assign length and orientation" error when trying to "Get lengths and orientation of branch segments" in CE-QUAL-W2 tu<br />
* 3249 3/15/2011&ndash;8/16/2011&mdash;Values multiplied by 3.28 when exporting a GeoTIFF<br />
* 3895 8/3/2011&ndash;8/15/2011&mdash;CE-QUAL-W2 crashes when trying to import boundary conditions for a branch<br />
* 3885 8/2/2011&ndash;8/15/2011&mdash;CE-QUAL-W2 crashes when trying to import a meteorological file<br />
* 3813 7/15/2011&ndash;8/12/2011&mdash;Resizing WMS causing computer to freeze<br />
* 3807 7/14/2011&ndash;8/12/2011&mdash;Crash when double clicking title bar<br />
* 3803 7/13/2011&ndash;8/10/2011&mdash;Coordinate Conversion Crash<br />
* 3796 7/12/2011&ndash;8/9/2011&mdash;See if 10-85 basin parameters are being transferred to the NSS database<br />
* 3743 7/6/2011&ndash;8/4/2011&mdash;More HY-8 Wizard Tutorial Issues<br />
* 3742 7/6/2011&ndash;8/4/2011&mdash;WMS crashes when doing DEM &rarr; Stream Arcs<br />
* 3741 7/6/2011&ndash;8/4/2011&mdash;WMS freezes when delineating watershed in HY-8 wizard<br />
* 3560 5/24/2011&ndash;8/4/2011&mdash;WMS 8.4 HSPF Bugs to fix (12 Hours)<br />
* 3496 5/9/2011&ndash;8/3/2011&mdash;Clean up the hydraulic toolbox tutorial and put it online<br />
* 3477 5/3/2011&ndash;8/1/2011&mdash;Extracting X-sections error if Elevation data is not selected<br />
* 3478 5/3/2011&ndash;8/1/2011&mdash;Exporting KMZ vector file<br />
* 3503 5/9/2011&ndash;7/28/2011&mdash;Export TIN-based filmloop to Google Earth<br />
* 3497 5/9/2011&ndash;7/28/2011&mdash;Bugs that came up in the HY8 modeling wizard tutorial<br />
* 3515 5/11/2011&ndash;7/27/2011&mdash;Not all soil types mapped to index map<br />
* 3612 6/2/2011&ndash;7/26/2011&mdash;Add integration tests to WMS<br />
* 3525 5/12/2011&ndash;7/25/2011&mdash;Error message while converting feature arcs to TIN<br />
* 286 12/8/2008&ndash;7/20/2011&mdash;Rewrite Infiltration tutorial on www.gsshawiki.com<br />
* 1511 10/12/2009&ndash;7/20/2011&mdash;New NSS databases not compatible with WMS 8.2<br />
* 995 6/3/2009&ndash;7/20/2011&mdash;In the 2D Scatter Data tab of the Display Options dialog decimal Z magnifications are not currently supported.<br />
* 3681 6/16/2011&ndash;7/18/2011&mdash;error when trying to install WMS 8.4.15 when WMS 8.4.14 is already installed<br />
* 3675 6/15/2011&ndash;7/18/2011&mdash;SWMM tutorial not exporting flowrates<br />
* 3678 6/16/2011&ndash;7/15/2011&mdash;SWMM Tutorial Bug: WMS not writing hydrograph information to EPA SWMM<br />
* 3672 6/15/2011&ndash;7/14/2011&mdash;Bug in SWMM tutorial: area exported in sq. mi. even though computed in acres<br />
* 3083 2/8/2011&ndash;7/14/2011&mdash;SWMM tutorial bugs<br />
* 3588 5/31/2011&ndash;7/13/2011&mdash;Problems with Modified Puls xy series editor in HEC-HMS Parameters dialog<br />
* 3366 4/5/2011&ndash;7/5/2011&mdash;Export a filmoop or KMZ from a TIN<br />
* 1648 11/23/2009&ndash;7/5/2011&mdash;WMS runs out of memory when converting one TIN contour to feature objects.<br />
* 2118 4/21/2010&ndash;7/5/2011&mdash;Clean&rarr;Snap Selected Nodes command gives you an hourglass instead of a select cursor<br />
* 1708 12/16/2009&ndash;7/5/2011&mdash;WMS not Print Correctly<br />
* 1496 10/7/2009&ndash;7/5/2011&mdash;Problem reading *.wpr or *.wms file with TIFF file<br />
* 996 6/3/2009&ndash;7/5/2011&mdash;wmsnss.exe crash<br />
* 865 4/28/2009&ndash;7/5/2011&mdash;Check to see if the fix for the single-basin at outlet problem has worked out in the dev version<br />
* 3732 7/1/2011&ndash;7/5/2011&mdash;Freeze when trying to delineate a basin in WMS 8.4<br />
* 3513 5/10/2011&ndash;6/30/2011&mdash;Crash or freeze when reading solution<br />
* 3713 6/29/2011&ndash;6/29/2011&mdash;Problem saving HMS file<br />
* 3531 5/13/2011&ndash;6/15/2011&mdash;WMS crash while converting DEM to TIM<br />
* 3609 6/2/2011&ndash;6/7/2011&mdash;Issues with new combo boxes in Film Loop Setup<br />
* 3590 5/31/2011&ndash;6/7/2011&mdash;Hydraulic Toolbox tutorial issue<br />
* 3634 6/6/2011&ndash;6/7/2011&mdash;Problem filtering TIN<br />
* 3492 5/9/2011&ndash;6/6/2011&mdash;Filtering angle option for TIN filtering not working properly<br />
* 3404 4/13/2011&ndash;6/2/2011&mdash;Add a pre-link event to copy shapesdb.dat (used in HY8) to the 64-bit WMS folder (1 hour)<br />
* 3431 4/25/2011&ndash;6/2/2011&mdash;Problem reading GSSHA project and GSSHA solution<br />
* 3475 5/3/2011&ndash;6/1/2011&mdash;Model Check Error when doing GSSHA<br />
* 3463 4/29/2011&ndash;5/31/2011&mdash;GSSHA card improperly written out in *.cif file<br />
* 3396 4/11/2011&ndash;5/31/2011&mdash;Index maps do not display in GSSHA model<br />
* 3397 4/11/2011&ndash;5/16/2011&mdash;GSSHA Film Loop<br />
* 2550 9/7/2010&ndash;5/11/2011&mdash;Need to be able to assign land use IDs manually<br />
* 3471 5/2/2011&ndash;5/3/2011&mdash;WMS crashes when opening hydrograph plot from palmer canyon GIS MODRAT model<br />
* 3239 3/14/2011&ndash;5/2/2011&mdash;problem with base files in GSSHA tutorials<br />
* 3240 3/14/2011&ndash;4/29/2011&mdash;GSSHA stops prematurely after adding a detention basin<br />
* 3231 3/11/2011&ndash;4/21/2011&mdash;Problem with flow accumulations at depression points<br />
* 3248 3/15/2011&ndash;4/20/2011&mdash;WMS 8.4 always says you're out of date<br />
* 3261 3/17/2011&ndash;4/19/2011&mdash;Redo the way we handle stream and cell boundary conditions in GSSHA<br />
* 3254 3/15/2011&ndash;4/19/2011&mdash;Error when selecting below last time step of GSSHA depth output<br />
* 3348 3/31/2011&ndash;4/18/2011&mdash;Problem with downloading land use data (possibly other web services also)<br />
* 3368 4/5/2011&ndash;4/14/2011&mdash;Bug in GSSHA Modeling Basics Infiltration tutorial (.cmt file problem--check)<br />
* 3369 4/5/2011&ndash;4/13/2011&mdash;Bug in GSSHA - Modeling - Wizard tutorial-GSSHA model checker errors<br />
* 3371 4/5/2011&ndash;4/13/2011&mdash;Problem with running GSSHA with wells and saving GSSHA well files<br />
* 3372 4/5/2011&ndash;4/11/2011&mdash;crash when running GSSHA<br />
* 3344 3/30/2011&ndash;4/6/2011&mdash;Minor Model check problem after opening existing project file<br />
* 3296 3/24/2011&ndash;4/6/2011&mdash;WMS hangs when processing NEXRAD radar rainfall grids<br />
* 3298 3/24/2011&ndash;4/6/2011&mdash;Fix all problems with importing and using radar rainfall grids<br />
* 3365 4/5/2011&ndash;4/5/2011&mdash;Remove a the "Crop Image" page from the wiki<br />
* 3295 3/24/2011&ndash;4/5/2011&mdash;Crash when reading GSSHA project with different size of grid cells than the .msk file in the index map<br />
* 3338 3/30/2011&ndash;4/5/2011&mdash;Select a better default for computing gage weights<br />
* 3337 3/30/2011&ndash;4/5/2011&mdash;Add a separate menu command to compute rainfall gage weights<br />
* 3330 3/30/2011&ndash;4/4/2011&mdash;Basin Time Computation Method is not saved<br />
* 3345 3/31/2011&ndash;4/4/2011&mdash;Problem with debris production estimates from MODRAT GIS Tutorial<br />
* 3343 3/30/2011&ndash;4/1/2011&mdash;Percent Impervious not mapped correctly from shapefile data<br />
* 3272 3/18/2011&ndash;3/22/2011&mdash;WMS basin boundaries not drawn completely in HEC-HMS (Willdan project)<br />
* 3157 2/22/2011&ndash;3/17/2011&mdash;Collar not cropped completely<br />
* 2992 1/20/2011&ndash;3/17/2011&mdash;WMS freezes when mapping to 1D schematic<br />
* 2993 1/20/2011&ndash;3/17/2011&mdash;WMS 8.4 freezes when trying to load a wms project file<br />
* 3255 3/16/2011&ndash;3/16/2011&mdash;WMS 8.4 installs HEC-RAS 4.1, but tries to launch 4.0<br />
* 3016 1/26/2011&ndash;3/16/2011&mdash;"Error reading scalar binary file, (floatarray)" appears when loading GSSHA depth solution<br />
* 3018 1/27/2011&ndash;3/15/2011&mdash;Second window appears after importing HEC-RAS GIS file<br />
* 2051 4/6/2010&ndash;3/15/2011&mdash;WMS crashes when trying to open RainGageBug.wms<br />
* 3019 1/27/2011&ndash;3/15/2011&mdash;Importing .cmt file into GSSHA Map Table Editor does not work<br />
* 3205 3/3/2011&ndash;3/15/2011&mdash;Problem with HMS diversions in Willdan project<br />
* 3014 1/26/2011&ndash;3/14/2011&mdash;Problem with trying to read SCS default rainfall distributions when a different version of WMS is installed then uninstalled<br />
* 2991 1/20/2011&ndash;3/14/2011&mdash;error message each time opening WMS 8.4 64-bit<br />
* 2903 12/22/2010&ndash;3/14/2011&mdash;Loading Projection file<br />
* 2900 12/21/2010&ndash;3/14/2011&mdash;Crash when generating a GSSHA grid<br />
* 3204 3/3/2011&ndash;3/11/2011&mdash;WMS not saving "description" field in HMS interface<br />
* 3198 3/1/2011&ndash;3/11/2011&mdash;% Impervious not displaying properly while Computing GIS Attributes<br />
* 3180 2/28/2011&ndash;3/11/2011&mdash;Basin Time Computation for HEC-HMS<br />
* 3079 2/8/2011&ndash;3/10/2011&mdash;TauDEM not working with depression points<br />
* 3215 3/7/2011&ndash;3/10/2011&mdash;Confusing error message when network lock has problems<br />
* 3197 3/1/2011&ndash;3/9/2011&mdash;Missing parameter in HEC-HMS Properties dialog<br />
* 3194 3/1/2011&ndash;3/9/2011&mdash;Problem with using the hydraulic toolbox in the WMS HY8 modeling wizard<br />
* 3073 2/4/2011&ndash;3/8/2011&mdash;HY-8 Wizard bugs<br />
* 3195 3/1/2011&ndash;3/8/2011&mdash;Cancel on the Hydraulic Toolbox Storage capacity input dialog does not work<br />
* 2921 1/5/2011&ndash;2/25/2011&mdash;Creating soil type coverage manually for use with GSSHA is problematic<br />
* 3074 2/4/2011&ndash;2/25/2011&mdash;crash when delineating inundated area in HY-8 wizard<br />
* 2976 1/18/2011&ndash;2/8/2011&mdash;NSS not functional in WMS 8.4<br />
<br />
=WMS 8.4 Bugfixes=<br />
==[[WMS:What's new in WMS version 8.4|Release 8.4]]/Intermediate Release WMS 8.4.9 &ndash; February 3, 2011==<br />
An update to WMS 8.4 has been posted on Aquaveo's web site. The final version of WMS 8.4 was also released in December 2010. The best place to obtain the update is from the download link on Aquaveo's web site at [http://www.aquaveo.com/ http://www.aquaveo.com/]. The following known bugs have been fixed in this version:<br />
<br />
Bug ID-Date Submitted&mdash;Updated-Summary<br />
* 3049 1/31/2011&ndash;2/1/2011&mdash;error when converting NEXRAD data to *.dss<br />
* 2681 10/15/2010&ndash;1/24/2011&mdash;Problem reading GSSHA sediment files<br />
* 2680 10/15/2010&ndash;1/24/2011&mdash;Problem with reading/saving GSSHA contaminant file from WMS<br />
* 2707 10/25/2010&ndash;1/20/2011&mdash;printed scale bar display error<br />
* 2682 10/15/2010&ndash;1/20/2011&mdash;Problem writing GSSHA project file with overland flow boundary condition<br />
* 2292 6/3/2010&ndash;1/20/2011&mdash;RAS import causing Issues<br />
* 2505 8/17/2010v1/18/2011&mdash;Problem reading HEC-1 file and writing it as an HMS file<br />
* 2665 10/11/2010&ndash;1/10/2011&mdash;DEM&rarr;Stream Arcs command not working for certain projects<br />
* 2922 1/5/2011&ndash;1/7/2011&mdash;WMS 8.4 crashes when loading Willdan .asc dem files as a group<br />
* 2549 9/7/2010&ndash;1/4/2011&mdash;WMS doesn't recognize all basins created w/ feature objects<br />
* 2511 8/20/2010&ndash;11/3/2010&mdash;WMS HANGS when deleting arc<br />
* 2624 10/4/2010&ndash;11/2/2010&mdash;Modrat Wrapper not finishing<br />
* 2623 10/1/2010&ndash;11/2/2010&mdash;Joining SSURGO data bug<br />
* 2565 9/9/2010&ndash;11/2/2010&mdash;Click on GSSHA Smooth Stream Dialog causes a crash<br />
* 2400 7/12/2010&ndash;10/28/2010&mdash;Build Polygons Crash<br />
* 2389 7/7/2010&ndash;10/28/2010&mdash;WMS 8.3 unable to Connect to Sever when selecting from web service<br />
* 2629 10/5/2010&ndash;10/27/2010&mdash;WMS cannot load images after converting DEM to TIN<br />
* 2436 7/21/2010&ndash;10/27/2010&mdash;WMS crashing when loading GIS data<br />
* 2359 6/29/2010&ndash;10/27/2010&mdash;WMS 8.3 Crashing when loading Raster<br />
* 2627 10/5/2010&ndash;10/25/2010&mdash;Severe WMS/Global Mapper bug when converting DEM to TIN<br />
* 2597 9/23/2010&ndash;10/25/2010&mdash;When loading the hydrograph solution to HEC-1 WMS Gives an error<br />
* 2508 8/19/2010&ndash;10/22/2010&mdash;WMS 84 can't load existing GSSHA model.<br />
* 2546 9/7/2010&ndash;10/20/2010&mdash;WMS Clean tool gives an hourglass instead of an arrow cursor<br />
* 2332 6/16/2010&ndash;7/19/2010&mdash;problems numbering Branch<br />
* 2321 6/11/2010&ndash;7/16/2010&mdash;Run GSSHA model button in the Hydrologic modeling wizard not working<br />
* 2311 6/9/2010&ndash;7/16/2010&mdash;Contour Options button not working<br />
* 2288 6/2/2010&ndash;7/16/2010&mdash;Hydrologic modeling wizard Define project boundary<br />
* 2244 5/24/2010&ndash;7/16/2010&mdash;flow vectors don't read in<br />
* 2239 5/20/2010&ndash;7/16/2010&mdash;Save File button not working in Coverage Overlay dialog<br />
* 2366 6/30/2010&ndash;7/15/2010&mdash;Display options<br />
* 2184 5/5/2010&ndash;7/14/2010&mdash;Tutorial change request<br />
* 2217 5/13/2010&ndash;7/13/2010&mdash;WMS not writing all lakes to file<br />
* 2215 5/13/2010&ndash;7/13/2010&mdash;Simple dam Break not finding Cross Section<br />
* 2237 5/20/2010&ndash;7/12/2010&mdash;Add the START_TIME and END_TIME cards to writing the GSSHA Project file and have fields for these cards in the GSSHA Job Control<br />
* 2108 4/19/2010&ndash;7/8/2010&mdash;Changed the elevations of a few cross sections to get rid of pooling and then tried to rerun HECRAS but it wouldn't run because<br />
* 2089 4/16/2010&ndash;7/8/2010&mdash;Cross sections Missing<br />
* 2236 5/20/2010&ndash;7/2/2010&mdash;Crash when deleting GSSHA model<br />
* 2234 5/19/2010&ndash;6/10/2010&mdash;Add option to select whether to export contaminant mass and concentration to GSSHA output control<br />
* 2156 4/28/2010&ndash;6/10/2010&mdash;Error in GSSHA Calibratiobn<br />
* 2153 4/28/2010&ndash;6/10/2010&mdash;GSSHA calibration output files<br />
* 2060 4/8/2010&ndash;6/10/2010&mdash;Allow editing polygon-selected index map ID's in the properties window<br />
* 2247 5/25/2010&ndash;6/9/2010&mdash;Add GSSHA Calibration Parameters in WMS<br />
* 2235 5/19/2010&ndash;6/9/2010&mdash;Report the name of the contaminant when reading the contaminant transport solution<br />
* 2249 5/25/2010&ndash;6/8/2010&mdash;Check while reading parameter and calibration file in GSSHA automated calibration<br />
* 2248 5/25/2010&ndash;6/8/2010&mdash;WMS does not read observed data file<br />
* 2075 4/12/2010&ndash;5/18/2010&mdash;"Error message when trying to open an image: ""The application has failed to start because gmp-vc90-mt.dll was not found"""<br />
* 2065 4/9/2010&ndash;5/18/2010&mdash;"The ""Select Shapes Tool"" in the GIS module should be an active tool but it is inactive."<br />
* 2141 4/26/2010&ndash;5/14/2010&mdash;WMS crashes when right clicking on a TIN Tree Item for a TIN that's been deleted<br />
* 2147 4/28/2010&ndash;5/13/2010&mdash;Error reading GSSHA Stochastic Simulation results<br />
* 2183 5/4/2010&ndash;5/12/2010&mdash;Save GSSHA Group Dialog<br />
* 2151 4/28/2010&ndash;5/12/2010&mdash;Issues with GSSHA Automated Calibration<br />
* 2175 5/3/2010&ndash;5/11/2010&mdash;converting dem contours to feature objects<br />
* 2143 4/26/2010&ndash;5/11/2010&mdash;Multi-Select index map grid cells<br />
* 1761 1/8/2010&ndash;4/19/2010&mdash;Louisiana SSURGO files will not download from Web Services<br />
* 1753 1/5/2010&ndash;4/19/2010&mdash;Opening this GSSHA project file causes WMS 8.3 to crash<br />
* 1754 1/6/2010&ndash;4/16/2010&mdash;WMS crashes when opening any GSSHA project with the attached *.ini file<br />
* 2020 3/29/2010&ndash;4/14/2010&mdash;Problem converting shapefile contour lines to feature objects (and then to elevations on a TIN)<br />
<br />
===Other fixes and updates===<br />
<br />
# Fixed MODRAT/WMS bugs<br />
# Rewrite all recursive functions associated with basin delineation and basin data computation<br />
# Add parameters toggle in Soil Type/Land Use attributes dialog for Initial and Constant, and add attribute for Initial Loss (in) and Constant Infiltration Rate (in/hr)<br />
# Automatically transfer Initial and Constant values to appropriate loss fields in HMS properties dialog (may require adding Initial Loss, Constant Infiltration Rate, and Percent Impervious to list of Basin data parameters)<br />
# Change "Compute Basin Data" function to only compute selected basin data parameters (may significantly reduce computation time for large datasets)<br />
# Modify HMS temporal distribution dialog to use more than 300 points<br />
<br />
=WMS 8.3 Bugfixes=<br />
==Intermediate Release WMS 8.3.4 &ndash; June 7, 2010==<br />
An update to WMS 8.3 has been posted on Aquaveo's web site. The best place to obtain the update is from the download link on Aquaveo's web site at [http://www.aquaveo.com/ http://www.aquaveo.com/]. The following known bugs have been fixed in this version:<br />
<br />
Bug Id Date Submitted&mdash;Updated-Summary<br />
* 2071 4/12/2010&ndash;5/18/2010&mdash;Zoom tool not working in Edit DEM Elevations plot window<br />
* 2084 4/14/2010&ndash;5/17/2010&mdash;DEM File won't read in<br />
* 2038 4/1/2010&ndash;4/14/2010&mdash;Placing a contour label causes WMS 8.3 to crash<br />
<br />
==Intermediate Release WMS 8.3.3 &ndash; March 19, 2010==<br />
An update to WMS 8.3 has been posted on Aquaveo's web site. The best place to obtain the update is from the download link on Aquaveo's web site at [http://www.aquaveo.com/ http://www.aquaveo.com/]. The following known bugs have been fixed in this version:<br />
<br />
Bug Id Date Submitted&mdash;Updated-Summary<br />
* 1860 2/4/2010&ndash;3/11/2010&mdash;Floating point error when running SMPDBK<br />
* 1919 2/26/2010&ndash;3/11/2010&mdash;Loading dem changes Current Coordinates.<br />
* 1944 3/3/2010&ndash;3/10/2010&mdash;Option to manually link nodes and outlets in SWMM does not work<br />
* 1958 3/4/2010&ndash;3/10/2010&mdash;"When selecting the basin icon in the NSS model (tutorial volume 2, ch3), WMS gives error window"<br />
* 1824 1/25/2010&ndash;3/9/2010&mdash;Floodplain delineation freeze<br />
* 1825 1/25/2010&ndash;3/9/2010&mdash;Opening these DEMs with Current Coordinates set to State Plane causes WMS to crash<br />
<br />
==[[WMS:What's new in WMS version 8.3|Release 8.3.0]]/Intermediate Release WMS 8.3.1 &ndash; January 26, 2010==<br />
An update to WMS 8.3 has been posted on Aquaveo's web site. The final version of WMS 8.3 was also released in December. The best place to obtain the update is from the download link on Aquaveo's web site at [http://www.aquaveo.com/ http://www.aquaveo.com/]. The following known bugs have been fixed in this version:<br />
<br />
Bug Id Date Submitted&mdash;Updated-Summary<br />
* 1762 1/8/2010&ndash;1/21/2010&mdash;"Change ""Join SSURGO data"" command to ""Join NRCS data"""<br />
* 1731 12/22/2009&ndash;1/21/2010&mdash;GSSHA cross section data not saved.<br />
* 1755 1/6/2010&ndash;1/20/2010&mdash;WMS 8.3 does not read in GSSHA custom cross-section data<br />
* 1609 11/6/2009&ndash;1/14/2010&mdash;WMS coverages not overlaying DEM properly in WMS 8.3<br />
* 1650 11/23/2009&ndash;1/13/2010&mdash;Converting TIN Contour to Feature Objects not working from menu<br />
* 1664 12/1/2009&ndash;1/12/2010&mdash;WMS crashes upon opening the .wms file included in bug #1531<br />
* 888 5/4/2009&ndash;12/3/2009&mdash;WMS 8.2 gets hung when trying to run on a computer with low resolution<br />
* 1642 11/19/2009&ndash;12/3/2009&mdash;Bug when displaying GIS data using ArcObjects in Albers coordinate system<br />
* 863 4/28/2009&ndash;11/19/2009&mdash;Problem reading land use ArcGrid with ArcObjects<br />
* 1035 6/15/2009&ndash;11/18/2009&mdash;Save files to temporary directory/filename before writing over original file<br />
* 1614 11/9/2009&ndash;11/18/2009&mdash;Map Data option for computing lag time in HEC-HMS doesn't transfer computed value<br />
* 1621 11/12/2009&ndash;11/18/2009&mdash;HMS Lag time for computing Clark's R doesn't update when edited manually<br />
* 1618 11/11/2009&ndash;11/11/2009&mdash;Button for Defining Inflow-Diverted flow in HMS Interface not working<br />
* 1615 11/9/2009&ndash;11/10/2009&mdash;WMS crashes when exporting scatter data to ASCII grid file<br />
* 1617 11/10/2009&ndash;11/10/2009&mdash;Basin area units wrong in HMS if computing basin data in acres<br />
* 1612 11/9/2009&ndash;11/9/2009&mdash;WMS giving the wrong Values in the ENDFILES<br />
* 1610 11/6/2009&ndash;11/9/2009&mdash;Land use shapefile descriptions not mapped to Level2<br />
* 1251 7/31/2009&ndash;11/9/2009&mdash;Let users change rain gage display<br />
* 450 1/15/2009&ndash;11/9/2009&mdash;WMS deletes TIN vertices and triangles when closing a project<br />
* 271 12/2/2008&ndash;11/9/2009&mdash;Cancel button does not work on the web services dialog<br />
* 237 11/19/2008&ndash;11/9/2009&mdash;Display doesn't refresh while dragging vertices<br />
* 1597 11/3/2009&ndash;11/9/2009&mdash;WMS Crash<br />
* 640 2/27/2009&ndash;11/5/2009&mdash;"Remove toggle box in CAD Data Display Options dialog &ndash; if not the whole dialog"<br />
* 1559 10/21/2009&ndash;10/30/2009&mdash;WMS title bar modification to facilitate testing of the 'release' version and elimination of the 'release robot' version<br />
* 1588 10/30/2009&ndash;10/30/2009&mdash;Problem with Extract Cross Sections dialog<br />
* 316 12/12/2008&ndash;10/30/2009&mdash;Detention basin overflowed error when running the Rational Method<br />
* 227 11/13/2008&ndash;10/30/2009&mdash;Display CAD data command does not turn CAD display off when toggled off<br />
* 226 11/13/2008&ndash;10/30/2009&mdash;CAD Layers coverages are not highlighted when they are set as the active coverage<br />
* 837 4/22/2009&ndash;10/29/2009&mdash;Why is the terraserver map scale dialog so big?<br />
* 284 12/8/2008&ndash;10/29/2009&mdash;Remove CROSS_SECTION_LIST card from GSSHA files that WMS writes<br />
* 415 1/8/2009&ndash;10/29/2009&mdash;"Upon Clicking ""Delineate Watershed"" ( Tutorials, Vol II, Ch 5, Sec 5.2.7) the file name is omitted from the title bar."<br />
* 1577 10/28/2009&ndash;10/28/2009&mdash;Default feature arc attribute not stored for 1D Hydraulic Centerline coverage<br />
* 1572 10/26/2009&ndash;10/28/2009&mdash;"Section 2.3.1, Volume 2, Chapter 2, Step 11"<br />
* 332 12/17/2008&ndash;10/28/2009&mdash;Properties window display bug<br />
* 188 11/6/2008&ndash;10/28/2009&mdash;Error reading shapefiles with associated .prj files<br />
* 178 11/4/2008&ndash;10/28/2009&mdash;Map data is hidden behind the 2D Grid when color filled contours are turned on in plan view<br />
* 177 11/4/2008&ndash;10/28/2009&mdash;Problem displaying 2D Grid flow vectors with blocked cells and color filled contours.<br />
* 851 4/24/2009&ndash;10/28/2009&mdash;"Sub-basins improperly delineated. Zero area error. Orange County Tutorial 6, section 6.3.2."<br />
* 1481 10/2/2009&ndash;10/26/2009&mdash;WMS crashes when treating generic polygons as basins.<br />
* 1568 10/23/2009&ndash;10/26/2009&mdash;MODRAT dialog warning of duplicate names when no duplicate names exist<br />
* 1517 10/13/2009&ndash;10/26/2009&mdash;Problem with moving GSSHA projects to a different directory<br />
* 832 4/21/2009&ndash;10/23/2009&mdash;Problem with sub-basin areas<br />
* 1469 9/30/2009&ndash;10/20/2009&mdash;HEC-1 Data Points<br />
* 1438 9/19/2009&ndash;10/19/2009&mdash;"Upon completion of Step 12, Section 3.4, Volume 6, the .wms or .wpr is dropped from the file name in the title bar."<br />
* 822 4/17/2009&ndash;10/16/2009&mdash;Generate IDs button never undims when entering Infiltration after Initial Moisture<br />
* 1535 10/16/2009&ndash;10/16/2009&mdash;WMS doesn't recognize drainage basin<br />
* 107 10/9/2008&ndash;10/16/2009&mdash;Incorrect prompt shown<br />
* 1531 10/15/2009&ndash;10/15/2009&mdash;Rain gage weights don't add up to one<br />
* 666 3/6/2009&ndash;10/15/2009&mdash;Contour Options dialog spreadsheet problems<br />
* 1488 10/6/2009&ndash;10/15/2009&mdash;Contour intervals incorrect when using specified values and then switching to color fill<br />
* 358 12/23/2008&ndash;10/14/2009&mdash;Save button in Project Filename page of Hydrologic Modeling Wizard overwrites existing files<br />
* 106 10/9/2008&ndash;10/14/2009&mdash;Hourglass not shown while deleting tin verts<br />
* 485 1/22/2009&ndash;10/13/2009&mdash;Problem when trying to indicate the location of WinHspfLt.exe<br />
* 314 12/12/2008&ndash;10/13/2009&mdash;Legend text in hydrograph plot for Rational method hydrographs<br />
* 219 11/12/2008&ndash;10/13/2009&mdash;Edit | Preferences window needs some tweaking<br />
* 789 4/3/2009&ndash;10/13/2009&mdash;Can't access drainage data display options<br />
* 480 1/21/2009&ndash;10/12/2009&mdash;Forum feature request: saving depression points<br />
* 140 10/24/2008&ndash;10/12/2009&mdash;Ghost Outlet Bug: WMS selects an imaginary outlet when selecting an outlet in the Map Module in 8.1<br />
* 451 1/15/2009&ndash;10/9/2009&mdash;WMS vanishes when working with a project with a deep file directory<br />
* 1472 9/30/2009&ndash;10/8/2009&mdash;MODRAT import Issue<br />
* 426 1/13/2009&ndash;10/7/2009&mdash;Saving image registration (world file) with xmdf project file<br />
* 398 1/7/2009&ndash;10/7/2009&mdash;Saving image registration data with .wms (xmdf) file<br />
* 1470 9/30/2009&ndash;10/7/2009&mdash;MODRAT Output Error<br />
* 1250 7/31/2009&ndash;10/7/2009&mdash;WMS crashes when converting a DTED DEM to a TIN and toggling the TIN display on and off<br />
* 836 4/22/2009&ndash;10/7/2009&mdash;State plane zone description not showing in shared projection dialog<br />
* 862 4/28/2009&ndash;10/7/2009&mdash;Another problem displaying image with ArcObjects enabled<br />
* 245 11/21/2008&ndash;10/7/2009&mdash;Cross section not displayed in channel calculator<br />
* 439 1/13/2009&ndash;10/7/2009&mdash;Duplicating a coverage takes a long time<br />
* 438 1/13/2009&ndash;10/7/2009&mdash;Changing coverage name in the Coverage Properties dialog takes a long time<br />
* 165 10/30/2008&ndash;10/6/2009&mdash;Rain Gage coverage should have Map data display attributes<br />
* 168 10/30/2008&ndash;10/6/2009&mdash;Legend gets stuck on WMS Screen when Selecting File | New<br />
* 433 1/13/2009&ndash;10/6/2009&mdash;Mapping shapefile to feature obejcts crash<br />
* 361 12/29/2008&ndash;10/6/2009&mdash;Problem with images on xmswiki.com<br />
* 1457 9/25/2009&ndash;10/6/2009&mdash;Crash when running OC rational<br />
* 357 12/23/2008&ndash;10/6/2009&mdash;DEM point selection tool slow selecting a DEM point<br />
* 1471 9/30/2009&ndash;10/6/2009&mdash;Adding stream arc crashes project<br />
* 315 12/12/2008&ndash;10/6/2009&mdash;Delete button in the Elevation Discharge Input dialog does not work<br />
* 301 12/9/2008&ndash;10/6/2009&mdash;Selecting a segment in the CE-QUAL-W2 Polygon Segment Attributes dialog does not select a segment in the graphics window<br />
* 1485 10/5/2009&ndash;10/6/2009&mdash;WMS vanishes when opening this GSSHA project from the wiki tutorials<br />
* 206 11/11/2008&ndash;10/5/2009&mdash;Remove Flat triangles does not work in WMS 8.2<br />
* 449 1/15/2009&ndash;10/5/2009&mdash;TIN and map file do not overlay properly in WMS 8.1<br />
* 179 11/4/2008&ndash;10/5/2009&mdash;Problem displaying 2D grid cell elevations with color filled contours<br />
* 916 5/7/2009&ndash;10/5/2009&mdash;Display issue with reading map file<br />
* 116 10/16/2008&ndash;10/5/2009&mdash;Web Services options that don't work should be dimmed out<br />
* 130 10/21/2008&ndash;10/5/2009&mdash;Errors when running through CE-QUAL tutorial in WMS 9.0<br />
* 1242 7/30/2009&ndash;10/2/2009&mdash;NSS will not load without write access to Program Files directory<br />
* 157 10/29/2008&ndash;10/2/2009&mdash;Pattern palette not working in WMS 8.1<br />
* 101 10/7/2008&ndash;10/2/2009&mdash;2D Grid Flow Vectors drawn on same layer as Color Filled Contours<br />
* 1473 9/30/2009&ndash;10/2/2009&mdash;NSS calculation possible error<br />
* 1271 8/6/2009&ndash;9/30/2009&mdash;WMS crashes when creating a filmloop of a partial solution<br />
* 1594 10/31/2009&ndash;11/4/2009&mdash;Vol 3, Ch4, Section 4.3.2, Step 2. Strange symbols appear in list box.<br />
* 1578 10/28/2009&ndash;11/4/2009&mdash;Multiple arcs should only have one attribute if connected<br />
<br />
=WMS 8.2 Bugfixes=<br />
==Intermediate Release WMS 8.2.6 &ndash; September 22, 2009==<br />
An update to WMS 8.2 has been posted on Aquaveo's web site. The best place to obtain the update is from the download link on Aquaveo's web site at [http://www.aquaveo.com/ http://www.aquaveo.com/]. The following known bugs have been fixed in this version:<br />
<br />
Bug Id Date Submitted-Updated&mdash;Summary<br />
* 170 10/31/2008&ndash;9/21/2009&mdash;Bug when opening a WMS project from spatial tutorials<br />
* 999 6/3/2009&ndash;9/21/2009&mdash;Error message occasionally pops up while moving through sediment flux or stream sediment flux dataset.<br />
* 898 5/5/2009&ndash;9/21/2009&mdash;WMS crashes when running Clean Up Model command on this project<br />
* 860 4/28/2009&ndash;9/21/2009&mdash;Problem reading TIFF image using File | Open command<br />
* 852 4/27/2009&ndash;9/21/2009&mdash;Upon completion of the Volume VI - Chapter 6 tutorial, Section 6.2, Step 13 WMS crashes.<br />
* 1391 9/8/2009&ndash;9/21/2009&mdash;GSSHA datasets don't match up with hydrographs<br />
* 360 12/23/2008&ndash;9/18/2009&mdash;Default DEM display point size<br />
* 464 1/19/2009&ndash;9/18/2009&mdash;Switching to Specified Values in Contour Options does not enable Value fields<br />
* 648 3/4/2009&ndash;9/18/2009&mdash;Remove reservoir display opts from the TIN drainage display tab<br />
* 283 12/6/2008&ndash;9/18/2009&mdash;Error message, Vol. V, Ch. 1, Section 1.2, step 24, "An unsupported operation was attempted."<br />
* 192 11/7/2008&ndash;9/18/2009&mdash;Bug when specifying a bias when creating a 2D grid<br />
* 171 10/31/2008&ndash;9/18/2009&mdash;Tc value not updating in ModClark tutorial<br />
* 105 10/9/2008&ndash;9/17/2009&mdash;DrawBuffer_enum GetDrawBuffer () Assertion<br />
* 100 10/7/2008&ndash;9/17/2009&mdash;WMS exports the canvas window background when saving a *.kmz film loop<br />
* 989 6/1/2009&ndash;9/17/2009&mdash;WMS crashes when running DEM->Stream Arcs command<br />
* 1199 7/20/2009&ndash;9/17/2009&mdash;WMS does not write out projection file when exporting grids from GSSHA output datasets<br />
* 277 12/4/2008&ndash;9/17/2009&mdash;Changes to GSSHA .cmt file requested by Chuck<br />
* 1270 8/6/2009&ndash;9/11/2009&mdash;Embankment arcs should not extend into inactive GSSHA cells or else GSSHA won't run<br />
* 1275 8/10/2009&ndash;9/11/2009&mdash;WMS does not read in more than 5, or 6 files into the "Convert Grids" dialog at a time.<br />
* 1286 8/12/2009&ndash;9/11/2009&mdash;In job control dialog,contaminant name and location are lost when you add a new contaminant<br />
* 1340 8/24/2009&ndash;9/10/2009&mdash;GSSHA sample tutorial crashes WMS<br />
* 1341 8/24/2009&ndash;9/10/2009&mdash;GSSHA doesn't save *.dep and *.ghm file when you choose to save before running<br />
* 1343 8/24/2009&ndash;9/10/2009&mdash;Basin data not read from file<br />
* 1389 9/3/2009&ndash;9/9/2009&mdash;WMS crashes when conforming GSSHA embankment arc to grid if no grid is available<br />
* 1068 6/23/2009&ndash;9/2/2009&mdash;Hydrograph output toggle in GSSHA solution results window not used, misleading<br />
* 1204 7/21/2009&ndash;8/17/2009&mdash;WMS Crashes upon completion of Step 12, Section 4.2, in the Volume 6, Chapter 3 tutorial.<br />
* 1170 7/15/2009&ndash;8/17/2009&mdash;Problem with either GSSHA or WMS-reading a GSSHA solution file<br />
* 1215 7/23/2009&ndash;8/11/2009&mdash;A dialog reading "There was an error reading record 1 in the Green-Ampt Land Use Table" cannot be dismissed.<br />
* 1051 6/17/2009&ndash;8/10/2009&mdash;DEM Contours written to KMZ file, when DEM is turned off<br />
* 1173 7/15/2009&ndash;8/10/2009&mdash;WMS crashes upon clicking the 'Assign' buttton during step 12, section 1.4, of the Volume 5, Chapter 1 &ndash; HSPF tutorial.<br />
* 1240 7/30/2009&ndash;8/7/2009&mdash;Save File command in coverage overlay window should show default file types<br />
* 1241 7/30/2009&ndash;8/7/2009&mdash;WMS crashes when delineating a watershed before running TOPAZ<br />
* 1138 7/10/2009&ndash;8/6/2009&mdash;Volume 3, Chapter 2 &ndash; Floodplain Delineation, csdb.idx file not found when saving *.wms file at the end.<br />
* 1252 7/31/2009&ndash;8/6/2009&mdash;Bug when reading in rain gages from format precip macro<br />
* 1188 7/16/2009&ndash;8/6/2009&mdash;The attached WMS.ini file causes WMS to crash when loading DEMs<br />
* 1002 6/3/2009&ndash;7/16/2009&mdash;HEC-1 lag time/time of concentration data computed<br />
* 997 6/3/2009&ndash;7/15/2009&mdash;SSURGO Shape files Bug<br />
* 1000 6/3/2009&ndash;7/15/2009&mdash;WMS crashes during the creation of an animation using the sediment flux and stream sediment flux data sets.<br />
* 1141 7/10/2009&ndash;7/10/2009&mdash;Bug in assigning texture using Join SSURGO command.<br />
* 1143 7/10/2009&ndash;7/10/2009&mdash;In WMS dev, the ksat algorithm in the Join SSURGO data command occasionally returns "-1.#IND00"<br />
* 1144 7/10/2009&ndash;7/10/2009&mdash;Bug in Joining SSURGO data KSAT values in WMS dev<br />
* 1145 7/10/2009&ndash;7/10/2009&mdash;resistance equation in Join SSURGO dialog should be changed to "equivalent conductance equation"<br />
* 919 5/7/2009&ndash;7/10/2009&mdash;WMS disappears when running DEM->Stream Arcs command on this DEM<br />
* 1004 6/4/2009&ndash;7/9/2009&mdash;GSSHA simulations including erosion and sediment only read in the first sediment from the .sed file into WMS.<br />
* 903 5/6/2009&ndash;7/9/2009&mdash;Tutorials, Volume V, Chapter 2, Section 2.6.2, Step 2.<br />
* 1066 6/22/2009&ndash;7/8/2009&mdash;CAD layers do not disable properly in the tree view<br />
* 1007 6/5/2009&ndash;7/6/2009&mdash;TerraServer generates an error upon completion of step 23, Section 2.7.2, of the Chapter 2, Volume 1 Tutorial.<br />
* 899 5/5/2009&ndash;7/1/2009&mdash;GSSHA hyetograph ranamed as "Hyetograph" in XY Series Editor<br />
* 909 5/6/2009&ndash;6/30/2009&mdash;spreadsheet entries in GSSHA Solution Analysis dialog dimmed for no good reason<br />
* 1083 6/26/2009&ndash;6/30/2009&mdash;GSSHA calibration mode results different when using different units<br />
* 901 5/6/2009&ndash;6/30/2009&mdash;Tutorials, Volume IV, Chapter 3, Section 3.5 - After finishing the tutorial WMS crashes while saving finished project file.<br />
* 906 5/6/2009&ndash;6/29/2009&mdash;GSSHA Outlfow hydrograph not matching stream flow graph in solution results window<br />
<br />
==Intermediate Release WMS 8.2.2 &ndash; June 23, 2009==<br />
An update to WMS 8.2 has been posted on Aquaveo's web site. The best place to obtain the update is from the download link on Aquaveo's web site at [http://www.aquaveo.com/ http://www.aquaveo.com/]. The following known bugs have been fixed in this version:<br />
<br />
Bug Id Date Submitted&mdash;Updated-Summary<br />
* 897 5/5/2009&ndash;6/15/2009&mdash;WMS crashes when deleting the GSSHA cumulative rainfall dataset from the project explorer<br />
* 902 5/6/2009&ndash;6/15/2009&mdash;MODRAT "Use Input Hydrograph" option doesn't work<br />
* 905 5/6/2009&ndash;6/12/2009&mdash;XY Series editor "show dates" option prompts for a reference date but doesn't use it<br />
* 908 5/6/2009&ndash;6/12/2009&mdash;WMS does not read the attached xy series file (even though it was created in WMS)<br />
* 924 5/11/2009&ndash;6/5/2009&mdash;WMS crashes when running model checker on the attached GSSHA model<br />
* 988 6/1/2009&ndash;6/5/2009&mdash;WMS crashes when importing these TOPAZ files<br />
* 952 5/18/2009&ndash;6/5/2009&mdash;WMS Crashes on Check Model command in GSSHA<br />
* 781 4/2/2009&ndash;6/5/2009&mdash;SURRGO Soils data not transferred to GSSHA index maps<br />
* 782 4/2/2009&ndash;6/5/2009&mdash;No units shown for joined SURRGO soils data<br />
* 896 5/5/2009&ndash;6/4/2009&mdash;infinite loop while trying to read prj file instead group project file<br />
* 998 6/3/2009&ndash;6/4/2009vRead project file crash<br />
* 808 4/10/2009&ndash;5/15/2009&mdash;GSSHA stops running after running the second hour of the attached 5-hour simulation<br />
* 849 4/24/2009&ndash;5/15/2009&mdash;WMS crashes when importing this GIS (.geo) file<br />
* 853 4/27/2009&ndash;5/14/2009&mdash;Problem reading or writing scalar data to or from 2D scattered data<br />
* 926 5/11/2009&ndash;5/13/2009&mdash;GSSHA crashes when trying to run the attached model<br />
* 775 4/2/2009&ndash;5/7/2009&mdash;GSSHA crashes when using lakes<br />
* 786 4/2/2009&ndash;5/6/2009&mdash;Prompt needed for users to switch model units from feet to meters if using GSSHA<br />
* 586 2/14/2009&ndash;5/6/2009&mdash;Title in the WMS 8.2 title bar needs to be cleaned up.<br />
* 309 12/11/2008&ndash;5/5/2009&mdash;GSSHA does not recognize wetlands (*.wlm) file when spaces are in the file path<br />
<br />
==Intermediate Release WMS 8.2.1 &ndash; May 4, 2009==<br />
An update to WMS 8.2 has been posted on Aquaveo's web site. The best place to obtain the update is from the download link on Aquaveo's web site at [http://www.aquaveo.com/ http://www.aquaveo.com/]. The following known bugs have been fixed in this version:<br />
<br />
Bug Id Date Submitted&mdash;Updated-Summary<br />
<br />
* 659 3/5/2009&ndash;5/1/2009&mdash;WMS crashes when running MODRAT with no file prefix<br />
* 698 3/16/2009&ndash;5/1/2009&mdash;MODRAT Error<br />
* 783 4/2/2009&ndash;5/1/2009&mdash;No feedback for MODRAT run &ndash; Randall Greenwood<br />
* 511 1/29/2009&ndash;5/1/2009&mdash;Deleted 1D-Hyd Cross-Section Arcs reappear when reopening WMS project<br />
* 200 11/10/2008&ndash;4/30/2009&mdash;WMS crashes when opening CAD file with image file (*.sid) loaded<br />
* 758 3/27/2009&ndash;4/29/2009&mdash;Better reading and processing needed for NLCD 2001 Land Use grids<br />
* 700 3/16/2009&ndash;4/28/2009&mdash;Problem with tying stream arcs to sub-basins<br />
* 633 2/27/2009&ndash;4/28/2009&mdash;WMS RASTER import Crash<br />
* 757 3/27/2009&ndash;4/28/2009&mdash;WMS crashes when importing an ArcGrid with ArcObjects enabled in WMS 8.1<br />
* 778 4/2/2009&ndash;4/27/2009&mdash;Selecting Redistribute Vertices command without a selected arc launches an unnecessary dialog<br />
* 671 3/10/2009&ndash;4/27/2009&mdash;2-D Scatter Dataset Not Created<br />
* 665 3/6/2009&ndash;4/27/2009&mdash;Problem with saving/reading datasets associated with TINs<br />
* 662 3/5/2009&ndash;4/23/2009&mdash;WMS 8.2 Crashes upon completion of Section 3.5, step 6 of the Volume IV, Chapter 3 tutorial.<br />
* 667 3/7/2009&ndash;4/23/2009&mdash;WMS 8.1 Disappears upon completion of step 9 of GSSHA Tutorials:3 Fixing Digital Dams<br />
* 436 1/13/2009&ndash;4/23/2009&mdash;WMS loses basin data reading in a project file<br />
* 432 1/13/2009&ndash;4/22/2009&mdash;Problems with coverage att tables when closing WMS<br />
* 702 3/16/2009&ndash;4/21/2009&mdash;Need input value length restrictions on MODRAT input values in Edit Parameters window<br />
* 660 3/5/2009&ndash;4/21/2009&mdash;WMS crashes when using Flood menu options with nothing loaded<br />
* 741 3/24/2009&ndash;4/20/2009&mdash;WMS 8.2 Crashes when reading in NSSmap_FL.map, step 2, section 7.4.1 of the Volume II, Chapter 7 tutorial. NSS Interface.<br />
* 717 3/18/2009&ndash;4/20/2009&mdash;Compute Basin Data Crash!<br />
* 110 10/9/2008&ndash;4/20/2009&mdash;Crash when going to global mapper dialog<br />
* 817 4/16/2009&ndash;4/16/2009&mdash;Opening this project file causes WMS to crash<br />
* 608 2/24/2009&ndash;4/14/2009&mdash;File path to LA County soils table needs to be updated in WMS 8.2 Preferences<br />
* 780 4/2/2009&ndash;4/14/2009&mdash;Problem when using hyetograph precip option with GSSHA<br />
* 764 3/30/2009&ndash;4/13/2009&mdash;Can't create filmloops<br />
* 610 2/25/2009&ndash;4/13/2009&mdash;WMS disppears when trying to open an HY-8 culvert project<br />
* 755 3/26/2009&ndash;4/13/2009&mdash;Problem converting coordinates when you download shapefiles with defined projection from web services<br />
* 784 4/2/2009&ndash;4/10/2009&mdash;Misleading text on button in GSSHA Maps dialog<br />
* 295 12/9/2008&ndash;4/10/2009&mdash;GSSHA 4.0 crashes in Tutorial 6.4<br />
* 704 3/16/2009&ndash;4/10/2009&mdash;WMS 8.2 Web services dialog does not appear if not connected to the internet<br />
* 703 3/16/2009&ndash;4/10/2009&mdash;Web service problem when downloading Louisiana data (and possibly data from other states)<br />
* 751 3/25/2009&ndash;4/10/2009&mdash;The option to convert two shapefiles of the same type to a single coverage is not available<br />
* 701 3/16/2009&ndash;4/7/2009&mdash;Problem with default Z units when converting NED DEM<br />
* 746 3/25/2009&ndash;4/7/2009&mdash;Problem converting coordinates with shapefile<br />
* 747 3/25/2009&ndash;4/7/2009&mdash;Problem converting coordinates with land use shapefile (no projection file)<br />
* 748 3/25/2009&ndash;4/7/2009&mdash;Problem with vertical units when reading a DEM file<br />
* 749 3/25/2009&ndash;4/6/2009&mdash;Problem setting and converting coordinates on a shapefile with a projection file<br />
* 750 3/25/2009&ndash;4/6/2009&mdash;Problem converting shapefiles with projections in the hydrologic modeling wizard<br />
* 692 3/12/2009&ndash;4/3/2009&mdash;Embankment Arc Profile Editor does not seem to update the endpoint elevations in the GSSHA-7 Tutorial.<br />
* 189 11/7/2008&ndash;4/3/2009&mdash;WMS crashes in Grid Ooptions dialog (display x-y axis)<br />
* 697 3/16/2009&ndash;4/2/2009&mdash;DEMEdit tutorial files not included in WMS 8.1 installation<br />
* 616 2/25/2009&ndash;4/2/2009&mdash;WMS window goes blank when deleting drainage data with Select Feature Objects tool<br />
* 448 1/15/2009&ndash;4/2/2009&mdash;Crash when opening *.map file on a TIN in WMS 8.1 and 8.2<br />
* 522 2/3/2009&ndash;4/1/2009&mdash;Color fill contours not displayed for flood delineation<br />
* 538 2/6/2009&ndash;3/31/2009&mdash;Delineate Basins Wizard stream display threshold units<br />
* 337 12/18/2008&ndash;3/31/2009&mdash;Update Delineate Basins Wizard<br />
* 507 1/29/2009&ndash;3/30/2009&mdash;Duplicate arcs being generated from 1D-Hyd Cross-Section coverage when exporting GIS file<br />
* 477 1/21/2009&ndash;3/27/2009&mdash;River Hydraulic Schematic should be deleted when XSection and Centerline coverages get deleted<br />
* 499 1/28/2009&ndash;3/27/2009&mdash;WMS not responding when accessing NED Data through Web Services if WebServices.exe is missing<br />
* 508 1/29/2009&ndash;3/26/2009&mdash;Allow the option to download and read SSURGO data files for multiple SSURGO soil shapefiles<br />
* 510 1/29/2009&ndash;3/25/2009&mdash;Allow users to select more than one soil type and/or land use shapefile for the Define Land Use and Soil Data step in the HMW<br />
* 611 2/25/2009&ndash;3/23/2009&mdash;Web Services reports two errors when trying to save to an unexisting directory<br />
* 547 2/6/2009&ndash;3/23/2009&mdash;Verify GSSHA embankment arc conceptualization<br />
* 655 3/4/2009&ndash;3/19/2009&mdash;Land use and soil shapefile options not saved<br />
* 656 3/4/2009&ndash;3/19/2009&mdash;Selected web catalog web service options (land use and soil) are not saved in the hydrologic modeling wizard<br />
* 657 3/4/2009&ndash;3/19/2009&mdash;Terraserver web service resolutions are not used in the hydrologic modeling wizard<br />
* 474 1/21/2009&ndash;3/19/2009&mdash;Save prompt is supressed after saving as .dwg, .dxf, .shp, or any other file type<br />
* 658 3/4/2009&ndash;3/18/2009&mdash;Better handling of web service file names in the hydrologic modeling wizard<br />
* 634 2/27/2009&ndash;3/18/2009&mdash;CE-QUAL-W2 bathymetry bug<br />
* 303 12/10/2008&ndash;3/16/2009&mdash;Problem color filling contours<br />
* 497 1/27/2009&ndash;3/12/2009&mdash;WMS crashes when re-entering the HY-8 Culvert dialog<br />
* 614 2/25/2009&ndash;3/10/2009&mdash;WMS crashes when deleting a MODRAT diversion from a basin in WMS 8.1 and 8.2<br />
* 532 2/5/2009&ndash;3/10/2009&mdash;Bug when setting bank arc attribute<br />
* 641 2/27/2009&ndash;3/10/2009&mdash;Change default output in MODRAT Edit Parameters window<br />
* 654 3/4/2009&ndash;3/10/2009&mdash;Problem creating uniform index map in WMS 8.1<br />
* 650 3/4/2009&ndash;3/9/2009&mdash;DEM properties dialog<br />
* 584 2/13/2009&ndash;3/9/2009&mdash;Next Hydrograph Station-> button in HEC-1 Parameters dialog causes WMS to crash<br />
* 615 2/25/2009&ndash;3/9/2009&mdash;Add Retrieve Diversion command to right click menu in MODRAT<br />
* 653 3/4/2009&ndash;3/9/2009&mdash;TR-20 CN entry<br />
<br />
==[[WMS:What's new in WMS version 8.2|Release WMS 8.2.0]] &ndash; April 16, 2009==<br />
WMS 8.2 has been released. This is the final release version. Bug fixes to WMS 8.2 will be posted in future updates.<br />
<br />
==Intermediate release WMS 8.2.1 (beta) &ndash; March 9, 2009==<br />
An update to WMS 8.2 Beta has been posted to the xmswiki.com web site. The main purpose of this update was to fix a problem with the WMS 8.2 beta version not working with WMS 8.1 hardware locks. The best place to obtain the update is from [[WMS:WMS Downloads|the WMS 8.2 beta download page on the xmswiki.com web site]]. The following known bugs have been fixed in this version:<br />
<br />
Bug Id-Date Submitted-Updated-Summary<br />
* None 12/6/2009&ndash;12/6/2009&mdash;Fixed a problem with WMS 8.2 not working with WMS 8.1 hardware locks<br />
* 272 12/2/2008&ndash;3/6/2009&mdash;WMS writes out MODRAT basin numbers incorrectly<br />
* 465 1/19/2009&ndash;3/6/2009&mdash;WMS crashes when color fill contouring one contour<br />
* 649 3/4/2009&ndash;3/5/2009&mdash;WMS crashes when converted TIN to DEM<br />
* 548 2/6/2009&ndash;3/5/2009&mdash;Crash converting TIN to DEM without triangulating TIN<br />
* 645 3/3/2009&ndash;3/5/2009&mdash;WMS 8.1 Bug &ndash; Saving as *.sup or *.shp file<br />
<br />
=WMS 8.1 Bugfixes=<br />
==Intermediate release WMS 8.1.6 &ndash; March 4, 2009==<br />
An update to WMS 8.1 has been posted to Aquaveo's web site. The best place to obtain the update is from the download link on Aquaveo's web site at [http://www.aquaveo.com/ http://www.aquaveo.com/]. The following known bugs have been fixed in this version:<br />
<br />
Bug Id Date Submitted&mdash;Updated-Summary<br />
* 737 12/8/2008&ndash;3/4/2009&mdash;Base Flow Parameters in HEC-1 not written properly to HEC-HMS<br />
* 341 12/19/2008&ndash;3/2/2009&mdash;TIN triangulation and display bugs in WMS 8.1 and WMS 8.2<br />
* 435 1/13/2009&ndash;2/26/2009&mdash;SWMM hydraulic schematic data not written to *.wpr or *.wms (xmdf) project files<br />
* 498 1/27/2009&ndash;2/26/2009&mdash;Crash when reading project file into WMS 8.2<br />
* 431 1/13/2009&ndash;2/25/2009&mdash;SMPDBK parameters not saved to *.wms (xmdf) project file<br />
* 282 12/5/2008&ndash;2/23/2009&mdash;Convert DEM to TIN crash<br />
* 147 10/27/2008&ndash;2/19/2009&mdash;"DEM Contours, Color Filled Polygons, and DEM Streams share same draw space in WMS 8.1"<br />
* 761 12/8/2008&ndash;2/19/2009&mdash;Reading the attached DEM files causes WMS to crash<br />
* 294 12/9/2008&ndash;2/18/2009&mdash;Film Loop issues in Tutorial 6.3 and 6.4<br />
* 762 12/8/2008&ndash;2/18/2009&mdash;WMS has problems reading the attached BIL files<br />
* 553 2/9/2009&ndash;2/17/2009&mdash;Flood depth coverage doesn't accept user defined depth intervals<br />
* 234 11/18/2008&ndash;2/16/2009&mdash;"WMS disappears when opening the project file at the beginning of the Volume VI, Chapter 4 tutorial."<br />
* 261 11/26/2008&ndash;2/16/2009&mdash;"WMS 8.1 disappears upon completion of step 10, of the 5th tutorial on the gsshawiki."<br />
* 262 11/26/2008&ndash;2/16/2009&mdash;WMS 8.1 Disappears upon completion of step 3 of Tutorials:7 Break-point Cross Sections on the GSSHA wiki.<br />
* 308 12/11/2008&ndash;2/16/2009&mdash;Error Displaying Shapefiles<br />
* 336 12/17/2008&ndash;2/16/2009&mdash;"WMS 8.2 Vanishes upon completion of step 3, section 2.3.6, of the Volume 2, Chapter 2 tutorial (Editing DEMs)."<br />
* 111 10/11/2008&ndash;2/12/2009&mdash;"WMS kills itself upon completion of the step 2, section 2.6.1, of tutorial vol 3, chapter 2."<br />
* 176 11/4/2008&ndash;2/12/2009&mdash;"On the WMS Testing machine WMS 8.1 disappears upon completion of tutorial Volume V, Chapter 2, Section 2.5.2, Step 1"<br />
* 293 12/9/2008&ndash;2/12/2009&mdash;"WMS 8.1 crashes upon completion of step 21, section 2.4.2, in the MODRAT Chapter 2, MODRAT GIS Tutorial"<br />
* 344 12/19/2008&ndash;2/12/2009&mdash;"XMDF (*.wms) file does not load (or possibly save) multiple datasets for 2D Grid, or single dataset for 2D Scatter"<br />
* 874 12/8/2008&ndash;2/11/2009&mdash;"Tutorials, Volume I, Chapter 5, Section 5.8.3.2, Step 7. Crash"<br />
* 875 12/8/2008&ndash;2/11/2009&mdash;"Tutorials, Volume I, Chapter 6, Section 6.2.4, Step 10. WMS Kills itself upon completion of this step."<br />
* 430 1/13/2009&ndash;2/10/2009&mdash;TIN data and xmdf project file<br />
* 437 12/8/2008&ndash;2/10/2009&mdash;Display Order andy nowak<br />
* 659 12/8/2008&ndash;2/10/2009&mdash;Orange County testing results<br />
* 734 12/8/2008&ndash;2/10/2009&mdash;Drawing order bug with drawing tools in 8.0 and 8.1<br />
* 746 12/8/2008&ndash;2/10/2009&mdash;The Shuffle (display order) tools for drawing objects do not work<br />
* 552 2/9/2009&ndash;2/9/2009&mdash;MODRAT 2.0 output (.out) problems<br />
* 559 2/9/2009&ndash;2/9/2009&mdash;MODRAT 2.0 does not run when using input hydrograph files<br />
* 545 2/6/2009&ndash;2/6/2009&mdash;Hydraulic structures entered at GSSHA nodes not saved<br />
* 531 2/5/2009&ndash;2/5/2009&mdash;GSSHA retention depth option not working<br />
* 527 2/4/2009&ndash;2/4/2009&mdash;Problems with the soil file running MODRAT 1.0<br />
* 310 12/11/2008&ndash;1/30/2009&mdash;Change the radio buttons in the Watershed Data step of the hydrologic modeling wizard from radio buttons to toggle boxes<br />
* 446 1/14/2009&ndash;1/30/2009&mdash;Problem saving wms.ini file from the hydrologic modeling wizard<br />
* 340 12/18/2008&ndash;1/28/2009&mdash;WMS will not open gdm files with old coord sys<br />
* 496 1/27/2009&ndash;1/27/2009&mdash;Crash deleting a GSSHA coverage<br />
* 429 1/13/2009&ndash;1/26/2009&mdash;Reading in options set in the HEC-HMS Meteorologic Parameters<br />
* 441 1/13/2009&ndash;1/26/2009&mdash;Extra default (elev) data set with ModClark model and *.wms (xmdf) project file<br />
* 493 1/26/2009&ndash;1/26/2009&mdash;Cropping collars on *.tif images not working properly<br />
* 296 12/9/2008&ndash;1/22/2009&mdash;WMS crashes when creating soil type coverage from the Hydrologic Modeling Wizard<br />
* 440 1/13/2009&ndash;1/22/2009&mdash;HEC-HMS ModClark transform option not saved with *.wpr or *.wms (xmdf) project files<br />
* 483 1/22/2009&ndash;1/22/2009&mdash;Hydrologic Modeling Wizard skips around<br />
* 258 11/25/2008&ndash;1/19/2009&mdash;We don't read 2D grid datasets when saving/reading the grid as an XMDF file-see description<br />
* 371 12/8/2008&ndash;1/19/2009&mdash;Help file not working for some help buttons<br />
* 743 12/8/2008&ndash;1/19/2009&mdash;Save GSSHA Project File resets display options<br />
* 183 11/6/2008&ndash;1/16/2009&mdash;WMS crash in Grid Options dialog<br />
* 184 11/6/2008&ndash;1/16/2009&mdash;WMS crashes in Grid Options dialog (Displaying Grid Points)<br />
* 359 12/23/2008&ndash;1/16/2009&mdash;Adverse slopes displayed on all coverages that support stream arcs<br />
* 416 1/9/2009&ndash;1/16/2009&mdash;Crash when creating an index map before initializing GSSHA<br />
* 428 1/13/2009&ndash;1/16/2009&mdash;WMS displays multiple hydrographs in the same window with the same color<br />
* 278 12/4/2008&ndash;1/15/2009&mdash;Using radar rainfall data for long-term gridded simulation<br />
* 241 11/20/2008&ndash;1/9/2009&mdash;WMS crashes (disappears) when using select feature line branch tool<br />
* 228 11/14/2008&ndash;1/8/2009&mdash;WMS 8.1 crashes without warning when snapping the upstream nodes of two streams together<br />
* 155 10/28/2008&ndash;1/6/2009&mdash;Fill below and Fill above options are backwards in WMS 8.1<br />
* 233 11/18/2008&ndash;1/2/2009&mdash;"WMS 8.1 Disappears upon completion of the last step of section 2.13.1 of the Volume VI, Chapter 2 tutorial."<br />
* 112 10/13/2008&ndash;12/30/2008&mdash;"Extra edit field for ""Round culverts"" in GSSHA"<br />
* 142 10/24/2008&ndash;12/18/2008&mdash;Problem displaying filmloops<br />
* 242 11/20/2008&ndash;12/18/2008&mdash;WMS crashes in Cross-Section Attributes dialog<br />
* 217 11/12/2008&ndash;12/17/2008&mdash;Add tmcontours.dwg and trailmountain.dem to the Tins directory of tutorials for WMS 8.2<br />
* 229 11/14/2008&ndash;12/17/2008&mdash;Add the lc.wpr file on Chris' computer and all its associated files to the HSPF tutorial directory and delete littlecotton.wpr<br />
* 321 12/15/2008&ndash;12/17/2008&mdash;Displaying properties of selections in the Properties Window<br />
* 322 12/15/2008&ndash;12/17/2008&mdash;Start time for link/node datasets in GSSHA models with precip gages not correct<br />
* 181 11/4/2008&ndash;12/16/2008&mdash;We need a default max conveyance depth value for GSSHA cross section channels in WMS 9.0<br />
* 317 12/12/2008&ndash;12/16/2008&mdash;Unitialized memory crash<br />
* 233 12/8/2008&ndash;12/15/2008&mdash;Crash when updating contours<br />
* 175 11/4/2008&ndash;12/12/2008&mdash;WMS Crashes after confirming the overwrite of a storm drain file.<br />
* 191 11/7/2008&ndash;12/12/2008&mdash;WMS crashes when viewing wetland cells in 2D Grid Display Options<br />
* 269 12/2/2008&ndash;12/12/2008&mdash;"Users should set horizontal and vertical units to meters at the beggining of the Volume 5, Chapter 1, HSPF Tutorial."<br />
* 274 12/3/2008&ndash;12/12/2008&mdash;WMS crashes when trying to assign detention basin parameters<br />
* 195 11/10/2008&ndash;12/11/2008&mdash;Help About Window needs to be updated<br />
* 161 10/29/2008&ndash;12/10/2008&mdash;WMS crashes at the end of the CE-QUAL-W2 Tutorial in WMS 8.1<br />
* 230 11/17/2008&ndash;12/10/2008&mdash;Bug in WMS 8.2 when right-clicking on a spreadsheet cell and selecting another cell<br />
* 213 11/12/2008&ndash;12/9/2008&mdash;"The transform command is in the TIN menu of the data module, but is not in the right-click menu for a TIN (8.1 and 8.2)"<br />
* 156 10/28/2008&ndash;12/8/2008&mdash;Measure tool disappears if snapped to a vertex or node in WMS 8.1<br />
* 232 11/17/2008&ndash;12/8/2008&mdash;Measure tool cannot trace arcs<br />
* 289 12/8/2008&ndash;12/8/2008&mdash;DEM color-filled contours with flow distance contours toggled on causes crash<br />
* 290 12/8/2008&ndash;12/8/2008&mdash;Basin labels displayed with excess space between parameters<br />
* 834 12/8/2008&ndash;12/8/2008&mdash;GSSHA Bug List from tutorials<br />
<br />
==Intermediate release WMS 8.1.4 &ndash; December 8, 2008==<br />
An update to WMS 8.1 has been posted to Aquaveo's web site. The best place to obtain the update is from the download link on Aquaveo's web site at [http://www.aquaveo.com/ http://www.aquaveo.com/]. The following known bugs have been fixed in this version:<br />
<br />
Bug Id Date Submitted&mdash;Updated-Summary<br />
* 270 12/2/2008&ndash;12/4/2008&mdash;Delineate Crash<br />
* 791 11/4/2008&ndash;12/4/2008&mdash;The Display Order options on the Display Options window don't work<br />
* 134 10/23/2008&ndash;12/3/2008&mdash;Define Land Use and Soil Data step in Wizard not working with GSSHA Model Coverage in 9.0<br />
* 273 12/2/2008&ndash;12/3/2008&mdash;File IO problem when assigning reservoirs to MODRAT diversions<br />
* 102 10/7/2008&ndash;12/2/2008&mdash;WMS crashes when color fill contouring a 2D grid and then dragging the WMS window to my other monitor<br />
* 118 10/17/2008&ndash;12/2/2008&mdash;Problem reading DEMs<br />
* 115 10/16/2008&ndash;12/2/2008&mdash;Contouring issue &ndash; all contour appear the same color (red)<br />
* 131 10/22/2008&ndash;12/2/2008&mdash;Saving shapefile *.prj files<br />
* 136 10/23/2008&ndash;12/1/2008&mdash;WMS 9.0 crashes when clicking "Compute Index Mapping Tables" in the Hydrologic Modeling Wizard<br />
* 4 7/9/2008&ndash;12/1/2008&mdash;Installation issues with copy protection and new demo password generation.<br />
* 194 11/7/2008&ndash;11/25/2008&mdash;change xmdf file extension from *.wpr to *.wms<br />
* 152 10/28/2008&ndash;11/20/2008&mdash;Computing rational method hydrographs triggers a bunch of graphics asserts in WMS 8.1<br />
* 174 11/4/2008&ndash;11/18/2008&mdash;WMS disappears in the HSPF tutorial (Vol V, Ch 1) when reading in littlecotton.wpr<br />
* 218 11/12/2008&ndash;11/17/2008&mdash;DEM display shifts when creating feature arcs<br />
* 877 11/4/2008&ndash;11/17/2008&mdash;WMS kills itself upon completion of Tutorial 2-2, section 2.2.3, step 7 or 8.<br />
* 38 8/7/2008&ndash;11/14/2008&mdash;Can't edit culvert parameters &ndash; Zack Young<br />
* 146 10/27/2008&ndash;11/14/2008&mdash;WMS 8.1 crashes when placing interior outlets<br />
* 135 10/23/2008&ndash;11/14/2008&mdash;When opening a GSSHA project in WMS 9.0, the wizard should set the current model to be GSSHA<br />
* 145 10/27/2008&ndash;11/14/2008&mdash;TIN display bug in WMS 8.1 &ndash; entire tin shifts when closing a feature arc<br />
* 150 10/28/2008&ndash;11/14/2008&mdash;WMS 8.1 crashes when adding subbasins and re-delineating after having computed a CN<br />
* 870 11/4/2008&ndash;11/14/2008&mdash;GSSHA Rain Gage File I/O Bug<br />
* 190 11/7/2008&ndash;11/13/2008&mdash;DEM contouring on screen is reversed (canyons are shown as ridges and ridges as canyons)<br />
* 224 11/13/2008&ndash;11/13/2008&mdash;Polygon and DEM point selection does not update correctly in graphics window<br />
* 182 11/6/2008&ndash;11/13/2008&mdash;Canceling out of TOPAZ Units dialog still writes out a TOPAZ elevation file<br />
* 123 10/21/2008&ndash;11/13/2008&mdash;Embankment Arc Profile Editor has several bugs (at least 9) in 9.0<br />
* 851 11/4/2008&ndash;11/13/2008&mdash;WMS Crashes when trying to create shapefiles from these coverages<br />
* 857 11/4/2008&ndash;11/13/2008&mdash;Embankment dialog does not change arc elevations when creating a vertical curve<br />
* 692 11/4/2008&ndash;11/12/2008&mdash;HMS | Compute Grid Parameters does not seem to work for computing SMA grid parameters<br />
* 196 11/10/2008&ndash;11/10/2008&mdash;Cannot define GSSHA link break nodes with erodible cross section stream arcs<br />
<br />
==Intermediate release WMS 8.1.3 &ndash; November 4, 2008==<br />
An update to WMS 8.1 has been posted to Aquaveo's web site. The best place to obtain the update is from the download link on Aquaveo's web site at [http://www.aquaveo.com/ http://www.aquaveo.com/]. The following known bugs have been fixed in this version:<br />
<br />
Bug Id Date Submitted&mdash;Updated-Summary<br />
* 173 10/31/2008&ndash;11/4/2008&mdash;WMS 8.1 Crashes upon completion of step 20, section 4.5.1 of the Volume II, Chapter 4 Tutorial. (HEC-HMS Interface)<br />
* 144 10/24/2008&ndash;10/31/2008&mdash;WMS 8.1 soil legend is squished<br />
* 167 10/30/2008&ndash;10/30/2008&mdash;Crash saving coordinate system metadata with DEM<br />
* 113 10/14/2008&ndash;10/23/2008&mdash;WMS disappears upon double clicking on the flood.wpr file in the "open" file dialog.<br />
* 133 10/23/2008&ndash;10/23/2008&mdash;When moving basin labels the heads of the arrows are quite large on my computer (The WMS testing machine).<br />
* 114 10/14/2008&ndash;10/23/2008&mdash;Upon Opening the run1.wpr file in Volume 3, Chapter 3 Tutorial WMS Crashes.<br />
* 637 10/31/2008&ndash;10/31/2008&mdash;Error upon saving file from the Volume 1 Chapter 3 Tutorial.<br />
* 876 10/30/2008&ndash;10/30/2008&mdash;WMS kills itself upon completion of Tutorial 2-1, section 1.3.5, step 7.<br />
* 345 10/30/2008&ndash;10/30/2008&mdash;Observation coverage does nothing<br />
* 860 10/30/2008&ndash;10/30/2008&mdash;Problems editing/saving/writing vertical curve weir data from a hydraulic structure point<br />
* 837 10/29/2008&ndash;10/29/2008&mdash;CE-QUAL-W2 issues<br />
* 283 10/29/2008&ndash;10/29/2008&mdash;Georeferencing is wrong for images saved with collar cropped<br />
* 816 10/28/2008&ndash;10/28/2008&mdash;WMS 8.1 Freezes in the Tc Wizard when rainfall depth is not entered.<br />
* 817 10/28/2008&ndash;10/28/2008&mdash;Hydrographs not visible near end of MODRAT-3 GIS Tutorial.<br />
* 829 10/28/2008&ndash;10/28/2008&mdash;WMS 8.1 gives a lot of asserts when removing flat triangles on TINs<br />
* 315 10/28/2008&ndash;10/28/2008&mdash;Saving Basin Only Projects<br />
* 359 10/28/2008&ndash;10/28/2008&mdash;WMS can't find HSPF LT executable<br />
* 855 10/28/2008&ndash;10/28/2008&mdash;Problem with clearing selections when selecting an item in the project explorer<br />
* 826 10/27/2008&ndash;10/27/2008&mdash;Bug in setting min and max contour intervals for Cumulative Rainfall Data<br />
* 868 10/27/2008&ndash;10/27/2008&mdash;Copy and paste error within WMS spreadsheets when commas are used<br />
* 849 10/27/2008&ndash;10/27/2008&mdash;Crash after importing TIN file (RELEASE VERSION ONLY)<br />
* 858 10/24/2008&ndash;10/24/2008&mdash;Swap edges tool is MESSED UP<br />
* 383 10/24/2008&ndash;10/24/2008&mdash;Cross Section computational stations remain at 0.0 when extracting Cross sections for SMPDBK<br />
* 862 10/24/2008&ndash;10/24/2008&mdash;Interpolation method other than IDW causes crash<br />
* 832 10/23/2008&ndash;10/23/2008&mdash;TR-55 spreadsheet labels are always dimmed<br />
* 836 10/23/2008&ndash;10/23/2008&mdash;Can't cancel out of contour options if min contour value is greater than max value<br />
* 838 10/23/2008&ndash;10/23/2008&mdash;Bug In CE-QUAL-W2 Tutorial block: Measure tool in segments dialog resets length to zero<br />
* 830 10/23/2008&ndash;10/23/2008&mdash;Building polygons around streams assigns polygons the wrong type<br />
* 137 10/23/2008&ndash;10/23/2008&mdash;Right-click option in spreadsheets<br />
* 145 10/22/2008&ndash;10/22/2008&mdash;TR-20 Reservoir Data<br />
* 77 10/22/2008&ndash;10/22/2008&mdash;Displaying arc after reading in TIN<br />
* 764 10/21/2008&ndash;10/21/2008&mdash;Vista Problem: wmsnff.exe crashes in Windows Vista<br />
* 871 10/21/2008&ndash;10/21/2008&mdash;Can we make the model wrapper resizable?<br />
* 872 10/21/2008&ndash;10/21/2008&mdash;Outflow Sedograph Plot Window bug<br />
* 869 10/20/2008&ndash;10/20/2008&mdash;GSSHA Soil Erosion dialog needs units<br />
* 562 10/20/2008&ndash;10/20/2008&mdash;Error appears when saving HEC-1 file with average precip defined<br />
* 870 10/20/2008&ndash;10/20/2008&mdash;GSSHA Rain Gage File I/O Bug<br />
* 854 10/17/2008&ndash;10/17/2008&mdash;GSSHA Multi-gage interpolation methods remain dimmed after importing a Multi-gage file<br />
* 807 10/17/2008&ndash;10/17/2008&mdash;Error writing curve number dataset when writing HEC-HMS file<br />
* 821 10/16/2008&ndash;10/16/2008&mdash;Static Text String for file path in Convert Grids dialog is too short<br />
* 840 10/16/2008&ndash;10/16/2008&mdash;Units for Wetland polygons do not match units reported on the gsshawiki<br />
* 811 10/16/2008&ndash;10/16/2008&mdash;Map Drawing Fonts will crash if non-standard fonts used<br />
* 740 10/15/2008&ndash;10/15/2008&mdash;Hydrographs not shown in the Volume 2 - Chapter 4 (HEC-1) Tutorial<br />
* 172 10/15/2008&ndash;10/15/2008&mdash;Tree right click menus bug, with "Change module when tree selection changes" off<br />
* 206 10/15/2008&ndash;10/15/2008&mdash;DEM delineation and redistributing arcs<br />
* 822 10/15/2008&ndash;10/15/2008&mdash;Bug in Contour Options dialog<br />
* 772 10/14/2008&ndash;10/14/2008&mdash;Film loops do not work<br />
* 815 10/14/2008&ndash;10/14/2008&mdash;Map Attributes Dialog Crash<br />
* 825 10/14/2008&ndash;10/14/2008&mdash;Incremental Rainfall dataset shows the wrong dates and times in the properties window<br />
* 828 10/14/2008&ndash;10/14/2008&mdash;Bug when viewing values from Hydrograph Plots<br />
* 814 10/13/2008&ndash;10/13/2008&mdash;WMS crashes when double clicking on GSSHA embankment arc "low points"<br />
* 865 10/13/2008&ndash;10/13/2008&mdash;Problem reading HEC-RAS Solution, crash when reading WMS 8.1 project file into WMS 9.0<br />
* 820 10/13/2008&ndash;10/13/2008&mdash;Bugs in Volume 2, Tutorial 7 of GSSHA Training course<br />
* 873 10/13/2008&ndash;10/13/2008&mdash;Virtual Earth gives you errors<br />
* 824 10/10/2008&ndash;10/10/2008&mdash;Bug in Convert Grids dialog<br />
* 827 10/10/2008&ndash;10/10/2008&mdash;Error when Importing Grids for GSSHA : "Error Reading Scalar Binary File"<br />
* 859 10/10/2008&ndash;10/10/2008&mdash;Crash when selecting gssha hydraulic structures<br />
* 852 10/10/2008&ndash;10/10/2008&mdash;GSSHA bug: GW_INIT_MOISTURE card not needed, not recognized by GSSHA<br />
* 856 10/10/2008&ndash;10/10/2008&mdash;Web Services Dialog - Tutorials Vol II, Ch 1, Section 1.3.3<br />
* 846 10/9/2008&ndash;10/9/2008&mdash;Problem displaying adverse slopes in GSSHA coverage<br />
* 864 10/9/2008&ndash;10/9/2008&mdash;GSSHA Stochastic run dialog crashes after reading GSSHA project file<br />
* 351 10/6/2008&ndash;10/6/2008&mdash;Tutorial files for tutorial 3 (basic feature objects)<br />
* 354 10/3/2008&ndash;10/3/2008&mdash;Typo in new tutorials<br />
<br />
==Intermediate release WMS 8.1.1 &ndash; October 2, 2008==<br />
Note about this update: Because [http://water.usgs.gov/software/NFF/ NFF] has been replaced by NSS in WMS 8.1, you may need to uninstall NFF from your computer before installing the update to WMS 8.1. It may also be a good idea to install NSS on your computer, though this should not be necessary. After installing this update, if you have trouble running NSS in WMS 8.1, make sure your NSSv4.mdb database file in the WMS 8.1 directory exists and is not set to Read-Only. If you continue to have problems, download and install [http://water.usgs.gov/software/NSS/ NSS from this location].<br />
<br />
* The NFF (National Flood Frequency) database has been converted to the newer NSS (National Streamflow Statistics) database in WMS 8.1.<br />
* A problem running GSSHA in "batch" mode has been fixed.<br />
* A problem in web services with converting data to anything other than NAD 83 has been fixed.<br />
* "File Import Wizard &ndash; Step 1 of 2" Dialog freezes upon clicking next in the Vol 1 Ch 5 tutorial has been fixed.<br />
* Arc Selection Problem &ndash; Tutorials &ndash; Volume 1, Chapter 6, Section 6.2.3, step4 has been fixed.<br />
* Tutorials, Volume II, Chapter 1, Section 1.3, step 4 &ndash; mixed units in "Units" dialog has been fixed.<br />
* Terra Server creates an error in the Volume III, Chapter 1, Tutorial has been fixed.<br />
* Tutorials, Volume III, Chapter 3, Section 3.4.2, Step 6 &ndash; Z Scale Combo Box inactive has been fixed.<br />
* Penman Evapotranspiration method parameters not displaying in Mapping Tables (GSSHA) has been fixed.<br />
<br />
== Related Topics ==<br />
* [[WMS:What's new in WMS version 9.0|What's new in WMS 9.0]]<br />
* [[WMS:What's new in WMS version 8.4|What's new in WMS 8.4]]<br />
* [[WMS:What's new in WMS version 8.3|What's new in WMS 8.3]]<br />
* [[WMS:What's new in WMS version 8.2|What's new in WMS 8.2]]<br />
* [[WMS:What's_new_in_WMS_version_8.1|What's New in WMS 8.1]]<br />
* [[System Requirements|System Requirements]]<br />
* [[Graphics_Card_Troubleshooting|Graphics Card Troubleshooting]]<br />
<br />
<br />
{{Template:WMSMain}}<br />
[[Category:WMS General Information]]<br />
[[Category:Bugfixes|WMS]]<br />
[[Category:What's New]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:Boreholes&diff=119076GMS:Boreholes2017-02-03T22:17:44Z<p>Dharker: /* Stratigraphy */ Noted bottom of boreholes is considered no-flow zone</p>
<hr />
<div>{{Boreholes links}}<br />
The Borehole module of GMS can be used to visualize boreholes created from drilling logs or synthetic boreholes created manually and to construct three-dimensional [[GMS:Borehole Cross Sections|cross sections]] between boreholes. These cross sections show the soil stratigraphy between two boreholes.<br />
<br />
Borehole data can be [[GMS:Creating and Editing Boreholes|imported or created]] in GMS. The borehole module contains its own set of [[GMS:Borehole Tool Palette|tools]] and [[GMS:Borehole Commands|commands]] for manipulating borehole data as well as its own display options. Borehole data can be [[GMS:Converting Borehole Data|converted]] to other types of objects such as 2D Scatter Points, TINs, 3D Meshes. <br />
<br />
The module also allows using [[GMS:Borehole Hydrogeologic Units|hydrogeologic units (HGUs)]] to be defined on boreholes.<br />
<br />
The Borehole Module can be added to a [http://www.aquaveo.com/software/gms-pricing paid edition] of GMS.<br />
[[Category:Link to Store]]<br />
<br />
==Types of Borehole Data==<br />
A borehole can contain either stratigraphy data or sample data or both.<br />
<br />
===Stratigraphy===<br />
<br />
Stratigraphy data are used to represent soil layers that are encountered in a soil boring. The soil layers are represented using contacts and segments as shown below. A segment represents a soil layer and a contact is the interface between two segments. GMS assumes no-flow bedrock below the bottom of each borehole when generating the stratigraphy.<br />
[[Image:Holes1.png|thumb|none|350 px|Boreholes representing soil stratigraphy with contacts and segments]]<br />
<br />
===Sample Data===<br />
<br />
Sample data represent data obtained by continuous sampling along the length of the hole. Cone penetrometer data or down-hole geophysical data like permeability are examples of sample data. The figure below shows an example of sample data being displayed. Sample data are stored in datasets which can be displayed and manipulated in a similar fashion as other datasets in GMS. To display the sample data the display options for the Borehole data can be modified such that the ''Sample data'' Points and Data plots are checked as visible while the borehole edges are hidden in the ''Display Options'' dialog.<br />
[[Image:Sampledata1.png|thumb|none|400 px|Boreholes with sample data]]<br />
<br />
<br />
{{Navbox GMS}}<br />
[[Category:Boreholes]]<br />
[[Category:Stratigraphy]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:Boreholes&diff=119074GMS:Boreholes2017-02-03T22:13:18Z<p>Dharker: Noted synthetic boreholes as an option</p>
<hr />
<div>{{Boreholes links}}<br />
The Borehole module of GMS can be used to visualize boreholes created from drilling logs or synthetic boreholes created manually and to construct three-dimensional [[GMS:Borehole Cross Sections|cross sections]] between boreholes. These cross sections show the soil stratigraphy between two boreholes.<br />
<br />
Borehole data can be [[GMS:Creating and Editing Boreholes|imported or created]] in GMS. The borehole module contains its own set of [[GMS:Borehole Tool Palette|tools]] and [[GMS:Borehole Commands|commands]] for manipulating borehole data as well as its own display options. Borehole data can be [[GMS:Converting Borehole Data|converted]] to other types of objects such as 2D Scatter Points, TINs, 3D Meshes. <br />
<br />
The module also allows using [[GMS:Borehole Hydrogeologic Units|hydrogeologic units (HGUs)]] to be defined on boreholes.<br />
<br />
The Borehole Module can be added to a [http://www.aquaveo.com/software/gms-pricing paid edition] of GMS.<br />
[[Category:Link to Store]]<br />
<br />
==Types of Borehole Data==<br />
A borehole can contain either stratigraphy data or sample data or both.<br />
<br />
===Stratigraphy===<br />
<br />
Stratigraphy data are used to represent soil layers that are encountered in a soil boring. The soil layers are represented using contacts and segments as shown below. A segment represents a soil layer and a contact is the interface between two segments.<br />
[[Image:Holes1.png|thumb|none|350 px|Boreholes representing soil stratigraphy with contacts and segments]]<br />
<br />
===Sample Data===<br />
<br />
Sample data represent data obtained by continuous sampling along the length of the hole. Cone penetrometer data or down-hole geophysical data like permeability are examples of sample data. The figure below shows an example of sample data being displayed. Sample data are stored in datasets which can be displayed and manipulated in a similar fashion as other datasets in GMS. To display the sample data the display options for the Borehole data can be modified such that the ''Sample data'' Points and Data plots are checked as visible while the borehole edges are hidden in the ''Display Options'' dialog.<br />
[[Image:Sampledata1.png|thumb|none|400 px|Boreholes with sample data]]<br />
<br />
<br />
{{Navbox GMS}}<br />
[[Category:Boreholes]]<br />
[[Category:Stratigraphy]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:Map_to_MODFLOW&diff=119073GMS:Map to MODFLOW2017-02-03T20:44:00Z<p>Dharker: /* MODFLOW-USG */ Explained initialisms</p>
<hr />
<div>{{MODFLOW Links}}<br />
After the [[GMS:MODFLOW Conceptual Model Approach|conceptual model]] is constructed and a grid has been created, the final step in converting a conceptual model to a MODFLOW numerical model is to select the '''Map &rarr; MODFLOW''' command. However, before this command can be selected, MODFLOW must be initialized. MODFLOW is initialized as follows:<br />
<br />
#Switch to the 3D Grid module<br />
#Select the '''New Simulation''' command in the ''MODFLOW'' menu.<br />
#MODFLOW simulations are steady state by default. For a transient simulation, go to the [[GMS:Global Options/Basic Package|''Global Options/Basic Package'' Dialog]] and select the ''Transient'' option. Then set up the [[GMS:Stress Periods|stress periods]] to use in the simulation.<br />
#By default, the top layer is unconfined and the remaining layers are confined. To use a different set of layer types, go to the BCF/LPF/HUF Package dialog and select the appropriate layer type for each layer.<br />
<br />
Once MODFLOW is initialized, the '''Map &rarr; MODFLOW''' command becomes available. When the command is selected, the ''Map &rarr; MODFLOW Options'' dialog appears. Three options are available for converting the conceptual model: ''Active coverage only'', ''All applicable coverages'', and ''All visible coverages''. If the ''All applicable coverages'' option is chosen, all of the feature objects in all of the MODFLOW-related coverages in the active conceptual model are used. This option is typically selected when the conceptual model is first converted. If the ''Active coverage only'' or the ''All visible coverages'' option is selected, only a subset of the coverages are used to update the numerical model.<br />
<br />
==Temporal Discretization==<br />
See the [[GMS:Temporal_Discretization|Temporal Discretization]] page.<br />
<br />
==Multiple Values Per Cell==<br />
Because GMS processes each feature object separately, there will often be sources/sinks that were derived from two separate feature objects in the same cell. In fact, this is almost always the case in the cell that contains the endpoint of one arc and the beginning point of an adjacent arc. This is not an error. MODFLOW handles each of the boundary conditions in the cell simultaneously.<br />
<br />
==Specified Head Cells==<br />
Because the constant head condition forces the head in those cells to match whatever is specified, it is inappropriate to have other boundary conditions defined in the cells that are designated constant head. Therefore, GMS processes all of the specified head objects first. Afterwards, if there is another stress that should normally be assigned to a cell that has been previously assigned a constant head condition, the new stress is not assigned.<br />
<br />
==Changing Head Boundary==<br />
When mapping a specified head boundary to MODFLOW, GMS always uses the CHD package ([[GMS:CHD Package|Time Variant Specified Head package]]). In MF2K, a changing head boundary must be used in order to extract fluxes out of the MODFLOW output for the arcs in the map module. With MF2K, it is not possible to get a flux observation with normal Spec Head. It is assumed that most of the time the user would want to see the flux in/out of the boundary. If a cell contains two different arcs, the specified head is split in 2 pieces at cells where 2 specified head arcs meet. This is done for 2 reasons. First, the CHD package will combine the CHD boundary conditions that are in the same cell. Second, the flux in/out of the cell will be partitioned to the 2 different arcs in the map module.<br />
<br />
A traditional specified head boundary can be manually applied by using the IBOUND and starting heads arrays. The computed heads from MODFLOW will be the same whether a constant head or changing head boundary is used.<br />
<br />
==Well Screens==<br />
'''''NOTE: This approach was developed prior to the existance of the MNW package. The MNW package can more accurately represent a well that crosses multiple MODFLOW layers.'''''<br />
<br />
:When using well screens in a conceptual model the following equation is used to partition the flow to different layers:<br />
<br />
<!--:[[Image:eq1.gif]]<br />
<math>Q_i = \frac{T_i}{T} = \frac{(k_h)_iB_i}{\displaystyle \sum_{j=1}^n (k_h)_iB_i}</math>--><br />
[[Image:maptomodflow1.jpg]]<br />
<br />
where<br />
<br />
''Q<sub>i</sub>'' = The flow rate for layer i<br />
<br />
''(kh)<sub>i</sub>'' = The horizontal hydraulic conductivity for layer i<br />
<br />
''B<sub>i</sub>'' = The length of the well screen intercepted by the layer<br />
<br />
For example<br />
<br />
:[[Image:well_flux_conv.png|325 px]]<br />
<br />
<br />
Assuming the ''K's'' are the horizontal ''K's'', ''Q<sub>1</sub>'' would be computed as:<br />
<br />
<!--:[[Image:eq2.gif]]<br />
<math>\ Q_1 = \frac{K_1B_1}{K_1B_1+K_2B_2+K_3B_3}</math>--><br />
[[Image:maptomodflow2.jpg]]<br />
<br />
In order to complete this computation, the ''K's'' must be assigned to the cells in the grid. Assign the ''K'' values to the grid prior to executing the '''Map &rarr; MODFLOW''' command.<br />
<br />
If the [[GMS:HUF Package|HUF]] package is being used then the ''K'' value for each cell is estimated from the HUF units.<br />
<br />
==Automatic Layer Assignment==<br />
When building a MODFLOW conceptual model with a multi-layer model, it is necessary to define the range of layers associated with a particular source sink object. In the [[GMS:Coverages#Coverage_Setup|Coverage Setup]] dialog when the "Layer range" option is checked option for assigning cell properties to various layers will appear in the feature object [[GMS:Coverages#Feature_Object_Attribute_Table|Attribute Table]] under the "Auto assign layer" column including "Use layer range", "Auto-assign BC to one cell" and "Auto-assign BC including lower cells". For example, an arc corresponding to a specified head boundary condition may be associated with layers 1-3 on the edge of a model. On the other hand, a drain arc in the middle of the model may only be associated with the top layer. The following example shows how a specified head boundary condition would map with the "Use layer range" option with the range set from 1 to 2:<br />
<br />
{{hide in print|[[File:Map-layer-range.png]]}}<br />
{{only in print|[[File:Map-layer-range.png|center|220px]]}}<br />
<br />
In some cases, however, the proper layer for a particular source/sink object will depend on the elevation of the object relative to the layer elevations. For example, a drain may represent a channel that cuts through the terrain. In some places the channel may be shallow and correspond to layer 1. In other places, the channel may be deep enough that it cuts into layer 2. The "Auto assign to one cell" option is used for defining the layer range in these cases. If this option is selected, the object will be associated with the layer where the elevation or head associated with the object falls between the top and bottom elevation for the layer. The following shows how the same specified head boundary condition would map with the "Auto assign to one cell" option:<br />
<br />
{{hide in print|[[File:Map-single-cell.png]]}}<br />
{{only in print|[[File:Map-single-cell.png|center|220px]]}}<br />
<br />
The "Auto-assign including lower cells" option is useful for cases where it's desired to have a specified head boundary assigned to the layer where the head is between the top and bottom elevation of the cell as well as any active cells below that cell. The following shows how the same specified head boundary condition would map with the "Auto-assign including lower cells" options:<br />
<br />
{{hide in print|[[File:Map-including-lower-cells.png]]}}<br />
{{only in print|[[File:Map-including-lower-cells.png|center|220px]]}}<br />
<br />
==Using TINs==<br />
TIN surfaces can be used as part of the conceptual model. See the [[GMS:Map_to_MODFLOW_with_TINs|Map to MODFLOW with TINs]] page.<br />
<br />
==Using Rasters==<br />
<br />
[[GMS:Rasters|Rasters]] can be used as part of the conceptual model. A raster can be used to assign the head or elevation to a boundary condition instead assigning a constant value. A raster can be associated with a point, arc, or polygon. When the '''Map &rarr; MODFLOW''' command is executed and a boundary condition is assigned to a cell, GMS will assign the head/elevation to the boundary condition using the raster value at the cell center. If the cell center is not within the raster then a warning will be reported and a value of 0.0 is assigned for the head/elevation.<br />
<br />
==MODFLOW-USG==<br />
<br />
There are a few unique issues to be aware of when targeting a [[GMS:UGrid_Module|UGrid]] and [[GMS:MODFLOW-USG|MODFLOW-USG]]. The list of features below require that the UGrid be a "stacked grid". A "stacked grid" is one in which there is no vertical sub-discretization of layers and the horizontal discretization of all layers is the same (i.e. the Index of Vertical Sub-Discretization (IVSD) in the UnStructured Grid Discretization (DISU) package could be set to -1).<br />
<br />
* Seepage face boundary condition<br />
* Specified flow boundary condition<br />
* [[GMS:LAK_Package|LAK package]]<br />
* [[GMS:SUB_Package|SUB package]]<br />
<br />
Also, the specified layer option is not supported by Map &rarr; MODFLOW with the RCH and EVT packages.<br />
<br />
==See also==<br />
*[[GMS:MODFLOW Conceptual Model Approach|MODFLOW Conceptual Model Approach]]<br />
*[[GMS:Conductance|Conductance]]<br />
*[[GMS:Map to MODFLOW with TINs|Map to MODFLOW with TINs]]<br />
<br />
<br />
{{Navbox GMS}}<br />
[[Category:MODFLOW|M]]<br />
[[Category:Equations|M]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:Creating_and_Editing_3D_Grids&diff=119040GMS:Creating and Editing 3D Grids2017-02-03T00:42:40Z<p>Dharker: /* Map &rarr; 3D Grid */ noted need for refinement selection in the coverage setup</p>
<hr />
<div>{{3D Grid links}}<br />
=== Creating 3D Grids ===<br />
Two techniques are available for creating 3D grids: the '''Create Grid''' command in the 3D Grid Module and the '''Map &rarr; 3D Grid''' command in the Map Module. When a 3D Cell Centered Grid is created two different viewing modes are available.<br />
=====Create Grid=====<br />
{{for|how to create 2D Grids|GMS:2D Grid Creation and Editing#Create Grid}}<br />
{{Create Finite Difference Grid dialog}}<br />
<br />
=====Map &rarr; 3D Grid=====<br />
:Once the feature object coverages defining a conceptual model have been completely defined, the conceptual model is ready to be converted to a numerical model. The first step in this conversion process is to create a grid using the '''Map &rarr; 3D Grid''' command. Typically, the [[GMS:Grid Frame|'''Grid Frame''']] command is used prior to this command to define the location and dimensions of the grid.<br />
<br />
:When the '''Map &rarr; 3D Grid''' command is selected, the ''Create Grid'' dialog appears. If a grid frame has been defined, the size and location of the grid frame are used to initialize the fields in the ''Create Grid'' dialog. In most cases, these values will not need to be changed and the user can simply select the '''OK''' button to create the grid. If a grid frame has not been defined, the size and location of the grid are initialized so that the grid just surrounds the currently defined conceptual model. Once again, in most cases, no changes will need to be made and the user can typically immediately select the '''OK''' button to create the grid.<br />
<br />
:If one or more refine points are defined in the conceptual model (available when "Refinement" is selected in the [[GMS:Coverages#Coverage_Setup|Coverage Setup]] dialog), the number of rows and columns in the grid will be automatically determined when the grid is created. Thus, these fields cannot be edited by the user and will be dimmed. If refine points are not defined, the number of rows and columns must be entered.<br />
<br />
:When refine points are specified the user must enter the ''Base size'', ''Bias'' and ''Max size''. The ''base size'' is the size the user wants the cell to be right at the refine point. The ''Max size'' is the largest size that the user would like the cells to be in the entire grid. The ''bias'' determines how quickly the cell size will vary as they move away from the refine point. If using a bias of 1.1 then the row next to the refine point will be 1.1 times the ''base size''. The next row will be 1.1 size the previous row.<br />
<br />
=== Editing 3D Grids ===<br />
Each cell in a 3D grid has attributes associated with it. Each grid cell can be specified as [[GMS:Active/Inactive Cells|active/inactive]] and each cell has a [[GMS:Materials|material]] associated with it. To edit the cell attributes associated with a numerical model see [[GMS:Cell Properties|Cell Properties]].<br />
<br />
Rows, columns, or layers can be added or removed from a 3D grid. A row, column, or layer may be added to the grid by using one of the following tools found in the [[GMS:3D Grid Tool Palette|3D Grid Tool Palette]]:<br />
<br />
*[[Image:Tool_AddIRow.png]] '''Add i Boundary'''<br />
<br />
*[[Image:Tool_AddJRow.png]] '''Add j Boundary'''<br />
<br />
*[[Image:Tool_AddKRow.png]] '''Add k Boundary'''<br />
<br />
The boundary of a cell can also be moved to a new location by using the [[GMS:3D Grid Tool Palette|'''Select Node''']] tool. Existing rows, columns, or layers can be deleted by using the '''Merge Selected''' command in the ''Grid'' menu which is used to merge two or more selected rows, columns, or layers into a single row, column, or layer. Since the dimensions of the grid are changed, this command causes all datasets to be deleted. However, MODFLOW input parameters are preserved.<br />
<br />
<br />
{{Navbox GMS}}<br />
[[Category:3D Grid]]<br />
[[Category:3D Grid Dialogs]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:2D_Grid_Creation_and_Editing&diff=119039GMS:2D Grid Creation and Editing2017-02-03T00:40:54Z<p>Dharker: /* Map &rarr; 2D Grid */ noted need for refinment selection in coverage setup</p>
<hr />
<div>{{2D Grid links}}<br />
GMS provides two methods for creating 2D grids and multiple was to edit a 2D grid.<br />
== Creating 2D Grids ==<br />
Two types of 2D grids are supported by GMS, [[GMS:2D Grid Module#2D Grid Types|mesh centered and cell centered]]. The two main techniques used to create 2D grids are: the '''Create Grid''' command and the [[GMS:Map to Modules#Map to 2D Grid|'''Map &rarr; 2D Grid''']] command. A 2D grid can also be created from an existing 3D grid using the [[GMS:3D Grid Module#Converting 3D Grids to Other Data Types|'''Grid &rarr; 2D Grid''']] command in the ''Grid'' menu of the [[GMS:3D Grid Module|3D Grid Module]]. A [[GMS:Importing/Exporting GIS Grids|GIS grid]] may also be imported.<br />
<br />
===Create Grid===<br />
{{for|how to create 3D Grids|GMS:Creating and Editing 3D Grids#Create Grid}}<br />
{{Create Finite Difference Grid dialog}}<br />
<br />
===Map &rarr; 2D Grid===<br />
The '''Map &rarr; 2D Grid''' command is used to construct a 2D grid using the feature objects in a 2D grid coverage. When the '''Map &rarr; 2D Grid''' command is selected, the ''Create Grid'' dialog appears. If a grid frame has been defined, the size and location of the grid frame are used to initialize the fields in the ''Create Grid'' dialog. In most cases, these values will not need to be changed so simply select the '''OK''' button to create the grid. If a grid frame has not been defined, the size and location of the grid are initialized so that the grid just surrounds the currently defined feature objects. If desired, the grid dimensions can be edited prior to selecting the '''OK''' button to create the grid.<br />
<br />
If one or more refine points are defined in the conceptual model (available when "Refinement" is selected in the [[GMS:Coverages#Coverage_Setup|Coverage Setup]] dialog), the number of rows and columns in the grid will be automatically determined when the grid is created. Thus, these fields cannot be edited and will be dimmed. If refine points are not defined, enter the number of rows and columns.<br />
[[Category:GMS Dialogs|2]]<br />
<br />
== Editing 2D Grids ==<br />
Each of the cells in a 2D grid can be active or inactive. An inactive cell is ignored when contours, fringes, or vectors are displayed on the mesh.<br />
<br />
Each cell in the grid has an associated material type. When a new grid is created, the material type for each cell corresponds to the default material type. The default material type can be set using the [[GMS:Materials|'''Materials Editor''']] command in the ''Edit'' menu. A new material can be assigned to a cell or a set of cells by selecting the cell(s) and then selecting the '''Properties''' command from the ''Edit'' menu.<br />
<br />
===Inserting Rows and Columns===<br />
Rows and columns can be added to an existing 2D grid by using the '''Add i Boundary''' tool and the '''Add j Boundary''' tool. Also, the interface between a row and a column can be moved by using the '''Move Boundary''' tool. (See [[GMS:2D Grid Tool Palette|2D Grid Tool Palette]])<br />
<br />
===Merging Rows and Columns===<br />
Rows or columns can be merged together by selecting the rows or columns using the '''Select i''' [[Image:Tool_2DG_Select_I.png]] or '''Select j''' [[Image:Tool_2DG_Select_J.png]] tools, right-clicking and selecting the '''Merge''' command from the pop-up menu. This command is the same as the '''Merge Cells''' command in the [[GMS:2D Grid Commands|''Grid'' menu]] in the main menu bar.<br />
<br />
<br />
{{Navbox GMS}}<br />
[[Category:2D Grid|Cre]]<br />
[[Category:2D Grid Dialogs|Creation]]<br />
[[Category:Needs Update]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:Creating_and_Editing_UGrids&diff=119038GMS:Creating and Editing UGrids2017-02-03T00:39:43Z<p>Dharker: /* Map &rarr; UGrid Dialog */ Noted need for refinement selection in the coverage setup</p>
<hr />
<div>{{UGrid links}}<br />
There are a number of ways to create UGrids. Currently UGrids cannot be edited after they are created.<br />
<br />
==Importing==<br />
UGrids can be imported from a [http://www.vtk.org/VTK/img/file-formats.pdf VTK XML file] by selecting the ''File'' | '''Open''' command or by dragging and dropping the file onto the GMS window. GMS recognizes the ".vtu" extension, which by convention is the extension used for a VTK XML file containing an unstructured grid.<br />
<br />
==New 2D or 3D UGrid==<br />
Right-clicking anywhere in the Project Explorer or on the UGrid Data item will display a menu with '''New UGrid 2D''' and '''New UGrid 3D''' commands. These commands bring up the ''New UGrid'' dialog which specifies options for the creation of a new UGrid, and is very similar to the [[GMS:Creating_and_Editing_3D_Grids#Create_Grid|''Create Grid'']] dialog for 3D structured grids.<br />
<br />
[[File:NewUGrid.png|thumb|none|600 px|The ''New UGrid'' dialog]]<br />
<br />
==Map &rarr; UGrid==<br />
The '''Map &rarr; UGrid''' command creates a UGrid from feature objects. It can be found in the ''Feature Objects'' menu, in the Map toolbar, and in some pop-up menus when right-clicking on items in the [[GMS:Project Explorer|Project Explorer]] (Coverage, Grid Frame). The command opens the ''Create UGrid'' dialog.<br />
<br />
[[Image:DialogCreateUGrid.png|thumb|right|250 px|Map &rarr; UGrid dialog.]]<br />
<br />
===Map &rarr; UGrid Dialog===<br />
*''Dimension'' &ndash; Specifies whether a 2D or 3D UGrid will be created.<br />
*''UGrid type''<br />
**''Regular (not refined)'' &ndash; Creates a grid with rectangular cells that are not refined. Any refinement attributes specified on feature objects are ignored.<br />
**''Quadtree'' &ndash; Creates a grid with rectangular cells that are refined in a quad tree manner around any points, arcs and polygons which specify the refinement attribute and refinement size. The cells surrounding the points, arcs, and polygons are also refined to smooth change from coarse cells to refined cells.<br />
**''Nested'' &ndash; Creates a grid with rectangular cells that are refined like the quadtree option, but the surrounding cells are not smoothed.<br />
**''Voronoi'' &ndash; Creates a Voronoi grid with cells of various sizes and shapes which meet the Voronoi criteria. Only the active coverage is used and it must contain a polygon because the algorithm uses the polygon to create a triangular mesh. The mesh is refined around points that are marked as refine points based on the specified refinement size. The mesh is constructed to honor all arc geometry. If refinement is specified as an attribute on arcs or polygons it is ignored.<br />
*''Refine points'' &ndash; If the ''Quadtree / Octree'' option is selected and refine points exist in multiple coverages (available when "Refinement" is selected in the [[GMS:Coverages#Coverage_Setup|Coverage Setup]] dialog), specifies which refine points to use.<br />
*''Point refinement'' &ndash; If the ''UGrid type'' is '''Quadtree / Octree''', this combo box shows the option '''Refine all layers the same''' which will result in all layers having the same number of cells, and the '''Octree''' option which refines and smooths in the vertical direction.<br />
*''Arc/poly refinement'' &ndash; Similar to the ''Point refinement'' option for arcs and polygons and with the addition of the option '''Quadtree on assigned layers''' which refines horizontally in a quadtree fashion for only the layers that the arcs and polygons are assigned to in the attribute tables.<br />
*''X, Y, Z number of cells''<br />
** If not using the Voronoi UGrid type, the size and number of cells in the X, Y and Z dimensions can be specified. For quad tree UGrids, the cell size represents the large, unrefined size. The small, refined size is determined by the refinement specified at points, arcs and polygons. Also for quad tree UGrids, if the cell size is specified, it represents a target cell size (large, unrefined size); the actual cell size will likely be somewhat different so that the cells fit within the grid boundaries.<br />
<br />
If a [[GMS:Grid_Frame|grid frame]] exists, it is used to determine the location of the grid boundaries. If polygons exist and the ''Regular'' or ''Quad tree'' options are used, any cells that are not inside a polygon are not included in the UGrid.<br />
<br />
{| class="wikitable"<br />
|+ Various UGrids created from the same coverage.<br />
|-<br />
| [[Image:MapToUGridMap.png|thumb|none|200 px|Coverage]]<br />
| [[Image:MapToUGridRegular.png|thumb|none|200 px|Regular UGrid]]<br />
| [[Image:MapToUGridQuad.png|thumb|none|200 px|Quadtree UGrid]]<br />
| [[Image:MapToUGridVoronoi.png|thumb|none|200 px|Voronoi UGrid]]<br />
|}<br />
<br />
==Conversion From Other Data Types==<br />
The following data types can be converted to UGrids by right-clicking on the object in the [[GMS:Project Explorer|Project Explorer]] and selecting the '''''Convert To > UGrid''''' command from the pop-up menu.<br />
<br />
*[[GMS:TIN Module|TINs]]<br />
*[[GMS:2D Grid Module|2D Grids]]<br />
*[[GMS:3D Grid Module|3D Grids]]<br />
*[[GMS:2D Mesh Module|2D Mesh]]<br />
*[[GMS:3D Mesh Module|3D Mesh]]<br />
*[[GMS:Feature_Objects#Polygons|Polygons]] in a [[GMS:Feature_Objects#Coverages|coverage]] (''Map To > Polygons -> UGrid'')<br />
*Polygon shape files in the [[GMS:GIS Module|GIS Module]]<br />
<br />
==Horizons==<br />
The [[GMS:Horizons_to_UGrid|'''Horizons &rarr; UGrid''']] command (in the [[GMS:TIN_Module|TINs]] and [[GMS:Boreholes|Boreholes]] menus) uses [[GMS:Horizons|horizons]] to create a 3D UGrid.<br />
<br />
==Extrude Down to 3D UGrid==<br />
Right-clicking on a UGrid shows the '''Extrude Down to 3D UGrid''' command. If the UGrid has 2D cells, this command can be used to create a new UGrid with 3D prismatic cells. The user can specify the number of layers and the thickness of each layer.<br />
<br />
==3D &#65515; 2D==<br />
If the UGrid has 3D cells, this command brings up a dialog asking for the layer number from which a UGrid consisting of 2D cells will be created.<br />
<br />
==UGrid Structure==<br />
<Prior to GMS 10.2><br />
<br />
A UGrid can keep track of the geometric structure it was generated from. The structure can control the editing operations that are allowed and how they are performed on the UGrid. The structure of a UGrid is shown in the UGrid Properties dialog.<br />
*''Quadtree'' structure is used for grids that were either converted from a 2D or 3D grid or were created using as a Regular, Quadtree, or Nested UGrid.<br />
*''Voronoi'' structure is used for grids created using Voronoi option in the ''Map &rarr; UGrid'' dialog. For the outer cells of a Voronoi UGrid the computational centroid of the cell is along the outer edge to maintain the right angle connection between cells when generating the MODFLOW UDIS package file.<br />
*''Unknown'' structure is used for all other UGrids.<br />
<br />
==Constraints (previously "UGrid Structure")==<br />
A UGrid is a general purpose unstructured grid that can have a variety of cell types. In GMS, we apply some structure to unstructured grids in the form of "constraints". The UGrid's constraint determines the types of cells and the editing operations that are allowed and how they are performed on the UGrid. The constraint of a UGrid is shown in the ''UGrid Properties'' dialog.<br />
*''Quadtree'' &ndash; Used for grids that were either converted from a 2D or 3D grid or were created using as a Regular, Quadtree, or Nested UGrid. Cells can be refined but not deleted or created and cell boundaries cannot be moved. Points cannot be added, deleted, or moved.<br />
*''Voronoi'' &ndash; Used for grids created using Voronoi option in the ''Map &rarr; UGrid'' dialog. For the outer cells of a Voronoi UGrid the computational centroid of the cell is along the outer edge to maintain the right angle connection between cells when generating the MODFLOW UDIS package file. Cells cannot be refined or deleted or created and cell boundaries cannot be moved. Points cannot be added, deleted, or moved.<br />
*''2D'' &ndash; Used for 2D surfaces such as a TIN, mesh, or simply as points without cells. This is the default when creating a new UGrid by clicking points in plan view, and when importing points from a text file and specifying "UGrid Points 2D". Points can be triangulated to form cells and cells can be deleted. Points can be added, deleted, and moved.<br />
*''None'' &ndash; No constraint. Used for all other UGrids. Points can be triangulated to form cells and cells can be deleted. Points can be added, deleted, and moved.<br />
<br />
==Cell Refinement==<br />
UGrid cells can be refined by selecting the cells, right clicking on them, and selecting the ''Refine'' menu item. A new copy of the UGrid will generated with the selected cells refined. The cells will be refined based on the structure of the UGrid. For a UGrid with quad tree structure a cell is refined by adding an additional level of quadtree refinement. Voronoi structured UGrid cells can only be refined by permanently changing the grid structure to Unknown. For a UGrid with unknown structure, a 3D cell is refined by adding a node at the middle of each horizontal edge along with a new node at the center of the top and bottom faces.<br />
<br />
==Deleting Points and Cells==<br />
Selected UGrid points and cells can be deleted by hitting the ''Delete'' key if the current UGrid [[#Constraints (previously "UGrid Structure")|constraint]] allows it.<br />
<br />
==Lock to Prevent Editing / Unlock for Editing==<br />
In order to prevent accidental editing of a UGrid, such as dragging a selected point, UGrids can be "locked" and "unlocked". They typically start out locked when they are created, and when locked, no editing is allowed. To unlock the UGrid, simply right-click on the UGrid and select the "Unlock for Editing" command. This command changes to say "Lock to Prevent Editing" when the UGrid is unlocked, allowing the user to lock the UGrid and thus prevent further editing.<br />
<br />
==Triangulate==<br />
UGrid points can be triangulated to form a Delauney triangulated irregular network, or TIN by right-clicking on the UGrid and selecting the '''Triangulate''' command. If any cells exist they will be deleted and new triangle cells will be created.<br />
<br />
<br />
{{Navbox GMS}}<br />
[[Category:UGrid]]<br />
[[Category:UGrid Dialogs]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=SMS:Grid_Smoothing&diff=119021SMS:Grid Smoothing2017-02-02T22:32:43Z<p>Dharker: Corrected spelling of 'and'</p>
<hr />
<div>[[File:Cartesian Grid Smoothing Options.jpg|thumb|225 px|''Cartesian Grid Smoothing Options'' dialog]]<br />
The ''Cartesian Grid Smoothing Options'' dialog is opened by right-clicking on a Cartesian Grid item in the [[SMS:Project Explorer|Project Explorer]] and selecting the '''Smooth...''' menu command. The following options can be specified:<br />
* ''Filter size'' &ndash; This determines how many neighbors are included when smoothing the grid. Options are 3x3 and 5x5.<br />
* ''Number of iterations'' &ndash; This specifies how many passes should be made with the smoothing algorithm.<br />
* ''Max. elevation change'' &ndash; This value specifies the maximum allowable elevation change per iteration for each cell.<br />
* ''Filter ratio'' &ndash; The new cell elevation is computed using the original elevation (at the beginning of the iteration not the whole process) and the "blurred" elevation. The filter ratio defines how far the elevation is changed between the original elevation and the "blurred" elevation. A filter ratio of 1.0 would replace the existing elevation with the "blurred" elevation. A filter ratio of 0.0 would be pointless as it wouldn't change the elevations. A filter ratio of 0.5 would give a new elevation that is the average of the original elevation and the blurred elevation.<br />
* ''Filter Range'' &ndash; The start and end index values specify the extents of the smoothing. Defaults to the grid extents.<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
* ''Column start'' &ndash; The column index on which to start the smoothing process.<br />
* ''Column end'' &ndash; The column index on which to end the smoothing process.<br />
* ''Row start'' &ndash; The row index on which to start the smoothing process.<br />
* ''Row end'' &ndash; The row index on which to end the smoothing process. </blockquote><br />
* ''Only modify selected cells/cell locations'' &ndash; If this option is selected, only the cells or cell locations (if model uses elevations at centers, faces, and corners) that are selected are smoothed. Cells or cell locations not selected may be used to compute "blurred" elevations but their elevations are never modified.<br />
<br />
==Related Topics==<br />
* [[SMS:Cartesian Grid Module#Project Explorer|Cartesian Grid Module Right-Click Menus]]<br />
* [[SMS:Cartesian Grid Module|Cartesian Grid Module]]<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
[[Category:SMS Cartesian Grid|S]]<br />
[[Category:2D Grid Dialogs]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:Map_to_MODFLOW&diff=119013GMS:Map to MODFLOW2017-02-02T21:12:22Z<p>Dharker: /* Automatic Layer Assignment */ Clarified how to use the automatic layer assignment after a customer was left confused</p>
<hr />
<div>{{MODFLOW Links}}<br />
After the [[GMS:MODFLOW Conceptual Model Approach|conceptual model]] is constructed and a grid has been created, the final step in converting a conceptual model to a MODFLOW numerical model is to select the '''Map &rarr; MODFLOW''' command. However, before this command can be selected, MODFLOW must be initialized. MODFLOW is initialized as follows:<br />
<br />
#Switch to the 3D Grid module<br />
#Select the '''New Simulation''' command in the ''MODFLOW'' menu.<br />
#MODFLOW simulations are steady state by default. For a transient simulation, go to the [[GMS:Global Options/Basic Package|''Global Options/Basic Package'' Dialog]] and select the ''Transient'' option. Then set up the [[GMS:Stress Periods|stress periods]] to use in the simulation.<br />
#By default, the top layer is unconfined and the remaining layers are confined. To use a different set of layer types, go to the BCF/LPF/HUF Package dialog and select the appropriate layer type for each layer.<br />
<br />
Once MODFLOW is initialized, the '''Map &rarr; MODFLOW''' command becomes available. When the command is selected, the ''Map &rarr; MODFLOW Options'' dialog appears. Three options are available for converting the conceptual model: ''Active coverage only'', ''All applicable coverages'', and ''All visible coverages''. If the ''All applicable coverages'' option is chosen, all of the feature objects in all of the MODFLOW-related coverages in the active conceptual model are used. This option is typically selected when the conceptual model is first converted. If the ''Active coverage only'' or the ''All visible coverages'' option is selected, only a subset of the coverages are used to update the numerical model.<br />
<br />
==Temporal Discretization==<br />
See the [[GMS:Temporal_Discretization|Temporal Discretization]] page.<br />
<br />
==Multiple Values Per Cell==<br />
Because GMS processes each feature object separately, there will often be sources/sinks that were derived from two separate feature objects in the same cell. In fact, this is almost always the case in the cell that contains the endpoint of one arc and the beginning point of an adjacent arc. This is not an error. MODFLOW handles each of the boundary conditions in the cell simultaneously.<br />
<br />
==Specified Head Cells==<br />
Because the constant head condition forces the head in those cells to match whatever is specified, it is inappropriate to have other boundary conditions defined in the cells that are designated constant head. Therefore, GMS processes all of the specified head objects first. Afterwards, if there is another stress that should normally be assigned to a cell that has been previously assigned a constant head condition, the new stress is not assigned.<br />
<br />
==Changing Head Boundary==<br />
When mapping a specified head boundary to MODFLOW, GMS always uses the CHD package ([[GMS:CHD Package|Time Variant Specified Head package]]). In MF2K, a changing head boundary must be used in order to extract fluxes out of the MODFLOW output for the arcs in the map module. With MF2K, it is not possible to get a flux observation with normal Spec Head. It is assumed that most of the time the user would want to see the flux in/out of the boundary. If a cell contains two different arcs, the specified head is split in 2 pieces at cells where 2 specified head arcs meet. This is done for 2 reasons. First, the CHD package will combine the CHD boundary conditions that are in the same cell. Second, the flux in/out of the cell will be partitioned to the 2 different arcs in the map module.<br />
<br />
A traditional specified head boundary can be manually applied by using the IBOUND and starting heads arrays. The computed heads from MODFLOW will be the same whether a constant head or changing head boundary is used.<br />
<br />
==Well Screens==<br />
'''''NOTE: This approach was developed prior to the existance of the MNW package. The MNW package can more accurately represent a well that crosses multiple MODFLOW layers.'''''<br />
<br />
:When using well screens in a conceptual model the following equation is used to partition the flow to different layers:<br />
<br />
<!--:[[Image:eq1.gif]]<br />
<math>Q_i = \frac{T_i}{T} = \frac{(k_h)_iB_i}{\displaystyle \sum_{j=1}^n (k_h)_iB_i}</math>--><br />
[[Image:maptomodflow1.jpg]]<br />
<br />
where<br />
<br />
''Q<sub>i</sub>'' = The flow rate for layer i<br />
<br />
''(kh)<sub>i</sub>'' = The horizontal hydraulic conductivity for layer i<br />
<br />
''B<sub>i</sub>'' = The length of the well screen intercepted by the layer<br />
<br />
For example<br />
<br />
:[[Image:well_flux_conv.png|325 px]]<br />
<br />
<br />
Assuming the ''K's'' are the horizontal ''K's'', ''Q<sub>1</sub>'' would be computed as:<br />
<br />
<!--:[[Image:eq2.gif]]<br />
<math>\ Q_1 = \frac{K_1B_1}{K_1B_1+K_2B_2+K_3B_3}</math>--><br />
[[Image:maptomodflow2.jpg]]<br />
<br />
In order to complete this computation, the ''K's'' must be assigned to the cells in the grid. Assign the ''K'' values to the grid prior to executing the '''Map &rarr; MODFLOW''' command.<br />
<br />
If the [[GMS:HUF Package|HUF]] package is being used then the ''K'' value for each cell is estimated from the HUF units.<br />
<br />
==Automatic Layer Assignment==<br />
When building a MODFLOW conceptual model with a multi-layer model, it is necessary to define the range of layers associated with a particular source sink object. In the [[GMS:Coverages#Coverage_Setup|Coverage Setup]] dialog when the "Layer range" option is checked option for assigning cell properties to various layers will appear in the feature object [[GMS:Coverages#Feature_Object_Attribute_Table|Attribute Table]] under the "Auto assign layer" column including "Use layer range", "Auto-assign BC to one cell" and "Auto-assign BC including lower cells". For example, an arc corresponding to a specified head boundary condition may be associated with layers 1-3 on the edge of a model. On the other hand, a drain arc in the middle of the model may only be associated with the top layer. The following example shows how a specified head boundary condition would map with the "Use layer range" option with the range set from 1 to 2:<br />
<br />
{{hide in print|[[File:Map-layer-range.png]]}}<br />
{{only in print|[[File:Map-layer-range.png|center|220px]]}}<br />
<br />
In some cases, however, the proper layer for a particular source/sink object will depend on the elevation of the object relative to the layer elevations. For example, a drain may represent a channel that cuts through the terrain. In some places the channel may be shallow and correspond to layer 1. In other places, the channel may be deep enough that it cuts into layer 2. The "Auto assign to one cell" option is used for defining the layer range in these cases. If this option is selected, the object will be associated with the layer where the elevation or head associated with the object falls between the top and bottom elevation for the layer. The following shows how the same specified head boundary condition would map with the "Auto assign to one cell" option:<br />
<br />
{{hide in print|[[File:Map-single-cell.png]]}}<br />
{{only in print|[[File:Map-single-cell.png|center|220px]]}}<br />
<br />
The "Auto-assign including lower cells" option is useful for cases where it's desired to have a specified head boundary assigned to the layer where the head is between the top and bottom elevation of the cell as well as any active cells below that cell. The following shows how the same specified head boundary condition would map with the "Auto-assign including lower cells" options:<br />
<br />
{{hide in print|[[File:Map-including-lower-cells.png]]}}<br />
{{only in print|[[File:Map-including-lower-cells.png|center|220px]]}}<br />
<br />
==Using TINs==<br />
TIN surfaces can be used as part of the conceptual model. See the [[GMS:Map_to_MODFLOW_with_TINs|Map to MODFLOW with TINs]] page.<br />
<br />
==Using Rasters==<br />
<br />
[[GMS:Rasters|Rasters]] can be used as part of the conceptual model. A raster can be used to assign the head or elevation to a boundary condition instead assigning a constant value. A raster can be associated with a point, arc, or polygon. When the '''Map &rarr; MODFLOW''' command is executed and a boundary condition is assigned to a cell, GMS will assign the head/elevation to the boundary condition using the raster value at the cell center. If the cell center is not within the raster then a warning will be reported and a value of 0.0 is assigned for the head/elevation.<br />
<br />
==MODFLOW-USG==<br />
<br />
There are a few unique issues to be aware of when targeting a [[GMS:UGrid_Module|UGrid]] and [[GMS:MODFLOW-USG|MODFLOW-USG]]. The list of features below require that the UGrid be a "stacked grid". A "stacked grid" is one in which there is no vertical sub-discretization of layers and the horizontal discretization of all layers is the same (IVSD in the DISU package could be set to -1).<br />
<br />
* Seepage face boundary condition<br />
* Specified flow boundary condition<br />
* [[GMS:LAK_Package|LAK package]]<br />
* [[GMS:SUB_Package|SUB package]]<br />
<br />
Also, the specified layer option is not supported by Map &rarr; MODFLOW with the RCH and EVT packages.<br />
<br />
==See also==<br />
*[[GMS:MODFLOW Conceptual Model Approach|MODFLOW Conceptual Model Approach]]<br />
*[[GMS:Conductance|Conductance]]<br />
*[[GMS:Map to MODFLOW with TINs|Map to MODFLOW with TINs]]<br />
<br />
<br />
{{Navbox GMS}}<br />
[[Category:MODFLOW|M]]<br />
[[Category:Equations|M]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:Defining_Layer_Elevations&diff=118961GMS:Defining Layer Elevations2017-02-02T00:15:06Z<p>Dharker: /* Step 2: Interpolating the Elevations to the MODFLOW Arrays */ Linked wiki page on Interpolate to MODFLOW Layers dialog</p>
<hr />
<div>{{MODFLOW Links}}<br />
One of the most important steps in defining a [[GMS:MODFLOW#Building a MODFLOW Model|MODFLOW model]] is to define the layer elevations. The layer elevations are stored in the [[GMS:Global Options/Basic Package|''Global Options/Basic package'']]. The layer elevations include a top elevation for layer 1 and a bottom elevation for all layers. For all layers except for the top layers, the top elevation for the layer is assumed to be equal to the bottom elevation of the layer above.<br />
<br />
==Define Layer Data==<br />
As described above, MODFLOW models can be defined using one of two approaches: (1) by editing the input values on a [[GMS:Cell Properties|cell-by-cell basis]] directly on the grid, or (2) by creating a high level [[GMS:MODFLOW Conceptual Model Approach|conceptual model]] using the [[GMS:Map Module|Map module]]. Both approaches can be used to define the layer elevation arrays. With the grid approach, a constant value can be assigned to the entire array at once or to a set of selected cells. With the conceptual model approach, a set of polygons can be used to define zones of elevations within each layer. While these two approaches are simple to use, in most cases they result in an overly simplistic stair step definition of the layer elevations. In most cases, it is more appropriate to use the [[GMS:2D Interpolation Options|2D geostatistical tools]] in GMS to smoothly interpolate layer elevations.<br />
<br />
==Interpolating Elevation Data==<br />
The following steps are used to interpolate elevation data:<br />
<br />
===Step 1: Importing the Scatter Point Elevation Data ===<br />
The fist step in defining MODFLOW layer elevation array data is to create a 2D scatter point set. The set should include a dataset for the top elevation of the top layer and the bottom elevation array of the top layer and each of the underlying layers. A water table elevation corresponding to the desired initial condition (starting head) may also be defined. The simplest way to create such a scatter point set is to create a tabular scatter point file using a spreadsheet or a text editor. The scatter point file is imported ''File'' | '''Open''' menu command. A sample tabular scatter point file for a three layer model is shown below:<br />
<br />
{| class="wikitable"<br />
!width="75"|x<br />
!width="75"|y<br />
!width="75"|top1<br />
!width="75"|bot1<br />
!width="75"|bot2<br />
!width="75"|bot3<br />
|-<br />
|align = "center"|360||align = "center"|1670||align = "center"|450||align = "center"|345||align = "center"|200||align = "center"|100<br />
|-<br />
|align = "center"|290||align = "center"|870||align = "center"|445||align = "center"|340||align = "center"|195||align = "center"|95<br />
|-<br />
|align = "center"|480||align = "center"|420||align = "center"|450||align = "center"|350||align = "center"|200||align = "center"|100<br />
|-<br />
|align = "center"|620||align = "center"|2120||align = "center"|455||align = "center"|245||align = "center"|200||align = "center"|100<br />
|-<br />
|align = "center"|990||align = "center"|1820||align = "center"|470||align = "center"|355||align = "center"|210||align = "center"|115<br />
|-<br />
|align = "center"|890||align = "center"|1190||align = "center"|465||align = "center"|350||align = "center"|205||align = "center"|110<br />
|-<br />
|align = "center"|1030||align = "center"|710||align = "center"|475||align = "center"|360||align = "center"|215||align = "center"|130<br />
|-<br />
|etc.||||||||||<br />
|}<br />
<br />
===Step 2: Interpolating the Elevations to the MODFLOW Arrays ===<br />
Once the scatter point file is imported to GMS, the next step in defining MODFLOW layer elevation arrays is to interpolate the elevations to the MODFLOW layer elevation arrays. The elevation values can be interpolated directly to the MODFLOW arrays using the '''...to MODFLOW Layers''' command in the ''Interpolation'' menu in the 2D Scatter Point module. When this command is selected, the ''[[GMS:Interpolate to MODFLOW Layers|Interpolate to MODFLOW Layers]]'' dialog appears.<br />
<br />
The purpose of this dialog is to associate each of the datasets in the scatter point set with one of the layer data input arrays. A dataset and the corresponding layer data array are selected in the top of the dialog and the '''Map''' button is selected. The defined relationship is then shown in the bottom of the dialog. Once this is completed for each dataset/layer data array combination, the '''OK''' button is selected and the scatter point data set values are interpolated directly to the MODFLOW arrays using the currently selected interpolation options.<br />
<br />
In some cases, GMS can automatically match the scatter point datasets to the appropriate layer elevation arrays. GMS searches each dataset name to see if "top" or "bot" makes up any portion of the name. If so, it then searches for a number to determine the layer the array should be interpolated to. For example, the dataset names top1, top of layer 1, and top elevation of layer 1 would all automatically map correctly.<br />
<br />
It should be noted that the layer data can be set up using multiple scatter point sets. For example, it is possible to have one dense set of scatter points to define the ground surface (top of layer one), and a second, more sparse set of scatter points to define the layer bottom elevations. In this case, the to Layers command would need to be selected twice, once for each of the scatter point sets.<br />
<br />
===Step 3: Fixing Layer Interpolation Errors===<br />
[[File:FixLayerErrors.png|thumb|375 px|The ''Fix Layer Errors'' dialog]]<br />
When interpolating layer data for the purpose of defining MODFLOW layer elevation arrays, there are often cases where the interpolated values overlap. For example, for some of the cells, the top elevation values for a particular layer may be lower than the bottom values for the layer. In some cases, the best way to fix such a problem is to experiment with the interpolation options or to create some "pseudo-points" to fill in the gaps between sparse scatter points. In other cases, the overlap may correspond to a pinchout or truncation in the layer. In such cases, the elevations need to be adjusted so that there is a small but finite thickness for all cells in the overlapping region.<br />
<br />
The first step in fixing layer errors is to use the [[GMS:Model Checker|Model Checker]] to determine if elevation overlaps occur. If they do occur, the '''Fix Layer Errors''' button at the top of the ''Model Checker'' dialog can be used to bring up the ''Fix Layer Errors'' dialog. The number of overlap errors for each layer is listed on the right side of the dialog. A layer is highlighted and a correction method is selected on the left side of the dialog. The '''Fix Selected Layer''' button is then used to adjust the elevations. Four options are available for fixing layer errors:<br />
<br />
===== Average =====<br />
With the ''Average'' method, for each cell where an overlap is found, the average elevation at the overlap is computed as<br />
<br />
<!--:[[Image:eq_fix1.gif]]<br />
<math>\text{ave} = \frac{\text{top} - \text{bottom}}{2}</math>--><br />
[[Image:layerele1.jpg]]<br />
<br />
The top and bottom elevations are then adjusted as follows:<br />
<br />
<!--:[[Image:eq_fix2.gif]]<br />
<math>\text{top} = \text{ave} + \frac{\text{min thickness}}{2}</math>--><br />
[[Image:layerele2.jpg]]<br />
<br />
<!--:[[Image:eq_fix3.gif]]<br />
<math>\text{bot} = \text{ave} - \frac{\text{min thickness}}{2}</math>--><br />
[[Image:layerele3.jpg]]<br />
<br />
This option is useful for modeling the transition zones adjacent to embedded seams.<br />
<br />
===== Preserve Top =====<br />
With the ''Preserve top'' method, at each cell, where an overlap is found the top elevation is unchanged and the bottom elevation is adjusted to:<br />
<br />
<!--:[[Image:eq_fix4.gif]]<br />
:<math>\ \text{bot} = \text{top} - \text{min thickness}</math>--><br />
[[Image:layerele4.jpg]]<br />
<br />
This option can be used to model truncated outcroppings.<br />
<br />
===== Preserve Bottom =====<br />
With the ''Preserve bottom'' method, at each cell where an overlap is found the bottom elevation is unchanged and the top elevation is adjusted to:<br />
<br />
<!--:[[Image:eq_fix5.gif]]<br />
:<math>\ \text{top} = \text{bot} + \text{min thickness}</math>--><br />
[[Image:layerele5.jpg]]<br />
<br />
===== Truncate to Bedrock =====<br />
The ''Truncate to bedrock'' option differs from the other methods in that it can be used to alter several layers at once. With this method, it is assumed that the bottom elevation values for the bottom layer represent the top of a bedrock unit. The bedrock elevations may overlap several upper elevation arrays. Each cell in the grid is checked and if the bedrock elevation is above the top elevation for the cell, the cell is turned off (made inactive). If the bedrock elevation is below the top elevation and above the bottom elevation for the cell, the bottom elevation for the cell is set equal to the bedrock elevation. If the bedrock elevation is below the bottom of the cell, the cell elevations are unchanged.<br />
<br />
==Define Layer Data with Solids==<br />
[[GMS:Solid Module|Solids]] can also be used to define layer data for MODFLOW. The [[GMS:Solids to MODFLOW Command|'''Solids &rarr; MODFLOW''']] and [[GMS:Solids to HUF|'''Solids &rarr; HUF''']] commands in the Solid module set up the layer elevations using the currently defined solids.<br />
<br />
<br />
{{Navbox GMS}}<br />
<br />
[[Category:MODFLOW]]<br />
[[Category:Equations|D]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:RT3D&diff=118650GMS:RT3D2017-01-26T00:14:45Z<p>Dharker: Added RT3D files table</p>
<hr />
<div>{{Infobox Model |<br />
|name= RT3D <br />
|model_type= multi-species reactive transport<br />
|developer= Battelle Pacific Northwest National Laboratory <br />
|documentation= [http://gmsdocs.aquaveo.com/rt3dman.pdf RT3D Manual v1] [http://gmsdocs.aquaveo.com/rt3dv2.5man.pdf RT3D Manual v2.5]<br />
|tutorials= [[GMS:Tutorials#Models|RT3D Tutorials]]<br />
}}<br />
RT3D is a multi-species reactive transport model developed by the [https://www.pnl.gov/ Pacific Northwest National Laboratory]. RT3D is a modified version of MT3DMS that utilizes alternate Chemical Reaction packages. Numerous pre-defined reactions are available and an option is provided for creating user-defined reactions. RT3D is well-suited for simulating natural attenuation and bioremediation.<br />
<br />
Since RT3D is a modified version of MT3DMS, most of the input to RT3D is identical to the input required for MT3DMS. Thus, the RT3D interface is contained within the ''MT3D'' menu in the 3D Grid module. In the [[GMS:Basic Transport Package Dialog|''Basic Transport Package'']] dialog, an option is provided for selecting the current model as either MT3DMS, RT3D, or SEAM3D. A number of options in the interface then change based on which model is selected.<br />
<br />
Since much of the RT3D interface is identical to the [[GMS:MT3DMS|MT3DMS Interface]], only the portions of the interface which are unique to RT3D are described in this help file.<br />
<br />
The RT3D model can be added to a [http://www.aquaveo.com/software/gms-pricing paid edition] of GMS.<br />
[[Category:Link to Store]]<br />
<br />
==Basic Transport Package==<br />
The first step in defining an RT3D simulation is to define the data required by the Basic Transport (BTN) package. The options in the [[GMS:Basic Transport Package Dialog|''Basic Transport Package'' dialog]] unique to RT3D are as follows:<br />
<br />
===Packages===<br />
The '''Packages''' button brings up the ''Packages'' dialog. If the RT3D model is the current model and the Chemical Reaction package is selected, one of the RT3D reactions must be selected from the pull-down list. The first nine reaction modules are pre-defined (specified as the IREACT value):<br />
<br />
* No reaction (tracer transport)<br />
* Inst. Aerobic Deg. of BTEX<br />
* Inst. Deg. of BTEX w/ MEA<br />
* Kinetic-Limited Deg. of BTEX w/ MEA<br />
* Rate-Limited Sorption Reactions<br />
* Double Monod Model<br />
* Sequential Decay Reactions<br />
* Aerobic/Anaerobic PCE/TCE Dechlorination<br />
* Test Model #1<br />
* Test Model #2<br />
<br />
If one of these reactions is selected, the names of the species and the names of the reaction parameters are automatically determined by GMS. The last reaction is a user-defined reaction. If this option is selected, a list of species and list of reaction parameters must be specified.<br />
<br />
===Define Species===<br />
For most of the reaction package options, once the reaction package is selected, the list of species used by the package is automatically initialized by GMS. However, if the user-defined reaction package is selected, the '''Define Species''' button is undimmed in the ''Basic Transport Package'' dialog and a list of species must be manually defined before any concentrations are assigned to sources/sinks.<br />
<br />
==Chemical Reactions Package==<br />
[[File:RT3D Chemical Reaction.png|thumb|500 px|The ''RT3D Chemical Reaction Package'' dialog]]<br />
The ''Chemical Reactions Package'' dialog utilized by RT3D is different from the ''MT3DMS Chemical Reactions'' dialog. The items in the dialog unique to RT3D are as follows:<br />
<br />
===Solver===<br />
If the selected reaction package is a kinetic reaction, several solvers are available for the solution of the chemical reaction equations. The desired solver should be selected from the ''Solver'' pull-down list. When one of these solvers is used, an absolute and relative tolerance must be specified for each of the mobile species using the atol and rtol parameters.<br />
<br />
===Reaction Parameters===<br />
With each reaction package, a set of reaction parameters must be defined. The method used to edit the reaction parameters depends on whether the reaction is a pre-defined reaction or a user-defined reaction.<br />
<br />
===Pre-Defined Reactions===<br />
For the pre-defined reactions, the number of reaction parameters and the names of the parameters are fixed. If the ''Spatially vary all'' toggle is off, a single value is entered for each parameter using the edit field below the parameter list. If the ''Spatially vary all'' toggle is on, an array of values is entered for each parameter using the '''Edit''' button. In this case, the cell-by-cell parameter values can also be edited using the '''Cell Attributes''' command.<br />
<br />
===User-Defined Reactions===<br />
For user-defined reactions, the list of reaction parameters must be defined using the '''Define Parameters''' button. This button brings up the ''Define Parameters'' dialog. This dialog functions similarly to the ''Define Species'' dialog. The '''New''' and '''Delete''' buttons are used to add and remove items from the list. The '''Import''' button is used to read a previously defined list of reaction parameters from an RT3D super file (*.rts).<br />
<br />
With the pre-defined reactions, the reaction parameters are either all spatially variable or all constant. However, with the user-defined reaction option, selected parameters may be designated as spatially variable while others are designated as constant. The variable/constant status of a parameter is selected using the ''Spatially variable'' toggle in the ''Define Parameters'' dialog.<br />
<br />
==RT3D Files==<br />
<br />
Below is a table of available RT3D files.<br />
<br />
* For more information on these files see pages 11-38 of the original RT3D online documentation ([http://gmsdocs.aquaveo.com/rt3dman.pdf#page=11])<br />
<br />
{| class="wikitable" <br />
|+'''Files'''<br />
!width="50" align="center"|Name<br />
!width="250" align="center"|Description<br />
|-<br />
|.ADV||Advection Package File<br />
|-<br />
|.BTN||Basic Transport File<br />
|-<br />
|.CON||Concentration Output File<br />
|-<br />
|.DSP||Dispersion Package File<br />
|-<br />
|.DSS||Data Super File<br />
|-<br />
|.MTR||GMS Results File<br />
|-<br />
|.OUT||Output File<br />
|-<br />
|.RCT||Chemical Reaction Package File<br />
|-<br />
|.RTS||RT3D Super File<br />
|-<br />
|.SSM||Sources/Sink Mixing File<br />
|-<br />
|}<br />
<br />
<br />
{{Navbox GMS}}<br />
[[Category:RT3D]]<br />
[[Category:3D Grid]]<br />
[[Category:GMS Dialogs|R]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=SMS:CMS-Wave&diff=118649SMS:CMS-Wave2017-01-25T22:18:36Z<p>Dharker: Fixed broken link</p>
<hr />
<div>{{SMS Infobox Model |<br />
|name= CMS-Wave<br />
|model_type= Designed for accurate and reliable representation of wave processes affecting operation and maintenance of coastal inlet structures in navigation projects as well as in risk and reliability assessment of shipping in inlets and harbors.<br />
|developer= <br />
[http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=Persons;112 Lihwa Lin, Ph.D.]<br />
|web_site= [http://www.erdc.usace.army.mil/Missions/Water-Resources/CIRP/ CIRP]<br />
|tutorials= <br />
General Section<br />
* Data Visualization<br />
* Observation<br />
Models Section<br />
* CMS - CMS-Wave (pending)<br />
}}<br />
<br />
CMS-Wave (formerly known as WABED) is one of the principal components of the [[SMS:CMS|Coastal Modeling System (CMS)]]. WABED stood for "Wave-Action Balance Equation Diffraction" model. The model is a 2-D wave spectral transformation (phase-averaged). The term "phase-averaged" means that it neglects changes in the wave phase in calculating wave and other nearshore processes. This class of wave models represent changes that occur only in the wave energy density. It was originally built to represent theoretically developed approximations for both wave diffraction and reflection in a nearshore domain. <br />
<br />
The [[SMS:SMS|SMS]] interface to CMS-Wave includes tools for creating input files as well as post-processing capabilities.<br />
<br />
The CMS-Wave model can be added to a [http://www.aquaveo.com/software/sms-pricing paid edition] of SMS.<br />
[[Category:Link to Store]]<br />
<br />
== Graphical Interface ==<br />
The [[SMS:CMS-Wave Graphical Interface|CMS-Wave Graphical Interface]] contains tools to create and edit a CMS-Wave simulation. The simulation consists of a geometric definition of the model domain (the grid) and a set of numerical parameters. The parameters define the boundary conditions and options pertinent to the model.<br />
<br />
The interface is accessed by selecting the [[SMS:Cartesian Grid Module|Cartesian Grid Module]] and setting the current model to CMS-Wave. If a grid has already been created for a CMS-Wave simulation or an existing simulation read, the grid object will exist in the [[SMS:Project Explorer|Project Explorer]] and selecting that object will make the Cartesian grid module active and set the model to CMS-Wave. See [[SMS:Cartesian Grid Module#Creating 2D Grids|Creating 2D Cartesian Grids]] for more information.<br />
<br />
The interface consists of the [[SMS:Cartesian_Grid_Module_Menus|Cartesian grid menus]] and [[SMS:Cartesian Grid Tools|tools]] augmented by the [[SMS:CMS-Wave Menu|CMS-Wave Menu]]. See [[SMS:CMS-Wave Graphical Interface|CMS-Wave Graphical Interface]] for more information.<br />
<br />
== Model Data Files ==<br />
Four input files are required for a CMS-Wave simulation. Up to six optional input files may also be utilized depending on the processes being modeled and the selected model parameters. Depending on which options are selected for the simulation, CMS-Wave will generate from one to six output files. See [[SMS:CMS-Wave Files|CMS-Wave Files]] for more information.<br />
<br />
== Sample Simulations ==<br />
Simulations illustrating the model capabilities will be posted here soon.<br />
<br />
== Model Development History ==<br />
*July 2006 &ndash; Initial CHETN announcing the release of WABED is published. Interface is available through the [[SMS:STWAVE|STWAVE]] interface in SMS.<br />
*December 2007 &ndash; Four new features were recently added to CMS-Wave. These include:<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
* wave run-up &ndash; The wave run-up calculation includes both wave setup and maximum vertical swash that enter, for example, in beach erosion during storms. <br />
* wave transmission and overtopping at structures &ndash; The calculation of wave transmission and overtopping is possible for either vertical wall or rubble- mound jetties and breakwaters, and for submerged reefs. These wave run-up and wave overtopping structure calculations are necessary, for example, in the study of overwash and flanking of beaches adjacent to jetties. <br />
* card-format for convenient model control<br />
* option for running in a Fast Mode &ndash; With the new ''Fast-Mode'' option, CMS-Wave calculates the spectral transformation on five directional bins (each 30-deg angle for a broad-band input spectrum) or on seven directional bins (each 5-deg angle for a narrow-band input spectrum, or on 25- deg angle for wind input) to minimize execution time. In Fast Mode, the wave model is at least five times faster than in the Normal Mode, which operates on 35 directional bins in the half plane. Fast Mode is recommended when needing rapid calculation in reconnaissance or test applications. Wave information estimated in the Fast Mode is expected to be less accurate than in the Normal Mode because the calculation is based on fewer directional bins. Normal Mode should be specified for final runs.<br />
</blockquote><br />
<br />
== Related Topics: ==<br />
* [[SMS:SMS Models|SMS Models Page]]<br />
* [[SMS:CMS-Flow|CMS-Flow]]<br />
<br />
== External Links: ==<br />
* [http://acwc.sdp.sirsi.net/client/search/asset/1000803 CMS-Wave Explanatory Report] Aug 2008<br />
* [http://cirp.usace.army.mil/techtransfer/workshops/nap12/Presentation/CMS_UserManual_030212_final.pdf CMS-Wave User Manual] Mar 2012<br />
* [http://cirpwiki.info/wiki/CMS#Documentation_Portal CIRP CMS Wiki]<br />
* August 2008 ERDC/CHL TR-08-13 CMS-Wave: A Nearshore Spectral Wave Processes Model for Coastal Inlets and Navigation Projects [http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=PUBLICATIONS;583]<br />
* May 2007 ERDC/CHL CHETN-I-74 WABED Model in the SMS: Part 2. Graphical Interface [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-i-74.pdf]<br />
* Jul 2006 ERDC/CHL CHETN-III-73 Wave-Action Balance Equation Diffraction (WABED) Model: Tests of Wave Diffraction and Reflection at Inlets [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iii-73.pdf]<br />
* Jul 2007 ERDC/CHL CHETN-IV-69 Tips for Developing Bathymetry Grids for Coastal Modeling System Applications [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-69.pdf]<br />
* Feb 2006 ERDC/CHL CHETN-IV-67 Frequently-Asked Questions (FAQs) About Coastal Inlets and U.S. Army Corps of Engineers' Coastal Inlets Research Program (CIRP) [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-67.pdf] Updated FAQ Website [http://cirp.usace.army.mil/pubs/FAQs/FAQ.html]<br />
* Sep 2008 Modeling of Morphologic Changes Caused by Inlet Management Strategies at Big Sarasota Pass, Florida [http://www.fsbpa.com/08Proceedings/07AlymovTruittPoffAnderson2008.pdf]<br />
* April 2012 ERDC/CHL CHETN-IV-81 Full-plane Wave Transformation and Grid Nesting. [http://acwc.sdp.sirsi.net/client/search/asset/1006680]<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
<br />
[[Category:CMS-Wave|CMS-Wave]]<br />
[[Category:Wave Modeling|CMS-Wave]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:RT3D&diff=118648GMS:RT3D2017-01-25T22:17:20Z<p>Dharker: Linked website</p>
<hr />
<div>{{Infobox Model |<br />
|name= RT3D <br />
|model_type= multi-species reactive transport<br />
|developer= Battelle Pacific Northwest National Laboratory <br />
|documentation= [http://gmsdocs.aquaveo.com/rt3dman.pdf RT3D Manual v1] [http://gmsdocs.aquaveo.com/rt3dv2.5man.pdf RT3D Manual v2.5]<br />
|tutorials= [[GMS:Tutorials#Models|RT3D Tutorials]]<br />
}}<br />
RT3D is a multi-species reactive transport model developed by the [https://www.pnl.gov/ Pacific Northwest National Laboratory]. RT3D is a modified version of MT3DMS that utilizes alternate Chemical Reaction packages. Numerous pre-defined reactions are available and an option is provided for creating user-defined reactions. RT3D is well-suited for simulating natural attenuation and bioremediation.<br />
<br />
Since RT3D is a modified version of MT3DMS, most of the input to RT3D is identical to the input required for MT3DMS. Thus, the RT3D interface is contained within the ''MT3D'' menu in the 3D Grid module. In the [[GMS:Basic Transport Package Dialog|''Basic Transport Package'']] dialog, an option is provided for selecting the current model as either MT3DMS, RT3D, or SEAM3D. A number of options in the interface then change based on which model is selected.<br />
<br />
Since much of the RT3D interface is identical to the [[GMS:MT3DMS|MT3DMS Interface]], only the portions of the interface which are unique to RT3D are described in this help file.<br />
<br />
The RT3D model can be added to a [http://www.aquaveo.com/software/gms-pricing paid edition] of GMS.<br />
[[Category:Link to Store]]<br />
<br />
==Basic Transport Package==<br />
The first step in defining an RT3D simulation is to define the data required by the Basic Transport (BTN) package. The options in the [[GMS:Basic Transport Package Dialog|''Basic Transport Package'' dialog]] unique to RT3D are as follows:<br />
<br />
===Packages===<br />
The '''Packages''' button brings up the ''Packages'' dialog. If the RT3D model is the current model and the Chemical Reaction package is selected, one of the RT3D reactions must be selected from the pull-down list. The first nine reaction modules are pre-defined (specified as the IREACT value):<br />
<br />
* No reaction (tracer transport)<br />
* Inst. Aerobic Deg. of BTEX<br />
* Inst. Deg. of BTEX w/ MEA<br />
* Kinetic-Limited Deg. of BTEX w/ MEA<br />
* Rate-Limited Sorption Reactions<br />
* Double Monod Model<br />
* Sequential Decay Reactions<br />
* Aerobic/Anaerobic PCE/TCE Dechlorination<br />
* Test Model #1<br />
* Test Model #2<br />
<br />
If one of these reactions is selected, the names of the species and the names of the reaction parameters are automatically determined by GMS. The last reaction is a user-defined reaction. If this option is selected, a list of species and list of reaction parameters must be specified.<br />
<br />
===Define Species===<br />
For most of the reaction package options, once the reaction package is selected, the list of species used by the package is automatically initialized by GMS. However, if the user-defined reaction package is selected, the '''Define Species''' button is undimmed in the ''Basic Transport Package'' dialog and a list of species must be manually defined before any concentrations are assigned to sources/sinks.<br />
<br />
==Chemical Reactions Package==<br />
[[File:RT3D Chemical Reaction.png|thumb|500 px|The ''RT3D Chemical Reaction Package'' dialog]]<br />
The ''Chemical Reactions Package'' dialog utilized by RT3D is different from the ''MT3DMS Chemical Reactions'' dialog. The items in the dialog unique to RT3D are as follows:<br />
<br />
===Solver===<br />
If the selected reaction package is a kinetic reaction, several solvers are available for the solution of the chemical reaction equations. The desired solver should be selected from the ''Solver'' pull-down list. When one of these solvers is used, an absolute and relative tolerance must be specified for each of the mobile species using the atol and rtol parameters.<br />
<br />
===Reaction Parameters===<br />
With each reaction package, a set of reaction parameters must be defined. The method used to edit the reaction parameters depends on whether the reaction is a pre-defined reaction or a user-defined reaction.<br />
<br />
===Pre-Defined Reactions===<br />
For the pre-defined reactions, the number of reaction parameters and the names of the parameters are fixed. If the ''Spatially vary all'' toggle is off, a single value is entered for each parameter using the edit field below the parameter list. If the ''Spatially vary all'' toggle is on, an array of values is entered for each parameter using the '''Edit''' button. In this case, the cell-by-cell parameter values can also be edited using the '''Cell Attributes''' command.<br />
<br />
===User-Defined Reactions===<br />
For user-defined reactions, the list of reaction parameters must be defined using the '''Define Parameters''' button. This button brings up the ''Define Parameters'' dialog. This dialog functions similarly to the ''Define Species'' dialog. The '''New''' and '''Delete''' buttons are used to add and remove items from the list. The '''Import''' button is used to read a previously defined list of reaction parameters from an RT3D super file (*.rts).<br />
<br />
With the pre-defined reactions, the reaction parameters are either all spatially variable or all constant. However, with the user-defined reaction option, selected parameters may be designated as spatially variable while others are designated as constant. The variable/constant status of a parameter is selected using the ''Spatially variable'' toggle in the ''Define Parameters'' dialog.<br />
<br />
<br />
{{Navbox GMS}}<br />
[[Category:RT3D]]<br />
[[Category:3D Grid]]<br />
[[Category:GMS Dialogs|R]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=SMS:CMS-Flow&diff=118647SMS:CMS-Flow2017-01-25T22:03:51Z<p>Dharker: Linked CIRP and ERDC websites</p>
<hr />
<div>{{SMS Infobox Model |<br />
|name= CMS-Flow<br />
|model_type= Hydrodynamic model intended for local applications, primarily at inlets, the nearshore, and bays<br />
|developer= <br />
Christopher W. Reed, Ph.D. <br /><br />
Alejandro Sanchez<br /><br />
Mitchell E. Brown<br />
|web_site= http://cirpwiki.info/wiki/CMS-Flow<br />
|tutorials= <br />
General Section<br />
* Data Visualization<br />
* Observation<br />
Models Section<br />
* CMS - CMS-Flow<br />
}}<br />
<br />
CMS-Flow is a component of the Coastal Modeling System ([[SMS:CMS|CMS]]). Until 2007, it was developed under the name M2D. At that point in time, it was revised, file formats were updated for better flexibility and expandability, and it was incorporated into the CMS suite. The model developers at the United States Army Corps of Engineers (USACE) Coastal Inlets Research Program ([http://www.erdc.usace.army.mil/Missions/Water-Resources/CIRP/ CIRP]) maintain a wiki [http://cirpwiki.info/wiki/CMS-Flow here] specifically for the numerical engine. For more information on the model itself, refer to the [https://web.archive.org/web/20150926064329/http://cirp.usace.army.mil/techtransfer/workshops/nap12/Presentation/CMS_UserManual_030212_final.pdf users manual] published by the USACE Engineer Research and Development Center ([http://www.erdc.usace.army.mil/ ERDC]). <br />
<br />
The model is a finite-volume numerical engine which includes the capabilities to compute both hydrodynamics (water levels and current flow values under any combination of tide, wind, surge, waves and river flow) sediment transport as bedload, suspended load, and total load, and morphology change. The interface in SMS allows setting up and editing computational grids, specifying model parameters, defining interaction of this model with the wave counterpart ([[SMS:CMS-Wave|CMS-Wave]]), launching the model, and visualizing the results. The model is intended to be run on a project-scale, meaning the domain should only be on the order of 1&ndash;100 kilometers in length and width. The following sections describe the interface and make recommendations for application of the model.<br />
<br />
Beginning with SMS 12.1 a quadtree grid system was implemented allowing for telescoping and refinement while replacing the previous cartesian grid. Sediment transport is less stable in SMS after version 11.2. The CMS-Flow model can be added to a [http://www.aquaveo.com/software/sms-pricing paid edition] of SMS.<br />
[[Category:Link to Store]]<br />
<br />
== Graphical Interface ==<br />
CMS-Flow makes use of SMS’s simulation interface. The [[SMS:CMS-Flow Simulation|simulation interface]] works by creating a simulation object in the Project Explorer then adding components for the simulation. CMS-Flow makes use of the following components:<br />
<br />
*A [[SMS:Quadtree Module|quadtree grid]]<br />
*A CMS-Flow [[SMS:CMS-Flow_Coverages#Boundary_Conditions|Boundary Conditions]] coverage<br />
*A CMS-Flow [[SMS:CMS-Flow_Coverages#Save_Points|Save Points]] coverage (optional)<br />
*An [[SMS:Generic Coverages|Activity Classification]] coverage. (optional)<br />
<br />
The CMS-Flow simulation has its own menu commands that can be accessed by right-clicking on the simulation object. Each of the CMS-Flow coverage may also have a right-click menu to access dialogs and functions specific to the coverage or objects in the coverage. <br />
<br />
From the simulation menu, the [[SMS:CMS-Flow Model Control|CMS-Flow ''Model Control'']] dialog can be accessed. In the ''Model Control'', parameters for the simulation run can be set.<br />
<br />
== Using the Model / Practical Notes ==<br />
<br />
For new simulations, create the CMS-Flow grid based on a conceptual model. The conceptual model includes:<br />
<br />
*Grid Generation &ndash; It's recommend generate a CMS-Flow grid using the conceptual model and a Quadtree Generator coverage. This coverage has attributes associated with a two-dimensional quadtree grid and the model parameters associated with CMS-Flow. The grid position and extents are defined in the coverage using a grid frame, which can be defined with three clicks of the mouse (recommendation is to click the lower left corner, lower right corner and then upper right corner, but the position, orientation and size can all be edited during the grid generation process. The grid's ''i,j'' origin, however, will always be at the lower-left corner regardless of where the clicks are done. The coverage also defines the location of land and water in the grid using one of three methods:<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
* Land/Water cells defined based bathymetric values &ndash; CMS-Flow uses depths, so positive depth indicates water, negative depth indicates land. Cells with depth less than the negative value of the water surface are dry. This option requires a geometric survey that includes both the bathymetric area and the areas that could potentially be flooded. This is the most intuitive option and the preferred method if geometric data is available.<br />
* Land/Water interface defined by coastline arcs &ndash; This option allows defining, reading, or importing arc definitions that delineate the water area. These arcs include an orientation. To the left of the arc is land, to the right is water. If necessary, select an arc and swap its orientation. All the area inside the grid frame on the "water" side of the arc must have elevations defined either from a survey, or by specification. Cells created on the "land" side of the arc will never be included in calculations (they are permanently dry). These arcs also include an attribute defining how cells spanning this interface are to be classified. They may be forced to be water (ocean preference), forced to be land (land preference) or split based on the percentage of the cell on each side of the arc (percent preference).<br />
* Land/Water interface defined by polygons &ndash; This option also requires defining arcs that delineate the extents of the computational area. However, these arcs must be closed into polygons. Each polygon is specified to enclose land or water and cells are classified accordingly.<br />
</blockquote><br />
* Model Output &ndash; The numerical engine consists of several components. The base engine computes hydrodynamics. To this, sediment transport and salinity can be enabled as well. Each process produces spatially varied solutions (values for each wet cell) that SMS can display as [[SMS:CMS-Flow Spatial Datasets|spatial datasets]]. Additional observation cells can be created to view output at a higher temporal resolution.<br />
<br />
==CMS-Flow Files==<br />
See the article [[SMS:CMS-Flow Files|CMS-Flow Files]].<br />
<br />
Here are tables of some of the available input and output files for CMS-Flow.<br />
<br />
* For more information on these files see pages 224 and 242 of the [http://cirp.usace.army.mil/techtransfer/workshops/nap12/Presentation/CMS_UserManual_030212_final.pdf#page=242 manual].<br />
<br />
{| class="wikitable" <br />
|+'''Required Input Files'''<br />
!width="40" align="center"|Name<br />
!width="200" align="center"|Description<br />
|-<br />
|DB3||dBASE III<br />
|-<br />
|_Depth.H5||Grid Depth Values XMDF<br />
|-<br />
|_Quadtrees.H5||Telescoping Grid<br />
|-<br />
|MAP||Grid and Projection Information<br />
|-<br />
|MATERIALS||Material Values<br />
|-<br />
|VTU||Visual Toolkit Unstructured Mesh<br />
|-<br />
|}<br />
<br />
{| class="wikitable"<br />
|+'''Output Files'''<br />
!align="center" width="50"|Name<br />
!width="200"|Description<br />
|-<br />
|CMCARDS||Coastal Modeling Card Settings<br />
|-<br />
|Hot_Start.H5||Hot Start Information<br />
|-<br />
|_Datasets.H5||Mannings Number Dataset<br />
|-<br />
|_Diag.H5||Diagnostic Solutions XMDF<br />
|-<br />
|_MP.H5||Model Parameters XMDF<br />
|-<br />
|_Vel.H5||Current Velocity XMDF<br />
|-<br />
|_WSE.H5||Water Surface Elevation XMDF<br />
|-<br />
|TEL||Telescoping Quadtree Mesh<br />
|-<br />
|TXT||Output Text<br />
|-<br />
|}<br />
<br />
== Case Studies / Sample Problems ==<br />
The following [[SMS:Tutorials|tutorials]] may be helpful for learning to use CMS-Flow in SMS:<br />
* Models Section<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
* CMS &ndash; CMS-Flow<br />
</blockquote><br />
<br />
== Related Links ==<br />
* [[SMS:SMS Models|SMS Models page]]<br />
* [[SMS:CMS-Wave|CMS-Wave]]<br />
* [[SMS:CMS-Flow/CMS-Wave Steering]] for running CMS-Flow with the results from CMS-Wave<br />
<br />
== External Links ==<br />
* [https://web.archive.org/web/20150926064329/http://cirp.usace.army.mil/techtransfer/workshops/nap12/Presentation/CMS_UserManual_030212_final.pdf CMS-FLOW Users Manual]<br />
* Sep 2008 Modeling of Morphologic Changes Caused by Inlet Management Strategies at Big Sarasota Pass, Florida [http://www.fsbpa.com/08Proceedings/07AlymovTruittPoffAnderson2008.pdf]<br />
* Jul 2007 ERDC/CHL CHETN-IV-69 Tips for Developing Bathymetry Grids for Coastal Modeling System Applications [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-69.pdf]<br />
* Aug 2006 ERDC/CHL TR-06-9 Two-Dimensional Depth-Averaged Circulation Model CMS-M2D: Version 3.0, Report 2, Sediment Transport and Morphology Change [http://cirp.usace.army.mil/Downloads/PDF/TR-06-9.pdf]<br />
* Feb 2006 ERDC/CHL CHETN-IV-67 Frequently-Asked Questions (FAQs) About Coastal Inlets and U.S. Army Corps of Engineers' Coastal Inlets Research Program (CIRP) [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-67.pdf] Updated FAQ Website [http://cirp.usace.army.mil/pubs/FAQs/FAQ.html]<br />
* May 2005 ERDC/CHL CHETN-IV-63 Representation of Nonerodible (Hard) Bottom in Two-Dimensional Morphology Change Models [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-63.pdf]<br />
* May 2004 ERDC/CHL TR-04-2 Two-Dimensional Depth-Averaged Circulation Model M2D: Version 2.0, Report 1, Technical Documentation and User’s Guide [http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=PUBLICATIONS!155]<br />
* Dec 2003 ERDC/CHL CHETN-IV-60 SMS Steering Module for Coupling Waves and Currents, 2: M2D and STWAVE [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-60.pdf]<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
<br />
[[Category:CMS-Flow]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=SMS:CMS-Flow&diff=118646SMS:CMS-Flow2017-01-25T21:59:06Z<p>Dharker: Defined initialisms and added CIRP info</p>
<hr />
<div>{{SMS Infobox Model |<br />
|name= CMS-Flow<br />
|model_type= Hydrodynamic model intended for local applications, primarily at inlets, the nearshore, and bays<br />
|developer= <br />
Christopher W. Reed, Ph.D. <br /><br />
Alejandro Sanchez<br /><br />
Mitchell E. Brown<br />
|web_site= http://cirpwiki.info/wiki/CMS-Flow<br />
|tutorials= <br />
General Section<br />
* Data Visualization<br />
* Observation<br />
Models Section<br />
* CMS - CMS-Flow<br />
}}<br />
<br />
CMS-Flow is a component of the Coastal Modeling System ([[SMS:CMS|CMS]]). Until 2007, it was developed under the name M2D. At that point in time, it was revised, file formats were updated for better flexibility and expandability, and it was incorporated into the CMS suite. The model developers at the United States Army Corps of Engineers (USACE) Coastal Inlets Research Program (CIRP) maintain a wiki [http://cirpwiki.info/wiki/CMS-Flow here] specifically for the numerical engine. For more information on the model itself, refer to the [https://web.archive.org/web/20150926064329/http://cirp.usace.army.mil/techtransfer/workshops/nap12/Presentation/CMS_UserManual_030212_final.pdf users manual] published by the USACE Engineer Research and Development Center (ERDC). <br />
<br />
The model is a finite-volume numerical engine which includes the capabilities to compute both hydrodynamics (water levels and current flow values under any combination of tide, wind, surge, waves and river flow) sediment transport as bedload, suspended load, and total load, and morphology change. The interface in SMS allows setting up and editing computational grids, specifying model parameters, defining interaction of this model with the wave counterpart ([[SMS:CMS-Wave|CMS-Wave]]), launching the model, and visualizing the results. The model is intended to be run on a project-scale, meaning the domain should only be on the order of 1&ndash;100 kilometers in length and width. The following sections describe the interface and make recommendations for application of the model.<br />
<br />
Beginning with SMS 12.1 a quadtree grid system was implemented allowing for telescoping and refinement while replacing the previous cartesian grid. Sediment transport is less stable in SMS after version 11.2. The CMS-Flow model can be added to a [http://www.aquaveo.com/software/sms-pricing paid edition] of SMS.<br />
[[Category:Link to Store]]<br />
<br />
== Graphical Interface ==<br />
CMS-Flow makes use of SMS’s simulation interface. The [[SMS:CMS-Flow Simulation|simulation interface]] works by creating a simulation object in the Project Explorer then adding components for the simulation. CMS-Flow makes use of the following components:<br />
<br />
*A [[SMS:Quadtree Module|quadtree grid]]<br />
*A CMS-Flow [[SMS:CMS-Flow_Coverages#Boundary_Conditions|Boundary Conditions]] coverage<br />
*A CMS-Flow [[SMS:CMS-Flow_Coverages#Save_Points|Save Points]] coverage (optional)<br />
*An [[SMS:Generic Coverages|Activity Classification]] coverage. (optional)<br />
<br />
The CMS-Flow simulation has its own menu commands that can be accessed by right-clicking on the simulation object. Each of the CMS-Flow coverage may also have a right-click menu to access dialogs and functions specific to the coverage or objects in the coverage. <br />
<br />
From the simulation menu, the [[SMS:CMS-Flow Model Control|CMS-Flow ''Model Control'']] dialog can be accessed. In the ''Model Control'', parameters for the simulation run can be set.<br />
<br />
== Using the Model / Practical Notes ==<br />
<br />
For new simulations, create the CMS-Flow grid based on a conceptual model. The conceptual model includes:<br />
<br />
*Grid Generation &ndash; It's recommend generate a CMS-Flow grid using the conceptual model and a Quadtree Generator coverage. This coverage has attributes associated with a two-dimensional quadtree grid and the model parameters associated with CMS-Flow. The grid position and extents are defined in the coverage using a grid frame, which can be defined with three clicks of the mouse (recommendation is to click the lower left corner, lower right corner and then upper right corner, but the position, orientation and size can all be edited during the grid generation process. The grid's ''i,j'' origin, however, will always be at the lower-left corner regardless of where the clicks are done. The coverage also defines the location of land and water in the grid using one of three methods:<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
* Land/Water cells defined based bathymetric values &ndash; CMS-Flow uses depths, so positive depth indicates water, negative depth indicates land. Cells with depth less than the negative value of the water surface are dry. This option requires a geometric survey that includes both the bathymetric area and the areas that could potentially be flooded. This is the most intuitive option and the preferred method if geometric data is available.<br />
* Land/Water interface defined by coastline arcs &ndash; This option allows defining, reading, or importing arc definitions that delineate the water area. These arcs include an orientation. To the left of the arc is land, to the right is water. If necessary, select an arc and swap its orientation. All the area inside the grid frame on the "water" side of the arc must have elevations defined either from a survey, or by specification. Cells created on the "land" side of the arc will never be included in calculations (they are permanently dry). These arcs also include an attribute defining how cells spanning this interface are to be classified. They may be forced to be water (ocean preference), forced to be land (land preference) or split based on the percentage of the cell on each side of the arc (percent preference).<br />
* Land/Water interface defined by polygons &ndash; This option also requires defining arcs that delineate the extents of the computational area. However, these arcs must be closed into polygons. Each polygon is specified to enclose land or water and cells are classified accordingly.<br />
</blockquote><br />
* Model Output &ndash; The numerical engine consists of several components. The base engine computes hydrodynamics. To this, sediment transport and salinity can be enabled as well. Each process produces spatially varied solutions (values for each wet cell) that SMS can display as [[SMS:CMS-Flow Spatial Datasets|spatial datasets]]. Additional observation cells can be created to view output at a higher temporal resolution.<br />
<br />
==CMS-Flow Files==<br />
See the article [[SMS:CMS-Flow Files|CMS-Flow Files]].<br />
<br />
Here are tables of some of the available input and output files for CMS-Flow.<br />
<br />
* For more information on these files see pages 224 and 242 of the [http://cirp.usace.army.mil/techtransfer/workshops/nap12/Presentation/CMS_UserManual_030212_final.pdf#page=242 manual].<br />
<br />
{| class="wikitable" <br />
|+'''Required Input Files'''<br />
!width="40" align="center"|Name<br />
!width="200" align="center"|Description<br />
|-<br />
|DB3||dBASE III<br />
|-<br />
|_Depth.H5||Grid Depth Values XMDF<br />
|-<br />
|_Quadtrees.H5||Telescoping Grid<br />
|-<br />
|MAP||Grid and Projection Information<br />
|-<br />
|MATERIALS||Material Values<br />
|-<br />
|VTU||Visual Toolkit Unstructured Mesh<br />
|-<br />
|}<br />
<br />
{| class="wikitable"<br />
|+'''Output Files'''<br />
!align="center" width="50"|Name<br />
!width="200"|Description<br />
|-<br />
|CMCARDS||Coastal Modeling Card Settings<br />
|-<br />
|Hot_Start.H5||Hot Start Information<br />
|-<br />
|_Datasets.H5||Mannings Number Dataset<br />
|-<br />
|_Diag.H5||Diagnostic Solutions XMDF<br />
|-<br />
|_MP.H5||Model Parameters XMDF<br />
|-<br />
|_Vel.H5||Current Velocity XMDF<br />
|-<br />
|_WSE.H5||Water Surface Elevation XMDF<br />
|-<br />
|TEL||Telescoping Quadtree Mesh<br />
|-<br />
|TXT||Output Text<br />
|-<br />
|}<br />
<br />
== Case Studies / Sample Problems ==<br />
The following [[SMS:Tutorials|tutorials]] may be helpful for learning to use CMS-Flow in SMS:<br />
* Models Section<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
* CMS &ndash; CMS-Flow<br />
</blockquote><br />
<br />
== Related Links ==<br />
* [[SMS:SMS Models|SMS Models page]]<br />
* [[SMS:CMS-Wave|CMS-Wave]]<br />
* [[SMS:CMS-Flow/CMS-Wave Steering]] for running CMS-Flow with the results from CMS-Wave<br />
<br />
== External Links ==<br />
* [https://web.archive.org/web/20150926064329/http://cirp.usace.army.mil/techtransfer/workshops/nap12/Presentation/CMS_UserManual_030212_final.pdf CMS-FLOW Users Manual]<br />
* Sep 2008 Modeling of Morphologic Changes Caused by Inlet Management Strategies at Big Sarasota Pass, Florida [http://www.fsbpa.com/08Proceedings/07AlymovTruittPoffAnderson2008.pdf]<br />
* Jul 2007 ERDC/CHL CHETN-IV-69 Tips for Developing Bathymetry Grids for Coastal Modeling System Applications [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-69.pdf]<br />
* Aug 2006 ERDC/CHL TR-06-9 Two-Dimensional Depth-Averaged Circulation Model CMS-M2D: Version 3.0, Report 2, Sediment Transport and Morphology Change [http://cirp.usace.army.mil/Downloads/PDF/TR-06-9.pdf]<br />
* Feb 2006 ERDC/CHL CHETN-IV-67 Frequently-Asked Questions (FAQs) About Coastal Inlets and U.S. Army Corps of Engineers' Coastal Inlets Research Program (CIRP) [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-67.pdf] Updated FAQ Website [http://cirp.usace.army.mil/pubs/FAQs/FAQ.html]<br />
* May 2005 ERDC/CHL CHETN-IV-63 Representation of Nonerodible (Hard) Bottom in Two-Dimensional Morphology Change Models [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-63.pdf]<br />
* May 2004 ERDC/CHL TR-04-2 Two-Dimensional Depth-Averaged Circulation Model M2D: Version 2.0, Report 1, Technical Documentation and User’s Guide [http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=PUBLICATIONS!155]<br />
* Dec 2003 ERDC/CHL CHETN-IV-60 SMS Steering Module for Coupling Waves and Currents, 2: M2D and STWAVE [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-60.pdf]<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
<br />
[[Category:CMS-Flow]]<br />
[[Category:External Links]]</div>Dharkerhttps://www.xmswiki.com/index.php?title=GMS:RT3D&diff=118570GMS:RT3D2017-01-25T00:35:06Z<p>Dharker: /* Packages */</p>
<hr />
<div>{{Infobox Model |<br />
|name= RT3D <br />
|model_type= multi-species reactive transport<br />
|developer= Battelle Pacific Northwest National Laboratory <br />
|documentation= [http://gmsdocs.aquaveo.com/rt3dman.pdf RT3D Manual v1] [http://gmsdocs.aquaveo.com/rt3dv2.5man.pdf RT3D Manual v2.5]<br />
|tutorials= [[GMS:Tutorials#Models|RT3D Tutorials]]<br />
}}<br />
RT3D is a multi-species reactive transport model developed by the Battelle Pacific Northwest National Laboratory. RT3D is a modified version of MT3DMS that utilizes alternate Chemical Reaction packages. Numerous pre-defined reactions are available and an option is provided for creating user-defined reactions. RT3D is well-suited for simulating natural attenuation and bioremediation.<br />
<br />
Since RT3D is a modified version of MT3DMS, most of the input to RT3D is identical to the input required for MT3DMS. Thus, the RT3D interface is contained within the ''MT3D'' menu in the 3D Grid module. In the [[GMS:Basic Transport Package Dialog|''Basic Transport Package'']] dialog, an option is provided for selecting the current model as either MT3DMS, RT3D, or SEAM3D. A number of options in the interface then change based on which model is selected.<br />
<br />
Since much of the RT3D interface is identical to the [[GMS:MT3DMS|MT3DMS Interface]], only the portions of the interface which are unique to RT3D are described in this help file.<br />
<br />
The RT3D model can be added to a [http://www.aquaveo.com/software/gms-pricing paid edition] of GMS.<br />
[[Category:Link to Store]]<br />
<br />
==Basic Transport Package==<br />
The first step in defining an RT3D simulation is to define the data required by the Basic Transport (BTN) package. The options in the [[GMS:Basic Transport Package Dialog|''Basic Transport Package'' dialog]] unique to RT3D are as follows:<br />
<br />
===Packages===<br />
The '''Packages''' button brings up the ''Packages'' dialog. If the RT3D model is the current model and the Chemical Reaction package is selected, one of the RT3D reactions must be selected from the pull-down list. The first nine reaction modules are pre-defined (specified as the IREACT value):<br />
<br />
* No reaction (tracer transport)<br />
* Inst. Aerobic Deg. of BTEX<br />
* Inst. Deg. of BTEX w/ MEA<br />
* Kinetic-Limited Deg. of BTEX w/ MEA<br />
* Rate-Limited Sorption Reactions<br />
* Double Monod Model<br />
* Sequential Decay Reactions<br />
* Aerobic/Anaerobic PCE/TCE Dechlorination<br />
* Test Model #1<br />
* Test Model #2<br />
<br />
If one of these reactions is selected, the names of the species and the names of the reaction parameters are automatically determined by GMS. The last reaction is a user-defined reaction. If this option is selected, a list of species and list of reaction parameters must be specified.<br />
<br />
===Define Species===<br />
For most of the reaction package options, once the reaction package is selected, the list of species used by the package is automatically initialized by GMS. However, if the user-defined reaction package is selected, the '''Define Species''' button is undimmed in the ''Basic Transport Package'' dialog and a list of species must be manually defined before any concentrations are assigned to sources/sinks.<br />
<br />
==Chemical Reactions Package==<br />
[[File:RT3D Chemical Reaction.png|thumb|500 px|The ''RT3D Chemical Reaction Package'' dialog]]<br />
The ''Chemical Reactions Package'' dialog utilized by RT3D is different from the ''MT3DMS Chemical Reactions'' dialog. The items in the dialog unique to RT3D are as follows:<br />
<br />
===Solver===<br />
If the selected reaction package is a kinetic reaction, several solvers are available for the solution of the chemical reaction equations. The desired solver should be selected from the ''Solver'' pull-down list. When one of these solvers is used, an absolute and relative tolerance must be specified for each of the mobile species using the atol and rtol parameters.<br />
<br />
===Reaction Parameters===<br />
With each reaction package, a set of reaction parameters must be defined. The method used to edit the reaction parameters depends on whether the reaction is a pre-defined reaction or a user-defined reaction.<br />
<br />
===Pre-Defined Reactions===<br />
For the pre-defined reactions, the number of reaction parameters and the names of the parameters are fixed. If the ''Spatially vary all'' toggle is off, a single value is entered for each parameter using the edit field below the parameter list. If the ''Spatially vary all'' toggle is on, an array of values is entered for each parameter using the '''Edit''' button. In this case, the cell-by-cell parameter values can also be edited using the '''Cell Attributes''' command.<br />
<br />
===User-Defined Reactions===<br />
For user-defined reactions, the list of reaction parameters must be defined using the '''Define Parameters''' button. This button brings up the ''Define Parameters'' dialog. This dialog functions similarly to the ''Define Species'' dialog. The '''New''' and '''Delete''' buttons are used to add and remove items from the list. The '''Import''' button is used to read a previously defined list of reaction parameters from an RT3D super file (*.rts).<br />
<br />
With the pre-defined reactions, the reaction parameters are either all spatially variable or all constant. However, with the user-defined reaction option, selected parameters may be designated as spatially variable while others are designated as constant. The variable/constant status of a parameter is selected using the ''Spatially variable'' toggle in the ''Define Parameters'' dialog.<br />
<br />
<br />
{{Navbox GMS}}<br />
[[Category:RT3D]]<br />
[[Category:3D Grid]]<br />
[[Category:GMS Dialogs|R]]<br />
[[Category:External Links]]</div>Dharker