The following is a list of bugs that were found in HEC-RAS Version 5.0.7 and fixed for Version 6.0:

  1. Pilot Channel through Bridges.  If you used the Pilot channel option all the way through a bridge and were also using the Pressure and Weir flow option for high flow at the bridge, the program was using the wrong elevation for checking for pressure flow.  The results were the program could go into a pressure/weir flow calculation sooner than it should have.
  2. SA/2D Area Conn and Rating Curve. If you were running the model in metric units, and were using a rating curve at an SA/2D Area Connection, if you did not put in coordinates for the centerline the program was connecting the rating curve to the wrong cells.
  3. SA/2D Area Connections with Culverts connected to Storage Areas. The interface was allowing SA/2D Area Connections to have culverts that were lower that the bottom of the storage area.  This was causing initial conditions problems and model stability problems.  The program was using the lowest point in the storage area as the ware surface against the culvert, which then resulted in a flow being computed, that should have been zero.  This is now trapped by the software, and the user must raise the culvert above the storage area minimum or lower the storage area minimum below the culvert.
  4. Geospatial Centerlines for Gate Openings. If a user had more than one gate group in a structure (Lateral structure or SA/2D Area Connection), and they put in geospatial coordinates for the centerlines of the gates, the software was blowing up with an "Unresolved Eternal”.  The arrays for the geospatial data were not being dimensioned properly.  This has been fixed.
  5. User-defined Rules when structure is connected to 2D flow Area. There was a bug when applying Rules for structures connected to 2D Flow Areas.  Rules for a SA/2D Hydraulic Connection will work if it is connected to 1D storage areas on both sides.  If either, or both, sides are connected to a 2D flow area, the rules will not work. 
  6. Volume accounting Error. A bug was fixed in the volume accounting output for version 5.0.6, but this inadvertently caused a bug in the volume accounting for version 5.0.7.  If a user has a model with 2D areas and one or more storage areas, but no 1D reaches, the volume accounting fails to account for the final volume left in the storage areas.  It shows up as blank and interprets it as zero.  This made it appear like there was a large volume error that actually did not exist.  This was only a Volume Accounting output problem, not a computational problem.
  7. Bug in Using a Rating Curve for a Gate. If a rating curve was put in for a gate, and the user only put in two values for the rating curve, such as 0.0 and max gate opening.  Then if the user was using a time series of gate openings and put the gate at max opening the entire time.  The program was not using max gate opening, instead if water surface is below top of gate it is using max water surface to go into the curve with that as gate opening.  It should have used the user specified gate opening and just go to curve and use the flow they put in.
  8. 1D/2D Lateral structure Connection across a Bridge and using the 2D Equations to compute flow transfer. If a user connected a Lateral structure from a 1D river to a 2D flow area and was using the "Normal 2D equations" for the flow transfer.  If there are bridges, the software had a bug in that it was allowing water to leave the 2D area across the lateral structure in the bridge computational zone (Between the two cross sections that bound the bridge).  No flow was supposed to go in or out of this region, due to the fact that the 1D bridge/culvert solution cannot change the flow in the middle of the bridge/culvert.
  9. 1D/2D Lateral Structure Connection with 2D Equations for Overflow and additional hydraulic outlet (Culvert, gates, rating curve, or time series flow). If the user has a Lateral structure connected to a 2D flow area that contains one of the hydraulic outlet types (culvert, gates, rating curve, or time series of flow), and they selected to use the 2D Equations to compute the overflow, the program was only computing flow through the hydraulic outlet, and not over the weir with the 2D equations.  This was being reported as weir flow was being computed, but it was not.
  10. Internal SA/2D Hydraulic Connection issue. After entering a new internal SA/2D Area Conn inside of a 2D area, when trying to run the model it says that the internal structure is "Not connected to any cross section".  This was obviously not correct, as it is an internal structure.  To fix it the user had to re-select the head water and tailwater connections from the connection drop downs on the SA/2D Hydraulic Connection editor.
  11. Lateral Inflow not showing up in Unsteady Flow Editor. If a user had a Lateral Inflow Connected to a Storage Area, it was not always showing up in the Unsteady Flow Data editor.  This was an issue due to the flow file being used with two different geometries/Plans.  When you open the unsteady flow editor there should be a lateral inflow connection to the Storage area.  It is not showing up, however it was in the flow file.  If you ran the model it actually uses the flow and runs correctly.  You just can’t see it in the flow file.
  12. Rating Curves in SA/2D Connections - Metric Units.  If you had a metric unit’s data set and you tried to use the Rating curve option in an SA/2D Area Connection, it was not converting any of the stage and flow data to English units for the computation engine.
  13. 1D Reach connected to same 2D Area (upstream and downstream). If you had a 1D river reach directly connected to the same 2D Flow Area, both at the upstream end and downstream end, the program was getting confused on what to set for the initial conditions.