SMS:SRH-2D Errors: Difference between revisions

From XMS Wiki
Jump to navigationJump to search
(Created page with "This is a list of known error messages produced by SRH-2D. ==List of Error Messages== The first three columns in the table are sortable. Simply click the smal...")
 
No edit summary
Line 188: Line 188:
==Related Topics==
==Related Topics==
* [[SMS:SRH-2D|SRH-2D]]
* [[SMS:SRH-2D|SRH-2D]]
* [[SMS:Bugfixes|Bugfixes]]
* [[SMS:Bugfixes|SMS Bugfixes]]





Revision as of 17:39, 22 December 2016

This is a list of known error messages produced by SRH-2D.

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 Preprocessor 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 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.
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 Stopped in structure_culvert.f90 ICELL error#5 BC arc mesh snapping does not match inactive material zone snapping 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.
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.
SRH-2D a face cannot be found given two mesh points

Two points are: 7262 591
Check your mesh node list; you may do this using _SIF.dat file directly!

Errors from final_touch.f90 **** on MONITOR LINE#2

Monitor line nodestring not snapped correctly

When the monitor line is snapped to the mesh as a nodestring, the nodestring does not have a continuous string of nodes but rather skips a node so that the nodestring crosses the middle of the element diagonally. This is a bug that has been fixed.
SRH-2D If you specify 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. All material polygons unassigned This occurs when none of the materials have been assigned to the material polygons. Also occurs when all material polygons covering the inflow BC are inactive.
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 time steps
No mesh that matches the scalar set. No mesh that matches the scalar set. Nodes | Renumber. It is a good idea after you are done editing your mesh to renumber the nodes, to make sure SMS and SRH-2D have the same numbers on every node.
WSE error directly under the bridge in the form of waves oscillating through the channel Use larger, quadrilateral elements in the area of deep flow (as you have found). This means that the piers need to be switched to obstructions
The following coverage(s) have an unsupported type and will be converted to area property: Mat_Test" error message Mat_Test" error message 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), adjust the parameters to make converge if not succesfully executed
1 Error code 1 srhmat file does not exist File didn't export successfully, Make sure assigned materials in the materials coverage, possibly too many monitoring lines (20 or less okay)
SRH-2D a face cannot be found given two mesh points

Two points are: 7262 591 Check your mesh node list; you may do this using _SIF.dat file directly!

Errors from final_touch.f90 on MONITOR LINE#2 rebuild the arcs
PreSRH-2D forrtl: severe (157): Program Exception - access violation Set up file location Preferences to the correct location for SRH-Pre
SRH-2D 4 All INLET cells are dry sets are dry from bc_mdot2.f90! Code may have blow up (sic) due to input errors or too-large time-step. This problem typically arises because the polygons that you have given for the obstructions do not overlap any element centroids. The problem can be solved by refining the elements in the area of the obstructions until the obstruction polygon is well represented by elements whose centroids lie within the spatial extent of the polygons.
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
PreSRH-2D a face cannot be found given two mesh points

Two points are: 38383 38494 Check your mesh node list; you may do this using _SIF.dat file directly!

Errors from final touch.f90 on MONITOR LINE#2

Inconsistent or disconnected nodestring for a monitor line

This was caused by having a monitoring line run across a large "hole" in the mesh. The hole was large enough that we were not snapping the monitor line to a valid nodestring.
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 if you have the right input of (X Y) coordinates for a monitoring points Monitor Point Outside of Mesh Monitor point must be somewhere within a mesh element.

Related Topics