CONCEPTOS BASICOS HEC RAS

I am working on a dam breach project where Im trying to simplify a complicated model with dozens of tributaries and storage areas. In the process, Im converting a few tributaries into storage areas (which are surrounded by other storage areas). For example, I want to convert the reach below (from 5.43 to 0.55) to a storage area. We happen to have the topographic data used to generate the original model (although we dont have the original geodatabase), so were good to go.

In order to do that, we need to delineate the storage area polygon, define new storage area connections, and generate lateral structures. The new reach (now a storage area) will look like the one below.

Now we need station-elevation data for storage area connections and lateral structures. Easy, right? Well, not so fast. HEC-GeoRAS seems to have some issues exporting data when you take an existing project and try to modify shapefiles and extract data for only a portion of the entire model. It is especially difficult if youre not the one who built the model in the first place. The shortcut is to think outside GeoRAS and obtain simple 3D station-elevation points directly from a TIN or grid for the storage area or structures you need. The bad part about that is that extracting tools in ArcGIS doesnt really have an option to limit the number of points that are generated, and you end up with thousands of points that you cant really use in HEC-RAS (the limit for cross section points, storage area connection weir/embankment points, and lateral structure weir points is 500). For example, in the connection called 83Coal in the figure above, I end up with over 2300 points. Im stuck. Or so I thought It turns out that RAS automatically expands its Station Elevation table to store however many points you need. In my case, 2339

HEC-RAS will still give you an error if you try to run the model with this data (the limit of 500 points still stands for computations!), but a simple click of the Filter button you s ee in the figure above solves the problem. Voila! Hope you liked this new (for me) discovery.
Posted by Chris G. at 7:06 AM 1 comments Email ThisBlogThis!Share to TwitterShare to Facebook Labels: Connection, Filter, GeoRAS., GIS, HEC-RAS, Lateral Structures, Station-Elevation Points, Storage Areas

Reactions:
TUESDAY, OCTOBER 8, 2013

Stabilizing a Dynamic Unsteady HEC-RAS Model

Written by Chris Goodell | WEST Consultants One of the most frustrating aspects of unsteady HEC-RAS modeling can be the model stabilization process. You know, youve gone to great lengths collecting the best survey/topo data and solid hydrology. Then youve painstakingly spent hourspossibly days entered all of that data only to find that once you press the Compute button, the model crashes. The dreaded Red Bar!

Sometimes you can get your simulation to complete without crashing, but the listed numerical errors are so high that you cant with good conscience submit that as your final simulation. Either way, approaching an unsteady HEC-RAS model (especially a dynamic one) as a beginner with little experience and understanding of how to stabilize it can cause significant delays in your project and worse, completely blow up your budget. Ive uploaded two HEC -RAS projects to the following DropBox Site:https://www.dropbox.com/sh/ebbaz8es6d4ncdf/flYbMC16bP RawleyResUnstable.prj is an unsteady flow dam breach HEC-RAS project recently sent to me for help. Although the model ran to completion without crashing, it had unacceptably high errors. RawleyResStable.prj is the fully stabilized version of the model with no numerical errors. The following lists out the courses of action taken to stabilize the model. Feel free to download the Unstable and Stable models and try these techniques on your own. The links following some of these items will take you to more information about that particular technique. 1. Cross Section Spacing. The initial spacing was way too coarse. A visual check alone of the geometry schematic and profile plot should encourage you to investigate a finer cross section spacing.

Geometry Schematic

Profile Plot Samuels equation suggests anywhere from 15 ft to 50 ft spacing (depending on what bed slope you use). I interpolated to 50 ft for the entire reach.http://hecrasmodel.blogspot.com/2008/12/samuels-equation-for-cross-section.html

2. Dam Breach models typically have time steps on the order of a minute or less. This model was initially set with a computation interval of 10 minutes which is high even for the largest and slowest of dam breach models. I changed the time step to 10 seconds. The selection of 10 seconds was based on gut feel and lots of experience doing dam breach models. There are some methods for approximating good timesteps, notably the Courant Condition and Freads equation. Also, setting the cross section spacing/time step ratio equal to a representative stream velocity will get you close. In this case, the cross section spacing is 50 ft, and I was able to pull some velocities (prior to the model crashing) at about 6 ft/s. That suggests a time step of 8.3 seconds. Close enough to 10 seconds, so well stick with that. 3. I changed the downstream boundary normal depth slope from 0.01 to 0.001. Not sure what is downstream of the first cross section, but 0.01 is awfully steep and was setting

up a very low depth at the downstream boundary (which was causing instabilities).http://hecrasmodel.blogspot.com/2010/01/downstream-boundary-normaldepth.html Notice in the following profile plot of the downstream end of the reach how the water surface at the boundary cross section is below critical depth (the red dot). This creates an overestimation of the water depth at the next upstream cross section, which in turns creates some instability over the next several timesteps.

