SMS:SRH-2D Errors

From XMS Wiki
Jump to navigationJump to search

This is a list of known error messages produced by SRH-2D. These errors will appear during the model run.

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.

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.

List of Error Messages

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.

The columns in the table include:

  • Location indicates whether the error occurs in the SRH-2D Pre-processor or in SRH-2D itself.
  • Error Code gives the Error Code (if any).
  • 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.
  • Description gives more details about the error.
  • Solution gives steps necessary to correct the issue.
Location Error Code Error Text from Model Description Solution
SRH-2D 1 Stopped in spline.f90 H 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. 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.
SRH-2D 1 Stopped in uti_qwin_xyplot.f90 TIME_SIMU Inconsistent time control The end time is prior to the start time in the model control. Adjust so it is later than the start time.
PreSRH-2D 1 unable to open srhhydro file! Unable to open srhhydro file 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.
PreSRH-2D 1 Element ID is not consecutive 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) The mesh nodes need to be renumbered using the Renumber command under the Nodes menu in the Mesh module
SRH-2D No cells cover an obstruction in structure_obstruction.f90 Obstruction feature area of influence does not cover the centroid of at least one element 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.
SRH-2D 5 Stopped in structure_culvert.f90 ICELL error#5 BC arc mesh snapping does not match inactive material zone snapping 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.
SRH-2D More than 99 obstructions exist 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.
Pre SRH-2D Errors from final_touch.f90 **** on MONITOR LINE#n
a face cannot be found given two mesh points

Two points are: xx xx
Check the mesh node list; do this using _SIF.dat file directly!

Monitor line spans a mesh void (hole) Reconfigure the monitor line. Monitor lines cannot span holes in the mesh.
SRH-2D If there is a z elevation to a bridge arc that is too high in the structures exercise, SRH doesn't run. bug
SRH-2D 2 ALL INLET cells are dry from bc_mdot2.f90! Code may have blow up due to input errors or too-large time step. Material polygons near inflow are unassigned 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.
SRH-2D FATAL ERROR The code diverged; further reduction of time step would help the convergence! Too large of a time step Reduce the size of the computational time step in the model control
SRH-2D 3 bad mesh ! Stopped in indx_conn.f Problem in mesh, often due to overlapping elements. Check if problem cell (element) id is listed. Otherwise, examine mesh quality in SMS.
SMS No mesh that matches the scalar set. 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. Take care when making edits to the mesh and renumbering the nodes. Any previous results will be invalidated when nodes are renumbered.
None None WSE error directly under the bridge in the form of waves oscillating through the channel 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.
None None 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. 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.
SMS The following coverage(s) have an unsupported type and will be converted to area property: (Name of Coverage(s) Listed) 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.
SRH-2D Exit code 0 Exit code 0 SRH-2D has stopped or finished (whether "successfully executed" or not), further troubleshooting is required if it has not finished running successfully.
1 Error code 1 srhmat file does not exist File didn't export successfully. Make sure materials are assigned in the materials coverage.
PreSRH-2D forrtl: severe (157): Program Exception - access violation Set up file location Preferences to the correct location for SRH-Pre
PreSRH-2D MESH-UNIT: Enter one of the following options for the unit of the mesh Mesh unit error SRH requires that vertical and horizontal units be in either meters or U.S survey feet
SRH-2D 8 Inconsistent cell ID in mesh_connectivity: maybe due to wrong nodestring Possibly due to overlapping elements. Also, check snapping of BC arcs.
PreSRH-2D 1 Stopped in add_nbdf.90 DIS Issue with BC nodestrings 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.
SRH-2D 1 Stopped in face_wd.f90 PRESS#1 Issue with Pressure Flow BC and "Piers" 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.
SRH-2D Program Stopped as Mesh is different in RST file

