https://www.xmswiki.com/api.php?action=feedcontributions&user=Wood&feedformat=atomXMS Wiki - User contributions [en]2024-03-29T05:53:35ZUser contributionsMediaWiki 1.39.0https://www.xmswiki.com/index.php?title=SMS:SRH-2D_Errors&diff=142150SMS:SRH-2D Errors2019-09-09T23:04:09Z<p>Wood: /* List of Error Messages */</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 />
An error may occur during either the Pre-SRH-2D process or during the SRH-2D process. During the run, errors will be listed in the SRH-2D model wrapper. Clicking the PreSRH-2D button in the model wrapper will display results from the pre-processor. Clicking the SRH-2D button will show results from the model run.<br />
<br />
If the model wrapper has been closed, two files are generated recording the model run. Opening the "*_.OUT.dat" or the "*_DIA.dat" files in a text editor will show errors in 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 Pre-processor 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 spline.f90 H<br />
| Time series data used to define inflows/outflows or time varying water surface elevations has issues with how it is defined, such as duplicate times. <br />
| The time series data should only have one data value per defined time. Go to the XY series editor where the time series data is defined and remove any and every duplicate time entry.<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 need 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 />
| In SMS v12.1, 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. Modify the placement of the structure arcs in the boundary condition coverage or unassigned material polygon edges so that the snap preview of the material polygon matches the snap preview of the structure arc. In SMS 12.2 or later, it is not necessary to create the unassigned material polygon to disable the area between the structure arcs because SRH-2D has been modified to do this internally. If encountering this error using 12.2 or later, one possible solution would be to delete the unassigned material polygon, rebuild polygons and double check all polygons to make sure valid material types have been assigned.<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 />
| Pre SRH-2D<br />
| <br />
| Errors from final_touch.f90 **** on MONITOR LINE#n<br> a face cannot be found given two mesh points<br><br />
Two points are: xx xx<br><br />
Check the mesh node list; do this using _SIF.dat file directly!<br />
| Monitor line spans a mesh void (hole)<br />
| Reconfigure the monitor line. Monitor lines cannot span holes in the mesh.<br />
|-<br />
| SRH-2D<br />
| <br />
| <br />
| If there is 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 />
| Material polygons near inflow are unassigned<br />
| This occurs when the material coverage has not been linked to the simulation. Also occurs when all material polygons covering the inflow BC are have an "unassigned" material type. This can also occur if no boundary conditions providing an inflow source have been included in the simulation.<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 computational time step in the model control<br />
|-<br />
| SRH-2D<br />
| 3<br />
| bad mesh ! Stopped in indx_conn.f<br />
| Problem in mesh, often due to overlapping elements. <br />
| Check if problem cell (element) id is listed. Otherwise, examine mesh quality in SMS.<br />
|-<br />
| SMS<br />
| <br />
| No mesh that matches the scalar set.<br />
| No mesh that matches the scalar set. The solution file does not correspond to the mesh in the project, or node numbering of the mesh has been changed, invalidating the solution.<br />
| Take care when making edits to the mesh and renumbering the nodes. Any previous results will be invalidated when nodes are renumbered.<br />
|-<br />
| <br />
| None<br />
| None<br />
| WSE error directly under the bridge in the form of waves oscillating through the channel<br />
| Use larger, quadrilateral elements in the deepest areas of flow. This could also mean that the piers need to be switched to obstructions. Lowering the time step may also help.<br />
|-<br />
|-<br />
| <br />
| None<br />
| None<br />
| SRH-2D is not recognizing a 1D structure or 2D pressure flow structure. When reviewing the 2D results or output files it does not appear that SRH-2D is using a structure such as a culvert, pressure flow bridge structure, weir, or gate.<br />
| Make sure the pair of arcs in the SRH-2D boundary condition coverage representing the faces of the structure were created in the same topologic direction. (i.e. Both were created left to right looking downstream or both were created right to left downstream.) The direction does not matter, just that both arcs are consistent. Turn on the display of arc "Direction" in the display options for the map arcs. This will add an arrow to the map arcs in the display denoting their topologic direction.<br />
|-<br />
| SMS<br />
| <br />
| The following coverage(s) have an unsupported type and will be converted to area property: ''(Name of Coverage(s) Listed)''<br />
| <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), further troubleshooting is required if it has not finished running successfully.<br />
|-<br />
| <br />
| 1<br />
| Error code 1<br />
| srhmat file does not exist<br />
| File didn't export successfully. Make sure materials are assigned in the materials coverage.<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 />
| 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. Also, check snapping of BC arcs.<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 the 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 />
| SRH-2D<br />
| 1<br />
| Stopped in structure_pressure_flow.f90 PARA DISTANCE<br />
| Shape of pressure zone is not acceptable for a parabolic type bridge ceiling<br />
| Ensure that the pressure zone, between the pressure flow arcs, is rectangular in shape<br />
|-<br />
| SRH-2D<br />
| 9669<br />
| Program stopped due to the following:<br />
Wrong IFACE matching occurred in structure_internal.f90 #4<br />
Error Code is: 9669<br />
| Ensure that the area between the pressure zone arcs with overtopping turned on is rectangular in shape and that the elements in between the arcs are quads (rectangles).<br />
| Create a new mesh with a rectangle between pressure flow arcs and which has quads in this area using the patch mesh generation method.<br />
|-<br />
|-<br />
| SRH-2D<br />
| 46631<br />
| Program stopped due to the following:<br />
Wrong IFACE matching occurred in structure_internal.f90 #4<br />
Error Code is: 46631<br />
| Ensure that the area between the pressure zone arcs with overtopping turned on is rectangular in shape and that the elements in between the arcs are quads (rectangles).<br />
| Create a new mesh with a rectangle between pressure flow arcs and which has quads in this area using the patch mesh generation method.<br />
|-<br />
|-<br />
| SRH-2D<br />
| 0<br />
| Program stopped due to the following:<br />
Wrong IFACE matching occurred in structure_internal.f90 #4<br />
Error Code is: 0<br />
| BC arc is not snapped properly between nodes along element edges with varying elevations.<br />
| Either modify the mesh to smooth elevations or redistribute vertices along BC arc and assign elevations that match mesh element edges (the "Scatter | Interpolate to Map" feature can be used to vary elevations along an existing BC arc).<br />
|-<br />
| SRH-2D<br />
| 16026<br />
| Program stopped due to the following: <br />
A downstream Structure nodestring has not set right; structure_culvert.f90 ICELL error#2<br />
Error Code is: 16026<br />
| The 2D mesh around and through the structure is not optimal.<br />
| Re-mesh areas around the structure. Suggestions to optimize the mesh around the structure include creating patched (quadrilateral) elements through the structure from one face to the other. SRH-2D inactivates elements between the structure faces where the 1D flow is computed. Creating quadrilateral elements in the zone between the faces facilitates the process SRH uses to locate and inactivate the flow computations for those elements in the mesh. Configure the mesh such that the structure faces can be created alone a series of element edges that are oriented in the same direction (along a flat and straight line of element edges).<br />
|-<br />
| SRH-2D<br />
| 79<br />
| Program stopped due to the following:<br />
Tailwater WSE exceeded the maximum TW in the Reverse HY8 Table structure_hy8.f90<br />
Error Code is: 79<br />
| Computed water surface elevations near the culvert become extremely high. This could be from too large of a time step, poor mesh quality near the culvert faces, or parts of the mesh were the culvert is applied have higher elevations than what are defined as the inverts defined in the HY-8 culvert definition<br />
| Review mesh quality near the culvert face. Check to ensure that mesh node elevations where culvert faces are applied do not exceed invert elevations as defined in the HY8 culvert definition. Lowering the time step to improve stability around the culvert could also help.<br />
|-<br />
| SRH-2D<br />
| N/A<br />
| forrtl: severe (24): end-of-file during read, unit n, file {your filepath.dat} Image PC Routine Line Source srh2d_3.2_quickwi...Unknown...<br />
| This is usually a generic error indicating something is wrong with the SRH simulation casename.DAT file created by SRH pre. It typically signifies that SRH-Pre did not terminate normally and generate a valid simulation file. The cause of the error could be any number of issues.<br />
| Check for any error messages reported by SRH-pre by going to the SMS model wrapper and clicking on the "PreSRH-2D" line and reviewing the on screen output messages.<br />
|-<br />
| SRH-2D<br />
| 1<br />
| Program stopped due to the following: Stopped in read_input2: Mismatch in HY8 ID<br />
| This is a bug in SRH caused by having two culvert crossings defined in the *.hy8 crossing file with certain similarities in their names.<br />
| The temporary workaround until this is fixed is to make all crossing names as different as possible, including the first character of the names. For example, "My Culvert" and "My Culvert1" could cause this error. Change one of the crossings to make it different, something like "My Culvert" and "Two Barrel Wingwall" would resolve the issue.<br />
|-<br />
| SRH-2D<br />
| N/A<br />
| Failed to find a mesh cell which contains the following (x y) points: (X,Y)=<br />
| This is caused when there is a void added to the mesh by deleting a mesh element from the mesh after the mesh has been generated. Creating void by deleting mesh elements may not actually remove the element data from the mesh in SRH-2D. <br />
|If a void is needed in the mesh, it should be created as a polygon in the Mesh Generator coverage and given a mesh type of "None". When a mesh is generated using polygons with the "None" type, a void will be created in the mesh that can be recognized by SRH-2D.<br />
|-<br />
| SRH-2D<br />
| 0<br />
| Program stopped due to the following: IFACE match does not found in structure_culvert.f90 #''n''<br />
| Element configuration around the structure face is causing a mismatch in the transition into or out of the structure.<br />
| It may help to ensure all elements within the two structures are quadrilateral elements. It may also help to ensure that the first row of elements downstream of the downstream structure face and upstream of the upstream structure face are also quadrilateral elements that are "well formed" ("Well formed" elements as in having interior corners as close to 90 degrees as possible).<br />
|-<br />
| SRH-2D<br />
| 1<br />
| Program stopped due to the following: Stopped in read_input2.f90 HY8 Forward_TABLE Line Error<br />
| There is a problem reading the culvert table file. One of the causes of this is that the HY8 file containing the culvert definition does not include a file extension.<br />
| Add a ".hy8" file extension to the culvert defintion filename.<br />
|-<br />
|SRH-2D<br />
|N/A<br />
|forrtl: severe (170): Program Exception - stack overflow<br />
|The simulation is too large for SRH-2D to process. Typically this occurs when running a simulation using sediment transport and a 2D mesh that contains more than 50,000 elements.<br />
|Reduce the number of elements in the 2D mesh and try running the simulation again.<br />
|-<br />
|SRH-2D<br />
| 3<br />
| Not ready in solve.f90 SEDIMENT MODULE<br />
| This errors occurs when sediment transport is being modeled in a project containing 1D hydraulic structures (culverts, weirs, pressure bridges, etc.). SRH-2D cannot model sediment transport in models containing 1D hydraulic structures.<br />
| Either do not use the sediment transport in the model run, or remove the 1D hydraulic structures from the model.<br />
|-<br />
|PreSRH-2D<br />
| 4<br />
| Program stopped due to the following: Stopped in sec_blow NLAY Error Code is: 4<br />
| This errors occurs when sediment transport is on and there are more than the maximum number of allowed sediment layers (9) for one or more sediment materials.<br />
| Reduce the number of sediment layers to 9 or less in each sediment material.<br />
|-<br />
|SRH-2D<br />
| 1<br />
| Program stopped due to the following: Wrong Boundary ID;may due to some boundary mesh points are not in NODESTRING lists in SMS<br />
| This error seems to be related to issues with mesh quality. <br />
| Review mesh quality. Check for elements with interior angles greater than 180 (if any are present adjust conceptual model so no elements have interior angles greater than 180).<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>Woodhttps://www.xmswiki.com/index.php?title=SMS:SRH-2D_Errors&diff=140697SMS:SRH-2D Errors2019-08-01T20:38:42Z<p>Wood: /* List of Error Messages */</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 />
An error may occur during either the Pre-SRH-2D process or during the SRH-2D process. During the run, errors will be listed in the SRH-2D model wrapper. Clicking the PreSRH-2D button in the model wrapper will display results from the pre-processor. Clicking the SRH-2D button will show results from the model run.<br />
<br />
If the model wrapper has been closed, two files are generated recording the model run. Opening the "*_.OUT.dat" or the "*_DIA.dat" files in a text editor will show errors in 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 Pre-processor 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 spline.f90 H<br />
| Time series data used to define inflows/outflows or time varying water surface elevations has issues with how it is defined, such as duplicate times. <br />
| The time series data should only have one data value per defined time. Go to the XY series editor where the time series data is defined and remove any and every duplicate time entry.<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 need 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 />
| In SMS v12.1, 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. Modify the placement of the structure arcs in the boundary condition coverage or unassigned material polygon edges so that the snap preview of the material polygon matches the snap preview of the structure arc. In SMS 12.2 or later, it is not necessary to create the unassigned material polygon to disable the area between the structure arcs because SRH-2D has been modified to do this internally. If encountering this error using 12.2 or later, one possible solution would be to delete the unassigned material polygon, rebuild polygons and double check all polygons to make sure valid material types have been assigned.<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 />
| Pre SRH-2D<br />
| <br />
| Errors from final_touch.f90 **** on MONITOR LINE#n<br> a face cannot be found given two mesh points<br><br />
Two points are: xx xx<br><br />
Check the mesh node list; do this using _SIF.dat file directly!<br />
| Monitor line spans a mesh void (hole)<br />
| Reconfigure the monitor line. Monitor lines cannot span holes in the mesh.<br />
|-<br />
| SRH-2D<br />
| <br />
| <br />
| If there is 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 />
| Material polygons near inflow are unassigned<br />
| This occurs when the material coverage has not been linked to the simulation. Also occurs when all material polygons covering the inflow BC are have an "unassigned" material type. This can also occur if no boundary conditions providing an inflow source have been included in the simulation.<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 computational time step in the model control<br />
|-<br />
| SRH-2D<br />
| 3<br />
| bad mesh ! Stopped in indx_conn.f<br />
| Problem in mesh, often due to overlapping elements. <br />
| Check if problem cell (element) id is listed. Otherwise, examine mesh quality in SMS.<br />
|-<br />
| SMS<br />
| <br />
| No mesh that matches the scalar set.<br />
| No mesh that matches the scalar set. The solution file does not correspond to the mesh in the project, or node numbering of the mesh has been changed, invalidating the solution.<br />
| Take care when making edits to the mesh and renumbering the nodes. Any previous results will be invalidated when nodes are renumbered.<br />
|-<br />
| <br />
| None<br />
| None<br />
| WSE error directly under the bridge in the form of waves oscillating through the channel<br />
| Use larger, quadrilateral elements in the deepest areas of flow. This could also mean that the piers need to be switched to obstructions. Lowering the time step may also help.<br />
|-<br />
|-<br />
| <br />
| None<br />
| None<br />
| SRH-2D is not recognizing a 1D structure or 2D pressure flow structure. When reviewing the 2D results or output files it does not appear that SRH-2D is using a structure such as a culvert, pressure flow bridge structure, weir, or gate.<br />
| Make sure the pair of arcs in the SRH-2D boundary condition coverage representing the faces of the structure were created in the same topologic direction. (i.e. Both were created left to right looking downstream or both were created right to left downstream.) The direction does not matter, just that both arcs are consistent. Turn on the display of arc "Direction" in the display options for the map arcs. This will add an arrow to the map arcs in the display denoting their topologic direction.<br />
|-<br />
| SMS<br />
| <br />
| The following coverage(s) have an unsupported type and will be converted to area property: ''(Name of Coverage(s) Listed)''<br />
| <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), further troubleshooting is required if it has not finished running successfully.<br />
|-<br />
| <br />
| 1<br />
| Error code 1<br />
| srhmat file does not exist<br />
| File didn't export successfully. Make sure materials are assigned in the materials coverage.<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 />
| 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 />
| 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 the 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 />
| SRH-2D<br />
| 1<br />
| Stopped in structure_pressure_flow.f90 PARA DISTANCE<br />
| Shape of pressure zone is not acceptable for a parabolic type bridge ceiling<br />
| Ensure that the pressure zone, between the pressure flow arcs, is rectangular in shape<br />
|-<br />
| SRH-2D<br />
| 9669<br />
| Program stopped due to the following:<br />
Wrong IFACE matching occurred in structure_internal.f90 #4<br />
Error Code is: 9669<br />
| Ensure that the area between the pressure zone arcs with overtopping turned on is rectangular in shape and that the elements in between the arcs are quads (rectangles).<br />
| Create a new mesh with a rectangle between pressure flow arcs and which has quads in this area using the patch mesh generation method.<br />
|-<br />
|-<br />
| SRH-2D<br />
| 46631<br />
| Program stopped due to the following:<br />
Wrong IFACE matching occurred in structure_internal.f90 #4<br />
Error Code is: 46631<br />
| Ensure that the area between the pressure zone arcs with overtopping turned on is rectangular in shape and that the elements in between the arcs are quads (rectangles).<br />
| Create a new mesh with a rectangle between pressure flow arcs and which has quads in this area using the patch mesh generation method.<br />
|-<br />
|-<br />
| SRH-2D<br />
| 0<br />
| Program stopped due to the following:<br />
Wrong IFACE matching occurred in structure_internal.f90 #4<br />
Error Code is: 0<br />
| BC arc is not snapped properly between nodes along element edges with varying elevations.<br />
| Either modify the mesh to smooth elevations or redistribute vertices along BC arc and assign elevations that match mesh element edges (the "Scatter | Interpolate to Map" feature can be used to vary elevations along an existing BC arc).<br />
|-<br />
| SRH-2D<br />
| 16026<br />
| Program stopped due to the following: <br />
A downstream Structure nodestring has not set right; structure_culvert.f90 ICELL error#2<br />
Error Code is: 16026<br />
| The 2D mesh around and through the structure is not optimal.<br />
| Re-mesh areas around the structure. Suggestions to optimize the mesh around the structure include creating patched (quadrilateral) elements through the structure from one face to the other. SRH-2D inactivates elements between the structure faces where the 1D flow is computed. Creating quadrilateral elements in the zone between the faces facilitates the process SRH uses to locate and inactivate the flow computations for those elements in the mesh. Configure the mesh such that the structure faces can be created alone a series of element edges that are oriented in the same direction (along a flat and straight line of element edges).<br />
|-<br />
| SRH-2D<br />
| 79<br />
| Program stopped due to the following:<br />
Tailwater WSE exceeded the maximum TW in the Reverse HY8 Table structure_hy8.f90<br />
Error Code is: 79<br />
| Computed water surface elevations near the culvert become extremely high. This could be from too large of a time step, poor mesh quality near the culvert faces, or parts of the mesh were the culvert is applied have higher elevations than what are defined as the inverts defined in the HY-8 culvert definition<br />
| Review mesh quality near the culvert face. Check to ensure that mesh node elevations where culvert faces are applied do not exceed invert elevations as defined in the HY8 culvert definition. Lowering the time step to improve stability around the culvert could also help.<br />
|-<br />
| SRH-2D<br />
| N/A<br />
| forrtl: severe (24): end-of-file during read, unit n, file {your filepath.dat} Image PC Routine Line Source srh2d_3.2_quickwi...Unknown...<br />
| This is usually a generic error indicating something is wrong with the SRH simulation casename.DAT file created by SRH pre. It typically signifies that SRH-Pre did not terminate normally and generate a valid simulation file. The cause of the error could be any number of issues.<br />
| Check for any error messages reported by SRH-pre by going to the SMS model wrapper and clicking on the "PreSRH-2D" line and reviewing the on screen output messages.<br />
|-<br />
| SRH-2D<br />
| 1<br />
| Program stopped due to the following: Stopped in read_input2: Mismatch in HY8 ID<br />
| This is a bug in SRH caused by having two culvert crossings defined in the *.hy8 crossing file with certain similarities in their names.<br />
| The temporary workaround until this is fixed is to make all crossing names as different as possible, including the first character of the names. For example, "My Culvert" and "My Culvert1" could cause this error. Change one of the crossings to make it different, something like "My Culvert" and "Two Barrel Wingwall" would resolve the issue.<br />
|-<br />
| SRH-2D<br />
| N/A<br />
| Failed to find a mesh cell which contains the following (x y) points: (X,Y)=<br />
| This is caused when there is a void added to the mesh by deleting a mesh element from the mesh after the mesh has been generated. Creating void by deleting mesh elements may not actually remove the element data from the mesh in SRH-2D. <br />
|If a void is needed in the mesh, it should be created as a polygon in the Mesh Generator coverage and given a mesh type of "None". When a mesh is generated using polygons with the "None" type, a void will be created in the mesh that can be recognized by SRH-2D.<br />
|-<br />
| SRH-2D<br />
| 0<br />
| Program stopped due to the following: IFACE match does not found in structure_culvert.f90 #''n''<br />
| Element configuration around the structure face is causing a mismatch in the transition into or out of the structure.<br />
| It may help to ensure all elements within the two structures are quadrilateral elements. It may also help to ensure that the first row of elements downstream of the downstream structure face and upstream of the upstream structure face are also quadrilateral elements that are "well formed" ("Well formed" elements as in having interior corners as close to 90 degrees as possible).<br />
|-<br />
| SRH-2D<br />
| 1<br />
| Program stopped due to the following: Stopped in read_input2.f90 HY8 Forward_TABLE Line Error<br />
| There is a problem reading the culvert table file. One of the causes of this is that the HY8 file containing the culvert definition does not include a file extension.<br />
| Add a ".hy8" file extension to the culvert defintion filename.<br />
|-<br />
|SRH-2D<br />
|N/A<br />
|forrtl: severe (170): Program Exception - stack overflow<br />
|The simulation is too large for SRH-2D to process. Typically this occurs when running a simulation using sediment transport and a 2D mesh that contains more than 50,000 elements.<br />
|Reduce the number of elements in the 2D mesh and try running the simulation again.<br />
|-<br />
|SRH-2D<br />
| 3<br />
| Not ready in solve.f90 SEDIMENT MODULE<br />
| This errors occurs when sediment transport is being modeled in a project containing 1D hydraulic structures (culverts, weirs, pressure bridges, etc.). SRH-2D cannot model sediment transport in models containing 1D hydraulic structures.<br />
| Either do not use the sediment transport in the model run, or remove the 1D hydraulic structures from the model.<br />
|-<br />
|PreSRH-2D<br />
| 4<br />
| Program stopped due to the following: Stopped in sec_blow NLAY Error Code is: 4<br />
| This errors occurs when sediment transport is on and there are more than the maximum number of allowed sediment layers (9) for one or more sediment materials.<br />
| Reduce the number of sediment layers to 9 or less in each sediment material.<br />
|-<br />
|SRH-2D<br />
| 1<br />
| Program stopped due to the following: Wrong Boundary ID;may due to some boundary mesh points are not in NODESTRING lists in SMS<br />
| This error seems to be related to issues with mesh quality. <br />
| Review mesh quality. Check for elements with interior angles greater than 180 (if any are present adjust conceptual model so no elements have interior angles greater than 180).<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>Woodhttps://www.xmswiki.com/index.php?title=SMS:SRH-2D_Files&diff=138212SMS:SRH-2D Files2019-01-11T21:27:07Z<p>Wood: </p>
<hr />
<div>{{TOCright}}<br />
The available input and output files for SRH-2D are listed below.<br />
<br />
{|<br />
|-<br />
|<br />
{|<br />
|-<br />
|valign="top"|<br />
{| class="wikitable" <br />
|+'''SMS Input Files'''<br />
!width="40" align="center"|Name<br />
!width="200" align="center"|Description<br />
|-<br />
|DB3||dBASE III SRH-2D Information<br />
|-<br />
|H5||2D Scatter XMDF Information<br />
|-<br />
|MAP||Mesh Arcs Information<br />
|-<br />
|MATERIALS||Materials Types Information<br />
|-<br />
|PRJ||Projection<br />
|-<br />
|}<br />
|<br />
{| class="wikitable" <br />
|+'''Pre-SRH Input Files'''<br />
!width="40" align="center"|Name<br />
!width="200" align="center"|Description<br />
|-<br />
|SRHGEOM||Mesh Geometry<br />
|-<br />
|SRHHYDRO||Model Control<br />
|-<br />
|SRHMAT||Mesh Material<br />
|-<br />
|SRHSEDMAT||Sediment Material Properties<br />
|-<br />
|SRHMPOINT||Monitor Points<br />
|-<br />
|XYS||Input files for XY Series of data including:<br />
*BC Flow time series<br />
*BC Stage vs. Flow rating curve<br />
*BC Sediment vs. Flow rating curve<br />
*Bed material gradiations<br />
|-<br />
|}<br />
|-<br />
|valign="top"|<br />
{| class="wikitable" <br />
|+'''SRH-2D Input Files'''<br />
!width="40" align="center"|Name<br />
!width="200" align="center"|Description<br />
|-<br />
|DAT||Pre-SRH File<br />
|-<br />
|SOF.DAT||Pre-SRH Script Output File<br />
|-<br />
|}<br />
|<br />
{| class="wikitable" <br />
|+'''SRH-2D Output Files'''<br />
!width="40" align="center"|Name<br />
!width="200" align="center"|Description<br />
|-<br />
|DIA.dat||Diagnostic Grid Depth Values XMDF<br />
|-<br />
|DIP.dat||Dynamic Input Telescoping Grid<br />
|-<br />
|INF.dat||Courant–Friedrichs–Lewy Residuals<br />
|-<br />
|EXIT''n''.dat||Q and WSE Time step Averages<br />
|-<br />
|LN''n''.dat||Monitor Line Report<br />
|-<br />
|OUT.dat||Model Run Summary Output<br />
|-<br />
|PT''n''.dat||Monitor Point Report<br />
|-<br />
|PT''n''SED.dat||Monitor Points Report for Sediment Transport Simulations<br />
|-<br />
|RC''n''.dat||Rating Curve Report<br />
|-<br />
|HY''n''.dat||HY-8 Culvert Report<br />
|-<br />
|CULV''n''.dat||FST Culvert Report<br />
|-<br />
|WEIR''n''.dat||1D Weir Report<br />
|-<br />
|GATE''n''.dat||1D Gate Report<br />
|-<br />
|INTERNAL''n''.dat||Pressure Flow Structure Overtopping Report<br />
|-<br />
|RES.dat||Time step Residuals <br />
|-<br />
|RST''n''.dat||Restart (Hotstart) Result Output<br />
|-<br />
|TSO.dat||Time step Series Output Index<br />
|-<br />
|INF.dat||Global Information<br />
|-<br />
|XMDF.H5||Output WSE, Depth, Velocity, etc.<br />
|-<br />
|}<br />
|}<br />
An explanation of files used by and generated by SRH-2D are as follows:<br />
==Output Files==<br />
A description of each file generated during an SRH-2D simulation run is as follows. In the file descriptions, * is a placeholder representing the specific case name as specified in the model control:<br />
; *.DAT : File created when SRHpre is run, for use by SRH-2D. It contains model input information as well as geometry information about the mesh.<br />
; *_DIA.dat : Diagnostic file with potential errors and warnings about the execution. It helps to identify causes of execution error or failure. For the tutorial case, the file is almost empty indicating a successful run of the model. <br />
; *_DIP.dat : Dynamic Input file allows setting up or modify frequently used parameters during an SRH-2D execution. Parameters that can be set up or modified include the total simulation time, number of iterations within each time step, specification of restart files, time interval used for writing out intermediate results, time step interval, damping, relaxation for continuity and momentum equations, and the turbulence model type. Changing the parameters in this file is not usually recommended. See SRH-2D documentation for more information about the implementation of this file.<br />
; *_LN''n''.dat : Monitor line file where flow discharge and water surface elevation are recorded corresponding to time. For sediment transport simulations, sediment discharge, concentration, bed elevations, and size fraction sediment discharges are added to this file.<br />
; *_OUT.dat : Output file providing general model information such as input parameters, mesh size, list of restart file numbers and their corresponding time, cpu time of the simulation, etc. <br />
; *_PT''n''.dat : Monitor point file that provides time history of output hydraulic variables at the user-specified monitor points. For sediment transport runs the D50 bed material size is also output. The file is in column format and may be imported into Excel for plotting. Output from the file may be used to decide if a steady state solution has been obtained or to examine unsteady change of a variable. If additional monitor points are used, files would have a similar naming convention with the only change being PT1, PT2, PT3, etc.<br />
; *_PT''n''SED.dat : This file is similar to the *_PTn.dat file that provides time history of output sediment transport variables at the user-specified monitor points.<br />
; *_RC''n''.dat : If a rating curve has been specified for the exit boundary condition this file is generated. It contains columns reporting the water surface elevation and flow rates at the exit boundary condition throughout the simulation run. If multiple exit boundary conditions have rating curves specified, a series of these files would be created having a similar naming convention with the only change being RC1, RC2, RC3, etc.<br />
; *_HY''n''.dat : If an HY-8 culvert is part of the simulation, then this file is generated. It reports data columns of computed flow rates, headwater, and tailwater throughout the simulation run. If multiple HY-8 culverts are included in the simulation, a series of these files would be created having a similar naming convention with the only change being HY1, HY2, HY3, etc.<br />
; *_CULV''n''.dat : If an FST culvert is part of the simulation, then this file is generated. It reports data columns of computed flow rates, headwater, tailwater, invert elevation, whether it is overtopped, and whether it is inlet controlled throughout the simulation run. If multiple FST culverts are included in the simulation, a series of these files would be created having a similar naming convention with the only change being CULV1, CULV2, CULV3, etc.<br />
; *_WEIR''n''.dat : If a 1D weir is part of the simulation, then this file is generated. It reports data columns of computed flow rates, crest elevation, upstream water surface elevation, and downstream water surface elevation throughout the simulation run. If multiple 1D weirs are included in the simulation, a series of these files would be created having a similar naming convention with the only change being WEIR1, WEIR2, WEIR3, etc.<br />
; *_GATE''n''.dat : If a 1D gate is part of the simulation, then this file is generated. It reports data columns of computed flow rates, crest elevation, upstream water surface elevation, and downstream water surface elevation throughout the simulation run. If multiple 1D gates are included in the simulation, a series of these files would be created having a similar naming convention with the only change being GATE1, GATE2, GATE3, etc.<br />
; *_INTERNAL''n''.dat : If overtopping has been specified for any pressure flow structures in the simulation this file is generated. It contains columns reporting the water surface elevation and overtopping flow rates throughout the simulation run. If multiple pressure flow structures have overtopping specified, a series of these files would be created having a similar naming convention with the only change being INTERNAL1, INTERNAL2, INTERNAL3, etc.<br />
; *_RES.dat : Residual file that contains residuals of continuity and two velocity equations during the solution. Note that residuals are normalized. For example, the ResH is normalized by the maximum of the first three iterations. Therefore, residual of 1.0 is obtained for ResH if NITER is less than 4 in the c1_DIP.dat file. <br />
; *_RST''n''.dat : Restart file used as a model input in successive runs. These are written out at an interval specified within the model control. If there is a restart file, there is an option to start a model run using it as the initial conditions of the model. <br />
; *_SOF.dat : Script Output File generated when SRHpre is run. In the script output file all inputs are saved. Can be used to rerun SRHpre by changing the name to *_SIF.dat <br />
; *_TSO.dat : The time series output index file which contains a list which matches the restart file to a specific time step.<br />
; *_INF.dat : Global informational file including the global residual for water surface elevations (RES_H), as well as the residuals for the X and Y velocity components (RES_U and RES_V). It also includes other global information such as the number of wet cells and the net flowrate at the exit boundaries. These are all reported to this file once every 100 timesteps.<br />
; *_XMDF.h5 : Output Extensible Model Data Format (XMDF) file used by SMS for post-processing and visualization of results. Results include water surface elevation, water depth, depth averaged velocity, Froude number, and bed shear stress. If a model includes sediment transport, output results also include bed elevation, sediment concentration, bed material D50 particle size, and erosion and deposition amounts.<br />
<br />
==Native Files==<br />
SRH-2D makes use of native files. The four native files are *.SRHHYDRO, *.SRMAT, *.SRHSEDMAT, *.SRHMPOINT, and *.SRHGEOM as described below:<br />
===SRHHYDRO File=== <br />
SRHHYDRO is written out by SMS to guide SRH-2D through the hydraulic simulation. The SRHHYDRO file contains key information about the simulation while acting as a directory to other files for SRH-2D to use. The SRHHYDRO file stores the case name, simulation description, model type, turbulence model information, Manning’s n values, boundary conditions, boundary types, unsteady flow designation, simulation time, resultant output information, and initial conditions. Details of each card in the file are given as follows:<br />
{|class="wikitable"<br />
|-<br />
|width="100"|Case <br />
|width="500"| This is an identifier for SRH-2D to use when running to help recognize the files that correspond to a specific project. The case should be given a name that is unique for a simulation.<br />
|-<br />
|Description <br />
|width="500"| The description is to show in review of what was done for a specific simulation<br />
|-<br />
|RunType<br />
|width="500"| This card tells SRH-2D what to compute. Flow means a hydraulic model. Mobile refers to a sediment transport model.<br />
|-<br />
|ModelTemp <br />
|width="500"| This card communicates to SRH-2D whether the model will be used to simulate temperature. Currently, temperature is not supported by SRH-2D v. 2.2<br />
|-<br />
|UnsteadyOutput <br />
|width="500"| Unsteady output is labeled for unsteady, where intermediate calculations are performed, or as steady, where only final calculations are computed for accuracy. <br />
|-<br />
|SimTime <br />
|width="500"| Three numbers are given to specify start time (hours), time step (seconds), and total simulation time (hours).<br />
|-<br />
|TurbulenceModel <br />
|width="500"| This option is either parabolic or ke for the current version of SRH-2D. <br />
|-<br />
|ParabolicTurbulence <br />
|width="500"| This card is dependent on TurbulenceModel being labeled parabolic. The value is a constant used in the parabolic turbulence equation.<br />
|-<br />
|InitCondOption <br />
|width="500"| This card communicates to SRH-2D the condition of each element prior the model run. Options include dry, auto, and rst, where rst represents a start-up file from a previous run.<br />
|-<br />
|Grid <br />
|width="500"| This card tells SRH-2D the name of the grid file.<br />
|-<br />
|HydroMat <br />
|width="500"| This card tells SRH-2D the name of the material file.<br />
|-<br />
|SubsurfaceBedFile<br />
|width="500"| This card tells SRH-2D the name of the sediment material file.<br />
|-<br />
|MonitorPtFile <br />
|width="500"| This card tells SRH-2D the name of the monitor point file if one has been created. <br />
|-<br />
|OutputFormat <br />
|width="500"| This option represents how SMS will write out the final files to be read back for post processing. Two inputs are required, the file type and the resultant units.<br />
|-<br />
|OutputInterval <br />
|width="500"| This card tells SRH-2D how often to write out results during the simulation. The value is given in hours.<br />
|-<br />
|ManningsN <br />
|width="500"| In this location two values are given representing the material number and the value of Manning’s n corresponding to that material value. SMS will always write a zero material type as a default.<br />
|-<br />
|NumSubsurfaceLayers<br />
|width="500"|This card indicates the number of sediment layers for each sediment material type. (SRH-2D requires that at least 2 layers be specified, even if they are teh same materials.)<br />
|-<br />
|Subsurface Thickness<br />
|width="500"|This card indicates the thicknesses and bulk unit weights of sediment layers.<br />
|-<br />
|BedSedComposition<br />
|width="500"|This line points to the files (.xys) containing the sediment gradations for each sediment layer.<br />
|-<br />
|BC <br />
|width="500"| This card refers to the boundary type. Two values are given representing the boundary number and the type of boundary for each boundary number<br />
|-<br />
|IQParams <br />
|width="500"| This card will be written for boundary types that ask for a subcritical inlet boundary. The values given represent the boundary id, the constant flow value or variable flow file name, the units of flow, and the distribution type<br />
|-<br />
|ISupCrParams <br />
|width="500"| This card requires the same information as IQParams with the addition of constant water surface elevation or varable water surface elevation file name.<br />
|-<br />
|EWSParams <br />
|width="500"| This card represents the stage exit boundary. Values include the boundary id, the constant watersurface elevation or variable watersurface elevation file, and units type.<br />
|-<br />
|EQParams <br />
|width="500"| This card gives the constant discharge value or variable discharge file name and unit type.<br />
|-<br />
|NDParams <br />
|width="500"| This card refers to a normal depth outlet boundary. Values include the nodestring number at which flow will be computed as well as the average bed slope at the exit location.<br />
|}<br />
<br />
The file acts as a map guiding SRH-2D to other important files such as the SRHMAT file, the SRHMONITORPTS file, and the SRHGEOM file. <br />
<br />
====SRHHYDRO Example====<br />
SRHHYDRO 30<br />
Case "Case"<br />
Description "Description"<br />
RunType FLOW<br />
ModelTemp OFF<br />
UnsteadyOutput UNSTEADY<br />
SimTime 0 1 3<br />
TurbulenceModel PARABOLIC<br />
ParabolicTurbulence 0.7<br />
InitCondOption DRY<br />
Grid "HohRiv.srhgeom"<br />
HydroMat "HohRiv.srhmat"<br />
MonitorPtFile "HohRiv.srhmpoint"<br />
OutputFormat XMDF ENGLISH<br />
OutputInterval 1<br />
ManningsN 0 0.02<br />
ManningsN 1 0.025<br />
ManningsN 2 0.07<br />
BC 6 WALL<br />
BC 5 WALL<br />
BC 4 MONITORING<br />
BC 3 MONITORING<br />
BC 2 EXIT-H<br />
BC 1 INLET-Q<br />
IQParams 1 "HohRiv.srhcurve1.xys" EN CONVEYANCE<br />
EWSParams 2 "HohRiv.srhcurve2.xys" EN<br />
<br />
===SRHMAT File===<br />
The SRHMAT file gives each element a material type. This file will categorize each element to a Manning’s n value.<br />
<br />
====SRHMAT Example====<br />
SRHMAT 30<br />
NMaterials 3<br />
MatName 1 "Channel"<br />
MatName 2 "Forest"<br />
Material 1 1 2 12 14 15 23 24 26 27 28<br />
29 36 37 38 39 40 41 42 49 50<br />
51 52 53 54 55 56 63 64 65 66<br />
67 68 69 70 71 82 83 84 85 86<br />
87 88 89 90 91 103 104 106 107 108<br />
109 110 111 112 113 114 115 116 117 118<br />
119 120 121 132 133 134 135 136 137 138<br />
139 140 141 142 143 144 145 146 147 148<br />
149 150 151 152 153 154 155 156 157 158<br />
159 170 171 172 173 174 175 176 177 178<br />
179 180 181 182 183 184 185 186 187 188<br />
189 190 191 192 193 194 195 196 207 208<br />
209 210 211 212 213 214 215 216 217 218<br />
<br />
Material 2 3 4 5 6 7 8 9 10 11 13<br />
16 17 18 19 20 21 22 25 30 31<br />
32 33 34 35 43 44 45 46 47 48<br />
57 58 59 60 61 62 72 73 74 75<br />
76 77 78 79 80 81 92 93 94 95<br />
96 97 98 99 100 101 102 105 122 123<br />
124 125 126 127 128 129 130 131 160 161<br />
162 163 164 165 166 167 168 169 197 198<br />
199 200 201 202 203 204 205 206 228 229<br />
237 238 239 240 241 242 243 244 245 246<br />
<br />
===SRHSEDMAT File===<br />
The SRHSEDMAT file gives each element a sediment material type. This file will categorize each element with specific sediment layer thicknesses, bulk densities, and gradations. The sediment materials may be the same or differ from the material types.<br />
<br />
====SRHSEDMAT Example====<br />
SRHSEDMAT 30<br />
NSedMaterials 3<br />
SedMatName 1 "Channel"<br />
SedMatName 2 "Forest"<br />
SedMaterial 1 1 2 12 14 15 23 24 26 27 28<br />
29 36 37 38 39 40 41 42 49 50<br />
51 52 53 54 55 56 63 64 65 66<br />
67 68 69 70 71 82 83 84 85 86<br />
87 88 89 90 91 103 104 106 107 108<br />
109 110 111 112 113 114 115 116 117 118<br />
119 120 121 132 133 134 135 136 137 138<br />
139 140 141 142 143 144 145 146 147 148<br />
149 150 151 152 153 154 155 156 157 158<br />
159 170 171 172 173 174 175 176 177 178<br />
179 180 181 182 183 184 185 186 187 188<br />
189 190 191 192 193 194 195 196 207 208<br />
209 210 211 212 213 214 215 216 217 218<br />
SedMaterial 2 3 4 5 6 7 8 9 10 11 13<br />
16 17 18 19 20 21 22 25 30 31<br />
32 33 34 35 43 44 45 46 47 48<br />
57 58 59 60 61 62 72 73 74 75<br />
76 77 78 79 80 81 92 93 94 95<br />
96 97 98 99 100 101 102 105 122 123<br />
124 125 126 127 128 129 130 131 160 161<br />
162 163 164 165 166 167 168 169 197 198<br />
199 200 201 202 203 204 205 206 228 229<br />
237 238 239 240 241 242 243 244 245 246<br />
<br />
===SRHMPOINT File===<br />
The SRHMONITORPTS file or SRHMPOINT file is tells SRH-2D that there are monitor points to watch and where those points are located. SRH-2D will take the coordinates from SMS to locate the areas to be monitored.<br />
<br />
====SRHMPOINT Example====<br />
SRHMON 30<br />
NUMMONITORPTS 2<br />
monitorpt 1 798814 309513<br />
monitorpt 2 799387 305853<br />
<br />
===SRHGEOM File===<br />
The SRHGEOM file tells SRH-2D where each node is located and which nodes comprise each element. The SRHGEOM file also holds information about the units of the grid and node strings that are used for boundary conditions and monitor lines.<br />
<br />
====SRHGEOM Example====<br />
<br />
SRHGEOM 30<br />
Name "HohRiverDomain" <br />
<br />
GridUnit "FOOT"<br />
<br />
Elem 1 5 1 6 15<br />
Elem 2 1 2 7 6<br />
Elem 3 3 1 5<br />
Elem 4 2 1 3<br />
Elem 5 5 8 3<br />
Elem 6 3 8 10<br />
Elem 7 9 8 4<br />
Elem 8 13 4 14<br />
Elem 9 14 4 8<br />
Elem 10 11 4 13<br />
Elem 11 4 11 9<br />
Elem 12 14 5 15 24<br />
Elem 13 8 5 14<br />
Elem 14 6 7 17 16<br />
Node 1 798908 309671 169.545<br />
Node 2 798857 309733 170.299<br />
Node 3 798975 309744 171.463<br />
Node 4 799084 309550 170.097<br />
Node 5 798959 309609 169.67<br />
Node 6 798877 309645 169.34<br />
Node 7 798828 309705 170.831<br />
Node 8 799047 309635 171.189<br />
NodeString 6 2 3 10 19 29 40 52 69 90 118<br />
149 183 217 254 292 330 368 405 441 476<br />
513 548 585 621 656 687 716 744 771 797<br />
NodeString 5 171 205 240 278 316 354 391 426 462 500<br />
536 574 610 646 679 710 740 767 793 819<br />
843 867 891 915 939 963 986 1008 1031 1032<br />
<br />
<br />
===Sediment Rating Curve File "user_named.xys"===<br />
The sediment rating curve file provides the water discharge versus sediment discharge for each of the size fractions included in the run. Both variables are in cfs or cms depending on the units selected for the project. The lines with “//” are comment lines..<br />
<br />
===Guidance for creating a sediment rating curve===<br />
<br />
When modeling sediment transport with SRH-2D a sediment rating curve may be specified for the upstream inflow boundary condition(s). The sediment rating curve option in SRH-2D requires that a Qs (or sediment discharge in cfs or m3/s) be provided for each size fraction in the run. It would be common for field measurements to provide the sediment concentration as parts per million by weight (ppm-wt) or mg/L. Here is a guideline for converting between such a quantity and the required input for SRH-2D (Qs).<br />
<br />
For low sediment concentrations (Cmg/L < 25,000) the conversion from concentration to sediment discharge, Qs is:<br />
<br />
:<math>Qs = C/((1,000,000)*SG) * Q</math><br />
<br />
Where:<br />
<br />
:Qs = Sediment discharge in cfs or m3/s <br />
:C (in mg/L) = concentration of sediment in inflow (in mg/L) <br />
:SG = specific gravity of inflow sediment<br />
:Q = volumetric flowrate in cfs or m3/s <br />
<br />
For higher concentrations the sediment contribution to the total flow volume should not be ignored. See HDS-6 Section 4.8 (FHWA, 2001) or a sediment transport textbook for exact relationships for high-concentration conditions.<br />
<br />
Particle Diameter Thresholds (in mm) must be specified when modeling sediment transport with SRH-2D. These values are entered in the ''BC Type Parameters'' dialog accessed by right-clicking on the SRH-2D Boundary Conditions coverage used in the SRH-2D sediment simulation and selecting '''BC Types'''. <br />
<br />
The number of columns in the sediment rating curve file should correspond to the intervals between the thresholds (or the number of thresholds minus one) plus an additional column at the beginning with the corresponding flow. It is the responsibility of the user to decide how many flows (one row for each) should be entered in the sediment rating curve. A particle size distribution analysis should be performed for the incoming sediment to determine the Qs in each size class in each particle diameter threshold interval. The number of sediment size classes in the sediment gradation curves specified for each layer in the sediment materials coverage don’t necessarily need to match the number of intervals between thresholds. <br />
<br />
The SRH-Capacity software developed by the US Bureau of Reclamation may be used to assist in this process of developing a sediment rating curve. For information on the SRH-Capacity software see [https://www.usbr.gov/tsc/techreferences/computer%20software/models/srhcapacity/index.html this page].<br />
<br />
====SEDIMENT RATING CURVE Example====<br />
<br />
RATING_CURVE<br />
// Q-vs- Qs rating curve at upstream boundary<br />
// 9 size fraction. 100ppm for cohesive sediment.<br />
35315 1.3326 4.58713 2.49675 3.82647 1.36954 0.21376 0.01986 0.00174 0.00019<br />
54080 2.0408 9.00825 4.97158 8.52648 3.24857 0.45732 0.02603 0.00245 0.00044<br />
81910 3.0909 13.84716 9.12011 18.89248 11.53444 2.91612 0.34379 0.02711 0.00651<br />
117161 4.4212 10.34221 9.51859 23.91257 20.10147 6.71838 1.17766 0.17474 0.03415<br />
178208 6.7248 5.48430 6.92301 20.87747 21.68023 8.27505 1.58578 0.26850 0.05264<br />
238037 8.9825 5.54236 7.73237 26.09735 31.32539 12.73831 2.58504 0.48187 0.12043<br />
<br />
==Related Topics==<br />
* For more information on these files see the [http://www.usbr.gov/tsc/techreferences/computer%20software/models/srh2d/Manual-SRH2D-v2.0-Nov2008.pdf manual].<br />
*[[SMS:SRH-2D|SRH-2D]]<br />
<br />
<br />
{{Navbox SMS}}<br />
<br />
[[Category:SRH-2D|F]]<br />
[[Category:SMS File Formats|S]]<br />
[[Category:Equations]]</div>Woodhttps://www.xmswiki.com/index.php?title=SMS:SRH-2D_Files&diff=138121SMS:SRH-2D Files2019-01-02T22:11:49Z<p>Wood: /* Sediment Rating Curve File "user_named.xys" */</p>
<hr />
<div>{{TOCright}}<br />
The available input and output files for SRH-2D are listed below.<br />
<br />
{|<br />
|-<br />
|<br />
{|<br />
|-<br />
|valign="top"|<br />
{| class="wikitable" <br />
|+'''SMS Input Files'''<br />
!width="40" align="center"|Name<br />
!width="200" align="center"|Description<br />
|-<br />
|DB3||dBASE III SRH-2D Information<br />
|-<br />
|H5||2D Scatter XMDF Information<br />
|-<br />
|MAP||Mesh Arcs Information<br />
|-<br />
|MATERIALS||Materials Types Information<br />
|-<br />
|PRJ||Projection<br />
|-<br />
|}<br />
|<br />
{| class="wikitable" <br />
|+'''Pre-SRH Input Files'''<br />
!width="40" align="center"|Name<br />
!width="200" align="center"|Description<br />
|-<br />
|SRHGEOM||Mesh Geometry<br />
|-<br />
|SRHHYDRO||Model Control<br />
|-<br />
|SRHMAT||Mesh Material<br />
|-<br />
|SRHSEDMAT||Sediment Material Properties<br />
|-<br />
|SRHMPOINT||Monitor Points<br />
|-<br />
|XYS||Input files for XY Series of data including:<br />
*BC Flow time series<br />
*BC Stage vs. Flow rating curve<br />
*BC Sediment vs. Flow rating curve<br />
*Bed material gradiations<br />
|-<br />
|}<br />
|-<br />
|valign="top"|<br />
{| class="wikitable" <br />
|+'''SRH-2D Input Files'''<br />
!width="40" align="center"|Name<br />
!width="200" align="center"|Description<br />
|-<br />
|DAT||Pre-SRH File<br />
|-<br />
|SOF.DAT||Pre-SRH Script Output File<br />
|-<br />
|}<br />
|<br />
{| class="wikitable" <br />
|+'''SRH-2D Output Files'''<br />
!width="40" align="center"|Name<br />
!width="200" align="center"|Description<br />
|-<br />
|DIA.dat||Diagnostic Grid Depth Values XMDF<br />
|-<br />
|DIP.dat||Dynamic Input Telescoping Grid<br />
|-<br />
|INF.dat||Courant–Friedrichs–Lewy Residuals<br />
|-<br />
|EXIT''n''.dat||Q and WSE Time step Averages<br />
|-<br />
|LN''n''.dat||Monitor Line Report<br />
|-<br />
|OUT.dat||Model Run Summary Output<br />
|-<br />
|PT''n''.dat||Monitor Point Report<br />
|-<br />
|PT''n''SED.dat||Monitor Points Report for Sediment Transport Simulations<br />
|-<br />
|RC''n''.dat||Rating Curve Report<br />
|-<br />
|HY''n''.dat||HY-8 Culvert Report<br />
|-<br />
|CULV''n''.dat||FST Culvert Report<br />
|-<br />
|WEIR''n''.dat||1D Weir Report<br />
|-<br />
|GATE''n''.dat||1D Gate Report<br />
|-<br />
|INTERNAL''n''.dat||Pressure Flow Structure Overtopping Report<br />
|-<br />
|RES.dat||Time step Residuals <br />
|-<br />
|RST''n''.dat||Restart (Hotstart) Result Output<br />
|-<br />
|TSO.dat||Time step Series Output Index<br />
|-<br />
|INF.dat||Global Information<br />
|-<br />
|XMDF.H5||Output WSE, Depth, Velocity, etc.<br />
|-<br />
|}<br />
|}<br />
An explanation of files used by and generated by SRH-2D are as follows:<br />
==Output Files==<br />
A description of each file generated during an SRH-2D simulation run is as follows. In the file descriptions, * is a placeholder representing the specific case name as specified in the model control:<br />
; *.DAT : File created when SRHpre is run, for use by SRH-2D. It contains model input information as well as geometry information about the mesh.<br />
; *_DIA.dat : Diagnostic file with potential errors and warnings about the execution. It helps to identify causes of execution error or failure. For the tutorial case, the file is almost empty indicating a successful run of the model. <br />
; *_DIP.dat : Dynamic Input file allows setting up or modify frequently used parameters during an SRH-2D execution. Parameters that can be set up or modified include the total simulation time, number of iterations within each time step, specification of restart files, time interval used for writing out intermediate results, time step interval, damping, relaxation for continuity and momentum equations, and the turbulence model type. Changing the parameters in this file is not usually recommended. See SRH-2D documentation for more information about the implementation of this file.<br />
; *_LN''n''.dat : Monitor line file where flow discharge and water surface elevation are recorded corresponding to time. For sediment transport simulations, sediment discharge, concentration, bed elevations, and size fraction sediment discharges are added to this file.<br />
; *_OUT.dat : Output file providing general model information such as input parameters, mesh size, list of restart file numbers and their corresponding time, cpu time of the simulation, etc. <br />
; *_PT''n''.dat : Monitor point file that provides time history of output hydraulic variables at the user-specified monitor points. For sediment transport runs the D50 bed material size is also output. The file is in column format and may be imported into Excel for plotting. Output from the file may be used to decide if a steady state solution has been obtained or to examine unsteady change of a variable. If additional monitor points are used, files would have a similar naming convention with the only change being PT1, PT2, PT3, etc.<br />
; *_PT''n''SED.dat : This file is similar to the *_PTn.dat file that provides time history of output sediment transport variables at the user-specified monitor points.<br />
; *_RC''n''.dat : If a rating curve has been specified for the exit boundary condition this file is generated. It contains columns reporting the water surface elevation and flow rates at the exit boundary condition throughout the simulation run. If multiple exit boundary conditions have rating curves specified, a series of these files would be created having a similar naming convention with the only change being RC1, RC2, RC3, etc.<br />
; *_HY''n''.dat : If an HY-8 culvert is part of the simulation, then this file is generated. It reports data columns of computed flow rates, headwater, and tailwater throughout the simulation run. If multiple HY-8 culverts are included in the simulation, a series of these files would be created having a similar naming convention with the only change being HY1, HY2, HY3, etc.<br />
; *_CULV''n''.dat : If an FST culvert is part of the simulation, then this file is generated. It reports data columns of computed flow rates, headwater, tailwater, invert elevation, whether it is overtopped, and whether it is inlet controlled throughout the simulation run. If multiple FST culverts are included in the simulation, a series of these files would be created having a similar naming convention with the only change being CULV1, CULV2, CULV3, etc.<br />
; *_WEIR''n''.dat : If a 1D weir is part of the simulation, then this file is generated. It reports data columns of computed flow rates, crest elevation, upstream water surface elevation, and downstream water surface elevation throughout the simulation run. If multiple 1D weirs are included in the simulation, a series of these files would be created having a similar naming convention with the only change being WEIR1, WEIR2, WEIR3, etc.<br />
; *_GATE''n''.dat : If a 1D gate is part of the simulation, then this file is generated. It reports data columns of computed flow rates, crest elevation, upstream water surface elevation, and downstream water surface elevation throughout the simulation run. If multiple 1D gates are included in the simulation, a series of these files would be created having a similar naming convention with the only change being GATE1, GATE2, GATE3, etc.<br />
; *_INTERNAL''n''.dat : If overtopping has been specified for any pressure flow structures in the simulation this file is generated. It contains columns reporting the water surface elevation and overtopping flow rates throughout the simulation run. If multiple pressure flow structures have overtopping specified, a series of these files would be created having a similar naming convention with the only change being INTERNAL1, INTERNAL2, INTERNAL3, etc.<br />
; *_RES.dat : Residual file that contains residuals of continuity and two velocity equations during the solution. Note that residuals are normalized. For example, the ResH is normalized by the maximum of the first three iterations. Therefore, residual of 1.0 is obtained for ResH if NITER is less than 4 in the c1_DIP.dat file. <br />
; *_RST''n''.dat : Restart file used as a model input in successive runs. These are written out at an interval specified within the model control. If there is a restart file, there is an option to start a model run using it as the initial conditions of the model. <br />
; *_SOF.dat : Script Output File generated when SRHpre is run. In the script output file all inputs are saved. Can be used to rerun SRHpre by changing the name to *_SIF.dat <br />
; *_TSO.dat : The time series output index file which contains a list which matches the restart file to a specific time step.<br />
; *_INF.dat : Global informational file including the global residual for water surface elevations (RES_H), as well as the residuals for the X and Y velocity components (RES_U and RES_V). It also includes other global information such as the number of wet cells and the net flowrate at the exit boundaries. These are all reported to this file once every 100 timesteps.<br />
; *_XMDF.h5 : Output Extensible Model Data Format (XMDF) file used by SMS for post-processing and visualization of results. Results include water surface elevation, water depth, depth averaged velocity, Froude number, and bed shear stress. If a model includes sediment transport, output results also include bed elevation, sediment concentration, bed material D50 particle size, and erosion and deposition amounts.<br />
<br />
==Native Files==<br />
SRH-2D makes use of native files. The four native files are *.SRHHYDRO, *.SRMAT, *.SRHSEDMAT, *.SRHMPOINT, and *.SRHGEOM as described below:<br />
===SRHHYDRO File=== <br />
SRHHYDRO is written out by SMS to guide SRH-2D through the hydraulic simulation. The SRHHYDRO file contains key information about the simulation while acting as a directory to other files for SRH-2D to use. The SRHHYDRO file stores the case name, simulation description, model type, turbulence model information, Manning’s n values, boundary conditions, boundary types, unsteady flow designation, simulation time, resultant output information, and initial conditions. Details of each card in the file are given as follows:<br />
{|class="wikitable"<br />
|-<br />
|width="100"|Case <br />
|width="500"| This is an identifier for SRH-2D to use when running to help recognize the files that correspond to a specific project. The case should be given a name that is unique for a simulation.<br />
|-<br />
|Description <br />
|width="500"| The description is to show in review of what was done for a specific simulation<br />
|-<br />
|RunType<br />
|width="500"| This card tells SRH-2D what to compute. Flow means a hydraulic model. Mobile refers to a sediment transport model.<br />
|-<br />
|ModelTemp <br />
|width="500"| This card communicates to SRH-2D whether the model will be used to simulate temperature. Currently, temperature is not supported by SRH-2D v. 2.2<br />
|-<br />
|UnsteadyOutput <br />
|width="500"| Unsteady output is labeled for unsteady, where intermediate calculations are performed, or as steady, where only final calculations are computed for accuracy. <br />
|-<br />
|SimTime <br />
|width="500"| Three numbers are given to specify start time (hours), time step (seconds), and total simulation time (hours).<br />
|-<br />
|TurbulenceModel <br />
|width="500"| This option is either parabolic or ke for the current version of SRH-2D. <br />
|-<br />
|ParabolicTurbulence <br />
|width="500"| This card is dependent on TurbulenceModel being labeled parabolic. The value is a constant used in the parabolic turbulence equation.<br />
|-<br />
|InitCondOption <br />
|width="500"| This card communicates to SRH-2D the condition of each element prior the model run. Options include dry, auto, and rst, where rst represents a start-up file from a previous run.<br />
|-<br />
|Grid <br />
|width="500"| This card tells SRH-2D the name of the grid file.<br />
|-<br />
|HydroMat <br />
|width="500"| This card tells SRH-2D the name of the material file.<br />
|-<br />
|SubsurfaceBedFile<br />
|width="500"| This card tells SRH-2D the name of the sediment material file.<br />
|-<br />
|MonitorPtFile <br />
|width="500"| This card tells SRH-2D the name of the monitor point file if one has been created. <br />
|-<br />
|OutputFormat <br />
|width="500"| This option represents how SMS will write out the final files to be read back for post processing. Two inputs are required, the file type and the resultant units.<br />
|-<br />
|OutputInterval <br />
|width="500"| This card tells SRH-2D how often to write out results during the simulation. The value is given in hours.<br />
|-<br />
|ManningsN <br />
|width="500"| In this location two values are given representing the material number and the value of Manning’s n corresponding to that material value. SMS will always write a zero material type as a default.<br />
|-<br />
|NumSubsurfaceLayers<br />
|width="500"|This card indicates the number of sediment layers for each sediment material type. (SRH-2D requires that at least 2 layers be specified, even if they are teh same materials.)<br />
|-<br />
|Subsurface Thickness<br />
|width="500"|This card indicates the thicknesses and bulk unit weights of sediment layers.<br />
|-<br />
|BedSedComposition<br />
|width="500"|This line points to the files (.xys) containing the sediment gradations for each sediment layer.<br />
|-<br />
|BC <br />
|width="500"| This card refers to the boundary type. Two values are given representing the boundary number and the type of boundary for each boundary number<br />
|-<br />
|IQParams <br />
|width="500"| This card will be written for boundary types that ask for a subcritical inlet boundary. The values given represent the boundary id, the constant flow value or variable flow file name, the units of flow, and the distribution type<br />
|-<br />
|ISupCrParams <br />
|width="500"| This card requires the same information as IQParams with the addition of constant water surface elevation or varable water surface elevation file name.<br />
|-<br />
|EWSParams <br />
|width="500"| This card represents the stage exit boundary. Values include the boundary id, the constant watersurface elevation or variable watersurface elevation file, and units type.<br />
|-<br />
|EQParams <br />
|width="500"| This card gives the constant discharge value or variable discharge file name and unit type.<br />
|-<br />
|NDParams <br />
|width="500"| This card refers to a normal depth outlet boundary. Values include the nodestring number at which flow will be computed as well as the average bed slope at the exit location.<br />
|}<br />
<br />
The file acts as a map guiding SRH-2D to other important files such as the SRHMAT file, the SRHMONITORPTS file, and the SRHGEOM file. <br />
<br />
====SRHHYDRO Example====<br />
SRHHYDRO 30<br />
Case "Case"<br />
Description "Description"<br />
RunType FLOW<br />
ModelTemp OFF<br />
UnsteadyOutput UNSTEADY<br />
SimTime 0 1 3<br />
TurbulenceModel PARABOLIC<br />
ParabolicTurbulence 0.7<br />
InitCondOption DRY<br />
Grid "HohRiv.srhgeom"<br />
HydroMat "HohRiv.srhmat"<br />
MonitorPtFile "HohRiv.srhmpoint"<br />
OutputFormat XMDF ENGLISH<br />
OutputInterval 1<br />
ManningsN 0 0.02<br />
ManningsN 1 0.025<br />
ManningsN 2 0.07<br />
BC 6 WALL<br />
BC 5 WALL<br />
BC 4 MONITORING<br />
BC 3 MONITORING<br />
BC 2 EXIT-H<br />
BC 1 INLET-Q<br />
IQParams 1 "HohRiv.srhcurve1.xys" EN CONVEYANCE<br />
EWSParams 2 "HohRiv.srhcurve2.xys" EN<br />
<br />
===SRHMAT File===<br />
The SRHMAT file gives each element a material type. This file will categorize each element to a Manning’s n value.<br />
<br />
====SRHMAT Example====<br />
SRHMAT 30<br />
NMaterials 3<br />
MatName 1 "Channel"<br />
MatName 2 "Forest"<br />
Material 1 1 2 12 14 15 23 24 26 27 28<br />
29 36 37 38 39 40 41 42 49 50<br />
51 52 53 54 55 56 63 64 65 66<br />
67 68 69 70 71 82 83 84 85 86<br />
87 88 89 90 91 103 104 106 107 108<br />
109 110 111 112 113 114 115 116 117 118<br />
119 120 121 132 133 134 135 136 137 138<br />
139 140 141 142 143 144 145 146 147 148<br />
149 150 151 152 153 154 155 156 157 158<br />
159 170 171 172 173 174 175 176 177 178<br />
179 180 181 182 183 184 185 186 187 188<br />
189 190 191 192 193 194 195 196 207 208<br />
209 210 211 212 213 214 215 216 217 218<br />
<br />
Material 2 3 4 5 6 7 8 9 10 11 13<br />
16 17 18 19 20 21 22 25 30 31<br />
32 33 34 35 43 44 45 46 47 48<br />
57 58 59 60 61 62 72 73 74 75<br />
76 77 78 79 80 81 92 93 94 95<br />
96 97 98 99 100 101 102 105 122 123<br />
124 125 126 127 128 129 130 131 160 161<br />
162 163 164 165 166 167 168 169 197 198<br />
199 200 201 202 203 204 205 206 228 229<br />
237 238 239 240 241 242 243 244 245 246<br />
<br />
===SRHSEDMAT File===<br />
The SRHSEDMAT file gives each element a sediment material type. This file will categorize each element with specific sediment layer thicknesses, bulk densities, and gradations. The sediment materials may be the same or differ from the material types.<br />
<br />
====SRHSEDMAT Example====<br />
SRHSEDMAT 30<br />
NSedMaterials 3<br />
SedMatName 1 "Channel"<br />
SedMatName 2 "Forest"<br />
SedMaterial 1 1 2 12 14 15 23 24 26 27 28<br />
29 36 37 38 39 40 41 42 49 50<br />
51 52 53 54 55 56 63 64 65 66<br />
67 68 69 70 71 82 83 84 85 86<br />
87 88 89 90 91 103 104 106 107 108<br />
109 110 111 112 113 114 115 116 117 118<br />
119 120 121 132 133 134 135 136 137 138<br />
139 140 141 142 143 144 145 146 147 148<br />
149 150 151 152 153 154 155 156 157 158<br />
159 170 171 172 173 174 175 176 177 178<br />
179 180 181 182 183 184 185 186 187 188<br />
189 190 191 192 193 194 195 196 207 208<br />
209 210 211 212 213 214 215 216 217 218<br />
SedMaterial 2 3 4 5 6 7 8 9 10 11 13<br />
16 17 18 19 20 21 22 25 30 31<br />
32 33 34 35 43 44 45 46 47 48<br />
57 58 59 60 61 62 72 73 74 75<br />
76 77 78 79 80 81 92 93 94 95<br />
96 97 98 99 100 101 102 105 122 123<br />
124 125 126 127 128 129 130 131 160 161<br />
162 163 164 165 166 167 168 169 197 198<br />
199 200 201 202 203 204 205 206 228 229<br />
237 238 239 240 241 242 243 244 245 246<br />
<br />
===SRHMPOINT File===<br />
The SRHMONITORPTS file or SRHMPOINT file is tells SRH-2D that there are monitor points to watch and where those points are located. SRH-2D will take the coordinates from SMS to locate the areas to be monitored.<br />
<br />
====SRHMPOINT Example====<br />
SRHMON 30<br />
NUMMONITORPTS 2<br />
monitorpt 1 798814 309513<br />
monitorpt 2 799387 305853<br />
<br />
===SRHGEOM File===<br />
The SRHGEOM file tells SRH-2D where each node is located and which nodes comprise each element. The SRHGEOM file also holds information about the units of the grid and node strings that are used for boundary conditions and monitor lines.<br />
<br />
====SRHGEOM Example====<br />
<br />
SRHGEOM 30<br />
Name "HohRiverDomain" <br />
<br />
GridUnit "FOOT"<br />
<br />
Elem 1 5 1 6 15<br />
Elem 2 1 2 7 6<br />
Elem 3 3 1 5<br />
Elem 4 2 1 3<br />
Elem 5 5 8 3<br />
Elem 6 3 8 10<br />
Elem 7 9 8 4<br />
Elem 8 13 4 14<br />
Elem 9 14 4 8<br />
Elem 10 11 4 13<br />
Elem 11 4 11 9<br />
Elem 12 14 5 15 24<br />
Elem 13 8 5 14<br />
Elem 14 6 7 17 16<br />
Node 1 798908 309671 169.545<br />
Node 2 798857 309733 170.299<br />
Node 3 798975 309744 171.463<br />
Node 4 799084 309550 170.097<br />
Node 5 798959 309609 169.67<br />
Node 6 798877 309645 169.34<br />
Node 7 798828 309705 170.831<br />
Node 8 799047 309635 171.189<br />
NodeString 6 2 3 10 19 29 40 52 69 90 118<br />
149 183 217 254 292 330 368 405 441 476<br />
513 548 585 621 656 687 716 744 771 797<br />
NodeString 5 171 205 240 278 316 354 391 426 462 500<br />
536 574 610 646 679 710 740 767 793 819<br />
843 867 891 915 939 963 986 1008 1031 1032<br />
<br />
<br />
===Sediment Rating Curve File "user_named.xys"===<br />
The sediment rating curve file provides the water discharge versus sediment discharge for each of the size fractions included in the run. Both variables are in cfs or cms depending on the units selected for the project. The lines with “//” are comment lines..<br />
<br />
===Guidance for creating a sediment rating curve===<br />
<br />
When modeling sediment transport with SRH-2D a sediment rating curve may be specified for the upstream inflow boundary condition(s). The sediment rating curve option in SRH-2D requires that a Qs (or sediment discharge in cfs or m3/s) be provided for each size fraction in the run. It would be common for field measurements to provide the sediment concentration as parts per million by weight (ppm-wt) or mg/L. This document provides a guideline for converting between such a quantity and the required input for SRH-2D (Qs).<br />
For low sediment concentrations (Cmg/L < 25,000) the conversion from concentration to sediment discharge, Qs is:<br />
<br />
<br/><br />
<br />
Qs = C/((1,000,000)*SG) * Q<br />
<br />
<br/><br />
<br />
Where:<br />
<br />
Qs = Sediment discharge in cfs or m3/s <br/><br />
C (in mg/L) = concentration of sediment in inflow (in mg/L) <br/><br />
SG = specific gravity of inflow sediment <br/><br />
Q = volumetric flowrate in cfs or m3/s <br/><br />
<br />
<br/><br />
For higher concentrations the sediment contribution to the total flow volume should not be ignored. See HDS-6 Section 4.8 (FHWA, 2001) or a sediment transport textbook for exact relationships for high-concentration conditions.<br />
<br />
<br />
Particle Diameter Thresholds (in mm) must be specified when modeling sediment transport with SRH-2D. These values are entered in the BC Type Parameters dialog accessed by right-clicking on the SRH-2D Boundary Conditions coverage used in the SRH-2D sediment simulation and selecting BC Types. <br />
<br />
<br />
The number of columns in the sediment rating curve file should correspond to the intervals between the thresholds (or the number of thresholds minus one) plus an additional column at the beginning with the corresponding flow. It is the responsibility of the user to decide how many flows (one row for each) should be entered in the sediment rating curve. A particle size distribution analysis should be performed for the incoming sediment to determine the Qs in each size class in each particle diameter threshold interval. The number of sediment size classes in the sediment gradation curves specified for each layer in the sediment materials coverage don’t necessarily need to match the number of intervals between thresholds. <br />
<br />
<br />
====SEDIMENT RATING CURVE Example====<br />
<br />
RATING_CURVE<br />
// Q-vs- Qs rating curve at upstream boundary<br />
// 9 size fraction. 100ppm for cohesive sediment.<br />
35315 1.3326 4.58713 2.49675 3.82647 1.36954 0.21376 0.01986 0.00174 0.00019<br />
54080 2.0408 9.00825 4.97158 8.52648 3.24857 0.45732 0.02603 0.00245 0.00044<br />
81910 3.0909 13.84716 9.12011 18.89248 11.53444 2.91612 0.34379 0.02711 0.00651<br />
117161 4.4212 10.34221 9.51859 23.91257 20.10147 6.71838 1.17766 0.17474 0.03415<br />
178208 6.7248 5.48430 6.92301 20.87747 21.68023 8.27505 1.58578 0.26850 0.05264<br />
238037 8.9825 5.54236 7.73237 26.09735 31.32539 12.73831 2.58504 0.48187 0.12043<br />
<br />
==Related Topics==<br />
* For more information on these files see the [http://www.usbr.gov/tsc/techreferences/computer%20software/models/srh2d/Manual-SRH2D-v2.0-Nov2008.pdf manual].<br />
*[[SMS:SRH-2D|SRH-2D]]<br />
<br />
<br />
{{Navbox SMS}}<br />
<br />
[[Category:SRH-2D|F]]<br />
[[Category:SMS File Formats|S]]</div>Woodhttps://www.xmswiki.com/index.php?title=SMS:SRH-2D_Errors&diff=137958SMS:SRH-2D Errors2018-11-29T23:49:41Z<p>Wood: /* List of Error Messages */</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 />
An error may occur during either the Pre-SRH-2D process or during the SRH-2D process. During the run, errors will be listed in the SRH-2D model wrapper. Clicking the PreSRH-2D button in the model wrapper will display results from the pre-processor. Clicking the SRH-2D button will show results from the model run.<br />
<br />
If the model wrapper has been closed, two files are generated recording the model run. Opening the "*_.OUT.dat" or the "*_DIA.dat" files in a text editor will show errors in 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 Pre-processor 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 spline.f90 H<br />
| Time series data used to define inflows/outflows or time varying water surface elevations has issues with how it is defined, such as duplicate times. <br />
| The time series data should only have one data value per defined time. Go to the XY series editor where the time series data is defined and remove any and every duplicate time entry.<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 need 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 />
| In SMS v12.1, 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. Modify the placement of the structure arcs in the boundary condition coverage or unassigned material polygon edges so that the snap preview of the material polygon matches the snap preview of the structure arc. In SMS 12.2 or later, it is not necessary to create the unassigned material polygon to disable the area between the structure arcs because SRH-2D has been modified to do this internally. If encountering this error using 12.2 or later, one possible solution would be to delete the unassigned material polygon, rebuild polygons and double check all polygons to make sure valid material types have been assigned.<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 />
| Pre SRH-2D<br />
| <br />
| Errors from final_touch.f90 **** on MONITOR LINE#n<br> a face cannot be found given two mesh points<br><br />
Two points are: xx xx<br><br />
Check the mesh node list; do this using _SIF.dat file directly!<br />
| Monitor line spans a mesh void (hole)<br />
| Reconfigure the monitor line. Monitor lines cannot span holes in the mesh.<br />
|-<br />
| SRH-2D<br />
| <br />
| <br />
| If there is 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 />
| Material polygons near inflow are unassigned<br />
| This occurs when the material coverage has not been linked to the simulation. Also occurs when all material polygons covering the inflow BC are have an "unassigned" material type. This can also occur if no boundary conditions providing an inflow source have been included in the simulation.<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 computational time step in the model control<br />
|-<br />
| SRH-2D<br />
| 3<br />
| bad mesh ! Stopped in indx_conn.f<br />
| Problem in mesh, often due to overlapping elements. <br />
| Check if problem cell (element) id is listed. Otherwise, examine mesh quality in SMS.<br />
|-<br />
| SMS<br />
| <br />
| No mesh that matches the scalar set.<br />
| No mesh that matches the scalar set. The solution file does not correspond to the mesh in the project, or node numbering of the mesh has been changed, invalidating the solution.<br />
| Take care when making edits to the mesh and renumbering the nodes. Any previous results will be invalidated when nodes are renumbered.<br />
|-<br />
| <br />
| None<br />
| None<br />
| WSE error directly under the bridge in the form of waves oscillating through the channel<br />
| Use larger, quadrilateral elements in the deepest areas of flow. This could also mean that the piers need to be switched to obstructions. Lowering the time step may also help.<br />
|-<br />
|-<br />
| <br />
| None<br />
| None<br />
| SRH-2D is not recognizing a 1D structure or 2D pressure flow structure. When reviewing the 2D results or output files it does not appear that SRH-2D is using a structure such as a culvert, pressure flow bridge structure, weir, or gate.<br />
| Make sure the pair of arcs in the SRH-2D boundary condition coverage representing the faces of the structure were created in the same topologic direction. (i.e. Both were created left to right looking downstream or both were created right to left downstream.) The direction does not matter, just that both arcs are consistent. Turn on the display of arc "Direction" in the display options for the map arcs. This will add an arrow to the map arcs in the display denoting their topologic direction.<br />
|-<br />
| SMS<br />
| <br />
| The following coverage(s) have an unsupported type and will be converted to area property: ''(Name of Coverage(s) Listed)''<br />
| <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), further troubleshooting is required if it has not finished running successfully.<br />
|-<br />
| <br />
| 1<br />
| Error code 1<br />
| srhmat file does not exist<br />
| File didn't export successfully. Make sure materials are assigned in the materials coverage.<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 />
| 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 />
| 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 the 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 />
| SRH-2D<br />
| 1<br />
| Stopped in structure_pressure_flow.f90 PARA DISTANCE<br />
| Shape of pressure zone is not acceptable for a parabolic type bridge ceiling<br />
| Ensure that the pressure zone, between the pressure flow arcs, is rectangular in shape<br />
|-<br />
| SRH-2D<br />
| 9669<br />
| Program stopped due to the following:<br />
Wrong IFACE matching occurred in structure_internal.f90 #4<br />
Error Code is: 9669<br />
| Ensure that the area between the pressure zone arcs with overtopping turned on is rectangular in shape and that the elements in between the arcs are quads (rectangles).<br />
| Create a new mesh with a rectangle between pressure flow arcs and which has quads in this area using the patch mesh generation method.<br />
|-<br />
|-<br />
| SRH-2D<br />
| 0<br />
| Program stopped due to the following:<br />
Wrong IFACE matching occurred in structure_internal.f90 #4<br />
Error Code is: 0<br />
| BC arc is not snapped properly between nodes along element edges with varying elevations.<br />
| Either modify the mesh to smooth elevations or redistribute vertices along BC arc and assign elevations that match mesh element edges (the "Scatter | Interpolate to Map" feature can be used to vary elevations along an existing BC arc).<br />
|-<br />
| SRH-2D<br />
| 16026<br />
| Program stopped due to the following: <br />
A downstream Structure nodestring has not set right; structure_culvert.f90 ICELL error#2<br />
Error Code is: 16026<br />
| The 2D mesh around and through the structure is not optimal.<br />
| Re-mesh areas around the structure. Suggestions to optimize the mesh around the structure include creating patched (quadrilateral) elements through the structure from one face to the other. SRH-2D inactivates elements between the structure faces where the 1D flow is computed. Creating quadrilateral elements in the zone between the faces facilitates the process SRH uses to locate and inactivate the flow computations for those elements in the mesh. Configure the mesh such that the structure faces can be created alone a series of element edges that are oriented in the same direction (along a flat and straight line of element edges).<br />
|-<br />
| SRH-2D<br />
| 79<br />
| Program stopped due to the following:<br />
Tailwater WSE exceeded the maximum TW in the Reverse HY8 Table structure_hy8.f90<br />
Error Code is: 79<br />
| Computed water surface elevations near the culvert become extremely high. This could be from too large of a time step, poor mesh quality near the culvert faces, or parts of the mesh were the culvert is applied have higher elevations than what are defined as the inverts defined in the HY-8 culvert definition<br />
| Review mesh quality near the culvert face. Check to ensure that mesh node elevations where culvert faces are applied do not exceed invert elevations as defined in the HY8 culvert definition. Lowering the time step to improve stability around the culvert could also help.<br />
|-<br />
| SRH-2D<br />
| N/A<br />
| forrtl: severe (24): end-of-file during read, unit n, file {your filepath.dat} Image PC Routine Line Source srh2d_3.2_quickwi...Unknown...<br />
| This is usually a generic error indicating something is wrong with the SRH simulation casename.DAT file created by SRH pre. It typically signifies that SRH-Pre did not terminate normally and generate a valid simulation file. The cause of the error could be any number of issues.<br />
| Check for any error messages reported by SRH-pre by going to the SMS model wrapper and clicking on the "PreSRH-2D" line and reviewing the on screen output messages.<br />
|-<br />
| SRH-2D<br />
| 1<br />
| Program stopped due to the following: Stopped in read_input2: Mismatch in HY8 ID<br />
| This is a bug in SRH caused by having two culvert crossings defined in the *.hy8 crossing file with certain similarities in their names.<br />
| The temporary workaround until this is fixed is to make all crossing names as different as possible, including the first character of the names. For example, "My Culvert" and "My Culvert1" could cause this error. Change one of the crossings to make it different, something like "My Culvert" and "Two Barrel Wingwall" would resolve the issue.<br />
|-<br />
| SRH-2D<br />
| N/A<br />
| Failed to find a mesh cell which contains the following (x y) points: (X,Y)=<br />
| This is caused when there is a void added to the mesh by deleting a mesh element from the mesh after the mesh has been generated. Creating void by deleting mesh elements may not actually remove the element data from the mesh in SRH-2D. <br />
|If a void is needed in the mesh, it should be created as a polygon in the Mesh Generator coverage and given a mesh type of "None". When a mesh is generated using polygons with the "None" type, a void will be created in the mesh that can be recognized by SRH-2D.<br />
|-<br />
| SRH-2D<br />
| 0<br />
| Program stopped due to the following: IFACE match does not found in structure_culvert.f90 #''n''<br />
| Element configuration around the structure face is causing a mismatch in the transition into or out of the structure.<br />
| It may help to ensure all elements within the two structures are quadrilateral elements. It may also help to ensure that the first row of elements downstream of the downstream structure face and upstream of the upstream structure face are also quadrilateral elements that are "well formed" ("Well formed" elements as in having interior corners as close to 90 degrees as possible).<br />
|-<br />
| SRH-2D<br />
| 1<br />
| Program stopped due to the following: Stopped in read_input2.f90 HY8 Forward_TABLE Line Error<br />
| There is a problem reading the culvert table file. One of the causes of this is that the HY8 file containing the culvert definition does not include a file extension.<br />
| Add a ".hy8" file extension to the culvert defintion filename.<br />
|-<br />
|SRH-2D<br />
|N/A<br />
|forrtl: severe (170): Program Exception - stack overflow<br />
|The simulation is too large for SRH-2D to process. Typically this occurs when running a simulation using sediment transport and a 2D mesh that contains more than 50,000 elements.<br />
|Reduce the number of elements in the 2D mesh and try running the simulation again.<br />
|-<br />
|SRH-2D<br />
| 3<br />
| Not ready in solve.f90 SEDIMENT MODULE<br />
| This errors occurs when sediment transport is being modeled in a project containing 1D hydraulic structures (culverts, weirs, pressure bridges, etc.). SRH-2D cannot model sediment transport in models containing 1D hydraulic structures.<br />
| Either do not use the sediment transport in the model run, or remove the 1D hydraulic structures from the model.<br />
|-<br />
|PreSRH-2D<br />
| 4<br />
| Program stopped due to the following: Stopped in sec_blow NLAY Error Code is: 4<br />
| This errors occurs when sediment transport is on and there are more than the maximum number of allowed sediment layers (9) for one or more sediment materials.<br />
| Reduce the number of sediment layers to 9 or less in each sediment material.<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>Woodhttps://www.xmswiki.com/index.php?title=SMS:SRH-2D_Errors&diff=137418SMS:SRH-2D Errors2018-10-23T22:00:19Z<p>Wood: /* List of Error Messages */</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 />
An error may occur during either the Pre-SRH-2D process or during the SRH-2D process. During the run, errors will be listed in the SRH-2D model wrapper. Clicking the PreSRH-2D button in the model wrapper will display results from the pre-processor. Clicking the SRH-2D button will show results from the model run.<br />
<br />
If the model wrapper has been closed, two files are generated recording the model run. Opening the "*_.OUT.dat" or the "*_DIA.dat" files in a text editor will show errors in 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 Pre-processor 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 spline.f90 H<br />
| Time series data used to define inflows/outflows or time varying water surface elevations has issues with how it is defined, such as duplicate times. <br />
| The time series data should only have one data value per defined time. Go to the XY series editor where the time series data is defined and remove any and every duplicate time entry.<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 need 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 />
| In SMS v12.1, 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. Modify the placement of the structure arcs in the boundary condition coverage or unassigned material polygon edges so that the snap preview of the material polygon matches the snap preview of the structure arc. In SMS 12.2 or later, it is not necessary to create the unassigned material polygon to disable the area between the structure arcs because SRH-2D has been modified to do this internally. If encountering this error using 12.2 or later, one possible solution would be to delete the unassigned material polygon, rebuild polygons and double check all polygons to make sure valid material types have been assigned.<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 />
| Pre SRH-2D<br />
| <br />
| Errors from final_touch.f90 **** on MONITOR LINE#n<br> a face cannot be found given two mesh points<br><br />
Two points are: xx xx<br><br />
Check the mesh node list; do this using _SIF.dat file directly!<br />
| Monitor line spans a mesh void (hole)<br />
| Reconfigure the monitor line. Monitor lines cannot span holes in the mesh.<br />
|-<br />
| SRH-2D<br />
| <br />
| <br />
| If there is 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 />
| Material polygons near inflow are unassigned<br />
| This occurs when the material coverage has not been linked to the simulation. Also occurs when all material polygons covering the inflow BC are have an "unassigned" material type. This can also occur if no boundary conditions providing an inflow source have been included in the simulation.<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 computational time step in the model control<br />
|-<br />
| SRH-2D<br />
| 3<br />
| bad mesh ! Stopped in indx_conn.f<br />
| Problem in mesh, often due to overlapping elements. <br />
| Check if problem cell (element) id is listed. Otherwise, examine mesh quality in SMS.<br />
|-<br />
| SMS<br />
| <br />
| No mesh that matches the scalar set.<br />
| No mesh that matches the scalar set. The solution file does not correspond to the mesh in the project, or node numbering of the mesh has been changed, invalidating the solution.<br />
| Take care when making edits to the mesh and renumbering the nodes. Any previous results will be invalidated when nodes are renumbered.<br />
|-<br />
| <br />
| None<br />
| None<br />
| WSE error directly under the bridge in the form of waves oscillating through the channel<br />
| Use larger, quadrilateral elements in the deepest areas of flow. This could also mean that the piers need to be switched to obstructions. Lowering the time step may also help.<br />
|-<br />
|-<br />
| <br />
| None<br />
| None<br />
| SRH-2D is not recognizing a 1D structure or 2D pressure flow structure. When reviewing the 2D results or output files it does not appear that SRH-2D is using a structure such as a culvert, pressure flow bridge structure, weir, or gate.<br />
| Make sure the pair of arcs in the SRH-2D boundary condition coverage representing the faces of the structure were created in the same topologic direction. (i.e. Both were created left to right looking downstream or both were created right to left downstream.) The direction does not matter, just that both arcs are consistent. Turn on the display of arc "Direction" in the display options for the map arcs. This will add an arrow to the map arcs in the display denoting their topologic direction.<br />
|-<br />
| SMS<br />
| <br />
| The following coverage(s) have an unsupported type and will be converted to area property: ''(Name of Coverage(s) Listed)''<br />
| <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), further troubleshooting is required if it has not finished running successfully.<br />
|-<br />
| <br />
| 1<br />
| Error code 1<br />
| srhmat file does not exist<br />
| File didn't export successfully. Make sure materials are assigned in the materials coverage.<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 />
| 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 />
| 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 the 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 />
| SRH-2D<br />
| 1<br />
| Stopped in structure_pressure_flow.f90 PARA DISTANCE<br />
| Shape of pressure zone is not acceptable for a parabolic type bridge ceiling<br />
| Ensure that the pressure zone, between the pressure flow arcs, is rectangular in shape<br />
|-<br />
| SRH-2D<br />
| 9669<br />
| Program stopped due to the following:<br />
Wrong IFACE matching occurred in structure_internal.f90 #4<br />
Error Code is: 9669<br />
| Ensure that the area between the pressure zone arcs with overtopping turned on is rectangular in shape and that the elements in between the arcs are quads (rectangles).<br />
| Create a new mesh with a rectangle between pressure flow arcs and which has quads in this area using the patch mesh generation method.<br />
|-<br />
| SRH-2D<br />
| 16026<br />
| Program stopped due to the following: <br />
A downstream Structure nodestring has not set right; structure_culvert.f90 ICELL error#2<br />
Error Code is: 16026<br />
| The 2D mesh around and through the structure is not optimal.<br />
| Re-mesh areas around the structure. Suggestions to optimize the mesh around the structure include creating patched (quadrilateral) elements through the structure from one face to the other. SRH-2D inactivates elements between the structure faces where the 1D flow is computed. Creating quadrilateral elements in the zone between the faces facilitates the process SRH uses to locate and inactivate the flow computations for those elements in the mesh. Configure the mesh such that the structure faces can be created alone a series of element edges that are oriented in the same direction (along a flat and straight line of element edges).<br />
|-<br />
| SRH-2D<br />
| 79<br />
| Program stopped due to the following:<br />
Tailwater WSE exceeded the maximum TW in the Reverse HY8 Table structure_hy8.f90<br />
Error Code is: 79<br />
| Computed water surface elevations near the culvert become extremely high. This could be from too large of a time step, poor mesh quality near the culvert faces, or parts of the mesh were the culvert is applied have higher elevations than what are defined as the inverts defined in the HY-8 culvert definition<br />
| Review mesh quality near the culvert face. Check to ensure that mesh node elevations where culvert faces are applied do not exceed invert elevations as defined in the HY8 culvert definition. Lowering the time step to improve stability around the culvert could also help.<br />
|-<br />
| SRH-2D<br />
| N/A<br />
| forrtl: severe (24): end-of-file during read, unit n, file {your filepath.dat} Image PC Routine Line Source srh2d_3.2_quickwi...Unknown...<br />
| This is usually a generic error indicating something is wrong with the SRH simulation casename.DAT file created by SRH pre. It typically signifies that SRH-Pre did not terminate normally and generate a valid simulation file. The cause of the error could be any number of issues.<br />
| Check for any error messages reported by SRH-pre by going to the SMS model wrapper and clicking on the "PreSRH-2D" line and reviewing the on screen output messages.<br />
|-<br />
| SRH-2D<br />
| 1<br />
| Program stopped due to the following: Stopped in read_input2: Mismatch in HY8 ID<br />
| This is a bug in SRH caused by having two culvert crossings defined in the *.hy8 crossing file with certain similarities in their names.<br />
| The temporary workaround until this is fixed is to make all crossing names as different as possible, including the first character of the names. For example, "My Culvert" and "My Culvert1" could cause this error. Change one of the crossings to make it different, something like "My Culvert" and "Two Barrel Wingwall" would resolve the issue.<br />
|-<br />
| SRH-2D<br />
| N/A<br />
| Failed to find a mesh cell which contains the following (x y) points: (X,Y)=<br />
| This is caused when there is a void added to the mesh by deleting a mesh element from the mesh after the mesh has been generated. Creating void by deleting mesh elements may not actually remove the element data from the mesh in SRH-2D. <br />
|If a void is needed in the mesh, it should be created as a polygon in the Mesh Generator coverage and given a mesh type of "None". When a mesh is generated using polygons with the "None" type, a void will be created in the mesh that can be recognized by SRH-2D.<br />
|-<br />
| SRH-2D<br />
| 0<br />
| Program stopped due to the following: IFACE match does not found in structure_culvert.f90 #''n''<br />
| Element configuration around the structure face is causing a mismatch in the transition into or out of the structure.<br />
| It may help to ensure all elements within the two structures are quadrilateral elements. It may also help to ensure that the first row of elements downstream of the downstream structure face and upstream of the upstream structure face are also quadrilateral elements that are "well formed" ("Well formed" elements as in having interior corners as close to 90 degrees as possible).<br />
|-<br />
| SRH-2D<br />
| 1<br />
| Program stopped due to the following: Stopped in read_input2.f90 HY8 Forward_TABLE Line Error<br />
| There is a problem reading the culvert table file. One of the causes of this is that the HY8 file containing the culvert definition does not include a file extension.<br />
| Add a ".hy8" file extension to the culvert defintion filename.<br />
|-<br />
|SRH-2D<br />
|N/A<br />
|forrtl: severe (170): Program Exception - stack overflow<br />
|The simulation is too large for SRH-2D to process. Typically this occurs when running a simulation using sediment transport and a 2D mesh that contains more than 50,000 elements.<br />
|Reduce the number of elements in the 2D mesh and try running the simulation again.<br />
|-<br />
|SRH-2D<br />
| 3<br />
| Not ready in solve.f90 SEDIMENT MODULE<br />
| This errors occurs when sediment transport is being modeled in a project containing 1D hydraulic structures (culverts, weirs, pressure bridges, etc.). SRH-2D cannot model sediment transport in models containing 1D hydraulic structures.<br />
| Either do not use the sediment transport in the model run, or remove the 1D hydraulic structures from the model.<br />
|-<br />
|PreSRH-2D<br />
| 4<br />
| Program stopped due to the following: Stopped in sec_blow NLAY Error Code is: 4<br />
| This errors occurs when sediment transport is on and there are more than the maximum number of allowed sediment layers (9) for one or more sediment materials.<br />
| Reduce the number of sediment layers to 9 or less in each sediment material.<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>Woodhttps://www.xmswiki.com/index.php?title=SMS:SRH-2D_Errors&diff=134421SMS:SRH-2D Errors2018-02-27T22:35:36Z<p>Wood: /* List of Error Messages */</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 need 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 />
| Pre SRH-2D<br />
| <br />
| Errors from final_touch.f90 **** on MONITOR LINE#n<br> a face cannot be found given two mesh points<br><br />
Two points are: xx xx<br><br />
Check your mesh node list; you may do this using _SIF.dat file directly!<br />
| Monitor line spans a mesh void (hole)<br />
| Reconfigure the monitor line. Monitor lines cannot span holes in the mesh.<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 />
| Material polygons near inflow are unassigned<br />
| This occurs when the material coverage has not been linked to the simulation. Also occurs when all material polygons covering the inflow BC are have an "unassigned" material type. This can also occur if no boundary conditions providing an inflow source have been included in the simulation.<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 computational time step in the model control<br />
|-<br />
| SRH-2D<br />
| 3<br />
| bad mesh ! Stopped in indx_conn.f<br />
| Problem in mesh, often due to overlapping elements. <br />
| Check if problem cell (element) id is listed. Otherwise, examine mesh quality in SMS.<br />
|-<br />
| SMS<br />
| <br />
| No mesh that matches the scalar set.<br />
| No mesh that matches the scalar set. The solution file does not correspond to the mesh in the project, or node numbering of the mesh has been changed, invalidating the solution.<br />
| Take care when making edits to the mesh and renumbering the nodes. Any previous results will be invalidated when nodes are renumbered.<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 deepest areas of flow. This could also mean that the piers need to be switched to obstructions. Lowering the time step may also help.<br />
|-<br />
| SMS<br />
| <br />
| The following coverage(s) have an unsupported type and will be converted to area property: ''(Name of Coverage(s) Listed)''<br />
| <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), further troubleshooting is required if it has not finished running successfully.<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 />
| 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 />
| 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 />
| 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 />
| SRH-2D<br />
| 1<br />
| Stopped in structure_pressure_flow.f90 PARA DISTANCE<br />
| Shape of pressure zone is not acceptable for a parabolic type bridge ceiling<br />
| Ensure that the pressure zone, between the pressure flow arcs, is rectangular in shape<br />
|-<br />
| SRH-2D<br />
| 9669<br />
| Program stopped due to the following:<br />
Wrong IFACE matching occurred in structure_internal.f90 #4<br />
Error Code is: 9669<br />
| Ensure that the area between the pressure zone arcs with overtopping turned on is rectangular in shape and that the elements in between the arcs are quads (rectangles).<br />
| Create a new mesh with a rectangle between pressure flow arcs and which has quads in this area using the patch mesh generation method.<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>Woodhttps://www.xmswiki.com/index.php?title=SMS:CGWAVE_Model_Control&diff=127686SMS:CGWAVE Model Control2017-08-14T16:01:28Z<p>Wood: fixed 2 typos</p>
<hr />
<div>[[Image:CGWAVE Model Control.jpg|thumb|500 px|''CGWAVE Model Control'' dialog]]<br />
The [[SMS:CGWAVE|CGWAVE]] model requires several user-specified parameters to control the analysis. The '''Model Control''' command from the [[SMS:CGWAVE Graphical Interface#CGWAVE Menu|''CGWAVE'' menu]] opens the ''Model Control'' dialog. This dialog contains parameters that control the execution of CGWAVE. The parameter description for each field is displayed in SMS using the interactive help messages.<br />
<br />
Controls include:<br />
* ''Title''<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
Enter the simulation name. This will be used for naming the generated datasets during the model run.<br />
</blockquote><br />
* ''Incident Wave Conditions''<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
The ''Incident Wave Conditions'' section specifies wave conditions to be simulated in a run. See [[SMS:CGWAVE Incident Wave Conditions|CGWAVE Incident Wave Conditions]] for more information. </blockquote><br />
* ''Open Boundary''<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
The ''Open Boundary'' section specifies the open boundary type. This should match the type selected when generating the domain in the Map Module. If the mesh has been generated using other methods, the domain shape must match the ''Open Boundary'' type. <br />
*''Semicircular''<br />
*''Circular''<br />
*''Boundary condition:''<br />
</blockquote><br />
*'' 1-D Options''<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
The 1-D section specifies the number of nodes and the nodal spacing for the one-dimensional data that is used to distribute incident wave data to the open boundary. The file format is described in the CGWAVE user manual[http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=Software;21]. The '''Compute 1-d Length''' button calculates the 1-d Spacing variable such that the specified number of nodes will extend to the limits of the bathymetry data. This bathymetry data is defined by a scattered dataset. Therefore, a scatter dataset must exist in order for this button to be active. If no scatter data exists, generate an appropriate file containing the one-dimensional depth values.</blockquote><br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
*''Current 1D Wave Line Settings''<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
* ''Spacing:''<br />
* ''Length:''<br />
* ''Number of nodes:''<br />
</blockquote><br />
*''1D Domain Extension Parameters''<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
* ''Length to edge of scatter:''<br />
* ''Radius of domain:''<br />
* ''Ideal 1D spacing:''<br />
* ''1D spacing''<br />
* ''Num. of Nodes''<br />
* ''Minimum 1D Depth''<br />
* ''Update Num. of Nodes''<br />
* ''Update Spacing''<br />
* ''Extract Depths''<br />
</blockquote></blockquote><br />
* ''Solver Options''<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
CGWAVE support two separate numerical solvers for robustness. Select which solver to use via the ''Solver'' radio group. The ''Standard solver'' should be utilized first. If CGWAVE fails to converge, the ''Modified'' method can be utilized.<br />
*''Solver:''<br />
*''Convergence tolerance:''<br />
*''Output echo frequency:''<br />
*''Maximum iterations:''<br />
*''Num. of bessel terms used:''<br />
</blockquote><br />
* ''Iteration Control''<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
CGWAVE allows specifying the maximum number of iteration to be performed by the numerical solver. This number is specified in the ''Maximum Iterations'' edit field. The solver will terminate after performing the maximum number of iterations or when the change in the solution is less than the convergence tolerance specified in the ''Convergence Tolerance'' edit field. It is recommended that the convergence value be between 1.0e-6 and 1.0e-9. CGWAVE will print a progress report on the tolerance at the user specified report interval entered in the ''Convergence Interval'' edit field.</blockquote><br />
* ''General Parameters''<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
CGWAVE includes options to model bottom friction, wave breaking and nonlinear dispersion. These options may be enabled using the appropriate toggle box. See the CGWAVE user manual for more information about these parameters.<br />
*''Bottom friction''<br />
*''Wave breaker''<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
*''Breaking coefficient''</blockquote><br />
*''Nonlinear dispersion relation''<br />
<blockquote style="margin-top:0px; margin-bottom:0px;"><br />
*''Convergence tolerance''<br />
*''Maximum iterations''<br />
</blockquote></blockquote><br />
<br />
==Related Topics==<br />
* [[SMS:CGWAVE Graphical Interface|CGWAVE Graphical Interface]]<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
<br />
[[Category:CGWAVE|Mod]]<br />
[[Category:CGWAVE Dialogs|mod]]<br />
[[Category:SMS Model Control|C]]<br />
[[Category:External Links]]</div>Woodhttps://www.xmswiki.com/index.php?title=GMS:Horizons&diff=95793GMS:Horizons2015-11-11T03:23:33Z<p>Wood: /* Assigning Horizons to Boreholes */</p>
<hr />
<div>{{Horizons Links}}<br />
The term “horizon” refers to the top of each stratigraphic unit that will be represented in a corresponding Solid, HUF unit, or 3D Mesh Layer. Horizons are numbered consecutively in the order that the strata are “deposited” (from the bottom up). Horizons can be assigned to [[GMS:Boreholes|Boreholes]], [[GMS:TIN Module|TINs]], and [[GMS:Coverages|Coverages]]. Beginning with version 9.0, [[GMS:Raster Catalog|raster catalogs]] can also be used to define horizons.<br />
<br />
Once horizons have been assigned to boreholes, TINs, and/or [[GMS:Rasters|Rasters]], the [[GMS:Horizons Wizard|Horizons Wizard]] can be used to create solids, 3D mesh, or HUF data.<br />
<br />
== Assigning Horizons to Boreholes==<br />
On boreholes, Horizons are defined at borehole contacts. Each contact that the user wishes to include in the construction of the solid must have a non-zero horizon ID. If the user wishes to ignore a contact, this can be done by leaving the horizon ID set to zero. Horizons are numbered in the order that the strata are “deposited” (from the bottom up). Gaps can exist in the horizon numbering. For example, horizons can be assigned using 1, 2, 3, etc..., or the user could assign horizons using 10, 20, 30, etc... Using larger numbers with gaps can be useful if more horizons are added at a later time.<br />
<br />
=== Automatic Assignment ===<br />
<br />
To have GMS automatically assign horizon IDs to boreholes, use the ''Boreholes'' | '''Auto-Assign Horizons''' menu command. Depending on the number and complexity of the boreholes, this command can take a considerable amount of time.<br />
<br />
=== Manual Assignment ===<br />
<br />
Horizons are defined at borehole contacts (interface between different materials on a borehole log) by double clicking on a contact with the [[GMS:Borehole Tool Palette|'''Select Contact''']] tool. The [[GMS:Creating and Editing Boreholes#Auto Select|''Boreholes'' | '''Auto Select''']] command can be helpful in assigning horizons to a large group of boreholes.<br />
<br />
[[Image:samp_bor.gif|none|frame|Horizons assigned to contacts on boreholes]]<br />
<br />
== Assigning Horizons to TINs ==<br />
A TIN Horizon is assigned in the TIN ''Properties'' dialog. This dialog can be accessed by right-clicking on a TIN in the [[GMS:The GMS Window|Project Explorer]] and selecting the properties command. Each TIN can be assigned one Horizon ID. Each TIN that the user wishes to include in the horizons algorithm must have a horizon ID. If the user wishes to ignore a TIN, this can be done by setting the horizon ID to zero.<br />
<br />
[[Image:Hor_Asg_TIN.jpg|thumb|none|300 px|Horizons assigned to contacts in TIN ''Properties'' dialog]]<br />
<br />
== Assigning Horizons to Rasters ==<br />
Raster can also be used to define horizons. See the [[GMS:Raster Catalog|Raster Catalog]] page for more information on using Rasters with horizons.<br />
<br />
{{Navbox GMS}}<br />
<br />
[[Category:Stratigraphy]]<br />
[[Category:Horizons]]<br />
[[Category:GMS Dialogs|H]]</div>Woodhttps://www.xmswiki.com/index.php?title=SMS:CMS-Flow_Hard_Bottom&diff=91039SMS:CMS-Flow Hard Bottom2015-08-27T15:51:36Z<p>Wood: </p>
<hr />
<div>CMS-Flow includes a Hard Bottom morphologic constraint that "provides the capability to simulate mixed bottom types within a single simulation," (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], p. 33). Hard bottom is a cell depth constraint applied to areas of the grid which represent exposed or covered non-erodible material such as bedrock. This specification limits the erosion of sediment to the hard bottom depth and therefore constrains water depth. During sediment transport calculations, exposed hard bottom cells may become covered through deposition.<br />
<br />
By default, CMS-Flow cells are fully-erodible cells with no specified hard bottom depth (inactive cells; denoted by the<br />
CMS-Flow null value of -999.0).<br />
<br />
When specified, cell hard bottom depths will appear in the Project Explorer as a scalar dataset beneath the CMS-Flow grid. This dataset can not be deleted, though it can be edited like any other dataset. A CMS-Flow simulation must contain the hard bottom dataset (even if it is not specified) so SMS will create a defaulted (inactive cells) dataset if it does not already exist when saving the simulation.<br />
<br />
Hard bottom should be specified only for computational (ocean) cells.<br />
<br />
The hard bottom dataset can be created, edited, viewed and verified using the following SMS interface features.<br />
<br />
== Model Control ==<br />
<br />
Within the CMS-Flow Model Control window, the hard bottom dataset can be created from the ''Sediment'' tab. If the dataset does not exist, it can be created using the '''Create Dataset''' button. If a dataset exists (created using the Data Calculator) which represents the intended hard bottom specifications, the '''Select Dataset...''' button can be used to select such dataset and copy the values to the hard bottom dataset.<br />
<br />
== Hard Bottom Specification ==<br />
[[Image:CMS-Flow Hard Bottom.jpg|thumb|250 px|''CMS-Flow Hard Bottom Specification'' dialog]]<br />
Although the hard bottom dataset can be edited (when its the active dataset) by selecting a cell (or group of cells) and changing the scalar (S) value in the ''Edit Window'', an user-friendly window exists which provides specification options. With the '''Select Grid Cell''' tool active, make a selection, right-click to bring up the tool menu and choose the '''Specify Hard Bottom...''' option.<br />
<br />
This will open the ''CMS-Flow Hard Bottom Specification'' window.<br />
<br />
The following options are provided in the ''Hard Bottom Specification'' window:<br />
*'''Use bathymetric cell depth''' &ndash; Sets the cell hard bottom depth to be the cell geometry value thereby creating an exposed non-erodible condition. If multiple cells were selected, then each cell will use its respective bathymetric depth.<br />
*'''Specified distance below bathymetric cell depth''' &ndash; Sets the cell hard bottom depth to be the cell geometry value plus the specified distance thereby creating a sediment-covered non-erodible condition. The distance is limited to positive values to ensure the hard bottom depth is greater than the geometry value. The cell can provide sediment for transportation, however, the amount of erosion is limited. If multiple cells were selected, then each cell will use its respective bathymetric depth.<br />
*'''Specified depth''' &ndash; Sets the cell hard bottom depth to the specified depth thereby creating a sediment-covered non-erodible condition similar to specified distance. The depth is limited to greater than the geometry value. If multiple cells were selected, then the depth is limited to greater than the largest geometry value and all cells will have the same value.<br />
*'''Unspecified''' &ndash; Resets to an inactive hard bottom condition. The cell hard bottom depth is set to the CMS-Flow null value. If multiple cells were selected, then all cells will be reset.<br />
<br />
If no cells are selected when opening the ''Hard Bottom Specification'' window, then all computational (ocean) cells will be used. If a selection of only non-computational cells, then specification cannot occur. If a selection contains computational and non-computational cells, then the specification will only apply to the computational cells.<br />
<br />
If multiple computational cells with differing specifications are selected, the window will not display a selected specification type and the '''OK''' button will be disabled. This is to protect the previous specifications from being overwritten by mistake. The '''OK''' button will be enabled when an option is selected. The minimum hard bottom depth of the multiple computational cells selected will be displayed in the ''Depth'' edit field and the minimum hard bottom depth minus the maximum geometry depth of the multiple computational cells selected will be displayed in the ''Distance'' edit field.<br />
<br />
== Display Options ==<br />
[[Image:CMS-Flow Hard Botttom Symbols.jpg|thumb|250 px|''CMS-Flow Hard Bottom Symbols'' dialog]]<br />
The hard bottom dataset (when its the active dataset) will only display the cells with hard bottom specified if the ''Ocean cell'' display option is turned on. Inactive hard bottom cells are not displayed.<br />
<br />
CMS-Flow includes hard bottom symbols to differentiate specifications. On the ''Cartesian Grid'' page of the ''Display Options'' window (when CMS-Flow is the active model), the ''Hard bottom symbols'' check box controls the display of symbols that will appear in hard bottom cells (even if the hard bottom dataset is not active). If this is turned on, then the user must be aware of the individual symbol settings accessed by clicking on the '''Options...''' button. The '''Options...''' button displays the ''CMS-Flow Hard Bottom Symbols'' window.<br />
<br />
Hard bottom symbols can be selected for three hard bottom specification types:<br />
*'''Non-erodible''' &ndash; Displayed in exposed hard bottom cells (cell hard bottom depth is equal to cell bathymetric depth).<br />
*'''Erodible to specified depth''' &ndash; Displayed in sediment-covered hard bottom cells (cell hard bottom depth is greater than cell bathymetric depth).<br />
*'''Invalid specification''' &ndash; Displayed in hard bottom cells where the hard bottom depth is less than cell bathymetric depth (the geometry is below the erosion limit).<br />
<br />
If the ''Hard bottom symbols'' check box is turned off, no symbols will be displayed and the individual settings cannot be accessed, however, the individual settings will not be changed.<br />
<br />
== Model Check ==<br />
The CMS-Flow Model Checker, accessed from the ''CMS-Flow'' | '''Model Check...''' menu item, includes a check to ensure that no invalid hard bottom specifications exist in the grid. An invalid specification may be created, for example, by setting an infeasible hard bottom scalar value in the Edit Window or adjusted the grid's geometry without updating the hard bottom. It is suggested that the model checker be used prior to running CMS-Flow.<br />
<br />
== Related Topics ==<br />
* [[SMS:CMS-Flow|CMS-Flow]]<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
<br />
[[Category:CMS-Flow|H]]<br />
[[Category:SMS Dialogs|C]]<br />
[[Category:External Links]]</div>Woodhttps://www.xmswiki.com/index.php?title=SMS:CMS-Wave_Spectral_Coverage&diff=83233SMS:CMS-Wave Spectral Coverage2015-02-24T23:03:43Z<p>Wood: </p>
<hr />
<div><center>'''''Information on this page pertains to SMS version 11.1 and earlier.</center><br />
==Spatially Varied Boundary Conditions==<br />
CMS-Wave has the ability to read in spectral data from various locations defined in a nesting file. Within SMS, this spectral data is defined using a spectral coverage. Each node in this coverage can be assigned to one spectral grid, defining the conditions at that location.<br />
<br />
==Coverage Properties==<br />
All spectral grids in a spectral coverage must have the same orientation and size. These grid parameters are defined in the ''Cover Properties'' dialog, which can be accessed by right-clicking on the coverage in the project explorer and selecting '''Properties...'''. The following grid attributes can be assigned:<br />
<br />
* '''Plane type''' (full or half) &ndash; SMS currently supports only half-plane <br />
* '''Angle''' &ndash; set the grid orientation<br />
<br />
[[Image:Spectral_Grid_Properties.jpg|thumb|250 px|''Spectral Grid Properties'' dialog]]<br />
==== Frequency Distribution ==== <br />
* '''Number''' &ndash; Set the number of frequency bands (Number = 30) <br />
* '''Delta''' &ndash; Set the step size (Delta = 0.01) in Hz. <br />
* '''Minimum''' &ndash; Set the minimum frequency (Minimum = 0.04) in Hz. <br />
* '''Maximum''' &ndash; View the maximum frequency (Maximum = 0.33) in Hz. <br />
<br />
====Angle Distribution==== <br />
* '''Number''' &ndash; View the number of angle bands (Number = 35). <br />
* '''Delta''' &ndash; Set the step size (Delta = 5) in degrees. <br />
* '''Minimum''' &ndash; View the minimum angle (Minimum = 0.0) in degrees. <br />
* '''Maximum''' &ndash; View the maximum angle (Maximum = 360.0) in degrees.<br />
<br />
==Creating Spectral Data==<br />
To create spectral data at a node in the spectral coverage, right-click on the node and select '''Node Attributes...'''. This will bring up the ''Spectral Energy'' dialog, from which a spectral grid and spectra can be created. Note that each node may only have one spectral grid at a time. See [[SMS:Generate/Edit Spectra|Generate/Edit Spectra]].<br />
<br />
==Using a Spectral Coverage With a CMS-Wave Model==<br />
A CMS-Wave model can be set to use a spectral coverage for spatially varied input by selecting ''Spatially varied'' in the ''Spectra'' section of the model control. By clicking on the '''Select...''' button, you can select which spectral coverage should be associated with the model. See [[SMS:CMS-Wave Model Control|CMS-Wave Model Control]].<br />
<br />
It is required that number of defined spectral cases in the model control does not exceed the number of datasets associated with spectral input defined in the spectral coverage.<br />
<br />
==Creating a CMS-Wave Spectral Event==<br />
[[Image:CMS-Wave Spectral Event.jpg|thumb|none|500 px|''CMS-WAve Spectral Event'' dialog]]<br />
<br />
== Related Topics ==<br />
* [[SMS:CMS-Wave|CMS-Wave]]<br />
* [[SMS:Spectral Energy|Spectral Energy]]<br />
<br />
{{Template:Navbox SMS}}<br />
<br />
[[Category:CMS-Wave|S]]</div>Woodhttps://www.xmswiki.com/index.php?title=SMS:Observation_Coverage&diff=82970SMS:Observation Coverage2015-02-06T16:57:58Z<p>Wood: </p>
<hr />
<div>SMS contains what is called an observation coverage that is designed to help in model verification and calibration processes. Result verification is an important part of the computer modeling process. SMS includes a number of powerful tools, associated with an observation coverage, that allow users to verify simulation results with observed data. The two tools used for verification and calibration in an observation coverage are observation points and observation arcs. Observation points are used to verify the numerical analysis with measured field data such as water surface elevation or velocity data. They are also be used to see how computed values change with time at a particular location. Observation arcs are used to view the results at a cross section or along the river profile. These tools can be used with any of the SMS models.<br />
<br />
== Creating an Observation Coverage ==<br />
To create a new observation coverage:<br />
# Right-click the ''Map Data'' item in the ''Project Explorer''<br />
# Select '''New Coverage''' from the right-click menu<br />
# Set the coverage type to ''Generic &rarr; Observation'' in the ''New Coverage'' dialog<br />
# Set the coverage name as desired<br />
# Click '''OK''' to exit the dialog<br />
Alternatively, an existing coverage can be changed to an observation coverage by right-clicking on the coverage in the [[SMS:Project Explorer|Project Explorer]] and setting the type to ''Observation'' using the right-click menu.<br />
<br />
== Creating an Observation Point ==<br />
Observation points are created at locations in the model where calibration data such as the velocity or water surface elevation has been measured in the field. Each observation point is used to compare the measured values with the values computed by the model at the point's x, y location. This comparison can assist the modeler in determining the accuracy of the numerical model results. If the numerical model results do not match the observed field data, model parameters such as manning's roughness may need to be modified to obtain more accurate results.<br />
<br />
Creating an observation point is just like creating a feature point in any other coverage type. Select the [[SMS:Map Module Tools|Create Feature Point tool]] from the [[SMS:Dynamic_Tools|Dynamic Toolbar]] and click the location for the feature point.<br />
<br />
== Creating an Observation Arc ==<br />
Observation arcs are created at cross sections in the model where calibration data such as the flowrate has been measured in the field. Observation arcs compute fluxes across the arc. Therefore, measurements for observation arcs are called ''Flux Measurements''. Each obseration arc is used to compare the measured values with the values computed by the model across the vertical plane defined by the arc. This comparison can assist the modeler in determining the accuracy of the numerical model results. If the numerical model results do not match the observed field data, model parameters such as manning's roughness may need to be modified to obtain more accurate results.<br />
<br />
Creating an observation arc is just like creating a feature arc in any other coverage type. Select the [[SMS:Map Module Tools|'''Create Feature Arc''' tool]] from the [[SMS:Dynamic Tools|Dynamic Toolbar]] and click out an arc. Double-click to end the arc. In an observation coverage, profile arcs and cross section arcs may be useful to analyze a simulation's solution.<br />
<br />
== Setting Observation Object Attributes ==<br />
Observation point and arc attributes are defined in the [[SMS:Observation Coverage#Observation Coverage Dialog|Observation Coverage dialog]]. See [[SMS:Observation Coverage#Observation Coverage Dialog|Observation Coverage dialog]] for a description of the ''Observation Coverage'' dialog.<br />
<br />
<br />
[[Image:Observ_arcs1.JPG]]<br />
<br />
== Viewing Results ==<br />
In addition to viewing the results of the solution data versus the observed data on the calibration targets, additional plots can be created using the [[SMS:Plot Window|Plot Wizard]]. See [[SMS:Plot Window|Plot Window]] for a description of the available plot types.<br />
<br />
== Calibration ==<br />
<br />
Calibration is the process of modifying the input parameters to a model until the output from the model matches an observed set of data. SMS includes a suite of tools to assist in the process of calibrating a model. Both point and flux observations are supported. Most of the calibration tools can be used with any of the models in SMS.<br />
<br />
Measurement types can be defined in SMS. They are defined in the map module and are associated with points and arcs in an observation coverage. Point observations represent locations in the field where some value has been observed. In most cases, the points will correspond to gauges or high water marks and the value will be the elevation of the water (the head) or a flow velocity (and possibly direction). Flux observations represent linear or areal objects such as streams gages where the flow rate has been measured or estimated. Both point and flow observations can be assigned a confidence interval or calibration target.<br />
<br />
Once a set of observed point and flow values has been entered, each time a model solution is imported, SMS automatically interpolates the computed solution to the observation points. A calibration target representing the magnitude of the residual error is displayed next to each observation point and each flux object as shown below. The size of the target is based on the confidence interval or the standard deviation. In addition to the calibration targets next to the observation points, a user can choose to display any of a number of statistical plots.<br />
<br />
== Calibration Target ==<br />
<br />
If an observed value has been assigned to an observation point or if an observed flow has been assigned to an arc or polygon, the calibration error at each object can be plotted using a "calibration target". A set of calibration targets provides useful feedback on the magnitude, direction (high, low), and spatial distribution of the calibration error.<br />
<br />
The components of a calibration target are illustrated in the following figure. The center of the target corresponds to the observed value. The top of the target corresponds to the observed value plus the interval and the bottom corresponds to the observed value minus the interval. The colored bar represents the error. If the bar lies entirely within the target, the color bar is drawn in green. If the bar is outside the target, but the error is less than 200%, the bar is drawn in yellow. If the error is greater than 200%, the bar is drawn in red. The display options related to calibration targets are specified in the ''Calibration Display Options'' dialog.<br />
<br />
If the active time step is before the first observed time, or after the last observed time, the targets are drawn lighter.<br />
<br />
[[Image:Calibration_targets.JPG|thumb|none|left|350 px|Components of a calibration target. ]]<br />
<br />
== Calibration Display Options ==<br />
Calibration targets are drawn next to their corresponding map data (point, arc, polygon). The ''Feature Objects Display Options'' dialog contains a toggle labeled ''calibration targets''. Below the toggle is a ''Scale'' edit field.<br />
<br />
The target is drawn such that the height of the target is equal to twice the confidence interval (+ interval on top, - interval on bottom). The Scale edit field allows the user to change the general length and width of the targets independent of the range of the active dataset.<br />
<br />
==Observation Coverage Dialog==<br />
[[Image:SMS Observation.jpg|thumb|400 px|''Observation Coverage'' dialog]]<br />
The ''Observation Objects'' dialog has two sections used to define the attributes of the points and arcs created in the observation coverage. To open the ''Observation Coverage'' dialog:<br />
# Make the observation coverage active in the [[SMS:Project Explorer|Project Explorer]]<br />
# Select the [[SMS:Map Module Tools|'''Create Feature Point''']] or [[SMS:Map Module Tools|'''Create Feature Arc''']] tool from the [[SMS:Dynamic_Tools|Dynamic Toolbar]]<br />
# Select a feature point or feature arc<br />
# Select the menu command ''Feature Objects'' | '''Attributes''' or double-click in the previous step<br />
<br />
=== Dialog Layout ===<br />
The options in the dialog will differ slightly based on the feature object type currently being edited (arc or point). The feature object type is specified using the combo box in the upper right of the dialog.<br />
<br />
In addition to a unique Name and Dataset(s), two other parameters are used to define the data represented by a measurement: ''Trans'' and ''Module''. When analyzing data that varies through time, select the ''Trans'' toggle. The Module of a measurement refers to the SMS module where the computed data is stored. (The Module is set by default and normally does not need to be changed.)<br />
<br />
=== Observation Point Attributes ===<br />
When "points" is selected in the Feature object type combo box, the top section of the dialog is entitled ''Measurements'' and the bottom section is entitled ''Observation Points.'' The ''Measurements'' section is used to specify which datasets correspond with the observed data entered in the ''Observation Points'' section. The ''Measurements'' section is used to enter the observed data at each point. Each observation point is assigned the following attributes:<br />
* '''Color''' &ndash; Color of the observation point.<br />
* '''Observe''' &ndash; Turn the observation point on or off.<br />
* '''Name''' &ndash; Name of the observation point.<br />
* '''X''' &ndash; X-location of the point.<br />
* '''Y''' &ndash; Y-location of the point.<br />
* '''Observed Value''' &ndash; Value measured in the field corresponding to the active measurement.<br />
* '''Interval''' &ndash; Allowable error (±) between the computed value and the observed value. Model verification is achieved when the error is within the interval (±) of the observed value.<br />
* '''Angle''' &ndash; When a measurement for observation points is tied to a vector dataset (as is the case with a Velocity measurement) an angle needs to be specified. This angle is an azimuth angle (measured clockwise from north) with the top of the screen representing north when in plan view.<br />
<br />
=== Observation Arc Attributes ===<br />
If "arcs" is selected in the combo box, then the top spreadsheet had the name ''Flux Measurements'' and the bottom spreadsheet has the name of ''Observation Arcs.''<br />
<br />
To define an arc measurement, the Name must first be defined. In addition to a unique Name, a scalar and vector dataset must be assigned to it. Two other parameters are also used to define the data represented by a measurement: ''Trans'' and ''Module''. When analyzing data that varies through time, select the ''Trans'' toggle. The ''Module of a measurement'' refers to the SMS module where the computed data is stored. (The Module is set by default and normally does not need to be changed.)<br />
<br />
Each observation arc is assigned the following attributes:<br />
* '''Color''' &ndash; Color of the observation arc.<br />
* '''Observe''' &ndash; Turn the observation arc on or off.<br />
* '''Name''' &ndash; Name of the observation arc.<br />
* '''x-origin''' &ndash; X origin of the arc (used to modify the x-value used in plots).<br />
* '''Observed Value''' &ndash; Value measured in the field corresponding to the active measurement.<br />
* '''Interval''' &ndash; Allowable error (±) between the computed value and the observed value. Model verification is achieved when the error is within the interval (±) of the observed value.<br />
<br />
==Related Topics==<br />
* [[SMS:Coverages|Coverages]]<br />
* [[SMS:Plot Window|Plot Window]]<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
<br />
[[Category:SMS Map|Observation Coverage]]<br />
[[Category:SMS Coverages|O]]<br />
[[Category:SMS Dialogs|O]]</div>Woodhttps://www.xmswiki.com/index.php?title=SMS:Observation_Coverage&diff=82969SMS:Observation Coverage2015-02-06T16:57:09Z<p>Wood: </p>
<hr />
<div>SMS contains what is called an observation coverage that is designed to help in model verification and calibration processes. Result verification is an important part of the computer modeling process. SMS includes a number of powerful tools, associated with an observation coverage, that allow users to verify simulation results with observed data. The two tools used for verification and calibration in an observation coverage are observation points and observation arcs. Observation points are used to verify the numerical analysis with measured field data such as water surface elevation or velocity data. They are also be used to see how computed values change with time at a particular location. Observation arcs are used to view the results at a cross section or along the river profile. These tools can be used with any of the SMS models.<br />
<br />
== Creating an Observation Coverage ==<br />
To create a new observation coverage:<br />
# Right-click the ''Map Data'' item in the ''Project Explorer''<br />
# Select '''New Coverage''' from the right-click menu<br />
# Set the coverage type to ''Generic &rarr; Observation'' in the ''New Coverage'' dialog<br />
# Set the coverage name as desired<br />
# Click '''OK''' to exit the dialog<br />
Alternatively, an existing coverage can be changed to an observation coverage by right-clicking on the coverage in the [[SMS:Project Explorer|Project Explorer]] and setting the type to ''Observation'' using the right-click menu.<br />
<br />
== Creating an Observation Point ==<br />
Observation points are created at locations in the model where calibration data such as the velocity or water surface elevation has been measured in the field. Each observation point is used to compare the measured values with the values computed by the model at the point's x, y location. This comparison can assist the modeler in determining the accuracy of the numerical model results. If the numerical model results do not match the observed field data, model parameters such as manning's roughness may need to be modified to obtain more accurate results.<br />
<br />
Creating an observation point is just like creating a feature point in any other coverage type. Select the [[SMS:Map Module Tools|Create Feature Point tool]] from the [[SMS:Dynamic_Tools|Dynamic Toolbar]] and click the location for the feature point.<br />
<br />
== Creating an Observation Arc ==<br />
Observation arcs are created at cross sections in the model where calibration data such as the flowrate has been measured in the field. Observation arcs compute fluxes across the arc. Therefore, measurements for observation arcs are called ''Flux Measurements''. Each obseration arc is used to compare the measured values with the values computed by the model across the vertical plane defined by the arc. This comparison can assist the modeler in determining the accuracy of the numerical model results. If the numerical model results do not match the observed field data, model parameters such as manning's roughness may need to be modified to obtain more accurate results.<br />
<br />
Creating an observation arc is just like creating a feature arc in any other coverage type. Select the [[SMS:Map Module Tools|'''Create Feature Arc''' tool]] from the [[SMS:Dynamic Tools|Dynamic Toolbar]] and click out an arc. Double-click to end the arc. In an observation coverage, profile arcs and cross section arcs may be useful to analyze a simulation's solution.<br />
<br />
== Setting Observation Object Attributes ==<br />
Observation point and arc attributes are defined in the [[SMS:Observation Coverage#Observation Coverage Dialog|Observation Coverage dialog]]. See [[SMS:Observation Coverage#Observation Coverage Dialog|Observation Coverage dialog]] for a description of the ''Observation Coverage'' dialog.<br />
<br />
<br />
[[Image:Observ_arcs1.JPG]]<br />
<br />
== Viewing Results ==<br />
In addition to viewing the results of the solution data versus the observed data on the calibration targets, additional plots can be created using the [[SMS:Plot Window|Plot Wizard]]. See [[SMS:Plot Window|Plot Window]] for a description of the available plot types.<br />
<br />
== Calibration ==<br />
<br />
Calibration is the process of modifying the input parameters to a model until the output from the model matches an observed set of data. SMS includes a suite of tools to assist in the process of calibrating a model. Both point and flux observations are supported. Most of the calibration tools can be used with any of the models in SMS.<br />
<br />
Measurement types can be defined in SMS. They are defined in the map module and are associated with points and arcs in an observation coverage. Point observations represent locations in the field where some value has been observed. In most cases, the points will correspond to gauges or high water marks and the value will be the elevation of the water (the head) or a flow velocity (and possibly direction). Flux observations represent linear or areal objects such as streams gages where the flow rate has been measured or estimated. Both point and flow observations can be assigned a confidence interval or calibration target.<br />
<br />
Once a set of observed point and flow values has been entered, each time a model solution is imported, SMS automatically interpolates the computed solution to the observation points. A calibration target representing the magnitude of the residual error is displayed next to each observation point and each flux object as shown below. The size of the target is based on the confidence interval or the standard deviation. In addition to the calibration targets next to the observation points, a user can choose to display any of a number of statistical plots.<br />
<br />
== Calibration Target ==<br />
<br />
If an observed value has been assigned to an observation point or if an observed flow has been assigned to an arc or polygon, the calibration error at each object can be plotted using a "calibration target". A set of calibration targets provides useful feedback on the magnitude, direction (high, low), and spatial distribution of the calibration error.<br />
<br />
The components of a calibration target are illustrated in the following figure. The center of the target corresponds to the observed value. The top of the target corresponds to the observed value plus the interval and the bottom corresponds to the observed value minus the interval. The colored bar represents the error. If the bar lies entirely within the target, the color bar is drawn in green. If the bar is outside the target, but the error is less than 200%, the bar is drawn in yellow. If the error is greater than 200%, the bar is drawn in red. The display options related to calibration targets are specified in the ''Calibration Display Options'' dialog.<br />
<br />
If the active time step is before the first observed time, or after the last observed time, the targets are drawn lighter.<br />
<br />
[[Image:Calibration_targets.JPG|thumb|none|left|350 px|Components of a calibration target. ]]<br />
<br />
== Calibration Display Options ==<br />
Calibration targets are drawn next to their corresponding map data (point, arc, polygon). The ''Feature Objects Display Options'' dialog contains a toggle labeled ''calibration targets''. Below the toggle is a ''Scale'' edit field.<br />
<br />
The target is drawn such that the height of the target is equal to twice the confidence interval (+ interval on top, - interval on bottom). The Scale edit field allows the user to change the general length and width of the targets independent of the range of the active dataset.<br />
<br />
==Observation Coverage Dialog==<br />
[[Image:SMS Observation.jpg|thumb|400 px|''Observation Coverage'' dialog]]<br />
The ''Observation Objects'' dialog has two sections used to define the attributes of the points and arcs created in the observation coverage. To open the ''Observation Coverage'' dialog:<br />
# Make the observation coverage active in the [[SMS:Project Explorer|Project Explorer]]<br />
# Select the [[SMS:Map Module Tools|'''Create Feature Point''']] or [[SMS:Map Module Tools|'''Create Feature Arc''']] tool from the [[SMS:Dynamic_Tools|Dynamic Toolbar]]<br />
# Select a feature point or feature arc<br />
# Select the menu command ''Feature Objects'' | '''Attributes''' or double-click in the previous step<br />
<br />
=== Dialog Layout ===<br />
The options in the dialog will differ slightly based on the feature object type currently being edited (arc or point). The feature object type is specified using the combo box in the upper right of the dialog.<br />
<br />
In addition to a unique Name and Dataset(s), two other parameters are used to define the data represented by a measurement: ''Trans'' and ''Module''. When analyzing data that varies through time, select the ''Trans'' toggle. The Module of a measurement refers to the SMS module where the computed data is stored. (The Module is set by default and normally does not need to be changed.)<br />
<br />
=== Observation Point Attributes ===<br />
When "points" is selected in the Feature object type combo box, the top section of the dialog is entitled ''Measurements'' and the bottom section is entitled ''Observation Points.'' The ''Measurements'' section is used to specify which datasets correspond with the observed data entered in the ''Observation Points'' section. The ''Measurements'' section is used to enter the observed data at each point. Each observation point is assigned the following attributes:<br />
* '''Color''' &ndash; Color of the observation point.<br />
* '''Observe''' &ndash; Turn the observation point on or off.<br />
* '''Name''' &ndash; Name of the observation point.<br />
* '''X''' &ndash; X-location of the point.<br />
* '''Y''' &ndash; Y-location of the point.<br />
* '''Observed Value''' &ndash; Value measured in the field corresponding to the active measurement.<br />
* '''Interval''' &ndash; Allowable error (±) between the computed value and the observed value. Model verification is achieved when the error is within the interval (±) of the observed value.<br />
* '''Angle''' &ndash; When a measurement for observation points is tied to a vector dataset (as is the case with a Velocity measurement) an angle needs to be specified. This angle is an azimuth angle (measured clockwise) with the top of the screen representing north when in plan view.<br />
<br />
=== Observation Arc Attributes ===<br />
If "arcs" is selected in the combo box, then the top spreadsheet had the name ''Flux Measurements'' and the bottom spreadsheet has the name of ''Observation Arcs.''<br />
<br />
To define an arc measurement, the Name must first be defined. In addition to a unique Name, a scalar and vector dataset must be assigned to it. Two other parameters are also used to define the data represented by a measurement: ''Trans'' and ''Module''. When analyzing data that varies through time, select the ''Trans'' toggle. The ''Module of a measurement'' refers to the SMS module where the computed data is stored. (The Module is set by default and normally does not need to be changed.)<br />
<br />
Each observation arc is assigned the following attributes:<br />
* '''Color''' &ndash; Color of the observation arc.<br />
* '''Observe''' &ndash; Turn the observation arc on or off.<br />
* '''Name''' &ndash; Name of the observation arc.<br />
* '''x-origin''' &ndash; X origin of the arc (used to modify the x-value used in plots).<br />
* '''Observed Value''' &ndash; Value measured in the field corresponding to the active measurement.<br />
* '''Interval''' &ndash; Allowable error (±) between the computed value and the observed value. Model verification is achieved when the error is within the interval (±) of the observed value.<br />
<br />
==Related Topics==<br />
* [[SMS:Coverages|Coverages]]<br />
* [[SMS:Plot Window|Plot Window]]<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
<br />
[[Category:SMS Map|Observation Coverage]]<br />
[[Category:SMS Coverages|O]]<br />
[[Category:SMS Dialogs|O]]</div>Woodhttps://www.xmswiki.com/index.php?title=SMS:GenCade&diff=51234SMS:GenCade2013-06-10T16:32:17Z<p>Wood: /* Functionality */</p>
<hr />
<div>The GenCade model is a next generation combination of previous long-term planform evolution of a beach models GENESIS (GENEralized Model for SImulating Shoreline Change[http://chl.erdc.usace.army.mil/chl.aspx?p=s&amp;a=software;34]) and Cascade[http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-xiv-2-pdf].) and Cascade.<br />
<br />
GenCade is a regional model for calculating coastal sediment transport, morphology change, and sand bypassing at inlets and engineered structures. GenCade is developed by the U.S. Army Engineer Research and Development Center (USACE-ERDC), Coastal and Hydraulics Laboratory (CHL). The developers maintain [http://cirp.usace.army.mil/wiki/GenCade documentation] for the model, comments on the [http://cirp.usace.army.mil/wiki/GenCade_Users_Guide interface] and steps for a [http://cirp.usace.army.mil/wiki/GenCade_Example sample application].<br />
<br />
==Functionality==<br />
GenCade simulates shoreline change relative to regional morphologic constraints upon which these processes take place. The evolution of multiple interacting coastal projects and morphologic features and pathways, such as those associated with inlets and adjacent beaches may also be simulated. The model supports responses to imposed wave conditions, coastal structures, and other engineering activity (e.g., beach nourishment).<br />
<br />
Typical longshore extents and time periods of modeled projects can be in the ranges of one to 100 km and one month to multiple decades, respectively, and almost arbitrary numbers and combinations of groins, detached breakwaters, seawalls, jetties, and beach fills can be represented. GenCade simulates shoreline change produced by spatial and temporal differences in longshore sand transport. Shoreline movement such as that produced by beach fills and river sediment discharges can also be represented. The main utility of the modeling system lies in simulating the response of the shoreline to structures sited in the nearshore. Shoreline change produced by cross-shore sediment transport as associated with storms and seasonal variations in wave climate cannot be simulated; support of cross-shore processes are being considered for future versions of the model. <br />
<br />
Capabilities of GenCade: <br />
* Almost arbitrary numbers and combinations for groins, jetties, detached breakwaters, beach fills, and seawalls <br />
* Compound structures such as T-shaped, Y-shaped, and spur groins <br />
* Bypassing of sand around and transmission through groins and jetties <br />
* Diffraction at detached breakwaters, jetties, and groins <br />
* Coverage of wide spatial extent <br />
* Offshore input waves of arbitrary height, period, and direction <br />
* Multiple wave trains (as from independent wave generation sources) <br />
* Sand transport due to oblique wave incidence and longshore gradient in height <br />
* Wave transmission at detached breakwaters<br />
<br />
==Related Topics==<br />
* [[SMS:1D Grid Module|1D Grid Module]] <br />
* [[SMS:Practical Notes For Using GenCade|Practical notes for using GenCade]]<br />
* [[SMS:GenCade Modeling Process|GenCade modeling process]]<br />
* [[SMS:GenCade Graphical Interface|GenCade graphical interface]]<br />
<br />
==Case Studies / Sample Problems== <br />
* Tutorials for learning to use GenCade in SMS are under development. <br />
<br />
==External Links== <br />
* US Army Corps of Engineers Coastal & Hydraulics Laboratory GENESIS website [http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=SOFTWARE;34&g=141] <br />
* GENESIS, Report 1, Technical Reference [http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=PUBLICATIONS;110&g=90] <br />
* GENESIS, Report 2, Workbook and System User's Manual [http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=PUBLICATIONS;111&g=90] <br />
* User's Guide to the Shoreline Modeling System [http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=PUBLICATIONS;112&g=90] <br />
* A History of GENESIS Updates [http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=ARTICLES;457&g=90] <br />
* Mar 2002 ERDC/CHL CHETN-II-45 Wave Transmission at Detached Breakwaters for Shoreline Response Modeling [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-ii-45.pdf] <br />
* Mar 1990 CETN-II-21 Computer Program: Genesis Version 2 [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/cetn-ii-21.pdf] <br />
* Cascade User Guide: [https://swwrp.usace.army.mil/_swwrp/swwrp/4-Pubs/TechNotes/swwrp-tn-06-5.pdf] <br />
* Cascade Theory and Model Formulation: [https://swwrp.usace.army.mil/_swwrp/swwrp/4-Pubs/TechNotes/swwrp-tn-06-7.pdf] <br />
* Inlet Reservoir Model (sub-model within Cascade) [http://cirp.wes.army.mil/cirp/cetns/chetn-iv39.pdf]<br />
<br />
{{Template:Navbox SMS}}</div>Woodhttps://www.xmswiki.com/index.php?title=SMS:ADCIRC&diff=49706SMS:ADCIRC2013-05-14T15:56:15Z<p>Wood: fixed link to Shinnecock Inlet pdf</p>
<hr />
<div>{{SMS Infobox Model |<br />
|name= ADCIRC<br />
|model_type= Finite element hydrodynamic model for coastal oceans, inlets, rivers and floodplains.<br />
|developer= <br />
Rick Luettich <br><br />
Joannes Westerink <br><br />
Randall Kolar <br><br />
Cline Dawson<br />
|web_site= http://www.adcirc.org<br />
|tutorials= <br />
General Section <br><br />
* Data Visualization<br />
* Mesh Editing<br />
* Observation<br />
Models Section <br><br />
* ADCIRC<br />
Several Sample problems can be found on the ADCIRC model developer's [http://adcirc.org/home/documentation/example-problems/ webpage]<br />
}}<br />
<br />
The ADCIRC (Advanced Circulation) model is a finite element hydrodynamic model for coastal oceans, inlets, rivers and floodplains. The initial developers of the code were Rick Luettich (University of North Carolina at Chapel Hill) and Joannes Westerink (University of Notre Dame). Other principal developers include Randall Kolar (University of Oklahoma at Norman) and Cline Dawson (University of Texas at Austin). Various other groups are involved in development and support around the country. <br />
<br />
The ADCIRC model is only valid for models in North America.<br />
<br />
== Graphical Interface == <br />
SMS provides a graphical interface that is designed to allow users to visualize the projects they are creating, easily modify project parameters, and view the solutions produced by the ADCIRC model. See [[SMS:ADCIRC Graphical Interface|ADCIRC Graphical Interface]] for more information.<br />
<br />
The [[SMS:ADCIRC Graphical Interface|ADCIRC Graphical Interface]] contains tools to create and edit an ADCIRC 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 ADCIRC. If a mesh has already been created for a ADCIRC 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 ADCIRC. 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:ADCIRC Menu|''ADCIRC'' Menu]]. See [[SMS:ADCIRC Graphical Interface|ADCIRC Graphical Interface]] for more information.<br />
<br />
== Functionality ==<br />
ADCIRC is a system of computer programs for solving time dependent, free surface circulation and transport problems in two and three dimensions. These programs utilize the finite element method in space allowing the use of highly flexible, unstructured grids. Typical ADCIRC applications have included: (i) modeling tides and wind driven circulation, (ii) analysis of hurricane storm surge and flooding, (iii) dredging feasibility and material disposal studies, (iv) larval transport studies, (v) near shore marine operations.<br />
<br />
For more information about the ADCIRC model visit [http://www.adcirc.org www.adcirc.org].<br />
<br />
== Using the Model / Practical Notes ==<br />
* There is an ADCIRC listserv that may be useful to keep up-to-date about the latest releases of ADCIRC and to post any questions about ADCIRC. It is [mailto:adcirc@listserv.unc.edu adcirc@listserv.unc.edu]. If you would like to join please email [mailto:cfulcher@email.unc.edu Crystal Fulcher].<br />
<br />
== Related Topics ==<br />
* [[SMS:SMS Models|SMS Models]]<br />
* [[SMS:LTEA|LTEA &ndash; Linear Truncation Error Analysis]]<br />
* [[SMS:ADCIRC_Database|ADCIRC Database]]<br />
<br />
== External Links ==<br />
* [http://adcirc.org/ ADCIRC Home page]<br />
* Mar 2002 ERDC/CHL CHETN-IV-40 Guidelines for Using Eastcoast 2001 Database of Tidal Constituents within Western North Atlantic Ocean, Gulf of Mexico and Caribbean Sea [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-40.pdf]<br />
* Jun 2001 ERDC/CHL CHETN-IV-32 Leaky Internal-Barrier Normal-Flow Boundaries in the ADCIRC Coastal Hydrodynamics Code [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-32.pdf]<br />
* Mar 2001 Technical Report CHL-98-32 Shinnecock Inlet, New York, site Investigation Report 4, Evaluation of Flood and Ebb shoal Sediment Source Alternatives for the West of Shinnecock Interim Project, New York [http://dl.dropboxusercontent.com/u/74679281/publications/2001/2001_Militello03.pdf]<br />
* Dec 1999 Coastal Engineering Technical Note IV-21 Surface-Water Modeling System Tidal Constituents Toolbox for ADCIRC [http://www.adcirc.org/publications/1999/1999_Militello.pdf] [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/cetn-iv-21.pdf]<br />
* [http://www.seahorsecoastal.com/wiki/doku.php ADCIRC wiki hosted by Seahorse Coastal Consulting]<br />
* [http://water.engr.psu.edu/hill/research/glba/default.stm Glacier Bay Test Case by Dave F. Hill]<br />
* [http://aos.princeton.edu/WWWPUBLIC/PROFS/adcirc_report.pdf Assessment of ADCIRC's Wetting and Drying Algorithm]<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
<br />
[[Category:SMS 2D Mesh|ADCIRC]]<br />
[[Category:ADCIRC|ADCIRC]]</div>Woodhttps://www.xmswiki.com/index.php?title=SMS:ADCIRC&diff=49705SMS:ADCIRC2013-05-14T15:53:31Z<p>Wood: fixed sample problem link</p>
<hr />
<div>{{SMS Infobox Model |<br />
|name= ADCIRC<br />
|model_type= Finite element hydrodynamic model for coastal oceans, inlets, rivers and floodplains.<br />
|developer= <br />
Rick Luettich <br><br />
Joannes Westerink <br><br />
Randall Kolar <br><br />
Cline Dawson<br />
|web_site= http://www.adcirc.org<br />
|tutorials= <br />
General Section <br><br />
* Data Visualization<br />
* Mesh Editing<br />
* Observation<br />
Models Section <br><br />
* ADCIRC<br />
Several Sample problems can be found on the ADCIRC model developer's [http://adcirc.org/home/documentation/example-problems/ webpage]<br />
}}<br />
<br />
The ADCIRC (Advanced Circulation) model is a finite element hydrodynamic model for coastal oceans, inlets, rivers and floodplains. The initial developers of the code were Rick Luettich (University of North Carolina at Chapel Hill) and Joannes Westerink (University of Notre Dame). Other principal developers include Randall Kolar (University of Oklahoma at Norman) and Cline Dawson (University of Texas at Austin). Various other groups are involved in development and support around the country. <br />
<br />
The ADCIRC model is only valid for models in North America.<br />
<br />
== Graphical Interface == <br />
SMS provides a graphical interface that is designed to allow users to visualize the projects they are creating, easily modify project parameters, and view the solutions produced by the ADCIRC model. See [[SMS:ADCIRC Graphical Interface|ADCIRC Graphical Interface]] for more information.<br />
<br />
The [[SMS:ADCIRC Graphical Interface|ADCIRC Graphical Interface]] contains tools to create and edit an ADCIRC 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 ADCIRC. If a mesh has already been created for a ADCIRC 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 ADCIRC. 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:ADCIRC Menu|''ADCIRC'' Menu]]. See [[SMS:ADCIRC Graphical Interface|ADCIRC Graphical Interface]] for more information.<br />
<br />
== Functionality ==<br />
ADCIRC is a system of computer programs for solving time dependent, free surface circulation and transport problems in two and three dimensions. These programs utilize the finite element method in space allowing the use of highly flexible, unstructured grids. Typical ADCIRC applications have included: (i) modeling tides and wind driven circulation, (ii) analysis of hurricane storm surge and flooding, (iii) dredging feasibility and material disposal studies, (iv) larval transport studies, (v) near shore marine operations.<br />
<br />
For more information about the ADCIRC model visit [http://www.adcirc.org www.adcirc.org].<br />
<br />
== Using the Model / Practical Notes ==<br />
* There is an ADCIRC listserv that may be useful to keep up-to-date about the latest releases of ADCIRC and to post any questions about ADCIRC. It is [mailto:adcirc@listserv.unc.edu adcirc@listserv.unc.edu]. If you would like to join please email [mailto:cfulcher@email.unc.edu Crystal Fulcher].<br />
<br />
== Related Topics ==<br />
* [[SMS:SMS Models|SMS Models]]<br />
* [[SMS:LTEA|LTEA &ndash; Linear Truncation Error Analysis]]<br />
* [[SMS:ADCIRC_Database|ADCIRC Database]]<br />
<br />
== External Links ==<br />
* [http://adcirc.org/ ADCIRC Home page]<br />
* Mar 2002 ERDC/CHL CHETN-IV-40 Guidelines for Using Eastcoast 2001 Database of Tidal Constituents within Western North Atlantic Ocean, Gulf of Mexico and Caribbean Sea [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-40.pdf]<br />
* Jun 2001 ERDC/CHL CHETN-IV-32 Leaky Internal-Barrier Normal-Flow Boundaries in the ADCIRC Coastal Hydrodynamics Code [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-32.pdf]<br />
* Mar 2001 Technical Report CHL-98-32 Shinnecock Inlet, New York, site Investigation Report 4, Evaluation of Flood and Ebb shoal Sediment Source Alternatives for the West of Shinnecock Interim Project, New York [http://www.adcirc.org/publications/2001/2001_Militello03.pdf]<br />
* Dec 1999 Coastal Engineering Technical Note IV-21 Surface-Water Modeling System Tidal Constituents Toolbox for ADCIRC [http://www.adcirc.org/publications/1999/1999_Militello.pdf] [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/cetn-iv-21.pdf]<br />
* [http://www.seahorsecoastal.com/wiki/doku.php ADCIRC wiki hosted by Seahorse Coastal Consulting]<br />
* [http://water.engr.psu.edu/hill/research/glba/default.stm Glacier Bay Test Case by Dave F. Hill]<br />
* [http://aos.princeton.edu/WWWPUBLIC/PROFS/adcirc_report.pdf Assessment of ADCIRC's Wetting and Drying Algorithm]<br />
<br />
<br />
{{Template:Navbox SMS}}<br />
<br />
[[Category:SMS 2D Mesh|ADCIRC]]<br />
[[Category:ADCIRC|ADCIRC]]</div>Woodhttps://www.xmswiki.com/index.php?title=Raster_Options&diff=36981Raster Options2012-04-23T20:59:15Z<p>Wood: </p>
<hr />
<div>== Importing Rasters ==<br />
Import a raster file by selecting Open in the File menu. Select the proper raster file as shown in the following table. Select Open. At the popup "Load it as...", select DEM.<br />
{| class="wikitable"<br />
!Format!!File to Open!!Source!!Importance!!Level of Support<br />
|-<br />
| ArcInfo Binary Grid||w001001.adf||ESRI||1||Supported in gms and in sms</td><br />
|-<br />
|ArcInfo Ascii Grid||asc||ESRI||2||Supported in gms and in sms<br />
|-<br />
|USGS DEM Grid Float||flt||http://seamless.usgs.gov||2||Supported in gms and in sms<br />
|-<br />
|USGS NED Grid Float||*.flt||http://seamless.usgs.gov||2||Supported in gms and in sms<br />
|-<br />
|Canadian DEM||*.dem||http://www.geobase.ca||3||Supported in gms and supported in sms<br />
|-<br />
|DTED||*.dt0||ERDC||3||Supported in gms and supported in sms<br />
|-<br />
|Aster DEM||*.tif||http://asterweb.jpl.nasa.gov/gdem-wist.asp||4||Supported in gms and supported in sms as images<br />
|-<br />
|SDTS||*.ddf||http://data.geocomm.com/dem/demdownload.html||5||Supported in gms and supported in sms<br />
|-<br />
|}<br />
'''<br />
<br />
'''How to export TINs in adf format from ArcGIS in a format that XMS will read'''<br />
#Load the TIN into ArcMap<br />
#Expand the “3D Analyst Tools | Conversion Tools | From TIN” toolset in ArcToolbox<br />
#Double click the “TIN to Raster” tool in ArcToolbox (specify your current TIN file in the "Input TIN” field). Make a note of the path in the "Output Raster" field.<br />
#Expand the “Conversion Tools | From Raster” toolset in ArcToolbox<br />
#Double click the “Raster to ASCII” tool in ArcToolbox (specify the raster file that you created in the previous step as the input raster, and make a note of the path for the output file)<br />
#Open Windows Explorer (My Computer) and browse to the location of the ASCII .txt file output in step 5<br />
#Make a copy of the *.txt file created in step 5<br />
#Change the extension of the *.txt file to *.dem<br />
#Open the “.dem” file in WMS<br />
<br />
== Displaying Rasters ==<br />
<br />
The raster display options are accessed by clicking on the Raster Options item or tab in the Display Options dialog. The default options vary between applications, and the options may be changed, saved, and restored within the project.<br />
<br />
[[Image:RasterDialog.png|400px|Raster dialog.]]<br />
<br />
The following table describes the raster display options.<br />
{| class="wikitable"<br />
! width="125" | Display Option !! Description<br />
|-<br />
| Image Display || Select the "Display as raster" radio button to display the raster as a flat image rather than as a surface with elevation changes. Contour options are applied to form the image with block color fill.<br />
|-<br />
| Image Elevation || The raster image is drawn at an elevation of 0.0 by default. Change the "Elevation:" value to draw it at a different elevation.<br />
|-<br />
| Surface Display || Select the "Display as surface" radio button to display the raster as a height varying surface rather than as a flat image. Enable either Contours, Edges, or Boundary to see that type of surface or nothing will be shown.<br />
|-<br />
| Surface Contour || Select the "Contours" check box to apply contour options to the surface with contour lines and/or smooth color fill.<br />
|-<br />
| Surface Edges || Select the "Edges" check box to display the polygonal edges between height samples in the surface. The control to the left sets line color and either enables line dashes or species line width for the edges. This is typically the slowest surface to render.<br />
|-<br />
| Surface Boundary || Select the "Boundary" check box to display only those polygonal edges between height samples on the perimeter of the surface. The control to the left sets line color and either enables line dashes or species line width for the boundary. This is typically the fastest surface to render.<br />
|-<br />
|}</div>Woodhttps://www.xmswiki.com/index.php?title=Raster_Options&diff=36927Raster Options2012-04-02T17:34:51Z<p>Wood: </p>
<hr />
<div>== Importing Rasters ==<br />
Import a raster file by selecting Open in the File menu. Select the proper raster file as shown in the following table. Select Open. At the popup "Load it as...", select DEM.<br />
{| class="wikitable"<br />
!Format!!File to Open!!Source!!Importance!!Level of Support<br />
|-<br />
| ArcInfo Binary Grid||w001001.adf||ESRI||1||Supported in gms and in sms</td><br />
|-<br />
|ArcInfo Ascii Grid||asc||ESRI||2||Supported in gms and in sms<br />
|-<br />
|USGS DEM Grid Float||flt||http://seamless.usgs.gov||2||Supported in gms and in sms<br />
|-<br />
|USGS NED Grid Float||*.flt||http://seamless.usgs.gov||2||Supported in gms and in sms<br />
|-<br />
|Canadian DEM||*.dem||http://www.geobase.ca||3||Supported in gms and supported in sms<br />
|-<br />
|DTED||*.dt0||ERDC||3||Supported in gms and supported in sms<br />
|-<br />
|Aster DEM||*.tif||http://asterweb.jpl.nasa.gov/gdem-wist.asp||4||Supported in gms and supported in sms as images<br />
|-<br />
|SDTS||*.ddf||http://data.geocomm.com/dem/demdownload.html||5||Supported in gms and supported in sms<br />
|-<br />
|}<br />
'''<br />
<br />
'''How to export TINs in adf format from ArcGIS in a format that WMS will read'''<br />
#Load the TIN into ArcMap<br />
#Expand the “3D Analyst Tools | Conversion Tools | From TIN” toolset in ArcToolbox<br />
#Double click the “TIN to Raster” tool in ArcToolbox (specify your current TIN file in the "Input TIN” field). Make a note of the path in the "Output Raster" field.<br />
#Expand the “Conversion Tools | From Raster” toolset in ArcToolbox<br />
#Double click the “Raster to ASCII” tool in ArcToolbox (specify the raster file that you created in the previous step as the input raster, and make a note of the path for the output file)<br />
#Open Windows Explorer (My Computer) and browse to the location of the ASCII .txt file output in step 5<br />
#Make a copy of the *.txt file created in step 5<br />
#Change the extension of the *.txt file to *.dem<br />
#Open the “.dem” file in WMS<br />
<br />
== Displaying Rasters ==<br />
<br />
The raster display options are accessed by clicking on the Raster Options item or tab in the Display Options dialog. The default options vary between applications, and the options may be changed, saved, and restored within the project.<br />
<br />
[[Image:RasterDialog.png|400px|Raster dialog.]]<br />
<br />
The following table describes the raster display options.<br />
{| class="wikitable"<br />
! width="125" | Display Option !! Description<br />
|-<br />
| Image Display || Select the "Display as raster" radio button to display the raster as a flat image rather than as a surface with elevation changes. Contour options are applied to form the image with block color fill.<br />
|-<br />
| Image Elevation || The raster image is drawn at an elevation of 0.0 by default. Change the "Elevation:" value to draw it at a different elevation.<br />
|-<br />
| Surface Display || Select the "Display as surface" radio button to display the raster as a height varying surface rather than as a flat image. Enable either Contours, Edges, or Boundary to see that type of surface or nothing will be shown.<br />
|-<br />
| Surface Contour || Select the "Contours" check box to apply contour options to the surface with contour lines and/or smooth color fill.<br />
|-<br />
| Surface Edges || Select the "Edges" check box to display the polygonal edges between height samples in the surface. The control to the left sets line color and either enables line dashes or species line width for the edges. This is typically the slowest surface to render.<br />
|-<br />
| Surface Boundary || Select the "Boundary" check box to display only those polygonal edges between height samples on the perimeter of the surface. The control to the left sets line color and either enables line dashes or species line width for the boundary. This is typically the fastest surface to render.<br />
|-<br />
|}</div>Woodhttps://www.xmswiki.com/index.php?title=Import_from_Web&diff=35897Import from Web2011-10-13T18:12:12Z<p>Wood: </p>
<hr />
<div>The ''Import from Web'' feature allows you to connect to the internet to download free data - images, elevation data etc. If you have an internet connection, this is an easy and convenient way to acquire this type of data.<br />
The data is made available for free by various entities who provide [http://en.wikipedia.org/wiki/Web_service web services]. Each XMS programs has a number of available data types they can retrieve.<br />
<br />
{| class="wikitable"<br />
|- align="center"<br />
| '''[[GMS:GMS|GMS]] '''<br />
| '''[[SMS:SMS|SMS]] '''<br />
| '''[[WMS:WMS|WMS]] '''<br />
|-<br />
|<br />
* [http://ned.usgs.gov/ NED data - USGS]<br />
* [http://srtm.usgs.gov/ SRTM data - USGS & NASA]<br />
* [http://www.terraserver.com/ TerraServer aerial photo]<br />
* [http://www.terraserver.com/ TerraServer urban]<br />
* [http://www.terraserver.com/ TerraServer topo]<br />
|<br />
* [http://www.terraserver.com/ TerraServer aerial photo]<br />
* [http://www.terraserver.com/ TerraServer urban]<br />
* [http://www.terraserver.com/ TerraServer topo]<br />
|<br />
* [http://ned.usgs.gov/ NED data - USGS]<br />
* [http://srtm.usgs.gov/ SRTM data - USGS & NASA]<br />
* [http://seamless.usgs.gov/nlcd.php Land use data]<br />
* [http://www.terraserver.com/ TerraServer aerial photo]<br />
* [http://www.terraserver.com/ TerraServer urban]<br />
* [http://www.terraserver.com/ TerraServer topo]<br />
* [http://crunch.tec.army.mil/nidpublic/webpages/nid.cfm NID data]<br />
* [http://waterdata.usgs.gov/nwis USGS stream data]<br />
* [http://mesowest.utah.edu/cgi-bin/droman/mesomap.cgi MesoWest data]<br />
|}<br />
<br />
This feature is found via the ''File|Import from Web'' command. This command results in the following series of dialogs.<br />
<br />
<!-- I specify an 80% scaling on all the dialog images. I think the dialogs look way to big otherwise. Unfortunately there's no easy way to do that in MediaWiki so I have to just calculate what 80% of the width is in pixels. --><br />
#'''Warning'''<br />
#:If your current coordinate system is 'Local', you will get the following warning dialog. The data that will be downloaded is georeferenced so your project coordinate system must be something other than 'Local'. Selecting ''OK'' will change the current coordinate system.<br />
#:[[Image:ImportFromWeb-CurrentCoordSystemWarning.png|center|400px|''Warning about Local Coordinate Systems'']]<br />
#'''Virtual Earth Map Locator'''<br />
#:Use the map in this dialog to go to your location of interest.<br />
#*You can '''zoom''' in or out using the controls or the mouse wheel.<br />
#*You can '''pan''' using the controls or by clicking and dragging. You can also enter the latitude and longitude to jump to a specific location.<br />
#*Use the ''Map Options'' menu to turn on the floating controls in the map (search, pan and zoom).<br />
#*Use the ''Map Style'' menu, or the floating controls, to change the map between '''Road''', '''Aerial''', and '''Hybrid'''.<br />
#:[[Image:ImportFromWeb-VirtualEarthMapLocator.png|none|718px|Virtual Earth Map Locator]]<br />
#'''Data Service Options'''<br />
#:Here you select which type of data you are interested in.<br />
#:[[Image:ImportFromWeb-WebServiceOptions.png|none|242px|Data Service Options dialog]]<br />
#'''Save'''<br />
#:Now you are asked where you want to save the data. You only need to specify one file name, even if you've selected more than one type of data in the previous dialog. The files will all be given the same prefix but different suffixes.<br />
#:[[Image:ImportFromWeb-Save.png|none|450px|Save dialog]]<br />
#'''Confirm File Creation'''<br />
#:You may be asked to confirm that you want to create the files.<br />
#:[[Image:ImportFromWeb-CreateFiles.png|none|208px|Confirmation of file creation dialog]]<br />
#'''Initialize Connection'''<br />
#:The following dialog is shown while the connection is being made.<br />
#:[[Image:ImportFromWeb-Initializing.png|none|166px|Dialog shown during initial connection]]<br />
#'''Select Scale'''<br />
#:Smaller numbers (larger scales) will result in better resolution, but longer download times.<br />
#:[[Image:ImportFromWeb-SelectScale.png|none|220px|Select Scale dialog]]<br />
#'''Downloading'''<br />
#:This dialog reports the download progress. If you click '''Abort''', your image will exist but will be only that portion that you've downloaded so far.<br />
#:[[Image:ImportFromWeb-TilesRemaining.png|none|166px|Dialog showing download progress]]<br />
<br />
Steps 6-8 will repeat for each data type you selected in step 4.<br />
After everything is finished, the data (images etc.) will appear in the [[GMS:Project Explorer|Project Explorer]].<br />
<br />
==See also==<br />
* [[Image Pyramids]]<br />
* [[Registering an Image]]<br />
* [[SMS:Web_Menu|SMS Web Menu]]<br />
<br />
<br />
<br />
<br />
[[Category:Importing Data]]</div>Woodhttps://www.xmswiki.com/index.php?title=Import_from_Web&diff=35896Import from Web2011-10-13T18:10:12Z<p>Wood: </p>
<hr />
<div>The ''Import from Web'' feature allows you to connect to the internet to download free data - images, elevation data etc. If you have an internet connection, this is an easy and convenient way to acquire this type of data.<br />
The data is made available for free by various entities who provide [http://en.wikipedia.org/wiki/Web_service web services]. Each XMS programs has a number of available data types they can retrieve.<br />
<br />
{| class="wikitable"<br />
|- align="center"<br />
| '''[[GMS:GMS|GMS]] '''<br />
| '''[[SMS:SMS|SMS]] '''<br />
| '''[[WMS:WMS|WMS]] '''<br />
|-<br />
|<br />
* [http://ned.usgs.gov/ NED data - USGS]<br />
* [http://srtm.usgs.gov/ SRTM data - USGS & NASA]<br />
* [http://www.terraserver.com/ TerraServer aerial photo]<br />
* [http://www.terraserver.com/ TerraServer urban]<br />
* [http://www.terraserver.com/ TerraServer topo]<br />
|<br />
* [http://www.terraserver.com/ TerraServer aerial photo]<br />
* [http://www.terraserver.com/ TerraServer urban]<br />
* [http://www.terraserver.com/ TerraServer topo]<br />
|<br />
* [http://ned.usgs.gov/ NED data - USGS]<br />
* [http://srtm.usgs.gov/ SRTM data - USGS & NASA]<br />
* [http://seamless.usgs.gov/nlcd.php Land use data]<br />
* [http://www.terraserver.com/ TerraServer aerial photo]<br />
* [http://www.terraserver.com/ TerraServer urban]<br />
* [http://www.terraserver.com/ TerraServer topo]<br />
* [http://crunch.tec.army.mil/nidpublic/webpages/nid.cfm NID data]<br />
* [http://waterdata.usgs.gov/nwis USGS stream data]<br />
* [http://www.met.utah.edu/mesowest/ MesoWest data]<br />
|}<br />
<br />
This feature is found via the ''File|Import from Web'' command. This command results in the following series of dialogs.<br />
<br />
<!-- I specify an 80% scaling on all the dialog images. I think the dialogs look way to big otherwise. Unfortunately there's no easy way to do that in MediaWiki so I have to just calculate what 80% of the width is in pixels. --><br />
#'''Warning'''<br />
#:If your current coordinate system is 'Local', you will get the following warning dialog. The data that will be downloaded is georeferenced so your project coordinate system must be something other than 'Local'. Selecting ''OK'' will change the current coordinate system.<br />
#:[[Image:ImportFromWeb-CurrentCoordSystemWarning.png|center|400px|''Warning about Local Coordinate Systems'']]<br />
#'''Virtual Earth Map Locator'''<br />
#:Use the map in this dialog to go to your location of interest.<br />
#*You can '''zoom''' in or out using the controls or the mouse wheel.<br />
#*You can '''pan''' using the controls or by clicking and dragging. You can also enter the latitude and longitude to jump to a specific location.<br />
#*Use the ''Map Options'' menu to turn on the floating controls in the map (search, pan and zoom).<br />
#*Use the ''Map Style'' menu, or the floating controls, to change the map between '''Road''', '''Aerial''', and '''Hybrid'''.<br />
#:[[Image:ImportFromWeb-VirtualEarthMapLocator.png|none|718px|Virtual Earth Map Locator]]<br />
#'''Data Service Options'''<br />
#:Here you select which type of data you are interested in.<br />
#:[[Image:ImportFromWeb-WebServiceOptions.png|none|242px|Data Service Options dialog]]<br />
#'''Save'''<br />
#:Now you are asked where you want to save the data. You only need to specify one file name, even if you've selected more than one type of data in the previous dialog. The files will all be given the same prefix but different suffixes.<br />
#:[[Image:ImportFromWeb-Save.png|none|450px|Save dialog]]<br />
#'''Confirm File Creation'''<br />
#:You may be asked to confirm that you want to create the files.<br />
#:[[Image:ImportFromWeb-CreateFiles.png|none|208px|Confirmation of file creation dialog]]<br />
#'''Initialize Connection'''<br />
#:The following dialog is shown while the connection is being made.<br />
#:[[Image:ImportFromWeb-Initializing.png|none|166px|Dialog shown during initial connection]]<br />
#'''Select Scale'''<br />
#:Smaller numbers (larger scales) will result in better resolution, but longer download times.<br />
#:[[Image:ImportFromWeb-SelectScale.png|none|220px|Select Scale dialog]]<br />
#'''Downloading'''<br />
#:This dialog reports the download progress. If you click '''Abort''', your image will exist but will be only that portion that you've downloaded so far.<br />
#:[[Image:ImportFromWeb-TilesRemaining.png|none|166px|Dialog showing download progress]]<br />
<br />
Steps 6-8 will repeat for each data type you selected in step 4.<br />
After everything is finished, the data (images etc.) will appear in the [[GMS:Project Explorer|Project Explorer]].<br />
<br />
==See also==<br />
* [[Image Pyramids]]<br />
* [[Registering an Image]]<br />
* [[SMS:Web_Menu|SMS Web Menu]]<br />
<br />
<br />
<br />
<br />
[[Category:Importing Data]]</div>Woodhttps://www.xmswiki.com/index.php?title=SMS:CGWAVE_BC_Nodestrings&diff=35533SMS:CGWAVE BC Nodestrings2011-08-24T15:15:56Z<p>Wood: /* Boundary Types */</p>
<hr />
<div>In the [[SMS:CGWAVE|CGWAVE]] model, a wave direction, amplitude and frequency must be specified at open boundaries and reflection coefficients are defined for all closed boundaries. In addition to these exterior boundaries, the model also includes the capability to simulate interior islands, and floating barriers. <br />
<br />
== Assign Boundary Condition ==<br />
The [[SMS:CGWAVE|CGWAVE]] Boundary Conditions dialog is used to assign boundary conditions to individual nodestrings. This dialog is invoked with the Assign BC Command in the [[SMS:CGWAVE_Menu|CGWAVE menu]]. Before assigning boundary conditions to nodestrings, at least one nodestring must be selected using the [[Image:SelectMeshNodestring.JPG]] [[SMS:2D_Mesh_Module_Tools|Select Nodestring tool]]. To assign boundary conditions to the selected nodestring(s), select one of the boundary condition options.<br />
<br />
=== Boundary Types ===<br />
* '''Open Ocean''' - Delineate the region where waves will enter the domain. The attributes of the waves that enter the domain are defined as incident wave characteristics in the [[SMS:CGWAVE_Model_Control|CGWAVE Model Control dialog]]. These values are propagated from an offshore location to the open ocean boundaries.<br />
* '''Coastline''' - Represent a region where the wave is obstructed. At these locations, the Reflection coefficient should be set. The coastline reflection term defines to what degree a section of coastline reflects incoming waves. Legal values vary from 0.0 for a gradual sandy incline to 1.0 for solid vertical rock wall. This boundary condition may be assigned to either exterior regions of the domain, or interior holes which represent islands.<br />
<br />
==Related Topics==<br />
* [[SMS:CGWAVE Graphical Interface|CGWAVE Graphical Interface]]<br />
<br />
{{Template:SMSMain}}<br />
<br />
[[Category:CGWAVE|B]]</div>Woodhttps://www.xmswiki.com/index.php?title=SMS:CMS-Flow&diff=35526SMS:CMS-Flow2011-08-03T19:31:02Z<p>Wood: </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://cirp.usace.army.mil/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.<br />
<br />
The model developers at the United States Army Corps of Engineers maintain a wiki specifically for the numerical engine. It can be viewed here [http://cirp.usace.army.mil/wiki/CMS-Flow]. For more information on the model itself, refer to the [http://cirp.usace.army.mil/Downloads/PDF/TR-06-9.pdf users manual] published by USACE-ERDC.<br />
<br />
CMS-Flow 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. <br />
<br />
The interface in SMS allows the user to set up and edit computational grids, specify model parameters, define interaction of this model with the wave counterpart ([[SMS:CMS-Wave|CMS-Wave]]), launch the model and visualize the results.<br />
<br />
The model is intended to be run on a project-scale, meaning the domain should only be on the order of 1-100 kilometers in length and width. The following sections describe the interface and make recommendations for application of the model. <br />
<br />
== Functionality ==<br />
<br />
== Graphical Interface ==<br />
The [[SMS:CMS-Flow Graphical Interface|CMS-Flow Graphical Interface]] is contained in the [[SMS:Cartesian Grid Module|Cartesian Grid Module]] as well as the [[SMS:Map Module|Map Module]] and includes tools to create and edit a CMS-Flow 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-Flow. If a grid has already been created for a CMS-Flow 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-Flow. See [[SMS:Cartesian Grid Module#Creating 2D Grids|Creating 2D Cartesian Grids]] for more information.<br />
<br />
<br />
== Using the Model / Practical Notes ==<br />
<br />
For new simulations, users will create the CMS-Flow grid based on a conceptual model. The conceptual model includes:<br />
<br />
*Grid Generation: We recommend that you generate a CMS-Flow grid using the conceptual model and a CMS-Flow Coverage. This coverage has attributes associated with a two-dimensional Cartesian grid and the model parameters associated with CMS-Flow. The grid position and extents are defined in the coverage using a grid frame, which you can define 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 coverage also defines the location of land and water in the grid using one of three methods:<br />
** Land/Water cells defined based bathymetric values. 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. This option allows the user to define, read or import 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. The user can 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. This option also requires the user to define arcs delineating 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 />
* Model Output: 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 Data Sets|spatial data sets]]. Additional observation cells can be created to view output at a higher temporal resolution.<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 />
** CMS - CMS-Flow<br />
<br />
== Related Links ==<br />
* [[SMS:SMS Models|SMS Models page]]<br />
* [[SMS:CMS-Wave|CMS-Wave]]<br />
<br />
== External Links ==<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/pubs/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://cirp.usace.army.mil/pubs/pdf/TR-04-2.pdf]<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 />
{{Template:SMSMain}}<br />
<br />
[[Category:CMS-Flow]]</div>Woodhttps://www.xmswiki.com/index.php?title=GMS:Map_to_MODFLOW&diff=35493GMS:Map to MODFLOW2011-07-27T19:47:22Z<p>Wood: </p>
<hr />
<div>: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 -> 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]] you wish 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 -> MODFLOW''''' command becomes available. When the command is selected, the Map -> 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 />
:'''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 you can not 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 />
:When using well screens in your 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 />
<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 />
{{hide in print|:[[Image:well_flux_conv.gif]]}}<br />
{{only in print|:[[Image:well_flux_conv.gif|frame|none|200px]]}}<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 />
<br />
<br />
:In order to complete this computation, the K's must be assigned to the cells in the grid. You must assign the K values to the grid prior to executing the Map -> 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. 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 you want 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 />
{{Navbox GMS}}</div>Woodhttps://www.xmswiki.com/index.php?title=GMS:T-PROGS&diff=35275GMS:T-PROGS2011-07-01T21:16:24Z<p>Wood: /* Material Limit */</p>
<hr />
<div>{{Infobox Model |<br />
|name= T-PROGS<br />
|screenshot= Image:Matset.gif<br />
|model_type= transition probability geostatistics on borehole data <br />
|developer= Steven Carle <br />
|quick_tour= [[GMS:Quick_Tour_-_T-PROGS|Quick Tour T-PROGS]]<br />
|documentation= [http://gmsdocs.aquaveo.com/t-progs.pdf T-Progs Manual]<br />
|tutorials= [[GMS:Tutorials#Models|T-PROGS Tutorials]]<br />
}}<br />
{{T-PROGS Links}}<br />
<br />
GMS includes an interface to the T-PROGS software developed by Steven Carle. The T-PROGS software is used to perform transition probability geostatistics on borehole data. The output of the T-PROGS software is a set of N [[GMS:Material Set|material sets]] on a 3D grid. Each of the material sets is conditioned to the borehole data and the materials proportions and transitions between the boreholes follows the trends observed in the borehole data. These material sets can be used for [[GMS:Stochastic Modeling#Stochastic Applications|stochastic simulations]] with MODFLOW. A sample material set generated by the TPROGS software is shown below. The T-PROGS software can also be used to generate multiple input data sets for the [[GMS:HUF Package|HUF package]].<br />
<br />
==T-PROGS Interface==<br />
<br />
{|<br />
| [[Image:pathlines.png|frame|none|''MODFLOW solution for a T-PROGS grid. Black lines are head contours and blue lines are pathlines for an extraction well.''|250px]]<br />
| [[Image:markov_graphs.png|frame|none|''Observed transition probabilities (circles) and Markov chain model (solid lines) for a set of borehole data with four materials.''|250px]]<br />
|}<br />
<br />
The T-PROGS software utilizes a transition probability-based geostatistical approach to model spatial variability by 3-D Markov Chains, set up indicator cokriging equations, and formulate the objective function for simulated annealing. The transition probability approach has several advantages over traditional indicator kriging methods. First, the transition probability approach considers asymmetric juxtapositional tendencies, such as fining-upwards sequences. Second, the transition probability approach has a conceptual framework for incorporating geologic interpretations into the development of cross-correlated spatial variability. Furthermore, the transition probability approach does not exclusively rely on empirical curve fitting to develop the indicator (cross-) variogram model. This is advantageous because geologic data are typically only adequate to develop a model of spatial variability in the vertical direction. The transition probability approach provides a conceptual framework to geologic insight into a simple and compact mathematical model, the Markov chain. This is accomplished by linking fundamental observable attributes – mean lengths, material proportions, anisotropy, and juxtapositioning – with Markov chain model parameters.<br />
<br />
The first step in using T-PROGS is to import a set of borehole data. The borehole data are then passed to a utility within T-PROGS called GAMEAS that computes a set of [[GMS:Vertical Markov Chain|transition probability curves]] as a function of lag distance for each category for a given sampling interval. A sample set of measured transition probability curves are shown by the dashed lines in the following figure.<br />
<br />
Each curve represents the transition probability from material j to material k. The transition probability t<sub>jk</sub>(h) is defined by:<br />
<br />
<!--[[Image:t-progs_eq1.png]]--><br />
<math>t_{jk}(\mathbf{h})= \text{Pr}\{k \text{ occurs at } \mathbf{x} + \mathbf{h}\ |\ j \text{ occurs at } \mathbf{x}\}</math><div style="float: right;"><ref><br />
{{citation <br />
|last=Carle<br />
|first=Steven F.<br />
|title=T-PROGS: Transition Probability Geostatistical Software. Version 2.1<br />
|place=Davis, California<br />
|year=1999<br />
|url=http://gmsdocs.aquaveo.com/t-progs.pdf<br />
|page=6<br />
}}</ref></div><br />
<br />
where x is a spatial location, h is the lag (separation vector), and j,k denote materials. Note that the curves on the diagonal represent auto-transition probabilities, and the curves on the off-diagonal represent cross-transition probabilities.<br />
<br />
The next step in the analysis is to develop a Markov Chain model for the vertical direction that fits the observed vertical transition probability data. The Markov Chain curves are shown as solid lines in the preceeding figure. Mathematically, a Markov chain model applied to one-dimensional categorical data in a direction Φ assumes a matrix exponential form:<br />
<br />
<!-- [[Image:t-progs_eq2.png]]--><br />
<math>\mathbf{T}(h_\phi)=\text{exp}(\mathbf{R}_{\phi}h_\phi)</math><div style="float: right;"><ref><br />
{{citation <br />
|last=Carle<br />
|first=Steven F.<br />
|title=T-PROGS: Transition Probability Geostatistical Software. Version 2.1<br />
|place=Davis, California<br />
|year=1999<br />
|url=http://gmsdocs.aquaveo.com/t-progs.pdf<br />
|page=26<br />
}}</ref></div><br />
<br />
where h denotes a lag in the direction Φ, and RΦ denotes a transition rate matrix<br />
<br />
[[Image:rate_matrix.gif]]<br />
<br />
with entries r<sub>jk</sub>,f representing the rate of change from category j to category k (conditional to the presence of j) per unit length in the direction Φ. The transition rates are adjusted to ensure a good fit between the Markov Chain model and the observed transition probability data.<br />
<br />
Once the Markov chain is developed for the z direction from the borehole data, a model of spatial variability must be developed for the x and y directions. Borehole data are typically not sufficiently dense in these directions. However, the [[GMS:Strike Dip Markov Chain|x and y-direction Markov chains]] can be developed by assuming that the juxtapositional tendencies and the proportions observed in the vertical direction also hold true in the horizontal directions. The modeler then provides an estimate of the ratio of the mean lengths in the x and y directions relative to the z direction, and the transition rate matrices for the x and y directions can be formulated. The x, y, and z Markov chains are converted into a continuous 3D Markov chain using the MCMOD utility within T-PROGS.<br />
<br />
In the final phase of setting up a transition probability analysis using T-PROGS, the modeler creates a grid, specifies the number of model instances (N), and launches the TSIM utility. The TSIM code uses the 3D Markov chain to formulate both indicator cokriging equations and an objective function for simulated annealing. It generates [[GMS:Stochastic Modeling#Stochastic Applications|stochastic simulations]] using a combination of modified versions of the GSLIB codes SISIM and ANNEAL.<br />
<br />
==T-PROGS OPTIONS==<br />
''T-PROGS Options dialog with and without borehole data.''<br />
{|<br />
| [[Image:t-progs_wo_boreholes.png|frame|none|''Without boreholes'']]<br />
| [[Image:t-progs_w_boreholes.png|frame|none|''With boreholes'']]<br />
|}<br />
<br />
When a user selects the ''New Simulation'' command to initialize a T-PROGS simulation, the ''T-PROGS Options'' dialog appears. If boreholes do not exist in the model, an unconditioned simulation will be generated. In this case, the user selects the materials to be used and a corresponding background material. The ''[[GMS:Materials|Materials Editor]]'' button enables users to quickly create, delete, or rename materials and the material list is automatically regenerated. The upper part of the dialog lists the materials in the boreholes. The first column of toggles indicates which materials are to be used in the analysis. By default, all materials associated with the boreholes are selected. These toggles are necessary since it is possible that there may be materials defined in the materials list that are not associated with boreholes. The second column in the top section of the dialog lists the background material. By default, the material type that had the predominant occurrence in the boreholes (greatest proportion) is marked as the background material. When defining the transition probability data in the next section, the input parameters do not need to be edited for the background material. The parameters for this material are automatically adjusted to balance the equations.<br />
<br />
===Background Material===<br />
<br />
Application of the transition probability approach involves the designation of a background material. The probabilistic constraints of the Markov chains make it unnecessary to quantify data for one category. Not only is it unnecessary, but it is futile to do so because values will be overwritten in order to satisfy constraints. Conceptually, the background material can be described as the material that “fills” in the remaining areas not occupied by other units. For example, in a fluvial depositional system, a floodplain unit would tend to occupy area not filled with higher-energy depositional units and would therefore be a logical choice for the background material.<br />
<br />
===Azimuth===<br />
''Azimuths for T-PROGS and 3D Grid.''<br />
{|multiple image<br />
| [[Image:azimuth1.png|frame|none|''T-Progs''|150px]]<br />
| [[Image:azimuth2.png|frame|none|''3D Grid''|175px]]<br />
|}<br />
<br />
The user also enters an azimuth in this dialog. The azimuth determines the orientation of the primary directions of the depositional trends in the strike/dip directions. These trends generally are aligned with the primary directions of horizontal flow in the aquifer. Theoretically, the azimuth can be oriented independently from the grid orientation. However, in practice, if the grid and azimuth orientations are offset by more than about 40<sup>o</sup>, checkerboard patterns appear in the indicator array results. Hence, the azimuth orientation is set equal to the grid orientation by default. However, the grid angle is defined counterclockwise, and the azimuth angle is clockwise. Therefore, if the grid angle is 40<sup>o</sup>, then the azimuth angle will be –40<sup>o</sup> by default. If there is anisotropy in the xy plane, the azimuth angle should be set to the principle direction of the anisotropy. If anisotropy is not present, this angle should be coincident with the x-axis (the rows or j-direction) of the grid.<br />
<br />
===Material Limit===<br />
<br />
One limitation for both the cases with and without boreholes is that a maximum of nine materials (starting at GMS version 8.0 if you have the WASH interface enabled - five prior to 8.0 and without the WASH interface enabled) can be used in the T-PROGS algorithm. This limitation was imposed to keep the data processing and user-interface reasonably simple. Although nine materials present a limitation, borehole data can generally be easily condensed down to nine or fewer materials. Furthermore since this is a stochastic approach, which is based on probability, the detail generated with numerous materials is rarely justifiable anyway. In addition, as the number of materials increase, the ratio of process time to detail becomes inefficient.<br />
<br />
==Generating Material Sets with T-PROGS==<br />
The underlying equations solved by the T-PROGS software require an orthogonal grid with constant cell dimensions (X, Y, and Z). The delta X values can be different from the delta Y and delta Z values, and the delta Y values can be different from the delta Z values, but all cells must have the same change in X, Y, and Z dimensions. The MODFLOW model is capable of using the [[GMS:LPF Package|Layer Property Flow (LPF) Package]] with the Material ID option for assigning aquifer properties. With this option, each cell in the grid is assigned a material id and the aquifer properties (Kh, Kv, etc.) associated with each material are automatically assigned to the layer data arrays for the LPF package when the MODFLOW files are saved. The T-PROGS software generates multiple material sets (arrays of material ids), each of which represents a different realization of the aquifer heterogeneity. When running a MODFLOW simulation in [[GMS:Stochastic Modeling#Stochastic Applications|stochastic mode]], GMS automatically loads each of the N material sets generated by the T-PROGS software and saves N different sets of MODFLOW input files. The N solutions resulting from these simulations can be read into GMS and used to perform [[GMS:Risk_Analysis_Wizard|risk analyses]] such as probabilistic capture zone delineation.<br />
<br />
=== One-Layer MODFLOW Grids ===<br />
[[Image:matset_samp.png|right|thumb|''Sample material set generated by the T-PROGS software. Blue lines represent particle path lines and black lines are head contours.''|275px]]<br />
<br />
Although MODFLOW is a three-dimensional model, a majority of the MODFLOW models constructed by typical users are 2D models consisting of one model layer. There are several reasons why 2D models are so common. One reason is that many of these models are regional models where the aquifer thickness is very small compared to the lateral extent of the model. As a result, the flow directions are primarily horizontal and little improvement is gained by adding multiple layers to the model. Even with local scale models, the aquifer thickness is often small enough that one-layer models are considered adequate. 2D models are also attractive due to the simplicity of the model increased computational efficiency. One of the problems associated with using multiple layers for MODFLOW models with unconfined aquifers is that as the water table fluctuates, the upper cells may go dry. These cells will not rewet even if the water table subsequently rises, unless the rewetting option has been selected in the flow package (BCF, LPF, or HUF). The rewetting issues can often be avoided with a one-layer model.<br />
<br />
When developing a one-layer model, the modeler must determine how to distribute the hydraulic conductivity values within the layer. One option is to assume a homogenous aquifer; this is typically a gross over-simplification since aquifers are usually highly heterogeneous. Therefore, a common approach is to delineate zones of hydraulic conductivity by examining the subsurface stratigraphic data. In many cases, these data are in the form of borehole logs. These borehole logs often exhibit substantial heterogeneity and don’t always exhibit definitive trends between adjacent boreholes. Furthermore, the boreholes are often clustered with large regions of the model lacking any borehole data. The modeler then faces a difficult task of trying to determine a rational approach to delineating two-dimensional zones of hydraulic conductivity based on complex 3D borehole data.<br />
<br />
As part of this research, we developed a technique for developing 2D zones of hydraulic conductivity from borehole logs using transition probability geostatistics. The technique is simple, fast, and preserves proportions and trends exhibited by the borehole data. The algorithm parses through each borehole and computes a predominant material at each borehole. When T-PROGS runs, the predominant material for each borehole is assigned to its corresponding location in the one-layer grid, and during the quenching process, simulations are conditioned to those data points.<br />
<br />
==Generating HUF Data with T-PROGS==<br />
<br />
Using transition probability geostatistics with MODFLOW models results in two basic limitations. First, the underlying stochastic algorithms used by the T-PROGS software are formulated such that the MODFLOW grid must have uniform row, column, and layer widths. The row width can be different from the column width, but each row must have the same width. This results in a uniform orthogonal grid. While MODFLOW grids are orthogonal in x and y, the layer thickness is allowed to vary on a cell-by-cell basis. This makes it possible for the layer boundaries to accurately model the ground surface and the tops and bottoms of aquifer units. If a purely orthogonal grid is used, irregular internal and external layer boundaries must be simulated in a stair-step fashion either by varying material properties or by activating/inactivating cells via the IBOUND array. A second limitation is that in order to get a high level of detail in the simulated heterogeneity, the grid cell dimensions are generally kept quite small. This can result in difficulties in the vertical dimension. The large number of layers with small layer thicknesses near the top of the model generally ensures that many of the cells in this region will be at or above the computed water table elevation (for simulations involving unconfined aquifers). As a result, these cells will undergo many of the numerical instabilities and increased computational effort issues associated with cell wetting and drying.<br />
<br />
[[Image:huf_sample.gif|right|frame|''Sample HUF stratigraphy data generated by the T-PROGS software. Blue lines represent particle path lines and water table.''|300px]]<br />
<br />
The Hydrogeologic Unit Flow (HUF) package released with MODFLOW 2000 makes it possible to overcome both of these limitations resulting in a powerful mechanism for incorporating transition probability geostatistics in MODFLOW simulations. With the HUF package, the modeler is allowed to input the vertical component of the stratigraphy in a grid-independent fashion. The stratigraphy data are defined using a set of elevation and thickness arrays. The first array defines the top elevation of the model. The remaining arrays define the thicknesses of a series of hydrogeologic units, starting at the top and progressing to the bottom of the model. For each array of thicknesses, many of the entries in the array may be zero. This makes it possible to simulate complex heterogeneity, including pinchouts and embedded lenses that would be difficult to simulate with the LPF and BCF packages.<br />
<br />
The T-PROGS interface in GMS includes an option for integrating transition probability geostatistics results with the HUF package. The basic approach used by the option is to overlay a dense background grid on the MODFLOW grid and run T-PROGS on the background grid. A set of HUF arrays is then extracted from the background grid for use with the MODFLOW model. To use this option, user should first create a MODFLOW grid with the desired number of layers and the layer elevations should be interpolated to match the aquifer boundaries. The row and column widths are uniform but the layer thicknesses may vary from cell to cell. Then, when TSIM is launched, the HUF option should be selected. GMS then generates a background grid that encompasses the MODFLOW grid. The rows and columns of this grid match the MODFLOW grid but the layer thicknesses are uniform and relatively thin, resulting in a much greater number of layers than the MODFLOW grid. The user specifies the number of layers in this background grid. A T-PROGS simulation is then performed to get a set of material sets on the background grid. Each of the material sets in the T-PROGS output is then transferred from the background grid to a set of HUF elevation/thickness arrays. The HUF top elevation array is set equal to the top of the MODFLOW grid. The thickness arrays are then found by searching through the background grid to find the bottom elevations of contiguous groups of indicators. The elevations from these groups are then added to an appropriate elevation array in the HUF input. The resulting set of HUF input arrays are listed in GMS [[GMS:The GMS Screen|Project Explorer]]. By clicking on each item in the [[GMS:Project Explorer|Project Explorer]], the selected set of HUF arrays are loaded into the HUF package and the corresponding stratigraphy is displayed in the GMS window. The multiple HUF input arrays can be used to perform a [[GMS:Stochastic Modeling#Stochastic Applications|stochastic simulation]].<br />
<br />
==Notes==<br />
<references/><br />
<br />
<br />
{{Navbox GMS}}<br />
[[Category:T-PROGS]]<br />
[[Category:Stochastic]]</div>Woodhttps://www.xmswiki.com/index.php?title=WMS:Models&diff=35004WMS:Models2011-06-24T14:04:01Z<p>Wood: /* Models Available in WMS */</p>
<hr />
<div>==Hydraulic Models==<br />
<br />
The primary purpose of the hydraulic modeling interface within WMS is to process digital terrain and map data (TINs and coverages) to build the basic geometry necessary for a 1D Hydraulic Model. Much of the information for developing models with these tools is described in the information on [[WMS:River Tools|River Tools]] in the [[WMS:The Map Module|Map module]].<br />
<br />
:* [[WMS:Hydraulic Modeling Introduction|Hydraulic Modeling]]<br />
<br />
It is possible to establish the hydraulic model with extracting cross section information from a TIN. Cross sections which have already been surveyed can be used by assigning them to an arc. This, along with geo-referencing the data is done using the cross section editor from the '''River Tools''' menu in the Map module (when River Tools is the active model).<br />
<br />
==Hydrologic Models==<br />
<br />
Hydrologic analysis is typically done using lumped parameter models such as HEC-1. The Tree module provides a graphical interface to HEC-1, TR-20, HSPF, TR-55, Rational Method, the National Flood Frequency (NFF), and other programs. In the absence of terrain data, topological or tree representations of a watershed can be created. Then all necessary input data to run one of the supported models can be defined using a series of user-friendly dialogs. <br />
<br />
:* [[WMS:Hydrologic Modeling Module|Hydrologic Modeling]]<br />
<br />
<br />
==Related Topics==<br />
:* [[WMS:Hydraulic Modeling Introduction|Hydraulic Modeling]]<br />
:* [[WMS:Hydrologic Modeling Module|Hydrologic Modeling]]<br />
<br />
==Models Available in WMS==<br />
:* [[WMS:CE-QUAL-W2|CE-QUAL-W2]]<br />
:* [[WMS:GSSHA|GSSHA]]<br />
:* [[WMS:HEC-1|HEC-1]]<br />
:* [[WMS:HEC-HMS|HEC-HMS]]<br />
:* [[WMS:HEC-RAS|HEC-RAS]]<br />
:* [[WMS:HSPF|HSPF]]<br />
:* [[WMS:MODRAT|MODRAT]]<br />
:* [[WMS:NFF|NFF]]<br />
:* [[WMS:Orange County Unit Hydrograph|OC Hydrograph]]<br />
:* [[WMS:Orange County Rational Method|OC Rational]]<br />
:* [[WMS:Rational Method|Rational]]<br />
:* [[WMS:River Tools|River Tools]]<br />
:* [[WMS:Storm Drain|Storm Drain]]<br />
:* [[WMS:Storm Drain-FHWA|Storm Drain-FHWA]]<br />
:* [[WMS:SMPDBK|SMPDBK]]<br />
:* [[WMS:SWMM|SWMM]]<br />
:* [[WMS:TR-20|TR-20]]<br />
:* [[WMS:TR-55|TR-55]]</div>Woodhttps://www.xmswiki.com/index.php?title=SMS:Images&diff=34151SMS:Images2011-06-07T17:07:41Z<p>Wood: </p>
<hr />
<div>{{SMS_at_a_glance_image_support|Heading===At a glance==}}<br />
<br />
A background image is a digital picture detailing topographic and land use attributes of an area of interest. In SMS, these digital pictures are typically maps or aerial photos that are useful in locating and defining the boundaries of the study area and the extents and features in the project domain. Images can be imported to SMS and displayed in the background to aid in the placement of objects as they are being constructed or simply to enhance a plot. Images can also be draped or "texture mapped" or draped onto a [[SMS:Scatter_Module | scatter data set]] (TIN) or [[SMS:Mesh_Module | finite element mesh]].<br />
<br />
== Supported Image File Formats ==<br />
* [http://en.wikipedia.org/wiki/Enhanced_Compressed_Wavelet_File Enhanced Compression Wavelet] (.ecw)<br />
* [http://en.wikipedia.org/wiki/Gif Graphics Interchange Format] (.gif)<br />
* [http://en.wikipedia.org/wiki/Jpeg Joint Photographic Experts Group] - (.jpg/jpeg)<br />
* [http://en.wikipedia.org/wiki/Mrsid Multiresolution Seamless Image Database] - (.MrSID)<br />
* [http://en.wikipedia.org/wiki/Tiff Tagged Image File Format] - (.tiff)<br />
<br />
== Importing an Image ==<br />
Images can be opened in SMS using the ''File | Open'' menu command. They can also be added to a simulation by dragging and dropping the file into SMS. The images are then added to the image folder in the [[SMS:Project Explorer|Project Explorer]] and displayed in the background to aid in the placement of objects as they are being constructed or simply to enhance visualization of the project domain. All TIFF images are converted to JPEG when they are read in. Multiple images can be imported into SMS.<br />
<br />
== Exporting Image Files ==<br />
Images (or files related to images) are saved in the following ways:<br />
<br />
=== Save As ===<br />
The image displayed in the Graphics Window can be saved as a Bitmap Image File (*.bmp) or JPEG Image File (*.jpg, *.jpeg) using the [[SMS:File_Menu|''File | Save As'' menu command]] and specifying an image file as the save as type. The resolution of the saved image is based on the screen resolution and scale factor specified in the [[SMS:Preferences|Preferences dialog]].<br />
<br />
=== Project File ===<br />
When a project file is saved any images that are part of the project are saved. The registration information is saved in the project file to provide the coordinate system information for the image.<br />
<br />
=== Copy to Clipboard ===<br />
When the [[SMS:Edit_Menu#Copy_to_Clipboard|''Edit | Copy to Clipboard'' menu command]] is selected, the image currently displayed in the Graphics Window is copied to the clipboard. This image can then be pasted into reports or other programs by pressing ''CTRL + V''. The resolution of the saved image is based on the screen resolution and scale factor specified in the [[SMS:Preferences|Preferences dialog]].<br />
<br />
=== Export World File ===<br />
A World File can be exported for the selected image by right-clicking on the [[SMS:Project Explorer|Project Explorer]] and selecting the Export World File command. A world file is a special file that contains registration data that can be used to register images.<br />
<br />
== Geo-Referencing ==<br />
A geo-referenced image includes information specifying the real world size and location of the image. The coordinate system can be embedded in the file or given in a separate file called a world file (for example: a tiff world file, *.tfw). When geo-referenced image files are opened, SMS automatically registers the image to the real world coordinate location specified. In the case where a separate world file is used, SMS will search for it and register the image if the world file has the same filename prefix as the image file and is in the same folder.<br />
<br />
If the image file is not geo-referenced then you will have to [[Registering an Image|register the image]] manually. (See [[Registering an Image|Registering an Image]])<br />
<br />
When the SMS project is saved, a link to the image is saved in the project file, along with the current image registration information so that the image is re-registered to the same coordinates every time the project is opened. The original image file and world file (if one exists) are not altered.<br />
<br />
== Display Options ==<br />
Image display options are changed in the [[SMS:Project Explorer|Project Explorer]]. Display options include:<br />
* '''Visibility''' - The visibility of an image is turned off by toggling the check box next to the image in the [[SMS:Project Explorer|Project Explorer]].<br />
* '''Transparency''' - The transparency of each image can be changed by right-clicking on the image in the [[SMS:Project Explorer|Project Explorer]] and selecting ''Transparency'' from the right click menu.<br />
<br />
== Image Deletion ==<br />
A single image is deleted by right-clicking on the image in the [[SMS:Project Explorer|Project Explorer]] and selecting the ''Delete'' command. To delete all images, you right-click on the Images folder in the [[SMS:Project Explorer|Project Explorer]] and select ''Clear Images''.<br />
<br />
== Dynamic Imagery from ArcGIS ==<br />
Starting in SMS 11.0 (32-bit only), dynamic background images can be accessed from the web through ArcGIS. If you have ArcGIS on your computer, you can use the GIS module within SMS to get background imagery that updates on the fly from the internet. To access these images, follow the steps below.<br />
<br />
#Switch to the GIS module (select the globe in the bottom left of the SMS screen)<br />
#Select “Data | Enable ArcObjects”<br />
#Select “Data | Add Data…”<br />
#Browse to the “C:\Program Files (x86)\SMS 11.0\Supporting Files\GIS Layer Files” directory<br />
#Select the desired layer<br />
#Select “Add”<br />
<br />
Note: This feature is only available in the SMS 11.0 beta (32-bit). Since this version is still in beta, it should not be used in place of the release version of SMS (SMS 10.1).<br />
<br />
== Related Topics ==<br />
* [[Image Pyramids|Image Pyramids]]<br />
* [[Import from Web]]<br />
* [[Registering an Image|Registering an Image]]<br />
<br />
{{Template:SMSMain}}</div>Woodhttps://www.xmswiki.com/index.php?title=GMS:Coverages&diff=34092GMS:Coverages2011-06-01T14:16:03Z<p>Wood: /* 3D grid layer option for obs. pts */</p>
<hr />
<div>{{Map links}}<br />
[[GMS:Feature Objects|Feature Objects]] in the Map module are grouped into coverages. Coverages are grouped into [[GMS:Conceptual Models|conceptual models]].<br />
<br />
A coverage is similar to a layer in a CAD drawing. Each coverage represents a particular set of information. For example, one coverage could be used to define recharge zones and another coverage could be used to define zones of hydraulic conductivity. These objects could not be included in a single coverage since polygons within a coverage are not allowed to overlap and recharge zones will typically overlap hydraulic conductivity zones.<br />
<br />
Coverages are managed using the [[GMS:The GMS Screen|Project Explorer]]. Coverages are organized below conceptual models. When GMS is first launched, no coverage exists. If no coverage exists and the user creates [[GMS:Feature Objects|feature objects]] then a new coverage will automatically be created. When multiple coverages are created, one coverage is designated the "active" coverage. New feature objects are always added to the active coverage and only objects in the active coverage can be edited. The figure below shows several coverages in the [[GMS:Project Explorer|Project Explorer]]. The active coverage is displayed with a color icon and bold text. A coverage is made the active coverage by selecting it from the [[GMS:Project Explorer|Project Explorer]]. In some cases it is useful to hide some or all of the coverages. The visibility of a coverage is controlled using the check box next to the coverage in the [[GMS:Project Explorer|Project Explorer]].<br />
<br />
A new coverage can be created by right-clicking on a folder or conceptual model and selecting the '''''New Coverage''''' command in the pop-up menu. <br />
<br />
[[Image:Tree_Map.gif]]<br />
<br />
Right clicking on a coverage brings up a menu with the following options: Delete, Duplicate, Rename, Coverage Setup, Attribute Table, the Map To submenu, Transform, Export, and Properties. The Delete, Duplicate, and Rename commands are self explanatory.<br />
<br />
== Coverage Setup ==<br />
The Coverage Setup command brings up the Coverage Setup dialog. This dialog controls the properties that are assigned to feature objects. The feature object properties have been divided into 3 general categories: ''Sources/Sinks/BCs'', ''Areal Properties'', and ''Observation Points''. Under the ''Sources/Sinks/BCs'' the user can select which source/sinks he would like to include in the coverage (like wells, rivers, drains, etc). ''Areal Properties'' includes recharge, ET, hydraulic conductivity, and other properties that are assigned to polygonal zones. ''Observation Points'' control which data sets have associated observation data.<br />
<br />
The ''Coverage type'' is used for WASH123D conceptual models to set the coverage to be a 3D or a 2D coverage.<br />
<br />
The ''Default layer range'' is used with MODFLOW conceptual models to default the "from layer"/"to layer" assignments for boundary conditions.<br />
<br />
The ''Use to define model boundary'' toggle is used with MODFLOW and MODAEM. This means that the polygons in this coverage are used to define the active area of the model.<br />
<br />
=== 3D grid layer option for obs. pts ===<br />
The ''3D grid layer option for obs. pts.'' is used to set the input option for observations associated with MODFLOW conceptual models. The MODFLOW observation package can handle observations that include multiple cells.Three options are available for determining which layer the observation point will be located:<br />
<br />
*by z location - When the "by z location" option is selected, the computed value for the observation point (that will be compared with the observed value) will be taken from the cell that corresponds with the elevation value assigned to the observation point.<br />
<br />
*by layer number - If you select the "by layer number" option in the coverage setup, the computed value will be taken from the cell that corresponds to the layer that is specified in the observation point coverage properties.<br />
<br />
*Use well screen - This option may be used when the model includes wells with screens. GMS finds the cell or cells that intersect the screened interval the user has entered.<br />
<br />
The ''Default elevation'' field can be used to define the initial Z elevation of new objects created in a coverage. By assigning a different elevation to each of the coverages, the coverages can be displayed as a stack of layers in oblique view.<br />
<br />
== Feature Object Attribute Table ==<br />
All feature object properties are edited using a single spreadsheet. This makes it possible to cut and paste feature object data using the clipboard and it makes it easier to edit entire columns of data at once. Filters at the top of the dialog control what type of objects are displayed.<br />
<br />
== Map To Submenu ==<br />
Coverages can be mapped to other geometric objects or Numerical models by selecting the corresponding command from the Map to Submenu.<br />
<br />
==''Related Links''==<br />
<br />
[[GMS:Conceptual Models|Conceptual Models]]<br />
<br />
[[GMS:Feature Objects|Feature Objects]]<br />
<br />
{{Navbox GMS}}</div>Woodhttps://www.xmswiki.com/index.php?title=GMS:Coverages&diff=34091GMS:Coverages2011-06-01T14:15:18Z<p>Wood: /* 3D grid layer option for obs. pts */</p>
<hr />
<div>{{Map links}}<br />
[[GMS:Feature Objects|Feature Objects]] in the Map module are grouped into coverages. Coverages are grouped into [[GMS:Conceptual Models|conceptual models]].<br />
<br />
A coverage is similar to a layer in a CAD drawing. Each coverage represents a particular set of information. For example, one coverage could be used to define recharge zones and another coverage could be used to define zones of hydraulic conductivity. These objects could not be included in a single coverage since polygons within a coverage are not allowed to overlap and recharge zones will typically overlap hydraulic conductivity zones.<br />
<br />
Coverages are managed using the [[GMS:The GMS Screen|Project Explorer]]. Coverages are organized below conceptual models. When GMS is first launched, no coverage exists. If no coverage exists and the user creates [[GMS:Feature Objects|feature objects]] then a new coverage will automatically be created. When multiple coverages are created, one coverage is designated the "active" coverage. New feature objects are always added to the active coverage and only objects in the active coverage can be edited. The figure below shows several coverages in the [[GMS:Project Explorer|Project Explorer]]. The active coverage is displayed with a color icon and bold text. A coverage is made the active coverage by selecting it from the [[GMS:Project Explorer|Project Explorer]]. In some cases it is useful to hide some or all of the coverages. The visibility of a coverage is controlled using the check box next to the coverage in the [[GMS:Project Explorer|Project Explorer]].<br />
<br />
A new coverage can be created by right-clicking on a folder or conceptual model and selecting the '''''New Coverage''''' command in the pop-up menu. <br />
<br />
[[Image:Tree_Map.gif]]<br />
<br />
Right clicking on a coverage brings up a menu with the following options: Delete, Duplicate, Rename, Coverage Setup, Attribute Table, the Map To submenu, Transform, Export, and Properties. The Delete, Duplicate, and Rename commands are self explanatory.<br />
<br />
== Coverage Setup ==<br />
The Coverage Setup command brings up the Coverage Setup dialog. This dialog controls the properties that are assigned to feature objects. The feature object properties have been divided into 3 general categories: ''Sources/Sinks/BCs'', ''Areal Properties'', and ''Observation Points''. Under the ''Sources/Sinks/BCs'' the user can select which source/sinks he would like to include in the coverage (like wells, rivers, drains, etc). ''Areal Properties'' includes recharge, ET, hydraulic conductivity, and other properties that are assigned to polygonal zones. ''Observation Points'' control which data sets have associated observation data.<br />
<br />
The ''Coverage type'' is used for WASH123D conceptual models to set the coverage to be a 3D or a 2D coverage.<br />
<br />
The ''Default layer range'' is used with MODFLOW conceptual models to default the "from layer"/"to layer" assignments for boundary conditions.<br />
<br />
The ''Use to define model boundary'' toggle is used with MODFLOW and MODAEM. This means that the polygons in this coverage are used to define the active area of the model.<br />
<br />
=== 3D grid layer option for obs. pts ===<br />
The ''3D grid layer option for obs. pts.'' is used to set the input option for observations associated with MODFLOW conceptual models. The MODFLOW observation package can handle observations that include multiple cells.Three options are available for determining which layer the observation point will be located:<br />
<br />
*by z location - When the "by z location" option is selected, the computed value for the observation point (that will be compared with the observed value) will be taken from the cell that corresponds with the elevation value assigned to the observation point.<br />
<br />
*by layer number - If you select the "by layer number" option in the coverage setup, the computed value will be taken from the cell that corresponds to the layer that is specified in the observation point coverage properties.<br />
<br />
*Use well screen - Use this option if you are using a well with a screen. GMS finds the cell or cells that intersect the screened interval the user has entered.<br />
<br />
The ''Default elevation'' field can be used to define the initial Z elevation of new objects created in a coverage. By assigning a different elevation to each of the coverages, the coverages can be displayed as a stack of layers in oblique view.<br />
<br />
== Feature Object Attribute Table ==<br />
All feature object properties are edited using a single spreadsheet. This makes it possible to cut and paste feature object data using the clipboard and it makes it easier to edit entire columns of data at once. Filters at the top of the dialog control what type of objects are displayed.<br />
<br />
== Map To Submenu ==<br />
Coverages can be mapped to other geometric objects or Numerical models by selecting the corresponding command from the Map to Submenu.<br />
<br />
==''Related Links''==<br />
<br />
[[GMS:Conceptual Models|Conceptual Models]]<br />
<br />
[[GMS:Feature Objects|Feature Objects]]<br />
<br />
{{Navbox GMS}}</div>Woodhttps://www.xmswiki.com/index.php?title=GMS:Coverages&diff=34090GMS:Coverages2011-06-01T14:14:34Z<p>Wood: /* 3D grid layer option for obs. pts */</p>
<hr />
<div>{{Map links}}<br />
[[GMS:Feature Objects|Feature Objects]] in the Map module are grouped into coverages. Coverages are grouped into [[GMS:Conceptual Models|conceptual models]].<br />
<br />
A coverage is similar to a layer in a CAD drawing. Each coverage represents a particular set of information. For example, one coverage could be used to define recharge zones and another coverage could be used to define zones of hydraulic conductivity. These objects could not be included in a single coverage since polygons within a coverage are not allowed to overlap and recharge zones will typically overlap hydraulic conductivity zones.<br />
<br />
Coverages are managed using the [[GMS:The GMS Screen|Project Explorer]]. Coverages are organized below conceptual models. When GMS is first launched, no coverage exists. If no coverage exists and the user creates [[GMS:Feature Objects|feature objects]] then a new coverage will automatically be created. When multiple coverages are created, one coverage is designated the "active" coverage. New feature objects are always added to the active coverage and only objects in the active coverage can be edited. The figure below shows several coverages in the [[GMS:Project Explorer|Project Explorer]]. The active coverage is displayed with a color icon and bold text. A coverage is made the active coverage by selecting it from the [[GMS:Project Explorer|Project Explorer]]. In some cases it is useful to hide some or all of the coverages. The visibility of a coverage is controlled using the check box next to the coverage in the [[GMS:Project Explorer|Project Explorer]].<br />
<br />
A new coverage can be created by right-clicking on a folder or conceptual model and selecting the '''''New Coverage''''' command in the pop-up menu. <br />
<br />
[[Image:Tree_Map.gif]]<br />
<br />
Right clicking on a coverage brings up a menu with the following options: Delete, Duplicate, Rename, Coverage Setup, Attribute Table, the Map To submenu, Transform, Export, and Properties. The Delete, Duplicate, and Rename commands are self explanatory.<br />
<br />
== Coverage Setup ==<br />
The Coverage Setup command brings up the Coverage Setup dialog. This dialog controls the properties that are assigned to feature objects. The feature object properties have been divided into 3 general categories: ''Sources/Sinks/BCs'', ''Areal Properties'', and ''Observation Points''. Under the ''Sources/Sinks/BCs'' the user can select which source/sinks he would like to include in the coverage (like wells, rivers, drains, etc). ''Areal Properties'' includes recharge, ET, hydraulic conductivity, and other properties that are assigned to polygonal zones. ''Observation Points'' control which data sets have associated observation data.<br />
<br />
The ''Coverage type'' is used for WASH123D conceptual models to set the coverage to be a 3D or a 2D coverage.<br />
<br />
The ''Default layer range'' is used with MODFLOW conceptual models to default the "from layer"/"to layer" assignments for boundary conditions.<br />
<br />
The ''Use to define model boundary'' toggle is used with MODFLOW and MODAEM. This means that the polygons in this coverage are used to define the active area of the model.<br />
<br />
=== 3D grid layer option for obs. pts ===<br />
The ''3D grid layer option for obs. pts.'' is used to set the input option for observations associated with MODFLOW conceptual models. The MODFLOW observation package can handle observations that include multiple cells.Three options are available for determining which layer the observation point will be located:<br />
<br />
*by z location - When the "by z location" option is selected, the computed value for the observation point (that will be compared with the observed value) will be taken from the cell that corresponds with the elevation value assigned to the observation point.<br />
<br />
*by layer number - If you select the "by layer number" option in the coverage setup, the computed value will be taken from the cell that corresponds to the layer that is specified in the observation point coverage properties.<br />
<br />
*Use well screen - Use this option if you are using a well with a screen. GMS finds the cell or cells that intersect the screened interval if the user has properly defined a screened interval for the point.<br />
<br />
The ''Default elevation'' field can be used to define the initial Z elevation of new objects created in a coverage. By assigning a different elevation to each of the coverages, the coverages can be displayed as a stack of layers in oblique view.<br />
<br />
== Feature Object Attribute Table ==<br />
All feature object properties are edited using a single spreadsheet. This makes it possible to cut and paste feature object data using the clipboard and it makes it easier to edit entire columns of data at once. Filters at the top of the dialog control what type of objects are displayed.<br />
<br />
== Map To Submenu ==<br />
Coverages can be mapped to other geometric objects or Numerical models by selecting the corresponding command from the Map to Submenu.<br />
<br />
==''Related Links''==<br />
<br />
[[GMS:Conceptual Models|Conceptual Models]]<br />
<br />
[[GMS:Feature Objects|Feature Objects]]<br />
<br />
{{Navbox GMS}}</div>Woodhttps://www.xmswiki.com/index.php?title=GMS:Coverages&diff=34089GMS:Coverages2011-06-01T14:11:46Z<p>Wood: /* 3D grid layer option for obs. pts */</p>
<hr />
<div>{{Map links}}<br />
[[GMS:Feature Objects|Feature Objects]] in the Map module are grouped into coverages. Coverages are grouped into [[GMS:Conceptual Models|conceptual models]].<br />
<br />
A coverage is similar to a layer in a CAD drawing. Each coverage represents a particular set of information. For example, one coverage could be used to define recharge zones and another coverage could be used to define zones of hydraulic conductivity. These objects could not be included in a single coverage since polygons within a coverage are not allowed to overlap and recharge zones will typically overlap hydraulic conductivity zones.<br />
<br />
Coverages are managed using the [[GMS:The GMS Screen|Project Explorer]]. Coverages are organized below conceptual models. When GMS is first launched, no coverage exists. If no coverage exists and the user creates [[GMS:Feature Objects|feature objects]] then a new coverage will automatically be created. When multiple coverages are created, one coverage is designated the "active" coverage. New feature objects are always added to the active coverage and only objects in the active coverage can be edited. The figure below shows several coverages in the [[GMS:Project Explorer|Project Explorer]]. The active coverage is displayed with a color icon and bold text. A coverage is made the active coverage by selecting it from the [[GMS:Project Explorer|Project Explorer]]. In some cases it is useful to hide some or all of the coverages. The visibility of a coverage is controlled using the check box next to the coverage in the [[GMS:Project Explorer|Project Explorer]].<br />
<br />
A new coverage can be created by right-clicking on a folder or conceptual model and selecting the '''''New Coverage''''' command in the pop-up menu. <br />
<br />
[[Image:Tree_Map.gif]]<br />
<br />
Right clicking on a coverage brings up a menu with the following options: Delete, Duplicate, Rename, Coverage Setup, Attribute Table, the Map To submenu, Transform, Export, and Properties. The Delete, Duplicate, and Rename commands are self explanatory.<br />
<br />
== Coverage Setup ==<br />
The Coverage Setup command brings up the Coverage Setup dialog. This dialog controls the properties that are assigned to feature objects. The feature object properties have been divided into 3 general categories: ''Sources/Sinks/BCs'', ''Areal Properties'', and ''Observation Points''. Under the ''Sources/Sinks/BCs'' the user can select which source/sinks he would like to include in the coverage (like wells, rivers, drains, etc). ''Areal Properties'' includes recharge, ET, hydraulic conductivity, and other properties that are assigned to polygonal zones. ''Observation Points'' control which data sets have associated observation data.<br />
<br />
The ''Coverage type'' is used for WASH123D conceptual models to set the coverage to be a 3D or a 2D coverage.<br />
<br />
The ''Default layer range'' is used with MODFLOW conceptual models to default the "from layer"/"to layer" assignments for boundary conditions.<br />
<br />
The ''Use to define model boundary'' toggle is used with MODFLOW and MODAEM. This means that the polygons in this coverage are used to define the active area of the model.<br />
<br />
=== 3D grid layer option for obs. pts ===<br />
The ''3D grid layer option for obs. pts.'' is used to set the input option for observations associated with MODFLOW conceptual models. Three options are available for determining which layer the observation point will be located:<br />
<br />
*by z location - When the "by z location" option is selected, the computed value for the observation point (that will be compared with the observed value) will be taken from the cell that corresponds with the elevation value assigned to the observation point.<br />
<br />
*by layer number - If you select the "by layer number" option in the coverage setup, the computed value will be taken from the cell that corresponds to the layer that is specified in the observation point coverage properties.<br />
<br />
*Use well screen - Use this option if you are using a well with a screen.<br />
<br />
The ''Default elevation'' field can be used to define the initial Z elevation of new objects created in a coverage. By assigning a different elevation to each of the coverages, the coverages can be displayed as a stack of layers in oblique view.<br />
<br />
== Feature Object Attribute Table ==<br />
All feature object properties are edited using a single spreadsheet. This makes it possible to cut and paste feature object data using the clipboard and it makes it easier to edit entire columns of data at once. Filters at the top of the dialog control what type of objects are displayed.<br />
<br />
== Map To Submenu ==<br />
Coverages can be mapped to other geometric objects or Numerical models by selecting the corresponding command from the Map to Submenu.<br />
<br />
==''Related Links''==<br />
<br />
[[GMS:Conceptual Models|Conceptual Models]]<br />
<br />
[[GMS:Feature Objects|Feature Objects]]<br />
<br />
{{Navbox GMS}}</div>Woodhttps://www.xmswiki.com/index.php?title=GMS:Coverages&diff=34088GMS:Coverages2011-06-01T14:11:31Z<p>Wood: /* Map To Submenu */</p>
<hr />
<div>{{Map links}}<br />
[[GMS:Feature Objects|Feature Objects]] in the Map module are grouped into coverages. Coverages are grouped into [[GMS:Conceptual Models|conceptual models]].<br />
<br />
A coverage is similar to a layer in a CAD drawing. Each coverage represents a particular set of information. For example, one coverage could be used to define recharge zones and another coverage could be used to define zones of hydraulic conductivity. These objects could not be included in a single coverage since polygons within a coverage are not allowed to overlap and recharge zones will typically overlap hydraulic conductivity zones.<br />
<br />
Coverages are managed using the [[GMS:The GMS Screen|Project Explorer]]. Coverages are organized below conceptual models. When GMS is first launched, no coverage exists. If no coverage exists and the user creates [[GMS:Feature Objects|feature objects]] then a new coverage will automatically be created. When multiple coverages are created, one coverage is designated the "active" coverage. New feature objects are always added to the active coverage and only objects in the active coverage can be edited. The figure below shows several coverages in the [[GMS:Project Explorer|Project Explorer]]. The active coverage is displayed with a color icon and bold text. A coverage is made the active coverage by selecting it from the [[GMS:Project Explorer|Project Explorer]]. In some cases it is useful to hide some or all of the coverages. The visibility of a coverage is controlled using the check box next to the coverage in the [[GMS:Project Explorer|Project Explorer]].<br />
<br />
A new coverage can be created by right-clicking on a folder or conceptual model and selecting the '''''New Coverage''''' command in the pop-up menu. <br />
<br />
[[Image:Tree_Map.gif]]<br />
<br />
Right clicking on a coverage brings up a menu with the following options: Delete, Duplicate, Rename, Coverage Setup, Attribute Table, the Map To submenu, Transform, Export, and Properties. The Delete, Duplicate, and Rename commands are self explanatory.<br />
<br />
== Coverage Setup ==<br />
The Coverage Setup command brings up the Coverage Setup dialog. This dialog controls the properties that are assigned to feature objects. The feature object properties have been divided into 3 general categories: ''Sources/Sinks/BCs'', ''Areal Properties'', and ''Observation Points''. Under the ''Sources/Sinks/BCs'' the user can select which source/sinks he would like to include in the coverage (like wells, rivers, drains, etc). ''Areal Properties'' includes recharge, ET, hydraulic conductivity, and other properties that are assigned to polygonal zones. ''Observation Points'' control which data sets have associated observation data.<br />
<br />
The ''Coverage type'' is used for WASH123D conceptual models to set the coverage to be a 3D or a 2D coverage.<br />
<br />
The ''Default layer range'' is used with MODFLOW conceptual models to default the "from layer"/"to layer" assignments for boundary conditions.<br />
<br />
The ''Use to define model boundary'' toggle is used with MODFLOW and MODAEM. This means that the polygons in this coverage are used to define the active area of the model.<br />
<br />
===3D grid layer option for obs. pts===<br />
The ''3D grid layer option for obs. pts.'' is used to set the input option for observations associated with MODFLOW conceptual models. Three options are available for determining which layer the observation point will be located:<br />
<br />
*by z location - When the "by z location" option is selected, the computed value for the observation point (that will be compared with the observed value) will be taken from the cell that corresponds with the elevation value assigned to the observation point.<br />
<br />
*by layer number - If you select the "by layer number" option in the coverage setup, the computed value will be taken from the cell that corresponds to the layer that is specified in the observation point coverage properties.<br />
<br />
*Use well screen - Use this option if you are using a well with a screen.<br />
<br />
The ''Default elevation'' field can be used to define the initial Z elevation of new objects created in a coverage. By assigning a different elevation to each of the coverages, the coverages can be displayed as a stack of layers in oblique view.<br />
<br />
== Feature Object Attribute Table ==<br />
All feature object properties are edited using a single spreadsheet. This makes it possible to cut and paste feature object data using the clipboard and it makes it easier to edit entire columns of data at once. Filters at the top of the dialog control what type of objects are displayed.<br />
<br />
== Map To Submenu ==<br />
Coverages can be mapped to other geometric objects or Numerical models by selecting the corresponding command from the Map to Submenu.<br />
<br />
==''Related Links''==<br />
<br />
[[GMS:Conceptual Models|Conceptual Models]]<br />
<br />
[[GMS:Feature Objects|Feature Objects]]<br />
<br />
{{Navbox GMS}}</div>Woodhttps://www.xmswiki.com/index.php?title=GMS:Coverages&diff=34087GMS:Coverages2011-06-01T14:11:19Z<p>Wood: /* Feature Object Attribute Table */</p>
<hr />
<div>{{Map links}}<br />
[[GMS:Feature Objects|Feature Objects]] in the Map module are grouped into coverages. Coverages are grouped into [[GMS:Conceptual Models|conceptual models]].<br />
<br />
A coverage is similar to a layer in a CAD drawing. Each coverage represents a particular set of information. For example, one coverage could be used to define recharge zones and another coverage could be used to define zones of hydraulic conductivity. These objects could not be included in a single coverage since polygons within a coverage are not allowed to overlap and recharge zones will typically overlap hydraulic conductivity zones.<br />
<br />
Coverages are managed using the [[GMS:The GMS Screen|Project Explorer]]. Coverages are organized below conceptual models. When GMS is first launched, no coverage exists. If no coverage exists and the user creates [[GMS:Feature Objects|feature objects]] then a new coverage will automatically be created. When multiple coverages are created, one coverage is designated the "active" coverage. New feature objects are always added to the active coverage and only objects in the active coverage can be edited. The figure below shows several coverages in the [[GMS:Project Explorer|Project Explorer]]. The active coverage is displayed with a color icon and bold text. A coverage is made the active coverage by selecting it from the [[GMS:Project Explorer|Project Explorer]]. In some cases it is useful to hide some or all of the coverages. The visibility of a coverage is controlled using the check box next to the coverage in the [[GMS:Project Explorer|Project Explorer]].<br />
<br />
A new coverage can be created by right-clicking on a folder or conceptual model and selecting the '''''New Coverage''''' command in the pop-up menu. <br />
<br />
[[Image:Tree_Map.gif]]<br />
<br />
Right clicking on a coverage brings up a menu with the following options: Delete, Duplicate, Rename, Coverage Setup, Attribute Table, the Map To submenu, Transform, Export, and Properties. The Delete, Duplicate, and Rename commands are self explanatory.<br />
<br />
== Coverage Setup ==<br />
The Coverage Setup command brings up the Coverage Setup dialog. This dialog controls the properties that are assigned to feature objects. The feature object properties have been divided into 3 general categories: ''Sources/Sinks/BCs'', ''Areal Properties'', and ''Observation Points''. Under the ''Sources/Sinks/BCs'' the user can select which source/sinks he would like to include in the coverage (like wells, rivers, drains, etc). ''Areal Properties'' includes recharge, ET, hydraulic conductivity, and other properties that are assigned to polygonal zones. ''Observation Points'' control which data sets have associated observation data.<br />
<br />
The ''Coverage type'' is used for WASH123D conceptual models to set the coverage to be a 3D or a 2D coverage.<br />
<br />
The ''Default layer range'' is used with MODFLOW conceptual models to default the "from layer"/"to layer" assignments for boundary conditions.<br />
<br />
The ''Use to define model boundary'' toggle is used with MODFLOW and MODAEM. This means that the polygons in this coverage are used to define the active area of the model.<br />
<br />
===3D grid layer option for obs. pts===<br />
The ''3D grid layer option for obs. pts.'' is used to set the input option for observations associated with MODFLOW conceptual models. Three options are available for determining which layer the observation point will be located:<br />
<br />
*by z location - When the "by z location" option is selected, the computed value for the observation point (that will be compared with the observed value) will be taken from the cell that corresponds with the elevation value assigned to the observation point.<br />
<br />
*by layer number - If you select the "by layer number" option in the coverage setup, the computed value will be taken from the cell that corresponds to the layer that is specified in the observation point coverage properties.<br />
<br />
*Use well screen - Use this option if you are using a well with a screen.<br />
<br />
The ''Default elevation'' field can be used to define the initial Z elevation of new objects created in a coverage. By assigning a different elevation to each of the coverages, the coverages can be displayed as a stack of layers in oblique view.<br />
<br />
== Feature Object Attribute Table ==<br />
All feature object properties are edited using a single spreadsheet. This makes it possible to cut and paste feature object data using the clipboard and it makes it easier to edit entire columns of data at once. Filters at the top of the dialog control what type of objects are displayed.<br />
<br />
=== Map To Submenu ===<br />
Coverages can be mapped to other geometric objects or Numerical models by selecting the corresponding command from the Map to Submenu.<br />
<br />
==''Related Links''==<br />
<br />
[[GMS:Conceptual Models|Conceptual Models]]<br />
<br />
[[GMS:Feature Objects|Feature Objects]]<br />
<br />
{{Navbox GMS}}</div>Woodhttps://www.xmswiki.com/index.php?title=GMS:Coverages&diff=34086GMS:Coverages2011-06-01T14:10:36Z<p>Wood: /* Coverage Setup */</p>
<hr />
<div>{{Map links}}<br />
[[GMS:Feature Objects|Feature Objects]] in the Map module are grouped into coverages. Coverages are grouped into [[GMS:Conceptual Models|conceptual models]].<br />
<br />
A coverage is similar to a layer in a CAD drawing. Each coverage represents a particular set of information. For example, one coverage could be used to define recharge zones and another coverage could be used to define zones of hydraulic conductivity. These objects could not be included in a single coverage since polygons within a coverage are not allowed to overlap and recharge zones will typically overlap hydraulic conductivity zones.<br />
<br />
Coverages are managed using the [[GMS:The GMS Screen|Project Explorer]]. Coverages are organized below conceptual models. When GMS is first launched, no coverage exists. If no coverage exists and the user creates [[GMS:Feature Objects|feature objects]] then a new coverage will automatically be created. When multiple coverages are created, one coverage is designated the "active" coverage. New feature objects are always added to the active coverage and only objects in the active coverage can be edited. The figure below shows several coverages in the [[GMS:Project Explorer|Project Explorer]]. The active coverage is displayed with a color icon and bold text. A coverage is made the active coverage by selecting it from the [[GMS:Project Explorer|Project Explorer]]. In some cases it is useful to hide some or all of the coverages. The visibility of a coverage is controlled using the check box next to the coverage in the [[GMS:Project Explorer|Project Explorer]].<br />
<br />
A new coverage can be created by right-clicking on a folder or conceptual model and selecting the '''''New Coverage''''' command in the pop-up menu. <br />
<br />
[[Image:Tree_Map.gif]]<br />
<br />
Right clicking on a coverage brings up a menu with the following options: Delete, Duplicate, Rename, Coverage Setup, Attribute Table, the Map To submenu, Transform, Export, and Properties. The Delete, Duplicate, and Rename commands are self explanatory.<br />
<br />
== Coverage Setup ==<br />
The Coverage Setup command brings up the Coverage Setup dialog. This dialog controls the properties that are assigned to feature objects. The feature object properties have been divided into 3 general categories: ''Sources/Sinks/BCs'', ''Areal Properties'', and ''Observation Points''. Under the ''Sources/Sinks/BCs'' the user can select which source/sinks he would like to include in the coverage (like wells, rivers, drains, etc). ''Areal Properties'' includes recharge, ET, hydraulic conductivity, and other properties that are assigned to polygonal zones. ''Observation Points'' control which data sets have associated observation data.<br />
<br />
The ''Coverage type'' is used for WASH123D conceptual models to set the coverage to be a 3D or a 2D coverage.<br />
<br />
The ''Default layer range'' is used with MODFLOW conceptual models to default the "from layer"/"to layer" assignments for boundary conditions.<br />
<br />
The ''Use to define model boundary'' toggle is used with MODFLOW and MODAEM. This means that the polygons in this coverage are used to define the active area of the model.<br />
<br />
===3D grid layer option for obs. pts===<br />
The ''3D grid layer option for obs. pts.'' is used to set the input option for observations associated with MODFLOW conceptual models. Three options are available for determining which layer the observation point will be located:<br />
<br />
*by z location - When the "by z location" option is selected, the computed value for the observation point (that will be compared with the observed value) will be taken from the cell that corresponds with the elevation value assigned to the observation point.<br />
<br />
*by layer number - If you select the "by layer number" option in the coverage setup, the computed value will be taken from the cell that corresponds to the layer that is specified in the observation point coverage properties.<br />
<br />
*Use well screen - Use this option if you are using a well with a screen.<br />
<br />
The ''Default elevation'' field can be used to define the initial Z elevation of new objects created in a coverage. By assigning a different elevation to each of the coverages, the coverages can be displayed as a stack of layers in oblique view.<br />
<br />
=== Feature Object Attribute Table ===<br />
All feature object properties are edited using a single spreadsheet. This makes it possible to cut and paste feature object data using the clipboard and it makes it easier to edit entire columns of data at once. Filters at the top of the dialog control what type of objects are displayed.<br />
<br />
=== Map To Submenu ===<br />
Coverages can be mapped to other geometric objects or Numerical models by selecting the corresponding command from the Map to Submenu.<br />
<br />
==''Related Links''==<br />
<br />
[[GMS:Conceptual Models|Conceptual Models]]<br />
<br />
[[GMS:Feature Objects|Feature Objects]]<br />
<br />
{{Navbox GMS}}</div>Woodhttps://www.xmswiki.com/index.php?title=GMS:Coverages&diff=34085GMS:Coverages2011-06-01T14:10:27Z<p>Wood: /* 3D grid layer option for obs. pts */</p>
<hr />
<div>{{Map links}}<br />
[[GMS:Feature Objects|Feature Objects]] in the Map module are grouped into coverages. Coverages are grouped into [[GMS:Conceptual Models|conceptual models]].<br />
<br />
A coverage is similar to a layer in a CAD drawing. Each coverage represents a particular set of information. For example, one coverage could be used to define recharge zones and another coverage could be used to define zones of hydraulic conductivity. These objects could not be included in a single coverage since polygons within a coverage are not allowed to overlap and recharge zones will typically overlap hydraulic conductivity zones.<br />
<br />
Coverages are managed using the [[GMS:The GMS Screen|Project Explorer]]. Coverages are organized below conceptual models. When GMS is first launched, no coverage exists. If no coverage exists and the user creates [[GMS:Feature Objects|feature objects]] then a new coverage will automatically be created. When multiple coverages are created, one coverage is designated the "active" coverage. New feature objects are always added to the active coverage and only objects in the active coverage can be edited. The figure below shows several coverages in the [[GMS:Project Explorer|Project Explorer]]. The active coverage is displayed with a color icon and bold text. A coverage is made the active coverage by selecting it from the [[GMS:Project Explorer|Project Explorer]]. In some cases it is useful to hide some or all of the coverages. The visibility of a coverage is controlled using the check box next to the coverage in the [[GMS:Project Explorer|Project Explorer]].<br />
<br />
A new coverage can be created by right-clicking on a folder or conceptual model and selecting the '''''New Coverage''''' command in the pop-up menu. <br />
<br />
[[Image:Tree_Map.gif]]<br />
<br />
Right clicking on a coverage brings up a menu with the following options: Delete, Duplicate, Rename, Coverage Setup, Attribute Table, the Map To submenu, Transform, Export, and Properties. The Delete, Duplicate, and Rename commands are self explanatory.<br />
<br />
=== Coverage Setup ===<br />
The Coverage Setup command brings up the Coverage Setup dialog. This dialog controls the properties that are assigned to feature objects. The feature object properties have been divided into 3 general categories: ''Sources/Sinks/BCs'', ''Areal Properties'', and ''Observation Points''. Under the ''Sources/Sinks/BCs'' the user can select which source/sinks he would like to include in the coverage (like wells, rivers, drains, etc). ''Areal Properties'' includes recharge, ET, hydraulic conductivity, and other properties that are assigned to polygonal zones. ''Observation Points'' control which data sets have associated observation data.<br />
<br />
The ''Coverage type'' is used for WASH123D conceptual models to set the coverage to be a 3D or a 2D coverage.<br />
<br />
The ''Default layer range'' is used with MODFLOW conceptual models to default the "from layer"/"to layer" assignments for boundary conditions.<br />
<br />
The ''Use to define model boundary'' toggle is used with MODFLOW and MODAEM. This means that the polygons in this coverage are used to define the active area of the model.<br />
<br />
===3D grid layer option for obs. pts===<br />
The ''3D grid layer option for obs. pts.'' is used to set the input option for observations associated with MODFLOW conceptual models. Three options are available for determining which layer the observation point will be located:<br />
<br />
*by z location - When the "by z location" option is selected, the computed value for the observation point (that will be compared with the observed value) will be taken from the cell that corresponds with the elevation value assigned to the observation point.<br />
<br />
*by layer number - If you select the "by layer number" option in the coverage setup, the computed value will be taken from the cell that corresponds to the layer that is specified in the observation point coverage properties.<br />
<br />
*Use well screen - Use this option if you are using a well with a screen.<br />
<br />
The ''Default elevation'' field can be used to define the initial Z elevation of new objects created in a coverage. By assigning a different elevation to each of the coverages, the coverages can be displayed as a stack of layers in oblique view.<br />
<br />
=== Feature Object Attribute Table ===<br />
All feature object properties are edited using a single spreadsheet. This makes it possible to cut and paste feature object data using the clipboard and it makes it easier to edit entire columns of data at once. Filters at the top of the dialog control what type of objects are displayed.<br />
<br />
=== Map To Submenu ===<br />
Coverages can be mapped to other geometric objects or Numerical models by selecting the corresponding command from the Map to Submenu.<br />
<br />
==''Related Links''==<br />
<br />
[[GMS:Conceptual Models|Conceptual Models]]<br />
<br />
[[GMS:Feature Objects|Feature Objects]]<br />
<br />
{{Navbox GMS}}</div>Woodhttps://www.xmswiki.com/index.php?title=GMS:Coverages&diff=34084GMS:Coverages2011-06-01T14:09:51Z<p>Wood: /* Coverage Setup */</p>
<hr />
<div>{{Map links}}<br />
[[GMS:Feature Objects|Feature Objects]] in the Map module are grouped into coverages. Coverages are grouped into [[GMS:Conceptual Models|conceptual models]].<br />
<br />
A coverage is similar to a layer in a CAD drawing. Each coverage represents a particular set of information. For example, one coverage could be used to define recharge zones and another coverage could be used to define zones of hydraulic conductivity. These objects could not be included in a single coverage since polygons within a coverage are not allowed to overlap and recharge zones will typically overlap hydraulic conductivity zones.<br />
<br />
Coverages are managed using the [[GMS:The GMS Screen|Project Explorer]]. Coverages are organized below conceptual models. When GMS is first launched, no coverage exists. If no coverage exists and the user creates [[GMS:Feature Objects|feature objects]] then a new coverage will automatically be created. When multiple coverages are created, one coverage is designated the "active" coverage. New feature objects are always added to the active coverage and only objects in the active coverage can be edited. The figure below shows several coverages in the [[GMS:Project Explorer|Project Explorer]]. The active coverage is displayed with a color icon and bold text. A coverage is made the active coverage by selecting it from the [[GMS:Project Explorer|Project Explorer]]. In some cases it is useful to hide some or all of the coverages. The visibility of a coverage is controlled using the check box next to the coverage in the [[GMS:Project Explorer|Project Explorer]].<br />
<br />
A new coverage can be created by right-clicking on a folder or conceptual model and selecting the '''''New Coverage''''' command in the pop-up menu. <br />
<br />
[[Image:Tree_Map.gif]]<br />
<br />
Right clicking on a coverage brings up a menu with the following options: Delete, Duplicate, Rename, Coverage Setup, Attribute Table, the Map To submenu, Transform, Export, and Properties. The Delete, Duplicate, and Rename commands are self explanatory.<br />
<br />
=== Coverage Setup ===<br />
The Coverage Setup command brings up the Coverage Setup dialog. This dialog controls the properties that are assigned to feature objects. The feature object properties have been divided into 3 general categories: ''Sources/Sinks/BCs'', ''Areal Properties'', and ''Observation Points''. Under the ''Sources/Sinks/BCs'' the user can select which source/sinks he would like to include in the coverage (like wells, rivers, drains, etc). ''Areal Properties'' includes recharge, ET, hydraulic conductivity, and other properties that are assigned to polygonal zones. ''Observation Points'' control which data sets have associated observation data.<br />
<br />
The ''Coverage type'' is used for WASH123D conceptual models to set the coverage to be a 3D or a 2D coverage.<br />
<br />
The ''Default layer range'' is used with MODFLOW conceptual models to default the "from layer"/"to layer" assignments for boundary conditions.<br />
<br />
The ''Use to define model boundary'' toggle is used with MODFLOW and MODAEM. This means that the polygons in this coverage are used to define the active area of the model.<br />
<br />
==3D grid layer option for obs. pts==<br />
The ''3D grid layer option for obs. pts.'' is used to set the input option for observations associated with MODFLOW conceptual models. Three options are available for determining which layer the observation point will be located:<br />
<br />
*by z location - When the "by z location" option is selected, the computed value for the observation point (that will be compared with the observed value) will be taken from the cell that corresponds with the elevation value assigned to the observation point.<br />
<br />
*by layer number - If you select the "by layer number" option in the coverage setup, the computed value will be taken from the cell that corresponds to the layer that is specified in the observation point coverage properties.<br />
<br />
*Use well screen - Use this option if you are using a well with a screen.<br />
<br />
The ''Default elevation'' field can be used to define the initial Z elevation of new objects created in a coverage. By assigning a different elevation to each of the coverages, the coverages can be displayed as a stack of layers in oblique view.<br />
<br />
=== Feature Object Attribute Table ===<br />
All feature object properties are edited using a single spreadsheet. This makes it possible to cut and paste feature object data using the clipboard and it makes it easier to edit entire columns of data at once. Filters at the top of the dialog control what type of objects are displayed.<br />
<br />
=== Map To Submenu ===<br />
Coverages can be mapped to other geometric objects or Numerical models by selecting the corresponding command from the Map to Submenu.<br />
<br />
<br />
==''Related Links''==<br />
<br />
[[GMS:Conceptual Models|Conceptual Models]]<br />
<br />
[[GMS:Feature Objects|Feature Objects]]<br />
<br />
{{Navbox GMS}}</div>Woodhttps://www.xmswiki.com/index.php?title=System_Requirements&diff=33910System Requirements2011-05-17T14:34:39Z<p>Wood: /* Windows XP */</p>
<hr />
<div>System requirements for GMS, SMS and WMS.<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''' || 1 GB || 4 GB or greater<br />
|-<br />
| '''CPU'''<br />
|colspan="2"| XMS software is CPU intensive. We recommend the fastest CPU your budget allows. A multi-core CPU may be useful for multi-tasking while XMS is running. However, XMS software does not use more than a single core at this time, so a faster dual core '''may''' provide better performance than a slower quad core CPU.<br />
|-<br />
| '''Hard Disk Free Space'''<br />
|| 300 MB || 300 MB or greater<br />
|-<br />
| '''Graphics Card'''<br />
| '''For all display features to be enabled, OpenGL 1.5 must be supported.'''<br />
| We recommend [http://en.wikipedia.org/wiki/NVIDIA_Quadro nVidia Quadro based graphics cards] because of their superb OpenGL support. The use of a dedicated graphics card is strongly recommended. Integrated graphics cards are often problematic.<br />
|-<br />
| '''Minimum Resolution'''<br />
||1024x768<br />
||1024x768 or greater<br />
|}<br />
<br />
== Windows Vista<ref>Windows Vista is supported in GMS 7.0, SMS 10.0, WMS 8.1 and greater versions only.</ref> ==<br />
Windows Vista is supported in GMS 7.0, SMS 10.0, WMS 8.1 and greater versions only.<br />
<br />
{| class="wikitable"<br />
! Component !! Minimum Required !! Recommended<br />
|-<br />
| '''RAM''' || 1 GB || 4 GB or greater<br />
|-<br />
| '''CPU'''<br />
|colspan="2"| XMS software is CPU intensive. We recommend the fastest CPU your budget allows. A multi-core CPU may be useful for multi-tasking while XMS is running. However, XMS software does not use more than a single core at this time, so a faster dual core '''may''' provide better performance than a slower quad core CPU.<br />
|-<br />
| '''Hard Disk Free Space'''<br />
|| 300 MB || 300 MB or greater<br />
|-<br />
| '''Graphics Card'''<br />
| '''For all display features to be enabled, OpenGL 1.5 must be supported.'''<br />
| We recommend [http://en.wikipedia.org/wiki/NVIDIA_Quadro nVidia Quadro based graphics cards] because of their superb OpenGL support. The use of a dedicated graphics card is strongly recommended. Integrated graphics cards are often problematic.<br />
|-<br />
| '''Minimum Resolution'''<br />
||1024x768<br />
||1024x768 or greater<br />
|}<br />
<br />
== Windows XP ==<br />
Windows XP is recommended for GMS 7.0, SMS 10.0, WMS 8.1 and greater versions.<br />
<br />
{| class="wikitable"<br />
! Component !! Minimum Required !! Recommended<br />
|-<br />
| '''RAM''' || 512 MB || 2 GB or greater<br />
|-<br />
| '''CPU'''<br />
|colspan="2"| XMS software is CPU intensive. We recommend the fastest CPU your budget allows. A multi-core CPU may be useful for multi-tasking while XMS is running. However, XMS software does not use more than a single core at this time, so a faster dual core '''may''' provide better performance than a slower quad core CPU.<br />
|-<br />
| '''Hard Disk Free Space'''<br />
|| 300 MB<br />
|| 300 MB or greater<br />
|-<br />
| '''Graphics Card'''<br />
| '''For all display features to be enabled, OpenGL 1.5 must be supported.'''<br />
| We recommend [http://en.wikipedia.org/wiki/NVIDIA_Quadro nVidia Quadro based graphics cards] because of their superb OpenGL support. The use of a dedicated graphics card is strongly recommended. Integrated graphics cards are often problematic.<br />
|-<br />
| '''Minimum Resolution'''<br />
||1024x768<br />
||1024x768 or greater<br />
|}<br />
<references/><br />
<br />
== Notes ==<br />
* You may have display problems when running over 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 you continue to experience problems after updating your graphics card drivers, contact [http://www.aquaveo.com/technical-support/ support].<br />
<br />
==Related Topics==<br />
* [[Graphics Card Troubleshooting]]<br />
<br />
== External Links ==<br />
* [http://support.microsoft.com/kb/190900 Description of the DirectX Diagnostic Tool]</div>Woodhttps://www.xmswiki.com/index.php?title=WMS:Quick_Tour_-_DEMs&diff=33802WMS:Quick Tour - DEMs2011-05-03T22:46:27Z<p>Wood: </p>
<hr />
<div>[[Image:wmsquicktour.jpg]]<br />
<br />
Digital elevation models can be used to quickly delineate watershed boundaries. Gridded elevation datasets can be downloaded from the [http://seamless.usgs.gov/website/seamless/viewer.htm National Elevation Dataset (NED)]. This elevation data is available at a resolution of 30-meters for the entire U.S. and some 90-meter world-wide data is also available.<br />
<br />
[[Image:image90.jpg]]<br />
<br />
<br />
[[WMS:Quick Tour - Terrain Data| '''< Previous''']] | [[WMS:Quick Tour - Flow Direction Vectors| ''' Next >''']]</div>Woodhttps://www.xmswiki.com/index.php?title=WMS:NSS&diff=33801WMS:NSS2011-05-03T22:14:40Z<p>Wood: </p>
<hr />
<div>WMS includes an interface to the National Streamflow Statistics Program (NSS). The NSS program is a compilation of all the current statewide and metropolitan area regression equations. The NSS interface in WMS version 8.1 and later uses the same database as the Windows version of the NSS program (released in 2006) which supersedes all previous versions of the NFF program such as the windows version of NFF (released in 2003) and the 1993 derivative used in previous versions of WMS.<br />
<br />
You may need to install the latest version of the NSS program from the following web site to get the program to work:<br />
<br />
http://water.usgs.gov/software/NSS/<br />
<br />
The regression equations are a result of years of effort by the United States Geological Survey (USGS) to develop regional regression equations for estimating flood magnitude and frequency of ungaged watersheds. The USGS, in cooperation with the Federal Highway Administration and the Federal Emergency Management Agency compiled all the regression equations into a single database file. This database file is the basis of the NFF program, which can be used to guide the user through the input required to compute peak flows for different frequencies using the database of state by state regression equations.<br />
<br />
The NSS interface in WMS provides a windows based, graphical user interface to the same database of regression equations. The entire program is run from a single dialog. Further, if a digital terrain model is available for the study area, all of the geometric parameters required for the regression equations are automatically supplied as the individual equations are specified. These parameters include area, slope, elevation, distances, and others. The GIS overlay command can be used to compute other variables such as forest cover, lake cover, etc.<br />
<br />
The NSS equations are useful for estimating a peak flood discharge and typical flood hydrograph for a given recurrence interval of an unregulated rural or urban watershed. These techniques should be useful to engineers and hydrologists for planning and design purposes. <br />
<br />
WMS uses the DLL's that are part of the USGS Windows based version of the NSS program. The USGS program does not include any kind of GIS component, but if you wish to run the NSS outside of WMS you can still use WMS to determine the necessary input. Complete documentation on the USGS NSS program, including specific information for each state can be found on line at the following USGS website:<br />
<br />
http://water.usgs.gov/software/NSS/<br />
<br />
The descriptions for each state are found at the bottom of the above web page.<br />
<br />
<br />
==Related Topics==<br />
* [[WMS:NSS Computing Peak Discharges|Defining an NSS Simulation]]<br />
* [[WMS:Saving and Restoring a Simulation|Saving and Restoring a Simulation]]<br />
* [[WMS:NSS Model Troubleshooting|NSS Model Troubleshooting]]<br />
<br />
<br />
{{WMSMain}}</div>Woodhttps://www.xmswiki.com/index.php?title=SMS:LTEA&diff=33796SMS:LTEA2011-05-03T15:55:18Z<p>Wood: </p>
<hr />
<div>Linear Truncation Error Analysis (LTEA) was initially presented by Dr. Scott C. Hagen as part of his doctoral research at Notre Dame. Development has continued on the methodology at the University of Central Florida. The LTEA algorithm performs analysis on an existing [[SMS:ADCIRC|ADCIRC]] mesh and its solution to help quantify the error associated with the mesh. Normally, this [[SMS:ADCIRC|ADCIRC]] solution is taken from a "linear ADCIRC" run. This type of run is used to make the process faster and to simplify the LTEA algorithm applied to the unstructured mesh. A second phase of the LTEA process uses the error values at each node to create a relative size function covering the domain called DelX.<br />
<br />
== The LTEA Toolbox ==<br />
SMS includes a graphical interface that allows the user to use the LTEA theory to guide the generation of a finite element mesh. The tool requires two inputs which must be loaded into SMS. These include:<br />
<br />
* A bathymetry scatter set.<br />
* An ADCIRC coverage having at least one polygon with the boundary conditions assigned.<br />
<br />
If you wish to start the mesh generation process from an existing ADCIRC mesh, you must convert the mesh to both a scatter set and ADCIRC conceptual model, Right clicking on the mesh in the project explorer gives access to commands to perform the basic conversion. The conceptual model must be defined on the arcs created in this way.<br />
<br />
The toolbox is accessed through the "Mesh Generation Toolbox..." from the ADCIRC menu in the Mesh Module. From the dialog that appears, select the LTEA option and click Run. The steps that follow include:<br />
<br />
* Step 1: Linear Run Mesh generation. In this step the user must specify the scatter set and conceptual model to be used for mesh generation. This step generates a basic mesh from the conceptual model to perform a linear run. This mesh may be saved for future reference. If a mesh already exists that is suitable for the linear run, the option to generate a linear run mesh should be turned off.<br />
<br />
* Step 2 - Linear ADCIRC Run. In this step, the toolbox runs ADCIRC in linear mode with the M2 tidal constituent and performs an harmonic analysis on the result. If a run of ADCIRC and harmonic analysis has already been performed, the option to use existing solution data becomes available. In this case the user must specify the data sets that contain the output of the harmonic analysis. If this is not the initial pass through the mesh generation toolbox, or if the user wants to generate a "Size guideline function" from anaother source, it may be provided. If this is the case, the linear run as well as the next step "LTEA calculations" are bypassed.<br />
<br />
* Step 3 - LTEA Analysis. The LTEA algorithm processes the harmonic analysis output and determines the relative error due to node spacing throughout the domain. It then computes a size guideline for generating a new mesh. The guideline is a dataset (a value for each node of the linear run mesh) named "DelX". The user must instruct LTEA to only perform calcualtions on the interior (no partial molecule) or to approximate the LTEA calculations right up to the boundary. (Note: extra controls exist in the dialog for tools that are under development.)<br />
<br />
* Step 4 - Generate Final Mesh. At this point, SMS has almost all the information required for mesh generation. The user must specify the target size of desired mesh as a number of nodes and a tolerable deviation from that target. The acceptable size transitions are also specified here (see the [[SMS:Smooth Size Data Set (Data Menu)|Smooth Size Data Set article]] for a description of this).<br />
<br />
The tool can be used repetitively to generate various meshes of the same area with varying resolution. In these cases, the first three steps should be bypassed by entering the input data in step 1 and the "DelX" function in step 3 and then proceeding to step 4.<br />
<br />
== Case Studies / Sample Problems ==<br />
=== [[SMS:Tutorials|Tutorials]] ===<br />
The following [[SMS:Tutorials|tutorials]] may be helpful for learning to use LTEA in SMS:<br />
<br />
* Models Section<br />
** ADCIRC LTEA - Uses LTEA to mesh Shinnecock bay and the area around it along Long Island, NY<br />
<br />
=== American Samoa ===<br />
: The following images illustrate the results of the LTEA toolbox applied to a domain around American Samoa. The first pair of images illustrate a mesh generated for the domain using the paving method. Density at the coastline was controlled by redistributing the vertices on the arcs representing the coastline and the density varied to a larger ocean boundary density. This mesh consists of 22,576 nodes (43,055 elements). The other images illustrate the varying resolution generated by LTEA to result in constant error with target mesh sizes of 24,000 nodes and 12,000 nodes respectively. The LTEA toolbox created meshes with 24,078 nodes (45,929 elements) and 12,029 nodes ( 22,543 elements).<br />
[[Image:AmericanSamoaLT12K.jpg|200px|right|12000 Node Mesh]]<br />
[[Image:AmericanSamoaPaved.jpg|200px|left|Paved Mesh]]<br />
[[Image:AmericanSamoaLT24K.jpg|200px|center|24000 Node Mesh]]<br />
[[Image:AmericanSamoaLT12K_Zoom.jpg|200px|right|12000 Node Detail]]<br />
[[Image:AmericanSamoaPaved_Zoom.jpg|200px|left|Paved Mesh Detail]]<br />
[[Image:AmericanSamoaLT24K_Zoom.jpg|200px|center|24000 Node Detail]]<br />
<br />
: These images illustrate the redistribution of density to increase the density in areas that require additional detail for solution variations, or to reduce the number of nodes in the mesh.<br />
<br />
=== Glacier Bay Alaska ===<br />
: The case of [http://water.engr.psu.edu/hill/research/glba/default.stm Glacier Bay Alaska], by [http://water.engr.psu.edu/hill/default.stm Dave F. Hill's] research group, poses another problem for the LTEA toolbox. This case includes two ocean boundaries. The figures below show three meshes generated for this case and illustrate the large variation in node density that can be produced by the procedure.<br />
[[Image:GlacierBayImage.jpg|200px|left|Glacier Bay Domain over areal photo]]<br />
[[Image:GlacierBayConceptual.jpg|200px|center|Glacier Bay Domain with second ocean boundary highlighted]]<br />
: This case includes two ocean boundaries. Currently, the LTEA toolbox makes a sometimes erroneous assumption that only one ocean boundary exists. To work around this problem in the current version of SMS, the following steps are required:<br />
* Change the inland ocean boundary to land<br />
* Run the first step of the LTEA toolbox to generate the "Linear Run Mesh" and then "Stop and Run" to that point.<br />
[[Image:GlacierBayLiinear.jpg|200px|left|Linear mesh for Glacier Bay (17,717 nodes)]]<br />
[[Image:LTEA_Harmonics.jpg|250px|center|Harmonic data sets for LTEA analysis]]<br />
* Outside of the toolbox, change the second ocean boundary to ocean on the linear run mesh and run a linear run of ADCIRC with harmonic analysis turned on. This will generate the data sets for LTEA calcuations.<br />
* Relaunch the toolbox and select the datasets from the linear run to guide the mesh generation process.<br />
[[Image:GlacierBay30K.jpg|250px|right|30000 Node Mesh (10,072 nodes)]]<br />
[[Image:GlacierBay10K.jpg|250px|left|20000 Node Mesh (19,929 nodes)]]<br />
[[Image:GlacierBay20K.jpg|250px|center|20000 Node Mesh (30,227 nodes)]]<br />
<br />
== Related Topics ==<br />
* [[SMS:ADCIRC|ADCIRC]]<br />
* [[SMS:LTEACD|LTEACD]]<br />
* [[SMS:Steering|Steering]]<br />
<br />
== External Links ==<br />
* [http://champs.cecs.ucf.edu/ Coastal Hydroscience Analysis, Modeling & Predictive Simulations Laboratory (CHAMPS Lab)]<br />
* [http://contentdm.lib.byu.edu/ETD/image/etd1550.pdf Dec 2006 Automatic, unstructured mesh generation for 2D, shelf-based tidal models]<br />
* [http://champs.cecs.ucf.edu/Publications/Refereed/IJCFD_Hagen_et_al_2006.pdf Sep 2006 Automatic, unstructured mesh generation for tidal calculations in a large domain]<br />
* [http://poc.omp.obs-mip.fr/DOCUMENTS/t-ugo/res.pdf Sep 2006 Resolution Issues in Numerical Models of Oceanic and Coastal Circulation]<br />
* [http://www.nd.edu/~adcirc/pubs/IJNMF-hwkh-2001-PUBL.pdf 2001 Two-dimensional, unstructured mesh generation for tidal models]<br />
* [http://www.nd.edu/~adcirc/pubs/ijnmf-hwk-2000-PUBL.pdf 2000 One-dimensional finite element grids based on a localized truncation error analysis]<br />
* [http://kfki.baw.de/conferences/ICHE/1998-Cottbus/45.pdf 1998 2D Finite Element Grids Based on a Localized Truncation Error Analysis]<br />
* [http://water.engr.psu.edu/hill/research/glba/default.stm Glacier Bay Test Case by Dave F. Hill]<br />
<br />
{{Template:SMSMain}}<br />
{{stub}}</div>Woodhttps://www.xmswiki.com/index.php?title=GMS:Importing_MODFLOW_Files&diff=33699GMS:Importing MODFLOW Files2011-04-12T19:17:09Z<p>Wood: /* Groundwater Vistas */</p>
<hr />
<div>{{MODFLOW Links}}<br />
<br />
GMS imports standard MODFLOW 88, 96, 2000 and 2005<ref name="GMS8">Supported starting at GMS version 8.0</ref> files. Currently GMS only supports MODFLOW 2000 and 2005<ref name="GMS8"/> so other versions will be converted to MODFLOW 2000 or 2005<ref name="GMS8"/>. If GMS created the MODFLOW simulation then you should open the corresponding GMS project file (.gpr). If there is no GMS project file, you can import the MODFLOW simulation into GMS as described below. GMS will create a new copy of the imported MODFLOW simulation in its own modified MODFLOW file format. Native MODFLOW files can be exported from GMS.<br />
<br />
==GMS modified MODFLOW file format==<br />
GMS uses it's own modified MODFLOW file format. MODFLOW simulations imported into GMS will be saved using this file format. See [[GMS:MODFLOW with HDF5|MODFLOW with HDF5]] for more information. GMS can [[GMS:MODFLOW_with_HDF5#Exporting_Native_MODFLOW_Files|export MODFLOW models in the standard MODFLOW format]].<br />
<br />
==How to import a MODFLOW model into GMS==<br />
You can follow these steps when importing a MODFLOW simulation into GMS.<br />
<br />
# Were the MODFLOW files created by GMS?<br />
#* Yes<br />
#*: If the files were created by GMS, and you have the GMS project file (.gpr), you should just read that into GMS using the standard ''File|Open'' command. If you don't have the .gpr file, you should import the MODFLOW model into GMS by opening the "super file" (.mfs) using the standard ''File|Open'' command. The super file is a non-standard file that GMS creates along with the standard MODFLOW files. If you don't have a super file, proceed to step 2 below.<br />
#* No<br />
#*: Proceed to step 2 below.<br />
#* Don't know<br />
#*: If you have a .gpr file or a .mfs file, then it's almost certain that the files were created by GMS. If you don't have these files, proceed to step 2 below.<br />
# Determine whether your model is MODFLOW 88, 96 or 2000. If you are unsure, refer to the section below entitled [[#Determining the MODFLOW version|Determining the MODFLOW version]] which describes each one.<br />
#* MODFLOW 88<br />
#*: Read the basic package file into GMS (using the standard ''File|Open'' dialog). GMS will attempt to import all the other files.<br />
#* MODFLOW 96<br />
#*: Read the name file.<br />
#* MODFLOW 2000<br />
#*: Read the name file.<br />
<br />
===Troubleshooting===<br />
If you are having trouble reading the files into GMS, first verify that MODFLOW can read the files by launching MODFLOW at a command prompt and giving it the name of the file to read. If MODFLOW can read the files but GMS cannot, it may be because you are attempting to import packages which GMS does not support ([[GMS:MODFLOW Packages Supported in GMS|Packages Supported in GMS]]), or because GMS has stricter limitations on file formats which it can read. For example, GMS is unable to import MODFLOW files that contain single quotes ( ' ). Replace single quotes ( ' ) with double quotes ( " ) or simply remove the quotes entirely.<br />
<br />
Contact [http://www.aquaveo.com/technical-support/ tech support] for additional help.<br />
<br />
==Determining the MODFLOW version==<br />
===MODFLOW 88===<br />
To tell if a file is MODFLOW 88 open up the basic package file as a text file. GMS uses *.bas as the extension for this file. The file should appear something like the figure below.<br />
<br />
<pre><br />
Heading 1<br />
Heading 2<br />
3 23 17 1 4<br />
11 13 14 15 0 0 16 0 0 0 0 10 12 0 0 0 0 0 0 0 0 29 0 0<br />
0 0<br />
1 1 (17I3) 0<br />
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1<br />
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1<br />
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1<br />
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1<br />
</pre><br />
<br />
For a MODFLOW 88 file the third line of the basic package file will include an IUNIT array with 24 slots. There may also be an IUNIT array with only 12 slots, if so just ok the warning GMS gives. These slots include the unit numbers for packages included in the file. Every number must be unique to its package. If the number does not correspond to a file then the file is an external array which must be matched by the user. If the basic package file includes an IUNIT array as described it is a MODFLOW 88 file.<br />
<br />
To import the MODFLOW 88 file locate the *.mfs file. If there is no *.mfs file then select the *.bas file. Then simply use the ''File|Open'' command to read the file into GMS.<br />
<br />
====More about MODFLOW 88 files====<br />
MODFLOW 88 files have no name (.nam or .mfn) file.<br />
<br />
GMS makes a few assumptions when reading in MODFLOW 88 files:<br />
#All files must have the same prefix.<br />
#:*Example: If the files are named bas.dat, drain.dat, and river.dat they all must be converted to run1.bas, run1.drn, and run1.riv<br />
#All files use the standard GMS suffixes as shown in the table below.<br />
#:*If these are not the suffixes in use, you will need to rename the files.<br />
#IUNIT slots must be standard with standard ID #'s according to MODFLOW documentation.<br />
#It is up to the user to know what external arrays go to which MODFLOW files. Otherwise the files will not be properly read in.<br />
#:*GMS can import external arrays but is unable to import external binary arrays<br />
#MODFLOW 88 files use a fixed format.<br />
<br />
<br />
{| class="wikitable" border="1"<br />
|+ MODFLOW 88 IUNIT Array Positions and Packages<br />
|- align=center<br />
| 1||2||3||4||5||6||7||8||9||10||11||12||13||14||15||16||17||18||19||20<br />
|-<br />
|BCF||WEL||DRN||RIV||EVT|| ||GHB||RCH||SIP||DE4||SOR||OC||PCG||GFD|| ||HFB||RES||STR||IBS||CHD<br />
|}<br />
<br />
{| class="wikitable"<br />
|+ Standard GMS Extensions for MODFLOW 88 files<br />
! Package !! Extension<br />
|-<br />
| BASIC || *.bas<br />
|-<br />
| OUTPUT CONTROL || *.oc<br />
|-<br />
| BCF || *.bcf<br />
|-<br />
| RIVER || *.riv<br />
|-<br />
| DRAIN || *.drn<br />
|-<br />
| WELL || *.wel<br />
|-<br />
| GENERAL HEAD BOUNDARY || *.ghb<br />
|-<br />
| STREAM || *.str<br />
|-<br />
| RECHARGE || *.rch<br />
|-<br />
| EVAPOTRANSPIRATION || *.evt<br />
|-<br />
| STRONGLY IMPLICIT PROCEDURE || *.sip<br />
|-<br />
| SLICE-SUCCESSIVE OVERRELAXATION || *.sor<br />
|}<br />
<br />
===MODFLOW 96===<br />
To tell if model files are in MODFLOW 96 format, open up the basic package file as a text file. For a MODFLOW 96 file the third line of the *.bas file will NOT include an IUNIT array. Instead the third line will say FREE, which means that the data in the file is in free format and each data entry is separated with a space. A 96 file may not contain the FREE line. Instead the line may be blank and the file may be fixed format. This file can be read in just the same using the name file.<br />
<br />
<pre><br />
Heading 1<br />
Heading 2<br />
3 23 17 1 4<br />
FREE<br />
0 0<br />
INTERNAL 1 (free) 0 "Ibound Layer 1"<br />
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 <br />
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 <br />
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 <br />
</pre><br />
<br />
If the basic package file says FREE as described it is a MODFLOW 96 file. A name file (typically with a *.mfn or *.nam extension) should also exist. If one does not it must be created as described below.<br />
<br />
To open a MODFLOW 96 file locate the name file and use the ''File|Open'' command to read the file into GMS.<br />
<br />
====More about MODFLOW 96 files====<br />
MODFLOW 96 files use a name file to identify the packages files. This replaces the IUNIT array used in MODFLOW 88. The advantage of it is that the files do not need to all have the same prefix in their name. The name file is laid out as shown below. In the first column the card name is given (see MODFLOW documentation for more information). In the second colum the IUNIT number is given. This number must be unique from all other numbers. The third column gives the file name and as stated does not need to have the same prefix for every package.<br />
<br />
Sample *.mfn file:<br />
LIST 26 "run1.out"<br />
BAS 1 "run1.bas"<br />
BCF 11 "run1.bcf"<br />
OC 10 "run1.oc"<br />
DATA(BINARY) 30 "run1.hed"<br />
DATA(BINARY) 40 "run140.ccf"<br />
PCG 12 "run1.pcg"<br />
RIV 15 "run1.riv"<br />
WEL 13 "run1.wel"<br />
RCH 20 "run1.rch"<br />
MT3D 29 "run1.hff"<br />
<br />
===MODFLOW 2000 & 2005<ref name="GMS8"/>===<br />
Like the MODFLOW 96 files, MF2K and MF2K5<ref name="GMS8"/> use name files rather than an IUNIT array. To know if a file is a MF2K or MF2K5<ref name="GMS8"/> file look for a discretization file (*.dis). If a *.dis file exists then use the ''File|Open'' command and select the name file (*.nam or *.mfn) to read the simulation into GMS.<br />
<br />
Sample *.mfn file:<br />
<pre><br />
# MF2K NAME file<br />
#<br />
# Output Files<br />
GLOBAL 1 "easttex.glo"<br />
LIST 2 "easttex.out"<br />
DATA(BINARY) 30 "easttex.hed"<br />
DATA(BINARY) 40 "easttex.ccf"<br />
LMT6 18 "easttex.lmt"<br />
#<br />
# Obs-Sen-Pes Process Input Files<br />
OBS 50 "easttex.obs"<br />
DROB 54 "easttex.drob"<br />
CHOB 55 "easttex.chob"<br />
ASP 71 "easttex.asp"<br />
#<br />
# Global Input Files<br />
DIS 19 "easttex.dis"<br />
#<br />
# Flow Process Input Files<br />
BAS6 3 "easttex.ba6"<br />
LPF 4 "easttex.lpf"<br />
OC 15 "easttex.oc"<br />
RCH 16 "easttex.rch"<br />
WEL 9 "easttex.wel"<br />
DRN 10 "easttex.drn"<br />
CHD 13 "easttex.chd"<br />
PCG 14 "easttex.pcg"<br />
</pre><br />
<br />
==Changes in GMS 7.0==<br />
{{Version GMS 7.0}}<br />
When GMS 7.0 or later reads a MODFLOW simulation it checks if the simulation files are in the modified GMS format. MODFLOW files created by GMS 6.5 or a later use this format. If the simulation is not in the GMS format then GMS converts it into this format.<br />
<br />
In versions of GMS prior to 7.0, GMS would read the MODFLOW files and do the conversion. Starting with version 7.0, GMS uses a modified version of MODFLOW to read the input files and do the conversion. GMS then reads the converted files. By using MODFLOW to read MODFLOW files and do the conversion, GMS can read whatever MODFLOW can read. Conversely, if GMS cannot read it, MODFLOW probably can't either.<br />
<br />
===Conversion Steps===<br />
<br />
Depending on the version of your model, GMS will perform all or some of the following steps to convert the model into the standard GMS format.<br />
<br />
# '''Convert MODFLOW 88 to MODFLOW 96'''. If importing a MODFLOW 88 model, GMS creates a MODFLOW 96 Name file by examining the Basic package file or the GMS super file. The name file is put in the same directory where the Basic package file or super file is found. In creating the MODFLOW 96 name file, GMS assumes the unit numbers in the IUNIT array in the Basic package file are ordered according to the standard MODFLOW 88 order (as found in the MODFLOW 88 source code). GMS uses the lowest unit number not used in the IUNIT array for the List file added to the name file. If external arrays are being used, the unit number GMS uses for the List file may be the same as one used for an external array.<br />
# '''Convert MODFLOW 96 to MODFLOW 2000'''. After creating the MODFLOW 96 Name file, GMS calls mf96to2k.exe, a USGS program distributed with MODFLOW 2000 which converts MODFLOW 96 models to MODFLOW 2000. This creates some new files in the same directory as the basic package file: name_MF2k.bas, name_MF2K.bcf, and name_MF2K.nam (where "name" is the name of the MODFLOW 96 name file).<br />
# '''Translate MODFLOW 2000 to GMS H5 Format'''. GMS then calls the MODFLOW Translator to translate the simulation into GMS H5 format. This creates an H5 file in the temp directory. The user must save the GMS project in order to have a GMS H5 formatted MODFLOW simulation on disk, otherwise the temp file will be discarded.<br />
<br />
===mf96to2k===<br />
Some modifications were made to mf96to2k.exe with regards to layer elevations and confining beds so that the program could be run in a non-interactive batch mode.<br />
<br />
====Grid Elevations====<br />
When mf96to2k.exe converts a MODFLOW 88/96 simulation to a MODFLOW 2000 simulation the program creates a discretization file (DIS). This file defines the layer elevations for the model grid as well as the stress periods. In MODFLOW 88/96 a model could be defined without the need for explicitly defining the top and bottom elevations of the model grid. If the old model has grid elevations defined in the BCF file then those elevations are preserved in the new MODFLOW 2000 DIS file. Where elevations are not defined in the old model then mf96to2k.exe would prompt the user to enter a constant elevation for the particular layer. When mf96to2k.exe is run by GMS these layer values are automatically set. After the model is read into GMS the user may need to edit these values.<br />
<br />
====Layer Confining Beds (LAYCBD)====<br />
When mf96to2k.exe converts a MODFLOW 88/96 model it also asks the user if a layer confining bed exists beneath each of the grid layers. When mf96to2k.exe is run by GMS no confining beds will be defined beneath the model layer. If the user wishes to include confining beds these can be edited in the Global/Basic dialog under the MODFLOW menu.<br />
<br />
==Files generated by other software==<br />
Other software such as Groundwater Vistas, Visual MODFLOW, and PM Win use their own file formats. However they do write out native MODFLOW files which GMS can read in. To use them make sure that the other software is saving out the files properly and then follow the steps above for the proper version of MODFLOW files.<br />
<br />
===Groundwater Vistas===<br />
<br />
To export MODFLOW files from Groundwater Vistas:<br />
<br />
#Open the simulation in Groundwater Vistas<br />
##Select “File | Open”<br />
##Navigate to and select the “*.gwv” file, then select “Open”<br />
#Export the native MODFLOW files from Groundwater Vistas<br />
##Select “Model | MODFLOW (or MODFLOW 2000) | Create Datasets”<br />
#Import the name file into GMS<br />
##Select “File | Open”, the “Open” macro, or just drag and drop the *.nam file in the GMS main screen.<br />
<br />
===PM Win===<br />
===Visual MODFLOW===<br />
Visual MODFLOW files can not be read into GMS. To use Visual MODFLOW files, you'll need to run MODFLOW from within Visual MODFLOW, and then modify the *.mfi file. See below for details.<br />
<br />
#Run MODFLOW from Visual MODFLOW<br />
##Open the Visual MODFLOW project (vmf file if using the latest version of Visual MODFLOW) in Visual MODFLOW<br />
##Select “Run” in the top menu<br />
##Select “Run” again from the top menu<br />
##Select “MODFLOW 2000” in the “Engines to Run” dialog, then select “Translate & Run”<br />
##Select the “Close” button in the “VMEngine” window when the model is finished running<br />
#Modify and rename the “*.mfi” file<br />
##Go to the directory where the simulation is saved on your computer<br />
##Create a copy of the “*.mfi” file. Change the extension of the copy to “*.mfn”<br />
##Open the *.mfn file in a text editor<br />
##Comment out packages that are not supported by the USGS release of MODFLOW (for example, the “WHS” and “NDC” lines)^<br />
##If necessary, modify the directory that each MODFLOW file is referencing. This is necessary if the Visual MODFLOW files were not created on the computer you are on<br />
##Save the *.mfn file<br />
#Open the *.mfn file in GMS<br />
##Select “File | Open”, the “Open” macro, or just drag and drop the *.mfn file in the GMS main screen<br />
##The “MODFLOW Translator” will most likely appear. Select “OK” after selecting the appropriate version of MODFLOW<br />
##Select “Done” when the MODFLOW Translator is finished<br />
##A dialog will appear saying that a supported solver was not found in the name file and that the PCG solver has been added. This is because the solver that Visual MODFLOW uses is not compatible with the USGS version of MODFLOW, and so GMS does not use it either. Select “OK”<br />
<br />
^Note: to comment out a package, place a pound/number sign in front of a line. See the [http://water.usgs.gov/nrp/gwsoftware/modflow2000/MFDOC/index.html?introduction.htm Online Guide to MODFLOW] for packages that the USGS version of MODFLOW supports.<br />
<br />
==USGS MODFLOW Documentation==<br />
Here are some links to MODFLOW documentation that may be helpful.<br />
{| class="wikitable"<br />
| MODFLOW 88<br />
| [http://gmsdocs.aquaveo.com/modflow88I.pdf MODFLOW 88 (I)], [http://gmsdocs.aquaveo.com/modflow88II.pdf MODFLOW 88 (II)]<br />
|-<br />
| MODFLOW 96<br />
| [http://gmsdocs.aquaveo.com/modflow96I.pdf MODFLOW 96 (I)], [http://gmsdocs.aquaveo.com/modflow96II.pdf MODFLOW 96 (II)]<br />
|-<br />
| MODFLOW 2000<br />
| [http://gmsdocs.aquaveo.com/mf2k_flowprocess.pdf MF2K Flow], [http://gmsdocs.aquaveo.com/mf2k_obssenspeprocess.pdf MF2K Obs-Sen-Pes], [http://gmsdocs.aquaveo.com/mf2k_huf.pdf HUF], [http://gmsdocs.aquaveo.com/mf2k_lmg.pdf LMG], [http://gmsdocs.aquaveo.com/mf2k_lmt.pdf LMT], [http://gmsdocs.aquaveo.com/mf2k_calibration.pdf MF2K Calibration]<br />
|-<br />
| MODFLOW 2005<br />
| [http://gmsdocs.aquaveo.com/mf2005_flowprocess.pdf MF2005 Flow Process]<br />
|}<br />
==Notes==<br />
<references/><br />
<br />
{{Navbox GMS}}<br />
[[Category:MODFLOW]]<br />
[[Category:Importing Data]]</div>Woodhttps://www.xmswiki.com/index.php?title=WMS:Image_Crop_Collar&diff=33641WMS:Image Crop Collar2011-04-05T19:45:49Z<p>Wood: </p>
<hr />
<div>Many of the images available for use in WMS are the standard USGS map series. These maps have been scanned as is and contain the information on the collar (border) of the maps. This information is okay and in fact you may want to see it, but often it is convenient to remove the collar (especially when you are tiling multiple images together).<br />
<br />
The '''Crop Collar''' command, available by right-clicking on an image in the Project Explorer, can be used to automatically remove the collar from the image for display.<br />
<br />
<br />
==Related Topics==<br />
* [[WMS:Importing an Image|Import Image]]<br />
* [[WMS:Image Display Options|Image Display Options]]<br />
<br />
<br />
{{WMSMain}}</div>Woodhttps://www.xmswiki.com/index.php?title=WMS:Exporting&diff=33640WMS:Exporting2011-04-05T19:45:28Z<p>Wood: </p>
<hr />
<div>The '''Export''' command, available when right-clicking on the image in the Project Explorer is used to save a registered image. This command is most useful after screen capturing or cropping an image, or multiple images so that you can save the new area as an image file.<br />
<br />
<br />
==Related Topics==<br />
* [[WMS:Importing an Image|Importing an Image]]<br />
* [[WMS:Screen Capture|Screen Capture]]<br />
<br />
<br />
{{WMSMain}}</div>Woodhttps://www.xmswiki.com/index.php?title=WMS:Image_Display_Options&diff=33639WMS:Image Display Options2011-04-05T19:45:07Z<p>Wood: </p>
<hr />
<div>Once an image is imported, the '''Display Options''' command in the '''Display''' menu can be used to control how the image is displayed. The Image Display Options button of the Map tab brings up the Image Display Options dialog. The following display options are available:<br />
<br />
==Draw on XY plane behind all objects==<br />
<br />
If this option is selected, the image is drawn in the background prior to drawing any other objects. This mode is used to aid in the creation of new objects or to simply enhance a plot. The image is only displayed in plan view.<br />
<br />
==Texture map to surface when shaded==<br />
<br />
If this option is selected, the image is "draped" or texture mapped over the designated surface (TIN or 2D Grid). The image must be registered such that the surface lies within the domain of the image. The surface is texture mapped when the image is shaded using the Shade command.<br />
<br />
<br />
==Related Topics==<br />
* [[WMS:Images|Images]]<br />
* [[WMS:Image Crop Collar|Crop Collar]]<br />
<br />
<br />
{{WMSMain}}</div>Woodhttps://www.xmswiki.com/index.php?title=SMS:BOUSS-2D_BC_Cell_Strings&diff=33530SMS:BOUSS-2D BC Cell Strings2011-03-21T16:06:40Z<p>Wood: </p>
<hr />
<div>[[image:BOUSS-2D_Boundary_Image.png|400px|right]]<br />
When the [[SMS:BOUSS-2D|BOUSS-2D]] grid is created, SMS creates cell strings around the computational boundaries of the domain. A cell string is a list of contiguous node locations in the grid. The image to the right shows a grid with four cell strings that were automatically created. The cell string on the left includes the cells along the open ocean. This one has been assigned to be a wave-maker. The one on the right defines the interface between ocean and land along the coastline, and the top and bottom define the portion of the grid that are open to the ocean on those sides.<br />
<br />
Cell strings can also be created manually to specify the location of structures, wave-makers, and areas where damping and/or porosity layers may be necessary.<br />
<br />
Boundary conditions are specified along cell strings in the BOUSS-2D Boundary Conditions dialog, which is accessed by selecting one or more cell strings using the select cell string tool, and then selecting the Assign BC menu item from the BOUSS-2D menu. Normally, the user will select a single cell string and assign a boundary condition. If a boundary condition has already exists for the selected cell string, the attributes are displayed. The different options for a cell string include:<br />
<br />
# Unassigned BC. When a cell string is created in BOUSS-2D its default boundary condition type is Unassigned. Unassigned cell strings do not influence the model. In fact, unassigned cell strings are not saved as part of the BOUSS-2D input files.<br />
# Damping BC. Waves propagating out of the computational domain are absorbed in damping regions (or damping layers) placed around the perimeter of the computational domain. Damping layers can also be used to model the partial reflection from harbor structures inside the computational area. The user must enter a physical width into the “Width” edit field to specify the size of the damping layer. The damping region extends the width on either side of the cell string. The damping value is a non-dimensional damping coefficient that is allowed to vary from 0.0 to 1.0. No damping will occur when a value of 0.0 is used. Waves will be damped when a value of 1.0 is used along the side boundaries. A typical value for shoreline is 0.1. The default damping value is 1.0. SMS will assign the value specified at the cell string and ramp down to 0.0 at a distance of “width” from the cell string.<br />
# Porosity BC. Porosity boundary conditions are used to simulate partial wave reflection and transmission through surface-piercing porous structures such as breakwaters. Enter a physical width into the “Width” edit field to specify the size of the porous structure. Like with the damping regions, this width is extended on both sides of the cell string. The porosity value is a non-dimensional porosity coefficient that is allowed to vary from 0.0 to 1.0. A value of 0.0 corresponds to an impervious structure, while a value of near 1.0 would correspond to a highly porous structure. Typical porosity for stone type breakwaters is 0.4. The default porosity value is 1.0.<br />
# Wave-maker BC. The wave-maker option is only available when a single cell string is selected and that cell string lies in a single column or row (straight line). Legal cell strings can be created using the SHIFT key when creating cell strings, using automatically created cell strings along a grid boundary, or by creating short cell strings. The extent and position of the wave maker can be modified using I,J indices in the dialog. BOUSS-2D generates waves emanating from this cell string. The properties of the waves are defined using the Wave Generator Properties dialog (described below) that is accessed through the Options button. The edit fields are used to position and size the wave maker in the computational domain. The first two values are the Start and End cells of the wave maker along the column or row that is specified by the third value, which is the Offset value. The Start and End values are limited to the number of cells in either the I- or J-direction, and the Offset value is limited to the number of rows or columns.<br />
<br />
When the ''OK'' button is clicked, a check is done to see if the wave maker cell string is at a constant depth. If the depth varies by more than 20% and the wave maker is on the edge of the grid (not internal), the user is asked whether they want to force constant depth along the wave maker cell string or not. If so, the grid is extended to allow the wave maker to be at the deepest elevation along the string, with a maximum slope of 1:10 from the existing grid to the new wave-maker position. A Wave Calculator is provided as part of BOUSS-2D interface in SMS (see Appendix B) to assist users in the preparation of wave input parameters required by the model. Note that the BOUSS-2D | Assign BC menu item is disabled any time multiple wave makers are selected or if a wave maker and one or more other cell strings are selected.<br />
<br />
{{Template:SMSMain}}<br />
<br />
[[Category:BOUSS-2D|B]]</div>Woodhttps://www.xmswiki.com/index.php?title=GMS:Observations&diff=33426GMS:Observations2011-03-10T22:29:40Z<p>Wood: /* Flow Observations */</p>
<hr />
<div>{{Infobox Calibration}}<br />
==Point Observations==<br />
The primary type of field data used in a typical calibration exercise is point observations. Point observations represent values that are measured at some location in the field. Point observations generally correspond to water table elevations measured at observation wells. However, multiple observed values can be defined at each observation point. Observation points are managed in the Map module using the Coverage Setup dialog.<br />
<br />
==Flow Observations==<br />
Flow observations represent gains or losses between aquifers and streams or reservoirs. In addition to point observations, flow observations are an essential part of a calibration exercise for a flow model. If calibration is attempted using point observations only, there may be many combinations of parameters such as hydraulic conductivity and recharge that will result in the same head distribution. Adding one or more flow observations serves to "pin down" the flow quantity resulting in a set of hydraulic conductivities and recharge values that are more likely to be unique.<br />
<br />
While the point observation tools are model independent, GMS only supports flow observations for MODFLOW and [[GMS:FEMWATER#FEMWATER Flows|FEMWATER]]. With MODFLOW, observed flows are assigned to selected arcs and polygons making up the MODFLOW conceptual model in the Map module. When a MODFLOW solution is imported, the computed flows are read for the arcs and polygons and compared with observed values. <br />
<br />
With a FEMWATER simulation, observed values cannot be assigned to objects in the FEMWATER conceptual model. However, when a FEMWATER solution is imported, the computed flows on selected model boundaries can be automatically summed. Comparison of computed vs. observed flows must then be made manually.<br />
<br />
==Observation Weights==<br />
When performing [[GMS:Automated Parameter Estimation|automated parameter estimation]], a set of head and flow observations are defined using points, arcs, and polygons in the Map module. When entering the point and flow observations, care should be taken when entering the calibration interval and confidence values. These values are used to determine the weights assigned to each observation in the inverse model. The weight is multiplied by the residual for the observation in the objective function. The weight that is sent to the inverse model input files by GMS is computed as 1/[(standard deviation)^2*Group Weight]. Note that GMS will automatically convert from an interval and a confidence to a standard deviation or you can directly enter the standard deviation.<br />
<br />
===Group Weight Multipliers===<br />
In addition to the individual weight, a group weight can also be assigned. Group weights are assigned using the Group Weight section of the Observations dialog. This dialog is accessed by selecting the Observations command in the MODFLOW menu.<br />
<br />
A group weight can be assigned to each of the following observation types:<br />
<br />
#'''Head observations.'''<br />
#'''Constant head flow observations.'''<br />
#'''River flow observations.'''<br />
#'''General head flow observations.'''<br />
#'''Drain flow observations.'''<br />
#'''Stream flow observations.'''<br />
<br />
Options 2-6 correspond to flow observations that are defined using the Observed flow rate option.<br />
<br />
The default value for the group weights is 1.0. The default value can be changed to give a larger influence to a particular observation type. For example, if a particular model had sixteen head observations and one flux observation corresponding to a stream gage, a better solution may be obtained by increasing the flux group weight to give more weight to the stream gage measurement.<br />
<br />
==Observations Dialog==<br />
This dialog is used to manage which coverages that contain MODFLOW observation data will be applied to the current simulation. It is also used to apply group weights. You can only access this dialog when observations have been created using the [[GMS:Map Module|Map Module]] in a MODFLOW conceptual model.<br />
<br />
===Group Weights===<br />
<br />
These weights can be used to emphasize (or deemphasize) a type of observation for the simulation.<br />
<br />
===Coverages===<br />
<br />
This spreadsheet allows you to choose which observation coverages will be used in the current simulation. This can be helpful if you have observations for a site from different times, but you only want to use one of the times.<br />
<br />
<!--{{Version GMS 8.0}}--><br />
{{template:Version GMS 8.0}}<br />
===Export Trans. Obs.===<br />
Beginning with version 8.0, this button allows you to export a csv (comma separated values) file with transient observation data. This file can be loaded into excel to create plots of the transient observation values vs. the model computed values. An example of using this data is included in the [[GMS:Tutorials|MODFLOW- Managing Transient Data]] tutorial.<br />
<br />
==Confidence Interval and Standard Deviation==<br />
The interval and standard deviation are related by the following equation:<br />
<br />
:sd = CI/z<br />
<br />
where sd is the standard deviation, CI is the confidence interval, and z is the the "z statistic" based on the specified confidence and the normal distribution. The user can enter an interval and confidence, and the standard deviation will be computed; or the user can enter a standard deviation and confidence, and the interval will be computed. <br />
<br />
In practical terms entering an interval (or standard deviation) and confidence is an indication of how much error the user believes is associated with the observed value.<br />
<br />
The standard deviation becomes important when using an inverse model. The weight assigned to each of the observations points is a function of the standard deviation. This weight is used in the objective function that the inverse model tries to minimize. An observation point with a small standard deviation will have a greater influence on the objective function than a point with a large standard deviation.<br />
<br />
The user must enter an interval (or standard deviation) and confidence in the [[GMS:Feature Objects#Feature Object Properties|Properties Dialog]]. Although these values are rarely quantified the following examples may prove helpful.<br />
<br />
If the user had the following set of head measurements for one observation well:<br />
<br />
{| style="text-align:center"<br />
!width="150"|<u>Date</u><br />
!width="75"|<u>Head</u><br />
|-<br />
|May 10, 1998||55.0<br />
|-<br />
|July 10, 1998||50.5<br />
|-<br />
|September 5, 1998||48.6<br />
|-<br />
|November 15, 1998||49.1<br />
|-<br />
|February 2, 1999||50.8<br />
|-<br />
|March 12, 1999||54.0<br />
|-<br />
|April 1, 1999||57.2<br />
|}<br />
<br />
The mean of the data is 52.17 and the standard deviation is 3.25. The user could enter this standard deviation and a confidence of 95%.<br />
<br />
Many times the user does not have this much data available. Usually the user will only have one measured value. In this case the user must use engineering judgement to estimate an interval or standard deviation. For example, if I have a single head measurement of 45.7 ft and I believe that observation to be accurate to within a 1 foot. Then I would enter 1 foot as my interval.<br />
<br />
==Related Links==<br />
<br />
[[GMS:Automated Parameter Estimation|Automated Parameter Estimation]]<br />
<br />
{{Navbox GMS}}<br />
<br />
[[Category:Calibration]]</div>Woodhttps://www.xmswiki.com/index.php?title=SMS:STWAVE&diff=33425SMS:STWAVE2011-03-10T22:27:12Z<p>Wood: /* Using the Model / Practical Notes */</p>
<hr />
<div>{{SMS Infobox Model |<br />
|name= STWAVE<br />
|model_type= Model for nearshore wind-wave growth and propagation.<br />
|developer= [http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=Persons;170 Jane Smith]<br />
|web_site= [http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=SOFTWARE;9 STWAVE web site]<br />
|tutorials= <br />
General Section<br />
* Data Visualization<br />
* Observation<br />
Models Section<br />
* STWAVE<br />
Several sets of sample problems and case studies are available. These include: <br />
* Model Validataion cases from the STWAVE [http://chl.erdc.usace.army.mil/chl.aspx?p=s&a=SOFTWARE;9 website]<br />
}}<br />
<br />
STWAVE is a steady-state, finite difference, spectral model based on the wave action balance equation. STWAVE is written by the U.S. Army Corps of Engineers Waterways Experiment Station (USACE-WES).<br />
<br />
== Functionality ==<br />
STWAVE simulates depth-induced wave refraction and shoaling, current-induced refraction and shoaling, depth- and steepness-induced wave breaking, diffraction, wave growth because of wind input, and wave-wave interaction and white capping that redistribute and dissipate energy in a growing wave field. The purpose of STWAVE is to provide an easy-to-apply, flexible, and robust model for nearshore wind-wave growth and propagation. Recent upgrades to the model include wind, surge and friction fields (spatially varied). Also, wind and surge fields can be temporally varied. The method of analysis used by the STWAVE code along with the file formats and input parameters are described in the STWAVE documentation. [[SMS:SMS|SMS]] supports both pre- and post-processing for STWAVE.<br />
<br />
The new full-plane version of STWAVE is not a replacement for the half-plane version, but a supplement. The half-plane version will always have an advantage of substantially lower memory requirements (~ two orders of magnitude) and faster execution. The half-plane limitation is generally appropriate for nearshore coastal applications, with the exception of enclosed or semi-enclosed bays, estuaries, and lakes where seas and swells may oppose each other or there is no clear “offshore” direction. The full-plane version allows wave input on all boundaries and wave generation from all directions.<br />
<br />
== Using the Model / Practical Notes ==<br />
* A grid for use with STWAVE is created and edited in [[SMS:SMS|SMS]] using the Map Module.<br />
* The modeling parameters required by STWAVE are generated and applied to the mesh using commands grouped in the STWAVE menu.<br />
* Post processing of solution data generated by STWAVE is done using the generic visualization tools of SMS.<br />
* Wind can be entered in the STWAVE model control as either a constant value or by specifying an existing Cartesian Grid data set.<br />
* STWAVE requires metric units. All data in SMS needs to be in metric units before running STWAVE.<br />
* Water depths are defined as positive numbers and land elevations are negative numbers.<br />
<br />
== Graphical Interface ==<br />
The [[SMS:STWAVE Graphical Interface|STWAVE Graphical Interface]] contains tools to create and edit a STWAVE 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 STWAVE. If a grid has already been created for a STWAVE 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 STWAVE. 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:STWAVE Menu|STWAVE Menu]]. See [[SMS:STWAVE Graphical Interface|STWAVE Graphical Interface]] for more information.<br />
<br />
== External Links ==<br />
* Aug 2007 ERDC/CHL CHETN-I-76 Modeling Nearshore Waves for Hurricane Katrina [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-i-76.pdf]<br />
* Aug 2007 ERDC/CHL CHETN-I-75 Full-Plane STWAVE with Bottom Friction: II. Model Overview [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-i-75.pdf]<br />
* Sep 2006 9th International Workshop On Wave Hindcasting and Forecasting Jane McKee Smith Modeling Nearshore Waves For Hurricane Katrina [http://www.waveworkshop.org/9thWaves/Papers/Smith.pdf]<br />
* Mar 2006 ERDC/CHL CHETN-I-71 Full Plane STWAVE: SMS Graphical Interface [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-i-71.pdf]<br />
* Dec 2003 ERDC/CHL CHETN-IV-60 SMS Steering Module for Coupling Waves and Currents, 2: M2D (now know as CMS-Flow) and STWAVE [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-60.pdf]<br />
* Jun 2002 ERDC/CHL CHETN-I-66 Grid Nesting with STWAVE [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-i-66.pdf]<br />
* Jun 2002 ERDC/CHL CHETN-IV-41 SMS Steering Module for Coupling Waves and Currents, 1: ADCIRC and STWAVE [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-iv-41.pdf]<br />
** Please see [http://aquaveo.invisionzone.com/index.php?showtopic=23 this forum post] for an explanation of ADCIRC and STWAVE steering<br />
* Sep 2001 ERDC/CHL CHETN-I-64 Modeling Nearshor Wave Transformation with STWAVE [http://chl.erdc.usace.army.mil/library/publications/chetn/pdf/chetn-i-66.pdf]<br />
<br />
<br />
{{Template:SMSMain}}<br />
<br />
[[Category:SMS Cartesian Grid]]<br />
[[Category:STWAVE]]</div>Woodhttps://www.xmswiki.com/index.php?title=GMS:Pilot_Points&diff=33105GMS:Pilot Points2011-02-03T18:23:47Z<p>Wood: /* Guidelines for Placement of Pilot Points */</p>
<hr />
<div>{{Infobox Calibration}}<br />
Pilot points can be thought of as a 2D scatter point set. Instead of creating a zone and having the inverse model estimate one value for the entire zone, the value of the parameter within the zone is interpolated from the pilot points. Then the inverse model estimates the values at the pilot points. The figure below shows a set of pilot points used to estimate horizontal hydraulic conductivity. Notice how the hydraulic conductivity now varies from cell to cell. When the inverse model runs, the values at the pilot points are adjusted and the “surface” defining the variation of K values is warped until the objective function is minimized.<br />
<br />
PEST provides an additional option for the pilot point method called “regularization”. Regularization imposes an additional measure of “stiffness” to the parameter being interpolated via a “homogeneity” constraint. In the absence of any strong influence from the PEST objective function, this constraint causes values at pilot points to approximate the mean value of adjacent pilot points. This constraint makes the inversion process much more stable and makes it possible to violate one of the typical constraints associated with parameter estimation: namely, the requirement that the number of parameters must be less than the number of observations. With regularization, the number of parameters can greatly exceed the number of observations. As a result, complex hydraulic conductivity distributions can be defined, resulting in extremely low residual error. The pilot point method with regularization is an incredibly powerful feature of PEST. (For more on PEST see [[GMS:Automated Parameter Estimation|Automated Parameter Estimation]])<br />
<br />
[[Image:pilot.gif]]<br />
''Pilot Points and Resulting Conductivity Field''<br />
<br />
===Interpolation Options===<br />
[[GMS:Kriging|Kriging]] and [[GMS:Inverse Distance Weighted|IDW]] are the only interpolation options supported with pilot points. The kriging option requires the establishment of a model variogram (by creating a nested structure). The nodal function options in the IDW method are not supported because those schemes compute gradients based on the data set values at the surrounding points. With the pilot point method, the values at the points will change during the inversion process, thereby rendering the previously computed gradients inaccurate.<br />
<br />
===Pilot Point Conditioning===<br />
For pilot point interpolation of hydraulic conductivity, it is sometimes useful to include one or more measured K values with the pilot point set. These measured values could represent K values extracted from a field pump test. The Pilot Point Conditioning option is available to represent this scenario. One of the properties associated with scatter points is a Fixed pilot point toggle. If this toggle is on and the corresponding scatter point set is used for pilot point interpolation, the K value assigned to the point is not allowed to vary during the parameter estimation process.<br />
<br />
[[Image:Pilot_Point_Cond.gif]]<br />
<br />
===Guidelines for Placement of Pilot Points===<br />
Note: The recommended maximum number of pilot points is about 200.<br />
# Place points between observations rather than on top of observations<br />
# Add greater density where there are more observations<br />
# Add points where head gradient is steep<br />
# Place a row of points between observation wells and head-dependent boundaries<br />
# Fill in the gaps<br />
<br />
==Related Links==<br />
<br />
[[GMS:Model Calibration|Model Calibration]]<br />
<br />
<br />
{{Navbox GMS}}<br />
[[Category:Parameters]]</div>Woodhttps://www.xmswiki.com/index.php?title=SMS:GFGEN_Executable_Known_Issues&diff=32968SMS:GFGEN Executable Known Issues2010-12-30T16:27:13Z<p>Wood: /* Node Location Truncation */</p>
<hr />
<div>Unfortunately there are some known issues and likely some unknown issues as well related to the GFGEN executable. This page is intended to help make users aware of known issues and how to work around them.<br />
<br />
GFGEN (TABS) is developed by Resource Management Associates, Lafayette, California, and modified by [http://www.wes.army.mil/Welcome.html WES]. Aquaveo does not have access to the GFGEN source code and cannot make changes to fix the issues found in the GFGEN numerical model. Aquaveo can fix problems in the SMS interface, used for pre and post processing of GFGEN files.<br />
<br />
This list may not contain all know issues, so please feel free to add to it.<br />
<br />
== Node Location Truncation ==<br />
GFGEN does not correctly calculate the midside node location if the x or y coordinate of a node are large. You may receive an error similar to the following:<br />
<pre><br />
* Node 50 Violates MIDDLE THIRD RULE ***** <br />
The node lies 0.0831 of the way from node 1 to node 49 <br />
</pre><br />
<pre><br />
=== Problem inside COEFS routine. Do 180. <br />
Element= 535 Gauss pt= 1 out of NGP= 16 <br />
Divide by DETJ= -0.0229 <br />
J11-J22-J12-J21= 1.1526 0.38006 0.74030 0.62257 <br />
stop in coefs <br />
</pre><br />
<br />
The current work around is to [[SMS:Transform_(Data_Menu)|translate the mesh]] so the x and y coordinates are smaller values.<br />
<br />
See the following forum posts:<br />
* [http://aquaveo.invisionzone.com/index.php?showtopic=375 RMA2 - same mesh, same BC, different results?, Results differ depending on nodal coordinates]<br />
* [http://aquaveo.invisionzone.com/index.php?showtopic=298 Problem inside COEFS routine]<br />
<br />
== Element Limit ==<br />
GFGEN can only handle up to 100,000 elements.<br />
<br />
== Related Topics ==<br />
* [[SMS:GFGEN|GFGEN]]<br />
<br />
<br />
{{Template:SMSMain}}<br />
<br />
[[Category:SMS 2D Mesh|G]]<br />
[[Category:TABS|G]]</div>Woodhttps://www.xmswiki.com/index.php?title=File:Effective_length2.jpg&diff=32958File:Effective length2.jpg2010-12-20T19:05:09Z<p>Wood: uploaded a new version of "File:Effective length2.jpg": A simple illustration of effective length and area of a cross section.</p>
<hr />
<div>A sketch of a cross section illustrating the effective length and area of a cross section.</div>Woodhttps://www.xmswiki.com/index.php?title=SMS:Q%26A_ADCIRC&diff=32953SMS:Q&A ADCIRC2010-12-20T17:54:26Z<p>Wood: </p>
<hr />
<div>[[SMS:Support_Knowledge Base|Return to the Main Q&A Page]]<br />
<br />
<br />
'''Q:''' Where can I find ADCIRC model documentation?<br />
<br />
''(Tags: ADCIRC, Documentation)''<br />
<br />
'''A:''' Answer.<br />
<br />
'''Q:''' When using the XY Series Editor to create a hydrograpgh to define a nodestring boundary condition, what do the time and flowrate variables have reference to?<br />
<br />
'''A:''' The time and flowrate variables will, most of the time, be read in from a file. They can also be user defined if no data is available. The time variable is the time when the corresponding flowrate was recorded. These times are independent from any other time variable needed by the ADCIRC model. The flowrate variable is the total flow recorded for the entire boundary specified. It is a good idea, if possible, to establish a time range in the XY Series Editor that is longer than the time to run for the sample model you are working on. This would ensure there is more than enough data for the complete model run time.<br />
<br />
'''Q:''' How is the "Sample Interval" in the Assign Flowrates from Hydrograph menu related to the FTIMINC variable defined in the fort.20 file description in the ADCIRC user manual?<br />
<br />
'''A:''' The "Sample Interval" variable is the FTIMINC variable defined in the fort.20 file description. The definition of this variable is the time increment (secs) between consecutive sets of normal flow boundary condition values contained in the fort.20 file.<br />
<br />
'''Q:''' What is the "Reference WSE" value in the Assign Flowrates from Hydrograph menu?<br />
<br />
'''A:''' The "Reference WSE" stands for Reference Water Surface Elevation. It is a specified initial water depth at the boundary to be used in calculating data such as velocity, and others.<br />
<br />
'''Q:''' Can you define different flowrate percentages at each of the nodes in the boundary nodestring?<br />
<br />
'''A:''' No, the flowrate can only be defined once for the entire nodestring. ADCIRC does, however, take into consideration the shape of the channel and the roughness, so flowrates will vary slightly across a boundary anyways.<br />
<br />
'''Q:''' Is there a way to find the distance (or length, or width) of a nodestring?<br />
<br />
'''A:''' Yes, there are two ways in which the length of a nodestring can be found. First, select the "Select Nodestring" tool from the toolbar. Next, select the nodestring desired by clicking on it. At the bottom of the screen in the information bar, information about the nodestring will be displayed. The length will be shown there. If you cannot see it, widen out the screen and more information should appear. The other way entails finding the distance between two nodes by selecting two nodes at once (do not select the entire nodestring, but he two end points only). The distance will appear at the very bottom of the screen in the information bar. To select two nodes at once, first select the "Select Node" tool from the toolbar, then select the first node desired by clicking on it, and last, while holding down the SHIFT key click on the second node.<br />
<br />
'''Q:''' How are the normal flow rates per unit width calculated in ADCIRC?<br />
<br />
'''A:''' Normal flow rates per unit width are calculated in the Extracted Data dialog. SMS looks at each node individually and calculates a flow rate per unit width value for each section along the boundary. It first calculates the length of each node section (effective length), the area of each node section (effective area), and the total area. Then it multiplies the total flow values defined on a hydrograph by the effective area of a node divided by the total area times the effective length of a node (or Q * (effective area/(total area * effective length))). These flow rate per unit width values should be written out to a fort.20 file when an ADCIRC model runs.<br />
<br />
[[File:Effective_length2.jpg]]</div>Wood