The proper way to handle this would be to find out what is downstream of your model and select a boundary condition that best represents those conditions. In absence of downstream conditions, the 0.001 slope for normal depth provides a reasonable solution. Either way, this underscores the importance of moving your downstream boundary far away from your area of interest in your study reach. That way the errors that do originate from your downstream boundary assumption will have diminished to negligible levels before impacting your area of interest.

4. In the unsteady flow editor, the initial flow and the first time step flow should always be equal. In the original model, the initial flow is left blank (which is actually okay because RAS will use the first timestep flow if left blank). However, the first time step flow is very low at 0.14 cfs. Peak discharge of your inflow hydrograph is around 600 cfs. I put in a baseflow (minimum flow) of 5% of this, which is 30 cfs. Just to be safe, I put 30 cfs in the initial flow input box as well. Its important to make sure that the 30 cfs baseflow does not have an impact on the peak of the breach outflow hydrograph. http://hecrasmodel.blogspot.com/2009/02/minimum-flow-requirements.html 5. The upstream end of your reservoir is very steep (14%). This one was easy to spot in the profile plot because of the very nice smooth profile plot followed by a sudden spike in the energy level (green dashed line) at the upstream end. Notice to that there is a corresponding supercritical solution at the upstream most cross section. These are both indications that more cross sections are needed here. http://hecrasmodel.blogspot.com/2010/01/another-reason-for-interpolated-cross.html

I added more cross sections by interpolating the steep slope at the upstream end of the reservoir (10 ft spacing).

Notice the energy spike is not completely gone, but it is much better. Refining the HTAB parameters (http://hecrasmodel.blogspot.com/2009/02/crazy-energy-grade-line.html), turning on mixed flow and bumping up n values will collectively take care of the rest of this (see numbers 8, 9, and 10 below). 7. From RS 4577 to 3791 you have your main channel defined in a small elevated side channel. The right overbank is lower in elevation than the channel.

This is problematic in RAS. Using the graphical cross section editor, I redefined the bank stations to get rid of this problem.

8. Notice now in the HTAB parameters property table, the HTAB definition begins at the elevation of the invert of the side channel that was previously defined as the main channel. There is a big gap in the computation points in the newly defined main channel. This poses problems with HEC-RAS, particularly at low discharges/stages, since RAS will have to extrapolate to obtain a solution over that range.

I readjusted the cross section HTAB parameters to reflect the new bank station definitions (I used the Copy Invert button for all cross sections). While in there, I maximized the resolution of the HTAB parameters by changing number of points to 100 and minimizing the increment as much as possible while still having full coverage of each cross section. http://hecrasmodel.blogspot.com/2009/02/crazy-energy-gradeline.html http://hecrasmodel.blogspot.com/2011/03/more-on-htab-parameters.html

9. In the figure below, notice all of the red areas in this zoomed in section of the upstream end of the reach.

These are areas that are near critical depth. I turned on the Mixed Flow option in the Unsteady Flow Analysis window, which helps stabilize the near critical depths at the upstream end of the reservoir. http://hecrasmodel.blogspot.com/2011/04/mixed-flow-regime-options-lpi-method.html If youve been following along correcting your own copy of the model, youll notice that the model now finally runs to completion without crashing. There are still a few minor errors as shown in the Computation Messages.

Its debatable whether you need to take care of these relatively small errors. Particularly for a dam breach model, where the presumed errors of the input data probably far outweigh these small numerical errors. Nevertheless, theres a sense of pride in putting out a very robust model, completely free of numerical errors. Solets continue. 10. The errors in the computation window above suggest a problem around river station 6200. That happens to be the upstream end of the reservoir and the source of the error can clearly be seen with the energy grade line and critical depth turned on.

The section at the upstream end of the reservoir is very steep at about 13.5%. In fact, thats greater than the suggested maximum slope of 10%, as stated in the HEC-RAS manuals. You can see as the pool starts to lower, the steep reach is exposed and because of the low n values, the water surface is calculated to be supercritical. Lets assume that the geometry is correct, and the upstream end of the reservoir really is that steep. Jarretts Equation suggests very high n values should be used here (~0.2), based on the bed slope and hydraulic radius (after the breach when the reservoir has drained). The original model had 0.07 and 0.035 for the overbanks and main channel, respectively. I changed all the n values in this steep reach to 0.15, because I think 0.2 might be a little overkill. http://hecrasmodel.blogspot.com/2009/12/n-values-in-steep-streams.html

Thereno errors! However, there is still a Warning about extrapolating above/beyond the rating curve at a bridge (R.S. 277).

11. To get rid of that warning, I increased the HTAB headwater maximum elevation at River Station 277 (the bridge) from 278 ft to 280 ft so that RAS doesnt have to extrapolate.

There we have it. A clean solution. No errors, no warnings.