One of the following is different:
Ncell Nvert Nface Nclfc Nclvt in RESTART file
do not match those in the input file
Ncell Nvert Nface Nclfc Nclvt
in restart file are: 13604 7374 20977 41693 41693
in casename.GRD file are: 15459 8277 23735 47225
Mesh topology has to be the same for irest>=1 or init_method=3

Using a restart file that was created with another mesh Restart files can only be used with simulations using the exact same mesh.
PreSRH-2D Could not find a mesh cell which contains the monitoring point! Check the input of (X Y) coordinates for a monitoring points Monitor Point Outside of Mesh Monitor point must be somewhere within a mesh element.
SRH-2D 6940 Ensure that areas upstream of the upstream culvert location and areas downstream of the downstream culvert location have a valid material type assigned.
SRH-2D 1 Stopped in structure_pressure_flow.f90 PARA DISTANCE Shape of pressure zone is not acceptable for a parabolic type bridge ceiling Ensure that the pressure zone, between the pressure flow arcs, is rectangular in shape
SRH-2D 9669 Program stopped due to the following:

Wrong IFACE matching occurred in structure_internal.f90 #4 Error Code is: 9669

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). Create a new mesh with a rectangle between pressure flow arcs and which has quads in this area using the patch mesh generation method.
SRH-2D 46631 Program stopped due to the following:

Wrong IFACE matching occurred in structure_internal.f90 #4 Error Code is: 46631

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). Create a new mesh with a rectangle between pressure flow arcs and which has quads in this area using the patch mesh generation method.
SRH-2D 0 Program stopped due to the following:

Wrong IFACE matching occurred in structure_internal.f90 #4 Error Code is: 0

BC arc is not snapped properly between nodes along element edges with varying elevations. Interpolate to Map" feature can be used to vary elevations along an existing BC arc).
SRH-2D 16026 Program stopped due to the following:

A downstream Structure nodestring has not set right; structure_culvert.f90 ICELL error#2 Error Code is: 16026

The 2D mesh around and through the structure is not optimal. 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).
SRH-2D 79 Program stopped due to the following:

Tailwater WSE exceeded the maximum TW in the Reverse HY8 Table structure_hy8.f90 Error Code is: 79

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 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.
SRH-2D N/A forrtl: severe (24): end-of-file during read, unit n, file {your filepath.dat} Image PC Routine Line Source srh2d_3.2_quickwi...Unknown... 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. 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.
SRH-2D 1 Program stopped due to the following: Stopped in read_input2: Mismatch in HY8 ID This is a bug in SRH caused by having two culvert crossings defined in the *.hy8 crossing file with certain similarities in their names. 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.
SRH-2D N/A Failed to find a mesh cell which contains the following (x y) points: (X,Y)= 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. 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.
SRH-2D 0 Program stopped due to the following: IFACE match does not found in structure_culvert.f90 #n Element configuration around the structure face is causing a mismatch in the transition into or out of the structure. 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).
SRH-2D 1 Program stopped due to the following: Stopped in read_input2.f90 HY8 Forward_TABLE Line Error 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. Add a ".hy8" file extension to the culvert defintion filename.
SRH-2D N/A forrtl: severe (170): Program Exception - stack overflow 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. Reduce the number of elements in the 2D mesh and try running the simulation again.
SRH-2D 3 Not ready in solve.f90 SEDIMENT MODULE 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. Either do not use the sediment transport in the model run, or remove the 1D hydraulic structures from the model.
PreSRH-2D 4 Program stopped due to the following: Stopped in sec_blow NLAY Error Code is: 4 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. Reduce the number of sediment layers to 9 or less in each sediment material.
SRH-2D 1 Program stopped due to the following: Wrong Boundary ID;may due to some boundary mesh points are not in NODESTRING lists in SMS This error seems to be related to issues with mesh quality. Review mesh quality. Check for elements with very small or very large interior angles (angles less than 10 degrees or greater than 180 degrees. If any are present, make adjustments in the conceptual model (mesh generator coverage) and re-generate the mesh.

Related Topics