Jump to content
GMS, SMS, and WMS User Forum

Hogans

FHWA
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Hogans

  • Rank
    Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

2,047 profile views
  1. I am not aware of the trouble with wall boundaries, but I am fairly certain that you cannot use these as an internal mesh boundary. The reference to using them along islands and channel banks assumes that there is a hole/void in the mesh that creates an external boundary.
  2. You cannot use a wall as an internal boundary condition. If you turn on Snap Preview (Shift+Q) after selecting the BC coverage in your simulation, you will see where it is actually being applied (mapped) . If you wish to block flow across an island, you could either raise the mesh elevations, or place two arcs for a weir BC and specify a high weir elevation. The area between the two arcs is excluded from the 2D calculations and replaced with the weir calculation.
  3. If your results are varying from one output timestep to the next, your computational timestep is likely to large. Just because SRH-2D ran to completion does not indicate that the results are correct. For a steady flow simulation, review the case_INF.dat file to confirm model stability. The last two columns of data are helpful to confirm stability. If the number of wet cells is still changing or oscillating at the end of the simulation, the results are not stable. Furthermore, if the final net flow flux is not less than about 2-5% of the initial flux into the domain, convergence has not been satisfied. Using a smaller timestep will usually solve most stability issues. If not, you should review the mesh quality. Abrupt transitions from very small to large elements can cause instability, as well as elements with small interior angles. Good luck.
  4. Kieth, Since you are using such and old version of SMS, I think you will find this resolved in the current versions. The observation plots in SMS 13 have evolved significantly since SMS 11.1. Scott
  5. Don, I recommend representing this structure in the terrain rather than as a blocked obstruction. Based on what I see in the image, you could simply add an arc (breakline) in your mesh generator coverage to force your element edges to coincide with the feature. This would make sure the elevations of the feature are reflected in the mesh. If you need more detailed hydraulic information around the feature you may consider adding multiple arcs or a polygon to the mesh generator with closely space vertices, to generate a more refined mesh in this area.
  6. Aquaveo may have more details to provided, but there were some changes in SMS 12.3 and updates in SRH-2D that result in the sediment transport module not working. I know they are working on it, but the temporary fix is to download and run the sediment transport simulation in SMS 12.2.
  7. I spoke with Dr. Lai, the developer of SRH-2D, and he confirmed that the water surface elevation is a discharge weighted calculation. In other words, the computed WSEL at each element is weighted based on the discharge computed at that element divided by the total discharge across the monitoring line.
  8. If the roughness values are different for each model scenario you should create a materials coverage for each, and then use the appropriate materials coverage in the corresponding simulation.
  9. The IFACE error occurs when SRH-2D has difficulty mapping the pressure zone. The best practice is to align the boundary condition arcs so that they form a rectangle rather than a parallelogram. When structures are skewed to the channel this can be challenging and sometimes warrants slightly changing the alignment of the BC arc such that it may not perfectly align with the bridge face. The skewed mesh elements (poor mesh quality) could also cause a stability issue. The upper example should be ok, but for the lower example try to realign the mesh elements and boundary condition arcs to form a rectangle. This should solve the IFACE error.
  10. I have run into this error a few times. In each case it was a problem with my mesh or boundary condition coverage. Consider trying a new boundary condition coverage with only an inflow and outflow. If this doesn't work, regenerate your mesh. This assumes you have already consider Cody's suggestion to verify that the materials coverage extends to the limits of your mesh.
  11. Right click on the GIS layer and you can convert the shapefile data to either a scatter set or a map coverage.
  12. I have previously reported this bug. Try clicking on one of your map coverages to make it active and then try saving again. This makes the file save option available, but the scatter save as option is still not available.
×
×
  • Create New...