- #NONMEM FORRTL SEVERE <170> PROGRAM EXCEPTION STACK OVERFLOW UPDATE#
- #NONMEM FORRTL SEVERE <170> PROGRAM EXCEPTION STACK OVERFLOW FULL#
- #NONMEM FORRTL SEVERE <170> PROGRAM EXCEPTION STACK OVERFLOW CODE#
If the material zone snapping does not match the BC arc snapping, there will be element inactivity problems at the face of the structure. In SMS v12.1, some paired arc 1D structures require an "unassigned" material zone between the structure arcs.
![nonmem forrtl severe <170> program exception stack overflow nonmem forrtl severe <170> program exception stack overflow](https://s1.manualzz.com/store/data/039731520_1-c19cc9d90a2ceebb9ba75adfbf13aad4.png)
Stopped in structure_culvert.f90 ICELL error#5īC arc mesh snapping does not match inactive material zone snapping 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.
![nonmem forrtl severe <170> program exception stack overflow nonmem forrtl severe <170> program exception stack overflow](https://i.stack.imgur.com/wWfZl.jpg)
Obstruction feature area of influence does not cover the centroid of at least one element No cells cover an obstruction in structure_obstruction.f90 The mesh nodes need to be renumbered using the Renumber command under the Nodes menu in the Mesh module
#NONMEM FORRTL SEVERE <170> PROGRAM EXCEPTION STACK OVERFLOW UPDATE#
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) Reduce the path length to less than 300 characters. Therefore, the SRH-2D preprocessor could not read the exported files from SMS. The path length for the SMS project is too long. Adjust so it is later than the start time. The end time is prior to the start time in the model control. Go to the XY series editor where the time series data is defined and remove any and every duplicate time entry. The time series data should only have one data value per defined time. 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. Solution gives steps necessary to correct the issue.Description gives more details about the error.Errors that do not produce any error text will have "no text" in this field.
#NONMEM FORRTL SEVERE <170> PROGRAM EXCEPTION STACK OVERFLOW FULL#
Error Text from Model gives the full text of the error message.
#NONMEM FORRTL SEVERE <170> PROGRAM EXCEPTION STACK OVERFLOW CODE#
Error Code gives the Error Code (if any).Location indicates whether the error occurs in the SRH-2D Pre-processor or in SRH-2D itself.Simply click the small arrows on the right side of the column header to sort in ascending or descending order. The first three columns in the table are sortable. Opening the "*_.OUT.dat" or the "*_DIA.dat" files in a text editor will show errors in the model run. If the model wrapper has been closed, two files are generated recording the model run. Clicking the SRH-2D button will show results from the model run. Clicking the PreSRH-2D button in the model wrapper will display results from the pre-processor. During the run, errors will be listed in the SRH-2D model wrapper. NOTE: To search this web page, use CTRL+FĪn error may occur during either the Pre-SRH-2D process or during the SRH-2D process.
![nonmem forrtl severe <170> program exception stack overflow nonmem forrtl severe <170> program exception stack overflow](https://i.stack.imgur.com/R2zK0.png)
These errors will appear during the model run. This is a list of known error messages produced by SRH-2D.