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 Plotter Tabular Data | When you access the 1D sediment results the tabular data does not show up. | RESOLVED |
502 Error When Downloading GRiD Files | When attempting to download files from GRiD, the download step will always fail with error 502. Workaround: The file export was successful, so a download link to the file will be available in the user's GRiD Exports page. Select the AOI called HEC-RAS under the "Exports" tab by clicking the HEC-RAS in green. From there the file can be downloaded. | RESOLVED |
2D Bridges Connected to Cells with Internal Boundary Conditions Causes Flows to Appear Elsewhere | When a 2D bridge and an internal boundary condition are connected to the same cell, flows from the internal boundary condition are showing up at other location in the model. This limitation means that internal BC lines, georeferenced culverts or gates from other structures, or pumps should not be connected to the same 2D cell as a bridge. An example of this can be found here. HEC-RAS 6.6 will have an error check to prevent geometries with this condition from running. Workaround: If possible, construct the mesh and/or place structures such that bridges are not connected to the same cells as other structures or boundary condition lines. | RESOLVED |
Bridges In Multiple 2D Areas Prevent Unsteady Flow Simulation from Starting | When there are multiple 2D areas in a model that contain bridges, an error occurs that prevents the simulation from running: "allocatable array is already allocated". Workaround: If possible, use a single 2D area instead of multiple 2D areas with bridges. Use other SA/2D Connection types to model bridges in 2D areas. Note: This was also a bug in version 6.2, it was fixed for versions 6.3 to 6.4.1 but reappeared in version 6.5. | RESOLVED |
Avalanching Not Working in 2D Sediment | The interfaces is sending no value for the angle, so the feature is not affecting the result. This will be fixed in 6.6. | RESOLVED |
1D Sediment Results Not Reporting Tabular Data | When you run a 1D sediment file, the "Table" is blank (reports "no data to tabulate"). | RESOLVED |
Sediment Time Series Boundary Condition Causes the Model to Crash with Fixed Start Times | RAS was not writing the Fixed Start Time for the time series sediment boundary condition, which was crashing the simulation. Workaround: Synch the start time with the plan and use the Plan Start Time method. | RESOLVED |
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. | RESOLVED |
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 |
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.