Resolved Issues

Some large models would inexplicably crash or go unstable.

The Hydraulic Design sediment budget tool (SIAM) will compute results but does not plot them either in the tabular or bar graph form.

Datasets that utilize 2D bridges (Pressure / Overtopping) and infiltration fail to run and are reporting an HDF error with subroutine READ_UN_HYDROLOGY.

Creating a RAS Terrain in RAS Mapper with the "Merge Inputs to Single Raster" not honoring tile priority (highest on top). 

Elevation update to cross sections using the Overbanks Only option in RAS Mapper fails when just updating the left overbank.  

The length of the time step inside of the DLB code is set at the start of the breach and it is not checked again. This is a bug if the length of the time step is changed during the breach as can happen if the user uses adaptive time step or adjust time step based on a series of time divisors.  

2D Bridge Scour export used approach-section WSE for the contracted section. Updated export to use the WSE at the contraction reference line. This primarily affects the computed/represented elevation of the abutment scour hole in Hydraulic Toolbox.  

If you build a 2D Bridge Scour file with the RASMapper tool and export it to the Federal Highway hydraulic toolbox, it imports into the toolbox as US Customary.   

If your model has multiple dam or levee breaches and some but not all of them use DLBreach, the model will crash.

In the 2D Bridge Scour editor for abutment scour condition A, the tool recommends the overbank contraction reference line and the automatic import button identifies the contraction overbank reference line from the reference lines assigned in contraction scour.  This should be the Contraction Channel reference line because Scour Condition A assumes that the channel migrates into the abutment.   

"Line" type modifications will sometimes not apply the correct profile when cutting a profile from a profile line or cutting a profile for face property tables.  This can happen when the "System Name" column is used.   It is inconsistent on when there is a problem and when there is not a problem. 

In DLBreach the soil internal friction input is labeled as an angle in degrees.  However, DLBreach uses the internal friction coefficient, which is the tangent of the friction angle.  The label is updated to "Internal Friction Coefficient" in version 7.0.2. 

In DLBreach grain size is labeled as mm, but passed to the DLBreach code as m.  We will convert this to mm in future versions. 

Gate flow for 2D hydraulic structures is not being computed for structures that meet all of the following conditions: (1)  the Energy Grade Line is selected for the Headwater Reference on the Weir editor, and (2) the gate is not georeferenced.  

Culvert flow for 2D hydraulic structures is not being computed for structures that meet all of the following conditions: (1) the 2D Domain equation is selected, (2) the Energy Grade Line is selected for the Headwater Reference on the Weir editor, and (3) the culvert is not georeferenced.  

If a 2D area has "Composite Classification Valeus in Cells" turned on, and table data is changed for calibration regions, then HEC-RAS will fail to recompute property tables.  

The "affected" faces shown in RAS Mapper for external boundary condition lines are inaccurate, it is only a visual bug, and does not represent actual "affected" faces. 

When a dataset contains a sluice gate in a Pipe Network and a gate on an SA/2D Connection or Lateral Structure a Fortran access violation can occur, preventing the model from running. 

In metric models, Pipe Network Side Inlet dimensions and weir coefficients are interpreted as English units in the compute engine. The impact of this is that when side inlets are entered in metric, the user will see far less inflows than expected. 

In metric models, Pipe Network Top Inlet weir coefficients are interpreted as English units in the compute engine. Note, the other parameters for Top Inlets were being converted correctly. 

When the 2D Area Option to Composite Classification Values in Cells is on, the geometry preprocessor was crashing while creating the 2D property tables.