HEC-RAS Known Issues
HEC-RAS 6.0 has been released!
Reported problems with Beta versions can be seen by choosing the Versions drop down in the upper right corner of this page.
HEC-RAS 6.0
| Issue | Description | Status 1 2 |
|---|---|---|
| DLBreach Not Included in 6.0 User Manual | The DLBreach manual was developed for the 6.0 release but omitted from the manual. It has been added to the 6.1 User Manual. | RESOLVED |
| Unsteady Computation Options and Tolerances - Boundary Condition Volume Check | The user interface table for turning on the Boundary Condition Volume Check per 2D flow area had a bug that prevented users from clicking that option on. | RESOLVED |
| Renaming a 2D area in RAS Mapper Breaks the Connection with Boundary Conditions Lines | If a 2D area is renamed in RAS Mapper, the boundary conditions for the 2D area are lost and the user has to reenter the boundary conditions in the Unsteady Flow Data editor. | IN PROGRESS |
| Unique Names with "/" and "\" cause several errors | Using slashes in the unique names for things such as 2D areas and boundary condition lines cause run time errors. In the future, these characters will not be allowed for unique names. | RESOLVED |
| Classification Polygons with "/" and "\" in the Name do not render. | Land classification naming conventions in RAS Mapper do not allow "\" or "/" in the filename. Previously, land cover import of NLCD datasets would allow slashes in the names - subsequent Classification Polygons with slashes in name would not render in Mapper. | RESOLVED |
| Resample to Single Terrain missing data | Export of RAS Terrain to a Single Terrain resulted in NoData cells in some places where stitches area used to fill in missing data. This effect can also be seen when zooming out on terrains with multiple input files. | RESOLVED |
| Courant Map Incorrect Rendering With Multiple Meshes | If the dataset had more than 1 mesh, and more than one mesh was in view, then the courant map would render incorrect values. Work around is try and only view one mesh at a time. | RESOLVED |
| Write Updated Geometry Bug | The new tool to write out a new geometry file based on the cross section change from a sediment (mobile bed) simulation does not work if the River or Reach have a space in the name. Work arounds: This does seem to work if the River and Reach do not have spaces in the name. For quasi-unsteady simulations, the legacy output option still works for this operation (button on the top-right of the XS plot). If the output file is too big to open with this editor, chose a larger output interval or fewer results parameters. Note: This also affected the Specific Gage tool. This has also been fixed. | RESOLVED |
| Pool Pass-Through Bug | The new Pool Pass-Through Method in the sediment model has a computational issue. | RESOLVED |
| Terrain Modifications Using "Replace Terrain Value" Not Obstructing Water | Users will find that water will flow through terrain modifications with the elevation type of "Replace Terrain Value", even if they are taller than the water surface elevation, and along a breakline. Use the other modes for the time being. | RESOLVED |
| Overbank Erosion Methods | The new global bed change method editor does not update the overbank erosion method when the user changes the drop down menu. | RESOLVED |
| Unsteady Sediment Table Update | HEC found and fixed a major bug in unsteady sediment. HEC-RAS 6.0 does not update the hydraulic tables in response to bed change in the mobile bed model, which fails to capture the feedback between hydraulics and bed change. | RESOLVED |
| Sediment Computation Multiplier Does Not Work for 2D Sediment | The sediment computation multiplier was not implemented in the 2D sediment transport model. The sediment computation multiplier allows for sediment to be computed at a time step larger than flow. The sediment time step is equal to the sum of N flow time steps, where N is the sediment computation multiplier. The model also enforces that the sediment computation times match the output times for output. | RESOLVED |
| Initial Condition Point/Initial Elevation for SI data sets | The initial water surface for an Initial Condition Point for SI data sets was not being handled correctly. | RESOLVED |
| Unable to plot SA/2D Structure in RASMapper when the SA/2D has differing US/DS 2D Areas | Users will not be able to plot results of an SA/2D structure in RAS Mapper if the SA/2D structure has a different 2D area for the US and the DS 2D areas. | RESOLVED |
| XS Layer → Update All Attributes Updating Attributes That Don't Exist | Users will find that the right click menu option for updating all XS attributes when editing an XS Layer will also update attributes that don't exist, such as Manning's N. Doing this will make all Manning's N values -9999, the no data value. Work around is do not use update all XS attributes menu item, and instead update attributes individually | RESOLVED |
| OK/Cancel/Apply Buttons Disappear 1366x768 Resolutions | Users using screen resolutions of 1366x768 were unable to apply projection and other options because the OK/Cancel/Apply buttons were not visible. The groundline modification editor also had this issue. | RESOLVED |
| Sheet and Splash Erosion | Sheet and splash erosion in 2D sediment is not working correctly in 6.0. There is currently no work around for this bug. The bug has been resolved and will be fixed in the next release. | RESOLVED |
| 1D Sediment Junctions | Version 6.0 includes a significant 1D sediment transport bug at junctions. This will affect all 1D sediment models with junctions. It has been fixed and will be functional in the next release. There is no good work-around. If you cannot model the system as a single reach (with flow and sediment point loads for the tributaries) or wait for the next version, we recommend using 5.0.7 for sediment models with junctions. | RESOLVED |
| Coupled 1D/2D Sediment Simulations | It is not possible to run coupled 1D/2D sediment simulations. However, a possible work around which may feasible in some situations is to run 1D and 2D sediment decoupled. For example, a 1D sediment model can be run and used to specify sediment time series for a downstream 2D sediment model. | IN PROGRESS |
| 2D Sediment Initial Bed Layer Thickness | The initial bed layer thickness is not properly assigned to Bed Gradations. The initial bed layer thickness gets assigned a large value. The work around is to use a bed layer groups and directly specify the bed layer thickness for each layer. | RESOLVED |
| 2D Bridges with multiple 2D areas | 2D Bridges are not working correctly if the model has more than one 2D area. | RESOLVED |
| 2D Bridges with 100+ cells/faces | There is a bug if a 2D Bridge has 100 or more cells/faces along the centerline of the bridge. This may show up as an access violation error. Alternately, the model may run but it may not allow any flow through the bridge. | RESOLVED |
| Lateral Structure Data Not Saving | Lateral structure data is not properly saving between the geometry file and the .hdf file. This issue will result in data not saving when you Stop Editing in RAS Mapper. HEC-RAS will warn the user, but the window will be stuck in the background (tell-tale sign is the spinning cursor in RAS Mapper). | RESOLVED |
| Georeferenced Gates with Rules Operation | Flow from georeferenced gates using the Rules capability where the Rules directly fix the flow (as opposed to the Rules controlling the height of the gate) were not always properly reporting flow in the output. The gate flow might not have been added to the Total Flow and in some situations it may not have been using the correct flow in the computations. This has been resolved for situations where the Rules directly fix the flow for a gate group. The max and min functions for gate groups have been improved but may not be as robust as directly fixing the flow. | RESOLVED |
| Geometry Flow Roughness Factors at Bridges | There is a potential bug if using geometry flow roughness factors that span a bridge. The work around is to make sure that the Roughness Factors at the start of the table are set to 1. Specifically, make sure that for flows between 0.0 and 2.0 cfs (0.06 m3/s), the roughness factor has a value of 1. | RESOLVED |
| Ineffective Flow / Blocked Obstruction Updates Not Saved | When updating ineffective flow areas / blocked obstructions data may not save. Work around is to update cross sections individually. If you wish to update all cross sections, will need to have ineffective data specified for every cross section in the model. | RESOLVED |
| Bulking-Only Interface/Non-Newtonian Method Selection | We changed the way users select the "bulking only" approach. Instead of selecting "Bulking Only" as a method, users now select "Newtonian" and then set the Cv and choose "Bulking" in the bulking method below. This changed the indexing from the drop down box, so it will impact the backward compatibility of the non-Newtonian editor. Users will have to go in and re-select their non-Newtonian methods | RESOLVED |
| Plotting From Unsteady Flow Boundary condition Tables | We are moving to a new hydrograph plotting capability. Several of the Boundary Condition Options in the Unsteady Flow Data editor will not allow the user to plot the data. | RESOLVED |
| Unable to plot Initial Condition Points | Initial Condition Points will show "No Data for Plot" in the new Hydrograph Plotter. Work around is make an identical reference point at the initial condition point and plot that instead. | IN PROGRESS |
| Default Surface Fills in RAS Mapper options not remembering interpolated/discrete | If you change one of the default map surface fills for a map, and change the type from interpolated to discrete, and then close and open RAS Mapper, RAS Mapper will not honor the discrete selection that was made earlier | RESOLVED |
| Groundline Modifications getting assigned wrong name when right click to edit | If you make a new ground line terrain modification, give it a non-default name, and then right click to edit that ground line modification, it will get a default name. | RESOLVED |
| Groundline Layers designated as a "Channel" layer still defaults to TakeHigher | If you make a new channel layer, add a new modification, and close and reopen rasmapper, and then draw a new modification, then the modification method TakeHigher will be selected instead of TakeLower | RESOLVED |
| GDAL Conflict when Opening RAS Mapper | "Error initializing the GDAL path variables. Please check HEC-RAS installation" error message is displayed when attempting to open RAS Mapper. | View Discussion |
1 RESOLVED issues are fixed and will be available in the next release.
2 IN PROGRESS issues are currently being worked on.