HEC-RAS Known Issues
HEC-RAS 6.5
Reported problems with previous versions can be seen by choosing the Versions drop down in the upper right corner of this page.
HEC-RAS 6.5
1D Sediment Results Not Reporting Tabular Data | When you run a 1D sediment file, the "Table" is blank (reports "no data to tabulate"). | IN PROGRESS |
The "Clastic" Non-Newtonian methods (Coulomb and Voellmy) are not working | We have verified that these clastic methods are not producing significantly different results from the clear-water, Newtonian simulations. Workaround: Use one of the other methods. Bingham has been effective in a wide range of situations. | IN PROGRESS |
Copy (Ctrl+C) in Attributes Table | When doing a copy in the attributes table in RAS Mapper, additional empty lines may appear when pasting. Workaround: Paste the data first into another program such as Microsoft Excel, then re-copy from that program and paste into the RAS Mapper attribute table. | RESOLVED |
Infiltration Layer not Recognized | When creating a new Infiltration layer, the Infiltration layer is not recognized by the Layer Association dialog. Workaround: Edit the Infiltration.hdf file in HDFView and rename the "LC Type" attribute on the root of the file from "LandCover" to either "InfiltrationDeficitConstantLoss", "InfiltrationSCSCurveNumber", or "InfiltrationGreenAmpt" . Workaround: Create the Infiltration layer in RAS 6.4.1. | RESOLVED |
Soils Layer not Recognized | When creating a new Infiltration layer, the Soils layer is not recognized in the Create New Infiltration dialog. Workaround: Edit the Soils.hdf file in HDFView and rename the "LC Type" attribute on the root of the file from "LandCover" to "Soils". Workaround: Create the Soils layer in RAS 6.4.1. | RESOLVED |
Slope from Measure Tool Incorrect | The RAS Mapper measure tool is reporting incorrect slope measurement. Workaround: Cut a profile of the terrain, subtract first elevation from last elevation in the table. Divide by the last station in the table. | RESOLVED |
Simplified physical breaching erodes immediately to max depth. | In at least one data set, the simplified physical breaching algorithm widens at the user-specified pace...but erodes vertically to the max extent almost immediately. | IN PROGRESS |
DL Breach computes rapid breaching width | There seem to be several issues with the current release of the DLBreach call from HEC-RAS. We are actively working on these. | IN PROGRESS |
Sediment Transport Capacity Calculator | The sediment transport capacity calculator (in the Hydraulic Design editor) computes bad values if some of the cross sections are included in the "Sediment Reach." Workaround: Select all of the cross sections in the Sediment reach. The tool appears to work if all of the cross sections are selected. | IN PROGRESS |
1D elements are not computing infiltration losses when finite volume solution is used | 1D elements are not computing infiltration losses when the finite volume method is selected. This will result in the total precipitation entering the 1D system, not excess precipitation. | IN PROGRESS |
Unable to Import WPC - QPF data in GRIB2 format | The National Weather Service's Weather Prediction Center provides 2 national gridded precipitation products in GRIB2 format: Quantitative Precipitation Estimates (QPE) and Quantitative Precipitation Forecasts (QPF). Currently, RAS is unable to import the QPF dataset due to its compression type. Workaround: Use HEC-MetVue or HEC-Vortex to convert the QPF data to DSS before use in RAS. | FUTURE VERSION |
Unable to Create Terrains from GeoTIFFs Exported from CAD Application | HEC-RAS geospatial libraries cannot determine the projection data stored in GeoTIFFs exported from a common CAD application. This results in a failure when importing the geotiff to a RAS terrain. | FUTURE VERSION |
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. |
1 RESOLVED - issues are fixed and will be available in the next release.
2 IN PROGRESS - issues are currently being worked on.
3 IMPROVED - the next version includes an incremental improvement but not a total fix.
4 FUTURE VERSION - this requires a structural change or major development. The team will add it to a future version if funding permits.