HEC-HMS
q q q q q
Basic Input and Output Options Precipitation Options Unit Hydrograph Options Flood Routing Option Creating and Viewing Results and Graphs
Execution of HEC-HMS
q q q q q
Running actual projects Calibration to gage data Castro Valley case study Keegans example Linkage with GIS/NEXRAD data (HEC Geo-HMS)
Offers a variety of modeling options in order to compute UH for basin areas. Offers a variety of options for flood routing along streams. Capable of estimating parameters for calibration of each basin based on comparison of computed data to observed data
1991 Version Provides Extended Memory Support 1998 Version 4.1 is Final Release
HEC NexGen Project Begins 1990 (RAS, HMS, FDA) HEC-HMS - New GUI and Updates
First Release April 1998 q Version 1.1 Released April 1999 q Current Version 2.0.3
q
HEC-HMS Background
Purpose of HEC-HMS
Improved User Interface, Graphics, and Reporting q Improved Hydrologic Computations q Integration of Related Hydrologic Capabilities
q
Importance of HEC-HMS
Foundation for Future Hydrologic Software q Replacement for HEC-1
q
HEC-HMS Availability
Available Through HEC Vendors Available at HEC Web Site: http://www.wrc-hec.usace.army.mil Public Domain Program No Copyright on Software No Copyright on HEC Documentation Special Training Available
EXAMPLE 5.1 Small Watershed Example (HEC-1) A small undeveloped watershed has the parameters listed in the following tables. A unit hydrograph and Muskingum routing coefficients are known for subbasin 3, shown in Fig. E5.1(a). TC and R values for subbasins 1 and 2 and associated SCS curve numbers (CN) are provided as shown. A 5-hr rainfall hyetograph in in./hr is shown in Fig. E5.1(b) for a storm event that occurred on June 19, 1983. Assume that the rain fell uniformly over the watershed. Use the information given to develop a HEC-1 input data set to model this storm. Run the model to determine the predicted outflow at point B. Note that this same sample will be used later with HEC-HMS as Example 5.2. SUBBASIN NUMBER 1 2 3
UH FOR SUBBASIN 3:
150
Solution The input data set is as follows: ID **** EXAMPLE 5.1 ID **** ID **** HEC-1 INPUT DATA SET ID **** IT 60 60 19-Jun-83 1200 100 IO 4 KK SUB1 KM RUNOFF FROM SUBBASIN 1 PI 0.2 1.5 2 1 0.5 BA 2.5 LS 66 0 UC 2.5 5.5 KK SUB2 KM RUNOFF FROM SUBBASIN 2 BA 2.7 LS 58 0 UC 2.8 7.5 KK A KM COMBINE RUNOFF FROM SUB 1 WITH RUNOFF FROM SUB 2 AT A HC 2 KKA TO B KM MUSKINGUM ROUTING FROM A TO B RM 1 3 0.15 KK SUB3 KM RUNOFF FROM SUBBASIN 3 BA 3.3 LS 58 0 UI 0 200 400 600 450 300 KK B KM COMBINE FLOW FROM SUB 3 AND ROUTED TO POINT B HC 2 ZZ
150
Program Organization
Main project screen
q
Using HEC-HMS
Three components
Basin model - contains the elements of the basin, their connectivity, and runoff parameters q Meteorologic Model - contains the rainfall and evapotranspiration data q Control Specifications - contains the start/stop timing and calculation intervals for the run
q
Project Definition
q q
May contain several basin models, meteorologic models, and control specifications User can select a variety of combinations of the three models in order to see the effects of changing parameters on one subbasin
Basin Model
Basin Model
q
Based on Graphical User Interface (GUI) Click on elements from left and drag into basin area Can import map files from GIS programs to use as background Actual locations of elements do not matter, just connectivity and runoff parameters
subbasins- contains data for subbasins (losses, UH transform, and baseflow) reaches- connects elements together and contains flood routing data junctions- connection point between elements reservoirs- stores runoff and releases runoff at a specified rate (storage-discharge relation)
sinks- has an inflow but no outflow sources- has an outflow but no inflow diversions- diverts a specified amount of runoff to an element based on a rating curve - used for detention storage elements or overflows
Abstractions (Losses)
Interception Storage Depression Storage Surface Storage Evaporation Infiltration Interflow Groundwater and Base Flow
Rainfall/Runoff Transformation
q q q q
Unit Hydrograph
Definition:
q
Sub-Basin Surface Outflow Due to Unit (1-in) Rainfall Excess Applied Uniformly Over a SubBasin in a Specified Time Duration HEC-HMS Sets Duration Equal to Computation Interval
Duration of UH:
q
SCS Dimensionless Unit graph Clark Unit Hydrograph (TC & R) Snyder Unit Hydrograph User-Defined Input Unit Hydrograph ModClark Unit Hydrograph
Compute Travel Time in Open Channels and Storm Sewers based on Flow Velocities Compute Reservoir Travel Time from Wave Velocity
Kerby Method Kirpich Method Overton & Meadows SCS TR-55 Method for Shallow Concentrated Flow
Baseflow Options
recession q constant monthly q linear reservoir q no baseflow
q
Reach Routing
Flood routing methods:
Simple Lag Modified Puls Muskingum Muskingum Cunge Kinematic Wave
Hydrologic Methods
Muskingum Method q Storage Method (Modified Puls) q Lag Method
q
Storage S
Inflow Outflow
t
I - Q = (dS/dt)
Averaging at two points in time: 1 and 2
Storage-Discharge Relationships
Flow increases until a fixed level and then a flow diversion table determines rate through the weir or across the divide
Reservoir Routing
Developed Outside HEC-HMS
Storage Specification Alternatives:
Storage versus Discharge Storage versus Elevation Surface Area versus Elevation
Spillways, Low-Level Outlets, Pumps Dam Safety: Embankment Overflow, Dam Breach
Reservoirs
Pond storage with outflow pipe Orifice flow
I S
I - Q d S = d t
L e v e l P o o l R e s e r v o ir Q (w e ir flo w )
Q I
Weir flows
Q
W e ir F lo w : 3 H Q = C L/2
tim e
Elevation Data Relates to Both Storage/Area and Discharge HEC-1 Routing Routines with Initial Conditions and Elevation Data can be Imported as Reservoir Elements
Meteorologic Model
Meteorologic Model
Precipitation
EvapotranspirationET
monthly average, no evapotranspiration
user hyetograph user gage weighting inverse-distance gage weighting gridded precipitation frequency storm
Precipitation
Historical Rainfall Data Recording Gages Non-Recording Rainfall Gages Design Storms Hypothetical Frequency Storms Corps Standard Project Storm Probable Maximum Precipitation
Gage Data
Gage Data
(from project definition screen)
Precipitation gagesprecipitation data for use with meteorologic models Stream gages- observed level data to compare computed and actual results
Data must be manipulated and stored in DSS file format Grids are HRAP (NWS) or SHG (HEC)
HRAP uses spherical projections and generalized earth radius values SHG uses Albers Equal Area projections Grids cover about 1 square kilometer
run-nam e.LOG: Messages generated during execution project-nam e.RUN: List of runs, including most
recent execution time
Pathnames Consist of Parts A through F q Part A: General name, project name q Part B: Specific name, or control point q Part C: Data type (PRECIP-INC, PRECIP-CUM, FLOW, STORAGE, etc.) q Part D: Start Date q Part E: Time interval q Part F: User specified
Control Specifications
Control Specifications - Start/Stop/Time Interval
Running a project
User selects the
1. Basin model 2. Meteorologic model 3. Control ID for the HMS run
Viewing Results
q
To view the results: right-click on any basin element, results will be for that point Display of results: hydrograph- graphs outflow vs. time summary table- gives the peak flow and time of peak time-series table- tabular form of outflow vs. time
q q q
Comparing computed and actual results: plot observed data on the same hydrograph to by selecting a discharge gage for an element
Viewing Results
hydrograph
HEC-HMS Output
1.
1. 2. 3. 4. 5.
Tables Summary Detailed (Time Series) Hyetograph Plots Sub-Basin Hydrograph Plots Routed Hydrograph Plots Combined Hydrograph Plots Recorded Hydrographs - comparison
Viewing Results
HEC-HMS Output
Sub-Basin Plots Runoff Hydrograph Hyetograph Abstractions Base Flow
HEC-HMS Output
Junction Plots
Tributary Hydrographs Combined Hydrograph Recorded Hydrograph
Purpose of Calibration
Can Compute Sub-Basin Parameters Loss Function Parameters Unit Hydrograph Parameters Can Compute Stream Flow Routing Parameters Requires Gage Records