HEC HMS - User's - Manual v4.11 20231018

HEC-HMS User's Manual
HEC-HMS Users Manual
Exported on 10/18/2023
HEC-HMS Users Manual – HEC-HMS User's Manual
Table of Contents
1 Report Documentation Page ..................................................................... 49

2 Preface ....................................................................................................... 52
3 Introduction ................................................................................................ 53
3.1 Scope .......................................................................................................... 53
3.2 History ........................................................................................................ 53
3.3 Capabilities................................................................................................. 54
3.3.1 Watershed Physical Description ............................................................... 54
3.3.2 Meteorology Description ........................................................................... 55
3.3.3 Hydrologic Simulation ............................................................................... 56
3.3.4 Parameter Estimation................................................................................ 56
3.3.5 Forecasting Future Flows.......................................................................... 57
3.3.6 Evaluating Depth-Area Effects .................................................................. 57
3.3.7 Building Frequency Curves........................................................................ 57
3.3.8 Assessing Uncertainty ............................................................................... 57
3.3.9 Sediment .................................................................................................... 57
3.3.10 GIS Connection .......................................................................................... 58
3.4 Limitations.................................................................................................. 58
3.4.1 Model Formulation..................................................................................... 58
3.4.2 Flow Representation .................................................................................. 59
3.5 References ................................................................................................. 59
4 Installing and Running the Program ......................................................... 61
4.1 Operating System Requirements .............................................................. 61
4.2 Hardware Requirements and Recommendations.................................... 61
4.3 Installation.................................................................................................. 61
4.3.1 Microsoft Windows Operating System..................................................... 62
4.3.1.1 Windows Installer....................................................................................... 62
4.3.1.2 Portable Version ........................................................................................ 63
2
4.3.2 Linux Operating System ............................................................................ 63

4.3.3 MacOS X ..................................................................................................... 64
4.4 Command Line Operation ......................................................................... 65
4.5 Running the Program................................................................................. 66
4.5.1 Microsoft Windows Operating System..................................................... 66
4.5.2 Linux Operating System ............................................................................ 66
4.5.3 Debug.......................................................................................................... 66
4.6 Managing Memory Allocation ................................................................... 67
4.7 Additional Resources................................................................................. 67
5 Overview ..................................................................................................... 68
5.1 Program Screen ......................................................................................... 68
5.1.1 Menu System ............................................................................................. 69
5.1.2 Toolbar ....................................................................................................... 77
5.1.3 Watershed Explorer.................................................................................... 79
5.1.4 Desktop....................................................................................................... 80
5.1.5 Component Editor ...................................................................................... 81
5.1.6 Message Log.............................................................................................. 82
5.2 Global Editors ............................................................................................. 82
5.2.1 Opening the Global Editor.......................................................................... 83
5.2.1.1 Subbasin Parameters: ............................................................................... 84
5.2.1.2 Reach Parameters: .................................................................................... 84
5.2.2 Filter the Element List ................................................................................ 85
5.2.3 Sorting the Element List ............................................................................ 85
5.2.4 Manually Editing Global Editor Table........................................................ 86
5.2.5 Calculator ................................................................................................... 87
5.2.6 Applying Edits............................................................................................. 88
5.2.7 Computing from Global Editor .................................................................. 88
3
5.2.8 Exporting Values from Global Editor Table .............................................. 89

5.2.9 Closing the Global Editor ........................................................................... 90
5.3 Program Settings ....................................................................................... 90
5.4 Data Conventions....................................................................................... 92
5.4.1 Saving Properties....................................................................................... 92
5.4.2 Number Formatting ................................................................................... 92
5.4.3 Date and Time Formatting ........................................................................ 93
5.4.4 Units Conversion........................................................................................ 93
5.4.5 Interpolation ............................................................................................... 94
5.5 Application Steps ....................................................................................... 94
5.5.1 Create a New Project ................................................................................. 94
5.5.2 Enter Shared Project Data ......................................................................... 94
5.5.3 Describe the Physical Watershed ............................................................. 97
5.5.4 Describe the Meteorology ....................................................................... 102
5.5.5 Enter Simulation Time Windows............................................................. 103
5.5.6 Simulate and View Results...................................................................... 104
5.5.7 Create or Modify Data.............................................................................. 106
5.5.8 Make Additional Simulations and Compare Results ............................. 107
5.5.9 Exit the Program ...................................................................................... 108
5.6 References: Overview .............................................................................. 108
6 Projects and Control Specifications ....................................................... 109
6.1 Projects..................................................................................................... 109
6.1.1 Creating a New Project............................................................................ 109
6.1.2 Opening a Project..................................................................................... 110
6.1.3 Copying a Project..................................................................................... 111
6.1.4 Renaming a Project.................................................................................. 112
6.1.5 Deleting a Project..................................................................................... 112
6.1.6 Project Properties .................................................................................... 113
6.2 Directories and Files ................................................................................ 114
4
6.2.1 Files Generated by the Program ............................................................. 114

6.2.2 Files Specified by the User ...................................................................... 116
6.2.3 Manually Entered Time-Series and Paired Data..................................... 116
6.2.4 Computed Results ................................................................................... 117
6.2.5 External Time-Series, Paired, and Grid Data........................................... 117
6.2.6 Security Limitations ................................................................................. 117
6.3 Control Specifications ............................................................................. 118
6.3.1 Creating a New Control Specifications................................................... 118
6.3.2 Copying a Control Specifications............................................................ 119
6.3.3 Renaming a Control Specifications ........................................................ 120
6.3.4 Deleting a Control Specifications ........................................................... 121
6.3.5 Time Window ........................................................................................... 123
6.3.6 Time Interval............................................................................................. 124
6.4 Importing HEC-1 Files.............................................................................. 124
6.4.1 Selecting and Processing a File .............................................................. 124
6.4.2 Unsupported Features ............................................................................. 125
6.5 Importing HEC-RAS HDF Files................................................................. 127
6.5.1 Selecting and Processing a File .............................................................. 128
6.6 References: Projects and Control Specifications .................................. 131
7 Shared Component Data ......................................................................... 132
7.1 Time-Series Data...................................................................................... 132
7.1.1 Creating a New Gage ............................................................................... 132
7.1.2 Copying a Gage ........................................................................................ 133
7.1.3 Renaming a Gage..................................................................................... 135
7.1.4 Deleting a gage ........................................................................................ 136
7.1.5 Time Windows.......................................................................................... 138
7.1.6 Data Source .............................................................................................. 142
7.1.7 Data Units ................................................................................................. 143
7.1.8 Time Interval............................................................................................. 143
5
7.1.9 Elevation ................................................................................................... 144

7.1.10 Reference Height ..................................................................................... 144
7.1.11 Latitude and Longitude............................................................................ 144
7.1.12 Manual Entry ............................................................................................ 146
7.1.13 Single Record HEC-DSS ........................................................................... 146
7.1.14 Multiple Record HEC-DSS........................................................................ 151
7.1.15 Table ......................................................................................................... 151
7.1.16 Graph ........................................................................................................ 152
7.2 Paired Data ............................................................................................... 153
7.2.1 Creating a New Paired Data Curve.......................................................... 153
7.2.2 Copying a Curve ....................................................................................... 154
7.2.3 Renaming a Curve.................................................................................... 156
7.2.4 Deleting a Curve ....................................................................................... 157
7.2.5 Data Source .............................................................................................. 159
7.2.6 Data Units ................................................................................................. 160
7.2.7 Time Intervals........................................................................................... 160
7.2.8 Retrieval From a HEC-DSS File................................................................ 160
7.2.9 Table ......................................................................................................... 165
7.2.10 Graph ........................................................................................................ 166
7.3 Grid Data................................................................................................... 167
7.3.1 Creating a New Grid ................................................................................. 167
7.3.2 Copying a Grid .......................................................................................... 168
7.3.3 Renaming a Grid....................................................................................... 170
7.3.4 Deleting a Grid.......................................................................................... 171
7.3.5 Retrieval From a HEC-DSS File................................................................ 173
7.3.6 Retrieval From ASCII or GeoTIFF Files ................................................... 178
7.3.6.1 Precipitation-Frequency Grids................................................................. 179
7.3.6.2 Precipitation Frequency Grid Importer ................................................... 180
7.4 Terrain Data.............................................................................................. 180
6
7.4.1 Creating Terrain Data............................................................................... 181

7.4.2 Copying Terrain Data ............................................................................... 183
7.4.3 Renaming Terrain Data............................................................................ 185
7.4.4 Deleting Terrain Data ............................................................................... 186
7.4.5 Associating Terrain Data with a Basin Model ........................................ 188
7.5 References: Shared Component Data .................................................... 189
8 Watershed Physical Description ............................................................. 190
8.1 Basin Models............................................................................................ 190
8.1.1 Creating a New Basin Model ................................................................... 190
8.1.2 Copying a Basin Model ............................................................................ 191
8.1.3 Renaming a Basin Model......................................................................... 192
8.1.4 Renaming Basin Model Elements ........................................................... 193
8.1.5 Deleting a Basin Model............................................................................ 195
8.1.6 Importing a Basin Model ......................................................................... 197
8.2 Basin Model Properties ........................................................................... 197
8.2.1 Local Flow ................................................................................................ 197
8.2.2 Unregulated Outputs................................................................................ 198
8.2.3 Flow Ratio................................................................................................. 198
8.2.4 Missing Flow ............................................................................................ 198
8.2.5 Unit System .............................................................................................. 199
8.2.6 Sediment .................................................................................................. 199
8.2.7 Water Quality ............................................................................................ 199
8.3 Basin Model Map ..................................................................................... 199
8.3.1 Background Maps.................................................................................... 199
8.3.2 Adjusting the View and Zooming............................................................ 201
8.3.3 Drawing Elements and Labels................................................................. 202
8.3.4 Displaying Flow Directions ...................................................................... 203
8.4 Hydrologic Elements................................................................................ 204
8.4.1 Creating a New Element .......................................................................... 204
7
8.4.2 Copying an Element ................................................................................. 205

8.4.3 Pasting an Element .................................................................................. 206
8.4.4 Cutting an Element .................................................................................. 207
8.4.5 Renaming an Element.............................................................................. 207
8.4.6 Renaming Multiple Elements .................................................................. 208
8.4.7 Deleting an Element ................................................................................. 208
8.4.8 Optional Element Properties ................................................................... 209
8.4.9 Element Inventory .................................................................................... 211
8.4.10 Finding and Selecting Elements.............................................................. 211
8.5 Flow Network ........................................................................................... 213
8.5.1 Moving Elements ..................................................................................... 213
8.5.2 Connecting and Disconnecting Elements .............................................. 213
8.5.3 Hydrologic Order ...................................................................................... 215
8.5.4 Locking Element Locations ..................................................................... 219
8.5.5 Locking Hydrologic Order........................................................................ 220
8.6 Zones ........................................................................................................ 220
8.6.1 Creating a New Zone Configuration ....................................................... 221
8.6.2 Copying a Zone Configuration ................................................................ 222
8.6.3 Renaming a Zone Configuration ............................................................. 222
8.6.4 Deleting a Zone Configuration ................................................................ 223
8.6.5 Creating a Zone in a Configuration ......................................................... 224
8.6.6 Renaming a Zone in a Configuration ...................................................... 225
8.6.6.1 Deleting a Zone from a configuration..................................................... 226
8.6.6.2 Adding Elements to a Zone ..................................................................... 227
8.6.6.3 Removing Elements from a Zone ........................................................... 228
8.6.6.4 Selecting a Current Zone Configuration ................................................. 229
8.7 Computation Points................................................................................. 232
8.7.1 Selecting Computation Points ................................................................ 232
8.7.2 Unselecting Computation Points ............................................................ 235
8
8.7.3 Selecting Calibration Parameters ........................................................... 236

8.7.4 Unselecting Calibration Parameters....................................................... 239
8.7.5 Settings for Calibration Parameters ....................................................... 240
8.7.6 Computation Point Results ..................................................................... 241
8.8 References: Watershed Physical Description ........................................ 244
9 Geographic Information .......................................................................... 245
9.1 GIS Menu .................................................................................................. 245
9.1.1 Coordinate System .................................................................................. 246
9.1.2 Terrain Reconditioning ............................................................................ 249
9.1.3 Preprocess Sinks ..................................................................................... 254
9.1.4 Preprocess Drainage ............................................................................... 255
9.1.5 Identify Streams....................................................................................... 256
9.1.6 Break Points Manager ............................................................................. 257
9.1.7 Delineate Elements .................................................................................. 258
9.1.8 Split Elements .......................................................................................... 260
9.1.9 Merge Elements ....................................................................................... 260
9.1.10 Reverse Flow Direction ............................................................................ 260
9.1.11 Georeference Existing Elements............................................................. 261
9.1.12 Import Georeferenced Elements............................................................. 261
9.1.13 Export Layers............................................................................................ 263
9.1.14 Compute Grid Cells .................................................................................. 264
9.1.15 Create Grid Cell File ................................................................................. 265
9.2 Basin Characteristics............................................................................... 267
9.2.1 Subbasin Characteristics ........................................................................ 267
9.2.1.1 Longest Flowpath (L)............................................................................... 269
9.2.1.2 Centroidal Flowpath (Lca) ....................................................................... 269
9.2.1.3 10-85 Flowpath (L10-85, S10-85)............................................................ 270
9.2.1.4 Basin Slope (S)......................................................................................... 271
9.2.1.5 Basin Relief (R)......................................................................................... 271
9
9.2.1.6 Relief Ratio (RR) ....................................................................................... 272

9.2.1.7 Elongation Ratio (El) ................................................................................ 272
9.2.1.8 Drainage Density (DD) ............................................................................. 272
9.2.2 Reach Characteristics.............................................................................. 272
9.2.2.1 Reach Slope.............................................................................................. 273
9.2.2.2 Reach Sinuosity........................................................................................ 273
9.2.2.3 Reach Relief.............................................................................................. 274
9.3 Parameter Estimation.............................................................................. 275
9.4 Coordinate Reference Systems .............................................................. 279
9.4.1 SHG Grid System...................................................................................... 279
9.4.1.1 Example .................................................................................................... 280
9.4.2 Standardized UTM Grid System.............................................................. 281
9.4.2.1 Example .................................................................................................... 282
10 Subbasin Elements .................................................................................. 283
10.1 Selecting a Discretization Method .......................................................... 283
10.1.1 None Discretization ................................................................................. 283
10.1.2 Structured Discretization......................................................................... 284
10.1.3 Unstructured Discretization .................................................................... 285
10.1.4 File-Specified Discretization.................................................................... 286
10.1.5 Viewing the Discretization Layer............................................................. 287
10.1.6 Global Editing ........................................................................................... 288
10.2 Selecting a Canopy Method .................................................................... 288
10.2.1 Dynamic Canopy ...................................................................................... 290
10.2.2 Gridded Simple Canopy ........................................................................... 291
10.2.3 Simple Canopy ......................................................................................... 292
10.3 Selecting a Snowmelt Method ................................................................ 293
10.3.1 Gridded Temperature Index..................................................................... 293
10.3.1.1 Initial Values ............................................................................................. 295
10.3.1.2 Parameter Values .................................................................................... 295
10
10.3.1.3 Required Meteorologic Model Boundary Conditions............................. 297

10.3.2 Temperature Index................................................................................... 297
10.3.2.1 Initial Values ............................................................................................. 298
10.3.3 Gridded Hybrid ......................................................................................... 302
10.3.3.1 Terrain Preprocessing ............................................................................. 303
10.3.3.2 Initial Values ............................................................................................. 304
10.3.4 Gridded Energy Balance .......................................................................... 306
10.3.4.1 Terrain Preprocessing ............................................................................. 308
10.3.4.2 Initial Values ............................................................................................. 308
10.3.5 Energy Balance......................................................................................... 310
10.3.5.1 Initial Values ............................................................................................. 311
10.4 Selecting a Surface Method .................................................................... 315
10.4.1 Gridded Simple Surface........................................................................... 317
10.4.2 Simple Surface ......................................................................................... 317
10.4.3 Dynamic Surface...................................................................................... 318
10.4.3.1 Pak & Lee Infiltration Limit ...................................................................... 319
10.4.3.2 Specified Infiltration Limit (Time-Series)................................................ 320
10.4.4 Gridded Dynamic Surface........................................................................ 321
10.5 Selecting a Loss Method ......................................................................... 322
10.5.1 A Note on Parameter Estimation ............................................................ 324
10.5.2 Deficit and Constant Loss ....................................................................... 324
11
10.5.3 Exponential Loss...................................................................................... 326

10.5.4 Green and Ampt Loss .............................................................................. 327
10.5.5 Gridded Deficit Constant Loss ................................................................ 328
10.5.6 Gridded Green and Ampt Loss ................................................................ 330
10.5.7 Gridded SCS Curve Number Loss ........................................................... 331
10.5.8 Gridded Soil Moisture Accounting Loss ................................................. 332
10.5.9 Initial and Constant Loss......................................................................... 333
10.5.10 Layered Green and Ampt Loss................................................................ 334
10.5.11 SCS Curve Number Loss ......................................................................... 338
10.5.12 Smith and Parlange Loss ........................................................................ 339
10.5.13 Soil Moisture Accounting Loss ............................................................... 341
10.6 Selecting a Transform Method ............................................................... 344
10.6.1 Clark Unit Hydrograph Transform........................................................... 345
10.6.1.1 Standard ................................................................................................... 346
10.6.1.2 Variable Parameter .................................................................................. 346
10.6.1.3 Maricopa County AZ USA ........................................................................ 347
10.6.2 Kinematic Wave Transform..................................................................... 348
10.6.2.1 Planes ....................................................................................................... 349
10.6.2.2 Subcollector and Collector ...................................................................... 350
10.6.2.3 Channel..................................................................................................... 352
10.6.3 ModClark Transform ............................................................................... 353
10.6.4 SCS Unit Hydrograph Transform ............................................................ 354
10.6.5 Snyder Unit Hydrograph Transform........................................................ 355
10.6.5.1 Standard ................................................................................................... 355
10.6.5.2 Ft Worth District ....................................................................................... 356
10.6.5.3 Tulsa District ............................................................................................ 357
10.6.6 User-Specified S-Graph Transform ......................................................... 358
10.6.6.1 Standard ................................................................................................... 359
10.6.6.2 Regression................................................................................................ 359
12
10.6.7 User-Specified Unit Hydrograph Transform ........................................... 360

10.6.8 2D Diffusion Wave Transform................................................................. 362
10.6.8.1 2D Mesh.................................................................................................... 362
10.6.8.2 2D Connections........................................................................................ 366
10.7 Selecting a Baseflow Method ................................................................. 368
10.7.1 Bounded Recession Baseflow ................................................................ 369
10.7.2 Constant Monthly Baseflow .................................................................... 370
10.7.3 Linear Reservoir Baseflow....................................................................... 371
10.7.4 Nonlinear Boussinesq Baseflow ............................................................. 373
10.7.5 Recession Baseflow ................................................................................ 374
10.8 References: Subbasin Elements ............................................................. 375
11 Reach Elements ....................................................................................... 377
11.1 Selecting a Reach Routing Method......................................................... 377
11.1.1 Kinematic Wave Routing ......................................................................... 378
11.1.2 Lag Routing .............................................................................................. 379
11.1.3 Lag and K Routing.................................................................................... 380
11.1.4 Modified Puls Routing ............................................................................. 381
11.1.5 Muskingum Routing................................................................................. 382
11.1.6 Muskingum-Cunge Routing..................................................................... 383
11.1.7 Normal Depth Routing ............................................................................. 385
11.1.8 Straddle Stagger Routing ........................................................................ 386
11.2 Selecting a Loss-Gain Method ................................................................ 387
11.2.1 Constant Loss/Gain................................................................................. 387
11.2.2 Percolation Loss/Gain ............................................................................. 388
11.3 References: Reach Elements .................................................................. 389
12 Reservoir Elements .................................................................................. 390
12.1 Selecting a Reservoir Routing Method ................................................... 390
12.2 Outflow Curve Routing............................................................................. 391
12.2.1 Storage Method ....................................................................................... 391
13
12.2.2 Initial Condition ........................................................................................ 392

12.3 Specified Release Routing....................................................................... 392
12.3.1 Storage Method ....................................................................................... 392
12.3.3 Discharge Gage Selection ....................................................................... 393
12.3.4 Discharge Limit Options .......................................................................... 394
12.4 Outflow Structures Routing ..................................................................... 394
12.4.1 Storage Method ....................................................................................... 394
12.4.3 Tailwater Method ..................................................................................... 396
12.4.4 Auxiliary Discharge Location................................................................... 396
12.4.5 Time Step Control .................................................................................... 397
12.4.6 Outlets ...................................................................................................... 397
12.4.6.1 Culvert Outlet............................................................................................ 397
12.4.6.2 Orifice Outlet ............................................................................................ 399
12.4.6.3 Spillways................................................................................................... 400
12.4.6.4 Spillway Gates.......................................................................................... 403
12.4.7 Dam Tops ................................................................................................. 405
12.4.7.1 Level Dam Top ......................................................................................... 405
12.4.7.2 Non-Level Dam Top ................................................................................. 406
12.4.8 Pumps....................................................................................................... 406
12.4.8.1 Head-Discharge Pump............................................................................. 407
12.4.9 Dam Break ................................................................................................ 408
12.4.9.1 Overtop Dam Break.................................................................................. 408
12.4.9.2 Piping Dam Break .................................................................................... 410
12.4.10 Dam Seepage ........................................................................................... 410
12.4.10.1 Tabular Seepage ...................................................................................... 411
12.4.11 Additional Release ................................................................................... 411
12.4.12 Evaporation .............................................................................................. 412
14
12.4.12.1 Monthly Evaporation................................................................................ 412

12.5 Rule-Based Operations Routing .............................................................. 413
12.5.1 Zones ........................................................................................................ 413
12.5.1.1 Storage Objective..................................................................................... 414
12.5.1.2 Rules ......................................................................................................... 414
12.5.2 Outlets ...................................................................................................... 416
12.5.2.1 General Outlet .......................................................................................... 416
12.5.2.2 Gated Orifice Outlet ................................................................................. 417
12.5.3 Spillways................................................................................................... 418
13 Source, Junction, Diversion, and Sink Elements .................................... 420
13.1 Source....................................................................................................... 420
13.1.1 Representative Area................................................................................. 420
13.1.2 Selecting an Inflow Method..................................................................... 421
13.1.3 Discharge Gage........................................................................................ 421
13.1.4 Constant Flow .......................................................................................... 421
13.2 Junction.................................................................................................... 422
13.3 Diversion................................................................................................... 423
13.3.1 Connecting Diversion Flow...................................................................... 423
13.3.2 Limiting Flow or Volume.......................................................................... 424
13.3.3 Selecting a Divert Method ....................................................................... 424
13.3.4 Constant Flow Divert ............................................................................... 424
13.3.5 Inflow Function Divert.............................................................................. 425
13.3.6 Lateral Weir Divert.................................................................................... 426
13.3.7 Pump Station Divert ................................................................................. 426
13.3.8 Specified Flow Divert ............................................................................... 428
13.4 Sink ........................................................................................................... 429
14 Meteorology Description ......................................................................... 430
14.1 Meteorologic Models............................................................................... 430
14.1.1 Creating a New Meteorologic Model ...................................................... 430
15
14.1.2 Copying a Meteorologic Model ............................................................... 431

14.1.3 Renaming a Meteorologic Model............................................................ 432
14.1.4 Deleting a Meteorologic Model ............................................................... 433
14.1.5 Importing a Meteorologic Model ............................................................ 434
14.1.6 Shortwave Radiation Method .................................................................. 435
14.1.7 Longwave Radiation Method .................................................................. 435
14.1.8 Precipitation Method ............................................................................... 436
14.1.9 Temperature Method............................................................................... 436
14.1.10 Windspeed Method.................................................................................. 437
14.1.11 Pressure Method...................................................................................... 437
14.1.12 Dew Point Method ................................................................................... 437
14.1.13 Evapotranspiration Method..................................................................... 437
14.1.14 Unit System .............................................................................................. 438
14.1.15 Missing Data ............................................................................................ 438
14.1.16 Selecting Basin Models ........................................................................... 439
14.2 Shortwave Radiation................................................................................ 440
14.2.1 Bristow Campbell..................................................................................... 440
14.2.2 FAO56 ....................................................................................................... 442
14.2.3 Gridded Hargreaves ................................................................................. 444
14.2.4 Gridded Shortwave................................................................................... 445
14.2.5 Hargreaves ............................................................................................... 446
14.2.6 Specified Pyranograph ............................................................................ 447
14.2.7 Interpolated Shortwave ........................................................................... 449
14.2.8 Reduced Solar Constant .......................................................................... 450
14.3 Longwave Radiation ................................................................................ 451
14.3.1 FAO56 ....................................................................................................... 451
14.3.2 Gridded Longwave ................................................................................... 453
14.3.3 Satterlund ................................................................................................. 454
14.3.4 Specified Pyrgeograph ............................................................................ 455
16
14.3.5 Interpolated Longwave ............................................................................ 456

14.3.6 Stefan Boltzmann Longwave .................................................................. 457
14.4 Precipitation ............................................................................................. 458
14.4.1 Frequency Storm...................................................................................... 459
14.4.1.1 Precipitation Depth Calculator ................................................................ 463
14.4.2 Gage Weights ........................................................................................... 466
14.4.3 Gridded Precipitation ............................................................................... 470
14.4.3.1 Time Shift ................................................................................................. 472
14.4.3.2 Transpose................................................................................................. 473
14.4.3.3 Bias Grid ................................................................................................... 474
14.4.4 Interpolated Precipitation........................................................................ 476
14.4.5 Inverse Distance....................................................................................... 476
14.4.6 Hypothetical Storm .................................................................................. 479
14.4.7 Specified Hyetograph .............................................................................. 482
14.4.8 Standard Project Storm ........................................................................... 484
14.5 Temperature............................................................................................. 486
14.5.1 Gridded Temperature............................................................................... 486
14.5.1.1 Time Shift ................................................................................................. 487
14.5.2 Interpolated Temperature ....................................................................... 489
14.5.3 Specified Thermograph ........................................................................... 491
14.6 Windspeed................................................................................................ 492
14.6.1 Gridded Windspeed.................................................................................. 492
14.6.2 Interpolated Windspeed .......................................................................... 493
14.6.3 Specified Anemograph ............................................................................ 495
14.7 Pressure.................................................................................................... 496
14.7.1 Gridded Pressure ..................................................................................... 496
14.7.2 Specified Barograph ................................................................................ 497
14.7.3 Interpolated Pressure .............................................................................. 498
14.7.4 Barometric Pressure ................................................................................ 500
17
14.8 Dew Point ................................................................................................. 501

14.8.1 Gridded Dew Point Temperature............................................................. 501
14.8.2 Gridded Humidity ..................................................................................... 502
14.8.3 Interpolated Dew Point Temperature ..................................................... 504
14.8.4 Interpolated Humidity .............................................................................. 505
14.8.5 Specified Dew Point Thermograph ......................................................... 507
14.8.6 Specified Humidograph........................................................................... 507
14.8.7 Precipitation Index Humidity ................................................................... 508
14.9 Evapotranspiration................................................................................... 509
14.9.1 Annual Evapotranspiration ...................................................................... 510
14.9.2 Gridded Hamon ........................................................................................ 511
14.9.3 Gridded Hargreaves ................................................................................. 512
14.9.4 Gridded Penman Monteith ...................................................................... 513
14.9.5 Gridded Priestley Taylor .......................................................................... 514
14.9.6 Hamon ...................................................................................................... 515
14.9.7 Hargreaves ............................................................................................... 516
14.9.8 Monthly Average ...................................................................................... 517
14.9.9 Penman Monteith .................................................................................... 518
14.9.10 Priestley Taylor......................................................................................... 519
14.9.11 Specified Evapotranspiration .................................................................. 520
14.10 References: Meteorology Description .................................................... 521
15 Hydrologic Simulation ............................................................................. 523
15.1 Simulation Runs ....................................................................................... 523
15.1.1 Creating a New Run ................................................................................. 523
15.1.2 Copying a Run .......................................................................................... 525
15.1.3 Renaming a Run ....................................................................................... 526
15.1.4 Deleting a Run .......................................................................................... 527
15.1.5 Importing a Run........................................................................................ 529
15.1.6 Selecting Components ............................................................................ 531
18
15.1.7 Simulation Results Output....................................................................... 531

15.1.8 Precipitation and Flow Ratios ................................................................. 533
15.1.9 Start and Save States .............................................................................. 534
15.2 Computing Results for a Run .................................................................. 535
15.2.1 Selecting a Current Simulation Run ........................................................ 536
15.2.2 Computing a Simulation Run .................................................................. 536
15.2.3 Computing to a Computation Point ........................................................ 536
15.2.4 Using Calibration Aids at a Computation Point ..................................... 538
15.2.5 Computing Multiple Runs ........................................................................ 540
15.3 Viewing Results for the Current Run....................................................... 541
15.3.1 Global Summary Table ............................................................................ 541
15.3.2 Individual Elements.................................................................................. 543
15.4 Viewing Results for Other Runs .............................................................. 549
15.4.1 Global Summary Table ............................................................................ 549
15.4.3 Element Time-Series Preview Graph ...................................................... 550
15.4.4 Time-Series Tables and Graphs .............................................................. 551
15.4.5 Changing Graph Properties ..................................................................... 552
15.5 Viewing Spatial Results ........................................................................... 553
15.5.1 Requirements for Spatial Results ........................................................... 555
15.5.2 Activate Spatial Results........................................................................... 555
15.5.3 Spatial Results Toolbar ........................................................................... 556
15.5.4 Legend, Scale Bar, and North Arrow ....................................................... 559
15.5.5 Max/Min Buttons ..................................................................................... 560
15.5.6 Export Animation and Snapshot Buttons ............................................... 560
15.5.6.1 Export Snapshot....................................................................................... 561
15.5.6.2 Export Animation ..................................................................................... 561
15.5.7 Display Settings ....................................................................................... 562
15.6 Viewing Calibration Results .................................................................... 565
19
16 Model Optimization ................................................................................. 567

16.1 Optimization Trials................................................................................... 567
16.1.1 Creating a New Optimization Trial .......................................................... 568
16.1.2 Copying an Optimization Trial................................................................. 569
16.1.3 Renaming an Optimization Trial.............................................................. 570
16.1.4 Deleting an Optimization Trial................................................................. 572
16.1.6 Entering a Time Window.......................................................................... 574
16.1.7 Search Methods: Deterministic............................................................... 574
16.1.8 Search Methods: Stochastic ................................................................... 575
16.1.9 Objective Function: Univariate, Simplex, and Differential Evolution ..... 578
16.1.10 Objective Function: Markov Chain Monte Carlo..................................... 582
16.1.11 Data Transformations ............................................................................. 582
16.1.12 Adding and Deleting Parameters ............................................................ 583
16.1.13 Specifying Parameter Information.......................................................... 592
16.1.14 Resuming an Optimization Trial.............................................................. 594
16.2 Computing Results for a Trial ................................................................. 595
16.2.1 Selecting a Current Optimization Trial.................................................... 595
16.2.2 Computing an Optimization Trial ............................................................ 595
16.2.3 Computing Multiple Trials ....................................................................... 596
16.3 Viewing Results for the Current Trial ...................................................... 597
16.3.1 Objective Function Table......................................................................... 597
16.3.2 Optimized Parameters Table .................................................................. 598
16.3.3 Parameter by Iteration Graph.................................................................. 598
16.3.4 Observed Data Graphs............................................................................. 600
16.3.5 Objective Function Graph ........................................................................ 602
16.4 Viewing Results for Other Trials ............................................................. 606
16.4.1 Trial Results.............................................................................................. 606
20

17 Forecasting Streamflow .......................................................................... 610
17.1 Forecast Alternatives............................................................................... 610
17.1.1 Creating a New Forecast Alternative ...................................................... 611
17.1.2 Creating a New Automated Forecast ..................................................... 613
17.1.3 Copying a Forecast Alternative ............................................................... 616
17.1.4 Renaming a Forecast Alternative............................................................ 617
17.1.5 Deleting a Forecast Alternative ............................................................... 618
17.1.8 Selecting Zone Configurations................................................................ 621
17.1.9 Start and Save States .............................................................................. 622
17.2 Adjusting Parameters for the Forecast .................................................. 624
17.2.1 Zone Parameter Adjustments ................................................................. 624
17.2.2 Element Parameter Overrides ................................................................. 625
17.2.3 Slider Adjustments................................................................................... 626
17.3 Subbasin Baseflow Initialization............................................................. 631
17.4 Reach Outflow Initialization .................................................................... 632
17.5 Reservoir Pool Initialization and Reset ................................................... 634
17.6 Blending Computed Flow with Observed Flow ...................................... 636
17.7 Computing Results for an Alternative..................................................... 638
17.7.1 Selecting a Current Forecast Alternative................................................ 638
17.7.2 Computing a Forecast Alternative .......................................................... 638
17.7.3 Computing to a Computation Point ........................................................ 639
17.7.4 Computing Multiple Alternatives ............................................................ 641
17.8 Viewing Results for the Current Alternative ........................................... 642
21

17.9 Viewing Results for Other Alternatives................................................... 646
17.10 Viewing Results for CWMS Alternatives................................................. 650
17.11 Viewing Spatial Results for Forecast Alternatives................................. 653
18 Depth-Area Reduction.............................................................................. 655
18.1 Depth-Area Analyses ............................................................................... 655
18.1.1 Creating a New Depth-Area Analysis...................................................... 655
18.1.2 Copying a Depth-Area Analysis............................................................... 657
18.1.3 Renaming a Depth-Area Analysis............................................................ 658
18.1.4 Deleting a Depth-Area Analysis............................................................... 660
18.1.6 Entering a Time Window and Time Interval ........................................... 662
18.1.7 Selecting Analysis Points ........................................................................ 662
18.2 Computing Results for an Analysis: Depth-Area Reduction .................. 663
18.2.1 Selecting a Current Depth-Area Analysis................................................ 663
18.2.2 Computing a Depth-Area Analysis .......................................................... 663
18.2.3 Computing Multiple Analyses ................................................................. 664
18.3 Viewing Results for the Current Analysis ............................................... 664
18.3.1 Peak Flow Summary Table...................................................................... 665
18.4 Viewing Results for Other Analyses........................................................ 669
18.4.1 Peak Flow Summary Table...................................................................... 669
22

19 Assessing Model Uncertainty ................................................................. 673
19.1 Uncertainty Analyses ............................................................................... 673
19.1.1 Creating a New Uncertainty Analysis ..................................................... 674
19.1.2 Copying an Uncertainty Analysis ............................................................ 676
19.1.3 Renaming an Uncertainty Analysis ......................................................... 677
19.1.4 Deleting an Uncertainty Analysis ............................................................ 678
19.1.7 Total Samples and Convergence ............................................................ 681
19.1.8 Adding and Deleting Parameters ............................................................ 681
19.1.9 Specifying Parameter Information.......................................................... 692
19.1.9.1 Simple Distribution................................................................................... 693
19.1.9.2 Monthly Distribution ................................................................................ 694
19.1.9.3 Regression With Additive Error ............................................................... 697
19.1.9.4 Specified Values ...................................................................................... 698
19.2 Computing Results for an Uncertainty Analysis .................................... 700
19.2.1 Choosing Output Results......................................................................... 701
19.2.2 Selecting a Current Uncertainty Analysis ............................................... 703
19.2.3 Computing an Uncertainty Analysis........................................................ 703
19.3 Viewing Results for an Analysis.............................................................. 704
19.3.1 Sampled Parameters ............................................................................... 705
20 Ensemble Simulations ............................................................................. 712
20.1 Ensemble Analyses.................................................................................. 712
23
20.1.1 Creating a New Ensemble Analysis ........................................................ 712

20.1.2 Copying an Ensemble Analysis ............................................................... 716
20.1.3 Renaming an Ensemble Analysis............................................................ 717
20.1.4 Deleting an Ensemble Analysis ............................................................... 718
20.1.5 Adding/Removing Ensemble Members.................................................. 720
20.2 Computing Results for an Ensemble Analysis ....................................... 720
20.2.1 Selecting a Current Ensemble Analysis.................................................. 720
20.2.2 Computing an Ensemble Analysis .......................................................... 721
20.3 Viewing Results for an Ensemble Analysis ............................................ 722
20.3.1 Graphical Results ..................................................................................... 723
20.3.2 Tabular Results ........................................................................................ 724
21 Erosion and Sediment Transport ............................................................ 726
21.1 Watershed Sediment Properties ............................................................. 726
21.2 Subbasin Sediment .................................................................................. 730
21.2.1 Selecting an Erosion Method .................................................................. 730
21.2.2 Build-up Wash-off..................................................................................... 731
21.2.3 Modified USLE.......................................................................................... 733
21.2.4 LA Debris Method EQ1 ............................................................................ 734
21.2.5 LA Debris Method EQ 2-5 ........................................................................ 736
21.2.6 Multi-Sequence Debris Prediction Method (MSDPM) ........................... 737
21.2.7 USGS Long-Term Debris Model .............................................................. 739
21.2.8 USGS Emergency Assessment Debris Model ........................................ 740
21.2.9 2D Sediment Transport ........................................................................... 741
21.2.10 Global Editing ........................................................................................... 743
21.3 Reach Sediment ....................................................................................... 743
21.3.1 Selecting a Sediment Method ................................................................. 744
21.3.2 Fisher's Dispersion................................................................................... 745
21.3.3 Linear Reservoir ....................................................................................... 747
24
21.3.4 Muskingum............................................................................................... 748

21.3.5 Uniform Equilibrium ................................................................................. 750
21.3.6 Volume Ratio ............................................................................................ 751
21.4 Reservoir Sediment.................................................................................. 752
21.4.2 Complete Sediment Trap......................................................................... 753
21.4.3 Specified Sediment.................................................................................. 753
21.4.4 Chen Sediment Trap ................................................................................ 754
21.4.5 Brune Sediment Trap ............................................................................... 755
21.4.6 Zero Sediment Trap ................................................................................. 756
21.5 Source Sediment...................................................................................... 757
21.5.2 Annual Load ............................................................................................. 757
21.5.3 Specified Load ......................................................................................... 758
21.6 Junction Sediment................................................................................... 759
21.7 Diversion Sediment.................................................................................. 759
21.7.2 Passage Efficiency .................................................................................. 760
21.7.3 Specified Load ......................................................................................... 761
21.8 Sink Sediment .......................................................................................... 762
21.9 Viewing Erosion and Sediment Results.................................................. 762
21.9.1 Subbasin................................................................................................... 762
21.9.2 Reach ........................................................................................................ 764
21.9.3 Reservoir................................................................................................... 766
21.9.4 Source....................................................................................................... 768
21.9.5 Junction.................................................................................................... 768
21.9.6 Diversion................................................................................................... 768
21.9.7 Sink ........................................................................................................... 768
21.10 References: Erosion and Sediment Transport ....................................... 768
25
22 Data Storage in HEC-DSS ........................................................................ 771

22.1 Descriptors ............................................................................................... 771
23 Utilities ...................................................................................................... 777
23.1 Calculator ................................................................................................. 777
23.1.1 Step 1: Select Source Variables .............................................................. 777
23.1.2 Step 2: Set Math Operation to Calculate ................................................ 778
23.1.3 Step 3: Select Destination ....................................................................... 779
23.1.4 Step 4: Processing ................................................................................... 779
23.1.5 Step 5: Calculator Complete ................................................................... 780
23.2 Clipper....................................................................................................... 780
23.2.1 Step 1: Select Source File ........................................................................ 781
23.2.2 Step 2: Select Source Grids ..................................................................... 781
23.2.3 Step 3: Select Clipping Datasource......................................................... 782
23.2.5 Step 5: Processing ................................................................................... 783
23.2.6 Step 6: Clipper Complete......................................................................... 784
23.3 Gridded Data Import ................................................................................ 784
23.3.1 Step 1: Select Files................................................................................... 784
23.3.2 Step 2: Select Variables........................................................................... 785
23.3.3 Step 3: Select Re-sampling Options........................................................ 785
23.3.5 Step 5: Processing ................................................................................... 787
23.3.6 Step 6: Import Complete.......................................................................... 787
23.4 Grid to Point Converter ............................................................................ 788
23.4.2 Step 2: Select the Zones shapefile ......................................................... 788
23.4.4 Step 4: Processing ................................................................................... 790
23.4.5 Step 5: Grid To Point Converter Complete ............................................. 790
26
23.5 Image Exporter......................................................................................... 791

23.5.2 Step 2: Set Export Location, Filename Prefix, and Format .................... 792
23.5.3 Step 3: Processing ................................................................................... 793
23.5.4 Step 4: Image Export Complete .............................................................. 793
23.5.5 Step 5: File Saved..................................................................................... 794
23.6 Normalizer ................................................................................................ 794
23.6.1 Theory ....................................................................................................... 794
23.6.1.1 Equation.................................................................................................... 794
23.6.1.2 Example 1 ................................................................................................. 795
23.6.1.3 Example 2 ................................................................................................. 795
23.6.1.4 Example 3 ................................................................................................. 796
23.6.1.5 Example 4 ................................................................................................. 796
23.6.2 Usage........................................................................................................ 797
23.6.2.1 Step 1: Select Source Variables .............................................................. 797
23.6.2.2 Step 2: Select Normal Variables ............................................................. 797
23.6.2.3 Step 3: Set Normalization Period & Normalization Interval .................. 798
23.6.3 Setting the normalization period and normalization interval ................ 799
23.6.3.1 Step 4: Select Destination ....................................................................... 799
23.6.3.2 Step 5: Processing ................................................................................... 799
23.7 Sanitizer.................................................................................................... 800
23.7.2 Step 2: Select Thresholds and Replacement Values ............................. 801
23.7.4 Step 4: Processing ................................................................................... 802
23.7.5 Step 5: Sanitizer Complete ...................................................................... 803
23.8 Time-Shifter.............................................................................................. 803
23.8.1 Usage........................................................................................................ 804
23.8.1.1 Step 1: Select Source Variables .............................................................. 804
27
23.8.1.2 Step 2: Determine the Time-Shift ............................................................ 804

23.8.1.3 Step 3: Select Destination ....................................................................... 805
23.8.1.4 Step 5: Processing ................................................................................... 805
24 Reports ..................................................................................................... 807
24.1 Standard Report ....................................................................................... 807
24.2 Statistics Report....................................................................................... 811
25 Scripting.................................................................................................... 814
26 Grid Cell File Format ................................................................................ 815
26.1 File Definition ........................................................................................... 815
27 HEC-HMS and HEC-1 Differences........................................................... 817
27.1 Recession Baseflow ................................................................................ 817
27.2 Clark Unit Hydrograph ............................................................................. 817
27.3 Muskingum Cunge Routing ..................................................................... 817
27.3.1 General Channel Properties .................................................................... 817
27.3.2 Eight Point Cross Sections...................................................................... 818
27.4 Kinematic Wave Routing ......................................................................... 818
27.5 Ogee Spillway Flow .................................................................................. 819
27.6 Green and Ampt Infiltration ..................................................................... 819
28 Terms and Conditions of Use ................................................................. 820
29 Release Notes .......................................................................................... 822
29.1 v4.11.0 Release Notes............................................................................. 822
29.1.1 New Features ........................................................................................... 822
29.1.1.1 Gridded Precipitation Storm Center Parameterization.......................... 822
29.1.1.2 Gridded Storm Transposition.................................................................. 823
29.1.1.3 Gridded Storm Optimization.................................................................... 824
29.1.1.4 Gridded Storm Uncertainty and Stochastic Storm Transposition ........ 825
29.1.1.5 Optimization of Total Storm Precipitation ............................................. 827
29.1.1.6 Spatially Variable Hypothetical Storm .................................................... 828
29.1.1.7 Precipitation-Frequency 10-min, 30-min, and 3-day depths .................. 829
28
29.1.1.8 Precipitation Frequency Depths Tabular Export .................................... 830

29.1.1.9 Interpolated Longwave Radiation, Humidity, and Atmospheric
Pressure.................................................................................................... 831
29.1.1.10 Stefan Boltzmann Longwave Radiation ................................................. 831
29.1.1.11 Reduced Solar Constant Shortwave Radiation ...................................... 831
29.1.1.12 Precipitation Index Humidity ................................................................... 832
29.1.1.13 Barometric Atmospheric Pressure ......................................................... 832
29.1.1.14 Atmospheric Pressure, Wind Speed, Humidity, Longwave Radiation, and
Net Shortwave Radiation Spatial Results ............................................... 832
29.1.1.15 Optimization Trial Improvements ........................................................... 832
29.1.1.16 Ensemble Compute ................................................................................. 835
29.1.1.17 Snow Modeling Improvements ............................................................... 836
29.1.1.18 Dynamic Surface and Gridded Dynamic Surface................................... 840
29.1.1.19 2D Diffusion Wave and Sediment Transport Enhancements................ 841
29.1.1.20 Separate Output for Linear Reservoir Baseflow Layers......................... 842
29.1.1.21 Sediment Modeling Improvements ........................................................ 843
29.1.1.22 Rule-Based Reservoir Operations and Related Features....................... 849
29.1.1.23 Drainage Area Added to the Basin Element Inventory Table ................ 852
29.1.1.24 Global Editor sorting relabeled from "Hydrologic" to "Watershed
Explorer" ................................................................................................... 853
29.1.1.25 Display global editors outside of desktop program setting .................. 854
29.1.1.26 Warnings Generated When Flow or Precipitation Ratios Are Applied .. 854
29.1.1.27 DSS 7 Migration Utility ............................................................................. 855
29.1.1.28 User Interface Themes ............................................................................ 856
29.1.1.29 Vortex Image Exporter ............................................................................. 856
29.1.2 Bugs Fixed ................................................................................................ 856
29.1.2.1 Snowmelt Parameter Optimization Trials .............................................. 857
29.1.2.2 Snowmelt Uncertainty Analyses ............................................................. 857
29.1.2.3 Subbasin Point Storm Depths would not Clear in Frequency Storm
Meteorologic Model................................................................................. 857
29
29.1.2.4 Manual Entry Paired Data Values were not being Saved ...................... 857
29.1.2.5 Aborted Simulations when New Basin Models Contained Subbasin
Elements Set to use the None Discretization Method........................... 857
29.1.2.6 Re-delineating Subbasins that use the 2D Diffusion Wave Transform
Method...................................................................................................... 858
29.1.2.7 Using Reservoir Elements with a Tailwater Option within the CAVI/HEC-
WAT Model Linking Editor ....................................................................... 858
29.1.2.8 Calibration Summary Table Values are Blank When Element Names
Contain Commas ..................................................................................... 858
29.1.2.9 Exporting Table to a non *.csv File Resulted in Corrupt File ................. 858
29.1.2.10 Not Including *.crs File with a Precipitation Grid Resulted in Abort with
no Message.............................................................................................. 858
29.1.2.11 Frequency Precipitation Calculator Aborted with no Message if *.dss File
Was Provided as Source for Precipitation Frequency Grid Data .......... 858
29.1.2.12 Reach Characteristics Table Shows As Blank When a non-Reach
Element is Selected in the Watershed Explorer ..................................... 859
29.1.2.13 Subbasin Characteristics Computations are Aborted with Missing GIS
Data........................................................................................................... 859
29.1.2.14 Modified Puls routing method requiring Elevation-Discharge curve .... 859
29.1.2.15 Time-series selection for Uncertainty Analysis not stored ................... 859
29.1.2.16 Meteorologic time-series not selectable in output results dialog ........ 859
29.1.2.17 Error 10000 when copying and pasting basin elements ....................... 859
29.1.2.18 Precipitation grid time shift with non-gridded subbasins ..................... 860
29.1.2.19 v2.2 project hangs on open ..................................................................... 860
29.1.2.20 Connect upstream subbasin to downstream junction for subbasin-split
with insert junction setting on................................................................. 860
29.1.2.21 Switching data source to *.dss for grid data would not save to file..... 860
29.1.2.22 Error 10000 when running a frequency analysis compute.................... 860
29.1.2.23 Old DSS output remained after changing the number of samples and
recomputing an uncertainty analysis...................................................... 860
29.1.2.24 Program hangs on open when attempting to forward migrate pre-v4.3
projects with groundmelt pattern in temperature-index snowmelt ...... 860
30
29.1.2.25 Incorrect error message displayed with FAO56 shortwave and longwave
radiation methods.................................................................................... 861
29.1.2.26 Selecting a 2D Connection as an Reservoir Auxiliary Connection........ 861
29.1.2.27 Global editors not opening for multiple basins with similar names ..... 861
29.1.2.28 Terrain reconditioner stalls at times when a smooth drop buffer is
specified ................................................................................................... 861
29.1.2.29 Filtered entries in File Reference Dialog not editable ............................ 861
29.1.2.30 2D Connection description would load to Subbasin description.......... 861
29.1.2.31 Switching between 2D Connection nodes in different basins would lead
to errors .................................................................................................... 861
29.1.2.32 Optimization Trial plots, if open, would not update when the objective
time-series and statistic were changed.................................................. 861
29.1.2.33 Temperature node was not displayed in results for gridded subbasin .862
29.1.2.34 Missing Resource for Error 21487 .......................................................... 862
29.1.2.35 Sediment Results with AGU 20 were not properly calculated............... 862
29.1.2.36 Incorrect maximum SWE values saved for an uncertainty analysis..... 862
29.1.2.37 Grid to Point tool not correctly computing averages for shapefiles with
multiple polygons..................................................................................... 862
29.1.2.38 Error in Specified ET when compute buffer length is less than simulation
time window ............................................................................................. 862
29.1.2.39 Rule-Based Reservoir Route method aborts when nothing is
changed .................................................................................................... 862
29.1.2.40 Empty paired data curves causing a fatal error ..................................... 863
29.1.2.41 Unknown error when a compute had None basin model, meteorological
model or specifications ........................................................................... 863
29.1.2.42 Setting independent parameter to none in uncertainty editor for
regression with additive error would not save ....................................... 863
29.1.2.43 New checks added to the Bilinear Interpolation method ...................... 863
29.1.2.44 Debris Flow does not compute sediment when only one runoff value is
above threshold value.............................................................................. 863
29.1.2.45 Flaky UI behavior with rule-based reservoir UI ....................................... 863
31
29.1.2.46 Synchronize Clark transform component editor and global editor

changes .................................................................................................... 863
29.1.2.47 Header - data mismatch when reordering columns within the Global
Summary Results Table........................................................................... 864
29.1.2.48 Synchronize Snow Method Global Editor Changes ............................... 864
29.1.2.49 Using the Field Calculator to Estimate Snow Method Parameters ...... 864
29.1.2.50 LA Debris EQs 2-5 did not work with a gridded subbasin...................... 864
29.1.2.51 Correct graph editor window titles for optimization parameter and
frequency analysis results....................................................................... 864
29.1.2.52 USGS Long Term Model Global Editor.................................................... 864
29.1.2.53 Changing Linear Reservoir baseflow to another baseflow method ..... 864
29.1.2.54 Global Editors reflect unit system changes ........................................... 864
29.1.2.55 Use Precipitation Parameters for Regression with Additive Error........ 865
29.1.2.56 File References table filtering for non-DSS grid ..................................... 865
29.1.2.57 Jython scripting against the Windows-installed version of HEC-HMS. 865
29.1.2.58 Missing Observed Data plots for maximization goal optimization ...... 865
29.1.2.59 Units reverting when trying to change for Paired Data.......................... 865
29.1.2.60 Global Editors do not track rename ........................................................ 865
29.1.2.61 Attempts to rename a basin or meteorological model to a name that is
already in use would remove the basin or meteorological model from the
project....................................................................................................... 865
29.1.2.62 Decreasing number of iterations in optimization search sometimes
caused unknown error ............................................................................. 866
29.1.2.63 Automatic removal of empty values when pasting from Excel/CSV/Text
causes data misalignment ...................................................................... 866
29.1.2.64 Broken functionality in Uncertainty Analysis results graphs................. 866
29.1.2.65 No error message for incorrectly defined objective function time
window ..................................................................................................... 866
29.1.2.66 Point/Zoom mouse adapter in results plots .......................................... 866
29.1.2.67 Observed sediment load was not accessible from the results tab ...... 866
29.1.2.68 Missing values when using Output Control............................................ 866
32
29.1.2.69 Basin and Met Models did not track renames of Gridded Data and Paired
Data........................................................................................................... 866
29.1.2.70 Graphs did not open from basin map..................................................... 867
29.1.2.71 Graph results shown as out-of-date ....................................................... 867
29.1.2.72 Sediment results differ with different buffer size .................................. 867
29.1.2.73 Changing simulation time window caused differences in debris flow
calculations .............................................................................................. 867
29.1.2.74 Simulation fails when using ratio of precipitation ................................. 867
29.1.2.75 Results graph for subbasin with a 2D connection wouldn't display
properly..................................................................................................... 867
29.1.2.76 Results graphs for reservoir components did not display .................... 867
29.1.2.77 Drop in Pak & Lee Infiltration Limit ......................................................... 867
29.1.2.78 Muskingum-Cunge Global Editor table would not appear..................... 868
29.1.2.79 Error looking for time-series gage record when running CWMS forecast
in HMS standalone................................................................................... 868
29.1.2.80 Renaming Parameter Value Sample drops selection from Uncertainty
Analysis Parameter editor panel............................................................. 868
29.1.2.81 Copying Parameter Value Sample fails with Error 10000 ..................... 868
29.1.2.82 User Interface Typo When Copying Simulations ................................... 868
29.1.2.83 HEC-HMS as first in program order for CWMS/HEC-RTS model causing
Error 10000............................................................................................... 868
29.1.2.84 Gridded loss methods fail when parameter grids use another unit
system ...................................................................................................... 868
29.1.2.85 Check parameters missing for gridded loss methods .......................... 869
29.1.2.86 Gridded records with invalid values cause Automated Forecast to
fail ............................................................................................................. 869
29.1.2.87 Terrain Reconditioner fails with large terrain rasters ............................ 869
29.1.2.88 Unknown error when changing between basin models in optimization
trials .......................................................................................................... 869
29.1.2.89 Incorrect sediment statistics in Global Summary.................................. 869
29.1.2.90 Changes in 2D connection outlet editor parameters didn't notify results
and cause recompute on next run .......................................................... 869
33
29.1.2.91 Uncertainty Analysis Output Control dialog fails to open when basin
model does not contain spatial 2D features .......................................... 869
29.1.2.92 Zero diameter in Gradation Curve yields erroneous results.................. 870
29.1.2.93 Unable to open Element Graph when Element Summary Table and/or
Element Time-Series Table were open ................................................... 870
29.1.2.94 Sediment Discharge with No Outflow from Reservoir........................... 870
29.1.2.95 Reservoir volume reduction did not use Cobble and Boulder grain
sizes.......................................................................................................... 870
29.1.2.96 Suspended sediment did not settle to bottom of reservoir .................. 870
29.1.2.97 Simulation stalls when computing sediment in reach with Kinematic
Wave route method.................................................................................. 870
29.1.3 Known Issues ........................................................................................... 871
29.1.3.1 Interpolated Meteorologic methods re-compute grids when there are
changes to parameters in the basin model............................................ 871
29.1.3.2 Time series results table doesn't open for time series with different end
time ........................................................................................................... 871
29.1.3.3 Cannot compute sediment and unregulated flow in the same basin
model ........................................................................................................ 871
29.1.3.4 Draw properties editor for raster layers does not show up for some non
US region .................................................................................................. 871
29.1.3.5 Occasional erroneous precipitation when using subbasins with multi-
part feature geometries and HMR52 precipitation method .................. 871
29.1.3.6 Occasional Aborted Computes when Using Energy Budget Snow....... 871
29.1.4 Beta Releases........................................................................................... 872
29.2 v.4.10.0 Release Notes............................................................................ 908
29.2.1 New Features ........................................................................................... 908
29.2.1.1 Frequency Analysis Compute ................................................................. 908
29.2.1.2 Interpolated Meteorology ........................................................................ 909
29.2.1.3 Snow Migration ........................................................................................ 911
29.2.1.4 Cached Meteorology................................................................................ 914
29.2.1.5 Meteorologic Grid Time Shift .................................................................. 914
29.2.1.6 Frequency Storm Enhancements............................................................ 915
34
29.2.1.7 Hypothetical Storm Computed Depth Area Checks .............................. 919

29.2.1.8 Legend, Scale Bar, and North Arrow ....................................................... 920
29.2.1.9 Time Series Plot Enhancements............................................................. 920
29.2.1.10 Display Minimum and Maximum Spatial Results .................................. 921
29.2.1.11 Export Spatial Results.............................................................................. 921
29.2.1.12 Brune Trap Efficiency Method................................................................. 922
29.2.1.13 Dynamic Reservoir Volume Reduction Method ..................................... 922
29.2.1.14 Simplex Optimization Improvements ..................................................... 923
29.2.1.15 Resume Differential Evolution Optimization .......................................... 923
29.2.1.16 Normalized Nash-Sutcliffe Efficiency Optimization Objective
Function.................................................................................................... 924
29.2.1.17 Peak-Weighted Variable Power Optimization Objective Function ........ 924
29.2.1.18 Calibration Results Map Layer for Flow and SWE ................................. 925
29.2.1.19 Global Basin Editors................................................................................. 925
29.2.1.20 Snowmelt Plot .......................................................................................... 926
29.2.1.21 Air Temperature Spatial Result ............................................................... 927
29.2.1.22 2D Diffusion Wave Transform and 2D Sediment Transport
Enhancements ......................................................................................... 928
29.2.1.23 Basin Element Area Variable Added to the Global Editor Expression
Calculator ................................................................................................. 928
29.2.1.24 Units Added to Slopes in the Subbasin and Reach Characteristics
Editors....................................................................................................... 929
29.2.1.25 Added Ability to Enable/Disable Messages to OS Console in Program
Settings..................................................................................................... 929
29.2.1.26 Improvements added for Processing and Applying Gridded
Temperature............................................................................................. 929
29.2.1.27 Relaxed Requirement for User-Defined Pattern Hypothetical Storm
Patterns to be Strictly Increasing............................................................ 929
29.2.1.28 Added File Override Warning and File Saved Dialogs............................ 929
29.2.1.29 Exposed Differential Evolution Initial Random Seed in the User
Interface ................................................................................................... 930
35
29.2.2 Bugs Fixed ................................................................................................ 930

29.2.2.1 Optimization Trial would Fail to Find Reasonable HMR 52 Storm
Parameters when using the Simplex Search Method............................ 930
29.2.2.2 No evapotranspiration computed when gridded meteorologic methods
are combined with non-gridded transform............................................. 930
29.2.2.3 Sliver Polygons within the Subbasin Boundary would Generate
Unreasonable Flow when Applying the HMR 52 Storm......................... 930
29.2.2.4 Failure to Copy Terrain when Reprojection Required ............................ 931
29.2.2.5 Raster Properties Editor Minor UI Fixes ................................................. 931
29.2.2.6 Hamon Evapotranspiration Method will Compute without Temperature
Method...................................................................................................... 931
29.2.2.7 Initial Outflow Parameter was not Available for Kinematic Wave
Routing...................................................................................................... 931
29.2.2.8 Reach Characteristics not Fully Computing after Re-delineation of an
Existing Basin........................................................................................... 931
29.2.2.9 Spatial Results would not be Displayed in Basin Models that Mix Clark
and ModClark Transform Methods. ....................................................... 931
29.2.2.10 Calibration Results (Flow) Would Not Be Displayed if One Out of Many
Subbasin Does Not Have an Observed Flow.......................................... 932
29.2.2.11 Color Scales Updated to Reflect Moriasi ET. al. 2007 and 2015
Performance Evaluation Criteria ............................................................. 932
29.2.2.12 Illegal Character in File Path would Freeze the Program ...................... 932
29.2.2.13 Error 10000 When Loading Project Using Uncertainty Analysis With
Layered Green-Ampt Loss ....................................................................... 933
29.2.2.14 Optimization Trial Parameters With Lower Bounds Less Than Upper
Bounds Incorrectly Throwing Error 17506: "Maximum value is less than
minimum value for parameter" ............................................................... 933
29.2.2.15 Paths to Some Grid Data and Terrain Data not Updating when Renaming
Project....................................................................................................... 933
29.2.2.16 Hypothetical Storm Becomes Uneditable After Renaming Basin......... 933
29.2.2.17 Hypothetical SCS-Type and Area-Dependent Pattern Storm does not
Compute Following a Run with Precipitation Method Set to Precipitation-
Frequency Grid ......................................................................................... 933
36
29.2.2.18 Map Did Not Display the Updated Identified Streams When the Stream
Threshold Was Updated .......................................................................... 934
29.2.2.19 Some Reservoir Element Time-Series Table Fails to Open ................... 934
29.2.2.20 Non-SHG Albers gridded precipitation compute fail ............................. 934
29.2.2.21 Raster Properties Editor to Use Basin Map Tooltip Precision for
Precision................................................................................................... 934
29.2.2.22 Error 10000 When No Parameter Set In Uncertainty Analysis .............. 934
29.2.2.23 Error 46551 When Los Angeles Debris Method EQ 2-5 is selected for
areas out of 3.0 to 200.0 square miles................................................... 934
29.2.2.24 Rename Project Drops Non-HEC-HMS files Located in the Project
Directory ................................................................................................... 934
29.2.2.25 Negative flows computed when Diversion has no Downstream
Element..................................................................................................... 935
29.2.2.26 Animation Framerate Did Not Change When Saved.............................. 935
29.2.2.27 Debris Volume Did Not convert for each grain size based on the unit
weight ....................................................................................................... 935
29.2.2.28 Reach Hydraulic State for Sediment Routing......................................... 935
29.2.2.29 Muskingum-Cunge Routing on Second Pass through Stream
Network .................................................................................................... 935
29.2.2.30 Kinematic Wave Routing ......................................................................... 935
29.2.2.31 Kinematic Wave Routing and Sediment Calculations ........................... 935
29.2.2.32 Sediment Deposition Limit ...................................................................... 935
29.2.2.33 Volume Ratio Sediment Routing ............................................................. 936
29.2.2.34 Failure to Abort Compute when Gridded Hamon ET Encountered Missing
Temperature Data .................................................................................... 936
29.2.2.35 Meteorology Model Component Editor Basins Tab Did Not Respond to
Method Selection ..................................................................................... 936
29.2.2.36 Import Georeferenced Elements could cause HEC-HMS to crash ....... 936
29.2.2.37 2D Diffusion Wave Component Editor Unit Labels ................................ 936
29.2.2.38 Standard Report Fails to Generate Report for Depth-Area Analysis
Simulations............................................................................................... 936
29.2.2.39 Spatial Results Fail to Update when Computing to Point...................... 937
37
29.2.2.40 Draw Properties for Shapefiles Not Saving Correctly............................ 937

29.2.2.41 2D Diffusion Wave and Gridded Loss Methods ..................................... 937
29.2.2.42 User Specified Pattern Hypothetical Storm - Bad Interpolation
Values ....................................................................................................... 937
29.2.2.43 Failure to Update all Subbasins when Changing Discretization Method
from File-Specified to Structured............................................................ 937
29.2.2.44 Failure to Compute Downstream Elements when Computing to a
Computation Point................................................................................... 937
29.2.2.45 Depth Area Analysis Time-Series Results for Elements using Special
Characters in Element Names ................................................................ 938
29.2.2.46 Difficulty Moving a Break Point............................................................... 938
29.2.2.47 Feature Labels for Shapefiles ................................................................. 938
29.2.2.48 Store Gridded State Variable Results Option Removed from Program
Settings..................................................................................................... 938
29.2.2.49 Gridded Temperature with non-Gridded Hamon ET .............................. 938
29.2.2.50 Undefined NoData Value in the Base Elevation Raster ......................... 938
29.2.2.51 Area Reduction Factor Paired Data Incorrect Unit Conversion............. 939
29.2.2.52 Null Pointer Exception thrown in Optimization Trial Editor ................... 939
29.2.2.53 Optimization results get lost after editing search criteria and force
computing ................................................................................................ 939
29.2.2.54 Change Method to Multi-Sequence Debris Prediction Method in the
Global Editor............................................................................................. 939
29.2.2.55 Optimization Trial Continuation Overrides Force Compute .................. 939
29.2.2.56 Warning 15303 Aborted Run When Attempting to Run a Simulation With
a New Subbasin ....................................................................................... 939
29.2.2.57 Cumulative Volume Flatlines for Muskingum-Cunge Channels in Long
Simulations............................................................................................... 939
29.2.2.58 Special Characters in Meteorologic Model Name ................................. 940
29.2.3 Beta Releases........................................................................................... 940
29.3 v.4.9.0 Release Notes .............................................................................. 956
29.3.1 New Features ........................................................................................... 956
29.3.1.1 Multiple Element Merge........................................................................... 956
38
29.3.1.2 Enhanced Element Split........................................................................... 957

29.3.1.3 Basin Reproject ........................................................................................ 958
29.3.1.4 Automated Forecast ................................................................................ 959
29.3.1.5 Output Control.......................................................................................... 960
29.3.1.6 Generalized Meteorologic Processes..................................................... 961
29.3.1.7 Basin-Meteorology Linking...................................................................... 961
29.3.1.8 Normalizer Utility ..................................................................................... 962
29.3.1.9 Gridded Data Processing Utilities ........................................................... 963
29.3.1.10 Generalized Extreme Value and Four-Parameter Kappa Distributions. 964
29.3.1.11 Constant Value Error Term - Regression With Additive Error................ 964
29.3.1.12 Additional Baseflow Parameters Available in Uncertainty Analysis..... 965
29.3.1.13 Simple Canopy Crop Coefficient Available in Optimization Trial and
Uncertainty Analysis ................................................................................ 965
29.3.1.14 Global File Reference Table .................................................................... 965
29.3.1.15 Default Behavior when File is Missing.................................................... 966
29.3.1.16 Visual Cues for File References .............................................................. 966
29.3.1.17 2D Diffusion Wave Transform Enhancements....................................... 967
29.3.1.18 2D Flow Support for macOS and Linux................................................... 967
29.3.1.19 Pre-packaged Native Dependencies for Linux ....................................... 967
29.3.1.20 Optimization using Snow Water Equivalent Time Series ...................... 968
29.3.1.21 Maricopa Tools ........................................................................................ 968
29.3.1.22 Debris Yield Global Editors ...................................................................... 968
29.3.1.23 Calibration Summary Table..................................................................... 969
29.3.1.24 Differential Evolution Optimization Search Method .............................. 969
29.3.1.25 Optimization Data Transforms................................................................ 969
29.3.1.26 Spatial Results Tooltips and Time Series............................................... 970
29.3.1.27 2D Sediment Transport ........................................................................... 971
29.3.1.28 Rename Basin Model Elements .............................................................. 972
29.3.1.29 Updated Raster Display Settings Editor.................................................. 973
39
29.3.1.30 DSS Grid Record Validator....................................................................... 974

29.3.2 Bugs Fixed ................................................................................................ 975
29.3.2.1 Subbasin and Reach Characteristics Not Sorted Correctly................... 976
29.3.2.2 Outflow for Normal Depth Reach Routing Method Equal to Zero......... 976
29.3.2.3 Flow Rate Threshold value in Debris Yield Methods ............................. 976
29.3.2.4 No-Data Value Dropped When Computing A Reconditioned Terrain ... 976
29.3.2.5 Using the Terrain Reconditioning Tool on a Basin Model Name that
Contains Hyphens.................................................................................... 976
29.3.2.6 Observed Stage Time Series ................................................................... 976
29.3.2.7 Importing a 2D Mesh ............................................................................... 976
29.3.2.8 Renaming a Subbasin that Uses the 2D Diffusion Wave Transform .... 977
29.3.2.9 Standard Report Unable to Generate Report for Depth Area
Simulations............................................................................................... 977
29.3.2.10 Subbasin latitude and longitude assignment after delineation ............ 977
29.3.2.11 Temperature Index Snowmelt Spatial Results....................................... 977
29.3.2.12 Univariate Search Parameter Value Unit Conversions .......................... 977
29.3.2.13 CAVI/HEC-RTS Annual Pattern Paired Data Issue................................. 978
29.3.2.14 Tabulating Results for a 2D Connection................................................. 978
29.3.2.15 Gridded Curve Number Loss Method ..................................................... 978
29.3.2.16 Using an Objective Function that Conflicts with the Optimization Trial
Compute Window..................................................................................... 978
29.3.2.17 Standard Report Failure Due to Error When Attempting to Reformat
Project's Title............................................................................................ 978
29.3.2.18 Standard Report Missing Subbasins ...................................................... 978
29.3.2.19 Malformed State Serialization with Gridded Soil Moisture Accounting
Loss Method ............................................................................................ 979
29.3.2.20 Renaming ASC/GeoTIFF grids from the Grid Data Manager ................ 979
29.3.2.21 The Percent Impervious Area Adjustment was Applied Twice to Losses
Sent to the Linear Reservoir Baseflow Method...................................... 979
29.3.2.22 Optimization Trial Returning Parameter Values Outside the User-
Specified Range ....................................................................................... 979
40
29.3.2.23 Selecting a New Downstream Connection............................................. 979

29.3.2.24 Copying a Maximization Goal Optimization Trial Causes a Time Window
Error .......................................................................................................... 979
29.3.2.25 Grid Editor Panel fails to open on Ubuntu .............................................. 980
29.3.3 Known Issues ........................................................................................... 980
Method...................................................................................................... 980
29.3.3.2 Grid-to-Point-Converter & Calculator Utility ............................................ 980
29.3.4 Beta Releases........................................................................................... 980
29.4 v.4.8.0 Release Notes .............................................................................. 987
29.4.1 New Features ........................................................................................... 987
29.4.1.1 Build Walls/Burn Streams ....................................................................... 987
29.4.1.2 Subbasin Characteristics Layer Display and Export .............................. 989
29.4.1.3 Junctions "Snap to Downstream" and Export ........................................ 989
29.4.1.4 USGS Emergency Assessment Debris Model ........................................ 990
29.4.1.5 Los Angeles Debris Method EQ 2-5 ........................................................ 991
29.4.1.6 Flow Rate Threshold for Debris Yield Methods ..................................... 993
29.4.1.7 Unregulated Outputs................................................................................ 993
29.4.1.8 New Linear Reservoir Baseflow Option when Paired with the 2D
Diffusion Wave Transform Method ........................................................ 994
29.4.2 Bugs Fixed ................................................................................................ 995
29.4.2.1 Sample project extract from Help | Install Sample Projects ................. 995
29.4.2.2 Import from projection file in Gridded Data Import Wizard................... 995
29.4.2.3 Grid cell file validation logic .................................................................... 996
29.4.2.4 Out of memory issue when Store gridded state variable results program
option is turned on ................................................................................... 996
29.4.2.5 Reach characteristics compute failure when reach name is null ......... 996
29.4.2.6 Subbasin can-merge failure with self-intersecting polygons ................ 996
29.4.2.7 Subbasin merge failure with self-intersecting polygons ....................... 996
29.4.2.8 Frequency storm re-compute after parameterization change .............. 996
41
29.4.2.9 Green & Ampt display keys in Optimization Trial compute................... 996
29.4.2.10 Alphabetical sort in new global editor framework ................................. 997
29.4.2.11 Failure to launch from CAVI/HEC-WAT after successive launch
attempts ................................................................................................... 997
29.4.2.12 CAVI/HEC-WAT Internet Maps issue...................................................... 997
29.4.2.13 Missing Coordinate Reference System (CRS) for 2D Mesh .................. 997
29.4.2.14 Sediment transport time series write error ............................................ 997
29.4.2.15 Basin copy with structured discretization .............................................. 997
29.4.3 Beta Releases........................................................................................... 997
29.4.4 General Acknowledgments ................................................................... 1002
29.5 v.4.7.1 Release Notes ............................................................................ 1003
29.5.1 Features.................................................................................................. 1003
29.5.1.1 Enhanced macOS distribution............................................................... 1003
29.5.2 Bug Fixes ................................................................................................ 1003
29.5.2.1 Special characters in project name when generating standard
report ...................................................................................................... 1003
29.5.2.2 Notes and warnings control when called via the HMS command
server ...................................................................................................... 1003
29.5.2.3 Project Save As and CWMS / HEC-WAT import missing grid cell
file ........................................................................................................... 1003
29.5.2.4 Grid cell file read fails when grid cell file has no extension ................ 1003
29.5.2.5 Grid cell file validation fails when subbasins within the grid cell file are
denoted with all caps............................................................................. 1004
29.5.2.6 Characteristics compute fails when characteristic value is NaN or
Infinity ..................................................................................................... 1004
29.5.2.7 Met mode tree not updated after initialization .................................... 1004
29.5.2.8 Tool tip settings not reflected in basin map ........................................ 1004
29.5.2.9 Spatial Results file grows with each compute ..................................... 1004
29.5.2.10 2D Diffusion Wave spatial results visualization wet area fraction set
incorrectly............................................................................................... 1004
29.5.2.11 2D Diffusion Wave discretization erroneous error message .............. 1005
42
29.5.2.12 2D Diffusion Wave computed results discrepancy.............................. 1005

29.6 v.4.7.0 Release Notes ............................................................................ 1005
29.6.1 New Features ......................................................................................... 1005
29.6.1.1 2D Diffusion Wave transform................................................................ 1005
29.6.1.2 Discretizations ....................................................................................... 1007
29.6.1.3 Basin characteristics ............................................................................. 1009
29.6.1.4 Expanded ASCII/GeoTIFF grid support ................................................ 1009
29.6.1.5 GIS parameter estimation ..................................................................... 1010
29.6.1.6 Gridded Data Import Wizard.................................................................. 1013
29.6.1.7 Spatial results visualization .................................................................. 1013
29.6.2 Bug Fixes ................................................................................................ 1015
29.6.2.1 Reservoir storage is incorrect when using FT:FT2 or M:M2 elevation-area
function................................................................................................... 1015
29.6.2.2 Gridded Green and Ampt: Incorrect parameterization in the component
editor....................................................................................................... 1015
29.6.2.3 Standard Report: Incorrect Units Displayed ......................................... 1015
29.6.3 Beta releases.......................................................................................... 1015
29.7 v.4.6.1 Release Notes ............................................................................ 1016
29.7.1 Bug Fixes ................................................................................................ 1016
29.7.1.1 Program hang after pre-processing drainage with multiple
processors.............................................................................................. 1016
29.7.1.2 "Could not delineate elements because the break points did not intersect
the stream network" error with ESRI WKT projection .......................... 1017
29.7.1.3 Terrain File path updated after import.................................................. 1017
29.7.1.4 Missing data on sediment load results from USGS Long-Term debris
yield method........................................................................................... 1017
29.7.1.5 Statistics Report Generator - Terminates for Datasets with Elements
That Did Not Have Results .................................................................... 1017
29.7.1.6 Standard Report Generator - Overlapping X-Axis (Time) in Several
Plots........................................................................................................ 1017
43
29.7.1.7 Standard Report Generator - Incorrectly Display Time Series Plots with
Missing Data for Certain Dates ............................................................. 1018
29.8 v.4.6.0 Release Notes ............................................................................ 1019
29.8.1 New Features ......................................................................................... 1019
29.8.1.1 ASCII precipitation-frequency grid ........................................................ 1019
29.8.1.2 Precipitation-frequency grid option in hypothetical storm.................. 1020
29.8.1.3 Depth-area analysis with precipitation-frequency grid hypothetical
storm....................................................................................................... 1020
29.8.1.4 Gumbel Distribution in Uncertainty Analysis........................................ 1021
29.8.1.5 Standard Reports ................................................................................... 1021
29.8.1.6 Global Monthly Average Evapotranspiration Editor............................. 1022
29.8.1.7 macOS Portable Distribution................................................................. 1023
29.8.1.8 Beta Releases......................................................................................... 1023
29.9 v.4.5.0 Release Notes ............................................................................ 1024
29.9.1 New Features ......................................................................................... 1025
29.9.1.1 Global temperature-index snow editors ............................................... 1025
29.9.1.2 Time-variable wet-meltrate ................................................................... 1025
29.9.1.3 Debris yield methods ............................................................................. 1025
29.9.1.4 Number of cores user interface selection............................................ 1025
29.9.1.5 Java 11 ................................................................................................... 1026
29.9.2 Bug Fixes ................................................................................................ 1026
29.9.2.1 Error 14703: No data source is specified for unit hydrograph when
attempting to use a user-specified unit hydrograph............................ 1026
29.9.2.2 Unit hydrograph interval and duration are not saved in the Paired Data
editor....................................................................................................... 1026
29.9.2.3 Failed copy + paste in the unit hydrograph Paired Data editor ........... 1026
29.9.2.4 Missing or reduced-area mod Clark grid cells when generating a grid cell
file with target projection differing from the basin model coordinate
referencing system ................................................................................ 1026
44
29.10 v.4.4.1 Release Notes ............................................................................ 1027

29.10.1 New Features ......................................................................................... 1027
29.10.1.1 No data handling during grid accumulations ....................................... 1027
29.10.1.2 Coordinates tool tip added to the basin map....................................... 1027
29.10.1.3 Install dependencies shell script added to Linux build........................ 1027
29.10.2 Bug Fixes ................................................................................................ 1028
29.10.2.1 Cumulative time series results reset to zero at forecast time............ 1028
29.10.2.2 Paste from the clipboard fails in some tabular editors ....................... 1028
29.10.2.3 Compute to point is not forced when control button is pressed ........ 1028
29.10.2.4 Name text field is collapsed in Create New Project dialog ................. 1028
29.10.2.5 Recent projects list grows unbounded after opening projects repeatedly
in the same HEC-HMS instance ............................................................ 1028
29.10.2.6 Flow ratio applied to source is not observed ....................................... 1028
29.10.2.7 MUSLE is not valid to grid cell............................................................... 1029
29.10.2.8 Sediment results discrepancy for reservoirs ....................................... 1029
29.10.2.9 MPI Error when running terrain processing tasks from GIS menu ..... 1029
29.10.2.10 Component Editor freezes when changing element connections...... 1029
29.10.2.11 Unable to select Linear Reservoir baseflow parameters in Forecast
Slider Adjustments editor ...................................................................... 1029
29.11 v.4.4.0 Release Notes ............................................................................ 1030
29.11.1 Installation.............................................................................................. 1030
29.11.2 New Capabilities .................................................................................... 1030
29.11.2.1 GIS Delineation Tools ............................................................................ 1030
29.11.2.2 Layered Green and Ampt Loss Method ................................................ 1031
29.11.2.3 Gridded Hamon Evapotranspiration Method ....................................... 1031
29.11.2.4 Gridded Hargreaves Evapotranspiration Method ................................ 1031
29.11.2.5 Green and Ampt Loss Method .............................................................. 1031
29.11.2.6 Linear Reservoir Baseflow Method....................................................... 1031
29.11.2.7 Clark Transform Maricopa County AZ Method.................................... 1032
29.11.2.8 Compute to Point Expansion................................................................. 1032
45
29.11.2.9 Melt Rate Options for Temperature Index Snow Method.................... 1032
29.11.2.10 Subbasin Level Temperature Index Parameterization ........................ 1032
29.11.2.11 Hypothetical Storm Enhancements ...................................................... 1033
29.11.2.12 Terrain Data............................................................................................ 1033
29.11.2.13 Color Ramp and Scale Editor ................................................................ 1033
29.11.3 Enhancements and Revisions ............................................................... 1034
29.11.3.1 Basin Map Mouse Controls ................................................................... 1035
29.11.3.2 Sediment Channel Routing Computations with Index Flow/Celerity.. 1035
29.11.3.3 Parallelization of Sub-basin and Reach Network Computation .......... 1035
29.11.3.4 Control of Messages ............................................................................. 1036
29.11.4 Problems Repaired ................................................................................ 1036
29.11.4.1 Summary Information for Total Diverted Flow was Not Correct ........ 1036
29.11.4.2 Unrecognized Changes in Objective Function ..................................... 1036
29.11.4.3 Missing Inflow to a Diversion ................................................................ 1036
29.11.4.4 Renaming Junctions Adds Element to List of Subbasin Zone
Elements................................................................................................. 1036
29.11.4.5 Blending Allowed Missing Percentage ................................................. 1037
29.11.4.6 Report Drainage Area Precision............................................................ 1037
29.11.4.7 Optimization of Manning's n Value....................................................... 1037
29.11.4.8 Reservoir Storage Is Incorrect When Using FT:FT2 Elevation-Area
Function.................................................................................................. 1037
29.11.4.9 Un-editable Text Boxes.......................................................................... 1037
29.11.4.10 Out-of-Memory Error from Opening and Closing the Basin Map ........ 1037
29.11.4.11 Renaming Control Specifications ......................................................... 1037
29.11.4.12 Saving Kinematic Wave Transform Parameters.................................. 1037
29.11.4.13 Forecast Blending when Observed Data Is Missing ............................ 1038
29.11.4.14 NegativeArraySizeException in Kinematic Wave Channel Routing .... 1038
29.11.4.15 Error 10000 when Adding New Precipitation Gage ............................. 1038
29.11.5 Documentation....................................................................................... 1038
29.11.6 Support Policy ........................................................................................ 1039
46
47
– 48
1 Report Documentation Page
Form Approved
OMB No.
REPORT DOCUMENTATION PAGE 0704-0188
The public reporting burden for this collection of information is estimated to average 1 hour per response,
including the time for reviewing instructions, searching existing data sources, gathering and maintaining
the data needed, and completing and reviewing the collection of information. Send comments regarding
this burden estimate or any other aspect of this collection of information, including suggestions for
reducing this burden, to the Department of Defense, Executive Services and Communications Directorate
(0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person
shall be subject to any penalty for failing to comply with a collection of information if it does not display a
currently valid OMB control number.
PLEASE DO NOT RETURN YOUR FORM TO THE ABOVE ORGANIZATION.
1. REPORT DATE 2. REPORT TYPE 3. DATES COVERED (From -

(DD-MM-YYYY) Computer Program Document To)
January 19, 2022
4. TITLE AND SUBTITLE 5a. CONTRACT NUMBER

Hydrologic Modeling System HEC-HMS
User's Manual 5b. GRANT NUMBER
5c. PROGRAM ELEMENT NUMBER
6. AUTHOR(S) 5d. PROJECT NUMBER

Mike Bartles, Tom Brauer, David Ho, Matt Fleming,
Greg Karlovits, Jay Pak, Nick Van, and Josh Willis 5e. TASK NUMBER
5F. WORK UNIT NUMBER
7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) 8. PERFORMING

• U.S. Army Corps of Engineers ORGANIZATION REPORT
• Institute for Water Resources NUMBER
• Hydrologic Engineering Center (CEIWR-HEC) CPD-74A
• 609 Second Street
• Davis, CA 95616-4687
Report Documentation Page – 49

9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/ MONITOR'S

ACRONYM(S)
11. SPONSOR/ MONITOR'S

REPORT NUMBER(S)
12. DISTRIBUTION / AVAILABILITY STATEMENT

Approved for public release; distribution is unlimited.
13. SUPPLEMENTARY NOTES
14. ABSTRACT
The Hydrologic Modeling System (HEC-HMS) is designed to simulate the complete hydrologic processes
of dendritic watershed systems. In includes many traditional hydrologic analysis procedures such as
event infiltration, unit hydrographs, and hydrologic routing. It also includes procedures necessary for
continuous simulation including evapo-transpiration, snowmelt, and soil moisture accounting. Gridded
runoff simulation can also be performed. Supplemental analysis tools are provided for parameter
estimation, depth-area analysis, flow forecasting, uncertainty assessment, and erosion and sediment
transport.
The program features an integrated work environment with data entry utilities, computation engine, and
results reporting tools. A graphical user interface allows seamless movement between the different parts
of the program. Simulation results are stored in the Data Storage System HEC-DSS and can be used in
conjunction with other software for studies of water availability, urban drainage, flow forecasting, future
urbanization impact, reservoir spillway design, flood damage reduction, floodplain regulation, and
systems operation.
15. SUBJECT TERMS

Hydrology, watershed, precipitation runoff, river routing, flood frequency, flood control, water supply,
computer simulation, environmental restoration.
16. SECURITY CLASSIFICATION OF: 17. LIMITATION 18. NUMBER 19a.

OF OF NAME
OF
a. b. ABSTRACT c. ABSTRACT PAGES RESPO
REPO U THIS UU NSIBLE
RT PAGE PERSO
U U N

19b.
TELEPH
ONE
NUMBE
R

2 Preface
This Manual is not intended to teach you how to do hydrologic engineering or even hydrology. It does not
describe the mathematical equations for the various models included in the program. So what does it do?
This Manual will teach you how to use the various features and capabilities of the program. It works very well
to simply read the Manual through starting at the beginning. If you read the Manual in front of your computer
with the program up and running, it will work even better. However, the Manual works equally well as an
occasional reference when you cannot remember exactly how to perform a certain task or need to check the
parameter definitions for a particular method.
The scope of this Manual does not mean that we think engineering applications or mathematical analysis are
unimportant. In fact, both of those things are vital to producing good engineering plans and designs. We feel
they are so important that we have created a separate Manual for each of them. The Technical Reference
Manual provides detailed descriptions of each of the models included in the program. You can expect to find
the mathematical derivation of the model equations, details on the numerical schemes employed in the
program to solve the equations, and specific guidance on parameter estimation. Consequently, it focuses
less on using the program and more on understanding the science of hydrology. The Applications Guide
provides practical suggestions for using the program to perform engineering work. We selected a number of
typical projects that engineers often encounter and showed how the program can be used to provide real
answers. Consequently, it focuses less on using the program and more on the engineering process.
Preface – 52
3 Introduction
The Hydrologic Modeling System (HMS) is designed to simulate the precipitation-runoff processes of
dendritic watershed systems. It is designed to be applicable in a wide range of geographic areas for solving
the widest possible range of problems. This includes large river basin water supply and flood hydrology, and
small urban or natural watershed runoff. Hydrographs produced by the program are used directly or in
conjunction with other software for studies of water availability, urban drainage, flow forecasting, future
urbanization impact, reservoir spillway design, flood damage reduction, floodplain regulation, and systems
operation.
3.1 Scope
The program is a generalized modeling system capable of representing many different watersheds. A model
of the watershed is constructed by separating the hydrologic cycle into manageable pieces and constructing
boundaries around the watershed of interest. Any mass or energy flux in the cycle can then be represented
with a mathematical model. In most cases, several model choices are available for representing each flux.
Each mathematical model included in the program is suitable in different environments and under different
conditions. Making the correct choice requires knowledge of the watershed, the goals of the hydrologic
study, and engineering judgment.
The program features a completely integrated work environment including a database, data entry utilities,
computation engine, and results reporting tools. A graphical user interface allows the seamless movement
between the different parts of the program. Program functionality and appearance are the same across all
supported platforms.
3.2 History
The computation engine draws on over 30 years experience with hydrologic simulation software. Many
algorithms from HEC-1 (HEC, 1998), HEC-1F (HEC, 1989), PRECIP (HEC, 1989), and HEC-IFH (HEC, 1992)
have been modernized and combined with new algorithms to form a comprehensive library of simulation
routines. Future versions of the program will continue to modernize desirable algorithms from legacy
software. The current research program is designed to produce new algorithms and analysis techniques for
addressing emerging problems.
The initial program release was called Version 1.0 and included most of the event-simulation capabilities of
the HEC-1 program. It did introduce several notable improvements over the legacy software including an
unlimited number of hydrograph ordinates and gridded runoff representation. The tools for parameter
estimation with optimization were much more flexible than in previous programs. The maiden release also
included a number of "firsts" for HEC including object-oriented development in the C++ language and
multiplatform support in a program with a graphical user interface.
The second major release was called Version 2.0 and focused on continuous simulation. The addition of the
soil moisture accounting method extended the program from an event-simulation package to one that could
work equally well with event or continuous simulation applications. The reservoir element was also expanded
to include physical descriptions for an outlet, spillway, and overflow. An overtopping dam failure option was
also added.
Introduction – 53
The third major release was called Version 3.0 and introduced new computation features and a brand new
graphical user interface. The meteorologic model was enhanced with new methods for snowmelt and
potential evapo-transpiration simulation. The basin model was enhanced with additional methods for
representing infiltration in the subbasin element, and additional computational options in the diversion and
reservoir elements. The new graphical user interface was designed to simplify creating and managing the
many types of data needed for hydrologic simulation, and to increase user efficiency with a better-integrated
work environment.
The fourth major release was called version 4.0 and focused primarily on new computation features and
integrating a GIS framework. A broad range of surface erosion and sediment transport features were added
to the subbasin, reach, reservoir, and other elements. A preliminary capability was also added for nutrient
water quality simulation. New simulation component was added to to facilitate real-time forecasting
operations. Finally, an integrated GIS framework was added to the program that allows modelers to delineate
subbasins and reaches, discretize subbasin elements for precipitation and process based computations,
estimate model parameters and visualize results.
Enhancement of the program is ongoing. HEC has a strong commitment to continued research in emerging
needs for hydrologic simulation, both in terms of simulation techniques and representation of physical
processes. Future needs are identified by conducting our own application projects, speaking with program
users, and monitoring academic journals. HEC also has a strong commitment to continued development of
the program interface. Plans are already underway to add new features in a future version that will make the
program easier to use by providing more flexible ways to accomplish work. New visualization concepts are
also being developed. Look for future versions to continue the tradition.
3.3 Capabilities
The program has an extensive array of capabilities for conducting hydrologic simulation. Many of the most
common methods in hydrologic engineering are included in such a way that they are easy to use. The
program does the difficult work and leaves the user free to concentrate on how best to represent the
watershed environment.
3.3.1 Watershed Physical Description

The physical representation of a watershed is accomplished with a Basin Model. Hydrologic elements are
connected in a dendritic network to simulate runoff processes. Available elements are: Subbasin, Reach,
Junction, Reservoir, Diversion, Source, and Sink. Computation proceeds from upstream elements in a
downstream direction.
An assortment of different methods is available to simulate infiltration losses. Options for event modeling
include Initial Constant, SCS Curve Number, Exponential, Green Ampt, and Smith Parlange. Continuous
simulation methods include the one-layer Deficit Constant, Layered Green and Ampt, and Soil Moisture
Accounting methods. The three-layer Soil Moisture Accounting method can be used for continuous
modeling of complex infiltration and evapotranspiration environments. Gridded methods are available for the
Deficit Constant, Green Ampt, SCS Curve Number, and Soil Moisture Accounting methods. Canopy and
Surface components can also be added when needed to represent interception and capture processes.
Eight methods are included for transforming excess precipitation into surface runoff. Unit hydrograph
methods include the Clark, Snyder, and SCS techniques. User-specified Unit Hydrograph or S-graph
Ordinates can also be used. The modified Clark method, ModClark, is a linear quasi-distributed unit
hydrograph method that can be used with gridded meteorologic data. An implementation of the Kinematic
Wave method with multiple planes and channels is also included. A 2D Diffusion Wave Transform option is
available that utilizes the same 2D engine used in HEC-RAS.
Introduction – 54
Five methods are included for representing baseflow contributions to subbasin outflow. The Recession
method gives an exponentially decreasing baseflow from a single event or multiple sequential events. The
Constant Monthly method can work well for continuous simulation. The Linear Reservoir method conserves
mass by routing infiltrated precipitation to the channel. The nonlinear Boussinesq method provides a
response similar to the Recession method but the parameters can be estimated from measurable qualities
of the watershed.
A total of nine hydrologic routing methods are included for simulating flow in open channels. Routing with no
attenuation can be modeled with the Lag method. Routing with constant or variable attenuation and
translation can be modeled with the Lag and K method. The traditional Muskingum method is included along
with the Straddle Stagger method for simple approximations of attenuation. The Modified Puls method can
be used to model a reach as a series of cascading, level pools with a user-specified storage-discharge
relationship. Channels with trapezoidal, rectangular, triangular, or circular cross sections can be modeled
with the Kinematic Wave or Muskingum-Cunge methods. Channels with overbank areas can be modeled
with the Muskingum-Cunge method and either an 8-point cross section or user defined tabular data.
Additionally, channel losses can also be included in the routing. The Constant Loss method can be added to
any routing method while the Percolation method can be used only with the Modified Puls or Muskingum-
Cunge methods.
Water impoundments can also be represented. Lakes are usually described by a user-entered storage-
discharge relationship. Reservoirs can be simulated by describing the physical spillway and outlet structures.
Pumps can also be included as necessary to simulate interior flood area. Control of the pumps can be linked
to water depth in the collection pond and, optionally, the stage in the main channel.
Diversion structures can also be represented. Available methods include a User-specified Function, Lateral
Weir, Pump Station, Observed Diversion Flows.
3.3.2 Meteorology Description

Meteorologic data analysis is performed by the Meteorologic Model and includes Shortwave Radiation,
Longwave Radiation, Precipitation, Temperature, Windspeed, Dewpoint, Evapo-transpiration, and Snowmelt.
Not all of these components are required for all simulations. Simple event simulations require only
Precipitation, while continuous simulation additionally requires additional meteorologic variables and Evapo-
transpiration. Generally, Snowmelt is only required when working with watersheds in cold climates.
Four different methods for analyzing historical precipitation are included. The User-specified Hyetograph
method is for precipitation data analyzed outside the program. The Gage Weights method uses an unlimited
number of recording and non-recording gages. The Thiessen technique is one possibility for determining the
weights. The Inverse Distance method addresses dynamic data problems. An unlimited number of recording
and non-recording gages can be used to automatically proceed when missing data is encountered. The
Gridded Precipitation method uses radar rainfall data or other sources of gridded precipitation data.
Five different methods for producing synthetic precipitation are included. The Frequency Storm method uses
statistical data to produce balanced storms with a specific exceedance probability. Sources of supporting
statistical data include Technical Paper 40 (National Weather Service, 1961), NOAA Atlas 2 (National
Weather Service, 1973). While it was not specifically designed to do so, data can also be used from NOAA
Atlas 14 (National Weather Service, 2004ab). The Standard Project Storm method implements the
regulations for precipitation when estimating the standard project flood (Corps of Engineers, 1952). The
Hypothetical Storm method implements the primary precipitation distributions for design analysis using
Natural Resources Conservation Service (NRCS) criteria (Soil Conservation Service, 1986) and provides
additional user options for defining the temporal pattern. The HMR 52 Storm creates a hypothetical storm as
defining in Hydrometeorologic Report 52 (Hansen, Schreiner, and Miller, 1982). The User-specified
Hyetograph method can be used with a synthetic hyetograph resulting from analysis outside the program.
Introduction – 55
Potential evapo-transpiration can be computed using monthly average values. The Hargreaves and Hamon
evapo-transpiration methods require temperature data. There are also implementations of the Priestley
Taylor method and the Penman Monteith method that require a range of atmospheric parameters. A gridded
version of both methods is also available where the required parameters of temperature, solar radiation, and
other atmospheric variables are specified on a gridded basis. The Priestley Taylor evapo-transpiration
method requires the net radiation while the Penman Monteith method requires separate estimates of
shortwave and longwave radiation. Shortwave radiation can be represented with the conceptual Bristow
Campbell method that utilizes daily maximum and minimum temperature, or the Shapiro method that
requires information about the cloud coverage in three layers. Longwave radiation can be represented with
the conceptual Satterlund method, or an adjunct to the Shapiro method based on the same cloud input data.
A User-specified method can be used with data developed from analysis outside the program.
Snowmelt can be included for tracking the accumulation and melt of a snowpack. A Temperature Index
method is available that dynamically computes the melt rate based on current atmospheric conditions and
past conditions in the snowpack; this improves the representation of the "ripening" process. The concept of
Cold Content is incorporated to account for the ability of a cold snowpack to freeze liquid water entering the
pack from rainfall. A subbasin can be represented with Elevation Bands or Grid Cells.
3.3.3 Hydrologic Simulation

The time span of a simulation is controlled by Control Specifications. Control Specifications include a
Starting Date and Time, Ending Date and Time, and a Time Interval.
A Simulation Run (see page 523) is created by combining a Basin Model, Meteorologic Model, and Control
Specifications. Run options include a precipitation or flow ratio, capability to save all basin state information
at a point in time, and ability to begin a simulation run from previously saved state information.
Simulation results can be viewed from the Basin Map. Global and element Summary Tables include
information on peak flow, total volume, and other variables. A Time-series Table and Graph are available for
elements. Results from multiple elements and multiple simulation runs can also be viewed. All graphs and
tables can be printed.
3.3.4 Parameter Estimation

A wide variety of automated parameter estimation tasks can performed using Optimization Trials (see page
567):
• Minimization of an objective function which decreases with model goodness-of-fit for simulated vs.
observed discharge
• Maximization of an objective function which increases with model goodness-of-fit for simulated vs.
observed discharge
• Maximization of simulated peak discharge, discharge volume or reservoir pool elevation
Most parameters for methods included in subbasin and reach elements can be estimated automatically
using Optimization Trials. Observed discharge must be available for at least one element before optimization
can begin. Parameters at any element upstream of the observed flow location can be estimated. Numerous
different objective functions for use with minimization or maximization goals are available to estimate the
goodness-of-fit between the computed results and observations. Three different search methods can be
used to deterministically optimize the objective function. Constraints can be imposed to restrict the
parameter space of the search method.
Introduction – 56
3.3.5 Forecasting Future Flows

The Basin Model includes features designed to increase the efficiency of producing forecasts of future flows
in a real-time operation mode. Zones can be created that group subbasins or routing reaches together on the
basis of similar hydrologic conditions or regional characteristics. Zones can be assigned separately for loss
rate, transform, baseflow, and reach routing. The Forecast Alternative (see page 610)is a type of simulation
that uses a Basin Model and Meteorologic Model in combination with control parameters to forecast future
flows. Parameter values can be adjusted by zone and blending can be applied at elements with observed
flow.
3.3.6 Evaluating Depth-Area Effects

Synthetic storms with an exceedance probability can be used for developing flow-frequency curves. It is well
known that peak storm intensity decreases as the storm area increases. This relationship between intensity
and area is captured in the Depth-Area Reduction Curve. The Depth-Area Analysis 1provides a convenient
way to develop the data for flow-frequency curves in large watersheds where the storm area should always
match the drainage area at each analysis point. It works with Meteorologic Models using the Frequency
Storm Precipitation method. A list of analysis points can be selected and the storm area is automatically
adjusted to compute flow at each analysis point.
3.3.7 Building Frequency Curves

The Frequency Analysis2 compute option in HEC-HMS is similar in nature to the existing Depth-Area Analysis
framework but with a different end goal in mind. Instead of analyzing multiple points within a watershed at a
single frequency, the Frequency Analysis compute option allows the user to analyze a single point over a
range of different frequencies. A Frequency Analysis can have one to many ordinates defined, each with their
own assigned Annual Exceedance Probability, Meteorologic Model, and Basin Model. Currently, the analysis
can be used to generate a flow frequency curve or a stage frequency curve at the point of interest.
3.3.8 Assessing Uncertainty

The principal of uncertainty captures the idea that a lack of knowledge and natural variability make it difficult
to precisely perform hydrologic simulation. There may be a lack of knowledge about exactly how to model a
specific component of the hydrologic cycle. There may be natural variability in soil properties that make it
difficult to parameterize an infiltration model. These uncertainties can be estimated quantitatively and
evaluated numerically using the Uncertainty Analysis3. Parameters can be selected for evaluation, probability
distributions assigned, and then a Monte Carlo simulation is performed to generate probabilistic results for
hydrographs and key hydrologic statistics such as volume or peak flow.
3.3.9 Sediment
Optional components in the Basin Model can be used within a Sediment Analysis. Surface erosion can be
computed at subbasin elements using the MUSLE approach for rural areas, the Build-up/Wash-off approach
for urban settings, or choose between different debris yield methods. The debris yield methods include the
1 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/.Depth-Area+Analyses+v4.4
2 https://www.hec.usace.army.mil/confluence/display/HMSUM/.Frequency+Analyses+v4.10
3 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/Uncertainty+Analyses
Introduction – 57
LA Debris Method EQ1, the Multi-Sequence Debris Prediction Method (MSDPM), and the USGS Long-Term
Debris Model. Channel erosion, deposition, and sediment transport can be added to reach elements while
sediment settling can be included in reservoir elements.
3.3.10 GIS Connection

The power and speed of the program make it possible to represent watersheds with hundreds of hydrologic
elements. Traditionally, these elements would be identified by inspecting a topographic map and manually
identifying drainage boundaries. While this method is effective, it is prohibitively time consuming when the
watershed will be represented with many elements. A Geographic Information System (GIS) can use
elevation data and geometric algorithms to perform the same task much more quickly. GIS tools have been
integrated directly within HEC-HMS. Current capability includes options to delineate subbasins and reaches
from a terrain dataset. Additional GIS tools have been added to the software that allow modelers to compute
physical characteristics and estimate model parameters from GIS datasets. Simulation results can be
displayed over a georeferenced Basin Model.
3.4 Limitations
Every simulation system has limitations due to the choices made in the design and development of the
software. The limitations that arise in this program are due to two aspects of the design: Simplified Model
Formulation, and Simplified Flow Representation. Simplifying the model formulation allows the program to
complete simulations very quickly while producing accurate and precise results. Simplifying the flow
representation aids in keeping the compute process efficient and reduces duplication of capability in the
HEC software suite.
3.4.1 Model Formulation

All of the mathematical models included in the program are deterministic. This means that the boundary
conditions, initial conditions, and parameters of the models are assumed to be exactly known. This
guarantees that every time a simulation is computed it will yield exactly the same results as all previous
times it was computed. Deterministic models are sometimes compared to stochastic models where the
same boundary conditions, initial conditions, and parameters are represented with probabilistic distributions.
While not the same as stochastic models, the Uncertainty Analysis allows the calculation of probabilistic
results using a Monte Carlo simulation of the deterministic models.
Most of the mathematical models included in the program use constant parameter values, that is, they are
assumed to be time stationary. During long periods of time it is possible for parameters describing a
watershed to change as the result of human or other processes at work in the watershed. Some model
parameter can be varied in an annual pattern or adjustments made at specific points in time. There is a
limited capability to break a long simulation into smaller segments and manually change parameters
between segments. Plans are underway to develop a variable parameter capability, through an as yet
undetermined means.
Key mathematical models representing the land surface are quasi-coupled. In the physical world, both the
amount of evapotranspiration and the amount of infiltration each depend on the amount of soil water.
However, evapotranspiration removes water from the soil at the same time infiltration adds water to the soil.
Ideally all of the equations for the relevant processes would be solved simultaneously. Quasi-coupling is
used in order to maintain flexibility in independently choosing the representation of each process. First,
potential evapotranspiration is computed based on atmospheric conditions. Second, precipitation is added
to the soil water. Third, actual evapotranspiration is computed based on the soil water content and then
Introduction – 58
removed. Finally, a mass balance is performed and soil water exceeding capacity is returned to the land
surface to become overland runoff. Any remaining errors due to the quasi-coupling scheme can be
minimized by using a suitably short simulation time interval.
3.4.2 Flow Representation

The design of the Basin Model only allows for dendritic stream networks. The best way to visualize a
dendritic network is to imagine a tree. The main tree trunk, branches, and twigs correspond to the main river,
tributaries, and headwater streams in a watershed. The key idea is that a stream does not separate into two
streams. The basin model allows each hydrologic element to have only one downstream connection so it is
not possible to split the outflow from an element into two different downstream elements. The 2D transform
option does allow the modeler to simulate backwater, branching, and looping flow within a subbasin
element's 2D grid. The diversion element provides a limited capability to remove some of the flow from a
stream and divert it to a different location downstream in the network. Likewise, a reservoir element may
have an auxiliary outlet. However, in general, branching or looping stream networks cannot be simulated with
the program and will require a separate hydraulic model which can represent such networks.
The design of the process for computing a simulation does not allow for backwater in the stream network.
For each time interval, the compute process begins at headwater subbasins and proceeds down through the
network. The process starts with each subbasin computing outflow for the time interval. These outflow
values are passed to downstream elements where they become inflow to that element. Continuing
downstream, each element receives inflow from upstream elements for the time interval, and then computes
its own outflow. Because outflow is only passed from upstream to downstream elements, it is not possible
for an upstream element to have knowledge of downstream flow conditions, which is the essence of
backwater effects. There is a limited capability to represent backwater if it is fully contained within a reach
element. However, in general, the presence of backwater within the stream network will require a separate
hydraulic model.
3.5 References
Corps of Engineers. 1952. Engineer Manual 1110-2-1411: Standard Project Flood Determinations. U.S. Army,
Washington, DC.
Hansen, E.M., L.C. Schreiner, and J.F. Miller. 1982. Application of Probable Maximum Precipitation Estimates
– United States East of the 105th Meridian. Hydrometeorological Report No. 52. National Weather Service,
Washington, D.C.
Hydrologic Engineering Center. June 1998. HEC-1 Flood Hydrograph Package: User's Manual. U.S. Army
Corps of Engineers, Davis, CA.
Hydrologic Engineering Center. April 1992. HEC-IFH Interior Flood Hydrology Package: User's Manual. U.S.
Army Corps of Engineers, Davis, CA.
Hydrologic Engineering Center. November 1989. Water Control Software: Forecast and Operations. U.S. Army
National Weather Service. 1961. Technical Paper 40: Rainfall Frequency Atlas for the United States for
Durations from 30 Minutes to 24 Hours and Return Periods from 1 to 100 Years. U.S. Department of
Commerce, Washington, DC.
National Weather Service. 2004. NOAA Atlas 14 Precipitation-Frequency Atlas of the United States: Volume 1
Semi Arid Southwest (Arizona, Southeast California, Nevada, New Mexico, Utah). U.S. Department of
Commerce, Silver Spring, MD.
Introduction – 59
National Weather Service. 2004. NOAA Atlas 14 Precipitation-Frequency Atlas of the United States: Volume 2
Delaware, District of Columbia, Illinois, Indiana, Kentucky, Maryland, New Jersey, North Carolina, Ohio,
Pennsylvania, South Carolina, Tennessee, Virginia, West Virginia. U.S. Department of Commerce, Silver
Spring, MD.
National Weather Service. 1973. NOAA Atlas 2: Precipitation-Frequency Atlas of the Western United States.
U.S. Department of Commerce, Silver Spring, MD.
Soil Conservation Service. 1986. Technical Release 55: Urban Hydrology for Small Watersheds. Department
of Agriculture, Washington, DC.
Introduction – 60
4 Installing and Running the Program

This section describes the recommended computer system requirements for running the program. Step-by-
step installation procedures are also provided for the three operating systems that are supported.
4.1 Operating System Requirements

The program has been created using the Java programming language. Programs written in the language can
run on almost any operating system. However, the program has several native dependencies. We have
created builds for Windows, Linux and macOS. Because the program was created with the Java language,
the program looks and behaves substantially the same on all operating systems.
The program is available for:
• Windows 10 64-bit or newer.
• Modern Linux x64 distributions.
• macOS Mojave, Catalina, and Big Sur.
The program has been extensively tested on Windows 10.
4.2 Hardware Requirements and Recommendations

The typical hardware equipment for the Microsoft Windows or Linux installation includes:
• Intel Pentium III/800 MHz or higher (or compatible).
• 512 MB of memory minimum.
• 1 GB of memory recommended.
• 120 MB of available hard disk space for installation.
• 1024x768 minimum screen resolution.
Significantly more resources may be needed depending on your application. The minimum equipment for
either operating system will be suitable for event simulation with Basin Models containing only 20 or 30
hydrologic elements. However, you will need better equipment if you intend to build Basin Models with over a
hundred elements, perform continuous simulation for long time windows, or use the ModClark or 2D
Diffusion Wave transform methods. For intense applications you should consider a multiple processor
system running at 2.0 GHz or faster, and 1 GB or more of physical memory.
4.3 Installation
Installation packages for the program are available from the Hydrologic Engineering Center (HEC) website
where the current version of the program is always available: https://www.hec.usace.army.mil/software/hec-
hms/downloads.aspx.
Old versions of the program are archived and can be downloaded. However, old versions are not maintained,
contain bugs and errors, and may not function correctly with current versions of the supported operating
systems.
Installing and Running the Program – 61

4.3.1 Microsoft Windows Operating System

There are two options for installation on Windows: an Installation Package or a Portable Archive.
4.3.1.1 Windows Installer

In order to run the installer you must have Administrator privileges on your computer. You only need the
privileges during installation; once installation is complete the program can run successfully without
Administrator privileges. If you do not have Administrator privileges, the installer will notify you and quit.
Please contact your system administrator for assistance during installation.
After you have obtained the installer and Administrator privileges, use the following steps to install the
program:
1. Run the HEC-HMS Setup Package downloaded from the HEC website.
2. Depending on your security settings, you may receive a warning before the installer starts. The
installer is signed with a digital signature so you can verify it was produced by HEC and has not been
altered. If the digital signature is OK, press the Run button to proceed with starting the installer.
3. The installer will open in a new window and perform some preliminary configurations in preparation
for installation. A Welcome window will notify you that HEC-HMS will be installed. Press
the Next button to continue with the installation.
4. The next window will display the terms and conditions for using the program. This must be accepted
during installation and later by every user who starts using the program on the computer where it is
installed. Please read the terms and conditions for use carefully. If you agree, click the I agree to the
above Terms and Conditions for Use radio button, and then press the Next button. If you do not
agree, the installer will exit without installing the program.
5. The next window is used to select the location where the program will be installed on the local disk. It
is recommended that the default location in the C:\Program Files folder be used. Press
the Next button when you are satisfied with the installation location.
6. The next window allows you to choose if a shortcut to the program will be placed on the desktop.
Program shortcuts will automatically be created in the Start menu under the All Programs |
HEC folder, so having a desktop shortcut is optional.
7. The next and final window allows you to confirm that you are ready for installation. If you would like
to change any of the previously configured settings, you may use the Back button. Press
the Install button to install the program with all of the configuration information specified in the
previous windows.
The installer will copy all necessary files and make additional configuration changes to the operating system.
You do not need to restart the computer after the installation completes. At any time you can uninstall the
program through the Control Panel. When future versions of the program become available, you may have
each version separately installed on your computer.

4.3.1.2 Portable Version
4.3.1.2.1 Unpack archive
The Windows portable version is distributed as a zip archive. Unpack, or unzip, the archive to the desired
location on your computer.
4.3.1.2.2 Run the Program
Launch the program by double-clicking hec-hms.exe or running the hec-hms.cmd script.
4.3.2 Linux Operating System

The distribution package is a compressed archive.

This installation guide was tested in the following environment:
• HEC-HMS v.4.6
• OS: Ubuntu 18.04 LTS
• Mpich 3.3~a2-4
• GDAL 2.4.2
Download the latest HEC-HMS version.

Unpack the archive:
tar -xzf /tmp/HEC-HMS-<version>.tar.gz -C /tmp
Install (this guide uses /opt but feel free to choose a different directory):
sudo mv /tmp/HEC-HMS-<version> /opt/HEC-HMS-<version>
HEC-HMS is now installed. When future versions of the program become available, you may have each
version separately installed on your computer. You will need to carefully organize the installation locations
so that each version can be kept separate.
4.3.2.1.2 Install Dependencies
Install the necessary libraries for TauDEM (C++, MPI, and GDAL) using the following commands:
sudo apt-get install build-essential
sudo apt-get install mpich

Add UbuntuGIS PPA to install GDAL Libraries:
sudo add-apt-repository ppa:ubuntugis/ppa
sudo apt-get update
Install the GDAL Libraries:
sudo apt-get install gdal-bin
sudo apt-get install libgdal-java
Run the program by changing the directory to the directory where the program is installed, changing the hms
script into an executable, then executing the hms script:
cd <HEC-HMS Install>
chmod +x hec-hms.sh
./hec-hms.sh
4.3.3 MacOS X

This installation guide was tested in the following environment:
• HEC-HMS v.4.6
• OS: macOS X 'Catalina'
• Open MPI 4.*
• GDAL 2.4.1
The macOS portable version is distributed as a zip archive. Unzip the archive on the local machine to unpack
the distribution.
4.3.3.1.2 Install Dependencies
Run the install-dependencies.sh script in the distribution root to build and install the required dependencies.
The GDAL build/install in the shell script takes 20-30 minutes depending on the system.

Run the program by changing directory to the directory where the program is installed and running the hec-
hms.sh script from the terminal:
./hec-hms.sh
4.4 Command Line Operation

The normal mode of operation starts the program and displays the interface. From the interface the user can
access all the features and capabilities of the program using the mouse and keyboard. However, for some
uses it may advantageous to start the program, have it carry out certain commands, and then shut down.
There is a very limited capability to operate in this mode using scripting control, see documentation here -
Scripting (see page 814). Additional scripting capabilities may be added in the future.
The first step is to create a Control Script. It is best if the simulation that will be computed by the script
already exists and has been tested in normal operation to make sure it completes successfully. A typical
script would contain the following lines in a file:
from hms.model.JythonHms import *

OpenProject("Tenk", "C:/hmsproj/Tenk")
Compute("Run 1")
Once you have created the script file, it can be used with the program from the command line. The program
will start and automatically process the script. The first line is used to setup the scripting environment and
make the program data model accessible to the script. The second line opens an existing project and the
third line computes an existing simulation run. The final line of the script exits the program.
To use a script on the Microsoft Windows® operating system, begin by opening a command window and
changing directories to the installation folder. The installation folder is not standardized and depends on
where you chose to install the program. One possibility would look like the following:
C:\Program Files\HEC\HEC-HMS\4.4>
At the command prompt, type the following to launch the program and run the script, where the last
argument is the complete path to a script:
hec-hms.cmd –s C:\hmsproj\Tenk\compute.script
To use a script on the Linux operating system, begin by opening a console and changing directories to the
installation folder. The installation folder is not standardized and depends on the policies of your system
administrator. One possibility would look like the following:
/usr/hec/hechms>
At the console, type the following to launch the program and run the script, where the last argument is the
complete path to the script:
hms –s /usr/smith/hmsproj/tenk/compute.script
The program will not be visible while it is running the script. However, the commands in the script will be
carried out. Any messages generated while computing the simulation run will be written to the log file. All

results will be stored in the output Data Storage System (DSS) file. Inspection of the log file will reveal any
errors, warning, or notes and results can be read from the DSS file.
4.5 Running the Program

The Windows version of the program is designed to be installed only once on a computer, and shared by
every user with logon access to the computer. On Linux the program can be installed by Root in a single
location for use by all users of the system, or each user can install it in their own home directory. Program
configuration information is stored separately for each user. Projects will also be stored separately for each
user, unless the users take steps to make the projects available to all users.
4.5.1 Microsoft Windows Operating System

Run the program by clicking on the Start menu and then place the mouse over the All Programs selection.
After a short hesitation, the list of available programs will be displayed. Move the mouse to the HEC folder
and move to the HEC-HMS subfolder. Click on the version of the program you wish to run.
If you chose to add a desktop shortcut during installation, you can also run the program directly from the
desktop. An icon will be shown on the desktop for the program. Move the mouse over the icon and double-
click the left mouse button.
4.5.2 Linux Operating System

Run the program by changing directory to the directory where the program is installed, changing hms script
into an executable, then executing the hms script:
cd <HEC-HMS Install>
chmod +x hec-hms.sh
./hec-hms.sh
4.5.3 Debug
Running the program in Debug mode prints output to the console that may be helpful when debugging
issues. Debug mode also opens "debug-only" features that are not suited for widespread use. To launch the
program in debug, add the -debug program argument. Examples are provided below.
Windows:
hec-hms.exe -debug
or
hec-hms.cmd -debug
Linux:
hec-hms.sh -debug

MacOS:
hec-hms.sh -debug
4.6 Managing Memory Allocation

The program defaults to using up to 512 MB of memory. This is sufficient for most common applications of
the program. However, simulations with Basin Models that include many elements, use long time windows
for continuous simulation, or make use of gridded meteorology can require significantly more memory.
Computing large simulations with insufficient memory may cause the program to abruptly cease operation.
The following files need to be changed to allow the program to use more memory than the default 512 Mb:
Windows:
<HEC-HMS Install>\HEC-HMS.cmd
<HEC-HMS Install>\HEC-HMS.config
Linux:
<HEC-HMS Install>/hms
In all three files, search for the string -Xmx512M and replace the 512 with the number of MB's you would
like to allow the program to use.
The amount of memory you can use depends on your operating system. A typical computer using Microsoft
Windows® or Linux® can usually use up to 1,350 Mb. These are general guidelines and your situation will
depend on the specifics of your hardware and other processes that may be executing at the same time as
the program. In no case should you attempt to use more than half of the physical memory in the machine
since other applications and system processes also require memory resources.
4.7 Additional Resources

The program includes an online Help System that is automatically installed when the program is installed.
The Help System is equivalent to the User's Manual, Technical Reference Manual, and Applications Guide.
The various documents are also available separately.
Three sample projects are included with the program. The Castro project shows how the program can be
used for basic hydrology. The Tenk project demonstrates the capability of the program to use gridded
precipitation. Finally, the Tifton project exhibits continuous simulation with the soil moisture accounting
method. The projects are kept in a space-saving, compressed form. They can be extracted for use at any
time by going to the Help menu and selecting the Install Sample Projects… command.

5 Overview
This section describes the basics of working with the program. It includes descriptions of the main parts of
the interface. Specific details of when and how data are saved is also included. Conventions are provided for
the formatting of input data, the use of units, and interpolation. An outline of the best way to use the program
is also provided.
5.1 Program Screen

As shown in the figure below, the program screen contains a Title Bar, Menu System, Toolbar, and four
Panes. These panes will be referred to as the Watershed Explorer, Desktop, Component Editor, and
the Message Logs shown in the figure below. The Title Bar displays the version of the program used and the
location of the currently-open project. The other parts of the program screen are discussed in detail in this
section.
1 The main program screen with Watershed Explorer in the upper left, Component Editor in the lower left, Message Log at the bottom,
and Desktop using the remaining area.
Overview – 68
5.1.1 Menu System

The Menu System contains several menus to help you use the program. Each menu contains a list of related
commands. For example, the Parameters menu contains a list of commands to open global parameter
tables for viewing and editing parameters required by hydrologic elements in the selected Basin Model.
Items in an individual menu are inactive (cannot be selected) if the command can not be carried out by the
program at the current time.
Commands for managing the opened project are available from the File menu. File menu items and the
resulting actions are provided in the following table. The last four projects opened are shown at the bottom
of the File menu. Click on one of the project names to open the project.
File Menu Commands Action
New Create a new project.
Open Open a project.
Import Import HEC-1 files, simulation run components, individual

components, HEC-RAS HDF files, and gridded data.
References Open a table showing pathnames to all files reference by the

project.
Save Save the current project.
Save As Make a copy of the current project.
Delete Delete the current project.
Rename Rename the current project.
Print Print the currently selected item.
Exit Exit the program.
1 Commands available from the File menu
The Edit menu contains commands for editing hydrologic elements in the selected Basin Model. If no Basin
Model is selected, then all commands in this menu are inactive. Edit menu commands and the resulting
actions are provided in the following table. Additional Edit menu includes commands select mouse tools for
use in the Basin Model Map.
Overview – 69
Edit Menu Commands Action
Cut Cut or delete the selected hydrologic element(s).
Copy Make a copy of the selected hydrologic element(s).
Paste Paste the copied hydrologic element(s).
Select All Select all hydrologic elements in the Basin Model.
Select Upstream Select all hydrology elements located upstream of the selected
element.
Invert Selection Select all elements not currently selected while unselecting the
currently selected elements
Clear Selection Unselect all selected hydrologic elements in the Basin Model.
Select By Name Open the Select By Name dialog.
2 Commands available from the Edit menu
The View menu contains a list of commands for working in the Basin Map. These commands are inactive if
no Basin Model is open in the Desktop pane. A list of View menu items and the resulting actions are provided
in the following table.
View Menu Commands Action
Map Layers Open the map layers editor.
Zoom In Zoom in by a factor of 25%.
Zoom Out Zoom out by a factor of 50%.
Zoom To Selected Zoom to the current element selection.
Zoom To All Zoom out to the maximum extents.
Draw Element Labels Toggle showing of labels in different formats.
Overview – 70
View Menu Commands Action
Draw Flow Directions Toggle flow direction arrows on reach elements.
Toolbars Toggle the file, components, and compute toolbars.
Clear Messages Clear all messages from the message window.
3 Commands available from the View menu
Component managers are opened from the Components menu. Program components include Grid Regions,
Basin Models, Meteorologic Models, Control Specifications, Time-Series Data, Paired Data, and Gridded
Data. A list of Components menu items and the resulting actions are provided in the following table.
Components Menu Commands Action
Create Component Open the Basin Model manager.
Basin Model Manager Open the Basin Model manager.
Meteorologic Model Manager Open the Meteorologic Model manager.
Control Specifications Manager Open the control specifications manager.
Time-Series Data Manager Open the time-series data manager.
Paired Data Manager Open the paired data manager.
Grid Data Manager Open the grid data manager.
Terrain Data Manager Opens the terrain data manager.
4 Commands available from the Components menu
The GIS menu contains menu commands to set the coordinate system of the Basin Model, perform
watershed delineation tasks, and georeferencing Basin Model elements, as listed in the table below.
GIS Menu Commands Action
Coordinate System View or set the Basin Model coordinate system.
Overview – 71
GIS Menu Commands Action
Terrain Reconditioning Use polygons and lines to edit the terrain (burn streams and build walls).
Preprocess Sinks Run the sink preprocessing step of the watershed delineation workflow.
Preprocess Drainage Run the flow direction and flow accumulation steps of the watershed
delineation workflow.
Identify Streams Run the stream identification step of the watershed delineation workflow.
Break Points Manager Open the break points manager.
Delineate Elements Complete the watershed delineation workflow by creating subbasin and
reach elements.
Split Element Split a selected subbasin or reach element at a point.
Merge Elements Merge two selected subbasin or reach elements.
Reverse Flow Direction Reverse the flow direction of a reach element.
Georeference Existing Georeference existing subbasin or reach elements using GIS files.
Elements
Import Georeferenced Import hydrologic elements from a GIS file.

Elements
Export Georeferenced Export subbasin or reach elements created using the watershed delineation
Elements workflow.
Compute Compute standard hydrologic or UTM grid cells for discretizing subbasin
elements.
5 Commands available from the GIS menu
Once the coordinate system has been set using the Coordinate System command, subbasin, reservoir, and
reach elements can be georeferenced using tools that are opened by selecting the Georeference Existing
Elements and Import Georeferenced Elements menu options. Setting the coordinate system and
georeferencing elements is optional. Some modeling methods, like the HMR 52 Storm Precipitation Method
requires subbasin elements to be georeferenced. One advantage to georeferencing elements is that that the
elements are drawn using polygons and polylines in the Basin Model map. You can display the elements
using icons and lines, GIS features, or both. The remaining menu commands are related to watershed
Overview – 72
delineation. The Preprocess Sinks, Preprocess Drainage, Identify Streams, and Delineate
Elements commands are functions that create transformations of terrain data in order to create a Basin
Model. Break Points Manager allows the user to manage break point elements needed for the delineation
process. Split Element and Merge Elements can be used on subbasin and reach elements that have been
created using the delineation process. Export Georeferenced Elements allows the user to export subbasin
and reach elements created using the delineation process. Commands will only be available if prerequisite
steps have been taken and the data necessary to perform the commands are available.
The Parameters menu contains menu commands to open Global Parameter Editors. Global parameter
editors let you view and edit subbasin and reach parameters for elements that use the same methods. The
table below provides a list of processes that can be globally edited.
Model Element Process
Basin Subbasin Discretization
Basin Subbasin Canopy
Basin Subbasin Surface
Basin Subbasin Loss
Basin Subbasin Transform
Basin Subbasin Baseflow
Basin Subbasin Erosion
Basin Reach Routing
Basin Reach Gain/Loss
Meteorologic Subbasin Snow
Meteorologic Subbasin Evapotranspiration
6 Processes that can be globally edited
For basin processes, global parameter menu options are only active if subbasin or reach elements in the
Basin Model use the method. For example, if the Parameter | Loss menu option is selected, a submenu with
all loss methods opens. Only loss methods used by subbasin elements in the current Basin Model will be
active in the menu. If hydrologic elements are selected in the Basin Model, then the selected elements
determine what menu items are available. The Parameters menu also contains menu commands to change
subbasin canopy, surface, loss, transform, and baseflow methods and reach routing and gain/loss methods.
Overview – 73
If subbasin or reach elements are selected in the Basin Model, then only the selected elements will change
methods. The last menu command on the Parameters menu is Element Inventory. This command lets you
view a table of all hydrologic elements in the Basin Model. If elements are selected, then only the selected
elements will be included in the table.
For meteorologic processes, Global Parameter Editors are available for snow methods and monthly-average
evapotranspiration. A Meteorologic Model that includes a snow method or monthly-average
evapotranspiration must be selected in the Watershed Explorer to enable the Global Editor menu item on the
Parameters menu. The Global Editor includes subbasins for all Basin Models that are linked to the
Meteorologic Model. The Meteorologic Model Global Editor can be filtered by basins, zones, or computation
points using the filters in the top left corner of the editor.
The Compute menu contains a list of commands for creating, computing, and managing Simulation Runs,
Optimization Trials, Forecast Alternatives, Depth-Area Analyses, and Uncertainty Analyses. A list
of Compute menu items and the resulting actions are provided in the table below. Menu commands for
creating Simulation Runs, Optimization Trials, Forecast Alternatives, Depth-Area Analyses and Uncertainty
Analyses are only enabled with the necessary underlying components have been created.
The Compute command is only enabled when a compute item is selected.
Compute Menu Commands Action
Create Compute Open a wizard to create a new simulation from among the
five types.
Simulation Run Manager Open the simulation run manager to create, copy, rename, or
delete runs.
Optimization Trial Manager Open the Optimization Trial manager.
Forecast Alternative Manager Open the Forecast Alternative manager.
Depth-Area Analysis Manager Open the depth-area analysis manager.
Uncertainty Analysis Manager Open the uncertainty analysis manager.
Run Calibration Aids When a run is selected, opens the calibration aids at a
computation point.
Forecast Initial Baseflow When a forecast is selected, choose observed flow for
automatically initializing subbasin baseflow
Forecast Initial Reach Outflow When a forecast is selected, choose observed flow for
automatically initializing reach flow
Overview – 74
Compute Menu Commands Action
Forecast Parameter Adjustments When a forecast is selected, opens the editor for loss rate
and other adjustments.
Forecast Slider Adjustments When a forecast is selected, choose parameter adjustments

for control by a slider.
Forecast Slider Settings When a forecast is selected, sets boundary range for each
slider.
Forecast Reservoirs When a forecast is selected, choose observed stage for

automatically initializing and adjusting reservoir storage.
Forecast Blending When a forecast is selected, opens the editor for observed
flow blending.
Multiple Compute Compute multiple simulations sequentially.
7 Commands available from the Compute Menu
The Results menu contains a list of commands for viewing results from hydrologic elements in a Basin
Model. Three cases must be met before commands from the Results menu are active:
1. A Simulation Run, Optimization Trial, Analysis, or Forecast Alternative must be selected.

2. A hydrologic element or elements must be selected.
3. The results for the simulation must be available.
Results for a simulation are available once the simulation has successfully computed. If you change
parameter data, like values in a paired data table used by a reach element for Modified-Puls routing, then the
simulation should be recomputed. The program keeps track whether results are out of date or still valid and
will display this information in results plots and tables. A list of Results menu items and the resulting actions
are provided in the table below.
Results Menu Commands Action
Global Summary Table1 Open a summary table containing all hydrologic elements
in the Basin Model.
Objective Function Summary2 Objective function value and statistics.
Optimized Parameters2 Optimized parameter values.
Overview – 75
Results Menu Commands Action
Hydrograph Comparison2 Comparison of computed and observed hydrographs.
Flow Comparison2 Computed versus observed flow values.
Flow Residuals2 Residual between computed and observed values.
Objective Function2 Objective function value by iteration.
Peak Flow Table3 Peak flow at analysis points.
Element Graph Open a graph of results for the current selection.
Element Summary Table Open a summary table for the current selection.
Element Time-Series Table Open a time-series table for the current selection.
Graph Properties Change the line styles, symbols, and other properties of
the selected graph.
8 Commands available from the Results menu
(1) are available for Simulations Runs, items with (2) are available for Optimization Trials, and items with (3)
are available for Depth-Area Analyses.
The Tools menu offers a list of specialized commands. A list of Tools menu items and the resulting actions
are provided in the table below. Additional tools will be added to the menu in a future program version.
Tools Menu Commands Action
Reach Table View and edit paired data functions for elevation-discharge,
elevation-area, and elevation-width.
Reservoir Tables View and edit paired data functions for elevation-discharge
and storage-discharge.
Parameter Sample Creator Convert the equilibrium sample from an Optimization Trial
using the MCMC search.
Data Tools available for modifying gridded datasets.
Overview – 76
Tools Menu Commands Action
Reports Generate reports of Basin Model or simulation run results

using a custom template.
Delete Results Delete time-series results for simulations.
Program Settings Change properties for the program.
9 Commands available from the Tools menu
The Help menu provides links to the online help system. The sample projects can be installed from this
menu. You may also access the terms and conditions for using the program, and information about the
program and development team; this information is helpful when reporting program problems.
5.1.2 Toolbar
Like the Menu System, the Toolbar groups tools with similar uses. Also, tools are inactive if the resulting
action for the tool can not be carried out by the program. The table below contains a description of tools on
the toolbar.
Tool Action
Create a new project.
Open an existing project.
Save the current project.
Print the selected item in the Desktop (Basin Map or result window).
Select hydrologic elements in the Basin Map.
Zoom tool.
Add a subbasin element to the Basin Map.
Overview – 77
Tool Action
Add a reach element to the Basin Map.
Add a reservoir element to the Basin Map.
Add a junction element to the Basin Map.
Add a diversion element to the Basin Map.
Add a source element to the Basin Map.
Add a sink element to the Basin Map.
Add a break point element to the Basin Map.
Compute the currently selected simulation run.
Compute the currently selected Optimization Trial.
Compute the currently selected Forecast Alternative.
Compute the currently selected depth-area analysis.
Compute the currently selected uncertainty analysis.
Open global summary table.
Open graph for the current element selection.
Overview – 78
Tool Action
Open summary table for the current element selection.
Open time-series table for the current element selection.
10 Description of the tools in the toolbar
5.1.3 Watershed Explorer

The Watershed Explorer was developed to provide quick access to all components and simulations in a
project. For example, the user can easily navigate from a Basin Model to a precipitation gage and then to a
Meteorologic Model without using menu commands or opening additional windows. The Watershed
Explorer is divided into three parts: Components, Compute, and Results.
A typical view of the Components tab of the Watershed Explorer is shown in the figure below.
2 Components tab in the Watershed Explorer.
Overview – 79
The hierarchical structure of model components, such as Basin Models, Meteorologic Models, etc., is
available from the Components tab. The Watershed Explorer organizes model components into individual
folders. If all component types were in a project, then the Components tab would contain seven main folders,
Terrain Data, Basin Models, Meteorologic Models, Control Specifications, Time-Series Data, Paired Data,
and Grid Data. The Watershed Explorer expands when one of these main component folders is selected.
When a component in a main folder is selected, the Watershed Explorer expands even more to show sub-
components. For example, when the Basin Models folder is selected, the Watershed Explorer expands to
show all Basin Models in the project. The Watershed Explorer will expand again to show all hydrologic
elements in a Basin Model when a Basin Model is selected. Notice in the figure above that the Castro 2 Basin
Model is selected and the Watershed Explorer is expanded to show all hydrologic elements in the Basin
Model. The plus/minus sign beside model components and sub-components can be used to expand or
collapse the Watershed Explorer. The Compute tab of the Watershed Explorer contains all project Simulation
Runs, Optimization Trials, Analyses, and Forecast Alternatives. Model results are available from the Results
tab of Watershed Explorer.
5.1.4 Desktop
The Desktop holds a variety of windows including Global Parameter Editors, and most importantly the Basin
Map. Result windows including graphs, summary tables, and time-series tables can be shown in the Desktop,
or optionally, outside the Desktop. All other windows cannot be moved outside of the Desktop area. The
Basin Map is used to develop a Basin Model. Hydrologic elements (subbasin, reach, reservoir, etc.) are added
from the toolbar and connected to represent the physical drainage network of the study area. Background
maps can be imported to help visualize the watershed. The Castro 1 Basin Map is shown in the figure below.
Overview – 80
3 Basin map for a basin model named Castro 2. The basin map is shown in the Desktop area of the program screen.
5.1.5 Component Editor

When a component or sub-component in the Watershed Explorer or hydrologic element in the Basin Map is
active (use the mouse and click on the component name in the Watershed Explorer or select the hydrologic
element in the Basin Map), a specific Component Editor will open. Data for model components is entered in
the Component Editor. Required data is indicated with a red asterisk. For example, loss parameter data for a
subbasin element is entered in the Component Editor for the subbasin. The Component Editor for the Castro
1 Basin Model is shown in figure below.
Overview – 81
4 A basin model component editor showing the name, description, and other parameter data.
5.1.6 Message Log

Notes, warnings, and errors are shown in the Message Log, as seen in the figure below. These messages are
useful for identifying why a Simulation Run failed or why a requested action, like opening a project, was not
completed.
5 Message Log showing recent messages generated while computing a simulation run.
5.2 Global Editors

Global Editors can be used to quickly edit information for all subbasins and reaches instead of editing
individual element Component Editors. Basin Model parameters can be edited globally from the Parameters
menu. Global Editors allow the user to edit element parameter values individually or in bulk. Values can be
transferred to and from tabulated data spreadsheets through simple copy and paste functions. The user can
calculate values based on physical subbasin characteristics or imported grid data for models that have been
georeferenced. The user can also filter data and sort elements.
Overview – 82
6 Loaded Global Editor for a Deficit and Constant
5.2.1 Opening the Global Editor

Select the Basin Model you wish to edit from the Watershed Explorer | Components tab. Click on the
Parameter menu and select the Parameter Type. Upon selecting a parameter to globally edit, a list of
available Methods for computing that parameter will be listed. The method(s) currently in use within your
Basin Model will be displayed in bolded text and unused methods will be greyed out. There will also be an
option listed to Change Method which allows you to change the method for all Basin Model elements or for
only the individual element selected from the Component tab. Both Subbasin and Reach parameters can be
edited from the Global Editor.
Menu options reflect the selected basin model elements. For example, if a junction element is selected in the
basin model then all Loss method menu options will be greyed out. You would need to unselect the junction
element before attempting to open a loss global editor.
Overview – 83
7 Accessing a Global Editor from a Parameters menu option
5.2.1.1 Subbasin Parameters:

• Discretization
• Canopy
• Surface
• Loss
• Transform
• Baseflow
• Snowmelt
• Evapotranspiration
5.2.1.2 Reach Parameters:

• Routing
• Loss/Gain
Overview – 84
5.2.2 Filter the Element List

In the Global Editor dialog box, the Filter dropdown menu allows you to display elements based on
Computation Point or Zone groupings you have previously designated. Click on the Filter dropdown menu. If
hydrologic elements are selected when opening a global editor then Initial Selection will be listed along with
Computation Point, Zone, and None. Select None to display all elements and remove any filters.
Select Filter | Computation Point to filter by computation point. A second dropdown menu will appear with a
list of Computation Points. Select the desired computation point to filter for only reach or subbasin elements
located upstream of that point.
Select Filter | Zone to filter by zone. Two additional dropdown menus will appear. The first dropdown menu
will list Configuration options. Select the desired configuration from the Configuration dropdown menu. The
second dropdown menu will list Zone options. Select the desired zone from the Zone dropdown menu to
filter for only elements assigned to that zone.
8 Filtering elements in a Global Editor
5.2.3 Sorting the Element List

In the Global Editor dialog box, the Sorting dropdown menu allows you to display elements sorted
Alphabetically (A to Z) or Hydrologically, from upstream to downstream. The hydrologic order is determined
by the element's proximity to the most downstream point, which HEC-HMS will recognize as the outlet. To
sort basin or reach elements by hydrologic order, select Hydrologic from the Sorting dropdown menu. To
sort basin or reach elements in alphabetic order, select Alphabetic from the Sorting dropdown menu.
Overview – 85
9 Sorting elements in a Global Editor
5.2.4 Manually Editing Global Editor Table

Values in the Global Editor table can be copied and pasted in for entire columns and rows or for only those
cells selected by the user. Click and drag your mouse to highlight the cells for which you want to copy in
values and hit CTRL+V on the keyboard or right click and select Paste. HEC-HMS has some additional built-in
tools to edit selected cells. Right click within the first selected row and select Fill. A variety of options will
appear in the Table Fill Options dialog in a separate window. Use the radio buttons to select the fill option
you want to use. Click OK and the fill operation will be applied to any selected cells in the Global Editor table.
Any updated values will appear highlighted in blue until applied.
Overview – 86
10 Table Fill Options available when editing data in the Global Editor Table
5.2.5 Calculator
The Global Editor dialog includes a Calculator function. The Calculator function allows you to calculate
parameters based on internal variables of physical watershed properties or user-imported gridded data. Click
the Calculator button and the Expression Calculator dialog box will open in a separate window.
Select the Parameter that you wish to calculate in the Field dropdown box in the Expression Calculator
dialog. The selected parameter will appear above the Expression window as the left side of the mathematical
expression as <Selected Parameter> =. The Variables window displays a list of available variables that you
can use in your expression. There are two tabs in the Variables window, Grids and Stats. In the Grids tab is a
list of user-imported gridded data. The Calculator uses a spatially averaged value for the grid cells that fall
within the bounds of each subbasin. The Stats tab displays a list of variables based on the physical
properties of your watershed's subbasin or reach elements. Double-click on a Grid or Stats variable to add it
to the Expression window. The Functions window displays a list of Visual Basic (VBA) math functions that
you can use in your expression. Below the functions window is a row of arithmetic operator buttons including
multiplication (*), division (/), addition (+), subtraction (-) and string concatenation (&). For more information
on the Expression Calculator, see Parameter Estimation (see page 275).
Overview – 87
11 Expression Calculator loaded from the Global Editor
Once the expression is complete. Click Calculate. The value of the selected parameter will be updated in the
Global Editor dialog and highlighted in blue. Click Close to close the Expression Calculator dialog window
and return to the Global Editor dialog window.
5.2.6 Applying Edits

Values updated in the Global Editor table either manually, computed in the Expression Calculator, or copied
in will be highlighted in blue. This indicates that these values are not saved or applied within the model.
Click Apply to save edits to parameter values and parameter values will change back to the default black text
within the table.
5.2.7 Computing from Global Editor

Simulation Runs can be computed directly from the Global Editor dialog window. Select the desired
Simulation Run from the Current Simulation Run dropdown menu. Select Compute | All Elements and click
the Compute button within the Global Editor dialog to compute results for the entire Basin Model and all
associated elements. In large complex models, it can be useful to compute isolated sections of the model.
Select the desired computation point from the Compute dropdown menu. This approach to computing
results can save time by not performing any calculations downstream of the selected computation point. A
window will automatically open that shows the progress of the compute.
Overview – 88
12 Selecting a Simulation Run to compute in the Global Editor
5.2.8 Exporting Values from Global Editor Table

Highlight cells by clicking and dragging to select cells you wish to copy out. Hit CTRL+V on the keyboard or
right click and select Copy. These cells will be copied to your clipboard and can be pasted into a table
external to the HEC-HMS program. The Global Parameter table can also be exported as a text file. Highlight
the cell you wish to export, right click, and select Export. To include table headings, click the Include column
labels box. The output text file will default to the model directory. Select the Browse button on the Table
Export Options to select a different folder directory and rename the output text file.
Overview – 89
13 Exporting values from the Global Editor Table
5.2.9 Closing the Global Editor

When desired updates have been successfully applied, click Close to close the Global Editor dialog window.
5.3 Program Settings

Additional program settings are available. Click the Tools menu and select the Program Settings command
to access the Program Settings window. This window allows you to change any of the optional settings as
shown in the figure below.
The General tab contains a number of settings for the general behavior of the program. This includes details
such as how much warning you want before making irreversible changes in modeling components, where to
display global editors, a display option for the decimal separator, language for displaying calendar dates, and
a display option for latitudes and longitudes.
Overview – 90
14 Program Settings window
The Basin Map tab contains settings for the Basin Map window. The settings include the option to
automatically re-center the map when selecting an element. The Basin Map tooltip precision, selection
highlight color, computation point color, and the directory used to save color ramps can also be selected.
The Defaults tab contains settings for the default unit system, subbasin component methods, and reach
component methods. These are the settings that will be used when new components are created. You can
always change the setting after the component is created.
The Compute tab contains settings for closing the compute progress if the compute is successful and other
details of how a compute is performed. Importantly, the buffer length controls how much memory is required
during a compute. When the length is set to a large value, the compute is optimized for speed but may
exhaust available memory. When the length is set to a small value, very large computes (large number of
elements or very long time windows) can be completed but the speed may be slower. You can set the
number of significant digits for parameter values when using parameter calculators from the Global
Parameter Editors or when using the Precipitation Depth Calculator in the Frequency Storm.
The Results tab contains a number of settings for managing simulations and the results that are produced.
Control is provided for where result windows are displayed and whether cumulative precipitation is displayed
rather than incremental precipitation. Finally, you can specify the number of decimal digits to use when
displaying different categories of results.
Overview – 91
The Messages tab contains settings for the error, warning, and note messages. You can select whether a
sound is played when a particular type of message occurs. You can also select whether notes or warnings
are displayed in the program console, or are written to the log file (errors are always displayed or written to
the log file.) Turning off messages to the program's Message Window and log file can save compute time for
optimization trials and uncertainty analysis simulations. You can also choose the color that is used to print
the message in the Message Log.
5.4 Data Conventions

The program must manage many different kinds of data that are part of a wide variety of components. Part
of the management is the saving and display of the data entered by the user. The remainder of the
management is the use of the data during a compute.
5.4.1 Saving Properties

The program uses the concept of the current component to manage saving updates or changes to
properties. The current component is the item in the project that is currently selected in the Watershed
Explorer. For example, if you click on a Subbasin icon in the Watershed Explorer it will become highlighted,
and its editor will be shown in the Component Editor. The subbasin becomes the current component at that
moment. You may make changes to the properties of the subbasin on any of the tabs in the Component
Editor. When you switch between tabs, any changes are automatically updated in the subbasin. The changes
are also updated when you leave the tabs and click anywhere else in the program interface. Even though the
updates are made in the subbasin properties, the changes are not saved to disk. Updates and changes are
only saved to disk when the project is saved. You can save the project two different ways.
The first way to save all pending changes is from the File menu. Click on the File menu and then select
the Save command. All components currently open in the project will be saved to disk, including the current
Basin Model with its hydrologic elements, current Meteorologic Model, current Control Specifications, and all
other project components.
The second way to save all pending changes is from the toolbar. Click the Save Current Project button. All
components in the project will be saved to disk.
5.4.2 Number Formatting

Each country of the world has socially accepted conventions for formatting numbers. It would be difficult for
the program to support every single convention in use around the world. However, one important factor is the
symbol used for the decimal separator. For example, in the United States a number would typically be
formatted as follows:
12.34
In Austria the same number would usually be displayed as follows:
12,34
Either format can be selected using the program settings described in Program Settings (see page 90). The
setting is used to interpret all user input and to configure all displayed output data.
Overview – 92
5.4.3 Date and Time Formatting

The formatting of dates and times is also subject to social convention. The program imposes some
limitations to simplify the formatting of date and time information. All dates should specify a two-digit day,
followed by the month abbreviation, and end with a four-digit year. For example, in the United States a date
would be entered or displayed as follows:
07Feb2004
The same date would be entered or displayed in France as follows:
07févr.2004
Dates will be processed using the common month abbreviation according to the language and country
selected in the program settings described in Program Settings (see page 90). The selected choice will be used
for displaying data information, for example, in computed results. The selected choice will also be used for
interpreting input, for example, when specifying the start time of a simulation.
All times are formatted with the same rules regardless of any settings on the computer. A time should use
two digits for the hour, followed by a colon, and end with two digits for the minutes. All times are assumed to
be in an arbitrary local time zone that does not observe summer time (daylight savings in the United States).
It uses 24-hour clock time instead of AM or PM notation. For example, time would always be displayed as:
14:25
Some status messages displayed by the program indicate when some event occurred. Those times also
include seconds.
The date system used in the program follows the Gregorian calendar. This calendar entered use at the end of
the day on 04 October 1582. It took many years for the calendar to gain wide-spread use in Europe. It
eventually became the most common calendar in use around the world. One of the principal features of the
calendar is the definition of leap year. Because the program does not implement the calendars that preceded
it, the leap year rules defined in the Gregorian calendar are applied throughout all time. This means that for
simulations with time intervals before 1582, the simulation results may show inconsistencies when
compared to the calendar actually in use during those ancient historical times.
5.4.4 Units Conversion

Almost all initial conditions and parameter data for the various methods included in the program require
units. For example, hydraulic conductivity has units of either millimeters per hour (mm/hr) or inches per hour
(in/hr) depending on the unit system of the Basin Model. The unit system is one of the properties of the
Basin Model and Meteorologic Model. If the system international unit system is selected for a Basin Model,
then the hydraulic conductivity should be entered in mm/hr. However, the conductivity should be entered in
in/hr if the U.S. customary unit system is selected. The units of an initial condition or parameter are shown in
parenthesis after the label.
The value of initial conditions and parameter data are automatically converted when the unit system of a
Basin Model or Meteorologic Model is changed. For example, suppose a Basin Model used the U.S.
customary unit system and a hydraulic conductivity was entered as 0.23 in/hr. If the unit system were
changed to system international, the conductivity would be automatically converted to 5.84 mm/hr. The
conversions are performed according to standards specified by the National Institutes of Standards and
Technology (Taylor 1995).
Overview – 93
Time-series data, paired data, and grid data components each have their own unit system based on the units
of the data. The unit system is determined automatically from the units of the data. For example, a discharge
time-series gage with units of cubic meters per second (M3/S) will be in the system international unit
system. The units are selected by the user for manual entry data, but are read automatically from the record
header for external DSS data. Data is automatically converted to the correct unit system during a compute.
5.4.5 Interpolation
Time-series data and gridset data are usually defined with a fixed time interval, though some data may be
defined on an irregular basis. All of the different types of simulations happen with a fixed time interval, as
specified in the control specifications. When the time interval of the time-series or gridset data does not
match the time interval of the compute, the data is automatically interpolated. A linear interpolation in time is
used.
Paired data components use a limited number of points to represent a curve, such as a storage-discharge
curve. However, the curve represents continuous data. Linear interpolation is used when a dependent value
is required for an independent value between two specified values. The interpolation is performed between
the dependent values corresponding to the closest available independent values on each side of the
requested value. Some paired data components use irregularly spaced values to represent an annual pattern,
such as a groundmelt pattern. Linear interpolation in time is used on these components.
5.5 Application Steps

The program is designed with reusable data sets that can be independently developed. However, some data
sets depend on others for important definitions. For example, gages must be created before they can be
used in Basin or Meteorologic Models. Consequently, there is a necessary sequence to successfully obtain
results. The remainder of this chapter provides an overview of the best procedure for obtaining computation
results.
5.5.1 Create a New Project

Create a new project by selecting the File | New menu command. After you press the button, a window will
open where you can name, choose a location on your computer or a network computer to save the new
project, and enter a description for the new project. If the description is long, you can press the button to the
right of the description field to open an editor. You should also select the default unit system; you can always
change the unit system for any component after it is created but the default provides convenience. Press
the Create button when you are satisfied with the name, location, and description. You cannot press
the Create button if no name or location is specified for the new project. If you change your mind and do not
want to create a new meteorologic model, press the Cancel button or the X button in the upper right of
the Create a New Project window.
5.5.2 Enter Shared Project Data

Shared Data includes Time-Series Data, Paired Data, and Grid Data. Shared Data is often required by Basin
and Meteorologic Models. For example, the Meteorologic Model typically requires precipitation observations.
In another example, a reach element using the Modified-Puls Routing Method requires a storage-discharge
relationship for the program to calculate flow through the reach. The following is a complete list of Shared
Data Types used by the program.
Overview – 94
All of the different types of Time-Series Data:

• Precipitation
• Discharge
• Stage
• Temperature
• Radiation
• Windspeed
• Air pressure
• Humidity
• Altitude
• Crop coefficient
• Snow water equivalent
• Sediment load
• Concentration
• Percent
• Evapotranspiration
• Sunshine
All of the different types of Paired Data:
• Storage-discharge
• Elevation-storage
• Elevation-area
• Elevation-discharge
• Inflow-diversion
• Diameter-percentage
• Cross sections
• Inflow-lag
• Outflow-attenuation
• Elevation-width
• Elevation-perimeter
• Area-reduction
• Unit hydrograph curves
• Percentage curves
• Duration-precipitation
• ATI-meltrate
• ATI-coldrate
• Groundmelt patterns
• Percent patterns
• Parameter value patterns
• Cumulative probability distributions
• Parameter value sample
All of the different types of Grid Data:
• Precipitation
• Temperature
Overview – 95
• Radiation
• Crop coefficient
• Storage capacity
• Percolation rate
• Storage coefficient
• Moisture deficit
• Impervious Area
• SCS curve number
• Elevation
• Cold content
• Cold content ATI
• Meltrate ATI
• Liquid water content
• Snow water equivalent
• Water content
• Water potential
• Air pressure
• Humidity
• Windspeed
• Precipitation-frequency
• Roughness
Open a Component Manager to add Shared Data to a project. Go to the Components menu and select Time-
Series Data Manager, Paired Data Manager, or Grid Data Manager command. Each one of these Component
Managers contains a menu for selecting the type of data to create or manage. The Paired Data Manager with
the Storage-Discharge data type selected is shown below. Once the data type is selected, you can use the
buttons on the right side of the component manager to add a New, Copy, Rename, and Delete a data type.
There is also a button that opens an editor where you can change the description of the selected component.
In the case of time-series data, the manager contains two extra buttons to add or delete time windows. A
time window is needed for entering or viewing time-series data.
Overview – 96
5.5.3 Describe the Physical Watershed

The physical watershed is represented in the Basin Model. Hydrologic elements are added and connected to
one another to model the real-world flow of water in a natural watershed. A description of each hydrologic
element is given in the table below.
Hydrologic Element Description
Subbasin The subbasin is used to represent the physical watershed. Given

precipitation, outflow from the subbasin element is calculated by
subtracting precipitation losses, calculating surface runoff, and adding
baseflow.
Reach The reach is used to convey streamflow in the basin model. Inflow to
the reach can come from one or many upstream elements. Outflow
from the reach is calculated by accounting for translation and
attenuation. Channel losses can optionally be included in the routing.
Junction The junction is used to combine streamflow from elements located

upstream of the junction. Inflow to the junction can come from one or
many upstream elements. Outflow is calculated by summing all inflows.
Source The source element is used to introduce flow into the basin model. The
source element has no inflow. Outflow from the source element is
defined by the user.
Sink The sink is used to represent the outlet of the physical watershed.
Inflow to the sink can come from one or many upstream elements.
There is no outflow from the sink.
Reservoir The reservoir is used to model the detention and attenuation of a

hydrograph caused by a reservoir or detention pond. Inflow to the
reservoir element can come from one or many upstream elements.
Outflow from the reservoir can be calculated using one of three routing
methods.
Diversion The diversion is used for modeling streamflow leaving the main
channel. Inflow to the diversion can come from one or many upstream
elements. Outflow from the diversion element consists of diverted flow
and non-diverted flow. Diverted flow is calculated using input from the
user. Both diverted and non-diverted flows can be connected to
hydrologic elements downstream of the diversion element.
11 Different kinds of hydrologic elements that can be used
Overview – 97
The Basin Model Manager can be used to add a new Basin Model to the project. Open the Basin Model
Manager by selecting the Components | Basin Model Manager command. The Basin Model Manager can be
used to copy, rename, or delete an existing Basin Model.
Hydrologic elements can be added to the Basin Map after it is created. Select the Basin Model in
the Watershed Explorer to open the Basin Map. If background map layers are available, add them to the
Basin Model before adding elements. Add an element by selecting one of the tools from the toolbar, and
clicking the left mouse button on the desired location in the Basin Map. Connect an element to a
downstream element by right-clicking the upstream element to access the Connect Downstream menu item.
Most hydrologic elements require parameter data so that the program can model the hydrologic processes
represented by the element. In the case of the subbasin element, many mathematical models are available
for determining precipitation losses, transforming excess precipitation to streamflow at the subbasin outlet,
and adding baseflow. In this document the different mathematical models will be referred to as Methods.
The available methods for subbasin and reach elements are shown in the table below.
Overview – 98
Hydrologic Element Calculation Type Method
Subbasin Discretization Structured
Unstructured
File Specified
Canopy Dynamic
Simple (also gridded)
Surface Simple (also gridded)
Loss Rate Deficit and constant (also

gridded)
Exponential
Green and Ampt (also gridded)
Layered Green and Ampt

(continuous simulation)
Initial and constant
SCS curve number (also

gridded)
Smith Parlange
Soil moisture accounting (also

gridded)
Overview – 99
Transform Clark unit hydrograph
Kinematic wave
ModClark
SCS unit hydrograph
Snyder unit hydrograph
User-specified s-graph
User-specified unit hydrograph
2D diffusion wave
Baseflow Bounded recession
Constant monthly
Linear reservoir
Nonlinear Boussinesq
Recession
Reach Routing Kinematic wave
Lag
Lag and K
Modified Puls
Muskingum
Overview – 100
Muskingum-Cunge
Normal Depth
Straddle stagger
Gain/Loss Constant
Percolation
12 Methods available in the subbasin and reach hydrologic elements
Parameter data is entered in the Component Editor. Select a hydrologic element in the Basin Map
or Watershed Explorer to open the correct Component Editor as shown in the figure below.
15 Component Editor for a reach element
Global Parameter Editors can also be used to enter or view parameter data for many hydrologic elements as
shown in the figure below. Global Parameter Editors are opened using the Parameters menu.
Overview – 101
16 Global editor for the Deficit and Constant Loss method
5.5.4 Describe the Meteorology

The Meteorologic Model calculates the boundary conditions required by elements in the Basin Model. The
main boundary condition is precipitation for subbasin elements. The Meteorologic Model can utilize both
point and gridded precipitation and has the capability to model frozen and liquid precipitation along with
evapo-transpiration. The Snowmelt Methods model the accumulation and melt of the snow pack. The
Evapo-Transpiration Methods include the Constant Monthly, Priestley Taylor, and Penman Monteith
methods, with gridded options available. An Evapo-Transpiration Method is only required when simulating
the continuous or long term hydrologic response in a watershed. When an energy balance evapo-
transpiration is selected, additional meteorologic variables must also be specified. A brief description of the
methods available for calculating basin average precipitation or grid cell precipitation is included in the table
below.
Precipitation Methods Description
Frequency storm Used to develop a precipitation event where depths for various
durations within the storm have a consistent exceedance
probability.
Gage weights User specified weights applied to precipitation gages.
Gridded precipitation Allows the use of gridded precipitation products, such as

NEXRAD radar.
Overview – 102
Precipitation Methods Description
Inverse distance Calculates subbasin average precipitation by applying an

inverse distance squared weighting with gages.
HMR 52 storm Probable maximum precipitation (PMP) using the HMR52

procedure.
Hypothetical storm Applies a user specified SCS time distribution to a 24-hour total
storm depth.
Specified hyetograph Applies a user defined hyetograph to a specified subbasin

element.
Standard project storm Uses a time distribution to an index precipitation depth.
13 Precipitation methods available for describing meteorology
Use the Meteorologic Model Manager to add a new Meteorologic Model to the project. The Meteorologic
Model Manager can also be used to copy, rename, and delete an existing Meteorologic Model.
5.5.5 Enter Simulation Time Windows

A Simulation Time Window sets the time span and time interval of a Simulation Run. A Simulation Time
Window is created by adding a Control Specifications to the project. This can be done using the Control
Specifications Manager. Besides creating a new Simulation Time Window, the Control Specifications
Manager can be used to copy, rename, and delete an existing window.
Once a new Control Specifications has been added to the project, use the mouse pointer and select it in
the Watershed Explorer. This will open the Component Editor for the Control Specifications as shown below.
Information that must be defined includes a Starting Date and Time, Ending Date and Time, and Time
Interval.
17 Control specifications component editor. The starting date and time are required, along with the ending date and time
Overview – 103
5.5.6 Simulate and View Results

A Simulation Run calculates the precipitation-runoff response in the Basin Model given input from the
Meteorologic Model. The Control Specifications define the time period and time interval. All three
components are required for a Simulation Run to compute.
Create a new Simulation Run by selecting the Compute | Create Simulation Run menu option. A wizard will
open to step you through the process of creating a Simulation Run as shown in the figure below. First, enter a
Name for the simulation. Then, choose a Basin Model, Meteorologic Model, and Control Specifications.
After the Simulation Run has been created, select the simulation in the Compute toolbar. Click the drop down
arrow to see all simulations in the project. Choose the correct simulation. To compute the simulation, re-
select the Compute menu and choose the Compute Run option at the bottom of the menu. Or you can click
the Compute All Elements icon from the Compute toolbar,
18 Create a Simulation Run wizard
Results can be accessed from the Basin Map and the Watershed Explorer | Results tab. Results are available
as long as the simulation has been successfully run. The program will keep track whether the results reflect
the current state of the model. If the model has changed since the last time the simulation was computed,
then the program will display a message about the results being out of date, and that the modeler should re-
compute the simulation to update the results.
The simulation must be selected (from the Compute toolbar) before results can be accessed from the Basin
Map. After the Simulation Run is selected, select the hydrologic element where you want to view results.
While the mouse is located on top of the element icon, click the right mouse button. In the menu that opens,
Overview – 104
select the View Results option. As shown below, three result types are available: Graph, Summary Table,
and Time-Series Table.
19 Accessing results for the current simulation run using the basin map
These results can also be accessed through the toolbar and the Results menu. A hydrologic element must be
selected before the toolbar buttons and options from the Results menu are active. A Global Summary Table
is available from the Compute toolbar and Results menu. The Global Summary Table contains peak flows
and time of peak flows for each hydrologic element in the Basin Model.
Overview – 105
Results can also be viewed from the Watershed Explorer | Results tab. Select the Simulation Run and
the Watershed Explorer will expand to show all hydrologic elements in the Basin Model. If you select one of
the hydrologic elements, the Watershed Explorer expands again to show all result types as shown in the
figure below.
20 Selecting simulation run results from the Watershed Explorer
For a subbasin element, you might see Outflow, Incremental Precipitation, Excess Precipitation,
Precipitation Losses, Direct Runoff, and Baseflow as the output results. Select one of these results to open a
Preview Graph. Multiple results can be selected and viewed by holding down the Control or Shift buttons.
Results from multiple hydrologic elements can be viewed together. Also, results from different Simulation
Runs can be selected and viewed. Once output types are selected in the Watershed Explorer, a larger graph
or time-series table can be opened by selecting the Graph and Time-Series buttons on the Compute toolbar.
5.5.7 Create or Modify Data

Many hydrologic studies are carried out to estimate the change in runoff given some change in the
watershed. For example, a residential area is planned in a watershed. The change in flow at some point
downstream of the new residential area is required to determine if flooding will occur as a result of the new
residential area. If this is the case, then two Basin Models can be developed. One is developed to model the
current precipitation-runoff response given predevelopment conditions and another is developed to reflect
future development.
An existing Basin Model can be copied using the Basin Model Manager or the right mouse menu in
the Watershed Explorer. In the Watershed Explorer, Components tab, select the Basin Model. Keep the
Overview – 106
mouse over the selected Basin Model and click the right mouse button. Select the Create Copy menu item to
copy the selected Basin Model. The copied Basin Model can be used to model the future development in the
watershed.
To reflect future changes in the watershed, method parameters can be changed. For example, the percent
impervious area can be increased for a subbasin element to reflect the increase in impervious area from
development. Routing parameters can also be adjusted to reflect changes to the routing reach.
5.5.8 Make Additional Simulations and Compare Results

Additional simulations can be created using new or modified model components. Results from each
Simulation Run can be compared to one another in the same graph or time-series table. Select the
Results tab in the Watershed Explorer. Select each Simulation Run that contains results you want to
compare. The Watershed Explorer will expand to show all hydrologic elements in the Basin Models. Select
the hydrologic element in all Simulation Runs where results are needed. This will expand the Watershed
Explorer even more to show available Result Types. Press the Control key and select each output result from
the different Simulation Runs. When a Result Type is selected the result is added to the preview graph. Once
all the results have been selected, a larger graph or time-series table can be opened by selecting
the Graph and Time-Series buttons on the Compute toolbar as seen in the figure below.
21 Comparison of results from two different simulation
Overview – 107
5.5.9 Exit the Program

Save the project by selecting the File | Save menu item. After the project is saved, exit the program by
selecting the File | Exit menu item.
5.6 References: Overview

Taylor, B. 1995. Special Publication 811: Guide for the Use of the International System of Units (SI). United
States Department of Commerce, National Institute of Standards and Technology. Gaithersburg, MD.
Overview – 108
6 Projects and Control Specifications

A Project serves as a container for all the different parts that together form the complete representation of a
watershed. Control Specifications are one of the main components of a Project, and are principally used to
control Simulation Runs. The remainder of the Project components are described in later sections. This
section describes how to create and manage Projects. It also includes information on how the file system is
used by the program to organize and access the files that represent the Project components. Finally, it
describes the Control Specifications.
6.1 Projects
A Project represents all of the input data and simulation output necessary to answer an engineering
question. Possible questions could include the following:
• What will be the flow rate at the bridge due to a 1% storm?
• How will the average in-stream flow depth for the month of July change after the operation schedule
of an irrigation diversion is modified?
• What is the impact of changing the land use on 7% of the watershed from cow pasture to home sites?
• How will the frequency curve be affected by building a reservoir?
The questions may involve a single watershed or several adjacent watersheds. There may only be a single
representation of the watershed, or multiple representations may be needed for different future scenarios.
The Project is flexible enough to work with any of these applications.
6.1.1 Creating a New Project

Select the File | New menu command to create a new Project. After this command is selected, the Create a
New Project window will open where you can name, select the location on your computer or network server
to store the Project, and describe the Project with a description (illustrated in the following figure). If the
Project description is long you can use the button to the right of the description field to open an editor. A
default location is provided. The default location for creating new Projects is specified in the program
settings described in Program Settings4. You are not required to use the default directory and may create a
new Project on the local computer or a network resource anywhere your security limitations permit. All
Project files created by the program will be saved in a folder (the folder name is the name of the Project) in
the location entered. Select the default unit system for creating new components. The unit system of a
component can always be changed after it is created. Press the Create button when you are satisfied with
the name, location, and description. You cannot press the Create button if no name or location is specified. If
you change your mind and do not want to create a new Project, press the Cancel button or the X button in the
upper right to close the window. The Create a New Project window can also be opened by pressing
the Create a New Project button on the toolbar.
4 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/.Program+Settings+v4.4
Projects and Control Specifications – 109

22 Creating a new Project
6.1.2 Opening a Project

Open a Project by selecting the File | Open menu option. After this option is selected, the Open an Existing
Project window will open as shown in the following figure. This window contains all Projects in the
Watershed List. The Watershed List contains all Projects previously opened by the program. Open a Project
by clicking the Project name and pressing the Open button. You may also double-click a Project name to
open it. You cannot press the Open button if no Project is selected.
23 Opening a project
If the Project you want to open is not in the list, press the Browse button. The Select Project File window
opens that lets you navigate to the directory containing the desired Project. If you change your mind and do
not want to open a Project, press the Cancel button or the X button in the upper right to close the window.

The Open an Existing Project window can also be opened by pressing the Open a Project button on the
toolbar.
24 Browsing to open a project that has not been opened previously
6.1.3 Copying a Project

Copy a Project by selecting the File | Save As menu option. After this option is selected, the Save Current
Project As window will open where you can name, select the location on your computer or network server to
store the Project, and describe the Project as shown below. A default location is provided. The default
location for creating new Projects is specified in the program settings described in Program Settings5.
25 Copying the current Project
You are not required to use the default directory and may copy a Project to the local computer or a network
resource anywhere your security limitations permit. All Project files will be copied to a folder (the folder name

is the name of the Project) in the location entered. If the Project description is long you can use the button to
the right of the description field to open an editor. Press the Copy button when you are satisfied with the
name, location, and description. You cannot press the Copy button if no name or location is specified. If you
change your mind and do not want to create a copy, press the Cancel button or the X button in the upper
right to close the window.
There is one option in this window that needs extra attention. The option, Copy DSS data (time-series,
paired, grid data), will copy all external DSS records defined in the Project and place the copied records into
DSS files in the new Project folder. Internal DSS files are always migrated to the new project directory.
External DSS files are only migrated if this box is checked; otherwise, a reference to the old project directory
is made. Time-series, paired, and grid data are copied into separate DSS files. All references to these DSS
records are automatically updated.
6.1.4 Renaming a Project

Rename a Project by selecting the File | Rename menu option. After this option is selected, the Rename
Current Project window opens. The window shows the current Project name and description and contains a
text box for you to enter the new Project name and description. If the Project description is long you can use
the button to the right of the description field to open an editor. Press the Rename button when you are
satisfied with the name and description. You cannot press the Rename button if no name is specified. If you
change your mind and do not want to rename the Project, press the Cancel button or the X button in the
upper right to close the window.
26 Renaming the current Project Name
6.1.5 Deleting a Project

Delete a Project by selecting the File | Delete menu item. The Delete Current Project window will open. This
window contains the Project name and description and three choices for deleting the Project. The first
option, Watershed entry in watershed list only (all files remain intact), will only delete the Project from the
Watershed List. The Watershed List contains all Projects previously opened by the program. No files are
deleted when this option is selected. The second option, Watershed entry and all watershed files (external

files remain intact), will delete the Project from the Watershed List and delete all Project files. Project files
include .hms, *.basin, etc. (refer to the table in Directories and Files6 for a complete list of Project files). No
external files are deleted when this option is selected. External files include DSS, grid cell, and background
map layer files. The third option, Watershed entry, watershed files, and all external files, will delete the
Project from the Watershed List, all files created by the program for this Project, and all external files
referenced by the Project (DSS, grid cell, and background map layer files). It is very important to keep in mind
that the third option will delete external files which could be used by other Projects. After the appropriate
option is selected, press the Delete button. Once a Project has been deleted it cannot be retrieved or
undeleted. If you change your mind and do not want to delete the Project, press the Cancel button or
the X button in the upper right to close the window.
27 Preparing to delete the current Project
6.1.6 Project Properties

Basic properties and settings for the Project are provided in the Component Editor for the Project. Access
the Component Editor on any tab of the Watershed Explorer. The highest level folder is labeled with the
Project name; click on the Project name to display the Component Editor.
6 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/Directories+and+Files

28 Project component editor accessed by clicking on the top node of the Watershed Explorer
The description can be used to provide internal documentation. It is helpful to include notes and comments
within the Project to remind yourself of details at a later time. It also helps with providing information to other
users who may work with the Project in the future. If the description is short, you can type it directly into the
description field. For long descriptions, you can press the editor button to the right of the description field.
The description editor makes it easier to enter and edit long descriptions.
Manual entry time-series gages and paired data are written to the Project DSS File by default. However, you
can change the file where results are written. If you wish, you can press the Folder button to the right of the
File field to open a File Browser for locating the file. The file browser is set to locate files with the DSS
extension. If you change your mind about searching for a different output file, you can press
the Cancel button or the X button in the upper right of the browser window. Press the Select button after you
locate and highlight the desired file. It is possible to have more than one Project write output results to the
same DSS file. However, the separate Projects are not synchronized and extreme care must be taken in
naming components in order to avoid conflicts.
6.2 Directories and Files

The program automatically creates and manages many different files, all of which are stored in the Project
Directory. A Project Directory is automatically created in the file system when a new Project is created. Even
though multiple Projects can be stored in the same directory, it is recommended that each Project be stored
in a separate directory. Separate directories improve file system organization and facilitate archiving by
external backup software.
6.2.1 Files Generated by the Program

Each data set or class of data sets is stored in a separate file in the Project Directory. The names used for
components or data sets are automatically converted to filenames for the files. Underscores are substituted
for special characters not allowed by the operating system. For example, a Basin Model named North Branch
would be stored in the file North_Branch.basin. A complete list of files used by the program is shown in the
table below. A majority of the files are in ASCII format but the user should never need to look at the files.
Management should always be performed using program commands in the graphical user interface since
some information is stored in multiple files. The program may not operate correctly when files are
unsynchronized because of external management operations.

Filename Description
Castro.access Control file; contains no data.
Castro.dsc Catalog of the Project DSS File to speed finding specific records.
Castro.dss Project DSS File containing manual entry time-series gages and
paired data.
Castro.gage List of all time-series gages.
Castro.grid List of all grid data.
Castro.hms Project definition including lists of Basin Models, meteorologic

models, and control specifications.
Castro.log All messages are recorded in the log file except for messages
generated during a compute. Each compute component has its
own log file.
Castro.nals List of all depth-area analyses.
Castro.out List of all data read or written from DSS files.
Castro.pdata Listing of all paired data.
Castro.regn List of grid regions.
Castro.run List of simulation runs with their properties and the time of last
compute.
North_Branch.basin Configuration for element properties, channel network, zones, and

map layers. One per basin.
Historic_Calib.met Configuration for precipitation, evapotranspiration, and snowmelt

data. One per meteorologic model.

Oct_1977.control Configuration for start time, end time, and time interval. One per
control specifications.
Castro.trial List of all the optimization trials.
Est_Baseflow.optim Optimization trial properties including search method, objective

function, and parameters.
Castro.fcstList list of all forecast alternatives.
DryStart.forecast Forecast alternatives properties including start and end times,

blending controls, and parameter adjustments. One per forecast
alternative.
Summer.mca Uncertainty analysis properties including start and end times, and
parameter sampling.
Castro.stateIndex List of all the saved states.
Mid_Oct_77.state Saved state information for all the hydrologic elements in a

specific Basin Model.
14 Files created by the program for storing component data. Sample names have been used assuming a project named Castro, that
contains a basin model named North Branch, a meteorologic model named Historic Calib, and a control specifications named Oct 1977.
It is also assumed that all features of the program are used including an optimization trial named Est Baseflow, and a saved state
named Mid Oct 77.
6.2.2 Files Specified by the User

Files that are not automatically created and managed by the program can be added to the Project Directory
by the user. Optional background map files can be added and used in Basin Models. The grid cell file
required by the ModClark Gridded Transform Method must be created external to the program. These
optional and required files can be stored at any location on the computer file system, but it is often
convenient to store them in the Project Directory. Additional supplementary files, related to the Project but
not used by the program, can also be placed in the Project Directory and will be ignored. However, when a
Project is copied, only files used by the program will be copied.
6.2.3 Manually Entered Time-Series and Paired Data

The Project DSS File stores all time-series and paired data that is manually entered by the user. The data
entered by the user is automatically stored as a record in the file. When the data is edited the record is
automatically updated. The record is automatically updated if the time-series gage or paired data function is
renamed, copied, or deleted. The record can be accessed by other programs that can read and write in the
DSS format.

Each DSS record contains only one type of data. Information about the data is stored in a header inside the
record. The header for time-series data includes the record name, whether the data is on a regular or irregular
time interval, start date and time, end date and time, number of values, measurement units, and data type.
The header for paired data includes the record name, number of curves, measurement units of the first
series, data type of the first series, measurement units of the second and subsequent series, and data type
of the second and subsequent series.
6.2.4 Computed Results

By default, all computed results are stored in the Simulation DSS File. However, the user has the option of
changing the file where computed results are stored. Any manually entered time-series or paired data will
continue to be stored in the Project DSS File regardless of the file used for computed results. If the computed
results are stored in a different file, that file can be safely deleted without affecting the program. However, it
is not possible to view results after deleting the file where they are stored.
The result from each element is stored in a separate record. Some elements compute different types of
results; each result is stored in a separate record. The record is identified with a pathname. Each record
pathname contains six parts called the A-part, B-part, C-part, D-part, E-part, and F-part. The pathname parts
are separated with a slash and may contain spaces. The complete pathname, including slashes and spaces,
can total up to 256 uppercase characters. The following is an example of a pathname for the computed flow
at a hydrologic element named Sand Cr in Simulation Run Plan 3A:
//SAND CR/FLOW/01JAN1985/1HOUR/RUN:PLAN 3A/
A consistent naming convention is used for assigning the different pathname parts of the computation
results (HEC, 1994). The B-part is assigned the name of the element in the Basin Model. The C-part is
assigned a data descriptor as described in Appendix A. The D-part is assigned the simulation start date. The
E-part is assigned the simulation time interval. The F-part begins with a three-letter code that identifies the
type of computed result, followed by a colon and the name of the compute component.
6.2.5 External Time-Series, Paired, and Grid Data

Any time-series or paired data that is not manually entered must be stored in an External DSS File. Grid data
cannot be manually entered and so must be stored in an External DSS File. External DSS Files are all DSS
files used in a Project except the Project DSS File which was created to store model data. The external files
can store regular or irregular interval time-series data, paired data, or grid data. They can be located
anywhere on the computer or network and shared with other programs. This program automatically
determines the data type, units, and interval from the record header.
6.2.6 Security Limitations

The program can create a Project on the local computer or on any accessible network device. Creating a
Project requires the user to have read and write permission for the folder that will contain the new Project.
Usually the system administrator determines where a user has permission to read and write. Depending on
the security settings assigned to the user by the system administrator, the program may not be able to create
a Project in some folders. As a user, be sure you understand where you have permission to create new
Projects. No other privileges beyond read and write permission are required to use the program; it is fully
compatible with operating in a so-called reduced privilege environment.
The program automatically checks all of the Project files for read and write permission every time the Project
is opened. If any of the files are read-only, then the program will not be able to open the Project and an error
message will be displayed. If a Project was previously accessible but becomes inaccessible, it is possible

that the file permissions were changed external to the program. It is also possible for the files to have read-
only permission if they are copied from a CD-ROM or other removable storage media. If the files have been
set to read-only permission for any reason, you will need to manually change the permissions on the files
before the program can open the Project. If you are using the Microsoft Windows® operating system, you
can change file permissions using Windows Explorer. On the Linux® operating systems, you can open a
command window and use the chmod command.
The program is designed to work with Projects that may be shared by several users. Usually shared Projects
will be stored on a server or network storage device, but could be stored in a shared folder on a local
computer. All users who will share the Project must have read and write permission for that folder. Even
though several users may share the Project, only one user can access the Project at a time. The program
automatically tracks how many users are accessing a Project and limits access as necessary.
6.3 Control Specifications

Control Specifications are one of the main components in a Project, even though they do not contain much
parameter data. Their principle purpose is to control when simulations start and stop, and what time interval
is used in the simulation.
6.3.1 Creating a New Control Specifications

A new Control Specifications is created using the Control Specifications Manager. To access the manager,
click on the Components menu and select the Control Specifications Manager command. The manager will
open and show all of the Control Specifications currently in the Project. The manager can remain open while
you manage Control Specifications or while you perform tasks elsewhere in the program. You can close the
manager using the X button in the upper right corner. The buttons to the right of the specifications list can be
used to manage existing specifications or create a new one. To create a new Control Specifications, press
the New button. After you press the button, a window will open where you can name and describe the new
Control Specifications that will be created. A default name is provided for the new specifications; you can
use the default or replace it with your own choice. A description can also be entered. If the description is
long, you can press the button to the right of the description field to open an editor. The editor makes it easy
to enter and edit long descriptions. When you are satisfied with the name and description, press
the Create button to finish the process of creating the new Control Specifications. You cannot press
the Create button if no name is specified for the new specifications. If you change your mind and do not
want to create a new Control Specifications, press the Cancel button or the X button in the upper right to
return to the Control Specifications Manager window.
29 Creating new control specifications

6.3.2 Copying a Control Specifications

There are two ways to copy a Control Specifications. Both methods for copying a Control Specifications
create an exact duplicate with a different name. Once the copy has been made it is independent of the
original and they do not interact.
The first way to create a copy is to use the Control Specifications Manager, which is accessed from
the Components menu. Select the Control Specifications you wish to copy by clicking on it in the list of
current Control Specifications. The selected Control Specifications is highlighted after you select it. After you
select a Control Specifications you can press the Copy button on the right side of the window. A new Copy
Control Specifications window will open where you can name and describe the copy that will be created. A
default name is provided for the copy; you can use the default or replace it with your own choice. A
description can also be entered; if it is long you can use the button to the right of the description field to open
an editor. When you are satisfied with the name and description, press the Copy button to finish the process
of copying the selected Control Specifications. You cannot press the Copy button if no name is specified. If
you change your mind and do not want to copy the selected Control Specifications, press the Cancel button
or the X button in the upper right to return to the Control Specifications Manager window.
30 Creating a copy of a Control Specifications
The second way to copy is from the Components tab of the Watershed Explorer. Move the mouse over the
Control Specifications you wish to copy, then press the right mouse button. A context menu is displayed that
contains several choices including Copy. Click the Create Copy command. A new Copy Control
Specifications window will open where you can name and describe the copy that will be created. A default
name is provided for the copy; you can use the default or replace it with your own choice. A description can
also be entered; if it is long you can use the button to the right of the description field to open an editor.
When you are satisfied with the name and description, press the Copy button to finish the process of copying
the selected Control Specifications. You cannot press the Copy button if no name is specified. If you change
your mind and do not want to copy the selected Control Specifications, press the Cancel button or
the X button in the upper right of the Copy Control Specifications window to return to the Watershed
Explorer.

31 Copying a Control Specifications from the Watershed Explorer
6.3.3 Renaming a Control Specifications

There are two ways to rename a Control Specifications. Both methods for renaming a specifications change
its name and then all references to the old specifications name are automatically updated to the new name.
The first way to perform a rename is to use the Control Specifications Manager, which you can access from
the Components menu. Select the Control Specifications you wish to rename by clicking on it in the list of
select a Control Specifications you can press the Rename button on the right side of the window. A
new Rename Control Specifications window will open where you can provide the new name. If you wish you
can also change the description at the same time. If the new description will be long, you can use the button
to the right of the description field to open an editor. When you are satisfied with the name and description,
press the Rename button to finish the process of renaming the selected Control Specifications. You cannot
press the Rename button if no name is specified. If you change your mind and do not want to rename the
selected Control Specifications, press the Cancel button or the X button in the upper right of the Rename
Control Specifications window to return to the Control Specifications Manager window.
32 Renaming a Control Specifications
The second way to rename is from the Components tab of the Watershed Explorer. Select the Control
Specifications you wish to rename by clicking on it in the Watershed Explorer; it will become highlighted.
Keep the mouse over the selected specifications and click the right mouse button. Select the Rename
command from the menu and the highlighted name will change to editing mode as shown in the following

figure. You can then move the cursor with the arrow keys on the keyboard or by clicking with the mouse. You
can also use the mouse to select some or all of the name. Change the name by typing with the keyboard.
When you have finished changing the name, press the Enter key to finalize your choice. You can also finalize
your choice by clicking elsewhere on the Components tab. If you change your mind while in editing mode and
do not want to rename the selected Control Specifications, press the Escape key.
33 Renaming a control specifications in the Watershed Explorer
6.3.4 Deleting a Control Specifications

There are two ways to delete a Control Specifications. Both methods for deleting a Control Specifications
remove it from the Project and then automatically update all references to that Control Specifications. Once
a Control Specifications has been deleted it cannot be retrieved or undeleted. Any references to the deleted
Control Specifications will switch to using no Control Specifications, which is usually not a valid choice
during a simulation. At a later time you will have to go to those components and manually select a different
Control Specifications.
The first way to perform a deletion is to use the Control Specifications Manager, which you can access from
the Components menu. Select the Control Specifications you wish to delete by clicking on it in the list of
select a Controls Specifications you can press the Delete button on the right side of the window. A window
will open where you must confirm that you wish to delete the selected Control Specifications as shown
below. Press the OK button to delete the Control Specifications. If you change your mind and do not want to
delete the selected Control Specifications, press the Cancel button or the X button in the upper right to return
to the Control Specifications Manager window.

34 Deleting a control specifications in the Control Specifications Manager
The second way to delete is from the Components tab of the Watershed Explorer. Select the Control
Specifications you wish to delete by clicking on it in the Watershed Explorer; it will become highlighted. Keep
the mouse over the selected Control Specifications and click the right mouse button. A context menu is
displayed that contains several choices including delete. Click the Delete command. A window will open
where you must confirm that you wish to delete the selected Control Specifications. Press the OK button to
delete the Control Specifications. If you change your mind and do not want to delete the selected Control
Specifications, press the Cancel button or the X button in the upper right to return to the Watershed Explorer.
35 Deleting a Control Specifications in the Watershed Explorer

6.3.5 Time Window

Each Control Specifications sets the Time Window over which a simulation will be performed. The time
window is specified using a separate Start Date, Start Time, End Date, and End Time. There is no limit on the
length of a time window, or the number of simulation time steps it can contain. The program contains
simulation methods suitable for both event and continuous simulation. Whether a particular simulation is
considered event or continuous depends on the length of the time window set in the Control Specifications
and the methods chosen in the Basin Model.
The program is capable of processing dates from 1583 AD through 4000 AD. All dates are processed
according to the rules specified in the Gregorian calendar for leap year. The format for specifying a date is to
use two digits for the day, followed by the three-letter month abbreviation, and finally the four digit year. Two
digit years are never used for entering or displaying dates. For example, the date February 8, 1936 should be
entered as follows:
08Feb1936
It is very important to use the correct format or the date you enter may be incorrectly interpreted. If the
program is not able to interpret a date, the entry field will become blank. The same format is used for both
start and end dates, and for dates throughout the program.
The program processes times assuming an arbitrary local time zone that does not observe summer time
(daylight savings in the United States). It uses 24-hour clock time instead of AM or PM notation. Time
windows can only be entered with minute resolution. Times may range from 00:00 at the beginning of a day
to 23:59 at the end. If a time of 24:00 is entered, it is automatically converted to 00:00 on the following day.
For example, the time of 2:15:00 PM should be entered as follows:
14:15
It is very important to use the correct format, including the colon, or the time may be incorrectly interpreted.
The same format is used for start and end times, and for times throughout the program.
Enter or edit the time window in the Component Editor for the Control Specifications. Access the editor from
the Watershed Explorer on the Components tab by clicking on the desired Control Specifications icon. Type
the date and time information in the appropriate fields.
36 An example of a Control Specifications component editor

6.3.6 Time Interval

Each Control Specifications includes the Time Interval that will be used to perform computations during a
simulation. The same interval will be used when viewing time-series results from the simulation. In some
cases, computations may be carried out at a shorter time interval and results interpolated to the interval
specified in the Control Specifications. Some methods in the Basin Model have parameters that are sensitive
to time interval. Those parameters should be estimated with knowledge of the time interval in the Control
Specifications.
Time-series gage data and grid data are interpolated to the time interval during a simulation. The original
data stored for the gage or grid is not altered; the available data is interpolated as part of the simulation
process and is not retained. The interpolation is performed linearly in time between the available data points.
Specify the time interval in the Component Editor for the Control Specifications (illustrated in the previous
figure). Access the editor from the Watershed Explorer on the Components tab by clicking on the desired
Control Specifications icon. Select the desired time interval from the list of available choices. The possible
choices range from 1 minute to 1 day.
It is important that any minutes included in a start or end time be an integer multiple of the time interval. For
example, if the time interval were chosen to be 10 minutes, then the start or end time could be 10:00, 10:10,
10:20 or other multiples of 10 minutes. For the same time interval of 10 minutes, the start or end time could
not be 10:07 because that is not an integer multiple of the time interval.
6.4 Importing HEC-1 Files

The program can import HEC-1 Files formatted for the 1981 and newer program versions. Some of the
computation options available in HEC-1 are not available in the program. Unrecognized input data is
automatically ignored during the import process and reported in the import log. However, the import process
is generally successful in separating the input file into component parts for addition to the current Project.
The job description and initialization data records become Control Specifications. The hydrograph
calculation data records are separated into a Basin Model and Meteorologic Model. Precipitation and flow
gages are created when necessary. Imported components should always be checked for accuracy.
6.4.1 Selecting and Processing a File

You can import an existing HEC-1 File into the current Project (HEC, 1998). The HEC-1 program used a single
file to contain all of the data necessary to perform a simulation. The import process will read the file and
create equivalent components for time-series and paired data. It will create a Basin Model, Meteorologic
Model, and Control Specifications. It is left to the user to check all of the imported data and create a
simulation run to obtain results. Because of more advanced numerical analysis techniques used in the
program, results may not match exactly the results obtained with HEC-1.
Begin the process of importing a HEC-1 File by clicking File menu and selecting the Import | HEC-1
File command. An Import HEC-1 File window opens where you can specify the HEC-1 File to be imported as
seen in the figure below. If you do not know which file you want to import, you can click the button to the
right of the file name field to open a File Browser. Use the browser to navigate the file system and find the
correct HEC-1 File. The browser will allow you to select HEC-1 Files, which usually end with the DAT or HC1
extensions. Once you have located and selected the desired HEC-1 File, press the Select button. If you
change your mind about selecting a file, you can press the Cancel button or the X button in the upper right of
the browser to return to the Import HEC-1 File window without selecting a file. If you change your mind about

importing a HEC-1 File, you can press the Cancel button or the X button in the upper right of the Import HEC-1
File window.
37 Selecting a HEC-1 file to import
After you specify the HEC-1 File to import, you must enter the name of the Basin Model, Meteorologic
Model, and Control Specifications. You can use the default names that are provided or you can enter your
own names. You can always rename the components at a later time. If the HEC-1 File includes ZR records for
loading time-series data from a HEC-DSS file, then you should specify the DSS file that contains the data.
Without specifying the file, you will have to manually connect to the time-series data. Press the Import button
when you have finished specifying the HEC-1 File name to import, and the names of the three components.
You cannot import a HEC-1 File unless the file name and all three component names are specified. When you
press the Import button, the import process will read the HEC-1 File and create the appropriate parts of the
three components.
6.4.2 Unsupported Features

Most of the features in the HEC-1 program are also available in this program. Some features related to
economic estimates were not incorporated into this program because they are inconsistent with modern
engineering analysis methods for risk-based design. Other features have not been added to this program
because they use old numerical algorithms that have been replaced by superior methods in this program and
no direct translation is available. Other features may be added to this program in the future. The so-called
cards from HEC-1 that are not supported during import are shown in the table below. An error message will
be displayed if any of those cards are encountered.
Record Identifier Alternative
IO, VS, VV The program automatically writes all computed time-series

data to the simulation DSS file. Complete summary tables
and time-series tables are available at all hydrologic
elements. There is no need to control the output level.

JP, KP The program does not currently compute multiple simulation

runs simultaneously.
JR The simulation run includes a precipitation or flow ratio

capability but only one ratio is provided. You will need to
create a separate simulation run for each ratio. See the
section Precipitation and Flow Ratios7.
JD Depth-area analyses provide an equivalent capability with

superior accuracy, but there is no direct conversion. See the
chapter Depth-Area Reduction8.
OU, OR Optimization trials provide an equivalent capability for

estimating loss rate method, transform method, baseflow
method, and routing method parameters but there is no
direct conversion. See the chapter Model Optimization9.
OS, OF, OO, DO, DC, DD, SO, SD, WO, WC, There is no capability to automatically estimate optimal
WD sizes for flood control system components based on
economic factors. Risk-based design procedures should be
used to size system components.
HB There is currently no capability to balance computed

hydrographs.
HL The Meteorologic Model includes a setting to compute local

flow at junctions that is similar. See the section Local
Flow10.
HS The specified release reservoir routing method provides

similar capability, but there is currently no direct conversion.
See the section Specified Release Routing11.
KF All computed results are stored in the simulation DSS file

using double precision. There is no need to specify output
format.
LM, LH The exponential-snowmelt and Holtan loss rate methods are

not currently available.
7 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/Simulation+Runs#SimulationRuns-PrecipFlowRatios
8 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/Depth-Area+Reduction
9 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/Model+Optimization
10 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/Basin+Model+Properties#BasinModelProperties-LocalFlow
11 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/Specified+Release+Routing

MA, MC, MT, MS, MD, MW There is a temperature index snowmelt capability in the
program that is similar, but there is no direct conversion. See
the section Temperature Index12.
PM The HMR52 precipitation method provides an equivalent

capability, but there is currently no direct conversion. See the
section HMR 52 Storm13.
QP Pattern hydrographs for local inflow are not needed because

of how the routing optimization is implemented.
RC Normal depth routing to determine the modified Puls

storage-outflow curve is not supported. Channel data are
converted to the Muskingum-Cunge method.
RL Channel losses may be specified using a constant rate or

percolation method, but there is currently no direct
conversion. See the section Selecting a Gain/Loss Method14.
UA The Clark transform method does include an optional time-

area curve, but there is currently no direct conversion. See
the section Clark Unit Hydrograph Transform15.
WP, WR The head-discharge pump included in the reservoir provides

a similar capability, but there is no direct conversion. See the
section Head-Discharge Pump16.
15 Unsupported HEC-1 records that cannot be processed during import along with possible alternatives
6.5 Importing HEC-RAS HDF Files

In order to utilize the 2D Diffusion Wave Transform Method, a Computational Mesh is required. This
computational mesh must be stored within an HDF 5 file. Currently, users must create a 2D mesh and any
associated normal depth, flow, stage, and/or rating curve boundary conditions within HEC-RAS (version 5.0.7
or newer) and then import to HEC-HMS. In the future, users will be able to create and modify both 2D meshes
and boundary conditions entirely within HEC-HMS. Also, users may only use one 2D mesh per Basin Model.
In the future, user's will be able to use multiple 2D meshes within the same Basin Model. Precipitation
boundary conditions will not be imported; they must be created and linked within HEC-HMS. If an HDF file is
imported from a version of HEC-RAS that is older than 5.0.7, some features may not be imported correctly.
12 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/.Snowmelt+v4.4#id-.Snowmeltv4.4-TempIndexSnow
13 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/.Precipitation+v4.4#id-.Precipitationv4.4-Hmr52
14 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/Selecting+a+Loss_Gain+Method
15 https://www.hec.usace.army.mil/confluence/display/
HMSDOCS/.Selecting+a+Transform+Method+v4.4#id-.SelectingaTransformMethodv4.4-ClarkUH
16 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/Outflow+Structures+Routing#OutflowStructuresRouting-
HeadDischargePump

Unrecognized input data is automatically ignored during the import process. Imported components should
always be checked for accuracy.
6.5.1 Selecting and Processing a File

Begin the process of importing features from an HEC-RAS HDF File by clicking the File menu and selecting
the Import | HEC-RAS HDF command. An Import from an HDF File wizard opens where you can specify the
HDF file to be imported as shown in the following figure. If you change your mind about importing an HEC-
RAS HDF file, you can press the Cancel button or the X button in the upper right of the Import from an HDF
File wizard.
Unsteady Plan HDF files have extensions of ".p##.hdf" where "p##" corresponds to the specific plan of
interest. If you do not know the exact path of the file which you'd like to import, you can click the button to
the right of the file name field to open a File Browser. Use the browser to navigate the file system and find
the correct HEC-RAS HDF file. The browser will automatically filter out all files that do not have an extension
of ".hdf". However, this filter can be removed by changing the Files of Type drop down menu to All Files.
Once you have located and selected the desired HEC-RAS HDF file, press the Select button. If you change
your mind about selecting a file, you can press the Cancel button or the X button in the upper right of the
browser to return to the Import from an HDF File wizard without selecting a file. Once an HDF file has been
selected, click the Next button to advance.
38 Choosing an HDF File
The next step requires the selection of a Basin Model that is contained within the currently opened Project,
as shown in the following image. Only Basin Models that have a valid, defined coordinate system will be
shown. Once a valid Basin Model has been selected, click the Next button to advance.

39 Selecting a Basin Model
The next step requires the selection of a Subbasin within the previously selected Basin Model, as shown in
the following figure. Only subbasins that are georeferenced will be shown. Once a valid subbasin has been
selected, click the Next button to advance.
40 Selecting a Subbasin

The final step requires the selection of a 2D Area within the previously selected HDF file, as shown in the
following figure. All 2D areas that are encountered within the selected HDF file will be shown along with the
associated number of cells and boundary condition lines. Once a 2D area has been selected, click the Finish
button to finalize the import process.
41 Selecting a 2D Area
Upon clicking the Finish button, the mesh and any associated normal depth, flow, stage, and/or rating curve
boundary conditions will be imported to the selected subbasin. The mesh and 2D connections can be viewed
within the map panel by toggling the Discretization and 2D Connection layers on, as shown in the figure
below. This menu can be accessed by clicking View | Map Layers or right clicking within the map panel and
selecting Map Layers.

42 Imported Mesh and Boundary Condition Lines
An example application demonstrating the process of creating a new HEC-RAS Project, loading the required
data, generating a 2D mesh, creating a plan HDF file, and importing to an HEC-HMS Project is shown here:
Creating a Simple 2D Flow Model within HEC-HMS17.
6.6 References: Projects and Control Specifications

Hydrologic Engineering Center. June 1998. HEC-1 Flood Hydrograph Package: User's Manual. U.S. Army
Hydrologic Engineering Center. October 1994. HEC-DSS User's Guide and Utility Manuals: User's Manual. U.S.
Army Corps of Engineers, Davis, CA.
Hydrologic Engineering Center. March 1984. HMR52 Probable Maximum Precipitation (Eastern United
States): User's Manual. U.S. Army Corps of Engineers, Davis, CA.
17 https://www.hec.usace.army.mil/confluence/display/HMSGUIDES/Creating+a+Simple+2D+Flow+Model+within+HEC-HMS

7 Shared Component Data

Hydrologic simulation requires a wealth of data that is used as initial conditions, boundary conditions, or
parameters. A large portion of the data is measurements of atmospheric conditions, such as precipitation,
temperature, and solar radiation. These boundary condition measurements may come from gage sites or
may be gridded over a wide area. Still significant are reservoir storage curves, stream channel rating curves,
and cross sections. Additional data is required when gridded modeling techniques will be used.
7.1 Time-Series Data

Hydrologic models often require time-series of precipitation data for estimating basin-average rainfall. A
time-series of flow data, often called observed flow or observed discharge, is helpful for calibrating a model
and is required for optimization. Other kinds of time-series data are used as well. Time-series data is stored
in a Project as a Gage. The program separates different types of data with different Gage Types. Gage data
only has to be entered one time. The gages are part of the Project and can be shared by multiple Basin or
Meteorologic Models.
7.1.1 Creating a New Gage

A new gage is created using the Time-Series Data Manager. To access the manager, click on
the Components menu and select the Time-Series Data Manager menu command. The manager can remain
open while you perform tasks elsewhere in the program. You can close the manager using the X button in the
upper right corner. At the top of the manager is a Data Type menu. This option lets you select one of the
Time-Series Data Types supported by the program. Refer to the Internal DSS data type label for different
types of time-series data (see table 17) table for a complete list of Time-Series Data Types. When a data type is
selected, the manager will show all time-series data of the same type. The buttons to the right of the time-
series data list can be used to manage existing data or create new data.
Shared Component Data – 132

43 Creating a new Gage
To create a new time-series gage, press the New button. After you press the button, the Create A New Time-
Series Data window will open where you can name and describe the new gage. A default name is provided
for the new gage; you can use the default or replace it with your own choice. A description can also be
entered. If the description is long, you can press the button to the right of the description field to open an
editor. The editor makes it easy to enter and edit long descriptions. When you are satisfied with the name
and description, press the Create button to finish the process of creating the new time-series gage. You
cannot press the Create button if no name is specified. If you change your mind and do not want to create a
new time-series gage, press the Cancel button or the X button in the upper right to return to the Time-Series
Data Manager.
44 Creating a new Time-Series Gage
7.1.2 Copying a Gage

There are two ways to copy a time-series gage. Both methods for copying a gage create an exact duplicate
with a different name. Once the copy has been made it is independent of the original and they do not interact.

The first way to create a copy is to use the Time-Series Data Manager, which is accessed from
the Components menu. First, select the Data Type of the Time-Series Gage you want to copy from the Data
Type menu. Then, select the Time-Series Gage you want to copy by clicking on it in the list of current time-
series gages. The selected gage is highlighted after you select it. After you select a gage you can press
the Copy button on the right side of the window. The Copy Discharge gage window will open where you can
name and describe the copy that will be created. A default name is provided for the copy; you can use the
default or replace it with your own choice.
45 Copying time-series gage
A description can also be entered; if it is long you can use the button to the right of the description field to
open an editor. When you are satisfied with the name and description, press the Copy button to finish the
process of copying the selected time-series gage. You cannot press the Copy button if no name is specified.
If you change your mind and do not want to copy the selected gage, press the Cancel button or the X button
in the upper right to return to the Time-Series Data Manager.
The second way to create a copy is from the Watershed Explorer, on the Components tab. Move the mouse
over the time-series component you wish to copy, then press the right mouse button. A context menu is
displayed that contains several choices including Copy. Click the Create Copy menu option. A new window
will open where you can name and describe the copy that will be created. A default name is provided for the
copy; you can use the default or replace it with your own choice. A description can also be entered; if it is
long you can use the button to the right of the description field to open an editor. When you are satisfied with
the name and description, press the Copy button to finish the process of copying the selected time-series
gage. You cannot press the Copy button if no name is specified. If you change your mind and do not want to
copy the gage, press the Cancel button or the X button in the upper right of the window to return to
the Watershed Explorer.

46 Creating a copy of a gage by selecting it in the Watershed Explorer and using the right-mouse menu
7.1.3 Renaming a Gage

There are two ways to rename a time-series gage. Both methods for renaming a gage changes its name and
then all references to the old name are automatically updated to the new name.
The first way to perform a rename is to use the Time-Series Data Manager, which you can access from
the Components menu. First, select the Data Type of the time-series gage you want to rename from the Data
Type menu. Then, select the Time-Series Gage you want to rename by clicking on it in the list of current
time-series gages. The selected gage is highlighted after you select it. After you select a gage you can press
the Rename button on the right side of the window. A window will open where you can provide the new
name. You can also change the description at the same time. If the new description will be long, you can use
the button to the right of the description field to open an editor. When you are satisfied with the name and
description, press the Rename button to finish the process of renaming the selected time-series gage. You
cannot press the Rename button if no name is specified. If you change your mind and do not want to rename
the selected gage, press the Cancel button or the X button in the upper right of the window to return to the
Time-Series Data Manager.

47 Renaming a time-series gage
The second way to rename is from the Watershed Explorer, on the Components tab. Move the mouse over
the time-series component you wish to rename, then press the right mouse button. A context menu is
displayed; select the Rename command and the highlighted name will change to editing mode. You can then
move the cursor with the arrow keys on the keyboard or by clicking with the mouse. You can also use the
mouse to select some or all of the name. Change the name by typing with the keyboard. When you have
finished changing the name, press the Enter key to finalize your choice. You can also finalize your choice by
clicking elsewhere in the Watershed Explorer. If you change your mind while in editing mode and do not want
to rename the selected gage, press the Escape key.
48 Renaming a gage by selecting it in the Watershed Explorer and then clicking again with the left mouse button to start editing in place
7.1.4 Deleting a gage

There are two ways to delete a time-series gage. Both methods for deleting a gage will remove it from the
Project and then automatically update all references to that gage. Once a gage has been deleted it cannot be
retrieved or undeleted. Any references to the deleted gage will switch to using no gage, which is usually not a

valid choice during a simulation. At a later time you will have to go to those components and manually select
a different gage.
The first way to perform a deletion is to use the Time-Series Data Manager, which you can access from
the Components menu. First, select the Data Type of the time-series gage you want to delete from the Data
Type menu. Then, select the Time-Series Gage you want to delete by clicking on it in the list of current time-
series gages. The selected gage is highlighted after you select it. After you select a gage you can press
the Delete button on the right side of the window. A window will open where you must confirm that you want
to delete the selected gage. Press the OK button to delete the gage. If you change your mind and do not want
to delete the selected gage, press the Cancel button or the X button in the upper right to return to the Time-
Series Data Manager.
49 Preparing to delete a gage from the Time-Series Data Manager
The second way to delete a gage is from the Watershed Explorer, on the Components tab. Select the Time-
Series Gage you want to delete by clicking on it in the Watershed Explorer; it will become highlighted. Keep
the mouse over the selected gage and click the right mouse button. A context menu is displayed that
contains several choices including Delete. Click the Delete menu option. A window will open where you must
confirm that you want to delete the selected gage. Press the OK button to delete the gage. If you change your
mind and do not want to delete the selected gage, press the Cancel button or the X button in the upper right
to return to the Watershed Explorer.

50 Preparing to delete a gage from the Watershed Explorer
7.1.5 Time Windows

Time Windows are used to separate the time-series data into manageable sections. You may choose to have
a separate time window for each event. Alternately, you may have several time windows for a continuous
record to break it into months or years. You may choose to have a combination of time window types and
they may overlap. All time windows use the same data units, time interval, and other properties discussed in
the following sections.
The program is capable of processing dates from 1583 AD through 4000 AD. All dates are processed
according to the rules specified in the Gregorian calendar for leap year. The format for specifying a date is to
use two digits for the day, followed by the three-letter month abbreviation, and finally the four digit year. Two
digit years are never used for entering or displaying dates. For example, the date October 2, 1955 should be
entered as follows:
02Oct1955
It is very important to use the correct format or the date you enter may be incorrectly interpreted. If the
program is not able to interpret a date, the entry field will become blank. The same format is used for both
start and end dates, and for dates throughout the program.
The program processes times assuming an arbitrary local time zone that does not observe summer time
(daylight savings in the United States). It uses 24-hour clock time instead of AM or PM notation. Time
windows can only be entered with minute resolution. Times may range from 00:00 at the beginning of a day
to 23:59 at the end. If a time of 24:00 is entered, it is automatically converted to 00:00 on the following day.
For example, the time of 6:20:00 PM should be entered as follows:
18:20

It is very important to use the correct format, including the colon, or the time may be incorrectly interpreted.
The same format is used for start and end times, and for times throughout the program.
There are two ways to create a new time window. The first way is from the Time-Series Data Manager,
accessed by clicking the Components menu and then selecting the Time-Series Data Manager command.
Select the desired data type, then click on a time-series data component in the list; the component will
become highlighted. Press the Add Window button to create a new time window. The Add Time-Series Data
Time Window window will open where you can enter the start date and other information as shown in the
following figure. You can either enter the information manually, or select a Control Specifications. If you
select a Control Specifications, the start and end time in that Control Specifications will be used for the new
time window. Press the Add button to create the new time window. The window will remain open for adding
additional time windows. When you are finished, press the Close button or the X button in the upper corner of
the Add Time-Series Data Time Window.
51 Creating a new time window for a gage, beginning from the Time-Series Data Manager
The second way to create a new time window is directly from the Watershed Explorer. Select a Time-Series
Component by clicking on it or one of the existing time windows. Keep the mouse over the gage or time
window icon and click the right mouse button. A context menu appears as shown in the figure below; click
the Create Time Window command to create a new time window. The same window shown in the previous
figure will open for creating a new time window.

52 Creating a new time window from the Watershed Explorer
There are two ways to delete a time window. The first way is from the Time-Series Data Manager, accessed
by clicking the Components menu and then selecting the Time-Series Data Manager command. Select the
desired Data Type, then click on a Time-Series Gage in the list; it will become highlighted. Press the Delete
Window button to delete a time window. The Delete Time-Series Data Time Window window will open where
you can select the window to delete. Click on the desired window and it will become highlighted. Press
the Delete button to delete the highlighted time window. If you change your mind and do not want to delete a
time window, press the X button in the upper corner of the Delete Time-Series Data Time Window window.
The second way to delete a time window is directly from the Watershed Explorer. Select a Time Window for
a time-series gage; it will become highlighted. Keep the mouse over the Time Window icon and click the right
mouse button. A context menu appears as shown in the following figure; click the Delete Time
Window command to delete the selected time window.

53 Deleting a selected time window from a gage after choosing it in the Watershed Explorer
The user can change the Start Date, Start Time, End Date, and End Time of an existing time window. Use
the Watershed Explorer to select the Time Window you wish to change. Click on the time window under the
correct time-series component. The component will become the selected component and its data will be
shown in the Component Editor as seen in the figure below; the Time Window tab is automatically selected.
Change the start date or other properties to the desired values. Click on a different tab in the Component
Editor or elsewhere in the program interface to make the changes take affect.
54 Using the time window component editor for a gage to view and edit the start and end time for a window

7.1.6 Data Source

The Data Source determines how the data for a time-series component will be entered. There are three
alternative methods for entering the data:
1. The user may enter the time-series values by manually typing each one. A variation of this method is
using the clipboard to copy and paste instead of manually typing. This first method is known as
Manual Entry.
2. The user may load data into a Data Storage System (HEC-DSS) file. This method can be facilitated
using the program HEC-DSSVue to create individual HEC-DSS files. The gage is linked to the time-
series values stored in the file. This second method is known as Single Record HEC-DSS.
3. The user may store alternative versions of the time-series values in a HEC-DSS file. This method is
used exclusively for forecasting operations with the Corps Water Management System (CWMS) and
planning studies with the Watershed Analysis Tool (HEC-WAT). This third method is known as
Multiple Record HEC-DSS.
The selected data source will determine how the time-series values are entered. The values may be manually
typed or linked to a HEC-DSS file. Compare the following figures to see the differences in specifying the data
sources.
55 Component editor for a temperature Gage with manually-entered data

56 Component editor for a precipitation Gage retrieving data from a Data Storage System (HEC-DSS) file
7.1.7 Data Units

The Data Units can only be selected for a manual entry time-series gage; they are retrieved automatically for
both HEC-DSS options. Most types of time-series data have only two options for units; one for the system
international unit system and one for the U.S. customary unit system. For example, discharge gages can use
cubic meters per second (M3/S) or cubic feet per second (CFS). The Precipitation Time-Series type has
additional options for specifying incremental or cumulative data. The units available in the "Units" field will
depend on the time-series type of the selected component. All time windows defined for a time-series
component must use the same data units.
Generally you should choose the data units before entering any data for the gage. However, if you change the
units after entering data, the data will be adjusted to the new units. There is no units conversion during the
adjustment. The values are all kept the same but the assigned units are changed. This is helpful when the
data is entered without first checking to make sure the data units are in the desired unit system.
Select the data units for a time-series gage using the Component Editor. Access the editor by selecting a
time-series gage in the Watershed Explorer. The Time-Series Gage tab in the Component Editor will display
the data units if the manual entry option is selected.
7.1.8 Time Interval

The Time Interval can only be selected for a manual entry time-series gage; it is retrieved automatically for
both HEC-DSS options. An interval must be selected from the available choices that range from 1 minute to 1
day. All time windows defined for a time-series component must use the same time interval.
Generally, you should choose the time interval before entering any data for the component. However, if you
change the time interval after entering data, the data will be adjusted to the new time interval. When the time
interval is made shorter, the data for each time window will be adjusted so that it still begins at the start of
the time window. The data will have the new, shorter time interval and there will be missing data from the
last specified value to the end of the time window. When the time interval is made longer, the data for each

time window will be adjusted so that it still begins at the start of the time window. The data will have the new,
longer time interval and the end of the time window will be advanced so that no data is lost.
Select the time interval for a time-series gage using the Component Editor. Access the editor by selecting a
time-series gage in the Watershed Explorer. The Time-Series Gage tab in the Component Editor will display
the time interval if the manual entry option is selected.
7.1.9 Elevation
Certain atmospheric variables show a strong trend with Elevation. Air pressure and air temperature both
decrease as the elevation increases. Relative humidity increases as the elevation increases. The physics of
water and air can be used to develop relationships for how these variables change with elevation. Therefore,
calculating atmospheric variables at a location in the watershed requires both the elevation where the
measurement was performed and the elevation where the variable should be calculated. The elevation must
be entered for data types that require it. In general, the ground surface elevation (above sea level) at the
measurement site is used. The value may be entered as either meters or feet, depending on the unit system
of the gage. The requirements for entering elevation are shown in Table 1.
7.1.10 Reference Height

Some atmospheric variables change dramatically near the ground surface. Windspeed is very close to zero
at the ground surface and increases as distance above the ground increases. Air temperature and relative
humidity change significantly with distance above a snow covered surface. Therefore, calculating these
atmospheric variables at the ground surface requires information about the height above the ground where
the measurements were performed. While it is common for meteorologic instruments to be mounted on a
tower 10 meters above the ground surface, other distances may be used at some installations. The
instrument reference height must be entered for data types that require it. The value may be entered as
either meters or feet, depending on the unit system of the gage. The requirements for entering reference
height are shown in the Requirements for entering additional properties for gages (see table 16) table.
7.1.11 Latitude and Longitude

The most important atmospheric variable in hydrology is precipitation. Developing an accurate
representation of a storm is critical to accurately simulating discharge throughout the watershed.
Precipitation gages measure the rainfall at discrete locations within and adjacent to the watershed.
Interpolation methods estimate precipitation continuously across the watershed based on the measured
rainfall. The methods require a precise description of the location of each precipitation gage. The location is
specified for each gage as the latitude and longitude. The latitude and longitude may be entered either as
decimal degrees or as a triplet of degrees, minutes, and seconds. The method of entering the latitude and
longitude is configured in the Program Settings. The requirements for entering latitude and longitude are
shown in the following table.
The degrees, minutes, and seconds are specified separately for the latitude and longitude. In general you
should only specify the whole degrees and whole minutes. You can choose to specify whole or fractional
seconds. If you enter more than 60 minutes or more than 60 seconds, the program will automatically adjust
the degrees, minutes, or second as necessary to have 60 or fewer minutes and 60 or fewer seconds.
Time-Series Elevation Reference Height Latitude Longitude

Precipitation X
Discharge
Stage
Temperature X X
Radiation
Windspeed X
Air pressure X
Humidity X X
Altitude
Crop Coefficient
Snow Water Equivalent
Sediment Load
Concentration
Percent
Evapotranspiration
Sunshine
16 Requirements for entering additional properties for Gages
For example, if you entered 120 degrees and 64 minutes, the program would convert that data to 121
degrees and 4 minutes. A similar adjustment is made when the number of seconds is greater than 60.
Alternately, you can specify the latitude and longitude in decimal degrees. In this case only the input for
degrees is shown. Instead of entering a value such as 121 degrees, 4 minutes, and 17 seconds, a value in
decimal degrees can be entered as 121.07139 degrees. Change the format for displaying and entering

latitude and longitude in the Program Settings which are described earlier in Program Settings18. The setting
is found on the General tab.
General cartography conventions use negative longitude degrees in the Western hemisphere and positive
longitude degrees in the Eastern hemisphere. Negative latitude degrees are used in the Southern hemisphere
and positive latitude degrees are used in the Northern hemisphere. These conventions should be used for
entry of latitude and longitude throughout the program.
7.1.12 Manual Entry

Manual Entry is the simplest way to get data values for a time-series gage. The values are manually typed for
each date and time. All of the data should be reviewed after entry to verify accurate typing. If no value was
recorded for a date and time, then the value should be left blank. The program does not automatically fill in
missing data. Data recovery should be considered for extended periods of missing data.
Manual entry can also be used in combination with the clipboard to transfer data values from another
computer program. Time-series values may be stored in a spreadsheet or other program. The values can be
selected in the other program and copied to the clipboard. The values copied to the clipboard can be pasted
in HEC-HMS. Using the clipboard can save a significant amount of manual typing and reduce errors when the
time-series values are available in another program.
Manual entry time-series values are automatically stored in a HEC-DSS file in the Project directory. The
program uses the name of the gage to create a HEC-DSS file for storing the manual entry data. Manual entry
values can be entered and then edited as many times as necessary to correct typing errors. Each time the
data values are modified manually by the user, the data is automatically updated in the HEC-DSS file. One
benefit of using a HEC-DSS file as an automatic storage solution is that the file can be reduced for other
modeling Projects.
7.1.13 Single Record HEC-DSS

Retrieving time-series data from a HEC-DSS file requires that the data be loaded in a file. The file can be
stored on the local computer or on a network server. It is not a good idea to store the file on removable
media since the file must be available whenever the time-series component is selected in the Watershed
Explorer, and during simulations. Data for each gage can be stored in a separate file or one file can contain
data for several gages. However, all data for a single time-series gage must be stored in the same HEC-DSS
file and use appropriate pathname convention. It is best practice to store the HEC-DSS files holding gage
data in the Project directory, or a subdirectory of the Project directory. The HEC-DSSVue utility (HEC 2003)
can be used to load time-series data into a DSS file.
When the Single Record HEC-DSS option is selected, you must specify the filename to use for the time-
series component. You may type the complete filename if you know it. To use a file browser to locate the file,
press the Open File Chooser button to the right of the DSS Filename field. The browser allows you to find the
desired file but it is limited to locating files with the DSS extension which is required for all Data Storage
System files. Once you locate the desired file, click on it in the browser to select it and press
the Select button. If you change your mind, press the Cancel button or the X button in the upper corner of
the Select HEC-DSS File window to return to the Component Editor.
You must also specify the pathname to retrieve from the selected HEC-DSS file (Figure 15). You may type the
complete pathname if you know it. Each pathname contains six parts called the A-part, B-part, C-part, D-part,
E-part, and F-part. The pathname parts are separated with a slash and may contain spaces. The complete

pathname, including slashes and spaces, can total up to 256 uppercase characters. The following is an
example of an incremental precipitation pathname:
//COOPER SMITH DAM/PRECIP-INC/01OCT2001/15MIN/OBS/
Because of internal performance considerations, a HEC-DSS file will usually contain multiple records when
storing long time-series. The different records will each have all the same pathname parts except for the D-
part which indicates the starting time of each record. Any of the record pathnames can be selected and the
program will automatically retrieve the correct data depending on the selected time window.
If you do not know the full pathname of the record you wish you use, you can use the pathname browser to
specify it. You must select a HEC-DSS file first before the browser is available. Press the Select DSS
Pathname button to the right of the "DSS Pathname" field to open the browser. The browser initially shows all
of the records in the selected HEC-DSS file, organized by pathname in the selection table. You can scroll
through the list and select a record pathname by clicking on it. Press the Select button at the bottom of the
browser to choose that record and return to the Component Editor. If you change your mind and do not want
to select a record pathname, press the Cancel button or the X button in the upper right of the Select
Pathname From HEC-DSS File window. You can reduce the number of record pathnames shown in the
selection table using the Search by Parts filters. A separate filter selection is shown for each of the six
pathname parts. By selecting a choice for a filter, only pathnames that match that choice will be shown in the
selection table. If you make choices in several filters, only pathnames that satisfy all of the choices will be
shown in the selection table.
The program observes a very strict set of rules for data type and units within the record pathnames. Rules
governing the C-part of the pathname are also enforced. Data cannot be used unless is follows the rules
correctly; error messages will be generated if you attempt to use an invalid C-part, data type, or units. The
acceptable data types for the different types of time-series data are shown in the following table.
Time-Series Type Description
Precipitation PER-CUM The incremental precipitation during each time

interval. The C-part should be "PRECIP-INC".
INST-CUM The cumulative precipitation at the end of each

interval. The C-part should be "PRECIP-CUM".
Discharge PER-AVER The average flow rate during each time interval,
usually for time steps of 24 hours or longer. The C-
part should be "FLOW".
INST-VAL The instantaneous flow rate at the end of each

time interval. The C-part should be "FLOW".
Stage PER-AVER The average elevation during each interval, usually

time steps of 24 hours or longer. The C-part should
be "STAGE".

INST-VAL The instantaneous elevation at the end of each

time interval. The C-part should be "STAGE".
Temperature PER-AVER The average temperature, in degrees, during each

time interval. The C-part should be
"TEMPERATURE".
INST-VAL The instantaneous temperature, in degrees, at the

end of each time interval. The C-part should be
"TEMPERATURE".
Radiation PER-AVER The average radiation, in power per area, occurring

during each time interval. The C-part should be
"RADIATION".
Windspeed INST-VAL The instantaneous windspeed at the end of each

time interval. The C-part should be "WINDSPEED".
Air pressure INST-VAL The instantaneous air pressure at the end of each
time interval. The C-part should be "PRESSURE".
Humidity INST-VAL The instantaneous humidity at the end of each time

interval. The C-part should be "HUMIDITY".
Altitude INST-VAL The instantaneous altitude at the end of each time

interval. The C-part should be "ALTITUDE".
Crop Coefficient INST-VAL The instantaneous crop coefficient, as a

dimensionless decimal number, occurring at the
end of each time interval. The C-part should be
"CROP COEFFICIENT".
Snow Water Equivalent INST-VAL The instantaneous snow water equivalent, as a

depth at the end of each time interval. The C-part
should be "SWE".
Sediment Load PER-CUM The total sediment load during each time interval.
The C-part should be "LOAD".
Concentration INST-VAL The instantaneous concentration at the end of

each time interval. The C-part should be "CONC".

Percent INST-VAL The instantaneous percent at the end of each time

interval. The C-part should be "PERCENT".
Evapotranspiration PER-CUM The incremental evapo-transpiration during each

time interval. The C-part should be "ET".
Sunshine PER-AVER The average sunshine during each time interval.

The C-part should be "SUNSHINE HOURS".
17 Internal DSS data type label for different types of time-series data
The correct unit labels are shown in the following table.
Time-Series Label Description
Precipitation MM Millimeters
IN Inches
Discharge M3/S Cubic meters per second
CFS Cubic feet per second
Stage M Meters
FT Feet
Temperature DEG C Degrees centigrade
DEG F Degrees Fahrenheit
Radiation WATT/M2 Watts per square meter
LANG/MIN Langleys per minute
Windspeed KPH Kilometers per hour
M/S Meters per second

MPH Miles per hour
FT/S Feet per second
Air Pressure KPA Kilo pascals
IN HG Inches of mercury
Humidity % Relative humidity
Altitude KM Kilometers above sea level
MILE Miles above sea level
Crop Coefficient UNSPECIF Dimensionless coefficient
Snow Water Equivalent MM Millimeters
IN Inches
Sediment Load TONS Tons
TONNES Metric tonnes
Concentration MG/L Milligrams per liter
Percent % Percent
Evapotranspiration MM Millimeters
IN Inches
Sunshine HR Hours
18 Internal DSS units label for different types of time-series data

7.1.14 Multiple Record HEC-DSS

The Multiple Record HEC-DSS data source is designed for forecasting operations with the Corps Water
Management System (CWMS). The System provides forecasts of future conditions that are used to support
operation decisions. It combines meteorologic and hydrologic data management with engineering simulation
models. Meteorologic data includes radar-based precipitation measurements and gage measurements of
atmospheric variables. Hydrologic data includes stage and discharge observations among others.
Engineering models include hydrology, reservoir operations, hydraulics, and consequences. A typical forecast
includes the following steps:
1. Combine recently observed precipitation with forecast precipitation.

2. Link the combined precipitation to HEC-HMS for computing channel flow.
3. Transfer the flow to a reservoir model to determine the best operations for the dam.
4. Connect the reservoir discharge to a hydraulic model to compute downstream flow.
5. Map the downstream flow and estimate economic consequences, and in the case of severe flooding,
the potential for life loss.
Forecast operations often consider more than one potential meteorologic forecast. The multiple
meteorologic forecasts may result from alternative atmospheric models, atmospheric model ensemble
members, or synthetic scenarios such as 150% of the forecast precipitation volume. The multiple record
HEC-DSS data source is designed to facilitate the multiple hydrologic simulations necessary to evaluate each
meteorologic alternative.
The multiple record data source includes a default selection for HEC-DSS file and pathname. The file and
pathname are selected using the same steps already detailed for the Single Record HEC-DSS data source.
The default selection will be used during simulations performed in HEC-HMS when it is not part of CWMS.
However, when HEC-HMS is used with CWMS, the multiple record data source will be automatically switched
to the correct meteorologic alternative based on the overall System configuration.
7.1.15 Table
The data for the current time window is shown in tabular form on the Table tab of the Component Editor. If
you select a time-series gage in the Watershed Explorer, only the tab for the Time-Series gage is shown in
the Component Editor. If you select a time window under a time-series gage in the Watershed Explorer, the
Table tab will be added to the Component Editor. Data in the table can be edited if the gage uses manual
entry. Data is not editable if the gage retrieves data from a DSS file. Furthermore, if the gage uses DSS data
and no time-series data is available for the specified time window, then the table will not contain any data.

57 Manually entering data for a temperature Gage
You can enter all of the data for each time window one value at a time in the table. However, there are tools
to help you enter the data quickly. The table includes support for the clipboard. This means you can copy
data stored in a spreadsheet or other file and then paste it into the table. You can also use the fill tool to
enter or adjust data values in the table. Select the cells in the table you wish to fill and click the right mouse
button. A context menu is displayed; select the Fill command. The Fill Table Options window opens for you
to control the process of filling and adjusting cell values. Options include interpolating the values between
the first and last cell in the selection, several choices for interpolating and replacing missing values, copying
the first selected cell value to all other selected cells, adding a constant value to all selected cells, and
multiplying the selected cell values by a constant. Press the OK button to apply your choice, or
the Cancel button to return to the table without making any changes.
7.1.16 Graph
The data for the current time window is shown in graphical form on the Graph tab of the Component
Editor. If you select a time-series gage in the Watershed Explorer, only the tab for the Time-Series gage is
shown in the Component Editor. If you select a time window under a time-series gage in the Watershed
Explorer, the Graph tab will be added to the Component Editor. Data in the graph cannot be edited regardless
of whether the gage uses manual entry or retrieves data from a DSS file. If no time-series data is available for
the specified time window, then the graph will not contain any data.

58 Viewing data for a discharge Gage connected to a HEC-DSS file
7.2 Paired Data

Hydrologic models often require the use of Paired Data to describe inputs that are functional in form.
Functional data defines a dependent variable in terms of an independent variable. For most cases, the
function must be monotonically increasing which means it only increases and never decreases. Examples of
paired data include unit hydrographs and stage-discharge curves. The program separates different types of
paired data with different data types. Paired data only has to be entered one time. The data are part of the
project and can be shared by multiple Basin or Meteorologic Models.
7.2.1 Creating a New Paired Data Curve

A new curve is created using the Paired Data Manager. To access the manager, click on
the Components menu and select the Paired Data Manager menu command. The manager can remain open
while you perform tasks elsewhere in the program. You can close the manager using the X button in the
upper right corner. At the top of the manager is a Data Type menu. This menu lets you select one of the
paired data types supported by the program. Refer to the Preferred data order and internal DSS data type
label for different types of Paired Data (see table 19) table for a complete list of Paired Data Types. When a
data type is selected, the manager will show all paired data of the same type. The buttons to the right of the
paired data list can be used to manage existing data or create new data. To create a paired data curve, press
the New button.

59 Paired Data Manager
After you press the button, the Create A Paired Data window will open where you can name and describe the
new curve. A default name is provided for the new curve; you can use the default or replace it with your own
choice. A description can also be entered. If the description is long, you can press the button to the right of
the description field to open an editor. The editor makes it easier to enter and edit long descriptions. When
you are satisfied with the name and description, press the Create button to finish the process of creating the
new paired data curve. You cannot press the Create button if no name is specified. If you change your mind
and do not want to create a paired data curve, press the Cancel button or the X button in the upper right to
return to the Paired Data Manager.
60 Creating a Paired Data
7.2.2 Copying a Curve

There are two ways to copy a paired data curve. Both methods for copying a curve create an exact duplicate
The first way to create a copy is to use the Paired Data Manager, which is accessed from
the Components menu. First, select the data type of paired data curve you want to copy from the Data

Type menu. Then, select the Paired Data Curve you want to copy by clicking on it in the list of current paired
data curves. The selected curve is highlighted after you select it. After you select a curve you can press
the Copy button on the right side of the window. A new window will open where you can name and describe
the copy that will be created. A default name is provided for the copy; you can use the default or replace it
with your own choice. A description can also be entered; if it is long you can use the button to the right of the
description field to open an editor. When you are satisfied with the name and description, press
the Copy button to finish the process of copying the selected paired data curve. You cannot press
the Copy button if no name is specified. If you change your mind and do not want to copy the selected curve,
press the Cancel button or the X button in the upper right to return to the Paired Data Manager.
61 Creating a copy of a Gage after pressing the Copy button in the Paired Data Manager
over the paired data component you wish to copy, then press the right mouse button. A context menu is
displayed that contains several choices including Copy. Click the Create Copy menu option. A new window
will open where you can name and describe the copy that will be created. A default name is provided for the
the name and description, press the Copy button to finish the process of copying the selected paired data
curve. You cannot press the Copy button if no name is specified. If you change your mind and do not want to
copy the curve, press the Cancel button or the X button in the upper right of the window to return to

62 Creating a copy of a cross section by selecting it in the Watershed Explorer and using the right-mouse menu
7.2.3 Renaming a Curve

There are two ways to rename a paired data curve. Both methods for renaming a curve changes its name
and then all references to the old name are automatically updated to the new name.
The first way to perform a rename is to use the Paired Data Manager, which you can access from
the Components menu. First, select the data type of paired data curve you want to rename from the Data
Type menu. Then, select the Paired Data Curve you want to rename by clicking on it in the list of current
curves. The selected curve is highlighted after you select it. After you select a curve you can press
the Rename button on the right side of the window. A window will open where you can provide the new
name. You can also change the description at the same time. If the new description will be long, you can use
the button to the right of the field to open an editor. When you are satisfied with the name and description,
press the Rename button to finish the process of renaming the selected paired data curve. You cannot press
the Rename button if no name is specified. If you change your mind and do not want to rename the selected
curve, press the Cancel button or the X button in the upper right of the window to return to the Paired Data
Manager.
63 Renaming a cross section after pressing the Rename button in the Paired Data Manager

The second way to rename is from the Watershed Explorer, on the Components tab. Move the mouse over
the paired data you wish to copy, then press the right mouse button. A context menu is displayed; select
the Rename command and the highlighted name will change to editing mode. You can then move the cursor
with the arrow keys on the keyboard or by clicking with the mouse. You can also use the mouse to select
some or all of the name. Change the name by typing with the keyboard. When you have finished changing the
name, press the Enter key to finalize your choice. You can also finalize your choice by clicking elsewhere in
the Watershed Explorer. If you change your mind while in editing mode and do not want to rename the
selected curve, press the Escape key.
64 Renaming a cross section by selecting it in the Watershed Explorer and using the right-mouse menu
7.2.4 Deleting a Curve

There are two ways to delete a paired data. Both methods for deleting a curve will remove it from the project
and then automatically update all references to that curve. Once a curve has been deleted it cannot be
retrieved or undeleted. Any references to the deleted curve will switch to using no curve, which is usually not
a valid choice during a simulation. At a later time you will have to go to those components and manually
select a different curve.
The first way to perform a deletion is to use the Paired Data Manager, which you can access from
the Components menu. First, select the data type for the paired data curve you want to delete from the Data
Type menu. Then, select the Curve you want to delete by clicking on it in the list of current curves. The
selected curve is highlighted after you select it. After you select a curve you can press the Delete button on
the right side of the window. A window will open where you must confirm that you want to delete the
selected curve. Press the OK button to delete the curve. If you change your mind and do not want to delete
the selected curve, press the Cancel button or the X button in the upper right to return to the Paired Data
Manager.

65 Preparing to delete a cross section from the Paired Data Manager
The second way to delete a paired data is from the Watershed Explorer, on the Components tab. Select the
curve you want to delete by clicking on it in the Watershed Explorer; it will become highlighted. Keep the
mouse over the selected curve and click the right mouse button. A context menu is displayed that contains
several choices including delete. Click the Delete menu option. A window will open where you must confirm
that you want to delete the selected curve. Press the OK button to delete the curve. If you change your mind
and do not want to delete the selected curve, press the Cancel button or the X button in the upper right to
return to the Watershed Explorer.
66 Deleting a cross section by selecting it in the Watershed Explorer and using the right-mouse menu

7.2.5 Data Source

The Data Source determines how the data for a paired data will be stored. Data may be entered manually or
retrieved from the Data Storage System (HEC-DSS). Manual entry means that you must enter each of the
values in the curve or pattern. Data can be retrieved from a DSS file without having to enter the values, but
the data must be correctly loaded into the file. The type of properties you specify for the paired data will be
determined by the data source, as discussed in the following sections. Compare the following figures to see
the difference in entering data for manual or HEC-DSS data sources.
67 Component editor for a storage-discharge curve retrieving data from a Data Storage System (HEC-DSS) file
68 Component editor for a unit hydrograph paired data curve with manually-entered data

7.2.6 Data Units

The Data Units can only be selected for a manual entry paired data; they are retrieved automatically for the
DSS option. Paired data have only two options for units; one for the system international unit system and one
for the U.S. customary unit system. For example, a storage-discharge curve can use 1000 cubic meters and
cubic meters per second (1000M3 - M3/S) or acre feet and cubic feet per second (ACFT - CFS). The units
available in the Units field will depend on the paired data type of the selected component.
Generally, you should choose the data units before entering any data for the component. However, if you
change the units after entering data, the data will be adjusted to the new units. There is no units conversion
during the adjustment. The values are all kept the same but the assigned units are changed. This is helpful
when the data is entered without first checking to make sure the data units are in the desired unit system.
Select the data units for a paired data component using the Component Editor. Access the editor by
selecting a paired data in the Watershed Explorer. The Paired Data tab in the Component Editor will display
the data units if the manual entry option is selected.
7.2.7 Time Intervals

Unit hydrographs are the only type of paired data that can have a time interval as seen in this previous
figure (see page 159). The time interval can only be selected for a manual entry unit hydrograph; it is retrieved
automatically for the DSS option. An interval must be selected from the available choices that range from 1
minute to 24 hours. Generally you should choose the time interval before entering data for the unit
hydrograph. However, if you change the time interval after entering data, the data will be adjusted to the new
time interval.
Select the time interval for a unit hydrograph paired data using the Component Editor. Access the editor by
selecting a unit hydrograph paired data in the Watershed Explorer. The Paired Data tab in the Component
Editor will display the time interval if the manual entry option is selected.
7.2.8 Retrieval From a HEC-DSS File

Retrieving paired data from a DSS file requires that the data be loaded in a file. The file can be stored on the
local computer or on a network server. It is not a good idea to store the file on removable media since the file
must be available whenever the paired data is selected in the Watershed Explorer, and during computes. It is
poor practice to store the data in the project DSS file used for storing simulation results. Data for each paired
data can be stored in a separate file or one file can contain data for several components. It is best practice to
store the DSS files holding gage data in the Project Directory, or a Subdirectory of the Project Directory. The
HEC-DSSVue utility (HEC 2003) can be used to load paired data into a DSS file.
When the DSS option is selected, you must specify the Filename to use for the paired data component (as
illustrated in this figure (see page 159)). You may type the complete filename if you know it. To use a file
browser to locate the file, press the Open File Chooser button to the right of the DSS Filename field. The
browser allows you to find the desired file but it is limited to locating files with the DSS extension which is
required for all Data Storage System files. Once you locate the desired file, click on it in the browser to select
it and press the Select button. If you change your mind, press the Cancel button or the X button in the upper
corner of the Select HEC-DSS File window to return to the Component Editor.
You must also specify the Pathname to retrieve from the selected DSS file. You may type the complete
pathname if you know it. Each pathname contains six parts called the A-part, B-part, C-part, D-part, E-part, and
F-part. The pathname parts are separated with a slash and may contain spaces. The complete pathname,

including slashes and spaces, can total up to 256 uppercase characters. The following is an example of a
storage-discharge curve pathname:
//BEAR CREEK/STORAGE-OUTFLOW///COMPUTED/
If you do not know the full pathname of the record you wish to use, you can use the Pathname Browser to
specify it. You must select a DSS file first before the browser is available. Press the Select DSS
Pathname button to the right of the DSS Pathname field to open the browser. The browser initially shows all
of the records in the specified DSS file, organized by pathname in the selection table. You can scroll through
the list and select a record pathname by clicking on it. Press the Select button at the bottom of the browser
to choose that record and return to the Component Editor. If you change your mind and do not want to select
a record pathname, press the Cancel button or the X button in the upper right of the Select Pathname From
HEC-DSS File window. You can reduce the number of record pathnames shown in the selection table using
the Search by Parts filters. A separate filter selection is shown for each of the six pathname parts. By
selecting a choice for a filter, only pathnames that match that choice will be shown in the selection table. If
you make choices in several filters, only pathnames that satisfy all of the choices will be shown in the
selection table.
The program observes a preferred order for paired data. For example, storage-outflow is preferred to
outflow-storage. However, the program is capable of using data specified backwards from the preferred
order. The program does observe a very strict set of rules for data type and units within the record
pathnames. Data cannot be used unless is follows the rules correctly; error messages will be generated if
you attempt to use an invalid data type or units. The units of both halves of the paired data must be in the
same unit system. The acceptable pathname C-parts for the different types of paired data are shown in the
following table.
Paired Data Description
Storage-Discharge Function Defines a storage versus outflow function. The C-part

should be "STORAGE-FLOW".
Elevation-Storage Function Defines an elevation versus storage function. The C-part

should be "ELEVATION-STORAGE".
Elevation-Area Function Defines an elevation versus area function. The C-part

should be "ELEVATION-AREA".
Elevation-Discharge Function Defines an elevation versus discharge function also known

as a rating curve. The C-part should be "STAGE-FLOW".
Unit Hydrograph Curve Defines a user-specified unit hydrograph. The C-part should
be "FLOW-UNIT GRAPH".
Percentage Curve Defines a percentage versus percentage function. The C-

part should be "PERCENT".

Cross Section Defines distance versus elevation function to represent a

cross section. The C-part should be "DISTANCE-
ELEVATION".
Inflow-Lag Function Defines an inflow versus time lag function. The C-part
should be "FLOW-LAG".
Outflow-Attenuation Function Defines an outflow versus attenuation function. The C-part

should be "FLOW-K".
Inflow-Diversion Function Defines an inflow versus diversion function. The C-part

should be "FLOW-DIVERSION".
Elevation-Width Function Defines an elevation versus top width function. The C-part
should be "ELEVATION-WIDTH".
Elevation-Perimeter Function Defines an elevation versus wetted perimeter function. The

C-part should be "ELEVATION-PERIMETER".
Diameter-Percentage Function Defines a diameter versus percentage function, also known

as a gradation curve. The C-part should be "DIAMETER-
PERCENT ".
Area-Reduction Function Defines a precipitation depth area reduction function. The

C-part should be "AREA-FACTOR".
Duration-Precipitation Function Defines a time duration versus precipitation depth function.

The C-part should be "DURATION-PRECIPITATION".
ATI-Meltrate Function Defines an antecedent temperature index versus meltrate

function. The C-part should be "ATI-MELTRATE".
ATI-Coldrate Function Defines an antecedent temperature index versus coldrate

function. The C-part should be "ATI-COLDRATE".
Groundmelt Pattern Defines a groundmelt rate that varies throughout the year.
The C-part should be "GROUNDMELT".
Percent Pattern Defines a percentage that varies throughout the year. The
C-part should be "PERCENT".

Cumulative Probability Distribution Defines a cumulative probability function. The C-part should
be "PROBABILITY".
Parameter Value Sample Defines a sequence of model parameter values. The C-part
should be "PARAMETER VALUE".
Parameter Value Pattern Defines a sequence of model parameter values. The C-part
should be "PARAMETER VALUE".
Storage Pattern Defines a guide curve for rule-based reservoir operations.

The C-part should be "STORAGE".
Daily Elevation Pattern Defines a top-of-zone elevation for rule-based reservoir

operations. The C-part should be "ELEVATION".
19 Preferred data order and internal DSS data type label for different types of paired data
The correct units are shown in the following table.
Paired Data X-Label Y-Label Description
Storage-Discharge THOU M3 M3/S Thousands of cubic meters; cubic meters per

ACRE-FT CFS second.
Acre-feet; cubic feet per second.
Elevation-Storage M THOU M3 Meters; thousands of cubic meters.

FT ACRE-FT Feet; acre-feet.
Elevation-Area M THOU M2 Meters; thousands of square meters.

M M2 Meters; square meters.
FT ACRE Feet; acres.
FT SQFT Feet; square feet.
Elevation-Discharge M M3/S Meters; cubic meters per second.

FT CFS Feet; cubic feet per second.
Unit Hydrograph M3/S Cubic meters per second.

CFS Cubic feet per second.

Percentage % % Percent; percent

Curve
Cross Section M M Meters; meters.

FT FT Feet; feet.
Inflow-Lag M3/S HR Cubic meters per second; hours.

CFS HR Cubic feet per second; hours.
Outflow-Attenuation M3/S HR Cubic meters per second; hours.

CFS HR Cubic feet per second; hours.
Inflow-Diversion M3/S M3/S Cubic meters per second; cubic meters per second.
CFS CFS Cubic feet per second; cubic feet per second.
Elevation-Width M M Meters; meters.

FT FT Feet; feet.
Elevation-Perimeter M M Meters; meters.

FT FT Feet; feet.
Diameter-Percentage MM % Millimeters; percent finer.

IN % Inches; percent finer.
Area-Reduction KM2 Square kilometers.

MI2 Square miles.
Duration-Precipitation HR MM Hours; millimeters.

HR IN Hours; inches.
ATI-Meltrate DEGC-D MM/DEG-D Degrees Celsius day; millimeters per degree Celsius
DEGF-D IN/DEG-D day.
Degrees Fahrenheit day; inches per degree
Fahrenheit day.
ATI-Coldrate DEGC-D MM/DEG-D Degrees Celsius day; millimeters per degree Celsius
DEGF-D MM/DEG-D day.
Degrees Fahrenheit day; inches per degree
Fahrenheit day.

Groundmelt Pattern MM/DAY Millimeters per day.

IN/DAY Inches per day.
Percent Pattern % Percent
Cumulative Probability
Parameter Value
Sample
Parameter Value
Pattern
Storage Pattern THOU M3 Thousands of cubic meters.

ACRE-FT Acre-feet.
Note: this is stored as an IR-Year time series.
Daily Elevation Pattern M Meters.

FT Feet.
Note: this is stored as a 1Day time series.
20 Internal DSS units for different types of Paired Data
7.2.9 Table
The data for the current paired data is shown in tabular form on the Table tab of the Component Editor. Data
in the table can be edited if the paired data uses manual entry. Data is not editable if the paired data retrieves
data from a DSS file. Furthermore, if the paired data uses DSS data and no data is available, then the table
will not contain any data.

69 Manually entering data for a storage-discharge curve
You can enter all of the data one value at a time in the table. However, there are tools to help you enter the
data quickly. The table includes support for the clipboard. This means you can copy data stored in a
spreadsheet or other file and then paste it into the table. You can also use the fill tool to enter or adjust data
values in the table. Select the cells in the table you wish to fill and click the right mouse button. A context
menu is displayed; select the Fill command. The Fill Table Options window opens for you to control the
process of filling and adjusting cell values. Options include interpolating the values between the first and last
cell in the selection, several choices for interpolating and replacing missing values, copying the first selected
cell value to all other selected cells, adding a constant value to all selected cells, and multiplying the selected
cell values by a constant. Press the OK button to apply your choice, or the Cancel button to return to the table
without making any changes.
7.2.10 Graph
The data for the current paired data is shown in graphical form on the Graph tab of the Component Editor.
Data in the graph cannot be edited regardless of whether the paired data uses manual entry or retrieves data
from an external DSS file. If no data is available, then the graph will not contain any data.

70 Viewing data for a storage-discharge curve
7.3 Grid Data

Some of the methods included in the program operate on a grid cell basis. This means that parameters must
be entered for each grid cell. It also means that boundary conditions like precipitation must be available for
each grid cell. One example of grid data is the SCS curve number grid, which is used as a parameter grid.
Another example is the temperature gridset, which is a time-series of grids. The program separates different
types of grid data with different data types. Grid data only has to be entered one time. The data are part of
the project and can be shared by multiple Basin or Meteorologic models.
7.3.1 Creating a New Grid

A new grid is created using the Grid Data Manager. To access the manager, click on the Components menu
and select the Grid Data Manager menu command. The manager can remain open while you perform tasks
elsewhere in the program. You can close the manager using the X button in the upper right corner. At the top
of the manager is a Data Type menu. This menu lets you select one of the grid data types supported by the
program. Refer to the Internal DSS data type label for different types of grid data (see table 21) for a complete
list of grid data types. When a data type is selected, the manager will show all grid data of the same type. The
buttons to the right of the grid data list can be used to manage existing data or create new data.

71 Grid Data Manager
To create a grid, press the New button. After you press the button, a window will open where you can name
and describe the new grid. A default name is provided for the grid; you can use the default or replace it with
your own choice. A description can also be entered. If the description is long, you can press the button to the
right of the description field to open an editor. The editor makes it easier to enter and edit long descriptions.
When you are satisfied with the name and description, press the Create button to finish the process of
creating the new grid. You cannot press the Create button if no name is specified. If you change your mind
and do not want to create the grid, press the Cancel button or the X button in the upper right to return to the
Grid Data Manager.
72 Creating a Parameter Grid Data
7.3.2 Copying a Grid

There are two ways to copy a grid. Both methods for copying a grid create an exact duplicate with a different
name. Once the copy has been made it is independent of the original and they do not interact.
The first way to create a copy is to use the Grid Data Manager, which is accessed from
the Components menu. First, select the grid data type you want to copy from the Data Type menu. Then,
select the Grid you want to copy by clicking on it in the list of current grids. The selected grid is highlighted

after you select it. After you select a grid you can press the Copy button on the right side of the window. A
new window will open where you can name and describe the copy that will be created. A default name is
provided for the copy; you can use the default or replace it with your own choice. A description can also be
entered; if it is long you can use the button to the right of the description field to open an editor. When you
are satisfied with the name and description, press the Copy button to finish the process of copying the
selected grid. You cannot press the Copy button if no name is specified. If you change your mind and do not
want to copy the selected grid, press the Cancel button or the X button in the upper right to return to the Grid
Data Manager.
73 Creating a copy of a precipitation gridset after pressing the Copy button in the Grid Data Manager
over the grid data you wish to copy, then press the right mouse button. A context menu is displayed that
contains several choices including Copy. Click the Create Copy menu option. A new window will open where
you can name and describe the copy that will be created. A default name is provided for the copy; you can
use the default or replace it with your own choice. A description can also be entered; if it is long you can use
the button to the right of the description field to open an editor. When you are satisfied with the name and
description, press the Copy button to finish the process of copying the selected grid. You cannot press
the Copy button if no name is specified. If you change your mind and do not want to copy the grid, press
the Cancel button or the X button in the upper right of the window to return to the Watershed Explorer.
74 Renaming a precipitation gridset by selecting it in the Watershed Explorer and using the right-mouse menu

7.3.3 Renaming a Grid

There are two ways to rename a grid. Both methods for renaming a grid changes its name and then all
references to the old name are automatically updated to the new name.
The first way to perform a rename is to use the Grid Data Manager, which you can access from
the Components menu. First, select the grid data type you want to rename from the Data Type menu. Then,
select the Grid you want to rename by clicking on it in the list of current grids. The selected grid is highlighted
after you select it. After you select a grid you can press the Rename button on the right side of the window. A
new window will open where you can provide the new name. You can also change the description at the
same time. If the new description will be long, you can use the button to the right of the description field to
open an editor. When you are satisfied with the name and description, press the Rename button to finish the
process of renaming the selected grid. You cannot press the Rename button if no name is specified. If you
change your mind and do not want to rename the selected grid, press the Cancel button or the X button in
the upper right of the window to return to the Grid Data Manager.
75 Renaming a precipitation gridset after pressing the Rename button in the Grid Data Manager
The second way to rename is from the Watershed Explorer, on the Components tab. Select the grid you want
to rename by clicking on it in the Watershed Explorer; it will become highlighted. Keep the mouse over the
selected grid and click the left mouse button again. The highlighted name will change to editing mode. You
can then move the cursor with the arrow keys on the keyboard or by clicking with the mouse. You can also
use the mouse to select some or all of the name. Change the name by typing with the keyboard. When you
have finished changing the name, press the Enter key to finalize your choice. You can also finalize your
choice by clicking elsewhere in the Watershed Explorer. If you change your mind while in editing mode and
do not want to rename the selected grid, press the Escape key.

76 Renaming a precipitation gridset by selecting it in the Watershed Explorer and using the right-mouse menu
7.3.4 Deleting a Grid

There are two ways to delete a grid. Both methods for deleting a grid will remove it from the project and then
automatically update all references to that grid. Once a grid has been deleted it cannot be retrieved or
undeleted. Any references to the deleted grid will switch to using no grid, which is usually not a valid choice
during a simulation. At a later time you will have to go to those components and manually select a different
grid.
The first way to perform a deletion is to use the Grid Data Manager, which you can access from
the Components menu. First, select the grid data type you want to delete from the Data Type menu. Then,
select the Grid you want to delete by clicking on it in the list of current grids. The selected grid is highlighted
after you select it. After you select a grid you can press the Delete button on the right side of the window
(shown in the following figure). A window will open where you must confirm that you want to delete the
selected grid. Press the OK button to delete the grid. If you change your mind and do not want to delete the
selected grid, press the Cancel button or the X button in the upper right to return to the Grid Data Manager.

77 Preparing to delete a precipitation gridset from the Grid Data Manager
The second way to delete a grid is from the Watershed Explorer, on the Components tab. Select the grid you
want to delete by clicking on it in the Watershed Explorer; it will become highlighted. Keep the mouse over
the selected grid and click the right mouse button. A context menu is displayed that contains several choices
including delete. Click the Delete menu option. A window will open where you must confirm that you want to
delete the selected grid. Press the OK button to delete the grid. If you change your mind and do not want to
delete the selected grid, press the Cancel button or the X button in the upper right to return to the Watershed
Explorer.
78 Preparing to delete a grid from the Watershed Explorer

7.3.5 Retrieval From a HEC-DSS File

Retrieving grid data from a DSS file requires that the data be loaded in a file. The file can be stored on the
local computer or on a network server. It is not a good idea to store the file on removable media since the file
must be available whenever the grid data is selected in the Watershed Explorer, and during computes. It is
poor practice to store the data in a DSS file used for storing simulation results. Data for each grid can be
stored in a separate file or one file can contain data for several grids. However, all data for a gridset must be
stored in the same DSS file and use appropriate pathname convention. It is best practice to store the DSS
files in the Project Directory, or a Subdirectory of the Project Directory. Utilities are available from HEC for
loading various formats of gridded data into a DSS file.
You must specify the Filename to use for the grid data component. You may type the complete filename if
you know it. To use a file browser to locate the file, press the Open File Chooser button to the right of the
DSS Filename field. The browser allows you to find the desired file but it is limited to locating files with the
DSS extension which is required for all Data Storage System files. Once you locate the desired file, click on it
in the browser to select it and press the Select button. If you change your mind, press the Cancel button or
the X button in the upper corner of the Select HEC-DSS File window to return to the Component Editor.
79 Component editor for a precipitation gridset
You must also specify the Pathname to retrieve from the selected DSS file. You may type the complete
pathname if you know it. Each pathname contains six parts called the A-part, B-part, C-part, D-part, E-part, and
F-part. The pathname parts are separated with a slash and may contain spaces. The complete pathname,
including slashes and spaces, can total up to 256 uppercase characters. The following is an example of a
pathname for a percolation parameter grid:
//SOLDIER CR WATERSHED/PERCOLATION///GIS ESTIMATE/
The convention for storing gridset data is different because a separate grid is required for each time interval.
The different records will each have all the same pathname parts except for the D-part and E-part. The D-part
indicates the starting time and the e-part the ending time of the individual record. Any of the record
pathnames can be selected and the program will automatically retrieve the correct data depending on the
time window during a compute. The following is an example of a temperature gridset:
//BRIDGER/TEMP/12JUL2003:1230/12JUL2003:1300/OBS/

If you do not know the full pathname of the record you wish you use, you can use the Pathname Browser to
specify it. You must select a DSS file first before the browser is available. Press the Select DSS
Pathname button to the right of the DSS Pathname field to open the browser. The browser initially shows all
of the records in the specified DSS file, organized by pathname in the selection table. You can scroll through
the list and select a record pathname by clicking on it. Press the Select button at the bottom of the browser
to choose that record and return to the Component Editor. If you change your mind and do not want to select
a record pathname, press the Cancel button or the X button in the upper right of the Select Pathname From
HEC-DSS File window. You can reduce the number of record pathnames shown in the selection table using
the Search by Parts filters. A separate filter selection is shown for each of the six pathname parts. By
selecting a choice for a filter, only pathnames that match that choice will be shown in the selection table. If
you make choices in several filters, only pathnames that satisfy all of the choices will be shown in the
selection table.
Grid Label Description
Precipitation PER-CUM The precipitation depth occurring during the grid

interval. The C-part should be "PRECIPITATION". The
D-part and E-part, respectively, should give the start
and end time for the cumulative value
Temperature PER-AVER The average temperature in degrees over during the

INST-VAL grid interval. The C-part should be "TEMPERATURE".
The D-part and E-part, respectively, should give the
start and end time for the average value.
The temperature in degrees at a specific time. The C-
part should be "TEMPERATURE". The time of the
value should be specified in the D-part.
Radiation PER-AVER The average solar radiation, measured in power per

area, occurring during the grid interval. The C-part
should be "SOLAR RADIATION". The D-part and E-
part, respectively, should give the start and end time
for the average value.
Crop Coefficient PER-AVER The average crop coefficient, specified as a

INST-VAL dimensionless decimal number, occurring during the
grid interval. The C-part should be "CROP
COEFFICIENT". The D-part and E-part, respectively,
should give the start and end time for the average
value.
The crop coefficient, specified as a dimensionless
decimal number, occurring at a specific time. The C-
part should be "CROP COEFFICIENT". The time of the
value should be specified in the D-part.

Storage Capacity INST-VAL The storage capacity, measured as a depth,

associated with a particular condition of the
watershed. The C-part should be "STORAGE
CAPACITY".
Percolation Rate INST-VAL The percolation rate, measured as a depth per time,
watershed. The C-part should be "PERCOLATION".
Storage Coefficient INST-VAL The storage coefficient, measured in hours,

watershed. The C-part should be "STORAGE
COEFFICIENT".
Moisture Deficit INST-VAL The moisture deficit, measured as a depth,

watershed. The C-part should be "MOISTURE
DEFICIT".
Impervious Area INST-VAL The impervious area, measured as a percentage,

watershed. The C-part should be "IMPERVIOUS
AREA".
SCS Curve Number INST-VAL The curve number, as a dimensionless decimal

number, associated with a particular condition of the
watershed. The C-part should be "CURVE NUMBER".
Cold Content INST-VAL The cold content, measured as a depth, associated

with a particular condition of the watershed. The C-
part should be "COLD CONTENT".
Cold Content ATI INST-VAL The cold content antecedent temperature index,
measured in degrees, associated with a particular
condition of the watershed. The C-part should be
"COLD CONTENT ATI".
Meltrate ATI INST-VAL The meltrate antecedent temperature index,

measured in degrees, associated with a particular
condition of the watershed. The C-part should be
"MELTRATE ATI".
Liquid Water INST-VAL The amount of liquid water, measured as a depth,

watershed. The C-part should be "LIQUID WATER".

Snow Water Equivalent INST-VAL The snow water equivalent, measured as a depth,
watershed. The C-part should be "SWE".
Water Content INST-VAL The fraction of the water holding capacity of the soil
that is saturated. The C-part should be "WATER
CONTENT".
Water Potential INST-VAL The potential or suction in the soil expressed as a

pressure during the grid interval. The C-part should
be "WATER POTENTIAL".
Humidity PER-AVER The relative humidity, expressed as a percentage of

INST-VAL saturation, occurring during the grid interval. The C-
part should be "HUMIDITY". The D-part and E-part,
respectively, should give the start and end time for
the average value.
The relative humidity, expressed as a percentage of
saturation, occurring at a specific time. The C-part
should be "HUMIDITY". The time of the value should
be specified in the D-part.
Windspeed PER-AVER The wind speed occurring during the grid interval.
INST-VAL The C-part should be "WINDSPEED". The D-part and
E-part, respectively, should give the start and end
time for the average value.
The wind speed occurring at a specific time. The C-
part should be "WINDSPEED". The time of the value
should be specified in the D-part.
Air Pressure PER-AVER The air pressure occurring during the grid interval.
INST-VAL The C-part should be "PRESSURE". The D-part and E-
part, respectively, should give the start and end time
for the average value.
The air pressure occurring at a specific time. The C-
part should be "PRESSURE". The time of the value
should be specified in the D-part.
Precipitation-Frequency INST-VAL The precipitation amount for a given return interval.

The C-part should be "PRECIPITATION-
FREQUENCY".
21 Internal DSS data type label for different types of grid data

Parameter Units Label Units
Precipitation MM Millimeters
IN Inches
Temperature DEG C Degrees Celsius

Radiation WATT/M2 Watts per square meter

LANG/MIN Langleys per minute
Crop Coefficient UNDEF Dimensionless coefficient
Storage Capacity MM Millimeters

IN Inches
Percolation Rate MM/HR Millimeters per hour

IN/HR Inches per hour
Storage Coefficient HR Coefficient in hours
Moisture Deficit MM Millimeters

IN Inches
Impervious Area % Percent of area
SCS Curve Number UNDEF Dimensionless parameter
Elevation M Meters
FT Feet
Cold Content MM Millimeters

IN Inches
Cold Content ATI DEG C Degrees Celsius


Meltrate ATI DEGC-D Degrees Celsius day

DEGF-D Degrees Fahrenheit day
Liquid Water MM Millimeters

Content IN Inches
Snow Water MM Millimeters

Equivalent IN Inches
Water Content UNDEF Fraction of saturation
Water Potential MM Millimeters

IN Inches
Humidity % Percent relative humidity
Windspeed KPH Kilometers per hour

MPH Miles per hour
Pressure KPA Kilopascal

INHG Inches of mercury
IN HG Inches of mercury
Precipitation-Frequency MM Millimeters
IN Inches
22 Internal DSS units label for different types of grid data
7.3.6 Retrieval From ASCII or GeoTIFF Files

Parameter grid types can be specified as ASCII or GeoTIFF (gridsets are a time-series of grids and include
precipitation and temperature). ASCII/GeoTIFF parameter grids can only be sampled from the Expression
Calculator that is launchable from select Basin Global Editors. ASCII/GeoTiff currently cannot be used to
initialize gridded methods such as Gridded Deficit and Constant Loss or Gridded SCS. These methods still
need to be initialized using the grid capabilities in HEC-DSS. The ASCII/GeoTIFF file format is supported for
all parameter grid types. The GeoTIFF and ASCII Data Source options are available in the Grid Component
Editor.
For Filename, a path to the valid ASCII/GeoTIFF file is provided. To use a file browser to locate the file, press
the Open File Chooser button to the right of the Filename field.
For Units, the user can select units for the gridded data from a list of valid unit options.

In the image below, a GeoTIFF percolation grid has been selected and parameterized.
When using ASCII files, you must include the projection file. The project file should have the
same name as the ASCII grid file and have an extension of *.prj.
80 Retrieving from a GeoTIFF percolation grid
7.3.6.1 Precipitation-Frequency Grids

Precipitation-Frequency Grids, which can be selected in the Hypothetical Storm and Frequency Storm
Precipitation Methods and can be used for supplying precipitation to georeferenced Basin Models, have
some special properties. The Precipitation-Frequency Grids can be specified from a Single-Record HEC-DSS
file, but the most common application is to use grids in ASCII format, like those produced by NOAA's
Hydrometeorological Design Studies Center. Precipitation-Frequency Grids are available as part of NOAA
Atlas 2 and NOAA Atlas 14. Other sources of ASCII-format precipitation-frequency data may also be used
(make sure the ASCII grid's projection file. *.asc, is co-located with the grid file, *.asc). Many such products
are distributed as integer grids with a scale factor. To get the true value of the data in the grid, the grid values
must be divided by the scale factor. As shown in the figure below, the Grid Data Component Editor for
Precipitation-Frequency Grids allows the user to select the units that the data are stored in (in or mm) and
also the scale factor. Typical unit/scale factor combinations are inches/1000.0 for NOAA Atlas 14 and
inches/100000.0 for NOAA Atlas 2. Metadata for the data source should always be checked prior to use.
81 Component editor for a precipitation-frequency gridset, sourced from an ASCII raster file.

7.3.6.2 Precipitation Frequency Grid Importer

Multiple precipitation frequency grids can be imported to the project's grid data simultaneously from
the Precipitation Frequency Grid Importer dialog. This feature also internalizes external source files for the
grids by copying them to <Project root>/data directory. To access the dialog, go to File | Import | Gridded
Data | Precipitation Frequency.
The Precipitation Frequency Grid Importer dialog is shown in the figure below. Enter a path to a valid ASCII/
GeoTiff file in the Path column. Alternatively, press the file browse icon in the right corner of the Path field to
browse to the file's location. The file browse icon in the top right corner of the dialog can be used to select
and add multiple files from a common folder. A default name matching the file name is provided for the grid
in the Name field. You can keep the default or enter a different name. Select the units in the Units field to
match the units of the data source, and enter the unit scale factor specified in the data source in the Unit
Scale Factor field. Typical data sources, units and scale factors for precipitation frequency grids are
discussed in the Precipitation-Frequency Grids section above.
82 Precipitation Frequency Grid Importer Dialog
7.4 Terrain Data

Information about the elevation of the land surface is necessary for delineating a watershed and creating a
Basin Model based on that delineation. Terrain Data are used in the delineation process and may also be
used to visualize the relief of a watershed as a base map. Each terrain data component stores a single
continuous Digital Elevation Model (DEM) and can be linked to multiple Basin Models.

Terrain File Size
The HEC-HMS team has confirmed the GIS delineation tools work with terrain files sizes up to 2
GB; however, we recommend you use a level of terrain detail/resolution that is appropriate for
subbasin and reach delineation. We have found that larger grid cell sizes, like 30 meters,
adequately provide accurate delineation results in many cases. There are terrain reconditioning
tools available that allow you to burn in streams, like those from the National Hydrology Dataset,
and add walls using HUC watershed boundaries to improve delineation results when using
coarser terrain datasets.
An example showing GIS processing times and results are provided for varying terrain
resolutions - https://www.hec.usace.army.mil/confluence/hmsdocs/hmsguides/gis-tutorials-
and-guides/comparing-gis-processing-run-times-with-different-size-terrain-models-and-
computers.
Less time spent downloading and processing terrain data that does not provide added benefit for
subbasin delineation allows you to spend more time calibrating and validating the model.
7.4.1 Creating Terrain Data

Terrain data can be created in two ways, both of which launch the same wizard. The first is to select the
Components menu and then Create Component and slide over to Terrain Data, which will directly launch the
wizard.
83 Launching the Terrain Data Creation wizard directly
The second way is to select the Components menu and then the Terrain Data Manager.

84 Opening the Terrain Data Manager
Once in the the manager, select the New button. Other buttons in the manager allow for copying, renaming,
deleting or adding the description to a terrain data component.
85 Launching the Terrain Data Creation wizard from the Terrain Data Manager
Either of the two methods above will launch the Create a Terrain Data wizard. First you must provide a
unique Name for the terrain data. Pressing Next will take you to the next step of the process. You can cancel
the creation of a terrain data component by pressing Cancel at any time during the wizard.

86 The first step of the Terrain Data Creation wizard
Next, you must provide the Filename of a GIS raster file of elevation data, as well as the Vertical Units of that
elevation dataset. You can browse to the file location of such a dataset using the Folder icon button. Units
are specified in a drop-down menu and the options are meters and feet. You may return to the first step of
the wizard by pressing the Back button. Selecting Finish will complete the wizard and the terrain data
component will be visible in the Watershed Explorer. Selecting Cancel will abort creation of the terrain data
component.
87 The second and final step of the Terrain Data Creation wizard
7.4.2 Copying Terrain Data

There are two ways to create a copy of an existing terrain data component. The first is to launch the Terrain
Data Manager from the Components menu and selecting an existing terrain data component in the manager.
The Copy button in the manager will then be available.

88 Creating a copy of a terrain data component from the Terrain Data Manager
Selecting the Copy button will prompt you to provide a new unique name for the copied terrain data. Pressing
Cancel or the X button will cancel the copy process. A name must be specified and the Copy button will not
be available if no name is specified or if the name is not unique. Optionally, you may provide a description of
the terrain data; if it is long, use the button to the right side to expand the text field.
89 Terrain Data copy dialog
The second way to create a copy of an existing terrain data component is to right-click on a terrain data
component in the Watershed Explorer and select Create Copy. This will also launch the Copy Terrain Data
dialog.
90 Creating a copy of a terrain data component from the Watershed Explorer

7.4.3 Renaming Terrain Data

There are two ways to rename a terrain data component. Both renaming methods will change the terrain
data name and update all references that point to the old name, to the new name.
The first way to rename a terrain data component is to launch the Terrain Data Manager through
the Components menu. There, you may select a terrain and press the Rename button, which will allow you to
choose a new name for the terrain data. Choosing Cancel or X will abort the renaming
process. Choosing Rename will change the name of the terrain data component and update all references
from the old name to the new name. The Rename button will not be available if no name is entered.
91 Renaming a terrain data component from the Terrain Data Manager
92 The Rename Terrain Data dialog
The second way to rename a terrain data component is to right click on an existing terrain data in
the Watershed Explorer and select Rename.

93 Renaming a terrain data component from the Watershed Explorer
This will allow you to directly edit the name of the terrain data in the Watershed Explorer. Press Enter on the
keyboard to accept the new name.
94 Editing the name of a terrain data component in the Watershed Explorer
7.4.4 Deleting Terrain Data

There are two ways to delete a terrain data component. Both methods remove it from the project and then
update any references pointing to that terrain data component. It does not delete the GIS raster data on disk
that was used as the source data to create the terrain data. Once the terrain data component has been
deleted, it cannot be retrieved or undeleted. Any references to the deleted terrain data will switch to using no
terrain data.
The first way to delete a terrain data component is to use the Terrain Data Manager through
the Components menu. There you can select the terrain data you wish to delete by clicking on it, and then
pressing the Delete button.

95 Deleting a terrain data component from the Terrain Data Manager
You will be prompted to confirm your choice to delete the terrain data. If you select OK the terrain data will be
deleted; if you select Cancel or the X it will remain.
96 Terrain Data Deletion Confirmation dialog
The second way to delete a terrain data component is through the Watershed Explorer. If you right-click on a
terrain data component and select Delete, you will see the Terrain Data Deletion Confirmation dialog. If you
select OK, the terrain data will be deleted; if you select Cancel or the X, it will remain.
97 Deleting terrain data from the Watershed Explorer

7.4.5 Associating Terrain Data with a Basin Model

In order to use a terrain data component in the watershed delineation process, it must be first associated
with a Basin Model. After creating terrain data, create or select a Basin Model. In the Basin
Model Component Editor, you may choose a terrain data component to assign to the Basin Model. After
selecting a terrain data component, press Save or choose the File menu and select Save, or press Ctrl+S to
save the project.
98 Selecting terrain data to use with a Basin Model
If the current Basin Model does not have a coordinate system, you will then be prompted to choose a Basin
Model Coordinate System (see page 245). Because terrain data are spatially referenced, the Basin Model must
also be spatially referenced. You will be prompted to choose a coordinate system for the spatial referencing
of the Basin Model. If you press Select, you will be allowed to specify a coordinate system for the Basin
Model in a number of ways. If you choose Skip the coordinate system for the Basin Model will be set based
on the coordinate system of the GIS data underlying the terrain data you are trying to associate with the
Basin Model.
99 Basin Model Coordinate System prompt
If you choose to select a coordinate system for your Basin Model, see Coordinate System (see page 167) for an
overview of the tool for doing so.

Once the Basin Model Coordinate System is set, or if the Basin Model already has a coordinate system, the
Basin Model map will be updated with a rendering of the elevation data.
100 Terrain data viewed in the Basin Model Map window
7.5 References: Shared Component Data

Hydrologic Engineering Center. January 2003. HEC Data Storage System Visual Utility Engine: User's Manual.
U.S. Army Corps of Engineers, Davis, CA.

8 Watershed Physical Description

This section describes how watershed information is entered into the program using a Basin Model. The
Basin Model is used for describing the physical properties of the watershed and the topology of the stream
network. It will contain the modeling components that describe canopy interception, surface storage,
infiltration, surface runoff, baseflow, channel routing, and lakes. It may additionally contain components for
representing engineered structures such as diversions, reservoirs, and pump stations. It will generally be the
focus of attention in performing simulations and viewing results. By creating multiple representations of the
same watershed, different development scenarios or management alternatives can be evaluated.
8.1 Basin Models

Basin Models are one of the main components in a project. Their principle purpose is to convert atmospheric
conditions into streamflow at specific locations in the watershed. Hydrologic elements are used to break the
watershed into manageable pieces. They are connected together in a dendritic network to form a
representation of the stream system. Background maps can be used to aid in placing the elements in a
spatial context.
8.1.1 Creating a New Basin Model

A new Basin Model is created using the Basin Model Manager. To access the manager, click on
the Components menu and select the Basin Model Manager command. The manager will open and show all
of the Basin Models currently in the project. The manager can remain open while you manage Basin Models
or while you perform tasks elsewhere in the program. You can close the manager using the X button in the
upper right corner. The buttons to the right of the model list can be used to manage existing models or
create a new one. To create a new Basin Model, press the New button. After you press the button, a window
will open where you can name and describe the new Basin Model that will be created. A default name is
provided for the new model; you can use the default or replace it with your own choice. A description can
also be entered. If the description is long, you can press the button to the right of the description field to
open an editor. The editor makes it easier to enter and edit long descriptions. When you are satisfied with the
name and description, press the Create button to finish the process of creating the new Basin Model. You
cannot press the Create button if no name is specified for the new model. If you change your mind and do
not want to create a new Basin Model, press the Cancel button or the X button in the upper right to return to
the Basin Model Manager window.
101 Creating a new Basin Model
Watershed Physical Description – 190

8.1.2 Copying a Basin Model

There are two ways to copy a Basin Model. Both methods for copying a model create an exact duplicate with
a different name. Once the copy has been made it is independent of the original and they do not interact.
The first way to create a copy is to use the Basin Model Manager, which is accessed from
the Components menu. Select the Basin Model you wish to copy by clicking on it in the list of current Basin
Models. The selected model is highlighted after you select it. After you select a model you can press
the Copy button on the right side of the window. A new Copy Basin Model window will open where you can
name and describe the copy that will be created. A default name is provided for the copy; you can use the
default or replace it with your own choice. A description can also be entered; if it is long you can use the
button to the right of the description field to open an editor. When you are satisfied with the name and
description, press the Copy button to finish the process of copying the selected Basin Model. You cannot
press the Copy button if no name is specified. If you change your mind and do not want to copy the selected
Basin Model, press the Cancel button or the X button in the upper right to return to the Basin Model
Manager window.
102 Creating a copy of a Basin Model
Basin Model you wish to copy, then press the right mouse button. A context menu is displayed that contains
several choices including Copy. Click the Create Copy command. A new Copy Basin Model window will open
where you can name and describe the copy that will be created. A default name is provided for the copy; you
can use the default or replace it with your own choice. A description can also be entered; if it is long you can
use the button to the right of the description field to open an editor. When you are satisfied with the name
and description, press the Copy button to finish the process of copying the selected Basin Model. You
cannot press the Copy button if no name is specified. If you change your mind and do not want to copy the
selected Basin Model, press the Cancel button or the X button in the upper right of the Copy Basin
Model window to return to the Watershed Explorer.

103 Copying a Basin Model from the Watershed Explorer
8.1.3 Renaming a Basin Model

There are two ways to rename a Basin Model. Both methods for renaming a model change its name and then
all references to the old model name are automatically updated to the new name.
The first way to perform a rename is to use the Basin Model Manager, which you can access from
the Components menu. Select the Basin Model you wish to rename by clicking on it in the list of current
Basin Models. The selected model is highlighted after you select it. After you select a model you can press
the Rename button on the right side of the window. A new Rename Basin Model window will open where you
can provide the new name. If you wish you can also change the description at the same time. If the new
description will be long, you can use the button to the right of the description field to open an editor. When
you are satisfied with the name and description, press the Rename button to finish the process of renaming
the selected Basin Model. You cannot press the Rename button if no name is specified. If you change your
mind and do not want to rename the selected Basin Model, press the Cancel button or the X button in the
upper right of the Rename Basin Model window to return to the Basin Model Manager window.
104 Renaming a Basin Model
The second way to rename is from the Components tab of the Watershed Explorer. Select the Basin Model
you wish to rename by clicking on it in the Watershed Explorer; it will become highlighted. Keep the mouse
over the selected model and click the left mouse button again. The highlighted name will change to editing
mode as shown below. You can then move the cursor with the arrow keys on the keyboard or by clicking with

the mouse. You can also use the mouse to select some or all of the name. Change the name by typing with
the keyboard. When you have finished changing the name, press the Enter key to finalize your choice. You
can also finalize your choice by clicking elsewhere on the Components tab. If you change your mind while in
editing mode and do not want to rename the selected Basin Model, press the Escape key.
105 Renaming a Basin Model in the Watershed Explorer
8.1.4 Renaming Basin Model Elements

You can also rename individual or multiple hydrologic elements from the Rename Basin Elements window.
To access the window, right-click on the basin name in the Components tab of the Watershed Explorer and
click on the Rename Basin Elements option. Once renamed, all the properties of the original element are
updated to the new name. However, the results of any previous simulation runs involving the renamed
elements are deleted, and you will need to rerun the simulations.
106 Rename Basin Elements option accessed from the Watershed Explorer

Clicking the Rename Basin Elements menu option opens the window with a table, where elements can be
renamed by double-clicking on an element's name in the last column of the table and typing in a new name,
as shown in the following figure. Once all the changes are entered, click the Apply button to apply the
changes and leave the window open, OK button to apply the changes and close the window, or click Cancel
or X to close and discard the changes.
107 Rename Basin Elements window
You can also sort and filter the hydrologic elements in the table. To filter elements by type (e.g. Subbasin,
Junction, etc.), click the down arrow in the Show Elements drop down menu in the top left portion of the
window and select the desired element type, as shown in the following figure. Only the elements of the
selected type will be displayed in the table.
108 Filtering elements by type

To sort elements in Hydrologic or Alphabetical order, press the down arrow and select the corresponding
option from the Sorting drop down menu in the top right portion of the window, as shown in the following
figure.
109 Sorting elements
A demonstration of this new feature can be found here:
Sorry, the widget is not supported in this export.

But you can reach it using the following URL:
http://youtube.com/watch?v=vNco8VmgB80
8.1.5 Deleting a Basin Model

There are two ways to delete a Basin Model. Both methods for deleting a model remove it from the project
and then automatically update all references to that model. Once a model has been deleted it cannot be
retrieved or undeleted. Any references to the deleted model will switch to using no Basin Model, which is
usually not a valid choice during a simulation. At a later time you will have to go to those components and
manually select a different Basin Model.
The first way to perform a deletion is to use the Basin Model Manager, which you can access from
the Components menu. Select the Basin Model you wish to delete by clicking on it in the list of current Basin
Models. The selected model is highlighted after you select it. After you select a model you can press
the Delete button on the right side of the window. A window will open where you must confirm that you wish
to delete the selected model as shown in the following figure. Press the OK button to delete the model. If you
change your mind and do not want to delete the selected Basin Model, press the Cancel button or
the X button in the upper right to return to the Basin Model Manager window.

110 Preparing to delete a Basin Model from the Basin Model Manager
The second way to delete is from the Components tab of the Watershed Explorer. Select the Basin Model
you wish to delete by clicking on it in the Watershed Explorer; it will become highlighted. Keep the mouse
over the selected model and click the right mouse button. A context menu is displayed that contains several
choices including Delete. Click the Delete command. A window will open where you must confirm that you
wish to delete the selected model. Press the OK button to delete the model. If you change your mind and do
not want to delete the selected Basin Model, press the Cancel button or the X button in the upper right to
return to the Watershed Explorer.
111 Deleting a Basin Model in the Watershed Explorer

8.1.6 Importing a Basin Model

You can import a Basin Model from another project into the current project. The model must have been
created previously and stored on your computer or an accessible network location. Click the Tools menu and
select the File | Import | Basin Model command. A file browser will open that you can use to find the model
you wish to import. The browser will only allow you to select Basin Model files which end with the BASIN
extension. When you click on a Basin Model file in the browser, the description of the model is shown on the
right side of the browser. Once you have located and selected the desired Basin Model, press
the Select button. If you change your mind, you can press the Cancel button or the X button in the upper right
to return to the main program window without importing a model. After you make your selection, the Basin
Model will be checked for dependent data such as time-series gages. The user is given the opportunity to
also import any required data. The program automatically copies the selected file and any additional data
into the project folder and adds the various components to the project.
8.2 Basin Model Properties

There are a number of properties for Basin Models that are selected on the Component Editor, as shown
below. These properties control configuration settings for the Basin Model itself or for all hydrologic
elements within the Basin Model. Access the Component Editor from the Watershed Explorer on the
Components tab by clicking on a Basin Model icon.
112 Viewing the Basin Model properties
8.2.1 Local Flow

Local Flow can be computed at junctions. Local flow is defined as the sum of all subbasin and source
outflows entering a junction. The subbasin and source elements must be connected directly to the junction.
Any subbasin or source outflow that moves through a routing element is no longer considered local flow.
When local flow is disabled, a junction element computes outflow as the sum of all inflow from any type of
element. No local flow is computed. When local flow is enabled, a junction continues to compute outflow as
the sum of all inflow. However, in addition to computing outflow, it additionally computes local flow (sum of
subbasin and source elements). Enabling or disabling local flow is done in the Component Editor for the

Basin Model, as shown above. Access the Component Editor from the Watershed Explorer on the
Components tab by clicking on a Basin Model icon.
8.2.2 Unregulated Outputs

Unregulated Outputs (flow, stage, water surface elevation, velocity, etc) can be computed at all elements
downstream of regulating structures. Within HEC-HMS, reservoir and diversion elements are considered
regulating structures. Unregulated outputs are produced by setting the outflow of a regulating structure
equal to the computed inflow. In this way, translation, attenuation, diversion, and/or other regulating effects
are removed.
The Unregulated Outputs option is accessed within the Component Editor for the Basin Model, as shown
above. When the Unregulated Outputs option is disabled, no changes to the computations will be made.
When the Unregulated Outputs option is enabled, a second iteration will be made through all Basin Model
computations. Within this second iteration, the routing method for all reservoir and diversion elements will
be set to None. Additional time series will then be written to disk and made available within the Results tab.
Unregulated outputs can be generated within all simulation types except for Optimization Trials.
8.2.3 Flow Ratio

Flow Ratios can be used to increase or decrease the computed flow by a fixed ratio; they can only be applied
to subbasin and source elements. Once the flow ratios are turned on, each subbasin and source can have a
separate ratio, or no ratio. It is not necessary to enter a ratio for every element in order to have a ratio at one
element. The ratio 1.0 is used if no ratio is specified. The calculations for computing outflow proceed
normally according to the method choices and parameter data for each element. At the conclusion of normal
processing, the flow ratio is applied to produce the final outflow.
Flow ratios are enabled or disabled in the Component Editor for the Basin Model, as shown above. After
disabling the flow ratios, any ratios specified for subbasin and source elements in the Basin Model are
removed and cannot be retrieved again or undeleted. The actual flow ratio is specified in the Component
Editor for the element on the Options tab. Access the editor from the Watershed Explorer on the
Components tab by clicking on the element icon. The last tab in the Component Editor is the Options tab.
The flow ratio field is disabled when flow ratios are disabled in the Basin Model. The field becomes enabled
when flow ratios are enabled in the Basin Model. The Flow Ratio field is never enabled for elements other
than subbasins and sources.
8.2.4 Missing Flow

Missing inflow data for an element can be set to zero. Under some conditions it may be possible for source
or subbasin elements to produce outflow with missing values. Downstream routing elements generally
cannot process missing data. When missing flow data is not replaced, any element that encounters missing
inflow data will halt a simulation with an error message. When missing flow data is replaced, the missing
inflow data is set to zero and a message is generated that indicates how many values were missing.
Processing in the routing element proceeds normally after any missing inflow data is set to zero. Setting the
action to take with missing inflow data is done on the Component Editor for the Basin Model, as shown
above.

8.2.5 Unit System

Each Basin Model must be in either United States customary units (sometimes called English units) or in
system international units (also called metric units). All parameter data in a Basin Model must be in the
same unit system. If you change the unit system, all data will be automatically converted to the new unit
system. All time-series data, paired data, and gridded data referenced in a Basin Model will be in its own unit
system. If necessary these referenced data are automatically converted to the unit system of the Basin
Model during a simulation.
The unit system is designated within the Component Editor for the Basin Model, as shown above. Access
the Component Editor by clicking the Basin Model icon on the Components tab of the Watershed Explorer. If
you change the unit system, all data is automatically converted to the new selection.
8.2.6 Sediment
The movement of sediment in the watershed can be included as part of the hydrology of the Basin Model.
When the sediment is disabled, no sediment processing will take place in the Basin Model. When the
sediment is enabled, appropriate sediment simulation components are added to elements in the Basin
Model. Subbasin elements include surface erosion and wash-off. Reach elements include erosion,
deposition, and sediment transport. Reservoir elements include sediment settling and sediment transport.
Source, junction, diversion, and sink elements pass sediment through the channel network.
8.2.7 Water Quality

Nutrient water quality (nitrogen and phosphorus) will be enabled within a future version of HEC-HMS.
8.3 Basin Model Map

The Basin Model Map is the primary method for visualizing the hydrologic elements that will be added to the
Basin Model to represent the watershed. Background maps can be added to display almost any type of
mapping data. It is often helpful to configure the background maps before beginning the process of creating
hydrologic elements and the flow network.
8.3.1 Background Maps

Background Maps provide a spatial context for the hydrologic elements composing a Basin Model. The
maps are not actually used in the compute process, but they can be very helpful in showing the spatial
relationship between elements. They are commonly used for showing the boundaries of a watershed or the
location of streams. They can also be useful for showing supplemental information such as the location of
levees. The use of background maps is always optional.
Background maps are added and removed using the Map Layers window. Access the window by clicking
the View menu and selecting the Map Layers command. The menu command is only available if the Basin
Model Map window is currently open. Any changes made to the current background maps or their draw order
take affect immediately as soon as they are made.

Add a map to the list of current background maps by pressing the Add button. A file browser opens for you
to select the map file you wish to add. Select the type of map file you wish to add using the Files of
type selection list at the bottom of the file browser.
Locate the map file you wish to add and select it. Press the Select button to add the map to the list of current
background maps. If you change your mind and do not want to add a map, press the Cancel button or
the X button in the upper right of the Select window. The program does not include any coordinate
transformation tools so you must independently make certain that all maps you wish to use are in the same
coordinate system.
113 Background maps can be added to provide a spatial context for the Basin Model elements
The current background maps are drawn in a specified order so that you can control overlapping and other
drawing issues. The draw order is based on the order they are shown in the Background Maps window. The
map at the bottom of the list is drawn first. After it is drawn, the map shown above it in the list is drawn
second. The map shown at the top of the list is drawn last. The hydrologic elements are drawn after all of the
maps have been drawn. You may temporarily turn drawing for a map On or Off using the check box in the
map list.
The draw order of the maps can be changed once all the desired background maps are shown in the list of
current maps. To change the order of a map you must first select it in the list of current maps. Place the
mouse over the desired map and click the left mouse button; the map name is highlighted to show that it is
selected. Press the Move Up button to move the map up in the draw order so that other maps are drawn first.
Press the Move Down button to move the map down in the draw order so that other maps are drawn after it.
Each time you press the Move Up or Move Down button the map is moved one position up or down. You can
press the buttons more than once to get the map to the desired position in the drawing order.
A background map can be removed from the display. Place the mouse over the map you wish to remove and
select it by clicking the left mouse button; the map name is highlighted to show that it is selected. Press
the Remove button. The background map is not deleted when it is removed from the list of current
background maps. The files that contain the actual background map data cannot be deleted from the
program; they must be deleted manually.

The drawing properties of a background map using the Shape File format can be controlled. The Draw
Properties button will be enabled whenever a map is selected that uses the Shape File format. Pressing the
button will open an editor that allows control of drawing properties including colors, line style and width,
shading, transparency, and other properties. Changes may be previewed before they become final. At this
time, draw properties cannot be controlled for other file formats.
For raster data, the Draw Properties button opens the Properties Editor, which allows detailed customization
of the way that rasters are displayed in the map, as shown below. The Symbology options are either Stretch
or Classify. When Stretch is selected, you must enter Maximum and Minimum values for the data range. By
default, the program extracts the maximum and minimum range from the dataset. The Classify option allows
you to break up the data into bins, each bin has a separate color. You can choose the Color Scheme for the
raster dataset.
There are Additional Settings for displaying data that fall outside of the minimum and maximum range.
The Display tab contains options for Transparency, turning on Hillshading, and Inverting the color scheme.
114 Raster display properties editor
8.3.2 Adjusting the View and Zooming

Several tools and commands are provided to zoom in, zoom out, and move around the Basin Model
Map window. Several of the tools are on the toolbar. All of the commands can be found on the View menu.
There are three ways to zoom in on the Basin Model Map window. The first way is to use the scroll wheel of
your mouse. When the mouse cursor is over the Basin Model Map window and the scroll wheel is rolled
forward (away from you), the map will be redrawn, with the view magnified on the location where the mouse

cursor was positioned while the scroll wheel was rolled. The second way to zoom in on the Basin Model
Map window is to use the Shift + = key combination on the keyboard. The third way to zoom in is to use the
Zoom In command on the View menu, which will zoom in by a predefined amount. The Zoom In command is
only accessible when the Basin Model Map window is open.
There are three ways to zoom out on the Basin Model Map window. The first way is to use the scroll wheel of
your mouse. When the mouse cursor is over the Basin Model Map window and the scroll wheel is rolled
backward (towards you), the map will be redrawn, with the view zoomed out centered on the location where
the mouse cursor was positioned while the scroll wheel was rolled. The second way to zoom out on
the Basin Model Map window is to use the - key on the keyboard. The third way to zoom out is to use the
Zoom Out command on the View menu, which will zoom out by a predefined amount. The Zoom
Out command is only accessible when the Basin Model Map window is open.
Navigating around the map at a constant zoom level is the default behavior for the Arrow Tool. While the
Arrow Tool is activated, if the user presses down the mouse button inside the Basin Model Map window, but
not on a hydrologic element, and drags the mouse in any direction, the map view will pan with the mouse
drag. When the mouse button is released, the map will be redrawn. If the user clicks (presses and releases)
the mouse in Arrow Tool mode on a hydrologic element, that element will be selected.
It can be very difficult to find the selected element or elements in a Basin Model with many hydrologic
elements. A special tool has been created to zoom to the current element selection. Begin by creating an
element selection. You can click on an element in the Watershed Explorer, or use the Edit | Select By
Name command to create a current selection. You can zoom to the selection by clicking the View menu and
selecting the Zoom To Selected command. The Basin Model Map window will automatically zoom to an
appropriate scale for the current element selection and center the view on the selection.
After zooming in and moving around the Basin Model, you may want to quickly return to viewing the entire
model. You can immediately zoom to the maximum extents. Click the View menu and select the Zoom To
All command. The Basin Model Map window will automatically zoom out to the coordinates specified as the
maximum extents and redraw.
8.3.3 Drawing Elements and Labels

Hydrologic elements can be drawn as Icons, as GIS Features, or as GIS Features and Icons. Drawing with
icons and GIS features is controlled separately. There is only one way to control each property. Additionally,
elements can be labeled when they are drawn.
The basic method for drawing elements is with Icons. Each element type has a unique icon for quick visual
identification. Reach elements are an exception since they are drawn as a line from the upstream end of the
reach to the downstream end. Turn the icons on and off using the View menu. Click on the View | Map
Layers menu option. An Icons layer is located within the Map Layers list, as shown in the following figure. A
check is shown next to the icons layer when they are displayed in the map. You can turn off display of the
icons by unchecking the Icons option.
GIS Features can also be turned on and off in the Basin Model map using the Map Layers editor. Subbasin
and reach GIS features show up in the Current map layers list as Subbasins and Reaches, respectively. If no
subbasin or reach GIS features have been added to the Basin Model, then these items, subbasins and
reaches, will not be in the Map Layers editor. Finally, the Map Layers editor is where background map layers,
shape files, can be added to the Basin Model map. There are additional editors available from the Map
Layers editor for changing the Draw Properties for background map layers. Draw properties cannot be
modified for Icons and subbasin/reach GIS features.

115 Turn on or off display of element icons, GIS features, and background GIS map layers from the Map Layers editor
The advanced method for drawing subbasin, reach, and reservoir elements is with GIS Features. Each
subbasin element can be drawn with a polygon representing the outline of the subbasin. Each reservoir
element can also be drawn with a polygon which usually represents the outline of the maximum extent of the
pool. Each reach element can be drawn with a polyline representing the exact turns of the stream. GIS
Features must be "imported" into a Basin Model using the Georeference Existing Elements19 or the Import
Georeferenced Elements20 options available from the GIS menu. Before adding GIS Features to a Basin
Model, the coordinate system must be defined. A Basin Model's coordinate system can be set using the
Coordinate System21 option from the GIS menu.
Using GIS Features is optional. When GIS Features are used, it is not necessary to have subbasin, reservoir,
and reach geometric data. It is permissible to use GIS features for one, two, or all three types of elements.
Additionally, it is not necessary to have GIS Features for every single subbasin, reservoir, or reach in the
Basin Model. GIS Features will be drawn for the elements for which it is available.
Element labels can be drawn with element Icons or GIS Features. Currently, the only option for the label is the
name of the element. Turn the element labels on and off using the View menu. Click on the View menu and
select the Draw Element Labels command to choose how to draw the labels. A check is shown next to the
selected option. To change the selected option, use the mouse to click on a different choice.
8.3.4 Displaying Flow Directions

Each reach element in the network only allows flow to move in one direction; from upstream to downstream.
If a reach is connected to its upstream and downstream elements in the wrong direction, then the network
may not be a good representation of the physical watershed. You can verify the flow directions by displaying
direction arrows. When the direction arrows are turned on, arrow heads are added to reach elements to show
the flow direction. There is only one way to turn the flow direction arrows on and off.
19 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/.GIS+Menu+v4.4#id-.GISMenuv4.4-GeoreferenceExistingElements
20 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/.GIS+Menu+v4.4#id-.GISMenuv4.4-ImportGeoreferencedElements
21 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/.GIS+Menu+v4.4#id-.GISMenuv4.4-BasinModelCoordinateSystem

Turn the flow direction arrows on and off using the View menu. Click on the View menu and select the Draw
Flow Directions command. A check is shown next to the menu command to indicate that the arrows are
turned on. You can turn off the direction arrows by clicking on the same menu command again.
8.4 Hydrologic Elements

Hydrologic Elements are the basic building blocks of a Basin Model. An element represents a physical
process such as a watershed catchment, stream reach, or confluence. Each element represents part of the
total response of the watershed to atmospheric forcing. Seven different element types have been included in
the program: Subbasin, Reach, Reservoir, Junction, Diversion, Source, and Sink.
An element uses one or more mathematical models to describe a physical process occurring in the
watershed. Sometimes the model is only a good approximation of the original physical process over a
limited range of environmental conditions. Data availability and the required parameters of a model can also
determine fitness. To make the program suitable for many different conditions, most elements have more
than one model or method for approximating the physical process. For example, there are seven different
methods for specifying overland flow for a subbasin.
8.4.1 Creating a New Element

New hydrologic elements are created directly in the Basin Model Map window. Begin the process of creating
a new element by opening the Basin Model into which you wish to add a new element. Select a Basin Model
in the Watershed Explorer to open it. Separate tools are provided in the toolbar for each of the seven
different kinds of element. Select the tool corresponding to the type of element you wish to create: Subbasin,
Reach, Reservoir, Junction, Source, Diversion, or Sink. After selecting the appropriate tool, move the mouse
over the Basin Model Map window; the mouse cursor changes to cross hairs. Move the mouse until the cross
hairs are over the location where you wish to create the element. Click the left mouse button. A window will
open where you can name and describe the new hydrologic element that will be created, as shown below. A
default name is provided for the new element; you can use the default or replace it with your own choice. A
description can also be entered. If the description is long, you can press the button to the right of the
description field to open an editor. The editor makes it easier to enter and edit long descriptions. When you
are satisfied with the name and description, press the Create button to finish the process of creating the new
hydrologic element. You cannot press the Create button if no name is specified for the new element. If you
change your mind and do not want to create a new hydrologic element, press the Cancel button or
the X button in the upper right to return to the Basin Model Map window. After you finish creating one
element, the element creation tool is still selected and you can create additional new elements of the same
type.

116 Creating a subbasin in a new Basin Model
Most of the elements are created by clicking the mouse button over the location where you want to create
the element. However, two mouse clicks are required when creating a Reach element. To create a reach,
begin by selecting the correct tool from the toolbar. Next click once over the location you want to be the
upstream end of the reach. Then as you move the mouse you will see a line connecting the mouse to the
upstream end of the reach. Move the mouse to the location you want to be the downstream end of the reach
and click. You will finish the process of creating a reach by selecting a name and entering the optional
description.
8.4.2 Copying an Element

Hydrologic elements can be copied to the clipboard from one Basin Model and then exact duplicates can be
pasted in either the same or a different Basin Model. Begin by opening the Basin Model that contains the
element or elements you wish to copy. Select the hydrologic element you wish to copy by clicking on it with
the Arrow Tool. You may also select more than one element in the map by either holding down the CTRL or
Shift keys to select multiple elements, or by drawing a box around multiple elements. The selected element
or elements become highlighted after the selection. After you make a selection, go to the Edit menu and

select the Copy button as shown in the following figure. You can now paste the selection into the same or a
different Basin Model. The copy command is only available if there is at least one element selected.
A single element can be copied using the right mouse context menu. Select an element in the Basin Model
Map, then place the mouse on top of the selected element and click the right mouse button. A context menu
will open with Copy Element menu option.
As shown in the following figure, menu options are available from the Edit menu to select all elements
upstream of the selected location or to invert the selected elements. The program tracks the hydrologic
connectivity of all elements within a Basin Model. The Edit | Select Upstream menu option was added as a
quick option for selecting multiple elements upstream of a selected junction, reach, reservoir, or division
element. The Edit | Invert Selection menu option was added as a quick option of inverting the selected set of
Basin Model elements.
The Invert Selection option could be used to select all elements downstream of a location. First, you would
choose a location in the Basin Model Map, and then choose the Select Upstream option to select all points
upstream of the selected location. Second, you would choose the Invert Selection option to switch the
selection, effectively selecting all elements downstream of the originally selected element.
117 Copying a group of selected elements from the Basin Map to the clipboard
8.4.3 Pasting an Element

An element in the clipboard can be pasted into a Basin Model. Pasting an element does not remove it from
the clipboard so you can paste the same selection into multiple Basin Models. Begin by opening the Basin
Model into which you wish to paste elements from the clipboard. Select the Arrow Tool and move the mouse
to the location where you wish to paste the element. If there are multiple elements on the clipboard then you
should place the mouse where you want the center of the element grouping to be located. Press the right
mouse button as shown below. A context menu is displayed that contains several choices including Paste.
Click the Paste Element command. The paste command is only available if there is at least one element on
the clipboard.

118 Pasting an element selection into the Basin Map
8.4.4 Cutting an Element

An element can be cut from a Basin Model and removed to the clipboard. Cutting an element places an exact
but independent copy of the element on the clipboard and then deletes it from the Basin Model. Once an
element is in the clipboard it can be pasted into the same Basin Model from which it was copied or it can be
pasted into a different model. Begin by opening the Basin Model from which you wish to cut an element.
Select the hydrologic element you wish to cut by clicking on it with the Arrow Tool. You may also select more
than one element in the map. The selected element or elements become highlighted after the selection. After
you make a selection, place the mouse over a selected element and press the right mouse button. A context
menu is displayed that contains several choices including cut. Click the Cut Element command. If more than
one element is selected in the Basin Model Map, then the Cut menu option from the Edit menu must be used.
You can now paste the selection into the same or a different Basin Model. The cut command is only
available if there is at least one element selected.
8.4.5 Renaming an Element

Rename a hydrologic element using the Components tab of the Watershed Explorer. Select the element you
wish to rename by clicking on it in the Watershed Explorer; it will become highlighted. Keep the mouse over
the selected element and click the left mouse button again. The highlighted name will change to editing
mode as shown below. You can then move the cursor with the arrow keys on the keyboard or by clicking with
can also finalize your choice by clicking elsewhere on the Components tab. If you change your mind while in
editing mode and do not want to rename the selected hydrologic element, press the Escape key.

119 Renaming an element in the Watershed Explorer
8.4.6 Renaming Multiple Elements

You can also rename individual or multiple hydrologic elements with the Rename Basin Elements menu,
accessed by right-clicking on the selected basin name in the Components tab of the Watershed Explorer.
More details on this feature can be found here22.
8.4.7 Deleting an Element

There are three ways to delete a hydrologic element. All methods for deleting an element remove it from the
Basin Model. Once an element has been deleted it cannot be retrieved or undeleted.
The first way to perform a deletion is from the Basin Model Map window. Select the hydrologic element you
wish to delete by clicking on it with the Arrow Tool. The selected element becomes highlighted after the
selection. After you make a selection, place the mouse over a selected element and press the right mouse
button. A context menu is displayed that contains several choices including Delete Element. Click the Delete
Element command. A window will open where you must confirm that you wish to delete the selected
hydrologic element. Press the OK button to delete the element or elements. If you change your mind and do
not want to delete the element selection, press the Cancel button or the X button in the upper right to return
to the Basin Model Map window.
22 https://www.hec.usace.army.mil/confluence/hmsdocs/hmsum/latest/watershed-physical-description/basin-models

120 Deleting a single element from the Basin Map
The second way to delete an element also uses the selection in the map. Select one or more elements that
you wish to delete. Press the Delete key on the keyboard. You will have to confirm your choice to delete.
The third way to delete is from the Components tab of the Watershed Explorer. Move the mouse over the
element you wish to delete and press the right mouse button as shown below. A context menu is displayed
that contains several choices including Delete. Click the Delete command. You will have to confirm your
choice to delete.
121 Deleting elements from the Watershed Explorer
8.4.8 Optional Element Properties

Several optional features are available at every hydrologic element regardless of the type of element. While
some of the features may be required for certain capabilities such as parameter estimation with
optimization, they are all optional for normal use in simulation runs. All optional features are contained in

a Component Editor that is automatically displayed along with the main element editor. Select an element in
the Watershed Explorer or the Basin Map to view its Component Editor.
A time-series discharge gage can be specified as observed flow for any hydrologic element. When used with
subbasins, the gage should generally represent the measured flow at the outlet of the subbasin. For reaches,
the gage should represent the measured flow at the downstream end of the reach. For all other elements it
should be a measured estimate of the outflow from that element. The observed flow is added to the time-
series results for the element and appears in summary tables, time-series tables, and graphs.
A time-series stage gage can be specified as observed stage for any hydrologic element. When used with
subbasins, the gage should generally represent the measured stage at the outlet of the subbasin. For
reaches the gage should represent the measured stage at the downstream end of the reach. For all other
elements it should be a measured estimate of the stage at that element. The observed stage is added to the
time-series results for the element. It is best used in combination with the elevation-discharge curve
described next.
A gage for observed Snow Water Equivalent (SWE) can be added to subbasins. This can be helpful when
calibrating simulations that include modeling the accumulation and melting of a snowpack. The observed
data can represent either measurements at a point, or may be the result of external averaging calculations
for the whole subbasin. Observed SWE is only available for subbasin elements.
A gage for observed pool elevation can be added to reservoirs. This can be helpful when calibrating
simulations. Using this data can be nearly equivalent to having observed inflow to the reservoir. Even when
observed inflow in available, the observed flow for an element should be compared to the computed outflow.
Observed pool elevation is only available for reservoir elements.
122 Element component editor for specifying option properties
The program fundamentally computes flow for each of the hydrologic elements included in a Basin Model.
An elevation-discharge curve can be specified so that stage can be computed as well. If a curve is specified,
the stage for each time step is determined by taking the computed flow and using it to interpolate elevation
from the curve. The computed stage is added to time-series results for the element and appears in summary
tables, time-series tables, and graphs.
The flow ratio is only shown for subbasin and source elements, and only if the Basin Model is set to allow
flow ratios. To enable or disable flow ratios, access the Component Editor for the Basin Model and make the
desired selection. When the ratios are enabled in the Basin Model, the flow ratio can be entered for subbasin

and source elements. The ratio is applied to the computed flow from the subbasin or source in order to
compute the final outflow.
A reference flow can be specified to assist in interpreting computed flow results. The flow is added to the
element results graph as a horizontal marker line at the specified flow value. The marker line is labeled with
the specified label. The reference flow can represent any significant flow value such as bank-full discharge,
flood watch, levee overtopping, or observed high water mark for a storm event.
8.4.9 Element Inventory

The Element Inventory provides a listing of some or all of the hydrologic elements in a Basin Model. This is
helpful for reviewing the various element names and descriptions. To access the inventory, click
the Parameters menu and select the Element Inventory command. A sample inventory is shown below. If
there is a current element selection, only the selected elements will be shown in the inventory when the
window opens; you can switch to showing all elements by using the selection control at the top of the
window. All hydrologic elements in the Basin Model will be shown if no elements are currently selected.
123 Typical element inventory for a Basin Model
8.4.10 Finding and Selecting Elements

The simplest way to find a hydrologic element in a Basin Model is to select it in the Watershed Explorer. All
of the elements in a Basin Model are shown in hydrologic order under the Basin Model icon. Click on an
element icon in the Watershed Explorer and it will become selected. The selected element is highlighted in
the Watershed Explorer and in the Basin Model Map window. More than one element may be selected at a
time but only the Component Editor for the first selected element is shown.
You can also find and select a hydrologic element in the Basin Model Map window. Begin by making sure
the Arrow Tool is selected on the toolbar. Examine the element icons in the Basin Model Map window until
you find the one you wish to select. Click on it with the arrow cursor and it will become selected. The

selected element is highlighted in the Basin Model Map window and in the Watershed Explorer. After you
make the first selection, you can add to the selection by holding the Shift key and clicking on additional
elements. You can select several elements simultaneously by using the arrow cursor to drag a box around
the desired elements. To select using a drag box, move the mouse to a blank area of the map. Hold the left
mouse button and drag the mouse. A box is drawn to show which elements will be selected when you
release the mouse button.
It can be difficult to find a specific hydrologic element in a large Basin Model with many elements. A Special
Select Tool is included that can be used to help locate a single element or a group of elements. Access the
tool by clicking the Edit menu and selecting the Select By Name command. The Select By Name window will
remain open until it is closed by pressing the Close button or the X button at the upper corner of the window.
Elements are selected in the Basin Model according to the selections on the Select Special window every
time the Apply button is pressed. There are three components to a special selection.
The first component of a special selection is the Element Name. You may enter a specific name, for example,
the name of an element appearing in an error message. You can find all elements that begin with a specific
sequence of letters by entering those letters followed by an asterisk. For example, entering sub* will find all
elements with names that start with "sub". You can also find all elements that end with a specific sequence
of letters by entering an asterisk followed by those letters. For example, entering * creek will find all
elements with names that end in "creek". Finally you can find all elements that contain a specific sequence of
letters by entering an asterisk, the letters, and ending with another asterisk. For example, entering * basin
* will find all elements with names that contain "basin". By default the "Element Name" is set to an asterisk
so that the special selection will find all element names.
The second component of a special selection takes the result of limiting by element name and further limits
it based on the Element Type. Elements will only be selected if they match the name criteria and their type is
checked on. For example, to only search among the source elements, check off all element types except
source. You may check on one, several, or all element types. The default is to search among all element
types.
124 Selecting elements by name

The third component of a special selection is the Selection Type to create. You may replace the current
selection. This means that whatever elements are found to meet the name criteria and the element type
criteria will become the selected elements. Any previously selected elements will no longer be selected. You
may alternately add to the current selection. This means the new selection will include any elements that are
currently selected plus the elements that meet the new name and element type criteria. Finally, you can
select from the current selection. In this case the name and element type criteria are further limited by only
selecting from among the elements that are already selected.
8.5 Flow Network

The Flow Network is the skeleton that connects hydrologic elements together into a representation of the
stream system in the watershed. Each link in the network is a one-way connector that takes outflow from an
element and connects it as inflow to a downstream element. The connection information of the flow network
along with the drainage area at each element is used to sort the elements in hydrologic order.
8.5.1 Moving Elements

Hydrologic elements are moved in the Basin Model Map window; they are moved the same way regardless
of whether they are connected to a downstream element. To move an element, start by selecting the Arrow
Tool from the toolbar. Next click the icon of the element you wish to move; it will become highlighted. Keep
the mouse over the element and hold the left mouse button. Drag the mouse until the element icon is in the
desired location. Release the left mouse button to finalize the move.
Reach elements are often connected between two junctions or possibly between other element types. Reach
elements must connect to the upstream and downstream element. If a reach is connected on both ends, it
can only be moved by moving the upstream or downstream element. If a reach is not connected on one end,
that free end can be moved. Click on the reach once with the mouse to select it. Move the mouse over the
free end of the reach and click again with the left mouse button. A small blue box appears at the free end.
Keep the mouse over that box and hold the left mouse button. Drag the mouse to move the free end of the
reach. Release the left mouse button to finalize the new location for that end of the reach. If a reach is not
connected on either end, the entire reach can be moved. Click on the reach once with the mouse to select it.
Keep the mouse over the reach and hold the left mouse button. Drag the mouse to move the reach to a new
location. Release the left mouse button to finalize the new reach location.
More than one element can be moved at a time. To move multiple elements, the user must select the
elements that will be moved. You may select the elements one at a time. Begin by clicking the first element.
Subsequently, hold the CTRL key and click additional elements. A selected element can be unselected by
holding the CTRL key and clicking it again. You may also select elements by dragging a box while the arrow
tool is selected. You could also select elements using the Select By Name command on the Edit menu. After
selecting all desired elements, use the arrow keys on the keyboard to move the elements. The elements will
move one distance increment each time an arrow key is pressed. The elements can be moved in smaller
distance increments by holding the CTRL key while pressing the arrow keys.
8.5.2 Connecting and Disconnecting Elements

Hydrologic elements can be connected or unconnected from the network using two different methods. The
first method uses the mouse in the Basin Model Map window. The second method is found on
the Component Editor for the element.

To connect an element in the Basin Model Map window, start by selecting the Arrow Tool from the toolbar.
Next move the mouse over the element you wish to connect to a downstream element, then press the right
mouse button. A context menu is displayed which includes the Connect Downstream command. If the
element is already connected, the command will not appear on the menu. After you click the Connect
Downstream command, the cursor will change to cross hairs as shown below. Move the mouse to position
the cross hairs over the element to which you wish to connect. Once the mouse is positioned, press the left
mouse button. A connection link will be shown between the upstream and downstream elements.
To disconnect an element in the Basin Model Map window, start by selecting the Arrow Tool from the
toolbar. Next click the icon of the element you wish to disconnect from its downstream element; the element
you click will become highlighted. Click the right mouse button to see a context menu that includes Delete
Connection. If the element is not connected, the command will not appear. After you click the Delete
Connection command, the connection link between the upstream and downstream element will be removed.
125 Preparing to connect the subbasin downstream to West Branch junction
You can also create and delete connections from the Component Editor for the element. To access
the Component Editor, click on the desired element in the Basin Model Map window, or on the Components
tab of the Watershed Explorer. The Component Editor shows the downstream element. If the element is not
connected to a downstream element, the selection list will show None as the selected element. To connect
the element currently shown in the Component Editor, select an element on the list. Only elements that could
potentially be downstream of the current element are shown. To disconnect the current element, change the
selection in the list to the None selection.

126 Selecting a downstream element using the subbasin component editor
8.5.3 Hydrologic Order

Hydrologic Order means that elements from the Basin Model are shown in order from the headwaters to the
outlet. The key properties used to determine hydrologic order are the flow network connections and drainage
area. From each element in the Basin Model it is possible for the program to automatically determine the
downstream element, and the upstream elements. These connections create the basic structure of the
network. The area entered for subbasins and sources is used to determine the drainage area for any other
downstream element in the network. While area is optional in source elements for many purposes, the
hydrologic order downstream of a source cannot be properly determined if the area is not specified. A simple
Basin Model is shown in the following figure with the corresponding Watershed Explorer shown in the
subsequent image.

127 A simple basin model for demonstrating hydrologic order
The hydrologic order shown in the Watershed Explorer is maintained automatically. Elements added to the
Basin Model are automatically sorted into correct hydrologic order. When an element is connected to the
flow network, or disconnected, the hydrologic order will be automatically updated to reflect the change. Any
changes to area for a subbasin or source element will automatically update drainage areas throughout the
flow network, and if necessary update the hydrologic order.
The hydrologic order is determined beginning from the outlet element. The outlet element is placed at the
bottom of the element list shown in the Watershed Explorer. Next the drainage areas of the elements
immediately upstream of the outlet are compared. The element with the smaller drainage area is placed
closest to the outlet, and the element with the larger drainage area is placed furthest. The process of
comparing the drainage areas of the upstream elements is then repeated element by element until all
elements have been sorted. In the case shown below, the drainage area of the Headwater 20 subbasin is
larger than the drainage area of the Headwater 10 subbasin.

128 Watershed Explorer showing hydrologic order corresponding to the elements shown i the previous figure
Some Basin Models have more than one outlet. When this is the situation, each outlet and its upstream
elements are sorted as outlined above. A second level of sorting is then carried out using the drainage area
of each outlet. The outlet with the largest drainage area appears at the bottom of the Watershed Explorer,
with its upstream elements above it. The outlet with the smallest drainage area appears at the top of
the Watershed Explorer, with its upstream elements above it.
In some situations the automatic sorting of hydrologic elements may not achieve the desired result. Manual
adjustments may be made to the order, and the adjusted order is then maintained as the new hydrologic
order. Two methods exist for making manual adjustments. The first option is to click on an element in
the Watershed Explorer so that it is selected. Next, right click on the element and choose either the Move
Up or the Move Down menu command, as shown in the figure below. The selected element will be moved up
or down one position in the element ordering. Repeated moves will be necessary in order to move the
element up or down more than one position. You may also select a contiguous block of elements and move
all of them up or down position in unison.

129 Manually moving an element in the hydrologic order using the right mouse menu
Any selected element in the Watershed Explorer can be moved several positions at once using the mouse.
Start by clicking on an element to select it. Next, carefully position the mouse over the selected element and
hold the left mouse button, and then drag the mouse. The shape of the cursor will change while you drag the
element and you will also see an insertion, as shown in the figure below. The insertion line shows where the
element will be placed when you release the mouse button. Drag the mouse up or down over the other
elements until you position the mouse where you want the element, and then release the button. The element
will be moved to the new position in the hydrologic order.

130 Manually moving an element in the hydrologic order by dragging it and dropping into position
Global Editors and Simulation Results shown throughout the program will display elements in hydrologic
order, as shown in the Watershed Explorer. Hydrologic order will be used when the editor or result is first
opened. However, each result window also includes a selection choice for switching between hydrologic
order and alphabetic order.
8.5.4 Locking Element Locations

Moving elements is an important part of creating a Basin Model. It is usually not necessary to perform
moves once all elements have been created and connected in the flow network. However, elements could be
accidentally moved small distances then they are selected depending on the user's skill with a mouse and
the sensitivity settings of the mouse hardware. You can Lock Element Locations to avoid such accidental
moves. Right click on a Basin Model node in the Watershed Explorer and choose the Lock Element
Locations menu option. Choosing this option toggles between permitting element moves and locking the
element locations to prevent moves. Once the locking is selected, it is no longer possible to move elements.
Unselect the locking option if you wish to move elements.

131 Lock element locations, icons, within the Basin Model Map
8.5.5 Locking Hydrologic Order

Sometimes the downstream connection of an element needs to be changed in the flow network. Other times
it is necessary to add an element to the Basin Model. In these cases it is helpful to have the automatic
hydrologic ordering of the elements. The remainder of the time it is not necessary to change the hydrologic
ordering. In fact, if many manual adjustments have been made to the hydrologic ordering, the ordering
should be preserved against accidental resorting or adjustment. You can lock the hydrologic order to avoid
such accidental changes.
Right click on a Basin Model node in the Watershed Explorer and choose the Lock Hydrologic Order menu
option. When the lock is disengaged, it is possible to resort the elements using the right mouse menu for the
Basin Model in the Watershed Explorer. It is also possible to make manual adjustments using the right
mouse menu for an element in the Watershed Explorer, or by dragging the element with the mouse. The
ordering will also be updated as elements are added in the Basin Model, or downstream flow connections are
changed.
When Lock Hydrologic Order is engaged, it is not possible to make any manual adjustments to the element
order. Right mouse menus and mouse dragging will be disabled. Any elements added to the Basin Model will
be put at the bottom of the element list. Elements will not move in the hydrologic order even if downstream
flow connections are changed. You will need to turn off the locking in order to make any changes.
8.6 Zones
Zones provide a way to group together elements with similar properties. The grouping could be performed
spatially so that a large watershed is subdivided with a separate zone for each tributary. Another way to
subdivide spatially is to group all subbasins between upstream and downstream gage locations.
Alternatively, the grouping could be performed parametrically so that a watershed is subdivided with a
separate zone for each type of land use. The properties used to group elements into zones are defined by the
user and may use any meaningful criteria. Zones are defined and managed as part of the Basin Model. Once
defined, the primary use of zones is for setting parameter values within the Forecast Alternative (see page 610),

described fully in a later section. In brief, during a forecast it becomes possible to set parameter values once
and have them immediately applied to all subbasins in a zone.
There are three organizational levels to the use of zones. The lowest organizational level is Individual
Elements (subbasins or reaches). The elements contain the actual parameter data and are located within the
watershed. The middle organizational level is a Zone. Each zone contains one or more elements. Elements
are grouped into zones using one of the schemes described in the previous paragraph. The highest level is
a Zone Configuration. Each zone configuration includes one or more zones. A Basin Model may include
multiple configurations.
8.6.1 Creating a New Zone Configuration

A new zone configuration is created using the Zone Configuration Manager. To access the manager, click on
the Parameters menu and select the Zone Configuration Manager command. The manager will open and
show all of the zone configurations currently in the Basin Model. The manager can remain open while you
manage the zone configurations or while you perform tasks elsewhere in the program. You can close the
manager using the X button in the upper right corner. The buttons to the right of the zone configuration list
can be used to manage existing configurations or create a new one.
132 The Zone Configuration Manager showing four configurations with schemes for grouping elements
To create a new zone configuration, press the New button. After you press the button, a window will open
where you can name and describe the new zone configuration that will be created. A default name is
provided for the new configuration; you can use the default or replace it with your own choice. A description
can also be entered. If the description is long, you can press the button to the right of the description field to
open an editor. The editor makes it easier to enter and edit long descriptions. A zone configuration may
contain subbasin or reach elements, but it cannot contain both types of elements. Other types of elements
cannot be included in a zone configuration. Select the type of element that will be included in the zone
configuration. When you are satisfied with the name, description, and element type, press the Create button
to finish the process of creating the new zone configuration. You cannot press the Create button if no name
is specified for the new configuration. If you change your mind and do not want to create a new zone

configuration, press the Cancel button or the X button in the upper right to return to the Zone Configuration
Manager window.
133 Creating a new zone configuration
8.6.2 Copying a Zone Configuration

Copy a zone configuration using the Zone Configuration Manager, which is accessed from
the Parameters menu. Select the zone configuration you wish to copy by clicking on it in the list of current
configurations. The selected configuration is highlighted after you select it. After you select a configuration
you can press the Copy button on the right side of the window. A new Copy Zone Configuration window will
open where you can name and describe the copy that will be created. A default name is provided for the
the name and description, press the Copy button to finish the process of copying the selected Basin Model.
You cannot press the Copy button if no name is specified. If you change your mind and do not want to copy
the selected zone configuration, press the Cancel button or the X button in the upper right to return to
the Zone Configuration Manager window.
134 Creating a copy of a zone configuration
8.6.3 Renaming a Zone Configuration

Rename a zone configuration using the Zone Configuration Manager, which is accessed from
the Parameters menu. Select the zone configuration you wish to rename by clicking on it in the list of current
configurations. The selected configuration is highlighted after you select it. After you select a configuration

you can press the Rename button on the right side of the window. A new Rename Zone
Configuration window will open where you can provide the new name. If you wish you can also change the
description at the same time. If the new description will be long, you can use the button to the right of the
the Rename button to finish the process of renaming the selected zone configuration. You cannot press
zone configuration, press the Cancel button or the X button in the upper right of the Rename Zone
Configuration window to return to the Zone Configuration Manager window.
135 Renaming a zone configuration
8.6.4 Deleting a Zone Configuration

Delete a zone configuration using the Zone Configuration Manager, which is accessed from
the Parameters menu. Select the zone configuration you wish to delete by clicking on it in the list of current
configurations. The selected configuration is highlighted after you select it. Press the Delete button on the
right side of the window to delete the selected zone configuration. A window will open where you must
confirm that you wish to delete the selected configuration. Press the OK button to delete the configuration. If
you change your mind and do not want to delete the selected zone configuration, press the Cancel button or
the X button in the upper right to return to the Zone Configuration Manager window.

136 Preparing to delete a zone configuration from the Zone Configuration Manager
8.6.5 Creating a Zone in a Configuration

Create a new zone from the Zones window, accessed directly from the Zone Configuration Manager. To
begin, open the zone configuration manager by clicking on the Parameters menu and selecting the Zone
Configuration Manager command. Next select the zone configuration to which you will add a new zone by
clicking on the configuration in the list of available configurations. The selected zone configuration is
highlighted after you click on it. After you select a zone configuration you can press the Zones button to open
the Zones window. Finally, press the New button in the Zones window to begin creating a new zone.

137 Managing the zones in a zone configuration
After you press the button, a window will open where you can name and describe the new zone that will be
added to the selected zone configuration. A default name is provided for the new zone; you can use the
default or replace it with your own choice. A description can also be entered. If the description is long, you
can press the button to the right of the description field to open an editor. The editor makes it easier to enter
and edit long descriptions. When you are satisfied with the name and description, press the Create button to
finish the process of creating the new zone. You cannot press the Create button if no name is specified for
the new zone. If you change your mind and do not want to create a new zone, press the Cancel button or
the X button in the upper right to return to the Zones window.
138 Creating a new zone
8.6.6 Renaming a Zone in a Configuration

Rename a zone from the Zones window, accessed directly from the Zone Configuration Manager. To begin,
open the Zone Configuration Manager by clicking on the Parameters menu and selecting the Zone
Configuration Manager command. Next select the zone configuration that contains the zone you wish to

rename by clicking on the configuration in the list of available configurations. The selected zone
configuration is highlighted after you click on it. After you select a zone configuration you can press
the Zones button to open the Zones window. Finally, select the zone you wish to rename by clicking on it in
the list of zones and then press the Rename button on the right side of the Zones window.
A new Rename Zone window will open where you can provide the new name. If you wish you can also
change the description at the same time. If the new description will be long, you can use the button to the
right of the description field to open an editor. When you are satisfied with the name and description, press
the Rename button to finish the process of renaming the selected zone. You cannot press the Rename
button if no name is specified. If you change your mind and do not want to rename the selected zone, press
the Cancel button or the X button in the upper right of the Rename Zone window to return to
the Zones window.
139 Renaming a zone
8.6.6.1 Deleting a Zone from a configuration

Delete a zone from the Zones window, accessed directly from the Zone Configuration Manager. To begin,
open the Zone Configuration Manager by clicking on the Parameters menu and selecting the Zone
Configuration Manager command. Next select the zone configuration that contains the zone you wish to
delete by clicking on the configuration in the list of available configurations. The selected zone configuration
is highlighted after you click on it. After you select a zone configuration you can press the Zones button to
open the Zones window. Finally, select the zone you wish to delete by clicking on it in the list of zones and
then press the Delete button on the right side of the Zones window, as shown below. A window will open
where you must confirm that you wish to delete the selected zone. Press the OK button to delete the zone. If
you change your mind and do not want to delete the selected zone, press the Cancel button or the X button in
the upper right to return to the Zones window.

140 Preparing to delete a zone from a zone configuration
8.6.6.2 Adding Elements to a Zone

Add an element to a zone using the Elements window, accessed directly from the Zone Configuration
Manager. To begin, open the zone configuration manager by clicking on the Parameters menu and select
the Zone Configuration Manager command. Next select the zone configuration that contains the zone to
which elements will be added. Click on the configuration in the list of available configurations to select it.
The selected zone configuration is highlighted after you click on it. After you select a zone configuration you
can press the Elements button to open the Elements window.
The left side of the Elements window shows all elements that have not been assigned to a zone. The Zones
Selector at the upper right of the window can be used to switch between zones in the selected zone
configuration. You must select the zone to which you wish to add elements. The right side of
the Elements window shows all elements that have been added to the selected zone.

141 Elements are added to the selected zone by pressing the Add button
There are two ways to add an element to the selected zone. The first way is to click on an unassigned
element in the left side of the Elements window. You may hold the CTRL key and click on additional elements
to add more than one element at a time. The selected elements are highlighted after clicking. Press
the Add button to add the selected elements to the selected zone.
The second way to add an element to the selected zone is to double-click it in the list of unassigned
elements. When an element is double-clicked, it will be added to the currently selected zone and removed
from the list of unassigned elements.
8.6.6.3 Removing Elements from a Zone

Remove an element from a zone using the Elements window, accessed directly from the Zone Configuration
Manager. To begin, open the Zone Configuration Manager by clicking on the Parameters menu and select
the Zone Configuration Manager command. Next select the zone configuration that contains the zone from
which elements will be removed. Click on the configuration in the list of available configurations to select it.
The selected zone configuration is highlighted after you click on it. After you select a zone configuration you
can press the Elements button to open the Elements window.

142 Elements are returned from the selected zone to the unassigned elements by pressing the Remove button
The right side of the Elements window shows all elements that have been assigned to a zone. The Zones
Selector at the upper right of the window can be used to switch between zones in the selected zone
configuration. You must select the zone from which you wish to remove elements. The left side of
the Elements window shows all elements have not been assigned to a zone.
There are two ways to remove an element from the selected zone. The first way is to click on an element in
the right side of the Elements window. You may hold the CTRL key and click on additional elements to
remove more than one element at a time. The selected elements are highlighted after clicking. Press
the Remove button to return the selected elements to the list of unassigned elements.
The second way to remove an element from the selected zone is to double-click it in the list of zone
elements. When an element is double-clicked, it will be removed from the currently selected zone and placed
on the list of unassigned elements.
8.6.6.4 Selecting a Current Zone Configuration

A zone configuration can be selected to be active in the Basin Model Map window, global editors, and results
accessed through the map. There are two ways to select the current zone configuration. The first way is to
click on the Parameters menu and select a zone configuration with the Select Zone
Configuration command. The command shows all zone configurations that have been established in the
Basin Model. The Select Zone Configuration command indicates the selected configuration with a check
mark.

The second way to select the current zone configuration is with the selection box on the toolbar. The
selection box shows all zone configurations that have been established in the Basin Model. Use the selection
box to choose a zone configuration.
143 Assigning the subbasin to the selected zone in the current zone configuration
Elements can be added to a zone or moved between zones using the Basin Model Map window once a
current zone configuration is selected. To assign or change the assignment of an element, click on the
element in the Basin Model Map window using the right mouse button. The Assign To Zone command
shows the zones available for assignment. If the element is not assigned to a zone, it will be assigned to the
selected zone. If the element is already assigned, it will be automatically removed from its current zone and
assigned to the newly selected zone. Elements assigned to a zone through the map must be assigned one at
a time.
Global Editors include additional features when there is a current zone configuration. As shown below, the
Global Editor can display all elements in the Basin Model or can be switched to display only the elements in a
zone of the current zone configuration. All of the zones are shown in the selection list with a prefix of Z:
indicating status as a zone. Additional selection items may also be included on the list and are shown with a
different prefix.

144 Viewing the parameter data for subbasins assigned to the zone in the Global Editor
The Global Summary Table also includes additional features when there is a current zone configuration. The
Global Summary Table can display all elements in the Basin Model or can be switched to display elements in
a particular zone. All of the zones are shown in the selection list with a prefix of Z: indicating status as a
zone. Additional selection items may also be included on the list and are shown with a different prefix.
145 Viewing the results for subbasins assigned to a selected zone in the Global Summary Table

8.7 Computation Points

Elements in the Basin Model can be designated as Computation Points. Generally, only elements with
observed flow, observed stage, or other observed data are designated as computation points. Computation
points are designed primarily for use with Simulation Runs23 and Forecast Alternatives24. When used with a
simulation run, the features of a computation point are a customizable editor that uses slider bars to adjust
parameters upstream of the computation point, and result graphs with customizable time-series selection.
Results from the simulation run are automatically recomputed as the slider bars are adjusted and the result
graphs update dynamically. When used with forecast alternatives, the principal feature of a computation
point is to make upstream to downstream calibration more efficient.
8.7.1 Selecting Computation Points

Any element in the Basin Model can be selected as a computation point, and there is no limit to the number
of computation points permitted. Usually an element is only designated as a computation point if it includes
observed data that can aid in calibration. However, observed data is not absolutely necessary.
There are two ways to select an element as a computation point. The first way is to click on the element in
the Basin Model Map window using the right mouse button. Choose the Select Computation Point command
to select the element as a computation point. It is only possible to select the element as a computation point
if it is not already selected. An element selected as a computation point shows a small red circle added to
the icon in the Basin Model Map window and also in the Watershed Explorer.
23 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/Simulation+Runs
24 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/.Forecast+Alternatives+v4.4

146 Setting a junction to be a computation point by right-clicking in the Basin Model Map
The second way to select an element as a computation point is by using the Computation Point
Manager window. To access the manager, click on the Parameters menu and choose the Computation Point
Manager command. The manager shows all of the elements that have been selected as computation points.
Press the Select Elements button to begin the process of selecting an element as a computation point.

147 The Computation Point Manager
The Select Elements window includes a selection list for choosing the type of element to display in the
selection table. The selection table shows the element name and description for all elements in the Basin
Model that match the selected element type. By default, only elements with observed data are shown in the
table, but all elements can be shown by using the option in the upper right of the window. To select an
element as a computation point, click on the row in the table and press the Select button. You cannot make a
selection unless a row in the table is selected; the selected row in the table is highlighted. Press
the Close button when you are done selecting elements and you will return to the Computation Point
Manager window.
148 Selecting elements to be computation points

8.7.2 Unselecting Computation Points

There are two ways to unselect an element so that it is no longer a computation point. The first way is to
click on the element in the Basin Model Map window using the right mouse button. Choose the Unselect
Computation Point command to indicate the element will no longer be a computation point. It is only
possible to unselect the element if it is already selected as a computation point. The small red circle added
to the element icon in the Basin Model Map window and also in the Watershed Explorer will be removed to
indicate the element is no longer a computation point.
149 Setting a junction to no longer be a computation point by right- clicking in the Basin Model Map
The second way to unselect an element as a computation point is by using the Computation Point
Select the element that will discontinue as a computation point; the selected element is highlighted in the
list. Press the Unselect Element button to undesignate the selected element as a computation point.

150 Unselecting an element as a computation point using the Computation Point Manager
8.7.3 Selecting Calibration Parameters

Each computation point includes a customizable editor to aid in calibration of a simulation run. The editor
can be customized by selecting the parameters it will contain. The parameters selected for the editor must
be in the elements upstream of the computation point. If the computation point is a subbasin or reach
element, then parameters at that element may also be selected. If there is an upstream computation point,
then the selected parameters must be at elements between the two computation points. Parameters
selected at one computation point will be automatically transferred if a new computation point is selected
upstream.
The process of selecting parameters for the customizable editor at a computation point begins on
the Computation Point Manager window. To access the manager, click on the Parameters menu and choose
the Computation Point Manager command.

151 Preparing to select parameters for the customizable editor at a selected computation point
The manager shows all of the elements that have been selected as computation points. Select the
computation point where you wish to add parameters; the selected computation point is highlighted in the
list. Press the Parameters button open the Parameter Management window and then press
the Select button to begin selecting the parameters for the computation point.

152 The Parameters Management window shows all the parameters for a computation point selected in the Computation Point
Manager
The Select Parameters window is used to choose the parameters to add to a computation point. Each of the
subbasin and reach elements upstream of the computation point are shown in a list on the left side of the
window. The element selected as the computation point is also shown in the list if the element is a subbasin
or reach. Click on an element in the list on the left side of the window; the selected element is highlighted.
The right side of the window will be updated to show all of the parameters at the selected element that can
be chosen for the customizable editor. More than one parameter can be selected simultaneously by holding
the CTRL key and clicking on several parameters. Press the Select button when you have selected the
parameters you wish to add. Selected parameters are removed from the list of available parameters. You can
choose parameters from additional elements by clicking on each element in the list on the left side of the
window and selecting parameters from that element. When you are finished selecting parameters for the
computation point, press the Close button to return to the Parameters window.

153 Selecting parameters for a computation point from those available at a subbasin element
8.7.4 Unselecting Calibration Parameters

Begin unselecting parameters from the customizable editor at a computation point using the
the Computation Point Manager window. To access the manager, click on the Parameters menu and choose
the Computation Point Manager command. The manager shows all of the elements that have been selected
as computation points. Select the computation point where you wish to remove parameters; the selected
computation point is highlighted in the list. Press the Parameters button to begin removing parameters from
the computation point.
The Parameters window shows all parameters that have been selected at the computation point. The left
column in the table shows the name of the element and the right column in the table shows the parameter.
The parameter is specified with the name of the method followed by the name of the parameter. In the
example shown below, the first row in the table represents the Conductivity parameter in the Green
Ampt loss rate method of subbasin Lower Pecan Cr. Click a row in the table to select it; the selected row is
highlighted. Press the Remove button to remove the parameter from the computation point. You may
unselect more than one parameter at a time by holding the CTRL key and clicking on multiple rows in the
table. Press the Close button when you have finished unselecting parameters and you will return to
the Computation Point Manager window.

154 Unselecting parameters from a computation point
8.7.5 Settings for Calibration Parameters

The parameters in the customizable editor are represented with slider bars. The slider can be used to quickly
change each parameter value in the range from a minimum value to a maximum value. By default the
minimum and maximum values cover a very wide range. You can change the minimum and maximum values
for each parameter to narrow the adjustment range to be suitable for a particular subbasin or reach in a
watershed.
Change parameter settings for the customizable editor at a computation point using the Computation Point
Select the computation point where you wish to make the parameter settings; the selected computation
point is highlighted in the list. Press the Parameter Settings button to begin editing the parameter settings
for the computation point.
The Parameter Settings window shows all of the parameters selected at a computation point. Each row in
the table displays settings information for one parameter. The first column specifies the name of the
element. The second column specifies the name of the method followed by the name of the parameter. The
third column specifies the units of the parameter. In the example shown below, the first row in the table
represents the Standard Lag parameter in the Snyder transform method of subbasin Lower Pecan Cr. The
units of the parameter are HR which represents hours. You may specify the minimum and maximum value
for the parameter in the final two columns of the table. While the parameter may take on values less than the
minimum or greater than the maximum, the slider bar in the customizable editor for the computation point
will only be able to adjust the parameter value within the range specified in the table.

155 Changing the minimum and maximum parameter values in the customizable editor at a computation point
8.7.6 Computation Point Results

A computation point may optionally include up to five customized result graphs. You may specify which
time-series results appear in each graph. The results selected for a graph must be in the elements upstream
of the computation point, or at the computation point itself. If there is an upstream computation point, then
the selected parameters must be at elements between the two computation points. Any of the various time-
series computed at an element may be included in a graph. The results in the graphs will automatically
update as soon as adjustments are made to parameter values using the customizable editor at the
computation point.
Configure results at a computation point using the the Computation Point Manager window. To access the
manager, click on the Parameters menu and choose the Computation Point Manager command. The
manager shows all of the elements that have been selected as computation points. Select the computation
point where you wish to configure result graphs; the selected computation point is highlighted in the list.
Press the Results button to begin configuring the results for the computation point. The Results window
opens and allows you to configure the results for up to five graphs. The selector in the upper left allows you
to choose which graph to configure; you may select any of the five graphs. The table in the center of the
window shows all of the results for the selected graph. The element name and the result name are shown for
each result added to the graph.

156 Selected results for the first graph at a selected computation point
Add a result to a graph by pressing the Select button in the Results window. The Select Time-Series window
opens for choosing one or more results to add to the current graph selection. The left side of the window
shows the computation point element and all elements upstream of it. Select the element that produces the
result that you wish to add to the graph. Select the element by clicking on it with the mouse; the selected
element is highlighted in the list. Only one element can be selected at a time. All of the available time-series
for the selected element are shown on the right side. Select the time-series result you wish to add to the
graph by clicking on it and then pressing the Select button. You can add multiple time-series results
simultaneously by holding the CTRL key and clicking on more than one result. All selected time-series are
added to the graph when the Select button is pressed. Time-series results are not shown in the list if they
have already been added to the graph. Press the Close button when you are done selecting results and wish
to return to the Results window.

157 Selecting the outflow time-series from a subbasin element for addition to a result graph at a computation point
Remove a selected time-series result from a graph directly on the Results window. Select the result you wish
to remove by clicking it with the mouse; the selected result is highlighted in the list. You may select multiple
results simultaneously by holding the CTRL key and clicking additional results. Press the Unselect button to
remove the time-series results from the current graph selection.

158 Removing a time-series result from a graph at a computation point
8.8 References: Watershed Physical Description

Autodesk, Inc. 2005. "AutoCAD 2006 Customization Guidebook." San Rafael, CA.
Barnes Jr., Harry H. 1967. "Roughness Characteristics of Natural Channels." U.S. Geological Survey, Denver,
CO.
Environmental Systems Research Institute, Inc. July 1998. "ESRI Shapefile Technical Description." Redlands,
CA.
U.S. Geological Survey. September 1999. "Standards for Digital Line Graphs: Part 2 Specifications."
Department of the Interior, Washington, DC.

9 Geographic Information
This section describes the tools available in HEC-HMS for dealing with models that have spatial information.
This includes spatial references for hydrologic elements and tools for delineating a watershed from a digital
elevation model. Most of these tools are found in the GIS menu, but may also be encountered in other
places.
9.1 GIS Menu

Various GIS tools are available under the GIS menu (shown below). Many of these tools are not activated
until other requirements are met; often this requirement is to have used other tools in this menu. For
watershed delineation functions, the menu serves as a roadmap: the workflow proceeds from top to bottom
in order.
159 GIS tools available in the GIS Menu
Geographic Information – 245

9.1.1 Coordinate System

This tool allows you to set or view the coordinate system for a Basin Model. If a Basin Model is selected and
it has a coordinate system assigned, selecting GIS | Coordinate System will show the current coordinate
system (shown below).
160 Viewing a basin model's coordinate system.
If a Basin Model is selected and no coordinate system has been assigned yet, selecting GIS | Coordinate
System will prompt you to choose a coordinate system for the spatial referencing of the Basin Model. First,
you will see a blank Coordinate System Selection prompt (shown below). Here you can choose to use a
predefined coordinate system if you select the Predefined button. You may also choose to browse to GIS
data that have a coordinate system reference and select it, extracting its coordinate system definition by
pressing Browse. Finally, you may copy and paste an OGC WKT definition for a coordinate system in the text
field. You may cancel the procedure by pressing Cancel. Once the text has been populated in the text field
using either the predefined, existing GIS data or copied OGC WKT, you can set the basin coordinate system
using the Set button.

161 Basin model coordinate system selection dialog.
HEC-HMS provides two predefined coordinate systems: Standard Hydrologic Grid (SHG) and Universal
Transverse Mercator (UTM). Choosing the Predefined setting produces a selection dialog with two options
(shown below).
162 Predefined coordinate systems.
Using SHG requires no additional information. Using UTM requires the UTM zone, hemisphere, and datum to
be specified (shown below). After setting the necessary options, pressing the Select button will populate the
coordinate system selection dialog text field with the appropriate information. Pressing Cancel or the X will
cancel the process.

163 UTM specification.
Using the Browse option allows you to navigate to any GIS data with a coordinate system specification (e.g.
shape file, raster data, .prj file, etc.) and select it so that HEC-HMS can extract its coordinate system
specification (shown below).
164 Browsing to a GIS data file that has a coordinate system specification.
Alternatively, you may enter the coordinate system specification in the text field using an OGC WKT format.
All three of these options will result in text in the text field (shown below). Once the coordinate system is
specified in that text field, pressing Set will set the coordinate system for that Basin Model.

165 Coordinate system specification in the definition text field.
9.1.2 Terrain Reconditioning

This tool will be available only if the following conditions are met:
• You have selected a Basin Model
• The Basin Model has a terrain data component assigned to it
Selecting GIS | Terrain Reconditioning will launch a two-step wizard that guides you through the process of
building walls and/or burning streams in your elevation dataset. For the majority of use cases, the terrain
reconditioning step can be skipped altogether as many watersheds will delineate accurately with the base
terrain data that is assigned to the Basin Model. However, if the relief of your watershed is extremely flat or if
you want to ensure that your HMS watershed delineations will exactly match published data such as
hydrologic units found within the USGS's Watershed Boundary Dataset (WBD) or subbasin boundaries from a
prior study, the build walls step within the terrain reconditioning tool can be very useful. The burn streams
step is helpful if you want to impose a stream network onto a terrain dataset in order to improve channel
definition. The figures below compare a base terrain dataset (left) and a HEC-HMS reconditioned dataset
with sharply raised walls and a smoothly dropped channel (right).

166 Base terrain dataset
167 HEC-HMS reconditioned dataset
The first step of the wizard allows you to build walls in the terrain. If you only desire to burn streams, you can
skip to the second step of the wizard by clicking the Next button. A shapefile with watershed boundaries
must be selected in order to build walls. A Smooth Raise Cell Buffer and Height and/or a Sharp Raise Height
must be entered. If your goal is to force the HMS watershed delineations to match the input shapefile, a
general recommendation is to enter a Smooth Raise Cell Buffer of 1 or 2 and a Smooth Raise height of 100
or more. The Smooth Raise Cell Buffer and height will gradually raise the elevations of all terrain cells that
fall within the specified buffer. The cell elevations that touch the shapefile watershed boundaries will be
raised to match the Smooth Raise height input and the surrounding cells within the buffer will be raised a
lesser amount so that there is a gradual transition to the elevations of the cells that fall outside of the

buffered area. For this reason, large cell buffers may result in long runtimes. A Sharp Raise Height will raise
only the single line of cell elevations that touch the shapefile watershed boundaries (no buffering operation
is performed). If both a Smooth Raise height and Sharp Raise Height are entered, the algorithm will first build
a gradual wall within the buffer that matches the Smooth Raise height and then it will raise the single line of
unbuffered wall cells an additional amount that matches the Sharp Raise Height. The vertical units of the
Smooth Raise and Sharp Raise Heights will match the vertical units of the terrain data component assigned
to the Basin Model. If negative heights are entered, the algorithm will dig trenches instead of building walls.
168 Step to build walls
The second step of the wizard allows you to burn streams into the terrain. If you only desire to build walls,
you can skip the second step by clicking the Finish button; however, when building walls, it is generally
recommended to add a streamline shapefile on the second step as it will be used to breach the walls at
intersections and allow for proper drainage (see next paragraph for more information). A shapefile with
stream delineations must be selected in order to burn streams. As with build walls, a Smooth Drop Cell
Buffer and Height and/or a Sharp Drop Height must be entered. One potential scenario when burning
streams might be useful is in a 2D rain-on-grid analysis. If the terrain data does not sufficiently capture the
stream network, then a shapefile with the desired stream delineations can be selected and burned into the
terrain using the Smooth Drop Cell Buffer and Height. This will gradually lower the elevations of all terrain
cells that fall within the buffer. The cell elevations that touch the stream shapefile polylines will be lowered to
match the Smooth Drop Height input and the surrounding cells within the buffer will be lowered a lesser
amount so that there is a gradual transition from the center of the stream to the overbank outside of the
buffered area. For this reason, large cell buffers may result in long runtimes. This is especially true if your
terrain resolution is fine and your stream network shapefile is very detailed. If both a Smooth Drop Height
and Sharp Drop Height are entered, the algorithm will first burn a gradually deepening stream within the
buffer that matches the Smooth Drop Height and then it will drop the unbuffered stream cells an additional
amount that matches the Sharp Drop Height. The vertical units of the Smooth Drop and Sharp Drop Heights
will match the vertical units of the terrain data component assigned to the Basin Model. If negative heights
are entered, the algorithm will raise stream elevations instead of lowering them.

169 Step to burn streams
If both build walls and burn streams inputs are entered into the Terrain Reconditioning wizard, then the burn
inputs will override the build inputs at places where they intersect. In other words, the burning of streams will
breach the walls near intersections as seen in the figure below. This breaching operation ensures that all
cells within the reconditioned terrain drain properly. The Smooth Drop Cell Buffer input is used to determine
the width of the wall breach. A buffer input of 0 results in a breach width of one cell whereas larger buffer
inputs result in larger breach widths at intersections. If you desire to build walls that are breached but do not
wish to burn streams, simply input a burn streams filename but leave the other burn streams inputs at 0.

170 Example of walls built in the Basin Map
The figures below serve to highlight how the Smooth Drop and Sharp Drop parameters are applied when
burning streams. The orange, hatched line represents a cross-section of a channel and the black dot
represents the input burn streams shapefile. The gridded line of squares represents the resolution of the
terrain data raster file. The Smooth Raise and Sharp Raise parameters are applied in the same way when
building walls except that the terrain is raised instead of dropped.
171 Burning streams with a Smooth Drop

172 Burning streams with a Sharp Drop
173 Burning Streams with a Smooth and Sharp Drop
The Terrain Reconditioning Tool is sufficient for many typical build/burn operations. If complex build/burn
operations are needed, it is recommended to use external GIS software to edit the terrain prior to importing
into HEC-HMS.
9.1.3 Preprocess Sinks

Selecting GIS | Preprocess Sinks will run a pit removal algorithm on the terrain data assigned to the selected
Basin Model and produce a new, hydrologically-corrected DEM and a raster indicating the location of sinks

and the depth they were filled. These two new rasters are added to the Map Layers list as Sink Fill and Sink
Locations, respectively.
If you run the Terrain Reconditioning command first, this algorithm will use the reconditioned DEM with the
wall and/or stream features. Otherwise, it will use the default dataset provided by the terrain data
component.
If the terrain data assigned to the Basin Model is a hydrologically-corrected DEM, then this step is not
necessary.
When the tool is run on large terrain datasets, it may produce an indefinite progress bar such as the one
shown below. The indefinite progress bars purpose is to indicate progress, without estimating the time to
completion.
174 Indefinite progress bar for the Preprocess Sinks step.
9.1.4 Preprocess Drainage

Selecting GIS | Preprocess Drainage will run an algorithm to determine the flow direction and flow
accumulation for each grid cell in the terrain data raster. If you run the Preprocess Sinks command first, this
algorithm will use the hydrologically-corrected DEM. If not, it will use the default elevation dataset provided
by the terrain data component or, if available, the reconditioned elevation dataset. Both of the resulting
rasters are added to the Map Layers list as Flow Direction and Flow Accumulation, respectively.
shown below.

175 Indefinite progress bar for the Preprocess Drainage step.
9.1.5 Identify Streams

• The Preprocess Drainage tool has been run
Selecting GIS | Identify Streams for the first time on a Basin Model will produce a prompt that requires you to
enter the drainage accumulation threshold that will define where a stream starts, as shown below. A default
is provided based on the resolution of the raster, but may produce too fine (or too coarse) of a threshold for
your intended delineation. The value you enter will be the approximate drainage area for the subbasin
elements that result.
176 Identify Streams prompt.
shown below.

177 Indefinite progress bar for the Identify Streams step.
If you have previously run the Identify Streams tool and you run it again, you will see the prompt
shown below.
178 Dialog on Identify Streams re-run.
9.1.6 Break Points Manager

• The Identify Streams tool has been run
The Break Points Manager (shown below) will allow you to view, rename, delete or modify the description of
any break points defined in the Basin Model. By default, a Basin Model does not contain any break points. At
least one break point, defining a watershed outlet, is necessary in order to perform a watershed delineation.
Additional break points will force delineation of a subbasin element at that location.

179 Break Points Manager.
Break points are created using the Break Point Creation Tool in the Components Toolbar (shown below).
180 Location of the Break Point Creation Tool in the Components toolbar.
Selecting the Break Point Creation Tool and clicking in the Basin Model Map Window will produce a prompt (
shown below) that asks for the name of the break point, as well as an optional description. If the text box is
left blank, or the name is invalid, the Create button will not be available. Break points are shown on the basin
map as red circles.
181 Break point creation prompt.
9.1.7 Delineate Elements



• The Identify Streams tool has been run
• At least one break point has been defined
Selecting GIS | Delineate Elements for the first time on a Basin Model will produce a prompt that requires
you to enter some naming scheme and delineation options (shown below). The Subbasin Prefix, Reach
Prefix, and Junction Prefix options are text strings that prepend the automatic numbering scheme for the
elements created in delineation. For example, if you enter S_ as the Subbasin Prefix, the subbasins created in
the delineation process will be named S_1, S_2, and so on. The Insert Junctions option will automatically
insert junctions above reaches when reaches are created in the delineation procedure. The Convert Break
Points option will make any locations where there are break points, computation points in the Basin Model.
The most downstream break point, which serves as a watershed outlet, will cause creation of a sink element
at that location.
182 Delineate Elements Options.
shown below.
183 Indefinite progress bar for the Identify Streams step.

The Delineate Elements tool can be re-run on a Basin Model, for example if you change the threshold for
the Identify Streams tool and wish to re-delineate, or have made other changes to the Basin Model and wish
to revert. When it is re-run, the Delineate Elements Options prompt (shown below) will appear, giving you an
opportunity to change delineation options. If you run the tool with an existing delineation, you will see a
dialog that indicates that a new delineation will delete an old one (shown in the following figure). Selecting
Continue will delete existing elements and re-delineate.
184 Confirmation prompt for deleting elements created by a previous delineation.
9.1.8 Split Elements

• The Delineate Elements tool has been run
• Exactly one subbasin or reach element has been selected
Selecting GIS | Split Elements will allow you to choose where to divide a subbasin or reach element into two
smaller elements.
9.1.9 Merge Elements

• The Delineate Elements tool has been run
Selecting GIS | Merge Elements will allow you to choose to combine subbasin or reach elements into one
larger element. HEC-HMS will not check to make sure that combining the elements makes hydrologic
"sense"; it will only ensure that the elements are adjacent and share a common outlet point. It is up to the
user to ensure that merging the selected elements makes sense. The result of running the tool is a single
element where there were previously two or more with a new element name.
9.1.10 Reverse Flow Direction

Using the GIS | Reverse Flow Direction tool will swap the upstream and downstream endpoints of a reach
element, effectively reversing the direction that the reach flows. It will affect the downstream element for the

reach, as well as any elements that flow downstream into the reach. It is typically used in cases where
imported elements flow in the incorrect direction.
9.1.11 Georeference Existing Elements

The Georeference Existing Elements option is used to add GIS features to existing subbasin, reservoir, and
reach elements. ESRI Shape Files are the GIS file format required for importing GIS features. The shape files
must contain a name attribute that the user selects when importing the GIS features into a Basin Model. A
coordinate system must be defined for the Basin Model prior to georeferencing elements.
The Georeference Existing Elements wizard is similar to the Import Georeferenced Elements25 wizard, there
are three steps for the user to select the element type, GIS file (shape file), and the name attribute within the
shape file. The Georeference Existing Elements option will result in GIS features for only those elements
already in the Basin Model model that have a name matching the name in the GIS layer's attribute table.
The Georeference Existing Elements option is useful for HEC-HMS projects created with earlier versions of
the software that only have element icons for subbasins, reaches, and reservoirs. It is an options for adding
more of a GIS look and feel to the Basin Model Map.
Geometric data in the ESRI Shape Files is matched to the elements using the Element Name. The element
name is specified when creating the element in the Basin Model Map Window. The geometric data must
have the same element name when georeferencing existing elements. As mentioned above, the element
name of the geometric data is specified using the Name field property in the DBF file (the user can choose
the attribute field containing the feature names when importing GIS features). The example project river
bend includes GIS features for the subbasin elements. The example project can be installed from
the Help menu; select the Install Sample Projects menu command.
9.1.12 Import Georeferenced Elements

The Import Georeferenced Elements option is used to add new elements to the Basin Model, while also
adding GIS features for the new elements. ESRI Shape Files are the GIS file format required for importing GIS
features. The shape files must contain a name attribute that the user selects when importing the GIS
features into a Basin Model. A coordinate system must be defined for the Basin Model prior to importing
georeferenced elements.
After the coordinate system has been defined, GIS features can be imported for existing elements, or new
elements can be added using GIS features. The figure below shows step 1 of 3 for the Import Georeferenced
Elements wizard. This wizard will import new HEC-HMS elements into the Basin Model. As stated in the
import wizard, polygon and line information are imported when the subbasin, reach, or reservoir elements are
added to the Basin Model Map. Step 1 requires the user to select the Element Type to import. The available
options are Subbasin, Reach, and Reservoir. Once the element type is selected, click the Next button.
25 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/.GIS+Menu+v4.4#id-.GISMenuv4.4-ImportGeoreferencedElements

185 Step 1 of the Import Georeferenced Elements wizard.
The figure below shows the second step of the Import Georeferenced Elements wizard. The user must
choose a shape file. Click the browse button and navigate to a directory with the shape file and choose the
appropriate file, choose the file with an extension of .shp. Click the Next button to go to step three.

The figure below shows the third step of the Import Georeferenced Elements wizard. The user must choose
a text field within the shape file's attribute table. Select the appropriate name field and click
the Finish button. The program will import the elements in the shape file while also adding GIS features for
those new element.
9.1.13 Export Layers

After completing some (or all) of the GIS workflow steps on the GIS menu, you may wish to export some of
the resulting geospatial features for use outside of HEC-HMS. Several features can be exported as a
shapefile using the GIS | Export Layers tool. When selecting the tool, you first will be prompted to select the
layer type that you wish to export (shown below). Pressing Cancel will exit the export wizard. Pressing Next
will take you to the second step of the process, exporting the selected element type.

188 Selecting a Layer Type to export
Note: if you wish to export junctions, you may want to use the Snap to Downstream tool first. This tool can
be accessed by right-clicking on the Basin Model Map and selecting Junctions | Snap to Downstream. If
junction elements have a reach as a downstream connection, this tool will ensure that they are snapped to
the nearest end of the reach.
Exported features will be in ESRI shapefile format, and you need to specify the destination file path and name
using the text field or browser on the second step of the wizard (shown below). If you select Back you can re-
choose which element type you would like to export. Cancel will exit the wizard. Finish will create the
exported shapefile in the specified location.
189 Specifying the destination file path for exporting layers
9.1.14 Compute Grid Cells

The program will automatically compute the subbasin Discretization when the Structured Discretization
Method is selected (see Selecting a Discretization Method (see page 283)). The terrain preprocessing step must

have been completed and the flow direction grid created before attempting to run GIS | Compute | Create
Grid Cells. The structured grid can be displayed in the Basin Model Map by checking the Discretization layer
in the Map Layers editor.
190 Setting the Discretization layer to be displayed via the Map Layers editor
9.1.15 Create Grid Cell File

A Grid Cell File can be used to apply gridded precipitation to a Basin Model, or when using any of the gridded
methods in the Meteorologic Model. A grid cell file can also be used by the ModClark transform method and
any of the gridded loss methods. There is a option to create a grid cell file from the GIS menu. The grid cell
file should only be created after delineating subbasin and reach elements, and updating element names with
names that are appropriate for the study. The grid cell file must be re-created if any of the subbasin names
are modified. The grid cell file option is no longer the preferred option for discretizing subbasin elements,
either the Structured or Unstructured Discretization Methods should be used.
The figure below shows the first editor in the Create a Grid Cell File wizard that is opened by clicking GIS |
Compute | Create Grid Cell File. The user must select the grid projection first, the options include Standard
Hydrologic Grid (SHG) or one of the UTM projections. The user must also select the grid resolution from a
drop down list. The grid resolution must match the resolution of all gridded meteorologic data-sets and any
parameter grids. The figure below shows the second editor in the Create a Grid Cell File wizard. The user
must select a file location and name for the grid cell file. By default, the file extension is *.mod. When clicking
the Finish button, the program will create the user specified grid, intersect the grid with the subbasin

boundaries, and create a text file containing the grid cells within each subbasin, their area, and their travel
length. The travel length is computed using the flow direction grid. The program computes an area weighted
travel length for each of the SHG or UTM grid cells.
191 Step 1 of creating a grid cell file

192 Step 2 of creating a grid cell file
9.2 Basin Characteristics
9.2.1 Subbasin Characteristics

Geospatial Subbasin Characteristics can be computed within HEC-HMS. To compute subbasin
characteristics, the Basin Model must have georeferenced subbasins and the GIS | Preprocess Sinks step,
the GIS | Preprocess Drainage step, and the GIS | Identify Streams step should be computed beforehand.
The Subbasin Characteristics view can be accessed from the Parameters | Characteristics menu. The first
time the Subbasin Characteristics view is accessed, statistics are computed on-the-fly.

193 Selecting the Subbasin Characteristics
The subbasin characteristics computed include:

• Longest flowpath length
• Longest flowpath slope
• Centroidal flowpath length
• Centroidal flowpath slope
• 10-85 flowpath length
• 10-85 slope
• Basin slope
• Basin relief
• Relief ratio
• Elongation Ratio
• Drainage Density
It is important to note that the subbasin characteristics calculations are based on the original terrain data
associated with the Basin Model. The calculations are NOT based on output that may exist from the GIS |
Terrain Reconditioning step in HMS (build walls / burn streams). Full descriptions for each characteristic are
provided below.
The image below illustrates the subbasin characteristics view for a Basin Model.

194 Subbasin Characteristics view
Subbasin characteristics can be recalculated using the Re-compute button in the lower-left corner of the
dialog. The user has the option to override the computed characteristic values by manually editing the table
values and clicking Apply to save the changes.
9.2.1.1 Longest Flowpath (L)

The Longest Flowpath extends from the subbasin outlet to the most hydraulically-remote point upstream.
Longest flowpath is significant in that it is typically used to determine the time of concentration for a
watershed.
9.2.1.2 Centroidal Flowpath (Lca)

The Centroidal Flowpath is a subset of longest flowpath. It begins at the subbasin outlet and extends
upstream along the longest flowpath until it reaches the point along the longest flowpath that is nearest to
the subbasin centroid. A comparison of centroidal flowpath and longest flowpath can be seen in the image
below.

195 Illustrations of a Centroidal Flowpath and Longest Flow Path
9.2.1.3 10-85 Flowpath (L10-85, S10-85)

The 10-85 Flowpath is also a subset of longest flowpath. Measuring from the outlet in the upstream
direction, the 10-85 flowpath begins at a point representing ten percent of the total length of the longest
flowpath and ends at a point representing eighty-five percent of the total length. Both the length and the
slope of the 10-85 flowpath are provided in the subbasin statistics table, shown above. The 10-85 slope is
often more representative of flowpath slopes as a whole within the watershed as it is not affected by the
more extreme upstream elevations of the longest flowpath that are typically found near the watershed divide.
A comparison of 10-85 flowpath and longest flowpath can be observed in the image below.

196 Illustrations of a 10-85 Flowpath and Longest Flowpath
9.2.1.4 Basin Slope (S)

The Basin Slope represents the average slope of the entire subbasin (rise/run). For each elevation raster
value within the subbasin, the algorithm scans the surrounding eight neighbors and computes the slope
using the maximum scanned elevation difference. The algorithm does not weigh north, east, south, and west
neighbors more than diagonal neighbors; each neighbor is considered equally. The basin slope output is the
average of all the computed slope values in the subbasin.
9.2.1.5 Basin Relief (R)

Basin Relief represents the elevation difference between the highest point on the drainage divide and the
outlet point of the subbasin.

9.2.1.6 Relief Ratio (RR)

The Relief Ratio is simply the basin relief divided by the length of the longest flowpath.
9.2.1.7 Elongation Ratio (El)

The Elongation Ratio is a dimensionless ratio used to categorize the general shape of a subbasin. It is a ratio
between the diameter of a circle with the same area as the subbasin and the basin length. Elongation ratio
values typically range from ~0.2 to 1.0, with lower values representing elongated basins and values close to
1 representing circular basins.
The HEC-HMS algorithm utilizes the length of the longest flowpath for the BasinLength variable in the above
equation.
9.2.1.8 Drainage Density (DD)

Drainage Density is a metric used to describe the efficiency in which a subbasin is drained by stream
channels. It is computed by summing the total length of stream channels within the subbasin and then
dividing by the area of the subbasin. It is important to note that drainage density that is calculated by HEC-
HMS is dependent on the stream threshold used when defining a stream network.
9.2.2 Reach Characteristics

In addition to subbasin characteristics, characteristics can also be computed for reach elements within HEC-
HMS. As with subbasin characteristics, this functionality can be accessed from the Parameters |
Characteristics menu. The Reach Characteristics calculators are capable of computing reach slope, reach
sinuosity, and reach relief. The calculated results can be viewed in tabular format.
The image below illustrates the Reach Characteristics view for the MiddleColumbia_WY1997 Basin Model.
197 Reach Characteristics view

9.2.2.1 Reach Slope

The Reach Slope is calculated using the most upstream point of a reach and the most downstream point of
a reach (rise/run). The tabular result is presented in standard slope format and not as a percent slope.
9.2.2.2 Reach Sinuosity

Reach Sinuosity is generally defined as the ratio of actual stream length to valley length. It is a descriptive
measure that quantifies the degree to which a channel meanders. If the reach is perfectly straight, the reach
sinuosity value will be 1. The higher the sinuosity value, the more the reach meanders and deviates from a
straight path. The algorithm estimates valley length by computing the straight line length from the most
upstream point of the reach and the most downstream point of the reach as demonstrated in the figure
below.

198 Illustrating the Straight Line Length used for computing the Reach Sinuosity
9.2.2.3 Reach Relief

Reach Relief represents the elevation difference between the most upstream point of a reach and its most
downstream point.

9.3 Parameter Estimation

Geospatial data is increasingly abundant in the earth science community and many hydrologic modeling
parameters can be estimated from such data. An Expression Calculator is included in HEC-HMS to facilitate
parameter estimation from GIS data. The Expression Calculator can be launched from basin global editors.
Because many of the calculation options incorporate GIS processing, the Basin Model must include
georeferenced subbasin elements for the Calculate button to be enabled.
The Expression Calculator is launched from the Calculator button of a Global Editor.
199 Loaded Expression Calculator
Select the Parameter that you wish to calculate from the Field dropdown box in the Expression Calculator
dialog. The selected parameter will appear above the Expression window as the left side of an mathematical
expression as <Selected Parameter> =. In the Expression Calculator, grids and characteristics can be used as
variables. In the Grids tab, you will see a list of user-imported gridded data. Double-click the desired Grid
variable to add it the Expression window. When a grid is included in the expression, a zonal average value of
the feature on the grid within the element is used in the calculation.
In the image below, a Percolation Rate grid has been included in the expression to estimate the Constant
Rate parameter.

200 Using the Expression Calculator for estimating the Constant Rate parameter
The Stats tab displays a list of variables based on the physical characteristics of your watershed's subbasin
or reach elements. When a characteristic is used in the expression, the characteristic value for a given
feature (subbasin or reach element) is used in the calculation. Double click on a variable to add it to the
Expression window.
In the image below, the Longest Flowpath Length has been included in the expression to estimate the Time
of Concentration parameter.

201 Using the Expression calculator to estimate the Time of Concentration parameter
Internal model variables for subbasin and reach elements are shown in the table below. Units (U.S.
Customary or Metric) for the Stats variables correspond to the selection of the basin model's Unit System in
the Component Editor.
Stats Variables for Units Stats Variables for Units

Subbasins Reaches
Area MI2 or KM2 Reach Length MI or KM
Longest Flowpath MI or KM Reach Slope FT/MI, M/KM or

Length dimensionless
Longest Flowpath Slope FT/MI, M/KM or Reach Relief FT or M

dimensionless
Centroidal Flowpath FT/MI, M/KM or

Slope dimensionless
10-85 Flowpath Length MI or KM

Stats Variables for Units Stats Variables for Units

Subbasins Reaches
10-85 Flowpath Slope FT/MI, M/KM or

dimensionless
Basin Slope FT/MI, M/KM or

dimensionless
Basin Relief FT or M
Drainage Density MI/MI2 or KM/KM2
Elongation Ratio dimensionless
Relief Ratio FT/MI, M/KM or

dimensionless
23 Internal model variables for subbasin and reach elements
The Functions window displays a list of Visual Basic (VBA) math functions that you can use in your
expression. Below the functions window is a row of arithmetic operator buttons including multiplication (*),
division (/), addition (+), subtraction (-) and string concatenation (&). You can use Grid variables, Stat
variables, VBA functions, and the mathematical operators in a single expression to calculate an element's
parameter value. Once the expression is complete. Click Calculate. The value of the selected parameter will
be updated in the Global Editor Dialog.
The number of significant figures reported by the Expression Calculator can be controlled in Tools | Program
Settings on the Compute tab. The program setting is called Expression Calculator Precision. The valid range
for the setting is 1 to 5 significant figures. The program uses a default value of 3 unless modified by the user.

202 Setting the Expression Calculator Precision
9.4 Coordinate Reference Systems
9.4.1 SHG Grid System
203 The Standard Hydrologic Grid (SHG)

The Standard Hydrologic Grid (SHG) is a variable-resolution square-celled map grid defined for the
conterminous United States. The coordinate system of the grid is based on the Albers Equal-Area Conic Map
Projection with the following parameters.
Units: Meters
Datum: North American Datum, 1983 (NAD83)
1st Standard Parallel: 29º 30’ 0” North
2nd Standard Parallel: 45º 30’ 0” North
Central Meridian: 96º 0’ 0” West
Latitude of Origin: 23º 0’ 0” North
False Easting: 0.0
False Northing: 0.0
Users of the grid can select a resolution suitable for the scale and scope of the study for which it is being
used. For general-purpose hydrologic modeling with NEXRAD radar precipitation data, HEC recommends
2000-meter cells, and HEC computer programs that use the SHG for calculation will select this cell size as a
default. HEC will also support the following grid resolutions: 10,000-meter, 5,000-meter, 1,000-meter, 500-
meter, 200-meter, 100-meter, fifty-meter, twenty-meter, ten-meter. The grids resulting from the different
resolutions will be referred to as SHG two-kilometer, SHG one-kilometer, SHG 500-meter and so on. The
corresponding DSS A-parts are SHG2K, SHG1K, SHG500, SHG100, SHG50, SHG20, and SHG10. A grid
identified as SHG with no cell-size indication will be assumed to have two-kilometer cells.
For identification, each cell in the grid has a pair of integer indices (i, j) indicating the position, by cell count,
of its southwest (or minimum-x, minimum-y) corner, relative to the grid’s origin at 96ºW, 23ºN. For example
the southwest corner of cell (121,346) in the SHG two-kilometer grid is located at an easting of 242000 meter
and a northing of 692000 meter. To find the indices of the cell in which a point is located, find the point’s
easting and northing in the projected coordinate system defined above, and calculates the indices with the
following formulas.
Where floor(x) is the largest integer less than or equal to x.
9.4.1.1 Example
As examples of cell identification in the SHG system, indices of cells containing points in the western US and
the eastern US will be given in the one-kilometer, two-kilometer, and 500-meter SHG grids.
Western United States: The location 121º 45′ west, 38º 35′ north (near Davis, California) projects to
-2185019 meter easting, 2063359 meter northing, in the specified Albers projection. In the SHG two-
kilometer system the indices of the cell containing this point are:
Eastern United States: The location 76º 30′ west, 42º 25′ north (near Ithaca, New York) projects to 1583506
meter easting, 2320477 meter northing, in the specified Albers projection. In the SHG two-kilometer system
the indices of the cell containing this point are:

In the SHG one-kilometer grid the indices are (1583, 2320), and in SHG 500-meter the indices are (3167,
4640).
9.4.2 Standardized UTM Grid System

The HRAP and SHG systems are undefined outside the conterminous US. To make practical applications of
gridded computations in HEC-HMS outside of the CONUS region easier, HEC has developed a grid system
based on UTM coordinates, using the cell-numbering conventions of SHG. When using the UTM grid, you
must select a UTM zone (including the selection of northern or southern hemisphere) and cell size.
Units: Meters
Datum: World Geodetic System (WGS84)
Projected Coordinate System: Universal Transverse Mercator (UTM)
Zones: 1-60, North(N) or South(S)
204 Island of Madagascar, UTM 38S, cells are 100 km square for illustration
As with SHG, users of the grid can select a resolution suitable for the scale and scope of the study for which
it is being used. HEC will support the following grid resolutions: 10,000-meter, 5,000-meter, 2,000-meter,
1,000-meter, 500-meter, 200-meter, 100-meter, fifty-meter, twenty-meter, ten-meter.
For identification, each cell in the grid has a pair of integer indices (i, j) indicating the position, by cell count,
of its southwest (or minimum-x, minimum-y) corner, relative to the UTM zone coordinate origin. For example
the southwest corner of cell (233, 4077) in a UTM two-kilometer grid is located at an easting of 466000
meters and a northing of 8154000 meters. To find the indices of the cell in which a point is located, find the
point’s easting and northing in the projected coordinate system defined above, and calculates the indices
with the following formulas.
where floor(x) is the largest integer less than or equal to x.

9.4.2.1 Example
As examples of cell identification in a UTM spatial reference system, indices of cells containing points on the
west and east coasts will be given in two-kilometer grids based on UTM zone 38S.
West coast: The location 43º 15′ 25" east, 22º 3′ 27" north (near the westernmost point of the island)
projects to 320132 meters easting, 755978 meters northing, in the UTM zone 38 south. In a two-kilometer
system the indices of the cell containing this point are:
East coast: The location 50º 31′ 49" east, 15º 20′ 11" south (near the easternmost point of the island)
projects to 449580 meters easting, 8304412 meters northing, in UTM zone 38 south. In a two-kilometer
system the indices of the cell containing this point are:
Note that a point at this longitude and latitude falls within the bounds of UTM zone 39 south. However, for
this example it is assumed that one grid is being produced for precipitation over the whole island, so the
coordinate are calculated for the easternmost zone (39 south) within the bounds of the grid.

10 Subbasin Elements
A Subbasin is an element that usually has no inflow and only one outflow. It is one of only two ways to
produce flow in the Basin Model. Outflow is computed from meteorologic data by subtracting losses,
transforming excess precipitation, and adding baseflow. Optionally the user can choose to include a canopy
component to represent interception and evapotranspiration. It is also optional to include a surface
component to represent water caught in surface depression storage. The subbasin can be used to model a
wide range of catchment sizes.
10.1 Selecting a Discretization Method

The Discretization Method defines how a subbasin is discretized. Traditionally, the Mod Clark grid cell file
has been used to define the spatially-discrete elements of a subbasin. One limitation of the Mod Clark grid
cell file is that it does not use absolute spatial references. Grid cell locations are referenced from an arbitrary
lower left corner. Structured and Unstructured Discretizations provide spatial-awareness to spatially-
discrete Subbasin Elements. Advantages of the spatially-aware approach include the ability to view discrete
elements, the ability to sample values from other geospatial data, and the ability to visualize results for
discrete elements.
There are four types of discretization: Structured, Unstructured, File-Specified, and None. The 2D Diffusion
Wave and Mod Clark transform methods are inherently gridded, and require a gridded discretization;
therefore, the Discretization Method can not be None when one of these methods are selected. Whenever a
gridded Canopy, Surface, or Loss Method is used, a gridded discretization must be provided.
10.1.1 None Discretization

The None Discretization represents the entire subbasin as one discrete element within the larger modeling
context. This configuration is commonly referred to as a "lumped-parameter". The reality is that all
discretization approaches do some amount of spatial-averaging. The amount of spatial-averaging depends
on the extent of discrete elements.
The following image shows the None Discretization selected. If the None Discretization is selected, there is
no Discretization tab in the Subbasin Element's component editor.
Subbasin Elements – 283

205 Selecting the None Discretization Method
10.1.2 Structured Discretization

The Structured Discretization creates a Cartesian grid within the bounds of the subbasin. The Structured
Discretization gives options for Standard Hydrologic Grid (SHG) or Universal Transverse Mercator (UTM)
projection and 50, 100, 200, 500, 1000, 2000, 5000, or 10000 meter grid cell sizes.
The following image shows a Structured Discretization that uses the SHG projection and a 2000 meter cell
size.
206 A Structured Discretization using SHG projection and a 2000 meter cell size

Spatial elements for a Structured Discretization are stored in a SpatiaLite database. The database is
identified by the File specification in the Component Editor. The database file is managed by HEC-HMS and
the file location shown in the Component Editor cannot be modified by the user. The spatial elements are
stored in a layer named discretization in the SpatiaLite database.
The Projection defines the projected coordinate system of the grid cells. There are options for SHG and UTM
zones 1-60, north and south.
The Grid Cell Size defines the grid cell size to be used in the discretization. There are options for 50, 100,
200, 500, 1000, 2000, 5000, or 10000 meter grid cell sizes.
After selecting a new Structured Discretization definition, the grid cells can be computed from the GIS |
Compute | Grid Cells menu option.
The Punxsutawney Basin Model shown below uses an SHG projection with a 1000 meter grid cell size for the
lower subbasin and a 2000 meter grid cell size for the upper subbasins.
207 Punxsutawney Basin Model
10.1.3 Unstructured Discretization

Unstructured Discretizations can have any coordinate reference system and the grid can be unstructured.
Unstructured grids can be imported from an HEC-RAS Unsteady Plan HDF file (using HEC-RAS version 5.0.7
or newer). The plan file has an extension of ".p##.hdf", where "p##" corresponds to the specific plan of
interest. Unstructured grids are most commonly used with the 2D Diffusion Wave transform method.
The following image shows an Unstructured Discretization.

208 Unstructured Discretization selected in the subbasin element component editor
Spatial elements for a Unstructured Discretization are stored in a HDF5 file. The backing file format for an
Unstructured Discretization is an HDF5 file with an identical schema to HEC-RAS, such that files are
interoperable. Once imported, the HDF file is managed by HEC-HMS and the file location shown in the
component editor can not be modified by the user.
The Number of Connections is the number of connections to or from the unstructured discretization.
Connections are created during import and currently can not be modified by the user.
The image below illustrates an Unstructured Discretization.
10.1.4 File-Specified Discretization

File-Specified Discretizations were introduced to support the traditional Mod Clark grid cell file, but also
support valid Structured Discretization and Unstructured Discretization files. When a File-Specified
Discretization is used, the path to a grid-defining file is provided by the user.

The following image shows a Mod Clark grid cell file specified in the File-Specified Discretization editor.
209 Specifying a Mod Clark grid cell file in the File-Specified Discretization editor
Mod Clark grid cell files can be created from the GIS | Compute | Grid Cell File menu option. For more on the
format, see Grid Cell File Format (see page 815).
The following image shows a valid Unstructured Discretization HDF file specified in the File-Specified
Discretization editor.
210 An Unstructured Discretization HDF file specified in the File-Specified Discretization editor
If a Structured or Unstructured Discretization has already been computed, the File-Specified option allows
users to rapidly change the Discretization definition without creating a new Basin Model.
10.1.5 Viewing the Discretization Layer

The spatial features display for Structured and Unstructured Discretizations can be toggled on or off in the
Map Layers (see page 68) dialog, shown below.
211 Toggling on or off the Discretization layer

10.1.6 Global Editing

Global editors can be used to quickly edit information for all subbasins and reaches instead of editing
individual element Component Editors. Discretizations can be edited globally from the Parameters |
Discretization menu.
The following image shows the global editor for a Basin Model where all subbasins are set to use the SHG
Structured Discretization.
212 Subbasins set to use the SHG Structured Discretization
10.2 Selecting a Canopy Method

The Canopy is one of the components that can be included in the Subbasin Element and can represent the
presence of plants in the landscape. Plants intercept precipitation, reducing the amount of precipitation that
arrives at the ground surface. Intercepted water evaporates between storm events. Plants also extract water
from the soil in a process called transpiration. Evaporation and transpiration are often combined as evapo-

transpiration. Selecting a Canopy Method is optional but should be used for continuous simulation
applications.
The Canopy Method for a subbasin is selected on the Component Editor for the Subbasin Element as shown
in the following figure. Access the Component Editor by clicking the Subbasin Element icon on the
Components tab of the Watershed Explorer. You can also access the Component Editor by clicking on the
element icon in the Basin Map, if the map is currently open. You can select a Canopy Method from the list of
four available choices. If you choose the None method, the subbasin will not compute any interception or
evapo-transpiration and all precipitation will be assumed as direct precipitation on the ground surface, and
subject to interception by the surface, and infiltration into the soil. Use the selection list to choose the
method you wish to use. Each subbasin may use a different method or several subbasins may use the same
method.
213 The Canopy Method is selected in the Subbasin Component editor
When a new subbasin is created, it is automatically set to use the default Canopy Method specified in the
Program Settings. You may change the Canopy Method for a subbasin at any time using the Component
Editor for the Subbasin Element. Since a subbasin can only use one Canopy Method at a time, you will be
warned when changing methods that the old parameter data will be lost. You can turn off this warning in the
Program Settings. You can change the Canopy Method for several subbasins simultaneously. Click on the
Parameters menu and select the Canopy Þ Change Method command. The Canopy Method you choose will
be applied to the selected subbasins in the Basin Model, or to all subbasins if none are currently selected.
The parameters for each Canopy Method are presented on a separate Component Editor from the Subbasin
Element editor. The Canopy editor is always shown next to the Subbasin editor. If the Kinematic Wave
Transform Method is selected, there may be two Canopy editors, one for each runoff plane. The information
shown on the canopy editor will depend on which method is currently selected.

10.2.1 Dynamic Canopy

This method includes an interception Storage Capacity and a Crop Coefficient that change in time. The
storage capacity specifies the amount of water that can be held in the canopy before precipitation begins
falling through to the ground surface. No through-fall will occur until the canopy storage is full. The canopy
will use all potential evapo-transpiration until the storage is emptied. The potential evapotranspiration is
multiplied by the crop coefficient to determine the amount of evapotranspiration from canopy storage and
later the surface and soil components. Only after the canopy storage has been emptied will unused potential
evapotranspiration be used by the surface and soil components. The Component Editor is shown below.
214 Dynamic Canopy Method editor
The initial condition of the canopy should be specified as the Percentage of the Canopy Storage that is full
of water at the beginning of the simulation. There is currently only one method for specifying the storage
capacity of the canopy. The storage is specified as a fixed effective depth of water that can be held in the
canopy before additional precipitation falls through to the ground surface. The storage depth does not
change for the duration of the simulation.
There are two methods for specifying the Crop Coefficient. A time-series may be used to specify how the
crop coefficient changes during the plant growing season. The coefficient must be defined as a gage in the
gage manager before it can be selected. You may use a chooser to select the gage by pressing the Gage
button next to the selection list. You will not be able to select a gage if no gages have been created in the
Time-Series Data Manager. Alternately, a grid may be used to specify how the crop coefficient changes at
each grid cell during the growing season. The crop coefficient grid must be selected from the grids that have
been previously defined in the Grid Data Manager.
The canopy can be set to only evaporate water from storage and extract water from the soil during dry time
periods with no precipitation (Only Dry Periods). Version 4.1 of the program and all previous versions only

performed evapotranspiration calculations during dry periods. Alternately, the canopy can be set to
evaporate water from storage and extract water from the soil during both dry and wet periods (Wet and Dry
Periods). The choice for simultaneous precipitation and evapotranspiration can improve results when using
a long time interval or during a snowmelt simulation.
There are two methods for extraction of water from the soil. The Simple method extracts water at the
potential evapo-transpiration rate, and can be used with the Deficit Constant or Soil Moisture Accounting
Loss Rate Methods. The Tension Reduction method extracts water at the potential evapo-transpiration rate
from the gravity zone but reduces the rate when extracting from the tension zone; it can only be used with
the Soil Moisture Accounting Loss Rate Method.
10.2.2 Gridded Simple Canopy

This method implements the Simple Canopy Method on a grid cell basis. Each grid cell has separate
parameter values, and separate precipitation. The Component Editor is shown below.
215 Gridded simple canopy method editor
of water at the beginning of the simulation. The same percentage will be applied to every grid cell.
The Canopy Storage Grid must be selected from the grids that have been previously defined in the Grid Data
Manager. The grid should specify the maximum canopy storage in each grid cell; the storage is constant for
the duration of a simulation. You may use a chooser to select the grid by pressing the Grid button next to the
selection list. You will not be able to select a grid if no grids have been created in the Grid Data Manager.
The Crop Coefficient Grid must be selected from the grids that have been previously defined in the Grid Data
Manager. The grid should specify the ratio of the potential evapo-transpiration computed in the Meteorologic
Model that should be applied in each grid cell; the coefficient is constant for the duration of a simulation. You
may use a chooser to select the grid by pressing the Grid button next to the selection list. You will not be able
to select a grid if no grids have been created in the Grid Data Manager.
periods with no precipitation. Version 4.1 of the program and all previous versions only performed
evapotranspiration calculations during dry periods. Alternately the canopy can be set to evaporate water
from storage and extract water from the soil during both dry and wet periods. The choice for simultaneous
precipitation and evapotranspiration can improve results when using a long time interval or during a
snowmelt simulation.

Loss Rate Methods. The Tension Reduction method extracts water at the potential evapo-transpiration rate
from the gravity zone but reduces the rate when extracting from the tension zone; it can only be used with
the Soil Moisture Accounting Loss Rate Method.
10.2.3 Simple Canopy

This method is a simple representation of a plant canopy. All precipitation is intercepted until the canopy
storage capacity is filled. Once the storage is filled, all further precipitation falls to the surface, or directly to
the soil if no representation of the surface is included. All potential evapotranspiration will be used to empty
the canopy storage until the water in storage has been eliminated. The potential evapotranspiration is
multiplied by the crop coefficient to determine the amount of evapotranspiration from canopy storage and
later the surface and soil components. Only after the canopy storage has been emptied will unused potential
evapotranspiration be used by the surface and soil components. The Component Editor is shown below.
216 Simple canopy method editor
of water at the beginning of the simulation.
Canopy Storage represents the maximum amount of water that can be held on leaves before through-fall to
the surface begins. The amount of storage is specified as an effective depth of water.
The Crop Coefficient is a ratio applied to the potential evapo-transpiration (computed in the Meteorologic
Model) when computing the amount of water to actually extract from the soil.
periods with no precipitation. Version 4.1 of the program and all previous versions only performed

evapotranspiration calculations during dry periods. Alternately the canopy can be set to evaporate water
from storage and extract water from the soil during both dry and wet periods. The choice for simultaneous
precipitation and evapotranspiration can improve results when using a long time interval or during a
snowmelt simulation.
Loss Rate Methods. The Tension Reduction method can be used with the Soil Moisture Accounting Method
and extracts water at the potential evapo-transpiration rate from the gravity zone but reduces the rate when
extracting from the tension zone. No water is extracted from the soil unless the Simple or Tension Reduction
method is selected.
10.3 Selecting a Snowmelt Method

Precipitation generally occurs as snow when the air temperature over the land surface is below the freezing
point. In general the snow will accumulate on the land surface so long as the air temperature remains below
the freezing point. In some watersheds it is part of the annual hydrologic cycle that snowfall accumulates in
a snowpack during the winter months. Snowpacks are not static but undergo continual ice crystal
transformations in response to diurnal temperature fluctuations. Ablation or melting of the snowpack occurs
when atmospheric conditions transfer energy sufficient to raise the temperature of the snowpack to the
freezing point, and then transform the snow to liquid water through the heat of fusion for ice. The most
common way to measure the water content of the snowpack is by the Snow Water Equivalent or SWE. The
SWE is the depth of water that results from melting a unit column of the snowpack.
The Snow Method included in the Basin Model is only necessary when the air temperature may be below the
freezing point during a simulation, or a snowpack may exist at the beginning of a simulation. Currently the
only option available is a Temperature Index approach that includes a conceptual representation of the
snowpack energy. It computes the liquid water available at the soil surface which is then subject to
infiltration and surface runoff.
10.3.1 Gridded Temperature Index

The Gridded Temperature Index Method is the same as the Regular Temperature Index Method except the
equations for simulating the snowpack are computed separately for each grid cell with separate precipitation
and temperature boundary conditions instead of area-averaged values over the whole subbasin. This method
can only be used if gridded precipitation and temperature are also used. The gridded temperature index
method can only be used with the ModClark and 2D Diffusion Wave transform methods.
The Gridded Temperature Index Method includes a Component Editor with snow pack initial conditions and
temperature index parameters for an individual subbasin element. You can open a global temperature index
editor from the Parameters | Snowmelt menu.

217 Gridded Temperature Index Component Editor

10.3.1.1 Initial Values

The Initial Values can be specified with gridsets, or can be initialized to default values. All cells in each
subbasin are set to the same default value when the Default Values option is chosen. The default values are:
• Initial SWE of 0 mm
• Initial Cold Content of 0 mm
• Initial Liquid of 0%
• Initial Cold Content ATI of 0° C
• Initial Meltrate ATI of 0 DegC-day
Five parameter grids must be selected when the Parameter Grids option is selected; the grids are described
in the following paragraphs.
The Initial Snow Water Equivalent that exists at the beginning of the simulation must be entered. This
information is usually determined by interpolating from actual measurements of snow water equivalent. This
value can be set to zero if there is no snow.
The Initial Cold Content that exists at the beginning of the simulation must be entered. It represents the heat
required to raise the temperature of the snow pack to 0° C (32° F) and is expressed as a number equivalent
to mm (inches) of frozen water. If there is no snow at the beginning of the simulation, it can be set to zero. If
there is a snowpack, it can be estimated as the depth of snow multiplied by the snow density multiplied by
the heat capacity of snow multiplied by the number of degrees below the freezing point.
The Liquid Water Held Within the Snowpack at the beginning of the simulation must be entered. Liquid water
can persist in the snow only if the snowpack temperature is at 0° C (32°F). There are few conditions when
this value can be exactly known. One case is when there is no snowpack and it can be set to zero. A second
case is when the air temperature has been continually below freezing for several days and it can be set to
zero.
The Initial Cold Content Antecedent Temperature Index is an index to the snow temperature near the
surface of the snowpack. It should be set to the approximate snowpack temperature at the beginning of the
simulation. If the initial temperature is not known, it can be set to 0° C (32° F).
The seasonal variation of meltrate is indexed by an Antecedent Temperature Function. The initial meltrate
ATI should be thought of as similar to "the accumulated thawing degree days." This antecedent temperature
function allows the melt rate to change as the snowpack matures and ages. If there is no snow on the
ground at the start of the simulation this term can be set to zero. It can also be set to zero if the simulation is
starting during or at the end of a cold period when air temperatures were continually below the base
temperature. Otherwise it must be calculated as the accumulation of degree-days since the last period of
sustained air temperature below freezing.
10.3.1.2 Parameter Values

The PX Temperature is used to discriminate between precipitation falling as rain or snow. When the air
temperature is less than the specified temperature, any precipitation is assumed to be snow. When the air
temperature is above the specified temperature, any precipitation is assumed to be rain. This discrimination
temperature may be up to 1° C.
The difference between the base temperature and the air temperature defines the Temperature Index used
in calculating snowmelt. The meltrate is multiplied by the difference between the air temperature and the
base temperature to estimate the snowmelt amount. If the air temperature is less than the base temperature,
then the amount of melt is zero. Typically, the base temperature should be 0° C.

The Wet Meltrate is used during time intervals when precipitation is falling as rain, and the rainfall rate is
greater than the rain rate limit. It represents the rate at which the snowpack melts when it is raining on the
snowpack.
There are two options for specifying the Wet Meltrate:
1. Constant Value. A constant value is used to calculate meltrate.

2. Annual Pattern. A meltrate pattern may be specified that defines the wet meltrate as a function of the
time of year. The pattern must be specified separately in the Paired Data Manager before it can be
used in the Snow Melt Method. The Paired Data Type should be Parameter Value Pattern with
parameter Wet Melt Rate.
The Rain Rate Limit discriminates between dry melt and wet melt. The wet meltrate is applied as the
meltrate when it is raining at rates greater than the rain rate limit. If the rain rate is less than the rain rate
limit, the meltrate is computed as if there were no precipitation. The default value of 0 mm/day is used if no
value is entered, meaning that even a trace of precipitation results in the use of the wet melt rate.
A meltrate must be calculated for time intervals when the precipitation rate is less than the rain rate limit.
The calculation starts with the meltrate antecedent temperature index. A coefficient is used to update the
antecedent meltrate index from one time interval to the next. The default value of 0.98 is used if no value is
entered.
There are three options for specifying the Dry Melt Rate:
1. ATI-Meltrate Function. An antecedent temperature index meltrate function is used to calculate a

meltrate from the current meltrate index. The function must be specified separately in the Paired
Data Manager before it can be used in the Snow Melt Method. The function should define
appropriate meltrates to use over the range of meltrate index values that will be encountered during a
simulation. The melt rate for dry conditions typically ranges from 1 to 4 mm/degC-day.
2. Annual Pattern. A meltrate pattern may be specified that defines the dry meltrate as a function of the
time of year. The pattern must be specified separately in the Paired Data Manager before is can be
parameter Dry Melt Rate.
3. Constant value. A constant value is used to calculate meltrate.
The Cold Limit accounts for the rapid changes in temperature that the snowpack undergoes during high
precipitation rates. When the precipitation rate exceeds the specified cold limit, the antecedent cold content
index is set to the temperature of the precipitation. If the temperature is above the base temperature, the
cold content index is set to the base temperature. If the temperature is below the base temperature, the cold
content index is set to the actual temperature. If the precipitation rate is less than the cold limit, the cold
content index is computed as an antecedent index. The default value of 0 mm/day is used if no value is
entered, meaning that even a trace of snowfall will reset the cold content.
The Cold Content Antecedent Temperature Index Coefficient is used to update the antecedent cold content
index from one time interval to the next. This is a separate index from the one used to update the meltrate
index. A default value of 0.5 is used if no value is entered.
An Antecedent Temperature Index Cold Content Function is used to calculate a cold content from the
current cold content index. The function must be specified separately in the Paired Data Manager before it
can be used in the Snow Melt Method. The function should define appropriate cold contents to use over the
range of cold content index values that will be encountered during a simulation. The cold rate typically
ranges from 1.22 to 1.32 mm/degC-day.

The Maximum Liquid Water Capacity specifies the amount of melted water that must accumulate in the
snowpack before liquid water becomes available at the soil surface for infiltration or runoff. Typically, the
maximum liquid water held in the snowpack is on the order of 3%-5% of the snow water equivalent, although
it can be higher. Liquid water can persist in the snow only if the snowpack temperature is at 0° C; at which
point the cold content is zero. The maximum is entered as a percentage of the snow water equivalent.
Heat from the Ground can cause snowmelt, especially if the snowpack accumulates on ground that is only
partially frozen or completely unfrozen. In these cases the warm ground is insulated by the snowpack. Heat
from the warm ground will cause the bottom of the snowpack to melt. Two methods are available for
specifying the melting of the snowpack due to contact with unfrozen ground:
1. A Fixed Value can be entered; the same amount of melt is computed for the snowpack regardless of
atmospheric conditions above the pack or the time of year.
2. An Annual Pattern can alternately be entered; the pattern specifies the meltrate due to contact with
the ground as a function of the time of year. The pattern must be entered in the Paired Data
Manager before is can be used in the Snowmelt Method. The Paired Data Type should be Parameter
Value Pattern with parameter Ground Melt Rate.
10.3.1.3 Required Meteorologic Model Boundary Conditions

In addition to the Subbasin parameters, a Gridded Air Temperature boundary condition must be supplied by
the Meteorologic Model to use this method.
10.3.2 Temperature Index

The Temperature Index Method is an extension of the degree-day approach to modeling a snowpack. A
typical approach to the degree day is to have a fixed amount of snowmelt for each degree above freezing.
This method includes a conceptual representation of the cold energy stored in the pack along with a limited
memory of past conditions and other factors to compute the amount of melt for each degree above freezing.
As the snowpack internal conditions and atmospheric conditions change, the melt coefficient also changes.
The Temperature Index Method includes a Component Editor with parameter data. Each subbasin must
have at least one elevation band and may have up to ten elevation bands. A separate Component Editor is
included for each elevation band. A Component Editor for the elevation band temperature index method is
shown below.

218 Elevation Band Temperature Index Component Editor

Each subbasin is broken into one or more Elevation Bands; each band has its own parameter data. One
elevation band may be used to represent a subbasin with very little terrain variation. Subbasins with large
elevation variations should use multiple elevation bands. Create an elevation band by clicking with the right
mouse button on the Temperature Index icon under a subbasin as shown below. A context menu is displayed
that allows you to create a new elevation band. You can also create an elevation band by clicking with the
right mouse button on any existing elevation band. The same context menu is displayed that allows you to

create a new elevation band. Delete an elevation band by clicking on it with the right mouse button. A context
menu is displayed that allows you to delete the elevation band. Clicking on the elevation band icon will
access the Component Editor used for each band.
219 Add or remove an elevation band
220 Specifying properties for a temperature index elevation band
A Component Editor is provided for each Elevation Band where parameter data defines the Relative Size of
the Band, the Elevation or the Band, and Initial Conditions for Snowpack in the Band. You must specify the
Percentage of the Subbasin that each elevation band composes. An elevation band is not required to be
contiguous. The percentage specified for each elevation band will automatically be normalized if the sum of
the percentages across all subbasins does not equal 100. There is no limit to the number of elevation bands
that can be used, but at least one is required. Typically only one band is used in watersheds with small
elevation differences. Mountainous watersheds usually require several bands for each subbasin.
Enter the Average Elevation for each elevation band. Typically the specified elevation will be either the area-
weighted elevation of the band, or the average of the highest and lowest points in the band.

The optional Precipitation Index must be entered in combination with an index value for the subbasin as a
whole if you wish to adjust precipitation for each elevation band. In general, precipitation increases at higher
elevations in mountainous watersheds.
The Initial Snow Water Equivalent (SWE) that exists at the beginning of the simulation must be entered. This
The Initial Cold Content that exists at the beginning of the simulation must be entered. It represents the heat
required to raise the temperature of the snow pack to 0° C (32° F) and is expressed as a number equivalent
to mm (inches) of frozen water. If there is no snow at the beginning of the simulation, it can be set to zero. If
there is a snowpack, it can be estimated as the depth of snow multiplied by the snow density multiplied by
the heat capacity of snow multiplied by the number of degrees below the freezing point.
The Liquid Water Held Within the Snowpack at the beginning of the simulation must be entered. Liquid water
can persist in the snow only if the snowpack temperature is at 0° C (32° F). There are few conditions when
this value can be exactly known. One case is when there is no snowpack and it can be set to zero. A second
case is when the air temperature has been continually below freezing for several days and it can be set to
zero.
The Initial Cold Content Antecedent Temperature Index is an index to the snow temperature near the
surface of the snowpack. It should be set to the approximate snowpack temperature at the beginning of the
simulation. If the initial temperature is not known, it can be set to 0° C (32° F).
The seasonal variation of meltrate is indexed by an Antecedent Temperature Function. The initial meltrate
ATI should be thought of as similar to "the accumulated thawing degree days." This antecedent temperature
function allows the melt rate to change as the snowpack matures and ages. If there is no snow on the
ground at the start of the simulation this term can be set to zero. It can also be set to zero if the simulation is
starting during or at the end of a cold period when air temperatures were continually below the base
temperature. Otherwise it must be calculated as the accumulation of degree-days since the last period of
sustained air temperature below freezing.

An optional Precipitation Index may be used. In order to use the index, it must be specified for the subbasin
as a whole and also for each elevation band. The ratio of the index for the subbasin and the index at an
elevation band is used to adjust the precipitation for each elevation band. Indexing is one method to adjust
for orographic trends in precipitation.
The PX Temperature is used to discriminate between precipitation falling as rain or snow. When the air
temperature is less than the specified temperature, any precipitation is assumed to be snow. When the air
temperature is above the specified temperature, any precipitation is assumed to be rain.
The difference between the Base Temperature and the Air Temperature defines the Temperature Index
used in calculating snowmelt. The meltrate is multiplied by the difference between the air temperature and
the base temperature to estimate the snowmelt amount. If the air temperature is less than the base
temperature, then the amount of melt is zero. Typically, the base temperature should be 0° C.
The Wet Meltrate is used during time intervals when precipitation is falling as rain, and the rainfall rate is
greater than the rain rate limit. It represents the rate at which the snowpack melts when it is raining on the
snowpack.
There are two options for specifying the Wet Melt Rate:
1. Constant value. A constant value is used to calculate meltrate.

2. Annual pattern. A meltrate pattern may be specified that defines the wet meltrate as a function of the
parameter Wet Melt Rate.
The Rain Rate Limit discriminates between dry melt and wet melt. The wet meltrate is applied as the
meltrate when it is raining at rates greater than the rain rate limit. If the rain rate is less than the rain rate
limit, the meltrate is computed as if there were no precipitation. The default value of 0 mm/day is used if no
value is entered, meaning that even a trace of precipitation results in the use of the wet melt rate.
A meltrate must be calculated for time intervals when the precipitation rate is less than the rain rate limit.
The calculation starts with the meltrate antecedent temperature index. A coefficient is used to update the
antecedent meltrate index from one time interval to the next. The default value of 0.98 is used if no value is
entered.
There are three options for specifying the Dry Melt Rate:
1. ATI-Meltrate Function. An Antecedent Temperature Index Meltrate Function is used to calculate a

meltrate from the current meltrate index. The function must be specified separately in the Paired
Data Manager before it can be used in the snow melt method. The function should define appropriate
meltrates to use over the range of meltrate index values that will be encountered during a simulation.
The melt rate for dry conditions typically ranges from 1 to 4 mm/degC-day.
2. Annual Pattern. A meltrate pattern may be specified that defines the dry meltrate as a function of the
parameter Dry Melt Rate.
3. Constant Value. A constant value is used to calculate meltrate.
The Cold Limit accounts for the rapid changes in temperature that the snowpack undergoes during high
precipitation rates. When the precipitation rate exceeds the specified cold limit, the antecedent cold content
index is set to the temperature of the precipitation. If the temperature is above the base temperature, the
cold content index is set to the base temperature. If the temperature is below the base temperature, the cold
content index is set to the actual temperature. If the precipitation rate is less than the cold limit, the cold
content index is computed as an antecedent index. The default value of 0mm/day is used if no value is
entered, meaning that even a trace of snowfall will reset the cold content.
The Cold Content Antecedent Temperature Index Coefficient is used to update the antecedent cold content
index from one time interval to the next. This is a separate index from the one used to update the meltrate
index. A default value of 0.5 is used if no value is entered.
An Antecedent Temperature Index Cold Content Function is used to calculate a cold content from the
current cold content index. The function must be specified separately in the Paired Data Manager before it
can be used in the Snow Melt Method. The function should define appropriate cold contents to use over the
range of cold content index values that will be encountered during a simulation. The cold rate typically
ranges from 1.22 to 1.32 mm/degC-day.
The Maximum Liquid Water Capacity specifies the amount of melted water that must accumulate in the
snowpack before liquid water becomes available at the soil surface for infiltration or runoff. Typically, the
maximum liquid water held in the snowpack is on the order of 3%-5% of the snow water equivalent, although
it can be higher. Liquid water can persist in the snow only if the snowpack temperature is at 0C; at which
point the cold content is zero. The maximum is entered as a percentage of the snow water equivalent.
Heat from the Ground can cause snowmelt, especially if the snowpack accumulates on ground that is only
partially frozen or completely unfrozen. In these cases the warm ground is insulated by the snowpack. Heat

from the warm ground will cause the bottom of the snowpack to melt. Two methods are available for
specifying the melting of the snowpack due to contact with unfrozen ground:
1. A Fixed Value can be entered; the same amount of melt is computed for the snowpack regardless of
atmospheric conditions above the pack or the time of year.
2. An Annual Pattern can alternately be entered; the pattern specifies the meltrate due to contact with
the ground as a function of the time of year. The pattern must be entered in the Paired Data
Manager before is can be used in the snowmelt method. The Paired Data Type should be Parameter
Value Pattern with parameter Ground Melt Rate.

To use this method, an Air Temperature boundary condition must be selected in the Meteorologic Model
linked to the basin model using the elevation band temperature index method.
10.3.3 Gridded Hybrid

The Gridded Hybrid Method, or Radiation-derived Temperature Index (RTI) Method, uses a radiation balance,
rather than temperature, as a proxy for available energy in the snowpack (Follum et al., (2015)26).
Measurements of solar radiation are rarely available and if available, they are typically point measurements.
In the original RTI model, the incident shortwave radiation for each grid cell is adjusted by reduction factors
for the distance from the earth to the sun, atmospheric scattering, absorption by clouds, vegetation, slope/
aspect of the terrain, and topographic shading. The current implementation of the model within HEC-HMS
does not include reduction factors for absorption by clouds or vegetation. The method is inherently gridded
and can only be used with the ModClark and 2D Diffusion Wave transform methods. The Gridded Hybrid
Method includes spatial variability in shortwave and longwave radiation and is therefore well-suited for
watersheds with forests and steep terrain. The Gridded Hybrid Method includes a Component Editor with
snow pack initial conditions and parameters for an individual subbasin element. You can open a global
temperature index editor from the Parameters | Snowmelt menu.
26 https://reader.elsevier.com/reader/sd/pii/S0022169415006599?
token=9C8AF9E24FE7AF6D210D54A031EFCFE1ECF61003B23598EAA6F585AC19CDEE688B0F63D9CC90EAE90600CC9B33F40DC1&
originRegion=us-east-1&originCreation=20220907215655

221 Gridded Hybrid Component Editor
10.3.3.1 Terrain Preprocessing

Prior to computing a Simulation Run with the Gridded Hybrid snowmelt method, the Slope, Aspect, and Solar
Shading of the terrain can be computed. To compute these parameters, expand the Terrain Data folder in the

Watershed Explorer. Right click on the terrain and select Preprocess Slope and Aspect and Preprocess Solar
Shading, as shown below.
222 Terrain preprocessing steps for Hybrid Method

subbasin are set to the same default value when the Default Values option is chosen. The default values
are:
• Initial SWE of 0 mm (0 in)
• Initial Albedo of 0.4
• Initial ATI of 0°C (32°F)
• Initial Heat Deficit of 0 mm (0 in)
Five parameter grids must be selected when the Parameter Grids option is selected; the grids are described
in the following paragraphs.
value can be set to zero if there is no snow. The Initial Snow Water Equivalent grid can be created within the
Grid Data Manager by selecting the Snow Water Equivalent Grids data type.
The Initial Liquid at the beginning of the simulation must be entered. Liquid water can persist in the snow
only if the snowpack temperature is at 0°C (32°F). There are few conditions when this value can be exactly
known. One case is when there is no snowpack and it can be set to zero. A second case is when the air
temperature has been continually below freezing for several days and it can be set to zero. The Initial Liquid
grid can be created within the Grid Data Manager by selecting the Liquid Water Content Grids data type.
The Initial Albedo that exists at the beginning of the simulation must be represented. This information is
usually obtained from simulated output. This value can be set to zero if there is no snow. The Initial Albedo
grid can be created within the Grid Data Manager by selecting the Albedo Grids data type.
The Initial ATI that exists at the beginning of the simulation must be represented. This information is usually
obtained from simulated output. This value can be set to zero if there is no snow. The Initial ATIgrid can be
created within the Grid Data Manager by selecting the Temperature Gridsets data type.

The Initial Heat Deficit at the beginning of the simulation must be entered. The heat deficit describes the net
heat loss from the snowpack since the start of the simulation. The Initial Heat Deficit grid can be created
within the Grid Data Manager by selecting the Cold Content Grids data type.

The Rain Threshold Air Temperature and the Snow Threshold Air Temperature are used to discriminate
between precipitation falling as rain or snow. When the air temperature is greater than the Rain Threshold Air
Temperature, any precipitation is assumed to be rain. When the air temperature is less than the Snow
Threshold Air Temperature, any precipitation is assumed to be snow. When the air temperature is between
the two threshold temperatures, the amount of precipitation is partitioned between snowfall and rainfall
based on the air temperature.
The Base Temperature is the temperature above which snow begins to melt. The base temperature typically
has a value of 0°C (32°F).
The Melt Factor varies seasonally based on seasonal variations in solar radiation and snow albedo.
The Maximum Negative Melt Factor is used to calculate the heat deficit within the snowpack due to the
difference between the air temperature and the snow surface temperature. Melt occurs when the energy
input into the snowpack overcomes the heat deficit.
The Antecedent Temperature Index (ATI) Coefficient is used to calculate a temperature index from the
current temperature index.
During melting periods, the air temperature is warmer than the snowpack surface temperature. The Wind
Function is used to describe the impediment of flow of vapor by this temperature gradient.
When the liquid water content in the snowpack exceeds the Water Capacity, water leaves the snowpack.
A tutorial and guide detailing the relative sensitivity of these parameters for a location in
Colorado can be found here: Evaluating Gridded Hybrid Snowmelt Parameter Sensitivity27.

In addition to the Subbasin parameters, the following Meteorologic Model boundary conditions are required
to use this method include:
• Gridded Shortwave Radiation
• Gridded Longwave Radiation
• Gridded Precipitation
• Gridded Air Temperature
• Gridded Atmospheric Pressure
• Gridded Relative Humidity
27 https://www.hec.usace.army.mil/confluence/hmsdocs/hmsguides/modeling-snowmelt/evaluating-snowmelt-parameter-sensitivity-
using-the-uncertainty-analysis/evaluating-gridded-hybrid-rti-snowmelt-parameter-sensitivity

10.3.4 Gridded Energy Balance

The Gridded Energy Balance Method is the same as the Regular Energy Balance Method except the
equations for simulating the snowpack are computed separately for each grid cell with separate precipitation
and temperature boundary conditions instead of area-averaged values over the whole subbasin. This method
can only be used if gridded precipitation and temperature are also used. The Gridded Energy Balance
Method can only be used with the ModClark and 2D Diffusion Wave transform methods. The Gridded Energy
Balance Method includes a Component Editor with snow pack initial conditions and energy balance
parameters for an individual subbasin element. You can open a global temperature index editor from the
Parameters | Snowmelt menu.

223 Gridded Energy Balance Component Editor

10.3.4.1 Terrain Preprocessing

Prior to computing a Simulation Run with the Gridded Energy Balance Method snowmelt method,
the Slope, Aspect, and Solar Shading of the terrain can be computed. To compute these parameters, expand
the Terrain Data folder in the Watershed Explorer. Right click on the terrain and select Preprocess Slope and
Aspect and Preprocess Solar Shading.

subbasin are set to the same default value when the Default Values option is chosen. The default values are:
• Initial SWE of 0 mm (0 in)
• Initial Surface Temperature of 0°C (32°F)
• Initial Pack Temperature of 0°C (32°F)
• Initial Albedo of 0.4
• Initial Energy of 0 J/m2 (0 BTU/ft2)
• Initial Depth of 0 mm (0 in)
Seven parameter grids must be selected when the Parameter Grids option is selected; the grids are
described in the following paragraphs.
value can be set to zero if there is no snow. The Initial Snow Water Equivalent grid can be created within the
Grid Data Manager by selecting the Snow Water Equivalent Grids data type.
The Initial Surface Temperature that exists at the beginning of the simulation must be entered. This
information is usually obtained from simulated output. This value can be set to zero if there is no snow. The
Initial Surface Temperature grid can be created within the Grid Data Manager by selecting the Temperature
Gridsets data type.
The Initial Pack Temperature at the beginning of the simulation must be entered. The Initial Pack
Temperature grid can be created within the Grid Data Manager by selecting the Temperature Gridsets data
type.
temperature has been continually below freezing for several days and it can be set to zero. The Initial Liquid
grid can be created within the Grid Data Manager by selecting the Liquid Water Content Grids data type.
The Initial Albedo that exists at the beginning of the simulation must be represented. This information is
usually obtained from simulated output. This value can be set to zero if there is no snow. The Initial Albedo
grid can be created within the Grid Data Manager by selecting the Albedo Grids data type.
The Initial Energy that exists at the beginning of the simulation must be represented. This information is
usually obtained from simulated output. This value can be set to zero if there is no snow. The Initial Energy
grid can be created within the Grid Data Manager by selecting the Energy Grids data type.
The Initial Depth of snow at the beginning of the simulation must be entered. This information is usually
determined by interpolating from actual measurements of snowpack depth. This value can be set to zero if

there is no snow. The Initial Depth grid can be created within the Grid Data Manager by selecting the Snow
Depth Grids data type.

Currently, only the Kondo and Yamazaki (1990)28 option is available for the Albedo Method. Additional
options will be added in the future.
The New Snow Albedo describes the reflectivity of newly fallen snow and typically has a value of 0.8-0.95.
The Minimum Snow Albedo describes the lower limit of the reflectivity of the snow. The minimum snow
albedo typically has a value of 0.2-0.5.
The Albedo Refresh Depth is the depth of fresh snow required to reset the albedo to the New Snow Albedo
value.
The Albedo Decay is a coefficient used in an exponential decay function to describe the decrease in the
albedo as the snowpack ages.
There are two methods for specifying the Albedo Decay Coefficient:
• Constant value. A constant value is used.
• Annual pattern. An albedo decay coefficient pattern may be specified that defines the albedo decay
coefficient as a function of the time of year. The pattern must be specified separately in the Paired
Data Manager before it can be used in the Snow Melt Method. The Paired Data Type should
be Parameter Value Pattern with parameter Albedo Decay Coefficient.
The Snow Thermal Conductivity describes the snow's ability to conduct heat and is used to calculate the
snowpack surface temperature flux. When the snowpack is shallow (i.e. less than the effective depth over
which the temperature gradient acts), an adjustment is applied to the thermal conductivity.
The Liquid Water Retention Fraction is used to compute the portion of energy content held as liquid water in
the snowpack.
The Snow Hydraulic Conductivity is used to calculate the liquid water content of the snowpack in Darcy's law
for flow through porous media.
The Soil Depth for Energy Balance is the depth of soil that interacts thermally with the snowpack.
Colorado can be found here: Evaluating Energy Budget Snowmelt Parameter Sensitivity29.
28 https://www.researchgate.net/publication/
234368511_A_Prediction_Model_for_Snowmelt_Snow_Surface_Temperature_and_Freezing_Depth_Using_a_Heat_Balance_Method
using-the-uncertainty-analysis/evaluating-energy-budget-snowmelt-parameter-sensitivity


In addition to the Subbasin parameters, the following Meteorologic Model boundary conditions are required
to use this method include:
• Gridded Shortwave Radiation
• Gridded Longwave Radiation
• Gridded Precipitation
• Gridded Air Temperature
• Gridded Wind Speed
• Gridded Atmospheric Pressure
• Gridded Relative Humidity
10.3.5 Energy Balance

The Energy Balance Method is based on the Utah Energy Balance (UEB) model (Tarboton and Luce, 199630;
Luce, 200031; Tarboton and Luce, 200132; You, 200433). The UEB snowmelt model is a physically-based
energy and mass balance model. Energy is exchanged between the snowpack, the air above, and the soil
below. The model represents the snowpack using a single layer and includes the upper part of the ground
which has thermal interaction with the snowpack. An energy balance is computed for the snowpack surface
to get the snowpack surface temperature. The snowpack surface temperature is then used to compute the
change in snowpack energy content over a time interval. The mass balance includes rainfall rate, snowfall
rate, meltwater outflow from the snowpack, and vapor transport between the snowpack and the atmosphere.
Snowpack condensation describes vapor transport from the atmosphere to the snowpack. Snowpack
sublimation describes vapor transport from the snowpack to the atmosphere.
The Energy Balance Method includes a Component Editor with parameter data. Each subbasin must have at
least one elevation band and may have up to ten elevation bands. A separate Component Editor is included
for each elevation band. A Component Editor for the elevation band energy balance method is shown below.
30 https://hydrology.usu.edu/dtarb/snow/snowrep.pdf
31 https://hydrology.usu.edu/dtarb/luce_dissertation.pdf
32 https://hydrology.usu.edu/dtarb/wsc2001.pdf
33 https://hydrology.usu.edu/dtarb/yjs_dissertation.pdf

224 Elevation Band Energy Balance Component Editor

Each subbasin is broken into one or more Elevation Bands; each band has its own parameter data. One
elevation band may be used to represent a subbasin with very little terrain variation. Subbasins with large
elevation variations should use multiple elevation bands. Create an elevation band by clicking with the right
mouse button on the Energy Balance icon under a subbasin as shown below. A context menu is displayed
that allows you to create a new elevation band. You can also create an elevation band by clicking with the

right mouse button on any existing elevation band. The same context menu is displayed that allows you to
create a new elevation band. Delete an elevation band by clicking on it with the right mouse button. A context
menu is displayed that allows you to delete the elevation band. Clicking on the elevation band icon will
access the Component Editor used for each band.
225 Add or remove an elevation band
A Component Editor is provided for each Elevation Band where parameter data defines the Relative Size of
the Band, the Elevation or the Band, and Initial Conditions for Snowpack in the Band.

226 Specifying properties for a energy balance elevation band
You must specify the Percentage of the Subbasin that each elevation band composes. An elevation band is
not required to be contiguous. The percentage specified for each elevation band will automatically be
normalized if the sum of the percentages across all subbasins does not equal 100. There is no limit to the
number of elevation bands that can be used, but at least one is required. Typically only one band is used in
watersheds with small elevation differences. Mountainous watersheds usually require several bands for
each subbasin.
Enter the Average Elevation for each elevation band. Typically the specified elevation will be either the area-
weighted elevation of the band, or the average of the highest and lowest points in the band.

Enter the Average Slope for each elevation band. Typically the specified slope will be either the area-
weighted slope of the band, or the average of the steepest and flattest points in the band.
Enter the Average Aspect for each elevation band. Aspect is the predominant downhill direction, oriented
clockwise from North. Typically the specified aspect will be either the area-weighted aspect of the band.
The optional Precipitation Index must be entered in combination with an index value for the subbasin as a
whole if you wish to adjust precipitation for each elevation band. In general, precipitation increases at higher
elevations in mountainous watersheds.
The Initial Snow Water Equivalent (SWE) that exists at the beginning of the simulation must be entered. This
The Initial Snow Depth that exists at the beginning of the simulation must be entered. This information is
usually determined by interpolating from actual measurements of snow depth. This value can be set to zero
if there is no snow.
The Initial Surface Temperature that exists at the beginning of the simulation must be entered. This
information is usually determined by interpolating from actual measurements of surface temperature. This
The Initial Snowpack Temperature that exists at the beginning of the simulation must be entered. This
information is usually determined by interpolating from actual measurements of snowpack temperature.
This value can be set to zero if there is no snow.
The Initial Albedo that exists at the beginning of the simulation must be entered. This information is usually
obtained from simulated output. This value can be set to zero if there is no snow.
temperature has been continually below freezing for several days and it can be set to zero.

Currently, only the Kondo and Yamazaki (1990)34 option is available for the Albedo Method. Additional
options will be added in the future.
The New Snow Albedo describes the reflectivity of newly fallen snow and typically has a value of 0.8-0.95.
The Minimum Snow Albedo describes the lower limit of the reflectivity of the snow. The minimum snow
albedo typically has a value of 0.2-0.5.
The Albedo Refresh Depth is the depth of fresh snow required to reset the albedo to the New Snow Albedo
value.
234368511_A_Prediction_Model_for_Snowmelt_Snow_Surface_Temperature_and_Freezing_Depth_Using_a_Heat_Balance_Method

The Albedo Decay is a coefficient used in an exponential decay function to describe the decrease in the
albedo as the snowpack ages.
There are two methods for specifying the Albedo Decay Coefficient:
• Constant value. A constant value is used.
• Annual pattern. An albedo decay coefficient pattern may be specified that defines the albedo decay
coefficient as a function of the time of year. The pattern must be specified separately in the Paired
Data Manager before it can be used in the Snow Melt Method. The Paired Data Type should
be Parameter Value Pattern with parameter Albedo Decay Coefficient.
The Snow Thermal Conductivity describes the snow's ability to conduct heat and is used to calculate the
snowpack surface temperature flux. When the snowpack is shallow (i.e. less than the effective depth over
which the temperature gradient acts), an adjustment is applied to the thermal conductivity.
The Liquid Water Retention Fraction is used to compute the portion of energy content held as liquid water in
the snowpack.
The Snow Hydraulic Conductivity is used to calculate the liquid water content of the snowpack in Darcy's law
for flow through porous media.
The Soil Depth for Energy Balance is the depth of soil that interacts thermally with the snowpack.

To use this method, the following boundary conditions must be selected in the Meteorologic Model linked to
the Basin Model using the elevation band energy balance method:
• Shortwave Radiation
• Longwave Radiation
• Precipitation
• Air Temperature
• Wind Speed
• Atmospheric Pressure
• Relative Humidity
10.4 Selecting a Surface Method

The Surface is one of the components that can be included in the subbasin element. It is intended to
represent the ground surface where water may accumulate in surface depression storage. The depression
storage of an impervious surface such as a parking lot is generally close to zero. However, the depression
storage for an agricultural field can be quite large if conservation tillage practices are used. Precipitation
through-fall from the canopy, or direct precipitation if there is no canopy, impacts on the surface. The net
precipitation accumulates in the depression storage and infiltrates as the soil has capacity to accept water.
Surface runoff will begin when the precipitation rate exceeds the infiltration rate of the soil layer (loss
method), and the surface storage is filled. The Dynamic Surface method does contain an option to simulate a
layer on top of the soil, which has its own surface infiltration rate. Precipitation residing in the surface
storage can infiltrate after precipitation stops and is subject to potential evapo-transpiration. Selecting a
Surface Method is optional and generally only used for continuous simulation or post wild-fire applications.
The Dynamic Surface method is available for each subbasin element to account for post wildfire scenarios
or other scenarios where a surface layer of vegetation and/or soil limits the amount of precipitation that is

available to infiltrate into the soil layer. The main purpose of this dynamic surface capability is to model the
recovery of infiltration over time after a fire which directly affects runoff generation and the implication for
predicting flash floods and debris flows. The dynamic surface infiltration options allows you an option to
model infiltration rates returning to their pre-fire rates resulting in reduced runoff over time as the watershed
recovers from its burned state.
The Surface Method for a subbasin is selected on the Component Editor for the subbasin element as shown
in the following figure. Access the Component Editor by clicking the subbasin element icon on the
element icon in the Basin Map, if the map is currently open. You can select a Surface Method from the list of
three available choices. If you choose the None method, the subbasin will not compute any surface
depression storage and all through-fall precipitation will be assumed as direct precipitation on the ground
surface, and subject to infiltration into the soil. Use the selection list to choose the method you wish to use.
Each subbasin may use a different method or several subbasins may use the same method.
227 The Surface Method is selected in the Subbasin Component editor
When a new subbasin is created, it is automatically set to use the default Surface Method specified in the
Program Settings. You may change the Surface Method for a subbasin at any time using the Component
Editor for the subbasin element. Since a subbasin can only use one Surface Method at a time, you will be
Program Settings. You can change the Surface Method for several subbasins simultaneously. Click on
the Parameters menu and select the Surface | Change Method command. The Surface Method you choose
will be applied to the selected subbasins in the Basin Model, or to all subbasins if none are currently
selected.

The parameters for each Surface Method are presented on a separate Component Editor from the subbasin
element editor. The Surface editor is always shown next to the Canopy editor. If the Kinematic Wave
Transform Method is selected, there may be two Surface editors, one for each runoff plane. The information
shown on the Surface editor will depend on which method is currently selected.
10.4.1 Gridded Simple Surface

This method implements the Simple Surface Method on a grid cell basis. Each grid cell has separate
parameter values, and separate precipitation through-fall. The Component Editor is shown below.
228 Gridded Simple Surface Method editor
The initial condition of the surface should be specified as the Percentage of the Surface Storage that is full
of water at the beginning of the simulation. The same percentage will be applied to every grid cell.
The Surface Storage Grid must be selected from the grids that have been previously defined in the Grid Data
Manager. The grid should specify the maximum surface storage in each grid cell. You may use a chooser to
select the grid by pressing the Grid button next to the selection list. You will not be able to select a grid if no
grids have been created in the Grid Data Manager.
10.4.2 Simple Surface

This method is a simple representation of the soil surface. All precipitation or precipitation through-fall that
arrives on the soil surface is captured in storage until the storage capacity of the surface is filled. Water in
surface storage infiltrates into the soil whenever it is present in storage. That is, water will infiltrate even
when the storage capacity is not full. Surface runoff will be generated when the storage capacity is filled, and
the precipitation through-fall rate exceeds the infiltration rate. The Component Editor is shown below.

229 Simple Surface Method editor
The initial condition of the surface should be specified as the Percentage of the Surface Storage that is full
of water at the beginning of the simulation.
Surface Storage represents the maximum amount of water that can be held on the soil surface before
surface runoff begins. The amount of storage is specified as an effective depth of water.
10.4.3 Dynamic Surface

The Dynamic Surface method includes a variable surface infiltration rate limit which can be computed from
three surface infiltration limit options. The surface infiltration rate limit represents the hydrophobic layer that
can form after a watershed burn as a result of lower organic material and changes in soil water repellency.
The hydrophobic soil layer moderates the amount of water that is available for infiltration into the soil. The
surface infiltration rate limit eventually returns to the pre-fire infiltration rate of the soil. Another application
of the surface infiltration limit option is that it can be used to set an upper limit to the amount of losses
computed from a subbasin element. For example, the deficit and constant loss method includes both a
moisture deficit state variable and constant loss rate parameter. The moisture deficit simulates how much
water, or lack of water, is in the soil layer. All precipitation is applied to reducing the moisture deficit until it
reaches 0 inches/mm, then the constant loss rate is used to determine excess and infiltration/percolation.
You can have a scenario where the moisture deficit is high, over 4 inches, and an intense precipitation rate of
1 inch/hour and HEC-HMS will not compute any excess precipitation (because the moisture deficit has not
reached 0 inches). In this case, the Dynamic Surface infiltration limit option could be used to set an upper
limit on infiltration losses so that there is runoff even though the moisture deficit is still greater than 0
inches.
This surface layer is conceptualized in the figure below.

Precipitation that is not captured by canopy will interact with the Dynamic Surface layer. Some of the
precipitation could be stored on the surface and lost to evaporation. The remaining precipitation will infiltrate
through the top hydrophobic soil layer at a reduced rate. Precipitation that is not stored by the canopy or
surface storage and is in excess of the surface layer's infiltration rate limit is transformed to runoff. The
infiltrated water will enter the soil layer at the rate determined by the hydrophobic soil layer. The soil layer
can store the water, evaporate the water, or further infiltrate/percolate for baseflow. There are three surface
Infiltration Limit methods available for the Dynamic Surface method: Pak & Lee, Specified (Time Series),
and None option. In the None option for the surface Infiltration Limit method, all water on the surface will be
available for infiltration into the soil layer and functions the same as the Simple Surface method.
10.4.3.1 Pak & Lee Infiltration Limit

The Dynamic Surface Pak & Lee Dynamic Infiltration Limit method was developed based on the Pak & Lee
fire factor equation generated using the percentage of the watershed burned, the number of years since the
fire, and the number of antecedent precipitation events above a certain threshold value since the fire (Pak &
Lee 2005). The Pak & Lee Infiltration Limit method is a simple process used to predict the temporal and
spatial variations of an infiltration rate. The surface infiltration limit is calculated based on the date of the
last fire, the percent burn (of the subbasin), and the number of preceding storm events. An event is defined
when the precipitation intensity exceeds a user-specified threshold. A dry duration is used to separate
precipitation events. Since the number of events is determined using precipitation data for each time step,
the surface infiltration rate limit will be updated each simulation time step. The Component Editor, when
using Pak & Lee Infiltration Limit method, is shown in the figure below.

230 Dynamic Surface component editor with the Pak and Lee Infiltration Limit method selected
The Initial Storage represents the initial condition of the surface layer and is specified as a percentage of the
surface storage that is full of water at the beginning of the simulation.
The Max Storage represents the maximum amount of water that can be held on the surface before surface
runoff begins. The amount of storage is specified as an effective depth of water.
The Date is the burn date of the wildfire within the watershed.
The Percent Burn is the percent of the subbasin area that was burned from the wildfire.
The Initial Rate is the initial surface infiltration rate limit value as a result of the fire.
The Maximum Rate is the max surface infiltration rate limit value after the watershed has recovered.
The Rain Intensity Threshold is the rain intensity threshold that is used to define when an event occurs.
The Dry Duration is used to define separate precipitation events. Precipitation events are considered
separate events once the duration with no precipitation exceeds the dry duration.
10.4.3.2 Specified Infiltration Limit (Time-Series)

The Specified Infiltration Limit method allows users to define the initial surface infiltration limit and a time
series gage, a percent gage, which can be used to modify the surface infiltration limit rate. For example, the
Initial Rate can represent the surface infiltration limit prior to a fire and the values in the Percent Gage can
represent reduction to the surface infiltration limit due to fire conditions. The values in the Percent Gage
could allow the surface infiltration limit to recover over successive years to the original pre-fire rate. The
Component Editor, when using Specified Infiltration Limit method, is shown in the figure below.

231 Dynamic Surface component editor with the Specified Infiltration Limit method selected
The Initial Storage represents the initial condition of the surface layer and is specified as a percentage of the
surface storage that is full of water at the beginning of the simulation.
The Max Storage represents the maximum amount of water that can be held on the surface before surface
runoff begins. The amount of storage is specified as an effective depth of water.
The Initial Rate is the initial surface infiltration rate limit value, and it could represent the post-fire condition
(values in the percent gage should recover the infiltration rate limit to a pre-fire condition).
The Percent Gage requires users to create a Percent Time-Series gage. The time-series values are entered as
percent and should overlap with the simulation period. This gage provides the percent factor to be applied to
the initial rate limit for the given date to define the modified surface infiltration limit.
10.4.4 Gridded Dynamic Surface

The Gridded Dynamic Surface method essentially implements the Dynamic Surface method but the Max
Storage is replaced with a Storage Grid, similar to the Gridded Simple Surface method. Each grid cell has a
separate max storage parameter value. The Gridded Dynamic Surface also includes the same three surface
Infiltration Limit methods, Dynamic Surface: Pak & Lee, Specified (Time Series), and None option; however,
these parameters do not vary by grid cells. The Pak & Lee Infiltration Limit and Specified Infiltration Limit
methods are shown in the figures below.

10.5 Selecting a Loss Method

While a subbasin element conceptually represents infiltration, surface runoff, and subsurface processes
interacting together, the actual infiltration calculations are performed by a Loss Method contained within the
subbasin. A total of twelve different Loss Methods are provided. Some of the methods are designed primarily
for simulating events while others are intended for continuous simulation. All of the methods conserve
mass. That is, the sum of infiltration and precipitation left on the surface will always be equal to total
incoming precipitation. The suitability of the various methods for event and continuous simulation is shown
in the following table.
Loss Method Event Continuous
Deficit and constant Yes
Exponential Yes
Green and Ampt Yes
Gridded deficit and constant Yes
Gridded Green and Ampt Yes
Gridded SCS curve number Yes
Gridded soil moisture accounting Yes
Initial and constant Yes
Layered Green and Ampt Yes
SCS curve number Yes

Loss Method Event Continuous
Smith Parlange Yes
Soil moisture accounting Yes
24 Selecting a loss method for event or continuous simulation
The Loss Method for a subbasin is selected on the Component Editor for the subbasin element as shown in
the following figure. Access the Component Editor by clicking the subbasin element icon on the
element icon in the Basin Map, if the map is currently open. You can select a Loss Method from the list of
twelve available choices. If you choose the None method, the subbasin will not compute infiltration and all
precipitation will be assumed as excess and subject to surface storage and runoff. Use the selection list to
choose the method you wish to use. Each subbasin may use a different method or several subbasins may
use the same method.
232 Selecting the Loss Rate Method in the Subbasin Component Editor
When a new subbasin is created, it is automatically set to use the default Loss Method specified in the
Program Settings. You may change the Loss Method for a subbasin at any time using the Component
Editor for the subbasin element. Since a subbasin can only use one Loss Method at a time, you will be
Program Settings. You can change the Loss Method for several subbasins simultaneously. Click on

the Parameters menu and select the Loss | Change Method command. The Loss Method you choose will be
applied to the selected subbasins in the Basin Model, or to all subbasins if none are currently selected.
The parameters for each Loss Method are presented on a separate Component Editor from the Subbasin
Element editor. The Loss editor is always shown next to the Surface editor. If the Kinematic Wave Transform
Method is selected, there may be two Loss editors, one for each runoff plane. The information shown on the
Loss editor will depend on which method is currently selected.
10.5.1 A Note on Parameter Estimation

The values presented in sources such as Engineer Manual 1110-2-1417 Flood-Runoff Analysis35, the HEC-
HMS Technical Reference Manual36, and the Introduction to Loss Rate Tutorials37 represent initial
estimates. Regardless of the source, these initial estimates must be calibrated and validated.
10.5.2 Deficit and Constant Loss

The Deficit Constant Loss Method uses a single soil layer to account for continuous changes in moisture
content. Using the Deficit Constant Loss Method allows for continuous simulation. It should be used in
combination with a Canopy Method that will extract water from the soil in response to potential evapo-
transpiration computed in the Meteorologic Model. The soil layer will dry out between precipitation events as
the canopy extracts soil water. There will be no soil water extraction unless a Canopy Method is selected. It
may also be used in combination with a Surface Method that will hold water on the land surface. The water in
surface storage infiltrates to the soil layer. The infiltration rate is determined by the capacity of the soil layer
to accept water. When both a Canopy and Surface Method are used in combination with the Deficit Constant
Loss Method, the system can be conceptualized as shown in the following figure.
35 https://www.publications.usace.army.mil/Portals/76/Publications/EngineerManuals/EM_1110-2-1417.pdf?ver=VFC-
A5m2Q18fxZsnv19U8g%3d%3d
36 https://www.hec.usace.army.mil/confluence/hmsdocs/hmstrm
37 https://www.hec.usace.army.mil/confluence/display/HMSGUIDES/Introduction+to+the+Loss+Rate+Tutorials

233 Deficit and Constant Loss Method Conceptual Diagram
Precipitation fills the canopy storage. Precipitation that exceeds the canopy storage will overflow onto the
land surface. The new precipitation is added to any water already in surface storage. If the moisture deficit is
greater than zero, then water will infiltrate from the surface into the soil layer at a rate that is essentially
infinite. This unlimited infiltration will continue until the soil layer reaches saturation (moisture deficit drops
to zero) and during this period there is no percolation. The infiltration rate is defined by the constant rate
while the soil layer remains at saturation. The percolation rate out the bottom of the layer is also defined by
the constant rate while the soil layer remains at saturation. Percolation stops as soon as the soil layer drops
below saturation (moisture deficit greater than zero). Moisture deficit increases in response to the canopy
extracting soil water to meet the potential evapo-transpiration demand. The Component Editor is shown in
the following figure.

234 Deficit constant loss method editor.
The Initial Deficit is the initial condition for the method. At the start of the simulation, it is the amount of
water that would be required in order to fill the soil layer to the maximum storage.
The Maximum Deficit specifies the total amount of water the soil layer can hold, specified as an effective
depth. An upper bound is the bulk thickness of the active soil layer multiplied by the porosity. However, in
most cases such an estimate must be reduced by the permanent wilting point and for other conditions that
reduce the water holding capacity. The thickness of the active soil layer is best determined through
calibration.
The Constant Rate defines the infiltration and percolation rates when the soil layer is saturated. Saturated
hydraulic conductivity is a good approximation.
The Percentage of the Subbasin Which is Directly Connected Impervious Area can be specified. No loss
calculations are carried out on the impervious area; all precipitation on that portion of the subbasin becomes
excess precipitation and subject to surface storage and direct runoff.
10.5.3 Exponential Loss

The Exponential Loss Method is empirical and generally speaking should not be used without calibration.
The Exponential Loss Method should only be used for event simulation. It represents incremental infiltration
as an exponentially decreasing function of accumulated infiltration. It includes the option for increased initial
infiltration when the soil is particularly dry before the arrival of a storm. Before using this method,
consideration should be given to the Green and Ampt Method because it produces a similar exponential
decrease in infiltration and uses parameters with better physical interpretation. The Component Editor is
shown in the following figure.

235 Exponential loss method editor.
The Initial Range is the amount of initial accumulated infiltration during which the loss rate is increased. This
parameter is considered to be a function primarily of antecedent soil moisture deficiency and is usually
storm-dependent.
The Initial Coefficient specifies the starting loss rate coefficient on the exponential infiltration curve. It is
assumed to be a function of infiltration characteristics and consequently may be correlated with soil type,
land use, vegetation cover, and other properties of a subbasin.
The Coefficient Ratio indicates the rate at which the exponential decrease in infiltration capability proceeds.
It may be considered a function of the ability of the surface of a subbasin to absorb precipitation and should
be reasonably constant for large, homogeneous areas.
The Precipitation Exponent reflects the influence of precipitation rate on subbasin-average loss
characteristics. It reflects the manner in which storms occur within an area and may be considered a
characteristic of a particular region. It varies from 0.0 up to 1.0.
excess precipitation and subject to direct runoff.
10.5.4 Green and Ampt Loss

The Green Ampt Infiltration Method is essentially a simplification of the comprehensive Richard's equation
for unsteady water flow in soil. The Green Ampt Method should only be used for event simulation and not for
a continuous simulation where there is an extended dry period(s) between precipitation. It assumes the soil
is initially at uniform moisture content, and infiltration takes place with so-called piston displacement. It is
also assumed that the soil layer is infinitely deep so that reaching saturation can be defined purely by the
Green and Ampt equation. The method automatically accounts for ponding at the soil-air interface.
The Component Editor is shown below.

236 Green Ampt loss method editor
A Method for specifying the initial soil moisture state at the beginning of a simulation must be selected. Two
choices are available: Initial Content and Initial Deficit. The Initial Content method allows the user to specify
the initial soil moisture state in terms of a moisture content. The two required parameters, Initial Content and
Saturated Content, must be specified as volume ratios. Conversely, the Initial Deficit method allows the user
to specify the initial soil moisture state in terms of a deficit. The single required parameter, Initial Deficit,
must be specified as a volume ratio. The Initial Deficit can be calculated as the difference between the
Saturated Content and Initial Content.
The Saturated Water Content specifies the maximum water holding capacity in terms of volume ratio. It is
often assumed to be the total porosity of the soil.
The Wetting Front Suction must be specified. It is generally assumed to be a function of the soil texture.
The Hydraulic Conductivity must also be specified. It can be estimated from field tests or approximated by
knowing the soil texture.
10.5.5 Gridded Deficit Constant Loss

The Gridded Deficit Constant Loss Method essentially implements the Deficit Constant Method on a grid
cell by grid cell basis. Each grid cell receives separate precipitation and potential evapotranspiration from the
Meteorologic Model, while parameters are represented with grids from the Grid Data Manager. A Gridded
Canopy Method should be selected that will extract water from the soil in response to potential evapo-
transpiration computed in the Meteorologic Model. There will be no soil water extraction unless a Canopy
Method is selected. The Component Editor is shown in the following figure.

237 Gridded deficit constant loss method editor
An Initial Deficit Grid must be selected from the list of choices. The selection list will show all Moisture
Deficit Grids available in the Grid Data Manager. You can use a chooser to select a grid by pressing the Grid
button next to the selection list. The chooser shows all of the Moisture Deficit Grids in the Grid Data
Manager. Click on a grid to view the description. This is especially helpful since Initial Deficit and Maximum
Storage Grids are both stored as Moisture Deficit Grids.
A Maximum Deficit Grid must be selected from the list of choices. The selection list will show all Moisture
Deficit Grids available in the Grid Data Manager. You can use a chooser to select a grid by pressing the Grid
button next to the selection list. The chooser shows all of the Moisture Deficit Grids in the Grid Data
Manager. Click on a grid to view the description. This is especially helpful since Initial Deficit and Maximum
Storage Grids are both stored as Moisture Deficit Grids.
A Constant Rate Grid must be selected from the list of choices. The selection list will show all Percolation
Rate Grids available in the Grid Data Manager. You can use the chooser to select a grid by pressing the Grid
button next to the selection list, or select directly from the list of choices.
An Impervious Grid must be selected from the list of choices. The selection list will show all Impervious
Area Grids available in the Grid Data Manager. You can use the chooser to select a grid by pressing the Grid
button next to the selection list.
The Initial Deficit Grid Ratio must be entered. The actual initial deficit value at each grid cell is obtained by
multiplying the value obtained from the initial deficit grid by the specified ratio. The default value is 1.0.
The Maximum Deficit Grid Ratio must be entered. The actual maximum deficit value at each grid cell is
obtained by multiplying the value obtained from the maximum deficit grid by the specified ratio. The default
value is 1.0.
The Constant Rate Grid Ratio must be entered. The actual constant loss rate value at each grid cell is
obtained by multiplying the value obtained from the constant rate grid by the specified ratio. The default
value is 1.0.

The Impervious Grid Ratio must be entered. The actual percentage of impervious area at each grid cell is
obtained by multiplying the value obtained from the impervious grid by the specified ratio. The default value
is 1.0.
10.5.6 Gridded Green and Ampt Loss

The Gridded Green Ampt Loss Method essentially implements the Green Ampt method on a grid cell by grid
cell basis. The Gridded Green Ampt Method should only be used for event simulation. Each grid cell receives
separate precipitation from the Meteorologic Model. Parameters are represented with grids from the Grid
Data Manager. The Component Editor is shown in the following figure.
238 Gridded Green and Ampt loss rate component editor
A Method for specifying the initial soil moisture state at the beginning of a simulation must be selected. Two
choices are available: Initial Content and Initial Deficit. The Initial Content method allows the user to specify
the initial soil moisture state in terms of a moisture content. The two required parameters, Initial Content and
Saturated Content, must be specified as volume ratios. Conversely, the Initial Deficit method allows the user
to specify the initial soil moisture state in terms of a deficit. The single required parameter, Initial Deficit,
must be specified as a volume ratio. The Initial Deficit can be calculated as the difference between the
Saturated Content and Initial Content.
Depending upon the selected initial soil moisture state Method, either an Initial Content and Saturated
Content Grid or just an Initial Deficit Grid must be selected from the list of choices. All of the
aforementioned grids are classified as Water Content Grids. The selection list will show all Water Content
Grids available in the Grid Data Manager. You can use the chooser to select a grid by pressing the Grid
button next to the selection list. The chooser shows all of the Water Content Grids in the Grid Data Manager.
Click on a grid to view the description.

The Wetting Front Suction Grid must be selected from the list of choices. The selection list will show all of
the Water Potential Grids available in the Grid Data Manager. You can use the chooser to select a grid by
pressing the Grid button next to the selection list.
The Hydraulic Conductivity Grid must be selected from the list of choices. The selection list will show all of
the Percolation Rate Grids specified in the Grid Data Manager, because conductivity is a type of percolation
and has the same units. You can use the chooser to select a grid by pressing the Grid button next to the
selection list.
An Impervious Grid must be selected from the list of choices. The selection list will show all Impervious
Area Grids available in the Grid Data Manager. You can use the chooser to select a grid by pressing the Grid
button next to the selection list.
10.5.7 Gridded SCS Curve Number Loss

The Gridded SCS Curve Number Loss Method essentially implements the Soil Conservation Service (SCS)
Curve Number Method on a grid cell by grid cell basis. The Gridded SCS Curve Number Loss Method should
only be used for event simulation. Details of the curve number approach can be found in the National
Engineering Handbook (NRCS, 2007). Each grid cell receives separate precipitation from the Meteorologic
Model. All cells are initialized by scaling based on the curve number at each cell, and then allowed to evolve
separately during the simulation based on individual precipitation inputs. The main parameter is represented
with a grid from the Grid Data Manager. The Component Editor is shown below.
239 Gridded SCS curve number loss method editor
The Curve Number Grid must be selected from the available choices. A Curve Number Grid must be defined
in the Grid Data Manager before it can be used in the subbasin. You can use a chooser to select a grid by
pressing the Grid button next to the selection list. The chooser shows all of the Curve Number Grids in the
Grid Data Manager.

The default Initial Abstraction Ratio is 0.2 but may optionally be changed. The Initial Abstraction Ratio is
used to compute the Initial Abstraction at each grid cell. The potential retention is calculated from the curve
number for each cell, then multiplied by the ratio to determine the actual Initial Abstraction for that cell.
The default Potential Retention Scale Factor is 1.0 but may optionally be changed. The Potential Retention
Scale Factor is used to adjust the retention calculated from the curve number before it is multiplied by the
Initial Abstraction Ratio.
10.5.8 Gridded Soil Moisture Accounting Loss

The Gridded Soil Moisture Accounting Loss Method essentially implements the Soil Moisture Accounting
Method on a grid cell by grid cell basis. Each grid cell receives separate precipitation and potential
evapotranspiration from the Meteorologic Model. All cells are initialized to the same initial conditions, and
then allowed to evolve separately during the simulation based on individual precipitation inputs. Parameters
are specified on a cell by cell basis using grids from the Grid Data Manager. A gridded Canopy Method
should be selected that will extract water from the soil in response to potential evapo-transpiration
computed in the Meteorologic Model. There will be no soil water extraction unless a Canopy Method is
selected. The Component Editor is shown below.
240 Gridded soil moisture accounting loss method editor
The Maximum Infiltration Grid is selected from the Percolation Grids that have been previously defined in
the Grid Data Manager. The grid should specify the maximum infiltration rate at each grid cell. This is the
upper bound on infiltration; the actual infiltration at any cell in a particular time interval is a linear function of
the surface and soil storage in the cell, if a Surface Method is selected. Without a selected Surface Method,
water will always infiltrate at the maximum rate. You may use a chooser to select the grid. The grid
selections will be disabled unless you have previously created grids in the Grid Data Manager. Likewise, you

must also select a Soil Percolation and Groundwater Percolation Grids. All Infiltration and Percolation Grids
use the same type of parameter grid so descriptions for the grids are important.
The Initial Condition of the Soil should be specified as the percentage of the soil storage that is full of water
at the beginning of the simulation. The same percentage will be applied to every grid cell. Likewise, you must
specify the Initial Storage of each groundwater layer.
The Soil Storage Grid must be selected from the grids that have been previously defined in the Grid Data
Manager. The grid should specify the maximum soil storage in each grid cell. You may use a chooser to
select the grid by pressing the Grid button next to the selection list. You will not be able to select a grid if no
grids have been created in the Grid Data Manager. Likewise, you must select a Tension Storage Grid, and a
Storage Grid for each groundwater layer. Because tension storage is contained within the total soil storage,
the tension storage at each cell must be less than the soil storage at the same cell.
Groundwater Coefficient Grids must be selected for the upper and lower groundwater layers. The selected
grid should specify the storage coefficient for each cell in the layer. The coefficient is used as the time lag on
a linear reservoir for transforming water in storage to become lateral outflow. Contributions from each grid
cell are accumulated to determine the total amount of flow available to become baseflow.
10.5.9 Initial and Constant Loss

The Initial Constant Loss Method is very simple but still appropriate for watersheds that lack detailed soil
information. It is also suitable for certain types or flow-frequency studies. The Initial Constant Loss Method
should only be used for event simulation. The Component Editor is shown below.
241 Initial and constant loss method editor
The Initial Loss specifies the amount of incoming precipitation that will be infiltrated or stored in the
watershed before surface runoff begins. There is no recovery of the initial loss during periods without
precipitation.

The Constant Rate determines the rate of infiltration that will occur after the initial loss is satisfied. The
same rate is applied regardless of the length of the simulation.
10.5.10 Layered Green and Ampt Loss

The Layered Green Ampt Loss Method uses two soil layers to account for continuous changes in moisture
content. The method is based on algorithms originally developed for the Guelph Agricultural Watershed
Storm-Event Runoff (GAWSER) model. Using the layered Green Ampt Method allows for continuous
simulation. It should be used in combination with a Canopy Method that will extract water from the soil in
response to potential evapo-transpiration computed in the Meteorologic Model. The soil layer will dry out
between precipitation events as the canopy extracts soil water. There will be no soil water extraction unless
a Canopy Method is selected. It may also be used in combination with a Surface Method that will hold water
on the land surface. The water in surface storage infiltrates to the soil layer. The infiltration rate is
determined by the capacity of the soil layer to accept water. When both a Canopy and Surface Method are
used in combination with the Layered Green and Ampt Method, the system can be conceptualized as shown
in the following figure.

242 Layered Green and Ampt Loss Method Conceptual Diagram
The Layered Green Ampt Loss Method uses two layers to represent the dynamics of water movement in the
soil. Surface water infiltrates into the upper layer, called Layer 1. Layer 1 produces seepage to the lower
layer, called Layer 2. Both layers are functionally identical but may have separate and distinct parameters.
Separate parameters can be used to represent layered soil profiles and also allows for better representation
of stratified soil drying between storms. Each layer is described using a bulk depth and water content values
for saturation, field capacity, and wilting point. Soil water in Layer 2 can percolate out of the soil profile. The
Layered Green Ampt Method is intended to be used in combination with the Linear Reservoir baseflow
method. When used in this manner, the percolated water can be split between baseflow and aquifer
recharge.

land surface. The precipitation is added to any water already in surface storage. The infiltration rate from the
surface into Layer 1 is calculated with the Green and Ampt Equation so long as Layer 1 is below saturation.
The infiltration rate changes to the current seepage rate when Layer 1 reaches saturation. Infiltrated water is
added to the storage in Layer 1. Seepage out of Layer 1 only occurs when the storage exceeds field capacity.
Maximum seepage occurs when Layer 1 is at saturation and declines to zero at field capacity. The seepage
rate changes to the percolation rate when Layer 2 is saturated. Seepage is added to the storage in Layer 2.
Percolation out of Layer 2 only occurs when the storage exceeds field capacity. Maximum percolation
occurs when Layer 2 is at saturation and declines to zero at field capacity. Most soils observe decreasing
hydraulic conductivity rates at greater depths below the surface. This means that the seepage rate is
reduced to the percolation rate when Layer 2 saturates, and the infiltration rate is reduced to the seepage
rate when Layer 1 saturates. The infiltration rate will change to the percolation rate if both Layers 1 and 2 are
saturated. Additionally, contribution to baseflow will not occur until both soil layers have reached field
capacity. Both convergence control and adaptive time stepping are used to accurately resolve the saturation
of each layer.
The canopy extracts water from soil storage to meet the potential evapo-transpiration demand. First, soil
water is extracted from Layer 1 at the full evapo-transpiration rate. This extraction from Layer 1 continues
until half of the available water has been taken to meet the evapo-transpiration demand. The available water
is defined as the saturation content minus the wilting point content, multiplied by the bulk layer thickness.
Second, soil water is extracted from Layer 2 at the full evapo-transpiration rate. This extraction from Layer 2
also continues until half of the available water has been taken. Third, the evapo-transpiration demand is
applied equally to both layers until one of them reaches wilting point content. Finally, the evapo-transpiration
demand is applied to the remaining layer until it also reaches wilting point content. Soil water below the
wilting point content is never used for evapo-transpiration.
The Layered Green Ampt Loss Method can be used for continuous simulation because it is built on a water
balance of the two layers. Infiltrated water is added to the layers and percolated water is removed from the
layers. Potential evapo-transpiration demand also removes water from the layers. The continuous simulation
will include storm events from time to time. The Green and Ampt Equation is used to compute the surface
infiltration during each of these storm events. The initial condition of the Green and Ampt equation for each
of these storms must be determined. The initial content is essentially a water content deficit which can be
calculated as the saturated water content minus the current water content. The water content deficit is
automatically calculated at the beginning of each storm based on current soil water storage in Layer 1. The
user can control the amount of time that must pass since the last precipitation in order for the initial
condition to be recalculated, using the dry duration parameter. When the time since last precipitation is less
than the dry duration, the precipitation is considered a continuation of the last storm event. The Component
Editor is shown below.

243 Layered Green Ampt loss method editor
The Layer 1 Initial Water Content sets the amount of soil water at the beginning of a simulation. It should be
specified in terms of volume ratio.
The Layer 2 Initial Water Content sets the amount of soil water at the beginning of a simulation. It should be
The Hydraulic Conductivity should be specified. It can be estimated from field tests or approximated by
knowing the surface soil texture.
The Maximum Seepage must be specified at the bottom of Layer 1. Field tests or the soil texture at the
bottom of Layer 1 can be used to estimate a value.
The Maximum Percolation must be specified at the bottom of Layer 2. Field tests or the soil texture at the
bottom of Layer 2 can be used to estimate a value.
The Wetting Front Suction must be specified. It is generally assumed to be a function of the soil texture.
The Dry Duration sets the amount of time that must pass after a storm event in order to recalculate the initial
condition for the Green and Ampt Equation. It has been found that 12 hours often works well.
The Layer 1 Thickness sets the bulk depth of soil measured from the ground surface down to the bottom of
Layer 1.
The Layer 1 Saturated Water Content specifies the maximum water holding capacity in terms of volume
ratio. It is often assumed to be the total porosity of the soil.
The Layer 1 Field Capacity Content specifies the point where the soil naturally stops seeping under gravity, in
terms of volume ratio.

The Layer 1 Wilting Point Content specifies the amount of water remaining in the soil when plants are no
longer capable of extracting it. It should be specified in terms of volume ratio.
The Layer 2 Thickness sets the bulk depth of soil measured from the bottom of Layer 1 down to the bottom
of Layer 2.
The Layer 2 Saturated Water Content specifies the maximum water holding capacity in terms of volume
ratio. It is often assumed to be the total porosity of the soil.
The Layer 2 Field Capacity Content specifies the point where the soil naturally stops percolating under
gravity, in terms of volume ratio.
The Layer 2 Wilting Point Content specifies the amount of water remaining in the soil when plants are no
longer capable of extracting it. It should be specified in terms of volume ratio.
10.5.11 SCS Curve Number Loss

The Soil Conservation Service (SCS) Curve Number Method implements the curve number methodology for
incremental losses (NRCS, 2007). The SCS Curve Number Loss Method should only be used for event
simulation. Originally, the methodology was intended to calculate total infiltration during a storm. The
program computes incremental precipitation during a storm by recalculating the infiltration volume at the
end of each time interval. Infiltration during each time interval is the difference in volume at the end of two
adjacent time intervals. The Component Editor is shown below.
244 SCS curve number loss method editor
You may optionally enter an Initial Abstraction. The Initial Abstraction defines the amount of precipitation
that must fall before surface excess results. However, it is not the same as an Initial Interception or Initial
Loss since changing the Initial Abstraction changes the infiltration response later in the storm. If this value is
left blank, it will be automatically calculated as 0.2 times the potential retention, which is calculated from the
Curve Number.

You must enter a Curve Number. This should be a composite curve number that represents all of the
different soil group and land use combinations in the subbasin. The composite curve number should not
include any impervious area that will be specified separately as the Percentage of Impervious Area.
The Percentage of the Subbasin Which is Directly Connected Impervious Area can be specified. Any
percentage specified should not be included in computing the composite curve number. No loss calculations
are carried out on the impervious area; all precipitation on that portion of the subbasin becomes excess
precipitation and subject to direct runoff.
10.5.12 Smith and Parlange Loss

The Smith Parlange Loss Method approximates Richard's Equation for infiltration into soil by assuming the
wetting front can be represented with an exponential scaling of the saturated conductivity. This linearization
approach allows the infiltration computations to proceed very quickly while maintaining a reasonable
approximation of the wetting front. The Smith Parlange Loss Method should only be used for event
simulation. The Component Editor is shown in the following figure.
245 Smith Parlange loss method editor
The Initial Water Content gives the initial saturation of the soil at the beginning of a simulation. It should be
The Residual Water Content specifies the amount of water remaining in the soil after all drainage has
ceased. It should be specified in terms of volume ratio. It may be determined in the laboratory or estimated
from the soil texture.
The Saturated Water Content specifies the maximum water holding capacity in terms of volume ratio. It is
often assumed to be the total porosity of the soil.
The Bubbling Pressure, also known as the Wetting Front Suction, must be specified. It is generally assumed
to be a function of the soil texture.

The Pore Size Distribution determines how the total pore space is distributed in different size classes. It is
typically assumed to be a function of soil texture.
The Hydraulic Conductivity must also be specified, typically as the effective saturated conductivity. It can be
estimated from field tests or approximated by knowing the soil texture.
Optionally, a Temperature Gage may be selected for adjusting the water density, water viscosity, and matric
potential based on temperature. If no Temperature Gage is selected then a temperature of 25C (75F) is
assumed to prevail. The gage must be defined in the Time-Series Manager before it can be selected in the
Component Editor.
The Beta Zero parameter is used to correct the matric potential based on temperature. It has been found to
be a function of soil texture. It will only be shown for input if a temperature gage has been selected. The
following table provides mean estimates of beta zero.
USDA Soil Texture Beta Zero
Sand -404.9
Loamy sand -403.4
Sandy loam -400.7
Loam -397.1
Silt loam -399.2
Sandy clay loam -393.5
Clay loam -390.4
Silty clay loam -390.0
Sandy clay -386.9
Silty clay -383.9
Clay -376.8
25 Beta Zero parameter values for various soil textures classes

10.5.13 Soil Moisture Accounting Loss

The Soil Moisture Accounting Loss Method uses three layers to account for continuous changes in moisture
content throughout the vertical profile of the soil. Using the Soil Moisture Accounting Method allows for
continuous simulation. It should be used in combination with a Canopy Method that will extract water from
the soil in response to potential evapo-transpiration computed in the Meteorologic Model. The soil layer will
dry out between precipitation events as the canopy extracts soil water. There will be no soil water extraction
unless a Canopy Method is selected. It may also be used in combination with a Surface Method that will hold
water on the land surface. The water in surface storage infiltrates to the soil layer. The infiltration rate is
determined by the capacity of the soil layer to accept water. When both a Canopy and Surface Method are
used in combination with the Soil Moisture Accounting Loss Method, the system can be conceptualized as

246 Soil Moisture Accounting Loss Method Conceptual Diagram
The Soil Moisture Accounting Loss Method uses three layers to represent the dynamics of water movement
in the soil. Layers include soil storage, upper groundwater, and lower groundwater. Groundwater layers are
not designed to represent aquifer processes; they are intended to be used for representing shallow inter-flow
processes. The soil layer is subdivided into an upper zone and a tension zone. Soil water only percolates
from the upper zone while water in the tension zone resists percolation. Water in upper groundwater
percolates to lower groundwater. The Soil Moisture Accounting Loss Method is designed to be used in
combination with the Linear Reservoir Baseflow Method. When used in this way, water can move laterally
out of upper groundwater and lower groundwater to enter baseflow. Water percolating out of lower
groundwater can be split between entering baseflow and leaving the land surface as aquifer recharge.

land surface. The new precipitation is added to any water already in surface storage. The current infiltration
rate is a function of the maximum infiltration rate, the current surface storage, and the current soil storage.
The highest infiltration occurs when the surface storage is at maximum and the soil storage is at zero.
Infiltration approaches zero as the surface storage falls to zero or as the soil storage reaches saturation.
Infiltration water is added to the water already in soil storage. The upper zone and tension zone both exist
within the soil storage. Water will percolate from the soil to upper groundwater whenever the soil storage is
between the tension zone depth and the soil storage depth. The percolation rate is a function of the
maximum percolation rate, the current soil storage, and the current upper groundwater storage. The highest
percolation occurs when the soil storage is at maximum (saturated) and the upper groundwater is at zero.
Percolation approaches zero as the soil storage falls to the tension zone depth or as the groundwater
reaches saturation. Similarly, water percolates from upper groundwater to lower groundwater as a function
of the maximum upper groundwater percolation rate, the upper groundwater storage, and the lower
groundwater storage.
The canopy extracts water from soil storage to meet the potential evapo-transpiration demand. Soil water is
extracted from the upper zone at the full potential evapo-transpiration rate. Once soil storage falls to the
tension storage depth, the further extraction of soil water is determined by the interaction of the canopy and
the amount of water in soil storage. This interaction is configured in the canopy component as the plant
uptake method. Depending on the uptake method, water may be extracted from the soil at the full potential
evapo-transpiration rate until no water remains in soil storage. An alternate uptake method continues to
extract water at the full potential evapo-transpiration rate until soil water falls to half of the tension storage
depth, with extraction less than potential as soil storage falls to zero. Potential evapo-transpiration is never
extracted from the groundwater layers. The Component Editor is shown below.
247 Soil moisture accounting loss method editor

The Initial Condition of the Soil should be specified as the percentage of the soil that is full of water at the
beginning of the simulation. The Initial Condition of the Upper and Lower Groundwater Layers must also be
specified.
The Maximum Infiltration Rate sets the upper bound on infiltration from the surface storage into the soil.
This is the upper bound on infiltration; the actual infiltration in a particular time interval is a linear function of
the surface and soil storage, if a Surface Method is selected. Without a selected Surface Method, water will
always infiltrate at the maximum rate.
The Percentage of the Subbasin Which is Directly Connected Impervious Area can be specified. All
precipitation on that portion of the subbasin becomes excess precipitation and subject to direct runoff.
Soil Storage represents the total storage available in the soil layer. It may be zero if you wish to eliminate soil
calculations and pass infiltrated water directly to groundwater.
Tension Storage specifies the amount of water storage in the soil that does not drain under the affects of
gravity. Percolation from the soil layer to the upper groundwater layer will occur whenever the current soil
storage exceeds the tension storage. Water in tension storage is only removed by evapotranspiration. By
definition, tension storage must be less that soil storage.
The Soil Percolation sets the upper bound on percolation from the soil storage into the upper groundwater.
The actual percolation rate is a linear function of the current storage in the soil and the current storage in the
upper groundwater.
Groundwater 1 Storage represents the total storage in the upper groundwater layer. It may be zero if you
wish to eliminate the upper groundwater layer and pass water percolated from the soil directly to the lower
groundwater layer.
The Groundwater 1 Percolation Rate sets the upper bound on percolation from the upper groundwater into
the lower groundwater. The actual percolation rate is a linear function of the current storage in the upper and
lower groundwater layers.
The Groundwater 1 Coefficient is used as the time lag on a linear reservoir for transforming water in storage
to become lateral outflow. The lateral outflow is available to become baseflow.
Groundwater 2 Storage represents the total storage in the lower groundwater layer. It may be zero if you
wish to eliminate the lower groundwater layer and pass water percolated from the upper groundwater layer
directly to deep percolation.
The Groundwater 2 Percolation Rate sets the upper bound on deep percolation out of the system. The actual
percolation rate is a linear function of the current storage in the lower groundwater layer.
The Groundwater 2 Coefficient is used as the time lag on a linear reservoir for transforming water in storage
to become lateral outflow. It is usually a larger value that the groundwater 1 coefficient. The lateral outflow is
likewise available to become baseflow.
10.6 Selecting a Transform Method

interacting together, the actual surface runoff calculations are performed by a Transform Method contained
within the subbasin. A total of nine different Transform Methods are provided. The choices include various
Unit Hydrograph Methods, a Kinematic Wave implementation, a Linear Quasi-distributed Method, and a
Two-dimensional (2D) Diffusion Wave Method.
The Transform Method for a subbasin is selected on the Component Editor for the subbasin element as
shown in the following figure. Access the Component Editor by clicking the subbasin element icon on the

element icon in the Basin Map, if the map is currently open. You can select a Transform Method from the list
of seven available choices. If you choose the None method, the subbasin will transform all excess
precipitation as runoff at the end of each time step. Use the selection list to choose the method you wish to
use. Each subbasin may use a different method or several subbasins may use the same method.
248 Selecting a Transform Method in the Subbasin Component Editor
When a new subbasin is created, it is automatically set to use the default Transform Method specified in the
Program Settings. You may change the Transform Method for a subbasin at any time using the Component
Editor for the subbasin element. Since a subbasin can only use one Transform Method at a time, you will be
Program Settings. You can change the Transform Method for several subbasins simultaneously. Click on
the Parameters menu and select the Transform | Change Method command. The Transform Method you
choose will be applied to the selected subbasins in the Basin Model, or to all subbasins if none are currently
selected.
The parameters for each Transform Method are presented on a separate Component Editor from the
Subbasin Element editor. The Transform editor is always shown near to the Loss editor. The Kinematic
Wave Method uses multiple tabs in the Component Editor. The information shown on the Transform editor
will depend on which method is currently selected.
10.6.1 Clark Unit Hydrograph Transform

The Clark Unit Hydrograph is a synthetic unit hydrograph method. This means that the user is not required to
develop a unit hydrograph through the analysis of past observed hydrographs. Instead, a Time Versus Area
Curve (time-area curve) is used to develop the translation hydrograph resulting from a burst of precipitation.

The resulting translation hydrograph is routed through a linear reservoir to account for storage attenuation
effects across the subbasin. There are three methods available for the Clark Unit Hydrograph: Standard,
Variable Parameter, and Maricopa County AZ USA. The Component Editor will automatically update based
on the selected method.
10.6.1.1 Standard
The Component Editor, when using the Standard method, is shown in the following figure.
249 Clark Standard Method Component Editor
The Time of Concentration defines the maximum travel time in the subbasin. It is used in the development of
the translation hydrograph.
The Storage Coefficient is used in the linear reservoir that accounts for storage effects. A dimensionless
ratio can be defined as the storage coefficient divided by the sum of the time of concentration and storage
coefficient. Many studies have found that the dimensionless ratio is relatively constant over a region.
10.6.1.2 Variable Parameter

Unit hydrograph theory assumes a linear relationship between precipitation and the runoff response. This
assumption can lead to errors in timing and peak magnitude when simulating events that result from
extremely large excess precipitation rates, such as the Probable Maximum Precipitation. When using the
Clark Unit Hydrograph, tables relating time of concentration and storage coefficient to the excess
precipitation can be used to vary the runoff response throughout the simulation. The Component Editor,
when using the Variable Parameter method, is shown below.

250 Clark Variable Method Component Editor
The Index Excess is an excess precipitation rate that is used to relate the Time of Concentration and
Storage Coefficient defined in the editor against the Variable Parameter Relationships. Typically, this rate is
1 inch/hour (or 1 mm/hour).
The Variable Parameter Relationships must be defined as percentage curves in the Paired Data Manager
before they can be used in the subbasin element. These curves must be monotonically increasing. The x-axis
of the percentage curves defines the excess precipitation rate relative to the Index Excess. The y-axis of the
percentage curves defines either the time of concentration or storage coefficient for each percent excess
precipitation rate (again, relative to the Index Excess).
The Default Time-Area Curve represents the subbasin using an elliptical shape. This shape has been shown
to approximate the timing of surface runoff very well for typical subbasins. However, there is also an option
to provide a user-specified Time-Area Curve. The relationship must be defined as a percentage curve in the
Paired Data Manager before it can be used in the subbasin element. The independent axis of the percentage
curve defines the percentage of the time of concentration, while the dependent axis of the curve defines the
cumulative percentage of subbasin area contributing runoff. The curve must be monotonically increasing.
10.6.1.3 Maricopa County AZ USA

The Component Editor, when using the Maricopa County AZ USA method, is shown below.

251 Clark Maricopa County Method Component Editor
The Clark Time of Concentration and Storage Coefficient parameters are automatically computed using
physical characteristics of the watershed and the following two equations.
L is the length of the hydraulically longest flow path, S is the watercourse slope of the longest flow path, Kb is
the resistance coefficient, and i is the average excess precipitation intensity. L, Kb, and S are estimated and
specified by the user into the Component Editor. Refer to the Maricopa County Drainage Design Manual for
information about estimating L, Kb, and S (Maricopa County, 2011). The average excess precipitation
intensity must be computed from the top ten highest five-minute time interval values. The HEC-HMS
compute process will perform a preliminary simulation to compute precipitation loss/excess at a five-minute
time interval (only when the Maricopa County AZ USA method is selected), regardless of the user defined
simulation time-step. After running a preliminary simulation at a five-minute time-step, the program will
extract the top ten highest five-minute time interval excess precipitation values, compute an average excess
precipitation rate, and then compute the time of concentration and storage coefficient.
HEC-HMS issues a couple of notes in the Message Window indicating the computed average excess
precipitation intensity, time of concentration, and storage coefficient. Note 45820 contains information
about the computed average excess precipitation intensity. Note 45917 displays the computed time of
concentration and storage coefficient.
10.6.2 Kinematic Wave Transform

The Kinematic Wave Method is designed principally for representing urban areas, although it can be used for
undeveloped regions as well. It is a conceptual model that includes one or two representative planes.

Typically, one plane is used for impervious surfaces and one for pervious surfaces. Examples of impervious
surfaces include building roofs, parking lots, and streets. Examples of pervious surfaces include lawn, parks,
and undeveloped open space. The key difference in impervious and pervious surfaces is whether the surface
allows infiltration. The same meteorologic boundary conditions are applied to each plane. However, separate
canopy, surface, and loss rate information is required for each plane and is entered separately. The
Kinematic Wave Equations are used to calculate runoff for each plane and then a weighted composite runoff
is calculated using the representative percentage for each plane.
The Composite Runoff is directed to a Subcollector. The Subcollector is used to represent primary collection
in the stormwater management system. The most common collection system is gutters along streets. In
areas without gutters, unlined ditches next to the street may perform a similar stormwater collection
function. The Composite Runoff is applied to the Subcollector as a uniform lateral boundary condition,
scaling based on the representative area of a typical Subcollector. Water is routed through a representative
Subcollector using the Kinematic Wave Equations. There is no seepage from the Subcollector so it may be
difficult to use it for representing vegetated swales and other types of best management practices.
The outflow from the representative Subcollector is directed to a Collector. The Collector is used to
represent the next step up in the stormwater management system. Conceptually, the Collector receives
inflow from multiple gutters or ditches. A common Collector is a concrete channel about two or three meters
wide. The outflow from the Subcollector is scaled up using the representative area of a typical Collector and
applied to the Collector as a uniform lateral boundary condition. Water is routed through a representative
Collector using the Kinematic Wave Equations. Again, there is no seepage from the Collector.
The outflow from the representative Collector is directed to a Channel. The Channel may be used to
represent the final step in the stormwater management system, or optionally may be used to represent the
river passing through the subbasin. Conceptually, the Channel receives inflow from multiple Collectors. The
outflow from the representative Collector is scaled up using the area of a typical Collector and the area of the
subbasin. The scaled flow is applied to the Channel as a uniform lateral boundary condition. Water is routed
through the Channel to become the outflow from the subbasin. The routing may be performed using either
the Kinematic Wave Equations or the Muskingum Cunge Equations.
10.6.2.1 Planes
A separate tab is provided for each plane; they are displayed whenever the Component Editor is shown for
the subbasin as seen in the following figure.

252 Kinematic Wave Plane Component Editor
The first parameter is the Length. The typical length of the conceptual plane should be entered. For
impervious areas, this should be the average flow length from the point where precipitation falls, to where
the runoff first enters a collection gutter or channel. For pervious areas, this should likewise be the average
flow length. When using the two planes to represent pervious and impervious areas, it is helpful to adopt a
convention for which plane number (one or two) represents the pervious area.
The Slope is also required for each plane that will be used. The slope should represent the average slope
along the flow line from the point where precipitation falls to where the runoff first enters a gutter or channel.
Roughness is the principal difference between a plane meant to represent impervious or pervious area.
Roughness coefficients for natural areas are much higher than for developed areas. However, in both cases
the Surface Roughness Coefficients are higher than typical Manning's Roughness Coefficients used for
open channel flow.
The Percentage of the Subbasin Area Occupied by Each Plane must be entered. If you only want to use one
plane, then enter 100 for the first plane and 0 for the second. You do not need to enter length, slope, or
roughness if the area will be set to zero.
The number of Routing Steps is used as a hint to the program when it determines the correct distance step
to use during runoff calculations. Criteria based on rate of precipitation and other factors are used to
automatically determine the correct distance and time steps for solving the kinematic wave equation. The
default value is five.
10.6.2.2 Subcollector and Collector

A separate tab is provided for the Subcollector and Collector as shown in the following figure.

253 Kinematic Wave Subcollector Component Editor
The Length should be the average distance from the beginning of the Subcollector to where it will enter a
Collector. Usually this value will be measured from maps of the stormwater collection system.
The Slope should be the average slope along the average flow length. This value may be estimated from
maps if they provide sufficient vertical resolution. Field survey data may be necessary to actually determine
elevations of the gutter or channel. If the slope varies significantly throughout the system, this may become a
determining factor in how the system is broken into Subcollectors, Collectors, and Main Channel.
The Manning's n Roughness Coefficient should be the average value for the whole Subcollector. It is
important to remember that the parameter data entered for the Subcollector should be typical of all similar
Subcollectors in the subbasin.
The number of Subreaches is used as a hint to the program when it determines the correct distance step to
use during routing calculations. The default value is five.
The typical Area of each Subcollector must be entered. This is used to determine how to apply the
composite outflow from the Subcollector to the Collector channel. It essentially determines the number of
Subcollector channels in the subbasin.
Five options are provided for specifying the Cross Section Shape: Circle, Deep, Rectangle, Trapezoid, and
Triangle. The circle shape cannot be used for pressure flow or pipe networks, but is suitable for representing
a free water surface inside a pipe. The deep shape should only be used for flow conditions where the flow
depth is approximately equal to the flow width. Depending on the shape you choose, additional information
will have to be entered to describe the size of the cross section shape. This information may include a
Diameter (circle), Bottom Width (deep, rectangle, trapezoid), or Side Slope (trapezoid, triangle). The Side
Slope is dimensionless and entered as the units of horizontal distance per one unit of vertical distance.
The outflow from the Subcollector enters a Collector as lateral inflow. The Collector Channel is intended to
represent small ditches or open channels that are part of an engineered stormwater management system.
The parameters for the Collector are exactly the same as for the Subcollector.

Length, Slope, Manning's n, and the number of Subreaches all have the same definitions. The area served by
a typical Collector must be entered; this is used to apply lateral inflow from the Collector to the main
channel. Options for the Cross Section Shape are exactly the same as for the Subcollector.
10.6.2.3 Channel
A separate tab is provided for the Channel as shown in the following figure.
254 Kinematic Wave Channel Component Editor
Normally, it is not possible to connect upstream inflow to a subbasin element. However, because of the
conceptual representation of the channel, it is possible to have an upstream inflow on the main channel. In
order to connect upstream elements to the subbasin, you must select the Route Upstream option.
The surface runoff on the two planes is always routed using the Kinematic Wave Method. However, you have
the choice of using Muskingum-Cunge Routing in the Subcollector, Collector, and Main Channel. All three
channels use the same method. Select the method you wish to use.
If the Route Upstream option is turned on, the Length should be the distance from the upstream boundary of
the subbasin to the outlet. If the Route Upstream option is turned off, the length should be from the
identifiable concentration point of the channel to the subbasin outlet. There is only one channel is each
subbasin.
The Slope should be the average slope for the whole channel. This value may be estimated from maps if they
provide sufficient vertical resolution. Field survey data may be necessary to actually determine elevations of
the channel bed for calculating the slope.
The number of Subreaches is used to determine the distance step to use during routing calculations. The
default value is five. This parameter is only entered when the Kinematic Wave Routing Method is selected.
For natural channels that vary in cross section dimension, slope, and storage, the number of Subreaches can

be treated as a calibration parameter. The number of Subreaches may be used to introduce numerical
attenuation which can be used to better represent the movement of floodwaves through the natural system.
A Cross Section Shape must be selected. If the Kinematic Wave Routing Method is selected, the options will
include Circle, Deep, Rectangle, Trapezoid, and Triangle. When the Muskingum-Cunge Routing Method is
selected, the options will include Circular, Rectangle, Tabular, Trapezoid, Triangle, and Eight Point. You will
have to enter a Manning's n Roughness Value for the channel. If the tabular shape is used, you will also have
to select multiple curves that describe the way in which discharge, area, and top width changes with
elevation. These curves must be defined as elevation-discharge, elevation-area, and elevation-width
functions, respectively, in the Paired Data Manager before they can be used in the reach element. These
curves must be monotonically increasing. Within each of the aforementioned curves, the x-axis defines the
elevation while the y-axis defines the variable of interest. Elevations must be monotonically increasing. If the
eight point cross section shape is used, you will also have to enter a roughness value for the left and right
overbank areas. You will have to enter other appropriate parameters data based on the cross section choice.
10.6.3 ModClark Transform

The ModClark Method is a linear, quasi-distributed Transform Method that is based on the Clark Conceptual
Unit Hydrograph. It fundamentally represents the subbasin as a collection of grid cells. The Clark Method
uses a time-area curve and the time of concentration to develop a translation hydrograph. By contrast, the
ModClark method eliminates the time-area curve and instead uses a separate travel time index for each grid
cell. The travel time index for each cell is scaled by the overall time of concentration. Excess precipitation
falling on each grid cell is lagged by the scaled time index and then routed through a linear reservoir. The
outputs from the linear reservoirs of the cells are combined to produce the final hydrograph.
The Time of Concentration defines the maximum travel time in the subbasin. The grid cell in the subbasin
with the largest travel time index will have exactly this specified time of concentration. All other grid cells will
have a scaled time of concentration based on the ratio of the cell's travel time index to the maximum travel
time index.
The Storage Coefficient is used in the linear reservoir for each grid cell. The same coefficient is used for all
cells in the subbasin.
Gridded Information (e.g. cell size and travel length) must be supplied using either a File-Specified
Discretization or a Structured Discretization. The Selecting a Discretization Method v4.7 (see page 283)
section describes these options in more detail.
The Component Editor is shown in the following figure.

255 ModClark Component Editor
10.6.4 SCS Unit Hydrograph Transform

The Soil Conservation Service (SCS) Unit Hydrograph Method defines a curvilinear unit hydrograph by first
setting the percentage of the unit runoff that occurs before the peak flow (NRCS, 2007). A triangular unit
hydrograph can then be fit to the curvilinear unit hydrograph so that the total time base of the unit
hydrograph can be calculated. The standard unit hydrograph is defined with 37.5% of unit runoff occurring
before the peak flow. This definition corresponds to a peak rate factor of 484 which incorporates the
percentage of unit runoff before the peak, calculated total time base, and unit conversions when applying the
equations within the US Customary unit system. An example of the Component Editor is shown below.

256 SCS Unit Hydrograph Component Editor
The percentage of unit runoff occurring before the peak flow is not uniform across all watersheds because it
depends on flow length, ground slope, and other properties of the watershed. By changing the percentage of
unit runoff before the peak, alternate unit hydrographs can be computed for watersheds with varying
topography and other conditions that effect runoff. The percentage of runoff occurring before the peak is
reflected in the Peak Rate Factor (PRF). It has been found that flat watersheds typically have a lower PRF
that may be as small as 100. Steeper watersheds have a larger PRF that may range up to 600. The default
unit hydrograph has a PRF of 484. Unit hydrographs with specific peak rate factors are defined in the
National Engineering Handbook (NRCS, 2007). A very specific case of the unit hydrograph for flat coastal
watersheds is known as the Delmarva Unit Hydrograph (Welle, Woodward, and Moody, 1980).
The Standard Lag is defined as the length of time between the centroid of precipitation mass and the peak
flow of the resulting hydrograph. Examination of the equations used in deriving the curvilinear unit
hydrograph show that the lag time can be computed as the duration of unit precipitation divided by two, plus
60% of the time of concentration.
10.6.5 Snyder Unit Hydrograph Transform

The Snyder Unit Hydrograph is a synthetic Unit Hydrograph Method. The original data only supported
computing the peak flow as the result of a unit of precipitation. Later, equations were developed to estimate
the time base of the hydrograph and the width at 50% of the peak flow. Since it does not compute all
ordinates of the hydrograph, a Clark Hydrograph is created in such a way that the Snyder properties are
maintained.
10.6.5.1 Standard
The Standard Method requires the user to estimate parameters using appropriate techniques. Many
approaches have been proposed for estimating the parameters, relying on different physical properties of the
watershed under consideration. The approaches are typically developed by fitting the unit hydrograph
parameters for a watershed with observed precipitation and discharge data. These approaches may be

effective at estimating parameters in ungaged watersheds if they are similar to the watersheds used to
develop the approach. The Component Editor is shown in the following figure.
257 Snyder Standard Method Component Editor
The Standard Lag is defined as the length of time between the centroid of precipitation mass and the peak
flow of the resulting hydrograph. Many relationships for estimating lag from subbasin characteristics have
been developed for different regions.
The Peaking Coefficient measures the steepness of the hydrograph that results from a unit of precipitation.
It ranges typically from 0.4 to 0.8 with lower values associated with steep-rising hydrographs. It is estimated
using the best judgement of the user, or possibly from locally-developed relationships to watershed physical
features.
10.6.5.2 Ft Worth District

The Ft Worth Method is the result of regional urban studies conducted by the U.S. Army Corps of Engineers,
Ft. Worth District in the Dallas-Ft Worth, Austin, and San Antonio areas. The method is applicable for
watersheds substantially similar to the watersheds included in the regional study. The user enters values for
five physical characteristics of a subbasin. Equations from the regional study use the parameter values to
calculate the Snyder Standard Lag. The Component Editor is shown in the following figure.

258 Snyder Ft Worth District Method Component Editor
The total Length is measured from the outlet of the subbasin, along the main watercourse to the most
hydraulically remote point on the subbasin boundary.
The Centroid Length is measured from the outlet of the subbasin, along the main watercourse, to a point
opposite the subbasin centroid.
The Weighted Slope is the slope of the main watercourse between points located at 10 percent and 85
percent of the length of the main watercourse, measured from the subbasin outlet.
Urbanization Percentage is estimated as the percentage of the subbasin where the drainage system has
been improved to more efficiently carry runoff to the outlet. Such improvements may include street gutters,
straightened channels, concrete lined channels, or other effeciencies. This parameter provides a way to
account for the effects of urbanization on the hydrologic response of the subbasin.
The Sand Percentage accounts for the effect of infiltration and surface runoff properties on hydrograph
generation. Zero percent indicates essentially all-clay soils with characteristically low infiltration rates.
Conversely, 100 percent indicates essentially all-sandy soils with characteristically high infiltration rates.
The Fort Worth method does not include estimation of the Peaking Coefficient. This parameter must be
estimated by another method and entered directly.
10.6.5.3 Tulsa District

The Tulsa Method is the result of regional urban studies conducted by the U.S. Army Corps of Engineers,
Tulsa District using watersheds across Oklahoma. The method is applicable for watersheds substantially
similar to the watersheds included in the regional study. The user enters values for four physical
characteristics of a subbasin. The values are used with equations developed in the regional study for
estimating the Standard Lag and Peaking Coefficient. The Component Editor is shown in the following
figure.

259 Snyder Tulsa District Method Component Editor
The total Length is measured from the outlet of the subbasin, along the main watercourse to the most
hydraulically remote point on the subbasin boundary.
The Centroid Length is measured from the outlet of the subbasin, along the main watercourse, to a point
opposite the subbasin centroid.
The Weighted Slope is the slope of the main watercourse between points located at 10 percent and 85
percent of the length of the main watercourse, measured from the subbasin outlet.
Channelization Percentage is estimated as the percentage of the subbasin where the drainage system has
been improved to more efficiently carry runoff to the outlet. Such improvements may include street gutters,
straightened channels, concrete lined channels, or other efficiencies. This parameter provides a way to
account for the effects of urbanization on the hydrologic response of the subbasin.
10.6.6 User-Specified S-Graph Transform

The User-Specified S-Graph Method is not synthetic. It uses a special summation unit hydrograph
(abbreviated as S-Graph) to represent the response of a subbasin to a unit of precipitation. The S-Graph is
defined with percentage of the time lag as the independent variable (x axis), and percentage of the
cumulative runoff volume as the dependent variable (y axis). Computationally, the S-Graph is scaled by a
specified time lag and then successive differences are taken along the curve to compute a unit hydrograph
directly from the scaled S-Graph. A given S-Graph is generally only applicable in a particular region with
subbasins that share certain characteristics.
The S-Graph must be chosen from a selection list of percentage curves defined previously in the Paired Data
Manager. While percentage curves are used for other applications in the program, in this case they represent
percentage of unit discharge versus percentage of time lag. You will not be able to use the selection list until

you create at least one S-Graph. If you wish, you can use the paired data button next to the selection list to
open a chooser that will assist in selecting the correct S-Graph. Click on a percentage curve to view its
description. Descriptions are particularly important for percentage curves because of the different
applications in the program.
10.6.6.1 Standard
There are two different methods for specifying the lag time to be applied to the S-Graph. The Standard
method allows the simple specification of the lag time in hours. The Lag Time is defined as the length of
time between the centroid of precipitation mass and the peak flow of the resulting hydrograph. An example
of this method is shown in the following figure.
260 User-Specified S-Graph Standard Method Component Editor
10.6.6.2 Regression
The Regression method provides for the automatic calculation of the lag time using an equation commonly
applied in regional regression studies. The equation is applied to the parameters within the context of the
U.S. Customary unit system. If parameters are entered in System International units, then the equation is
evaluated after converting the parameters to U.S. Customary equivalents. The equation takes the following
form for computing the lag time in hours:
The length of the longest flowpath in the subbasin is specified using the L parameter. The length along the
stream from the outlet to a point opposite the centroid is specified by the Lca parameter. A typical stream

slope must be specified as the s parameter. The C coefficient describes hydraulic efficiency of the stream
channel. The m and p parameters should be found through a regional regression study of watershed
properties and observed lag time. An example of this method is shown in the following figure.
261 User-Specified S-Graph Regression Method Component Editor
10.6.7 User-Specified Unit Hydrograph Transform

The User-Specified Unit Hydrograph Method is not a synthetic technique. Consequently, a separate unit
hydrograph must be developed for each subbasin. Ideally, these unit hydrographs are developed from
multiple storm observations when precipitation and flow have been measured at similar time intervals. The
unit hydrograph developed in this manner has a so-called duration that is equal to the duration of excess
precipitation. For example, a 3-hour duration unit hydrograph is generated by a precipitation event with 3
hours of excess precipitation.
A unit hydrograph must be defined in the Paired Data Manager before it can be used for a subbasin. An
example of a unit hydrograph in the Paired Data Manager is shown in the following figure. Notice the
duration and interval of the unit hydrograph are required. The duration must be set equal to the duration of
excess precipitation used to develop the unit hydrograph. The interval is the time interval of the ordinates of
the unit hydrograph. For example, a unit hydrograph developed from excess precipitation (which was
uniformly distributed in space and time) over a duration of 3 hours can have a time interval of 15 minutes.

262 Unit Hydrograph Paired Data Component Editor
Information required for the user-specified unit hydrograph method is the selection of a unit hydrograph from
the Paired Data Manager and the number of passes, as shown in the following figure. The unit hydrograph is
defined for the duration specified in the Paired Data Manager. The number of passes is meant to correct for
minor inflection points in the S-curve that is used to convert the unit hydrograph from the input duration to
the duration required as per the computational interval. For instance, if the unit hydrograph 3 hour duration
unit hydrograph is meant to be used within a simulation that has a computational interval of 1 hour, the unit
hydrograph must be converted from a 3 hour duration to a 1 hour duration. S-curves are used to perform this
conversion. If the S-curves derived from the 3 hour unit hydrograph contain inflection points, the resultant 1
hour unit hydrograph may display unwanted oscillations. A maximum of 20 passes is allowed. The unit
hydrograph must be entered in the Paired Data Manager before it can be selected in the Component Editor. If
you wish, you can use the Paired Data button next to the selection list to open a chooser to assist in
selecting the correct unit hydrograph.

263 User-Specified Unit Hydrograph Component Editor
10.6.8 2D Diffusion Wave Transform

The 2D Diffusion Wave Transform Method explicitly routes excess precipitation throughout a subbasin
element using a combination of the continuity and momentum equations. Unlike Unit Hydrograph
Transform Methods, this Transform Method can be used to simulate the non-linear movement of water
throughout a subbasin when exposed to large amounts of excess precipitation (Minshall, 1960). This
Transform Method can be combined with all Canopy, Surface, and Loss methods that are currently within
HEC-HMS. However, only the None, Linear Reservoir, and Constant Monthly Baseflow Methods can be used
with this Transform Method. For instance, the Deficit and Constant Loss Method can be used to convert
precipitation to excess precipitation, the Simple Canopy Method can extract infiltrated water through
evapotranspiration processes, the 2D Diffusion Wave Transform Method can be used to route surface flow,
and the Linear Reservoir Baseflow Method can be used to re-introduce infiltrated water as baseflow at the
subbasin outlet. Additionally, precipitation that does not initially infiltrate and becomes runoff can infiltrate
at a later time or within another grid cell. Spatial variables specific to 2D, such as water surface elevation,
hydraulic depth (computed as the volume of water within a cell / wetted area of the cell), and average
velocity within a cell, can be displayed within the map when using this Transform Method.
10.6.8.1 2D Mesh
The 2D Diffusion Wave Method represents the subbasin using a 2D mesh which is comprised of both grid
cells and cell faces. Grid cells do not have to have a flat bottom and cell faces do not have to be straight
lines with a single elevation. Instead, each grid cell and cell face is comprised of hydraulic property tables
that are developed using the details of the underlying terrain. This type of model is often referred to as a

“high resolution subgrid model” (Casulli, 2008). The term “subgrid” implies the use of a detailed underlying
terrain (subgrid) to develop the geometric and hydraulic property tables that represent the grid cells and the
cell faces. Currently, users must create a 2D mesh (and any associated connections) within HEC-RAS
(version 5.0.7 or newer) and then import to HEC-HMS38. In the future, users will be able to create and modify
both 2D meshes and boundary conditions entirely within HEC-HMS. The 2D mesh preprocessor within HEC-
RAS creates: 1) an elevation-volume relationship for each grid cell and 2) cross sectional information (e.g.
elevation-wetted perimeter, area, roughness, etc) for each cell face. The net effects of using a subgrid model
such as this are fewer computations, faster run times, greater stability, and improved accuracy. For more
information related to the development of a 2D mesh, users are referred to the HEC-RAS 2D Modeling User's
Manual39.
The 2D Diffusion Wave Transform can only be used with Unstructured or File-Specified Discretizations. An
Unstructured Discretization can be created by importing a 2D mesh from an HEC-RAS Unsteady Plan HDF file
using the File | Import | HEC-RAS HDF File option. Unsteady Plan HDF files have extensions of ".p##.hdf"
where "p##" corresponds to the specific plan of interest. When importing a 2D mesh from an HEC-RAS
Unsteady Plan HDF file, any accompanying boundary conditions for the selected 2D mesh (except for
precipitation time series) will be imported and used to create new 2D Connections with the same
parameterization. If a File-Specified Discretization is used, the backing file must be in an HDF 5 format and
created using either HEC-RAS or HEC-HMS. Pathnames to the HDF file must be limited to a maximum of 256
characters.
The 2D Diffusion Wave Component Editor is shown in the following figure.
264 2D Diffusion Wave Component Editor
Within this Component Editor, users must specify various computational tolerances and parameters for the
2D mesh associated with the subbasin.
38 https://www.hec.usace.army.mil/confluence/display/HMSUM/.Importing+HEC-RAS+HDF+Files+v4.8
39 https://www.hec.usace.army.mil/software/hec-ras/documentation/HEC-RAS%205.0%202D%20Modeling%20Users%20Manual.pdf

10.6.8.1.1 Implicit Weighting Factor
This parameter is used to weight the spatial derivatives between the current time step and the previously
computed time step. In many other applications, this parameter is also termed Theta. The default value for
this parameter is 1.0. However, the user can vary this parameter between 0.5 and 1.0. A value of 1.0 (which
is equivalent to the Backward Euler scheme) provides the most stable solution and will use only the current
time step for the spatial derivatives. A value of 0.5 (which is equivalent to the Crank-Nicholson method)
provides the most accurate solution of the equations but tends to be less stable. In most applications of real
world flood runoff events, a value of 1.0 will provide similar results as a value of 0.5. However, this
assumption should be tested for each model due to site specific geometry and flood propagation.
10.6.8.1.2 Water Surface Tolerance
The Water Surface Tolerance is used within the iteration scheme. The default value for this tolerance is
0.001. If the solution results in a numerical error that is less than the specified water surface tolerance, the
solver will move to the next time step. If the solution results in a numerical error that is greater than the
specified water surface tolerance, the solver will iterate over the same time step. The solver will only iterate
up to the specified maximum number of iterations.
10.6.8.1.3 Volume Tolerance
The Volume Tolerance is also used within the solver for the specific 2D mesh when iterating. The default
value for this tolerance is 0.001. The volume error computed by the solver is first converted to a depth using
the previous time step's water surface elevation and the elevation-volume curve for the cell. Then, the
change in water surface elevation is computed based on the current time step's volume error. If the solution
results in a numerical error that is less than the specified volume tolerance, the solver will move to the next
time step. If the solution results in a numerical error that is greater than the specified volume tolerance, the
solver will iterate over the same time step. The solver will only iterate up to the specified maximum number
of iterations.
10.6.8.1.4 Maximum Iterations
The specified Maximum Iterations will be used by the solver for the specific 2D mesh to get an answer that
has a numerical error less than the user specified tolerances at all locations. The default value for this
parameter is 20. However, the user can change it from 0 to 40. It is not recommended to change this
parameter unless you are sure that changing the value will either improve the chances that the model will
converge (i.e. increasing the value) or speed up the computations without causing any significant errors.
10.6.8.1.5 Time Step Method
Two methods can be used to control the time step: Adaptive Time Step and Fixed Time Step
10.6.8.1.5.1 Adaptive Time Step
When this option is selected, the time step can change based upon the Courant Number within all cells in the
2D mesh. The Adaptive Time Step option can be used to improve model stability as well as reduce

computational time. However, not all models will be faster with the use of the variable time step. Two
parameters are needed when using this method: Maximum Courant Number and Maximum Time Step.
Maximum Courant Number
This option specifies the Maximum Courant Number that is allowed within any cell in the 2D mesh. The
default value for this parameter is 1.0. If the maximum Courant number is exceeded, the computational
interval will be halved for the next time step. Because the solver uses an implicit solution scheme, Courant
numbers can be greater than 1.0 and still maintain a stable and accurate solution. In general, if the flood
wave is rising and falling slowly (depth and velocity are changing slowly), the solver can handle extremely
high Courant numbers. For these types of cases, users may enter a Courant number of 5.0 or more.
However, if the flood wave is very rapidly changing (depth and velocity are changing very quickly over time),
then a Courant number closer to 1.0 will be more appropriate.
Maximum Time Step
This option specifies the Maximum Time Step (i.e. computational interval) that will be used within the solver
for the specific 2D mesh.
10.6.8.1.5.2 Fixed Time Step
When this option is selected, the time step will not change throughout the simulation. Only one parameter is
needed when using this method: Time Step.
Time Step
This option specifies the Time Step (i.e. computational interval) that will be used within the solver for the
specific 2D mesh.
10.6.8.1.6 Use Warm Up Period
This option can be used to "ramp up" the water surface from a dry condition to a wet condition. By default,
no Warm Up Period will be used. When this option is enabled, two additional parameters are required: Warm
Up Period and Warm Up Period Fraction.
10.6.8.1.6.1 Warm Up Period
The default value for this parameter is blank (i.e. will not be used). This option allows the user to specify a
time (in hours) to run the computations for the 2D mesh while slowly transitioning any Flow 2D Connections
from zero to their initial value and/or any Stage 2D Connections from a dry elevation to their initial water
surface elevation. When using a Warm Up Period, a Warm up Period Fraction must also be specified.
10.6.8.1.6.2 Warm Up Period Fraction
This option is used in conjunction with the Warm Up Period. The default value for this parameter is blank
(i.e. will not be used). A value of 0.1 means that 10% of the specified warm up period time will be used to
"ramp up" the boundary conditions to their initial values. The remaining time will be used to hold the

boundary conditions constant but allow the flow to propagate throughout the 2D mesh, thus providing time
to stabilize to an appropriate initial condition.
10.6.8.1.7 Number of Cores
This option allows users to adjust the Number of Cores that are used by the solver. The default value for this
parameter will be set using the specified Number of Cores within the Tools | Program Settings | Defaults
menu. The number of available cores will be determined for each user's computer and used to populate this
drop down menu. Increasing the number of cores will result in more resources being allocated during a
compute that uses the 2D Diffusion Wave Transform. In general, as the number of cores is increased, the
compute will proceed faster. However, there is a point of diminishing returns; increasing the number of
cores past a certain point may result in decreased performance.
10.6.8.2 2D Connections
Within HEC-HMS, 2D Connections are used to supply boundary conditions as well as link other elements to/
from the 2D mesh. Currently, 2D Connections that are internal to the mesh (i.e. internal boundary conditions
within HEC-RAS) are not supported. All 2D Connections must be along the perimeter and external to the
mesh. The 2D Connection Component Editor is shown in the following figure.
265 2D Connection Component Editor

10.6.8.2.1 Downstream
10.6.8.2.2 Each 2D Connection can be connected to a downstream element through the

Downstream drop down menu. However, if an upstream element (e.g. subbasin,
junction, etc) is connected to a 2D Connection, the Downstream drop down will be
deactivated and not editable.
10.6.8.2.3 Type
Four types of 2D Connections are available for use: Flow, Normal Depth, Rating Curve, and Stage. For
example, if the user wanted to allow flow to leave the 2D mesh using a normal depth assumption, a Normal
Depth 2D Connection could be used. Also, if the user wanted to apply a time series of flow to a 2D mesh, a
Flow 2D Connection could be used. Finally, if an upstream element is connected to a 2D Connection, only
the Flow or Stage type can be selected.
10.6.8.2.3.1 Stage Hydrograph
A Stage Hydrograph 2D Connection allows the user to supply flow or allow flow to leave a 2D mesh. If the
water surface elevation supplied by the 2D Connection is higher than the cell water surface elevation (or dry
elevation), flow will go into the cell. When the water surface elevation supplied by the 2D Connection is lower
than the cell water surface elevation, flow will leave the cell. If a cell is dry and the water surface elevation
supplied by the 2D Connection is lower than the cell minimum elevation, no flow will transfer. Flow is
computed on a per cell basis. For instance, if the water surface elevation supplied by the 2D Connection is
higher in some of the connected cells but lower in other connected cells, water will simultaneously enter and
exit the Stage Hydrograph boundary.
When using this type of connection and an upstream element is not connected, a time series of stage must
be supplied.
When the Initial Stage option is set to Yes, the first stage in the associated hydrograph will be used to fill the
2D mesh as an initial condition. The filling starts at the 2D Connection and proceeds to fill any cell as long as
it is hydraulically connected. The filling stops when faces with a higher elevation are encountered that is
higher than the initial stage.
10.6.8.2.3.2 Flow Hydrograph
A Flow Hydrograph 2D Connection is generally used to supply flow into a 2D mesh. However, this type can
also be used to remove flow from a 2D mesh by using negative flow values.
When using this type of connection and an upstream element is not connected, a time series of flow must be
supplied.
The Energy Grade Slope is used to compute a normal depth from the given flow rate and the underlying
terrain data along the 2D Connection for each computational time step. This slope should be estimated at
the location of the 2D Connection. A flow distribution along the 2D Connection is then computed based on
the normal depth water surface elevation and the conveyance. The flow distribution is then used to
appropriately distribute the flow to cells along the 2D Connection that are wet. At any given time step, only a
portion of the 2D Connection may be wet, thus only the cells in which the water surface elevation is higher
than their outer boundary face terrain will receive water. However, if the computed normal depth water

surface elevation is higher than all the boundary face elevation data along the 2D Connection, then all the
cells will receive water based on a conveyance weighting approach.
10.6.8.2.3.3 Normal Depth
A Normal Depth 2D Connection can only be used to allow flow to leave a 2D mesh.
The Friction Slope is used to compute a normal depth water surface elevation given the underlying terrain
data along the 2D Connection for each computational time step. This slope should be estimated at the
location of the 2D Connection. Similar to a Stage Hydrograph 2D Connection, a Normal Depth 2D
Connection is applied on a per cell basis.
10.6.8.2.3.4 Rating Curve
A Rating Curve 2D Connection can only be used to allow flow to leave a 2D mesh. Similar to a Stage
Hydrograph 2D Connection, a Rating Curve 2D Connection is applied on a per cell basis.
10.6.8.2.4 Ratio of Subbasin Baseflow
The Ratio of Subbasin Baseflow is defined as the ratio of baseflow generated within the subbasin that will
reach the particular 2D Connection. The default value for this parameter is 0.0, which implies that no
baseflow generated within the subbasin will reach the particular 2D Connection. Conversely, a value of 1.0
implies that all baseflow generated within the subbasin will reach the particular 2D Connection. This
parameter cannot be used to remove or create mass within a subbasin; as such, the ratios of subbasin
baseflow for all 2D Connection in a particular 2D mesh or subbasin must sum to 1.0. However, when the
None baseflow method is selected for a subbasin, no checks regarding this parameter will be performed.
10.7 Selecting a Baseflow Method

interacting together, the actual subsurface calculations are performed by a Baseflow Method contained
within the subbasin. A total of six different Baseflow Methods are provided. Some of the methods are
designed primarily for simulating events while others are intended for continuous simulation.
The Baseflow Method for a subbasin is selected on the Component Editor for the subbasin element as
shown in the following figure. Access the Component Editor by clicking the subbasin element icon on the
element icon in the Basin Map, if the map is currently open. You can select a Baseflow Method from the list
of six available choices. If you choose the None method, the subbasin will not compute baseflow and the
outflow will only include direct runoff from the Transform Method. Use the selection list to choose the
method you wish to use. Each subbasin may use a different method or several subbasins may use the same
method.

266 Selecting the Baseflow Method in the Subbasin Component Editor
When a new subbasin is created, it is automatically set to use the default Baseflow Method specified in the
Program Settings. You may change the Baseflow Method for a subbasin at any time using the Component
Editor for the subbasin element. Since a subbasin can only use one Baseflow Method at a time, you will be
Program Settings. You can change the Baseflow Method for several subbasins simultaneously. Click on
the Parameters menu and select the Baseflow | Change Method command. The Baseflow Method you
choose will be applied to the selected subbasins in the Basin Model, or to all subbasins if none are currently
selected.
The parameters for each Baseflow Method are presented on a separate Component Editor from the
Subbasin Element editor. The Baseflow editor is always shown near the Transform editor. The information
shown on the baseflow editor will depend on which method is currently selected.
10.7.1 Bounded Recession Baseflow

The Bounded Recession Baseflow Method is intended primarily for real-time forecasting operations. The
method is very similar to the Recession Method, and like it, does not conserve mass in the subbasin. The
principal difference is that monthly baseflow limits can be specified. The baseflow is computed according to
the Recession Methodology and then the monthly limits are imposed. Though there are many similarities
with the Recession Method, one important difference is that this method does not reset the baseflow after a
storm event. The Component Editor is shown below.

267 Bounded recession baseflow method editor
The Initial Baseflow at the beginning of a simulation must be specified. Two methods are available for
specifying the initial condition: Initial Discharge and Initial Discharge Per Area. Using the first method, you
must specify the Initial Baseflow as a discharge with units of volume per time. This method is particularly
good when there is observed streamflow data at the outlet of the subbasin for determining the initial flow in
the channel. In the second method you specify the Initial Baseflow as a volume per area per time. This
method is better suited when general guidelines for watershed yield must be used to estimate the initial flow.
The Recession Constant describes the rate at which baseflow recedes between storm events. It is defined
as the ratio of baseflow at the current time, to the baseflow one day earlier.
A Baseflow Value must be entered for the month of January. Likewise, a value must also be entered for each
of the remaining months from February to December. This value is used to limit the computed baseflow.
10.7.2 Constant Monthly Baseflow

The Constant Monthly Baseflow Method allows the specification of a constant baseflow for each month of
the year. It does not conserve mass within the subbasin. It is intended primarily for continuous simulation in
subbasins where the baseflow is nicely approximated by a constant flow for each month. This Baseflow
Method can be combined with the 2D Diffusion Wave Transform Method. The Component Editor is shown
below.

268 Constant monthly baseflow method editor
A Baseflow Value must be entered for the month of January. Likewise, a value must also be entered for each
of the remaining months from February to December.
10.7.3 Linear Reservoir Baseflow

The Linear Reservoir Baseflow Method, as its name implies, uses a linear reservoir to model the recession of
baseflow after a storm event. It is the only Baseflow Method that conserves mass within the subbasin.
Infiltration or percolation computed by the Loss Method is connected as the inflow to the linear reservoirs. It
can be used with one, two, or three reservoirs. Partition fractions are used to split the inflow to each of the
reservoirs. The inflow is multiplied by the partition fraction to determine the amount of inflow going to each
reservoir. The sum of the partition fractions must be less than or equal to one. If the sum of the fractions is
less than one, the remaining percolated water is considered as aquifer recharge. If the sum of the fractions is
exactly equal to one, then all percolation will become baseflow and there will be no aquifer recharge. All
losses from the SCS Curve Number, Exponential, Initial and Constant, Green and Ampt, and Smith-Parlange
Loss Methods are routed to the Linear Reservoir Baseflow model. Only percolation losses (during saturated
conditions) in the Soil Moisture Accounting, Layered Green and Ampt, and Deficit and Constant Loss
Methods are routed to the Linear Reservoir Baseflow model.
Using the Linear Reservoir Baseflow Method with the Soil Moisture Accounting or Gridded Soil Moisture
Accounting Loss Methods results in special behavior. In this case, the number of baseflow reservoirs should
be consistent with the number of groundwater layers in the Loss Method. The lateral outflow from upper
groundwater is connected as the inflow to baseflow reservoir 1. The lateral outflow from lower groundwater
is connected as the inflow to baseflow reservoir 2. The percolation out of lower groundwater is connected as
inflow to baseflow reservoir 3. Partition fractions are not used for baseflow reservoirs 1 and 2 because their
inflow is determined by the respective lateral outflow. A partition fraction should be used with the percolation
in order to define the split between aquifer recharge and inflow to baseflow reservoir 3. The Component
Editor is shown below.

The Linear Reservoir Baseflow Method can be combined with the 2D Diffusion Wave Transform Method.
When it is, the Flow Type can be either Interflow or Baseflow. If the user chooses the Baseflow flow type,
then the routed subsurface water is added to the total flow at the subbasin outlet (outlet(s) of the 2D area). If
the user chooses the Interflow flow type, then the subsurface water is only routed within the 2D cell, where
the infiltration happened. The routed interflow is added to the cell's surface flow and routed on the 2D
surface to downstream grid cells (where it can be infiltrated again). The new Interflow Linear Reservoir
Baseflow option can only be activated when the 2D Diffusion Wave Transform option is selected.
269 Linear Reservoir Baseflow Method editor
The Number of Reservoirs (number of groundwater layers) must be specified. The minimum is one and the
maximum is three. Each groundwater layer requires separate initial conditions and parameters.
The Initial Baseflow at the beginning of a simulation must be specified for each groundwater layer. Two
methods are available for specifying the initial condition: Initial Discharge and Initial Discharge Per Area.
Using the first method, you must specify the initial baseflow as a discharge with units of volume per time.
This method is particularly good when there is observed streamflow data at the outlet of the subbasin for
determining the initial flow in the channel. In the second method you specify the initial baseflow as a volume
per area per time. This method is better suited when general guidelines for watershed yield must be used to

estimate the initial flow. The same method must be used for specifying the initial condition for all
groundwater layers.
The Fraction determines how water from the Loss Method is split to the groundwater layers. Each fraction
must be greater than zero and less than or equal one. When the sum of the fractions is exactly one then
there will be no aquifer recharge. When the sum of the fractions is less than one, the remainder of the
percolation becomes aquifer recharge.
The Groundwater Storage Coefficient is the time constant for each groundwater layer (linear reservoir
coefficient). Because it is measured in hours, it gives a sense of the response time for a component of
subsurface flow within a subbasin.
The Number of Steps can be used to subdivide the routing through a reservoir and is related to the amount
of attenuation during the routing. Minimum attenuation is achieved when only one routing step is selected.
Attenuation of the baseflow increases as the number of steps increases.
10.7.4 Nonlinear Boussinesq Baseflow

The Nonlinear Boussinesq Baseflow Method is designed to approximate the typical behavior observed in
watersheds when channel flow recedes after an event. It is similar to the Recession Baseflow Method, but by
assuming an unconfined groundwater layer and invoking the Boussinesq assumptions, it is possible to
parameterize the method using measurable field data. This method is intended primarily for event
simulation. However, it does have the ability to automatically reset after each storm event and consequently
may be used for continuous simulation. It does not conserve mass within the subbasin. The Component
Editor is shown in the following figure.
270 Nonlinear Boussinesq baseflow method editor

must specify the initial baseflow as a discharge with units of volume per time. This method is particularly
the channel. In the second method you specify the initial baseflow as a volume per area per time. This
There are two different methods for determining how to reset the baseflow during a storm event: Ratio to
Peak and Threshold Flow. When using the Ratio to Peak method, you must specify the flow ratio to the peak.
The baseflow is reset when the current flow divided by the peak flow is falls to the specified value. For
example, if a ratio of 0.2 is selected, the baseflow will be reset on the receding limb of an event hydrograph
when the flow has decreased to 20% of the event peak flow. With the Threshold Flow method, the baseflow
is always reset when the receding limb of the hydrograph falls to a specified flow value, regardless of the
peak flow during the previous storm event.
The Characteristic Subsurface Flow Length must be specified. This could be estimated as the mean
distance from the subbasin boundary to the stream.
The Conductivity of the soil must be specified. This could be estimated from field tests or from the soil
texture.
The Drainable Porosity must be specified in terms of volume ratio. The upper limit would be the total
porosity minus the residual porosity. The actual drainable porosity depends on local conditions.
10.7.5 Recession Baseflow

The Recession Baseflow Method is designed to approximate the typical behavior observed in watersheds
when channel flow recedes exponentially after an event. This method is intended primarily for event
simulation. However, it does have the ability to automatically reset after each storm event and consequently
may be used for continuous simulation. It does not conserve mass within the subbasin. The Component

271 Recession baseflow method editor
must specify the initial baseflow as a discharge with units of volume per time. This method is particularly
the channel. In the second method you specify the initial baseflow as a volume per area per time. This
The Recession Constant describes the rate at which baseflow recedes between storm events. It is defined
as the ratio of baseflow at the current time, to the baseflow one day earlier.
There are two different methods for determining how to reset the baseflow during a storm event: Ratio to
Peak and Threshold Flow. When using the Ratio to Peak method, you must specify the flow ratio to the peak.
The baseflow is reset when the current flow divided by the peak flow is falls to the specified value. For
example, if a ratio of 0.2 is selected, the baseflow will be reset on the receding limb of an event hydrograph
when the flow has decreased to 20% of the event peak flow. With the Threshold Flow method, the baseflow
is always reset when the receding limb of the hydrograph falls to a specified flow value, regardless of the
peak flow during the previous storm event.
10.8 References: Subbasin Elements

Casulli. 2008. A high-resolution wetting and drying algorithm for free-surface hydrodynamics. Int. J. Numer.
Meth. Fluids. 2008.
Flood Control District of Maricopa County (Maricopa County). 2011. Drainage Design Manual. Maricopa
County, AZ.
Minshall, N. E. (1960). Predicting Storm Runoff on Small Experimental Watersheds. ASCE Journal of the
Hydraulics Division, HY8, 17-37.

Natural Resources Conservation Service (NRCS). 2007. National Engineering Handbook: Chapter 16
Hydrographs. Washington, DC.
Welle, P., D. Woodward, and H. Moody. 1980. "A Dimensionless Unit Hydrograph for the Delmarva Peninsula."
American Society of Agricultural Engineers Paper 80-2013, St. Joseph, Michigan.

11 Reach Elements
A Reach is an element with one or more inflow and only one outflow. Inflow comes from other elements in
the Basin Model. If there is more than one inflow, all inflow is added together before computing the outflow.
Outflow is computed using one of the several available methods for simulating open channel flow.
Optionally, it may include a method for representing interactions with the subsurface. The Reach Element
can be used to model rivers and streams.
11.1 Selecting a Reach Routing Method

While a reach element conceptually represents a segment of stream or river, the actual calculations are
performed by a Routing Method contained within the reach. A total of nine different Routing Methods are
provided. Each of the methods implements a hydrologic Routing Methodology as compared to a hydraulic
approach that implements the full unsteady flow equations. Each method included in the program provides a
different level of detail and not all methods are equally adept at representing a particular stream.
The Routing Method for a reach is selected on the Component Editor for the reach element. Access
the Component Editor by clicking the Reach Element icon on the Components tab of the Watershed Explorer.
You can also access the Component Editor by clicking on the element icon in the Basin Map, if the map is
currently open. You can select a Routing Method from the list of seven available choices. If you choose the
None method, the reach will translate flow instantaneously and without attenuation. Use the selection list to
choose the method you wish to use. Each reach may use a different method or several reaches may use the
same method.
When a new reach is created, it is automatically set to use the default Routing Method specified in the
Program Settings. You may change the Routing Method for a reach at any time using the Component
Editor for the reach element. Since a reach can only use one Routing Method at a time, you will be warned
when changing methods that the old parameter data will be lost. You can turn off this warning in the
Program Settings. You can change the Routing Method for several reaches simultaneously. Click on
the Parameters menu and select the Routing | Change Method command. The Routing Method you choose
will be applied to the selected reaches in the basin model, or to all reaches if none are currently selected.
The parameters for each Routing Method are presented on a separate Component Editor from the Reach
Element editor. The Routing editor is always shown next to the Reach editor. The information shown on the
Routing editor will depend on which method is currently selected.
Reach Elements – 377

272 Reach Component Editor
11.1.1 Kinematic Wave Routing

The Kinematic Wave Routing Method approximates the full unsteady flow equations by ignoring inertial and
pressure forces. It also is assumed that the energy slope is equal to the bed slope. Consequently, this
method is best suited to fairly steep streams. It is often used in urban areas where natural channels have
been modified to have regular shapes and slopes. The Component Editor is shown in the following figure.
There are two options for an initial condition: Inflow Equals Outflow and Specified Discharge. If you use the
first option, it will be assumed that the initial outflow is the same as the initial inflow to the reach from
upstream elements. This is essentially the same as assuming a steady-state initial condition. If you use the
second option, you will also have to enter a discharge value. The Length should be the total length of the
reach element. Usually this value will be measured from maps of the watershed.

273 Kinematic wave routing method editor
The Slope should be the average friction slope for the whole reach. This value may be estimated from maps
if they provide sufficient vertical resolution. Field survey data may be necessary to actually determine
elevations of the channel bed for calculating the slope. If the slope varies significantly throughout the stream
represented by the reach, it may be necessary to use multiple reaches with different slopes.
The Manning's n Roughness Coefficient should be the average value for the whole reach. This value can be
estimated from pictures of streams with known roughness coefficient (Barnes, 1967) or by calibration.
The Number of Subreaches is used as a minimum when the program determines the distance step to use
during routing calculations. The distance step is first estimated from the travel time. If the estimated
distance step is greater than the length divided by the number of subreaches, then the distance step is
decreased appropriately. The travel time is computed from the Index Celerity. When Index Flow is entered,
the index flow is converted to index celerity using the properties of the reach.
Five options are provided for specifying the cross section shape: Circle, Deep, Rectangle, Trapezoid, and
Triangle. The Circle shape cannot be used for pressure flow or pipe networks, but is suitable for representing
a free water surface inside a pipe. The Deep shape should only be used for flow conditions where the flow
depth is approximately equal to the flow width. Depending on the shape you choose, additional information
Diameter (circle), Bottom Width (deep, rectangle, trapezoid), or Side Slope (trapezoid, triangle). The Side
11.1.2 Lag Routing

The Lag Routing Method only represents the translation of flood waves. It does not include any
representation of attenuation or diffusion processes. Consequently, it is best suited to short stream

segments with a predicable travel time that doesn't vary with flow depth. The Component Editor is shown in
274 Lag routing method editor
There are two options for initial condition: Inflow Equals Outflow and Specified Discharge. If you use the first
option, it will be assumed that the initial outflow is the same as the initial inflow to the reach from upstream
elements. This is essentially the same as assuming a steady-state initial condition. If you use the second
option, you will also have to enter a discharge value.
The Lag Routing parameter is the time (in minutes) that the inflow hydrograph will be translated. Inflow to
the reach is delayed in time by an amount equal to the specified lag, and then becomes outflow.
11.1.3 Lag and K Routing

The Lag and K Routing Method is a hydrologic storage Routing Method based on a graphical routing
technique that is extensively used by the National Weather Service. The method is a special case of the
Muskingum method where channel storage is represented by the prism component alone with no wedge
storage (i.e. Muskingum X = 0). The lack of wedge storage means that the method should only be used for
slowly varying flood waves. Like all hydrologic Routing Methods, it does not account for complex flow
conditions such as backwater effects and/or hydraulic structures. The Component Editor, when using
constant Lag and K values, is shown in the following figure.
275 Lag and K routing method editor

The Lag Term accounts for the travel time of the flood wave as it moves downstream. The K Term accounts
for attenuation of the flood wave. Lag and K parameters can be entered as constants or variable functions.
When using variable Lag and K functions, Lag is entered as an Inflow-Lag curve and K is entered as an
Outflow-Attenuation curve. Evaluation of historical flood hydrographs provides the basis for Lag and K
relationships within a reach. Care must be exercised when using lag functions with multiple intercepts (i.e.
lag is the same for more than one flow rate). This may result in numerically attenuated peak flow rates.
11.1.4 Modified Puls Routing

The Modified Puls Routing Method is also known as storage routing or level pool routing. It uses
conservation of mass and a relationship between storage and discharge to route flow through the stream
reach. Attenuation is achieved though the storage and delayed release of water in the reach instead of
through a rigorous conservation of momentum approach. It can be useful for representing backwater due to
flow constrictions in a channel so long as the backwater affects are fully contained within the reach.
A Storage-Discharge Function defines the amount of outflow for a specific amount of storage in the reach.
Storage is the independent variable and the values entered must cover the entire range of storages that may
be encountered during a simulation. Usually the first storage will be zero and the maximum storage should
be slightly more than the volume in the stream reach when it is at maximum flow. Generally, the outflow
values corresponding to each storage value are computed with the assistance of a hydraulic model that
computes water surface profiles. The function must be monotonically increasing. The storage-discharge
function must be defined in the Paired Data Manager before it can be used in the reach element.
276 Modified Puls routing method editor
The Number of Subreaches must be entered. It affects attenuation where one subreach gives the maximum
attenuation and increasing the number of subreaches approaches zero attenuation. This parameter is
necessary because the travel time through a subreach should be approximately equal to the simulation time

step for an idealized channel. An initial estimate of this parameter can be obtained by dividing the actual
reach length by the product of the wave celerity and the simulation time step. For natural channels that vary
in cross section dimension, slope, and storage, the number of subreaches can be treated as a calibration
parameter. The number of subreaches may be used to introduce numerical attenuation which can be used to
better represent the movement of floodwaves through the natural system.
There are two options for initial condition: Specified Discharge and Inflow Equals Outflow. If you use the first
option, you will also have to enter a discharge value. The initial storage in the reach will be calculated from
the specified discharge and the storage-discharge function. If you use the second option, it will be assumed
that the initial outflow is the same as the initial inflow to the reach from upstream elements. This is
essentially the same as assuming a steady-state initial condition. The initial storage will be computed from
the first inflow to the reach and storage-discharge function.
Optionally an Elevation-Discharge Function can be selected. If used, it should represent the depth of water
for any given outflow from the reach. The function must be monotonically increasing. The elevation-
discharge function must be defined in the Paired Data Manager before it can be used in the reach element.
If the optional Elevation-Discharge Function is selected, then an invert elevation should also be specified. The
flow depth is added to the invert elevation to compute the stage.
11.1.5 Muskingum Routing

The Muskingum Routing Method uses a simple conservation of mass approach to route flow through the
stream reach. However, it does not assume that the water surface is level. By assuming a linear, but non-
level, water surface it is possible to account for increased storage during the rising side of a flood wave and
decreased storage during the falling side. By adding a travel time for the reach and a weighting between the
influence of inflow and outflow, it is possible to approximate attenuation. The Component Editor is shown in
277 Muskingum routing method editor

The Muskingum K is essentially the travel time through the reach. It can be estimated from knowledge of the
cross section properties and flow properties. It may be a calibration parameter in some cases.
The Muskingum X is the weighting between inflow and outflow influence; it ranges from 0.0 up to 0.5. In
practical application, a value of 0.0 results in maximum attenuation and 0.5 results in no attenuation. Most
stream reaches require an intermediate value found through calibration.
The Number of Subreaches must be entered. It affects attenuation where one subreach gives more
attenuation and increasing the number of subreaches decreases the attenuation. An initial estimate of this
parameter can be obtained by dividing the actual reach length by the product of the wave celerity and the
simulation time step. For natural channels that vary in cross section dimension, slope, and storage, the
number of subreaches can be treated as a calibration parameter. The number of subreaches may be used to
introduce numerical attenuation which can be used to better represent the movement of floodwaves through
the natural system.
11.1.6 Muskingum-Cunge Routing

The Muskingum-Cunge Routing Method is based on the combination of the conservation of mass and the
diffusion representation of the conservation of momentum. It is sometimes referred to as a variable
coefficient method because the routing parameters are recalculated every time step based on channel
properties and the flow depth. It represents attenuation of flood waves and can be used in reaches with a
small slope. The Component Editor is shown below.
278 Muskingum-Cunge routing method editor

The Length should be the total length of the reach element. Usually this value will be measured from maps of
the watershed.
The Slope should be the average friction slope for the whole reach. This value may be estimated from maps
if they provide sufficient vertical resolution or by field surveying. If the slope varies significantly throughout
the stream represented by the reach, it may be necessary to use multiple reaches with different slopes.
The Manning's n Roughness Coefficient should be the average value for the whole reach. This value can be
estimated from pictures of streams with known roughness coefficient (Barnes, 1967) or by calibration. When
the Tabular shape is selected, no Manning's n roughness values need to be entered.
The Space-Time Interval selection provides three options. When the Auto DX Auto DT Method is selected,
the program will automatically select space and time intervals that maintain numeric stability. Alternately,
when the Specified DX Auto DT Method is selected, the program will use the specified number of
subreaches (i.e. DX) while automatically varying the time interval to take as long a time interval as possible
while also maintaining numeric stability. Finally, when the Specified DX Specified DT Method is selected, the
program will use the specified number of subreaches and subintervals throughout the entire simulation.
The Index Method is used in conjunction with the physical properties of the channel and the previously
mentioned space-time interval selection. The selected index method and specified parameter will be used by
the program to discretize the routing reach in both space and time. Appropriate reference flows and
celerities are dependent upon the physical properties of the channel as well as the event(s) in question.
Experience has shown that a reference flow (or celerity) based upon average values of the hydrograph in
question (i.e. midway between the base flow and the peak flow) is, in general, the most suitable choice.
Reference flows (or celerities) based on peak values tend to numerically accelerate the wave much more
than would occur in nature, while the converse is true if a low reference flow (or celerity) is used (Ponce,
1983).
Six options are provided for specifying the cross section shape: Circle, Eight Point, Rectangle, Tabular,
Trapezoid, and Triangle. The Circle shape cannot be used for pressure flow or pipe networks, but is suitable
for representing a free water surface inside a pipe. Depending on the shape you choose, additional
information will have to be entered to describe the properties of the cross section. This information may
include a Diameter (circle), Bottom Width (rectangle, trapezoid), or Side Slope (trapezoid, triangle). The Side
If the Tabular shape is used, you will also have to select multiple curves that describe the way in which
discharge, area, and top width changes with elevation. These curves must be defined as elevation-discharge,
elevation-area, and elevation-width functions, respectively, in the Paired Data Manager before they can be
used in the reach element. When routing sediment or computing losses through the bottom of the channel,
an elevation-wetted perimeter function must also be defined and selected. These curves must be
monotonically increasing. Within each of the aforementioned curves, the x-axis defines the elevation while
the y-axis defines the variable of interest. Elevations must be monotonically increasing.
The Eight Point shape requires a cross section simplified with only eight station-elevation values. The cross
section is usually configured to represent the main channel plus left and right overbank areas. A separate
Manning's n value is entered for each overbank. The cross section should extend from the channel invert up
to the maximum water surface elevation that will be encountered during a simulation. The cross section
must be created in the Paired Data Manager before it can be used in the reach.
Optionally, an Invert Elevation may be specified. When used, the flow depth computed during the routing is
added to the invert elevation to compute the stage.

11.1.7 Normal Depth Routing

The Normal Depth Routing Method uses a Modified Puls Routing approach where storage-discharge
relationships are developed using a normal depth assumption for the reach. The user enters geometric data
for the channel. HEC-HMS computes the storage-discharge relationship for the given channel using
Manning's equation for normal depth. HEC-HMS computes the number of Modified Puls subreaches by
dividing the travel time by the simulation time interval. The Component Editor is shown in the following
figure.
279 Normal Depth routing method editor
option, you will also have to enter a discharge value. The Length should be the total length of the reach
element. Usually this value will be measured from maps of the watershed or through GIS tools. The Slope
should be the average slope for the whole reach. This value may be estimated from GIS datasets if they
provide sufficient vertical resolution or by field surveying. If the slope varies significantly throughout the
stream represented by the reach, it may be necessary to use multiple reaches with different slopes. The
Manning's n Roughness Coefficient should be the average value for the whole reach. This value can be
estimated from pictures of streams with known roughness coefficient (Barnes, 1967), GIS datasets, or by
calibration. The Index Flow should represent the expected maximum flow in the reach. A storage-discharge
relationship will be created ranging from zero to 1.5 times the index flow. The travel time will be computed
using the reference flow, channel geometry, and reach length, from which the number of subreaches will be
automatically computed as the travel time divided by the simulation time interval.
Optionally, an Invert Elevation may be specified. The invert is referenced to the downstream end of the
routing reach. When used, the flow depth computed during the routing is added to the invert elevation to
compute the stage.

Five options are provided for specifying the cross section shape: Circle, Eight Point, Rectangle, Trapezoid,
and Triangle. The Circle shape cannot be used for pressure flow or pipe networks, but is suitable for
representing a free water surface inside a pipe. Depending on the shape you choose, additional information
Diameter (circle), Bottom Width (rectangle, trapezoid), or Side Slope (trapezoid, triangle). The Side Slope is
dimensionless and entered as the units of horizontal distance per one unit of vertical distance. The Eight
Point shape requires a cross section simplified with only eight station-elevation values. The cross section is
usually configured to represent the main channel plus left and right overbank areas. A separate Manning's n
value is required for each overbank when the eight point cross section shape is selected. The cross section
should extend from the channel invert up to the maximum water surface elevation that will be encountered
during a simulation. The cross section must be created in the Paired Data Manager before it can be used in
the reach.
11.1.8 Straddle Stagger Routing

The Straddle Stagger Method uses empirical representations of translation and attenuation processes to
route water through a reach. Inflow is delayed a specified amount of time. The delayed flows are averaged
over a specified amount of time to produce the final outflow. The Component Editor is shown in the
following figure.
The Lag parameter specifies travel time through the reach. Inflow to the reach is delayed in time by an
amount equal to the specified lag.
The Duration parameter specifies the amount of spreading in a flood peak as it travels through the reach.
The delayed inflows are averaged over this specified time duration. The duration parameter loses physical
meaning when it is greater than twice the lag time.
280 Straddle stagger routing method editor

11.2 Selecting a Loss-Gain Method

While a reach element conceptually represents a segment of stream or river, optional modeling of
interactions with the subsurface is performed by a Loss/Gain Method contained within the reach. A Loss/
Gain Method represents losses from the channel, additions to the channel from groundwater, or bi-
directional water movements depending on the specific implementation of a method. A total of three
different Loss/Gain Methods are provided. Each method included in the program provides a different level of
detail and not all methods are equally adept at representing a particular stream. Further, because of differing
data requirements, some Loss/Gain Methods are only compatible with certain Routing Methods.
The Loss/Gain Method for a reach is selected on the Component Editor for the reach element. Access
the Component Editor by clicking the reach element icon on the Components tab of the Watershed Explorer.
You can also access the Component Editor by clicking on the element icon in the Basin Map, if the map is
currently open. You can select a Loss/Gain Method from the list of three available choices. If you choose the
None method, the reach will perform routing calculations without including any losses or gains to the
channel. Use the selection list to choose the method you wish to use. Each reach may use a different method
or several reaches may use the same method.
When a new reach is created, it is automatically set to use the default Loss/Gain Method specified in the
Program Settings. You may change the Loss/Gain Method for a reach at any time using the Component
Editor for the reach element. Since a reach can only use one Loss/Gain Method at a time, you will be warned
when changing methods that the old parameter data will be lost. You can turn off this warning in the
Program Settings. You can change the Loss/Gain Method for several reaches simultaneously. Click on
the Parameters menu and select the Loss/Gain | Change Method command. The Loss/Gain Method you
choose will be applied to the selected reaches in the Basin Model, or to all reaches if none are currently
selected.
The parameters for each Loss/Gain Method are presented on a separate Component Editor from the Reach
Element editor. The Loss/Gain editor is always shown next to the Routing editor. The information shown on
the Loss/Gain editor will depend on which method is currently selected.
11.2.1 Constant Loss/Gain

The Constant Loss/Gain Method uses an empirical relationship to calculate channel loss using a fixed flow
rate reduction and a ratio of the flow. It does not include any capability to representing gaining streams. A
fixed flow rate is subtracted from the routed flow and then the remainder is multiplied by a ratio. The reduced
flow becomes the outflow for the reach. This method is compatible with all Routing Methods.
The Component Editor is shown below.

281 Loss/Gain Component Editor
The Flow Rate parameter specifies the amount of flow to be subtracted from the inflow. It may be zero or
greater than zero; if the specified value is zero then no flow rate reduction will occur. If the specified value is
greater than the inflow for a time step, then no outflow will result for that interval.
The Fraction is used to reduce the inflow in linear proportion to the flow rate. After the constant value is
subtracted from the routed inflow, the remainder is multiplied by the value one minus the fraction. The
fraction must be between zero and one.
11.2.2 Percolation Loss/Gain

The Percolation Method uses a constant infiltration rate in combination with the inundated area in the reach
to compute channel loss. It does not include any capability to representing gaining streams. This method is
only compatible with the Modified Puls and Muskingum-Cunge Routing Methods. When used with the
Modified Puls method, the optional Elevation-Discharge Function and Invert Elevation must be specified in
the routing parameters. The inundated area is calculated differently depending on the Routing Method. In
combination with the Modified Puls method, the current storage and outflow are combined with the
elevation-discharge curve to compute inundated area. With the Muskingum-Cunge method, the wetted
perimeter is multiplied by the reach length to compute area. The Component Editor is shown below.
282 Percolation loss/gain method editor.
The Rate parameter specifies percolation in terms of a flow rate per area. The inundated area is multiplied by
the rate to determine the channel loss for each time interval.

11.3 References: Reach Elements

Ponce, V.M., 1983. Development of Physically Based Coefficients for the Diffusion Method of Flood Routing.
Final Report to the USDA, Soil Conservation Service. Lanham, Maryland, September 1983.

12 Reservoir Elements
A Reservoir is an element with one or more inflow and one computed outflow. Inflow comes from other
elements in the Basin Model. If there is more than one inflow, all inflow is added together before computing
the outflow. It is assumed that the water surface in the reservoir pool is level. Several methods are available
for defining the storage properties of the reservoir. The element can be used to model reservoirs, lakes, and
ponds. Unregulated Outputs (see page 197) can also be computed for elements located downstream of
reservoirs. Access the Component Editor by clicking the Reservoir Element icon on the Components tab of
the Watershed Explorer (see figure).
283 Reservoir Component Editor using the outflow curve routing method with a storage-discharge function
12.1 Selecting a Reservoir Routing Method

While a reservoir element conceptually represents a natural lake or a lake behind a dam, the actual storage
simulation calculations are performed by a Routing Method contained within the reservoir. Five different
Routing Methods are available. The Outflow Curve Method is designed to simply represent the reservoir with
a known storage-outflow relationship. The Specified Release Method uses a specified discharge from the
reservoir and computes the storage that would result. The Outflow Structures Method is designed to
represent individual components of the outlet works. The Rule-Based Operations Routing Method extends
the outlet works components to also allow for rule-based operations of gates within those structures. There
is also a choice for the None Routing Method. This option assumes no storage in the reservoir and all inflow
is passed as outflow for each time interval of the simulation.
The Routing Method for a reservoir is selected on the Component Editor for the reservoir element. Access
the Component Editor by clicking the Reservoir Element icon on the Components tab of the Watershed
Explorer. You can also access the Component Editor by clicking on the element icon in the Basin Map, if the
map is currently open. You can select a Routing Method from the list of five available choices (Reservoir
Elements (see page 390), see figure). Use the selection list to choose the method you wish to use.
Reservoir Elements – 390

The parameters for each Routing Method are presented below the method selection list. The exact
parameter data displayed in the Component Editor depends on which method is selected. Some parameters
are common to more than one Routing Method. However, all possible required and optional data for each
Routing Method is described in the following sections.
12.2 Outflow Curve Routing

This Routing Method represents the reservoir or lake with a user-provided relationship between storage and
discharge. The water surface in the reservoir is assumed to be level. The relationship between discharge and
storage must be unique, which does not permit looped rating curves. Further, the relationship must be
monotonically increasing with storage. The user must develop the storage relationship external to the
program by considering all the possible outlets for water from the reservoir and combining them in a single
storage relationship. The simulation is accomplished with the Modified Puls algorithm using one routing
step.
12.2.1 Storage Method

There are four different options for specifying the storage relationship. The first option is the Storage-
Discharge choice. The user must select a Storage-Discharge curve from the available curves in the Paired
Data Manager. The second option is the Elevation-Storage-Discharge choice. The user must select both a
Storage-Discharge curve and Elevation-Storage curve from the Paired Data Manager. The third option is the
Elevation-Area-Discharge choice. In this case the user must select both an Elevation-Area curve and an
Elevation-Discharge curve from the Paired Data Manager. With this choice, the program automatically
transforms the elevation-area curve into an elevation-storage curve using the Conic Formula. The final option
is the Elevation-Storage-Area-Discharge choice. In this case the user must select a Storage-Discharge, an
Elevation-Storage curve, and an Elevation-Area curve from the Paired Data Manager. Regardless of which
option is selected, the routing is always performed using only the storage-discharge curve. After the routing
is complete using the storage-discharge curve, the program will compute the elevation and surface area for
each time step, depending on the selected storage method.
Interpolation is used when the Elevation-Storage-Discharge, Elevation-Area-Discharge, and Elevation-
Storage-Area-Discharge storage methods are used. This means that it is not necessary for the storage-
discharge and elevation-storage/area curves used to contain matching independent variables. The curves do
not need to have the same storage values in each curve, or even have the same number of rows. At compute
time, the curves selected by the user are combined into a single routing table with rows for: Elevation,
Storage, Area, and Discharge. The table is initially configured using the curve selected by the user as the
Primary Curve. The remaining column(s) are interpolated from the curve not selected as the primary curve.
Finally, the storage routing is completed from the combined table using the storage and outflow columns,
and then elevation and area is calculated from the computed storages where possible.
You must select appropriate functions to define the selected Storage Method. For example, if you select the
Elevation-Storage-Discharge method, you must select an elevation-storage and a storage-discharge paired
data function. Appropriate selection lists will be shown directly under the Storage Method selection list. Any
necessary paired data functions must be defined in the Paired Data Manager before they can be used in the
reservoir. Choose an appropriate function in each selection list. If you wish, you can use a chooser by
clicking the Paired Data button next to the selection list. A chooser will open that shows all of the paired data
functions of that type. Click on a function to view its description.

12.2.2 Initial Condition

The Initial Condition sets the amount of storage in the reservoir at the beginning of a simulation. Therefore,
the simplest option is to specify the Storage as a volume of water in the reservoir. For convenience, other
options are also provided. The Inflow=Outflow method takes the inflow to the reservoir at the beginning of
the simulation, and uses the storage-discharge curve to determine the storage required to produce that same
flowrate as the outflow from the reservoir. Some storage methods permit the specification of Elevation as
the initial condition. In this case, the elevation provided by the user is used to interpolate a storage value
from the elevation-storage curve. Other storage methods permit the specification of Discharge as the initial
condition. In this case, the storage is interpolated from the storage-discharge curve. The initial condition
options depend on the selected storage method and are shown in the table below.
Storage Method Available Initial Conditions
Storage-Discharge Discharge, storage, inflow = outflow
Elevation-Storage-Discharge Discharge, storage, elevation, inflow = outflow
Elevation-Area-Discharge Discharge, elevation, inflow = outflow
Elevation-Storage-Area-Discharge Discharge, elevation, inflow = outflow, storage
26 Available initial condition options for different storage methods used with the outflow curve routing method
12.3 Specified Release Routing

The Specified Release Routing Method is designed to model reservoirs where the total discharge is known
for each time interval of a simulation. Usually this method is used when the discharge is either observed or
completely specified by an external decision process. The method can then be used to preserve the specified
release and track the storage using the Inflow, Outflow, and Conservation of Mass.

There are two different options for specifying the storage relationship, as shown in the figure below. The first
option is the Elevation-Storage choice. The user must select an Elevation-Storage curve from the available
curves in the Paired Data Manager. After the routing is complete, the program will compute the elevation and
storage for each time interval. The second option is the Elevation-Area choice, which requires the selection
of an Elevation-Area curve from the available curves in the Paired Data Manager. With this choice, the
program automatically transforms the elevation-area curve into an elevation-storage curve using the Conic
Formula. After the routing is complete, the program will compute the elevation, surface area, and storage for
each time interval.
You must select an appropriate function to define the selected Storage Method. For example, if you select
the Elevation-Storage method you must select an appropriate elevation-storage paired data function that

defines the storage characteristics of the reservoir. The appropriate selection list will be shown directly
under the Storage Method selection list. The necessary paired data functions must be defined in the Paired
Data Manager before they can be used in the reservoir. Choose an appropriate function in each selection list.
If you wish, you can use a chooser by clicking the paired data button next to the selection list. A chooser will
open that shows all of the paired data functions of that type. Click on a function to view its description.

The Initial Condition sets the amount of storage in the reservoir at the beginning of a simulation. The
choices depend on the method selected for specifying the storage characteristics of the reservoir. When the
Elevation-Storage method is selected, you may choose to specify the Initial Elevation or the Initial Storage.
When the Elevation-Area method is selected, you must specify an Initial Elevation.
12.3.3 Discharge Gage Selection

You must select a Discharge Time-Series Gage as the outflow from the reservoir. The gage should record
the discharge to use for each time interval of the simulation. If there is missing data in the record and the
Basin Model options are set to replace missing data, a zero flow rate will be substituted for each missing
data value. If the Basin Model is not set to replace missing data, any missing data will cause the simulation
to stop and an error message will be displayed.
The Discharge Time-Series Gage must be defined in the Time-Series Manager before it can be used in the
Reservoir Editor (see figure below). Selecting the correct gage is performed on the Component Editor for the
Reservoir Element. Access the Component Editor by clicking the Reservoir Element icon on the
element icon in the Basin Map, if the map is currently open.
284 Reservoir Component Editor using the specified release routing method with an elevation-storage function

12.3.4 Discharge Limit Options

The Maximum Release setting is optional. It will cause a warning message during a simulation if the
specified release exceeds the setting value. The specified release from the time-series gage record will
always be discharged from the reservoir. However, the warning will occur when the specified release
exceeds the optional maximum release value.
The Maximum Capacity setting is optional. It will cause a warning message during a simulation if the
calculated storage exceeds the setting value. The storage is calculated for each time interval using
conservation of mass. The storage at the end of the previous time interval, and the inflow volume and
specified outflow volume for the current time interval, are used to calculate the storage at the end of the
current time interval. The calculated storage will not be changed when it exceeds the setting value. However,
the warning message will occur when the calculated storage exceeds the setting value.
12.4 Outflow Structures Routing

The Outflow Structures Routing Method is designed to model reservoirs with a number of uncontrolled
outlet structures. For example, a reservoir may have a spillway and several low-level outlet pipes. While there
is an option to include gates on spillways, the ability to control the gates within the Outflow Structures
Routing Method is limited. However, there is an ability to include a time-series of releases in addition to the
uncontrolled releases from the various structures. An external analysis may be used to develop the
additional releases based on an operations plan for the reservoir. Rule-based reservoir operations, including
gated outlets, can be simulated using Rule-Based Operations Routing (see page 413).
Additional features in the reservoir for culverts and pumps allow the simulation of interior ponds. This class
of reservoir often appears in urban flood protection systems. A small urban creek drains to a collection pond
adjacent to a levee where flood waters collect. When the main channel stage is low, water in the collection
pond can drain through culverts into the main channel. Water must be pumped over the levee when the main
channel stage is high.

There are two different options for specifying the storage relationship. The first option is the Elevation-
Storage choice, as shown in the following figure. The user must select an Elevation-Storage curve from the
available curves in the Paired Data Manager. After the routing is complete, the program will compute the
elevation and storage for each time interval. The second option is the Elevation-Area choice, which requires
the selection of an Elevation-Area curve from the available curves in the Paired Data Manager. With this
choice, the program automatically transforms the elevation-area curve into an elevation-storage curve using
the Conic Formula. After the routing is complete, the program will compute the elevation, surface area, and
storage for each time interval.

285 Reservoir Component Editor using the Outflow Structures Routing Method with three outlets, one spillway, and one dam top
representing an emergency spillway
You must select an appropriate function to define the selected Storage Method. For example, if you select
the Elevation-Storage method you must select an appropriate elevation-storage paired data function that
defines the storage characteristics of the reservoir. The appropriate selection list will be shown directly
under the Storage Method selection list. Any necessary paired data functions must be defined in the Paired
Data Manager before they can be used in the reservoir. Choose an appropriate function in each selection list.
If you wish, you can use a chooser by clicking the Paired Data button next to the selection list. A chooser will
open that shows all of the paired data functions of that type. Click on a function to view its description.

The Initial Condition sets the amount of storage in the reservoir at the beginning of a simulation. Therefore,
the simplest option is to specify the Storage as a volume of water in the reservoir. For convenience, other
options are also provided. The Inflow=Outflow method takes the inflow to the reservoir at the beginning of
the simulation, and determines the pool elevation necessary to cause that outflow through the outlet
structures. The pool elevation is then used in the elevation-storage curve to determine the matching storage.
The pool Elevation method can also be selected for the initial condition. In this case, the elevation provided
by the user is used to interpolate a storage value from the elevation-storage curve. The initial condition
options depend on the selected storage method and are shown in the following table.
Storage Method Available Initial Conditions
Elevation-Storage Elevation, storage, inflow = outflow
Elevation-Area Elevation, inflow = outflow
27 Available Initial Condition options for different storage methods used with the Outlet Structures Routing Method

12.4.3 Tailwater Method

The selected Tailwater Method determines how submergence will be calculated for the individual structures
specified as part of the reservoir. When a structure is submerged, the discharge through the structure will
decrease in accordance with the physics of the structure and the tailwater elevation for each time interval.
Only one tailwater method can be selected and it is applied to all structures specified as part of the reservoir.
The Assume None method is used in cases where reservoir tailwater has no affect on the reservoir outflow.
The Reservoir Main Discharge method is typically used with reservoirs that span the stream channel and are
not influenced by backwater from downstream sources. For such cases, the tailwater below the reservoir
only comes from the reservoir releases. A rating curve defined by an elevation-discharge paired data function
must be selected to convert reservoir outflow to stage. The elevation-discharge function must be defined
before it can be used in the reservoir. Choose an appropriate function in the selection list or use a chooser by
clicking the Paired Data button next to the selection list. The rating curve should be specified in the same
vertical datum as the function used to describe the storage characteristics of the reservoir.
The Downstream of Main Discharge method is typically used with reservoirs that represent an interior pond
or pump station, and the outflow from the reservoir will have a significant impact on the downstream stage.
In this case, the outflow from the reservoir is combined with all other inflows to the element downstream of
the reservoir. That combined inflow is used in combination with a rating curve to determine the stage for the
reservoir tailwater. The elevation-discharge function for the rating curve must be defined in the Paired Data
Manager before it can be used in the reservoir. Choose an appropriate function in the selection list or use a
chooser by clicking the Paired Data button next to the selection list. The rating curve should be specified in
the same vertical datum as the function used to describe the storage characteristics of the reservoir.
The Specified Stage method is typically used with reservoirs that represent an interior pond or pump station,
and the outflow from the reservoir will have minimal effect on the downstream stage. In this case, the
outflow from the reservoir is adjusted for submergence based on the stage specified in a stage time-series
gage. The gage must be defined in the Time-Series Data Manager before it can be used in the reservoir.
Choose an appropriate gage in the selection list or use a chooser by clicking the Gage Data button next to
the selection list. The stage should be specified in the same vertical datum as the function used to describe
the storage characteristics of the reservoir.
The Fixed Stage method is typically used with reservoirs that represent an interior pond or pump station. The
same stage is used for all time intervals in a simulation. In this case, the outflow from the reservoir is
adjusted for submergence based on the specified stage.
12.4.4 Auxiliary Discharge Location

All reservoirs have a primary discharge to the downstream. Flow through outlets, spillways, and other
structures leaves the reservoir and enters some type of channel. However, some reservoirs also have an
Auxiliary Discharge in addition to the primary discharge. The flow exiting through the Auxiliary Discharge
Location does not enter the same channel as the main discharge. The auxiliary discharge may be an
emergency spillway that enters a secondary channel that eventually enters the main downstream channel.
The auxiliary discharge could also be a withdrawal for urban consumptive use or possibly an agricultural
irrigation canal.
Each structure added to the reservoir can be designated to discharge to the Main or Auxiliary direction. The
default is for a structure to discharge in the Main direction. Optionally, one or more outlet structures can be
set to discharge in the Auxiliary direction. Both the Main and Auxiliary locations use separate tailwater
methods. An appropriate Tailwater selection should be made for the auxiliary location if it will be used. The
selection of Tailwater Method is independent for the two directions so they may be the same or different.

When a rating curve is used for the Tailwater Method, the rating curve should be appropriate for the main or
auxiliary location where it is selected for use.
12.4.5 Time Step Control

The Outflow Structures Routing Method uses an Automatic Adaption Time Step. The time step specified in
the Control Specifications is used during periods of a simulation when the reservoir pool elevation is
changing slowly. However, under conditions when the pool elevation is changing rapidly, such as during a
dam break, a shorter time step is used. The Automatic Adaption Time Step Method automatically selects an
interval based on the rates at which the pool elevation, storage, and outflow are changing. Results are always
computed at the time interval specified in the Control Specifications. Any adaptive steps taken between
these time intervals are used internally to obtain the solution but are not stored for later use or display. While
the Automatic Adaption Time Step Method yields very good results for the pool elevation and outflow, the
method may require many more calculations to obtain the results. For preliminary simulations, especially
those with a long time window, it may be advantageous to disable the adaptive time step portion of the
algorithm. This can be accomplished in the Reservoir Component editor (illustrated in the previous figure) by
selecting the Simulation Interval time step method. Simulations with a short time window or final
simulations with a long time window should use the Automatic Adaption Time Step Method to get the best
possible precision in the results.
12.4.6 Outlets
Outlets can be included in reservoirs using the Outflow Structures Routing Method. Outlets typically
represent structures near the bottom of the dam that allow water to exit in a controlled manner. They are
often called gravity outlets because they can only move water when the head in the reservoir is greater than
the head in the tailwater. Up to 10 independent outlets can be included in the reservoir. Select the number of
outlets you wish to include. An Outlets folder with icons for each outlet will be added to the Reservoir icon in
the Watershed Explorer. You will need to expand the Outlets folder and click on the individual outlet icon to
enter parameter data for it. There are two different methods for computing outflow through an outlet: Culvert
or Orifice.
12.4.6.1 Culvert Outlet

The Culvert Outlet allows for partially full or submerged flow through a culvert with a variety of cross-
sectional shapes. It can account for inlet controlled outflow or outlet control. A typical culvert outlet is shown

286 Outlet Component Editor with the Culvert Method selected
You must select a solution method for the culvert: Inlet Control, Outlet Control, or Automatic. You may select
Inlet Control if it is known that at all times during a simulation the culvert outflow will be controlled by a high
pool elevation in the reservoir. You may likewise select Outlet Control if it is known that at all times the
culvert outflow will be controlled by a high tailwater condition. In general, it is best to select Automatic
control and the program will automatically determine the controlling inlet or outlet condition.
You must select the Number of Identical Barrels. This can be used to specify several culvert outlets that are
identical in all parameters. There can be up to 10 identical barrels.
The Shape specifies the cross-sectional shape of the culvert: Arch, Box, Circular, Con-Span, Elliptical, High-
Profile Arch, Low-Profile Arch, Pipe Arch, or Semi-Circular. The shape you choose will determine some of
the remaining parameters in the Component Editor. The parameters you will need to enter are shown in the
previous figure.
The Chart specifies the FHWA chart identification number40. Only the charts that apply to the selected shape
will be shown in the selection list (illustrated in the previous figure).
The Scale specifies the FHWA scale identification number41. Only the scales that apply to the selected chart
number will be shown in the selection list.
Cross Section Shape Diameter Rise Span
Circular X
Semi Circular X
Elliptical X X
40 https://www.hec.usace.army.mil/confluence/rasdocs/ras1dtechref/latest/modeling-culverts/culvert-data-and-coefficients/fhwa-chart-
and-scale-numbers
41 https://www.hec.usace.army.mil/confluence/rasdocs/ras1dtechref/latest/modeling-culverts/culvert-data-and-coefficients/fhwa-chart-
and-scale-numbers

Cross Section Shape Diameter Rise Span
Arch X X
High-Profile Arch X
Low-Profile Arch X
Pipe Arch X
Box X X
Con Span X X
28 Listing of which parameters are required for each cross section shape
The Length of the culvert must be specified. This should be the overall length of the culvert including any
projection at the inlet or outlet.
The Inlet Elevation must be specified as the invert elevation at the bottom of the culvert on the inlet side. The
inlet side is always assumed to be in the reservoir pool. This should be measured in the same vertical datum
as the paired data functions defining the storage characteristics of the reservoir.
The Entrance Coefficient describes the energy loss as water moves into the inlet of the culvert. Values may
range from 0.2 up to 1.0.
The Exit Coefficient describes the energy loss that occurs when water expands as it leaves the culvert outlet.
Typically the value is 1.0.
The Outlet Elevation must be specified as the invert elevation at the bottom of the culvert on the outlet side.
The outlet side is always assumed to be in the reservoir tailwater. This should be measured in the same
vertical datum as the paired data functions defining the storage characteristics of the reservoir.
A Manning's n value should be entered that describes the roughness in the culvert. At this time, the same n
value must be used for the entire length of the culvert, as well as the entire top, sides, and bottom.
12.4.6.2 Orifice Outlet

The Orifice Outlet assumes sufficient submergence on the outlet for orifice flow conditions to dominate. It
should not be used to represent an outlet that may flow only partially full. The inlet of the structure should be
submerged at all times by a depth at least 0.2 times the diameter. A typical Orifice Outlet editor is shown in

287 Outlet Component Editor with the Orifice Method selected
You must select the Number of Barrels. This can be used to specify several culvert outlets that are identical
in all parameters. There can be up to 10 identical barrels.
The Center Elevation specifies the center of the cross-sectional flow area. This should be measured in the
same vertical datum as the paired data functions defining the storage characteristics of the reservoir. It is
used to compute the head on the outlet, so no flow will be released until the reservoir pool elevation is above
this specified elevation.
The Cross-Sectional Flow Area of the outlet must be specified. The orifice assumptions are independent of
the shape of the flow area.
The dimensionless Discharge Coefficient must be entered. This parameter describes the energy loss as
water exits the reservoir through the outlet.
12.4.6.3 Spillways
Spillways can be included in reservoirs using the Outflow Structures Routing Method. Spillways typically
represent structures at the top of the dam that allow water to go over the dam top in a controlled manner. Up
to 10 independent spillways can be included in the reservoir. Select the number of spillways you wish to
include. Select the number of outlets you wish to include. A Spillways folder with icons for each outlet will be
added to the Reservoir icon in the Watershed Explorer. You will need to expand the Spillways folder and click
on the individual spillway icon to enter parameter data for it. There are three different methods for computing
outflow through a spillway: Broad-Crested, Ogee, and User Specified. The Broad-Crested and Ogee methods
may optionally include gates. If no gates are selected, then flow over the spillway is unrestricted. When gates
are included, the flow over the spillway will be controlled by the gates. Up to 10 independent gates may be
included on a spillway.
12.4.6.3.1 Broad-Crested Spillway
The Broad-Crested Spillway allows for controlled flow over the top of the reservoir according to the weir flow
assumptions. A typical Broad-Crested Spillway editor is shown in the following figure.
The Crest Elevation of the spillway must be specified. This should be measured in the same vertical datum

288 Spillway Component Editor with the Broad-Crested Method selected
The Length of the spillway must be specified. This should be the total width through which water passes.
The Discharge Coefficient accounts for energy losses as water enters the spillway, flows through the
spillway, and eventually exits the spillway. Depending on the exact shape of the spillway, typical values range
from 1.10 to 1.66 in System International units (2.0 to 3.0 US Customary units).
12.4.6.3.2 Ogee Spillway
The Ogee Spillway allows for controlled flow over the top of the reservoir according to the weir flow
assumptions. However, the discharge coefficient in the weir flow equation is automatically adjusted when
the upstream energy head is above or below the design head. A typical Ogee Spillway editor is shown in the
following figure.
289 Spillway Component Editor with the Ogee Method selected
The ogee spillway may be specified with Concrete or Earthen Abutments. These abutments should be the
dominant material at the sides of the spillway above the crest. The selected material is used to adjust energy

loss as water passes through the spillway. The spillway may have one, two, or no abutments depending on
how the spillway or spillways in a reservoir are conceptually represented.
The ogee spillway is assumed to have an Approach Channel that moves water from the main reservoir to the
spillway. If there is such an Approach Channel, you must specify the Depth of the Channel, and the Energy
Loss that occurs between the main reservoir and the spillway. If there is no Approach Channel, the Depth
should be the difference between the spillway crest and the bottom of the reservoir, and the Loss should be
zero.
The Crest Elevation of the spillway must be entered. This should be measured in the same vertical datum as
the paired data functions defining the storage characteristics of the reservoir.
The Crest Length of the spillway must be specified. This should be the total width through which water
passes.
The Apron Elevation is the elevation at the bottom of the ogee spillway structure. This should be measured
in the same vertical datum as the paired data functions defining the storage characteristics of the reservoir.
The Apron Width must be specified. This should be the total width of the spillway bottom.
The Design Head is the total energy head for which the spillway is designed. The discharge coefficient will be
automatically calculated when the head on the spillway departs from the design head.
12.4.6.3.3 Specified Spillway
The User-Specified Spillway can be used to represent spillways with flow characteristics that cannot be
represented by the broad-crested or ogee weir assumptions. The user must create an elevation-discharge
curve that represents the spillway discharge as a function of reservoir pool elevation. At this time there is no
ability to include submergence effects on the spillway discharge. Therefore the User-Specified spillway
method should only be used for reservoirs where the downstream tailwater stage cannot affect the
discharge over the spillway. A typical User-Specified Spillway editor is shown in the following figure.
290 Spillway Component Editor with the User-Specified Method selected
The Rating Curve describing flow over the spillway must be created in the Paired Data Manager as an
elevation-discharge function. The function must be calculated external to the program on the basis of
advanced spillway hydraulics or experimentation. The Rating Curve is chosen from the selection list. If you
wish, you can use a chooser by clicking the paired data button next to the selection list. A chooser will open
that shows all of the paired data functions of that type. Click on a function to view its description.

12.4.6.4 Spillway Gates

Spillway Gates are an optional part of specifying the configuration of a spillway. They may be included on
either broad-crested or ogee spillways. The number of gates to use for a spillway is specified on the Spillway
editor. An icon for each gate will be added to the associated spillway icon in the Watershed Explorer. You will
need to click on the individual gate icon to enter parameter data for it. There are two different methods for
computing outflow through a gated spillway: Sluice or Radial. In both cases you may specify the number of
identical units; each identical unit has exactly the same parameters, including how the gate is controlled.
12.4.6.4.1 Controlling Spillway Gates
An important part of defining gates on a spillway is the specification of how each gate will operate. It is rare
that a gate is simply opened a certain amount and then never changed. Usually gates are changed on a
regular basis in order to maintain the storage in the reservoir pool at targets; usually seasonal targets will be
defined in the reservoir regulation manual. Under some circumstances, the gate operation may be changed
to prevent flooding or accommodate other special concerns.
Three gate methods are available: Fixed Opening, Percent Annual Pattern, and Percent Time Series.
The Fixed Opening control method only accommodates a single setting for the gate. The distance between
the spillway and the bottom of the gate is specified as the Opening. The same setting is used for the entire
simulation time window.
Percent Annual Pattern is defined by a Percent Pattern Paired Data curve. This defines a pattern of gate
openings expressed as a percent of the maximum. The gate settings are defined by the day of the year and
repeated for every year in the simulation period.
Percent Time Series is defined by a Percent Gage Time Series. This defines a series of specified percent
gate openings on a time-series basis instead of based on an annual pattern.
12.4.6.4.2 Sluice Gate
A Sluice Gate moves up and down in a vertical plane above the spillway in order to control flow. The water
passes under the gate as it moves over the spillway. For this reason it is also called a vertical gate or
underflow gate. The editor is shown in the following figure.

291 Sluice Gate Component Editor for spillways
The Width of the sluice gate must be specified. It should be specified as the total width of an individual gate.
The Gate Coefficient describes the energy losses as water passes under the gate. Typical values are
between 0.5 and 0.7 depending on the exact geometry and configuration of the gate.
The Orifice Coefficient describes the energy losses as water passes under the gate and the tailwater of the
gate is sufficiently submerged. A typical value for the coefficient is 0.8.
12.4.6.4.3 Radial Gate
A Radial Gate rotates above the spillway with water passing under the gate as it moves over the spillway.
This type of gate is also known as a Tainter Gate. The editor is shown in the following figure.
292 Radial Gate Component Editor for spillways
The Width of the radial gate must be specified. It should be specified as the total width of an individual gate.

The Gate Coefficient describes the energy losses as water passes under the gate. Typical values are
between 0.5 and 0.7 depending on the exact geometry and configuration of the gate.
The Orifice Coefficient describes the energy losses as water passes under the gate and the tailwater of the
gate is sufficiently submerged. A typical value for the coefficient is 0.8.
The pivot point for the radial gate is known as the Trunnion. The Height of the Trunnion above the spillway
must be entered.
The Trunnion Exponent is part of the specification of the geometry of the radial gate. A typical value is 0.16.
The Gate Opening Exponent is used in the calculation of flow under the gate. A typical value is 0.72.
The Head Exponent is used in computing the total head on the radial gate. A typical value is 0.62.
12.4.7 Dam Tops

Dam Tops can be included in reservoirs using the Outflow Structures Routing Method. These typically
represent the top of the dam, above any spillways, where water goes over the dam top in an uncontrolled
manner. In some cases it may represent an emergency spillway. Up to 10 independent dam tops can be
included in the reservoir. Select the number of dam tops you wish to include. A Dam Tops folder with icons
for each dam top will be added to the Reservoir icon in the Watershed Explorer. You will need to expand the
Dam Tops folder and click on the individual dam top icon to enter parameter data for it. There are two
different methods for computing outflow through a dam top: Level or Non-Level.
12.4.7.1 Level Dam Top

The Level Dam Top assumes flow over the dam can be represented as a broad-crested weir. The
calculations are essentially the same as for a Broad-Crested Spillway. They are included separately mostly
for conceptual representation of the reservoir structures. A typical Level Dam Top is shown in the following
figure.
293 Dam Top Component Editor with the Level Overflow Method selected
The Crest Elevation of the dam top must be specified. This should be measured in the same vertical datum
The Length of the dam top must be specified. This should be the total width through which water passes,
excluding any amount occupied by spillways if any are included.

The Discharge Coefficient accounts for energy losses as water approaches the dam top and flows over the
dam. Depending on the exact shape of the dam top, typical values range from 1.10 to 1.66 in System
International units (2.0 to 3.0 US Customary units).
12.4.7.2 Non-Level Dam Top

The Non-Level Dam Top assumes that the top of the dam can be well-represented by a cross section with
eight station-elevation pairs. A separate flow calculation is carried out for each segment of the cross section.
The broad-crested weir assumptions are made for each segment. A typical non-level dam top is shown in the
following figure.
A Cross Section must be selected which describes the shape of the top of the dam from abutment to
abutment of the dam, with a simplified eight point shape. The cross section should not include any spillways
that are part of the dam. It may be necessary to use multiple dam tops to represent the different sections of
the dam top between spillways. The cross section should extend from the dam top up to the maximum water
surface elevation that will be encountered during a simulation. The cross section must be defined in the
Paired Data Manager before it can be used in the Reservoir Element.
The Discharge Coefficient accounts for energy losses as water approaches the dam top and flows over the
dam. The same value is used for all segments of the dam top. Typical values range from 2.6 to 4.0
depending on the exact shape of the dam top.
294 Dam Top editor with the Non-Level Overflow Method selected
12.4.8 Pumps
Pumps can be included in reservoirs using the Outflow Structures Routing Method. These typically represent
pumps in interior ponds or pump stations that are intended to move water out of the reservoir and into the
tailwater when gravity outlets alone are not sufficient. Up to 10 independent pumps can be included in the
reservoir. Select the number of pumps you wish to include. A Pumps folder with icons for each pump will be
added to the Reservoir icon in the Watershed Explorer. You will need to expand the Pumps folder and click
on the individual pump icon to enter parameter data for it. There is only one method for computing outflow
through a pump: Head-Discharge Pump.

12.4.8.1 Head-Discharge Pump

The Head-Discharge Pump is designed to represent low-head, high-flow situations. This means that the
pump is designed for high flow rates against a relatively small head. The pump can be controlled to turn on
and shut off as the reservoir pool elevation changes. A typical Head-Discharge Pump is shown in the
following figure.
The Number of Identical Units must be specified. This allows data to be entered only once when there are
multiple pump units with exactly the same parameters.
295 Pump Component Editor with the Head-Discharge Method selected
The Intake Elevation defines the elevation in the reservoir pool where the pump takes in water. This should
be measured in the same vertical datum as the paired data functions defining the storage characteristics of
the reservoir.
The Line Elevation defines the highest elevation in the pressure line from the pump to the discharge point.
This should be measured in the same vertical datum as the paired data functions defining the storage
characteristics of the reservoir.
You must specify the Elevation When the Pump Turns On. This should be measured in the same vertical
datum as the paired data functions defining the storage characteristics of the reservoir. Once the pump turns
on, it will remain on until the reservoir pool elevation drops below the trigger elevation to turn the pump off.
You must specify the Elevation When the Pump Turns Off. This should be measured in the same vertical
datum as the paired data functions defining the storage characteristics of the reservoir. This elevation must
be lower than the elevation at which the pump turns on.
The specification of a Minimum Rest Time is optional. If it is used, once a pump shuts off it must remain off
the specified minimum rest time even if the reservoir pool elevation reaches the trigger elevation to turn the
pump on.
The specification of a Minimum Run Time is optional. If it is used, once a pump turns on it must remain on
the specified minimum run time even if the reservoir pool elevation drops below the trigger elevation to turn
the pump off. The only exception is if the pool elevation drops below the intake elevation, then the pump will
shut off even though the minimum run time is not satisfied.

The Equipment Loss includes all energy losses between the intake and discharge points, including the pump
itself. This loss is added to the head difference due to reservoir pool elevation and tailwater elevation to
determine the total energy against which the pump must operate.
The Head-Discharge Curve describes the capacity of the pump as a function of the Total Head. Total head is
the head difference due to reservoir pool elevation and tailwater elevation, plus equipment loss. A curve must
be defined as an elevation-discharge function in the Paired Data Manager before it can be selected for a
pump in the reservoir. You can press the Paired Data button next to the selection list to use a chooser. The
chooser shows all of the available elevation-discharge functions in the project. Click on a function to view its
description.
12.4.9 Dam Break

Dam Break can be included in reservoirs using the Outflow Structures Routing Method. Only one dam break
can be included in the reservoir. Choose whether you wish to include dam break. An icon for the dam break
will be added to the Reservoir icon in the Watershed Explorer. You will need to click on the dam break icon to
enter parameter data for it. There are two different methods for computing outflow through a dam break:
Overtop Breach and Piping Breach.
12.4.9.1 Overtop Dam Break

The Overtop Dam Break (illustrated in the following figure) is designed to represent failures caused by
overtopping of the dam. These failures are most common in earthen dams but may also occur in concrete
arch, concrete gravity, or roller compacted dams as well. The failure begins when appreciable amounts of
water begin flowing over or around the dam face. The flowing water will begin to erode the face of the dam.
Once erosion begins, it is almost impossible to stop the dam from failing. The method begins the failure at a
point on the top of the dam and expands it in a trapezoidal shape until it reaches the maximum size. Flow
through the expanding breach is modeled as weir flow.
The Top Elevation is the top of the dam face. The breach may be initiated at a lower elevation than the top
depending on the selection of the trigger. This information is used to constrain the top of the breach opening
as it grows. It should be measured in the same vertical datum as the paired data functions defining the
storage characteristics of the reservoir.

296 Dam Break Component Editor with the Overtop Breach Method selected
The Bottom Elevation defines the elevation of the bottom of the trapezoidal opening in the dam face when
the breach is fully developed. This should be measured in the same vertical datum as the paired data
functions defining the storage characteristics of the reservoir.
The Bottom Width defines the width of the bottom of the trapezoidal opening in the dam face when the
breach is fully developed.
The Left Side Slope is dimensionless and entered as the units of horizontal distance per one unit of vertical
distance. The Right Side Slope is likewise dimensionless and entered as the units of horizontal distance per
one unit of vertical distance.
The Development Time defines the total time for the breach to form, from initiation to reaching the
maximum breach size. It should be specified in hours.
There are three methods for triggering the initiation of the failure: Elevation, Duration at Elevation, and
Specific Time. Depending on the method you choose, additional parameters will be required. For the
Elevation method, you will enter an elevation when the failure should start. The breach will begin forming as
soon as the reservoir pool elevation reaches that specified elevation. For the Duration at Elevation method,
you will enter an elevation and duration to define when the failure should start. The reservoir pool will have to
remain at or above the specified elevation for the specified duration before the failure will begin. For the
Specific Time method, the breach will begin opening at the specified time regardless of the reservoir pool
elevation. When specifying an elevation, it should be measured in the same vertical datum as the paired data
functions defining the storage characteristics of the reservoir.
The Progression Method determines how the breach grows from initiation to maximum size during the
development time. Select the Linear method to have the breach grow in equal increments of depth and
width. Select the Sine Wave method to have the breach grow quickly in the early part of breach development
and more slowly as it reaches maximum size. The speed varies according to the first quarter cycle of a since
wave. Select the User Curve method to have the breach grow according to a specified pattern. You will need
to select a curve in the selection list, which will show all percentage curves defined in the Paired Data
Manager. The independent variable should range from 0 to 100 percent and define the percentage of the
development time. The dependent variable should define the percentage opening of the maximum breach
size. The function must be monotonically increasing.

12.4.9.2 Piping Dam Break

The Piping Dam Break is designed to represent failures caused by piping inside the dam. These failures
typically occur only in earthen dams. The failure begins when water naturally seeping through the dam core
increases in velocity and quantity enough to begin eroding fine sediments out of the soil matrix. If enough
material erodes, a direct piping connect may be established from the reservoir water to the dam face. Once
such a piping connect is formed it is almost impossible to stop the dam from failing. The method begins the
failure at a point in the dam face and expands it as a circular opening. When the opening reaches the top of
the dam, it continues expanding as a trapezoidal shape. Flow through the circular opening is modeled as
orifice flow while in the second stage it is modeled as weir flow.
The Piping Dam Break (illustrated below) uses many of the same parameters as the overtop dam break. The
Top Elevation, Bottom Elevation, Bottom Width, Left Slope, and Right Slope all are used to describe a
trapezoidal breach opening that will be the maximum opening in the dam. These are only used once the
piping opening transitions to an open breach. The parameters for Development Time, Trigger Method, and
Progression Method are also the same for defining when the failure initiates, how long it takes to attain
maximum breach opening, and how the breach develops during the development time. The remaining
parameters, unique to piping dam break, are described below.
297 Dam Break Component Editor with the Piping Breach Method selected
The Piping Elevation indicates the point in the dam where the piping failure first begins to form. This should
the reservoir.
The Piping Coefficient is used to model flow through the piping opening as orifice flow. As such, the
coefficient represents energy losses as water moves through the opening.
12.4.10 Dam Seepage

Dam Seepage can be included in reservoirs using the Outflow Structures Routing Method. Most dams have
some water seeping through the face of the dam. The amount of seepage depends on the elevation of water
in the dam, the elevation of water in the tailwater, the integrity of the dam itself, and possibly other factors. In
some situations, seepage from the pool through the dam and into the tailwater can be a significant source of

discharge that must be modeled. Interior ponds may discharge seepage water but in some situations water
in the main channel may seep through the levee or dam face and enter the pool. Both of these situations can
be represented using the dam seepage structure.
There can only be one dam seepage structure in a reservoir that must represent all sources and sinks of
seepage. When water seeps out of the reservoir, the seepage is automatically taken from the reservoir
storage and added to the main tailwater discharge location. This is the mode of seepage when the pool
elevation is greater than the tailwater elevation. Seepage into the reservoir happens when the tailwater
elevation is higher than the pool elevation. In this mode the appropriate amount of seepage is added to
reservoir storage, but it is not subtracted from the tailwater.
12.4.10.1 Tabular Seepage

The Tabular Seepage Method uses an elevation-discharge curve to represent seepage as shown in the
following figure. Usually the elevation-discharge data will be developed through a geotechnical investigation
separate from the hydrologic study. A curve may be specified for inflow seepage from the tailwater toward
the pool, and a separate curve selected for outflow seepage from the pool to the tailwater. The same curve
may be selected for both directions if appropriate. Any curve used for dam seepage must first be created in
the Paired Data Manager. If a curve is not selected for one of the seepage directions, then no seepage will be
calculated in that direction.
298 Dam Seepage Component Editor showing seepage into a reservoir
12.4.11 Additional Release

An Additional Release can be included in reservoirs using the Outflow Structures Routing Method. In most
situations a dam can be properly configured using various outlet structures such as spillways, outlets, etc.
The total outflow from the reservoir can be calculated automatically using the physical properties entered for
each of the included structures. However, some reservoirs may have an additional release beyond what is
represented by the various physical structures. In many cases this additional release is a schedule of
managed releases achieved by operating spillway gates. The additional release can be used in combination
with other outlet structures to determine the total release from the reservoir. Alternatively, the Rule-Based
Operations Routing (see page 413) options can be used to simulate these releases.
The additional release that will be specified must be stored as a discharge gage. The appropriate gage can
be selected in the editor as shown in the following figure. The gage must be defined in the Time-Series Data
Manager before it can be selected. You can press the Time-Series Data button next to the selection list to
use a chooser. The chooser shows all of the available discharge gages in the project. Click on a Gage to view
its description.

299 Additional Release Component Editor showing a selected discharge gage
12.4.12 Evaporation
Evaporation can be included in reservoirs using the Outflow Structures Routing Method. Additionally, the
reservoir must be set to use the Elevation-Area storage option. Water losses due to evaporation may be an
important part of the water balance for a reservoir, especially in dry or desert environments. The evaporation
losses are different from other structures because they do not contribute to either main or auxiliary outflow.
They are accounted separately and available for review with the other time-series results for the reservoir. An
evaporation depth is computed for each time interval and then multiplied by the current surface area.
12.4.12.1 Monthly Evaporation

The Monthly Evaporation Method can be used to specify a separate evaporation rate for each month of the
year, entered as a total depth for the month. The evaporation data must be developed through separate,
external analysis and entered as shown in the following figure.
300 Evaporation Component Editor showing the monthly Evaporation Method for a reservoir

12.5 Rule-Based Operations Routing

The Rule-Based Operations Routing Method is an extension of the Outflow Structures Routing Method (see
page 394) that allows the outlet structures to be controlled using a set of rules. A reservoir can operate
moveable gates to meet a number of objectives that can be seasonally-dependent, such as a desired volume
of storage, limits or targets for releases, downstream controls, and so on. The reservoir structures with
operable gates are the General Outlet, which is designed to duplicate outlet capacity curves from a water
control manual; the Gated Orifice Outlet, and Sluice Gates and Radial Gates atop Broad-Crested or Ogee
Spillways. The Rule-Based Operations method has all of the features and parameters of the Outflow
Structures method, with the addition of Zones, as well as the option to use the General Outlet and Gated
Orifice. Refer to the section of the documentation covering Outflow Structures for all other features.
The Rule-Based Operations routing method can be selected in the Reservoir Component Editor:
301 Reservoir Element Component Editor
The Component Editor for this methods shares most of its functionality and features with the Outflow
Structures routing method with a two notable differences. First, the inclusion of a Zone component, which
implements rules, and extra outlet types not available in the Outflow Structures method.
12.5.1 Zones
Zones are sets of homogeneous operation rules. The day of the year of the simulation and the current pool
elevation of the reservoir dictate which Zone the reservoir operations fall within. A reservoir may have as few

as one Zone, and potentially very many Zones to handle operations that vary during low flow, flood events, or
in response to seasonal conditions. By default a Reservoir element has no zones, but to use the Rule-Based
Operations method you will need to add at least one Zone using the spinner box in the reservoir element's
Component Editor. A typical Zone Component Editor is below:
302 Reservoir Element Component Editor Zone Tab
Each Zone is defined by a maximum elevation, which is a Daily Elevation Pattern Paired Data curve. The
reservoir identifies which Zone it is in based on the day's reservoir elevation, and finds the lowest Maximum
Elevation curve above the current elevation. There can be blanks in the maximum elevation curve, which
imply that the Zone is inactive for a given day.
Rules are added to a Zone by increasing the spinner. A Zone may have zero rules, in which case the reservoir
only attempts to reach the storage objective (guide curve).
12.5.1.1 Storage Objective

Zones have at minimum a Storage Objective (also called a rule curve). A Storage Objective is implemented
as a Storage Pattern Paired Data curve. It defines the reservoir's target storage for each day of the year.
Typically a reservoir will have a single storage objective that can be applied to each Zone, but for flexibility, a
different curve is allowed to be used for each Zone.
303 Reservoir Element Component Editor Storage Objective Tab
12.5.1.2 Rules
A Zone may have zero or more additional rules beyond a Storage Objective. There are eleven rule types that
can be used.

Rule Name Usage
--None-- Does not actually apply a rule. Generally don't use this.
Maximum Auxiliary Release If you have specified any outlet structures to use a reservoir
auxiliary, this controls the maximum amount that may be
released in that direction.
Maximum Downstream Flow Maximum allowed flow at a chosen element downstream of

the reservoir.
Maximum Main Release This controls the maximum amount of flow that may be
released in the main release direction.
Maximum Rate Flow Change Each time a gate change is made, this is the maximum amount
the release is allowed to change.
Minimum Auxiliary Release If you have specified any outlet structures to use a reservoir
auxiliary, this controls the minimum amount that may be
released in that direction.
Minimum Downstream Flow Minimum allowed flow at a chosen element downstream of

the reservoir.
Minimum Main Release This controls the minimum amount of flow that may be
released in the main release direction.
Specified Auxiliary Release If you have specified any outlet structures to use a reservoir
auxiliary, the reservoir will operate to release a specified
amount in that direction.
Specified Downstream Flow Specified target flow at an element downstream of the

reservoir that you choose.
Specified Main Release The reservoir will operate to release a specified flow in the
main direction.
Each rule has a Rule Type, and possibly additional parameters. For rules that are not downstream controls,
they typically have one extra parameter, as in this Maximum Main Release rule editor:

304 Rule Tab with Maximum Main Release Rule
For rules that operate for downstream controls, additional information is required:
305 Rule Tab with Maximum Downstream Flow Rule
12.5.2 Outlets
Four types of outlets are available in the Rule-Based Operations Routing Method. The General Outlet
and Gated Orifice Outlet have operable gates. The other two outlet types are identical to the outlets in the
Outflow Structures routing method.
12.5.2.1 General Outlet

The General Outlet is a simple outlet method that depends on two rating curves: a Minimum Discharge curve
and a Maximum Discharge curve. The reservoir operates a "virtual gate" that opens between 0 and 100%. At
0% and 100%, the reservoir releases the minimum and maximum discharges, respectively, for a given
elevation. The release for gate openings between 0 and 100% is linearly interpolated.

306 Outlet Tab with General Outlet Method
12.5.2.1.1 Gate Method
The General Outlet has three gate methods: Adjustable Gate Control, Percent Annual Pattern, and Percent
Time Series.
The Adjustable Gate Control requires the Initial Opening for the gate to be set and is used for initial release
computations until a gate change is applied. The frequency of gate adjustments is defined by the Min Time
Between Adjustments parameter.
12.5.2.2 Gated Orifice Outlet

The Gated Orifice Outlet applies the orifice flow equations to a gate-controlled outlet. See the notes in the
Orifice Outlet section of Outflow Structures Routing (see page 394) for details on this type of outlet. The gated
version of this outlet offers four types of gate controls: Adjustable Gate Control, Fixed Opening, Percent
Annual Pattern, and Percent Time Series. A typical Gated Orifice Outlet Component Editor is shown in the
following figure.

307 Outlet Tab with Gated Orifice Method
There are two dimensionless loss coefficients, the Gate Coefficient and the Orifice Coefficient.
When the outlet it not submerged, weir flow is applied, and the specified Weir Coefficient is used.
Two geometric parameters are required, the Width and the Invert Elevation. The Invert Elevation should be
measured in the same vertical datum as the paired data functions defining the storage characteristics of the
reservoir.
When the gate method is set to Fixed Opening, only one additional option is necessary, the Opening.
For adjustable gate methods, including Adjustable Gate Control, Percent Annual Pattern, and Percent Time
Series, a Maximum Opening is required.
12.5.3 Spillways
Both the Broad-Crested Spillway and Ogee Spillway have the option to specify gates that control the flow
over the spillway. The user can choose from Sluice Gates or Radial Gates to control the flow. The
parameters and geometry for the spillway gates are the same as for Outflow Structures Routing (see page 394)
and information can be found there.
With the Rule-Based Reservoir Operations routing method, four types of gate control methods are available:
Adjustable Gate Control, Fixed Opening, Percent Annual Pattern, and Percent Time Series. The Component
Editor for an Adjustable Gate Control applied to a Sluice Gate is shown below.

308 Adjustable Gate Control Component Editor
When the gate method is set to Fixed Opening, only one additional option is necessary, the Opening.
For adjustable gate methods, including Adjustable Gate Control, Percent Annual Pattern, and Percent Time
Series, a Maximum Opening is required.

13 Source, Junction, Diversion, and Sink Elements

Source Elements provide a way to add measured inflows to the flow network, or to represent upstream
boundary conditions. Junction Elements are used in the flow network to combine multiple inflows, often at a
confluence. The Diversion Element is used to represent locations in the flow network where water is
withdrawn from the channel, and may be discharged to a canal or stream. Finally, Sink Elements are used to
represent the outlet of a watershed. It is permissible to have more than one outlet in a Basin Model.
13.1 Source
A Source is an element with no inflow, one outflow, and is one of only two ways to produce flow in the Basin
Model. The source can be used to represent boundary conditions to the Basin Model such as measured
outflow from reservoirs or unmodeled headwater regions. The boundary condition can also represent
contributing area modeled in a separate Basin Model. Access the Component Editor by clicking the Source
Element icon on the Components tab of the Watershed Explorer.
309 Source Component Editor
13.1.1 Representative Area

Specification of a Representative Area for the source is optional. If the area is specified, then it will be
possible for the program to automatically compute drainage area at downstream elements. If the area is not
specified, then downstream elements will not have a drainage area. When the source represents a region
modeled separately, then the area should be equal to the drainage area at the source location in the
watershed. When the source is used to represent a spring, inter-basin transfer, or other movement of water,
then the area should usually be set to zero.
If you choose to include a representative area, specify the area on the Component Editor for the source
element. Access the Component Editor by clicking the Source Element icon on the Components tab of
the Watershed Explorer. You can also access the Component Editor by clicking on the element icon in the
Basin Map, if the map is currently open.
Source, Junction, Diversion, and Sink Elements – 420

13.1.2 Selecting an Inflow Method

While a source element conceptually represents a source of inflow to the flow network, the actual
calculations are performed by an inflow method contained within the source element. Three methods are
currently available for computing the inflow. The Source Method is selected on the Component Editor for the
Diversion Element. Access the Component Editor by clicking the Source Element icon on the
element icon in the Basin Map, if the map is currently open. You can select an Inflow Method from the list of
three available choices. If you choose the None method, the source will have a discharge of exactly zero into
the flow network throughout the simulation. Use the selection list to choose the method you wish to use.
Each source element may use a different method or several sources may use the same method.
The parameters for the Inflow Method are presented on a separate Component Editor from the Source
Element editor. The Inflow editor is always shown next to the Source editor. The information shown on the
Inflow editor will depend on which method is currently selected.
13.1.3 Discharge Gage

When the Discharge Gage method is selected for the source, you must select a Time-Series Discharge
Gage. The gage should record the discharge to use for each time interval during a simulation. If there is
missing data in the record and the Basin Model options are set to replace missing data, a zero flow rate will
be substituted for each missing data value. If the Basin Model is not set to replace missing data, any missing
data will cause the simulation to stop and an error message will be displayed.
The Time-Series Discharge Gage must be defined in the Time-Series Manager before it can be used in the
source element, as shown below. Selecting the correct gage is performed on the Component Editor for the
source element. Access the Component Editor by clicking the Source Element icon on the Components tab
of the Watershed Explorer. You can also access the Component Editor by clicking on the element icon in the
310 Selecting a discharge gage at a source
13.1.4 Constant Flow

When the Constant Flow method is selected for the source, you must enter a Flow Rate. The same flow rate
is used for all time steps during a simulation. Specify the Flow Rate on the Component Editor for the source

element. Access the Component Editor by clicking the Source Element icon on the Components tab of
the Watershed Explorer. You can also access the Component Editor by clicking on the element icon in the
311 Source editor using the Constant Flow Method
An Annual Adjustment Pattern is optional. Without a specified annual pattern, the same discharge value is
used for every time interval in the simulation. When a pattern is specified, the discharge value is multiplied by
the percentage found in the annual pattern for each time interval in the simulation. The annual pattern
provides a percentage that varies throughout the year. The percent annual pattern must be defined in the
Paired Data Manager before it can be used in the source element.
13.2 Junction
A Junction is an element with one or more inflows and only one outflow. All inflow is added together to
produce the outflow by assuming zero storage at the junction. It is usually used to represent a river or stream
confluence.
The junction element does not have any special data or properties; it only has the standard Component
Editor used by all elements. Access the Component Editor by clicking the Junction Element icon on the
Components tab of the Watershed Explorer (see figure below). You can also access the Component Editor
by clicking on the element icon in the Basin Map, if the map is currently open.
312 Junction Component Editor

13.3 Diversion
A Diversion is an element with two outflows, main and diverted, and one or more inflows. Inflow comes from
other elements in the Basin Model. If there is more than one inflow, all inflow is added together before
computing the outflows. Six methods are available for computing the diverted flow that will be taken out of
the channel. All flow that is not diverted becomes the main outflow. Diverted flow can be connected to an
element that is computationally downstream. The Diversion can be used to represent weirs or pump stations
that divert flow into canals or off-stream storage. The Diversion Element includes optional properties for
limiting the amount of diverted flow. Unregulated outputs (see page 197) can also be computed for elements
located downstream of diversions. Access the Component Editor by clicking the Diversion Element icon on
the Components tab of the Watershed Explorer (as shown in the following figure).
13.3.1 Connecting Diversion Flow

You may optionally choose to connect the diversion flow to another point in the element network. In this
case, the diversion flow can become inflow to a junction or other element. This can be useful for
representing water that is diverted at a point location in a watershed, moves through a separate channel
network, and rejoins the stream from which it was diverted. Properly configured, it can also be used to
represent inter-basin transfers. If you do not connect the diversion flow, then it is removed from the system
at the diversion element. In either case, the time-series of diversion flow is shown in the graph and time-
series tables for the Diversion Element. The amount of diversion flow is also shown in the Diversion Element
Summary Table.
The connection for diversion flow is specified on the Component Editor for the diversion element. Access
the Component Editor by clicking the Diversion Element icon on the Components tab of the Watershed
Explorer (illustrated in the following figure). You can also access the Component Editor by clicking on the
element icon in the Basin Map, if the map is currently open. The selection list includes all elements that are
computationally downstream of the Diversion Element. Select an element from the list to connect the
diversion flow to that element as an Inflow, or choose Not Connected.
313 Diversion Component Editor

13.3.2 Limiting Flow or Volume

Two options are available for limiting the amount of water removed from the channel as diversion flow. If
neither option is used, the diversion flow will not be limited. If one or both options are used, diversion flow
will be computed first without any limitations then reduced as necessary to meet the optional requirements.
The optional limitations are included on the Component Editor for the diversion element. Access
the Component Editor by clicking the Diversion Element icon on the Components tab of the Watershed
Explorer (as illustrated in the previous figure). You can also access the Component Editor by clicking on the
The first option for limiting diversion flow is the Specification of a Maximum Volume. Diversion flow is
computed normally and the cumulative volume of diverted flow is tracked. Once the cumulative volume
reaches the specified maximum volume, all future diversion flow will be set to zero.
The second option for limiting diversion flow is the Specification of a Maximum Allowed Flowrate. Diversion
flow is initially computed without limitation. For every time interval, the computed diversion flow is compared
to the specified maximum flow. If the computed flow is above the maximum flow, the diversion flow is
reduced to the specified maximum flow.
13.3.3 Selecting a Divert Method

While a Diversion Element conceptually represents a diversion from the stream or river, the actual
calculations are performed by a Divert Method contained within the Diversion Element. Six methods are
currently available for computing the diversion flow. The Divert Method is selected on the Component
Editor for the Diversion Element. Access the Component Editor by clicking the Diversion Element icon on the
Components tab of the Watershed Explorer (shown in the previous figure). You can also access
the Component Editor by clicking on the element icon in the Basin Map, if the map is currently open. You can
select a Divert Method from the list of six available choices. If you choose the None method, the diversion
will pass all flow down the main connection and no flow will be diverted. Use the selection list to choose the
method you wish to use. Each Diversion Element may use a different method or several diversions may use
the same method.
The parameters for the Divert Method are presented on a separate Component Editor from the Diversion
Element editor. The Divert editor is always shown next to the Diversion editor. The information shown on the
Divert editor will depend on which method is currently selected.
13.3.4 Constant Flow Divert

This method uses a Constant Diversion Flowrate for the entire simulation. It is best suited to event
simulation when the diversion flow is more likely to be constant. In cases where the diversion flowrate
changes during the year according to a reliable pattern, the optional Percentage Pattern can be used to
adjust the constant rate throughout the year. The Component Editor is shown in the following figure.
The Diversion Flowrate must be specified. It is entered on the Component Editor. If the total inflow to the
diversion element is less than the specified diversion flow, the diversion flow will be limited to the total
inflow.

314 Specifying the constant diversion flowrate without using the optional annual adjustment pattern
An Annual Adjustment Pattern is optional. Without a specified annual pattern, the same diversion flowrate is
used for every time interval in the simulation. When a pattern is specified, the diversion value is multiplied by
the percentage found in the annual pattern for each time interval in the simulation. The annual pattern
provides a percentage that varies throughout the year. The percent annual pattern must be defined in the
Paired Data Manager before it can be used in the source element.
13.3.5 Inflow Function Divert

This method uses a Functional Relationship Between Inflow and Diversion Flow to determine the amount of
flow to divert from the channel. The range of inflows specified in the function should cover the complete
range of total inflow from upstream elements. Usually the first inflow in the function should be zero. The last
inflow should be greater than the maximum anticipated inflow to the element. Diversion flow is the
dependent variable and must be specified for each corresponding inflow value. The determination of the
correct diversion flow for a specified inflow depends on how the diversion operates. Generally you must
compute the diversion for each inflow value using knowledge of the lateral weir, pump station, or other
structure that is represented by the diversion element. The Component Editor is shown in the following
figure.
Select the Inflow-Diversion Function from the list of available choices. The inflow-diversion function must be
specified in the Paired Data Manager before it can be selected in the Component Editor.
315 The Inflow-Diversion Function Divert editor

13.3.6 Lateral Weir Divert

The only method currently available for computing Flow Over the Lateral Weir is the Broad-Crested Spillway
Method. Flow depth in the channel is computed using a rating curve. It is assumed to be level with a uniform
head along the length of the weir computed using the rating curve. Tailwater is similarly computed using a
rating curve that represents the characteristics of the area where the weir discharges the diverted flow.
316 The Lateral Weir Divert Method editor
A Rating Curve must be selected for the channel. The curve should give the stage for the entire range of
inflows that will occur during a simulation. The curve must be monotonically increased. It must be defined in
the Paired Data Manager before it can be selected.
Optionally, a Rating Curve may be entered for Tailwater. The curve should give the tailwater stage in the area
where the diverted flow is discharged. It is used to automatically account for submergence of the weir. The
curve must be monotonically increasing. It must be defined in the Paired Data Manager before it can be
selected. If the optional rating curve is not specified, then flow over the weir is computed assuming no
tailwater influence.
The Crest Elevation of the Weir must be specified. This should be measured in the same vertical datum as
the paired data functions defining the rating curves.
The Length of the Weir must be specified. This should be the total width through which water passes.
The Discharge Coefficient accounts for energy losses as water enters the weir, flows over the weir, and then
exits. Depending on the exact shape of the weir, typical values range from 1.10 to 1.66 in System
International units (2.0 to 3.0 US Customary units).
13.3.7 Pump Station Divert

The Pump Station Divert Method is designed to represent one or more pump units extracting water from a
channel and discharging it into a canal or other open channel. Flow depth in the channel is computed using a
rating curve, then compared with the operating elevations for the pump. Tailwater is similarly computed
using a rating curve that represents the characteristics of the area where the pump discharges the diverted
flow. The Component Editor is shown in the figure below.

317 The Pump Station Divert Method editor
A Rating Curve must be selected for the Channel. The curve should give the stage for the entire range of
inflows that will occur during a simulation. The curve must be monotonically increased. It must be defined in
the Paired Data Manager before it can be selected. You can press the Paired Data button next to the
selection list to use a chooser. The chooser shows all of the available elevation-discharge functions in the
project. Click on a function to view its description.
Optionally, a Rating Curve may be entered for Tailwater. The curve should give the tailwater stage in the area
where the diverted flow is discharged. It is used to automatically account for submergence of the pump
discharge line. The curve must be monotonically increasing. It must be defined in the Paired Data Manager
before it can be selected. If the optional rating curve is not specified, then discharge from the pump is
computed assuming no tailwater influence on the discharge line.
The Number of Identical Units must be specified. This allows data to be entered only once when there are
multiple pump units with exactly the same parameters.
The Intake Elevation defines the elevation in the reservoir pool where the pump takes in water. This should
the reservoir.
The Line Elevation defines the highest elevation in the pressure line from the pump to the discharge point.
This should be measured in the same vertical datum as the paired data functions defining the storage
characteristics of the reservoir.
You must specify the Elevation When the Pump Turns On. This should be measured in the same vertical
datum as the paired data function defining the stage in the channel. Once the pump turns on, it will remain on
until the stage in the channel drops below the trigger elevation to turn the pump off.

You must specify the Elevation When the Pump Turns Off. This should be measured in the same vertical
datum as the paired data function defining the stage in the channel. This elevation must be lower than the
elevation at which the pump turns on.
The specification of a Minimum Rest Time is optional. If it is used, once a pump shuts off it must remain off
the specified minimum rest time even if the reservoir pool elevation reaches the trigger elevation to turn the
pump on.
The specification of a Minimum Run Time is optional. If it is used, once a pump turns on it must remain on
the specified minimum run time even if the reservoir pool elevation drops below the trigger elevation to turn
the pump off. The only exception is if the pool elevation drops below the intake elevation, then the pump will
shut off even though the minimum run time is not satisfied.
The Equipment Loss includes all energy losses between the intake and discharge points. These losses are
are sometimes called static losses because the do not change very much even as the water surface
elevation in the channel fluctuates. Components of the loss include entrance losses to the suction line,
losses in the pump itself, pipe friction losses, bend losses in the line, and exit losses at the end of the
discharge line. This loss is added to the dynamic head to determine the total head against which the pump
must operate.
The Head-Discharge Curve describes the pumping capability of the pump as a function of the total head.
The total head is the sum of the equipment loss and the dynamic head. The dynamic is head is first
estimated as the difference between the water surface elevation in the channel and the line elevation. If the
water surface elevation is above the line elevation, then the estimated value will be zero. Secondarily, the
estimate is adjusted for tailwater submergence. This second stage is only necessary if an optional tailwater
rating curve is specified. When specified, the tailwater water surface elevation is compared to the line
elevation. If the tailwater exceeds the line elevation, then the depth of submergence over the line elevation is
added to the initial estimate of the dynamic head. The head-discharge curve is used to calculate the diverted
flow given the calculated total head. A curve must be defined as an elevation-discharge function in the
Paired Data Manager before it can be selected for a pump in the Diversion Element. You can press the
Paired Data button next to the selection list to use a chooser. The chooser shows all of the available
elevation-discharge functions in the project. Click on a function to view its description.
13.3.8 Specified Flow Divert

The Specified Flow Diversion Method is designed for situations where the flow diverted from the channel is
measured with a flow gage. Alternately, it can be used if the diversion flow is calculated externally from the
program. In either case, the user may enter a time-series of discharges to be diverted from the channel. If the
specified diversion discharge exceeds the total inflow to the diversion, then diversion will be limited to the
inflow volume. The Component Editor is shown in the following figure.
318 The Specified Flow Divert Method editor

The Time-Series Discharge Gage representing the diversion flows must be defined in the Time-Series
Manager before it can be used in the diversion element, as shown in the previous figure. Selecting the
correct gage is performed on the Component Editor for the Diversion Element. Access the Component
Editor by clicking the Diversion Element icon on the Components tab of the Watershed Explorer. You can
also access the Component Editor by clicking on the element icon in the Basin Map, if the map is currently
open.
13.4 Sink
A Sink is an element with one or more inflows but no outflow. Multiple inflows are added together to
determine the total amount of water entering the element. Sinks can be used to represent the lowest point of
an interior drainage area or the outlet of the basin model.
The sink element does not have any special data or properties; it only has the standard Component
Editor used by all elements. Access the Component Editor by clicking the Sink Element icon on the
319 Sink Component Editor

14 Meteorology Description
This chapter describes how meteorology information is entered into the program using a Meteorologic
Model. The Meteorologic Model is responsible for preparing the boundary conditions that act on the
watershed during a simulation. Consequently, a Meteorologic Model is prepared for use with one or more
Basin Models. If the Basin Model contains subbasin elements, then the Meteorologic Model must specify
how precipitation will be generated for each subbasin (only when using non-gridded
methods). Evapotranspiration should be included if the Basin Model is configured for continuous simulation
using any of the following loss methods: Deficit Constant, Gridded Deficit Constant, Soil Moisture
Accounting, Gridded Soil Moisture Accounting.
14.1 Meteorologic Models

Meteorologic Models are one of the main components in a project. The principle purpose is to prepare
meteorologic boundary conditions for subbasins. Consequently, you must create at least one Basin Model
before creating a Meteorologic Model. A Meteorologic Model can be used with many different Basin Models.
However, results computed by the Meteorologic Model will be matched with the subbasins in the Basin
Models using the name of the subbasin. If subbasins in different Basin Models have the same name, they
will both receive the same boundary conditions from the Meteorologic Model. Careful naming of subbasins
is necessary so that the the correct boundary conditions are computed for each one.
14.1.1 Creating a New Meteorologic Model

A new Meteorologic Model is created using the Meteorologic Model Manager. To access the manager, click
on the Components menu and select the Meteorologic Model Manager command. The manager will open
and show all of the Meteorologic Models currently in the project. The manager can remain open while you
manage Meteorologic Models or while you perform tasks elsewhere in the program. You can close the
manager using the X button in the upper right corner. The buttons to the right of the model list can be used to
manage existing models or create a new one. To create a new Meteorologic Model, press the New button.
After you press the button a window will open where you can name and describe the new Meteorologic
Model that will be created. A default name is provided for the new model; you can use the default or replace
it with your own choice. A description can also be entered. If the description is long, you can press the button
to the right of the description field to open an editor. The editor makes it easier to enter and edit long
descriptions. When you are satisfied with the name and description, press the Create button to finish the
process of creating the new Meteorologic Model. You cannot press the Create button if no name is specified
for the new model. If you change your mind and do not want to create a new Meteorologic Model, press
the Cancel button or the X button in the upper right to return to the Meteorologic Model Manager window.
Meteorology Description – 430

320 Creating a new Meteorologic Model
14.1.2 Copying a Meteorologic Model

There are two ways to copy a Meteorologic Model. Both methods for copying a model create an exact
duplicate with a different name. Once the copy has been made it is independent of the original and they do
not interact.
The first way to create a copy is to use the Meteorologic Model Manager, which is accessed from
the Components menu. Select the Meteorologic Model you wish to copy by clicking on it in the list of current
Meteorologic Models. The selected model is highlighted after you select it. After you select a model you can
press the Copy button on the right side of the window. A new Copy Meteorologic Model window will open
where you can name and describe the copy that will be created. A default name is provided for the copy; you
can use the default or replace it with your own choice. A description can also be entered; if it is long you can
use the button to the right of the description field to open an editor. When you are satisfied with the name
and description, press the Copy button to finish the process of copying the selected Meteorologic Model.
You cannot press the Copy button if no name is specified. If you change your mind and do not want to copy
the selected Meteorologic Model, press the Cancel button or the X button in the upper right to return to
the Meteorologic Model Manager window.
321 Creating a copy of a Meteorologic Model
Meteorologic Model you wish to copy, then press the right mouse button. A context menu is displayed that
contains several choices including Copy. Click the Create Copy command. A new Copy Meteorologic
Model window will open where you can name and describe the copy that will be created. A default name is
selected Meteorologic Model. You cannot press the Copy button if no name is specified. If you change your

mind and do not want to copy the selected Meteorologic Model, press the Cancel button or the X button in
the upper right of the Copy Meteorologic Model window to return to the Watershed Explorer.
322 Copying a Meteorologic Model from the Watershed Explorer
14.1.3 Renaming a Meteorologic Model

There are two ways to rename a Meteorologic Model. Both methods for renaming a model change its name
and then all references to the old model name are automatically updated to the new name.
The first way to perform a rename is to use the Meteorologic Model Manager, which you can access from
the Components menu. Select the Meteorologic Model you wish to rename by clicking on it in the list of
current Meteorologic Models. The selected model is highlighted after you select it. After you select a model
you can press the Rename button on the right side of the window. A new Rename Meteorologic
Model window will open where you can provide the new name. If you wish you can also change the
the Rename button to finish the process of renaming the selected Meteorologic Model. You cannot press
Meteorologic Model, press the Cancel button or the X button in the upper right of the Rename Meteorologic
Model window to return to the Meteorologic Model Manager window.
323 Renaming a Meteorologic Model

The second way to rename is from the Components tab of the Watershed Explorer. Select the Meteorologic
Model you wish to rename by clicking on it in the Watershed Explorer; it will become highlighted. Keep the
mouse over the selected model and click the right mouse button. Select the Rename command from the
menu and the highlighted name will change to editing mode as shown in the following figure. You can then
move the cursor with the arrow keys on the keyboard or by clicking with the mouse. You can also use the
mouse to select some or all of the name. Change the name by typing with the keyboard. When you have
finished changing the name, press the Enter key to finalize your choice. You can also finalize your choice by
clicking elsewhere on the Components tab. If you change your mind while in editing mode and do not want to
rename the selected Meteorologic Model, press the Escape key.
324 Renaming a Meteorologic Model in the Watershed Explorer
14.1.4 Deleting a Meteorologic Model

There are two ways to delete a Meteorologic Model. Both methods for deleting a model remove it from the
project and then automatically update all references to that model. Once a model has been deleted it cannot
be retrieved or undeleted. Any references to the deleted model will switch to using no Meteorologic Model,
which is usually not a valid choice during a simulation. At a later time you will have to go to those
components and manually select a different Meteorologic Model.
The first way to perform a deletion is to use the Meteorologic Model Manager, which you can access from
the Components menu. Select the Meteorologic Model you wish to delete by clicking on it in the list of
current Meteorologic Models. The selected model is highlighted after you select it. After you select a model
you can press the Delete button on the right side of the window. A window will open where you must confirm
that you wish to delete the selected model. Press the OK button to delete the model. If you change your mind
and do not want to delete the selected Meteorologic Model, press the Cancel button or the X button in the
upper right to return to the Meteorologic Model Manager window.

325 Preparing to delete a meteorologic model from the Meteorologic Model Manager
The second way to delete a Meteorologic Model is from the Components tab of the Watershed Explorer.
Select the Meteorologic Model you wish to delete by clicking on it in the Watershed Explorer; it will become
highlighted. Keep the mouse over the selected model and click the right mouse button. A context menu is
displayed that contains several choices including Delete. Click the Delete command. A window will open
where you must confirm that you wish to delete the selected model. Press the OK button to delete the model.
If you change your mind and do not want to delete the selected Meteorologic Model, press the Cancel button
or the X button in the upper right to return to the Watershed Explorer.
326 Deleting a Meteorologic Model in the Watershed Explorer
14.1.5 Importing a Meteorologic Model

You can import a Meteorologic Model from another project into the current project. The model must have
been created previously and stored on your computer or an accessible network location. Click the File menu
and select the Import | Meteorologic Model command. A file browser will open that you can use to find the

model you wish to import. The browser will only allow you to select Meteorologic Model files which end with
the MET extension. When you click on a Meteorologic Model file in the browser, the description of the model
is shown on the right side of the browser. Once you have located and selected the desired Meteorologic
Model, press the Select button. If you change your mind, you can press the Cancel button or the X button in
the upper right to return to the main program window without importing a model. After you make your
selection, the Meteorologic Model will be checked for dependent data such as time-series gages or
parameter grids. The user is given the opportunity to also import any required data. The program
automatically copies the selected file and any additional data into the project folder and adds the various
components to the project.
14.1.6 Shortwave Radiation Method

Shortwave Radiation represents the incoming radiation from the sun. It is usually the largest source of
energy to the land surface, and is reduced by clouds in the atmosphere. Shortwave radiation is zero at night.
There are five different Shortwave Radiation Methods, including the option for No Shortwave Radiation.
Shortwave radiation is only necessary when using Energy Balance Evapotranspiration Methods. This
includes the Penman Monteith and Priestley Taylor Evapotranspiration Methods and the Energy Balance
Snowmelt Method. You can use the No Shortwave Method if you are not using any of these methods.
Select the Shortwave Radiation Method in the Component Editor for the Meteorologic Model. Only one
Shortwave Method can be selected at a time. You can always change the Shortwave Method. When you
change the Shortwave Method, all data for the old method is deleted and cannot be retrieved or undeleted.
Some Shortwave Radiation Methods require parameter data for each subbasin. Other methods use the same
data for all subbasins. Depending on the method you choose, the Watershed Explorer will be updated to
indicate which data is required.
327 The Meteorology Model Component Editor
14.1.7 Longwave Radiation Method

Longwave Radiation represents the radiant energy given off by all bodies. It includes energy radiated by the
land surface toward the atmosphere, and also energy radiated by clouds and the empty sky toward the land
surface. Net longwave radiation can be either from the atmosphere toward the land surface, or the land
surface toward the atmosphere. The direction of net longwave radiation depends on current conditions and

temperatures. There are five different Longwave Radiation Methods, including the option for No Longwave
Radiation. Longwave radiation is only necessary when using Energy Balance Evapotranspiration Methods.
This includes the Penman Monteith Evapotranspiration Method. You can use the No Longwave Method if
you are not using either of these methods.
Select the Longwave Radiation Method in the Component Editor for the Meteorologic Model. Only one
Longwave Method can be selected at a time. You can always change the Longwave Method. When you
change the Longwave Method, all data for the old method is deleted and cannot be retrieved or undeleted.
Some Longwave Radiation Methods require parameter data for each subbasin. Other methods use the same
14.1.8 Precipitation Method

Precipitation includes all rain and snowfall over the land surface. The determination of liquid or frozen
precipitation is performed in the Snowmelt Method; the Precipitation Method only determines the amount of
water falling to the land surface. There are nine different Precipitation Methods including an option for No
Precipitation. If you plan to use the Meteorologic Model with Basin Models that contain subbasins, you must
choose a Precipitation Method. If any of the subbasins use the ModClark Gridded Transform Method you
must use the Gridded Precipitation Method. You can use the No Precipitation option if the Basin Models do
not contain subbasins.
Select the Precipitation Method in the Component Editor for the Meteorologic Model (illustrated in the
previous figure). Only one Precipitation Method can be selected at a time. You can always change the
Precipitation Method. When you change the Precipitation Method, all data for the old method is deleted and
cannot be retrieved or undeleted.
Some Precipitation Methods require parameter data for each subbasin. Other methods use the same data
for all subbasins. Depending on the method you choose, the Watershed Explorer will be updated to indicate
which data is required. Also, some Precipitation Methods have optional settings. If the method you select
has optional settings then an additional tab may be added to the Component Editor.
14.1.9 Temperature Method

Temperature represents the heat intensity of the air over the land surface. There are four different
Temperature Methods, including the option for No Temperature. Temperature as a Meteorologic Model is
only necessary when using certain Evapotranspiration Methods, Shortwave Radiation Methods or Longwave
Radiation Methods. Temperature is also a principal input for determining Snowmelt, however, Snowmelt is a
hydrologic process and is handled within the basin model. Boundary conditions for Snowmelt are input
within the Basin Model Component Editor.
Select the Temperature Method in the Component Editor for the Meteorologic Model. Only one Temperature
Method can be selected at a time. You can always change the Temperature Method. When you change the
Temperature Method, all data for the old method is deleted and cannot be retrieved or undeleted.
Some Temperature Methods require parameter data for each subbasin. Other methods use the same data
for all subbasins. Depending on the method you choose, the Watershed Explorer will be updated to indicate
which data is required.

14.1.10 Windspeed Method

Windspeed is a measure of how fast air is moving past a certain point. There are four different
Windspeed Methods, including the option for No Windspeed. Windspeed is only necessary when using
certain Evapotranspiration Methods or Longwave Radiation Methods.
Select the Windspeed Method in the Component Editor for the Meteorologic Model. Only one Windspeed
Method can be selected at a time. You can always change the Windspeed Method. When you change the
Windspeed Method, all data for the old method is deleted and cannot be retrieved or undeleted.
Some Windspeed Methods require parameter data for each subbasin. Other methods use the same data for
all subbasins. Depending on the method you choose, the Watershed Explorer will be updated to indicate
14.1.11 Pressure Method

Pressure represents the pressure exerted by the weight of the atmosphere over the land surface. There are
three different Pressure Methods, including the option for No Pressure. Pressure is only necessary when
using certain Evapotranspiration Methods.
Select the Pressure Method in the Component Editor for the Meteorologic Model. Only one Pressure Method
can be selected at a time. You can always change the Pressure Method. When you change the Pressure
Method, all data for the old method is deleted and cannot be retrieved or undeleted.
Some Pressure Methods require parameter data for each subbasin. Other methods use the same data for all
subbasins. Depending on the method you choose, the Watershed Explorer will be updated to indicate which
data is required.
14.1.12 Dew Point Method

Dew Point represents the temperature below which dew can form. There are six different Dew
Point Methods, including the option for No Dew Point. Dew Point is only necessary when using
certain Evapotranspiration Methods or Longwave Radiation Methods.
Select the Dew Point Method in the Component Editor for the Meteorologic Model. Only one Dew Point
Method can be selected at a time. You can always change the Dew Point Method. When you change the Dew
Point Method, all data for the old method is deleted and cannot be retrieved or undeleted.
Some Dew Point Methods require parameter data for each subbasin. Other methods use the same data for
all subbasins. Depending on the method you choose, the Watershed Explorer will be updated to indicate
14.1.13 Evapotranspiration Method

The Meteorologic Model is responsible for computing the potential evapotranspiration over the land surface.
The potential evapotranspiration is the amount of evapotranspiration that would occur if there was an infinite
supply of water in the soil. The potential amount can generally be computed based on atmospheric
conditions. Including evapotranspiration is usually not important for short events, but becomes critical for
longer simulations. There are seven different Evapotranspiration Methods including an option for No
Evapotranspiration. If you plan to use the Meteorologic Model with Basin Models that contain subbasins, you
may need to choose an Evapotranspiration Method. The following loss methods require evapotranspiration

boundary conditions: Deficit Constant, Gridded Deficit Constant, Soil Moisture Accounting, Gridded Soil
Moisture Accounting. If you use a Meteorologic Model with subbasins using any of those loss methods, you
should select an Evapotranspiration Method. If you use those loss methods but no Evapotranspiration
Method is selected in the Meteorologic Model, then evapotranspiration is assumed to be zero in the
subbasins. A Gridded Evapotranspiration Method is provided for use with the ModClark Gridded Transform
Method. Using a Gridded Evapotranspiration Method provides separate boundary conditions for each grid
cell. Using a Non-Gridded Evapotranspiration Method means that the same boundary condition will be
applied at each grid cell in a subbasin.
Select the Evapotranspiration Method in the Component Editor for the Meteorologic Model (shown in the
previous figure). Only one Evapotranspiration Method can be selected at a time. You can always change the
Evapotranspiration Method. When you change the Evapotranspiration Method, all data for the old method is
deleted and cannot be retrieved or undeleted.
Some Evapotranspiration Methods require parameter data for each subbasin. Other methods use the same
14.1.14 Unit System

Each Meteorologic Model must be in either United States customary units (sometimes called English units)
or in system international units (also called metric units). All parameter data in a Meteorologic Model,
whether for all subbasins or individual subbasins, must be in the same unit system. If you change the unit
system, all data will be automatically converted to the new unit system. All time-series data, paired data, and
gridded data referenced in a Meteorologic Model will be in its own unit system. If necessary, these
referenced data are automatically converted to the unit system of the Meteorologic Model during a
simulation.
Select the unit system using the Component Editor for the Meteorologic Model. Access the Component
Editor by clicking on the Meteorologic Model icon on the Components tab of the Watershed Explorer. If you
change the unit system, all data is automatically converted to the new selection.
14.1.15 Missing Data

Missing Data is a common problem with atmospheric measurements. The exact meaning of missing data
often depends on the type of data. Missing precipitation data often means that no precipitation was
occurring. Care must be used, but it is often possible to assume that zero rainfall can be substituted for
missing data. Other types of atmospheric measurements are more difficult to manage when data is missing.
When air temperature is missing there is usually no reasonable substitution that can be made.
There are two options for managing missing data in the Meteorologic Model. The first option is to Abort the
Compute with an Error Message. Using this option means that when any missing data is encountered, the
simulation is stopped and an error message will report the time-series gage or grid that contained the
missing data. Using this approach is the best because it requires all atmospheric data to be reviewed and
corrected before use in a simulation. The second option is to Assume a Default Value. For example, with this
option selected any missing precipitation data will be assumed to be zero. However, allowing missing data to
be replaced with a default value sometimes leads to inconsistent results that can be difficult to interpret.
Furthermore, some types of data such as temperature have no default value. The compute will always abort
with an error message when missing data is encountered for data types with no defined default value.
Select the action to take for missing data using the Component Editor for the Meteorologic Model. Access
the Component Editor by clicking on the Meteorologic Model icon on the Components tab of the Watershed
Explorer.

14.1.16 Selecting Basin Models

The main purpose of a Meteorologic Model is to prepare meteorologic boundary conditions for subbasins.
These boundary conditions include precipitation and when also necessary, shortwave radiation, longwave
radiation, temperature, windspeed, pressure, dewpoint and potential evapotranspiration. The Meteorologic
Model must be configured to compute the necessary boundary conditions. This is accomplished by
specifying which Basin Models will be used with each Meteorologic Model as shown in the following figure
(you only need to link the meteorologic model to a basin model when non-gridded meteorologic methods are
selected). Once a Basin Model is selected to work with a Meteorologic Model, the subbasins are connected
to the Meteorologic Model. The connection is performed using the name of the subbasin. If several Basin
Models all include a subbasin with the same name, the Meteorologic Model will compute the same boundary
conditions for the subbasin in each model. If you want each subbasin to have unique boundary conditions,
then the name of the subbasin must be unique across all Basin Models that will be used with the same
Meteorologic Model.
328 Specifying which basin models should be used with a meteorologic model
Once a Basin Model is selected to work with a Meteorologic Model, the Meteorologic Model is automatically
kept synchronized with changes in that Basin Model. When a Basin Model is renamed, it is updated in all
Meteorologic Models working with that Basin Model. When a Basin Model is deleted, any subbasins it
contains are removed from all Meteorologic Models working with that Basin Model. However, subbasins will
not be removed from a Meteorologic Model when a Basin Model is deleted if the subbasins are also included
in other Basin Models still used by the Meteorologic Model. Subbasins are likewise removed if a Basin Model
is unselected from a Meteorologic Model. Similar changes are also made automatically when subbasins are
added to or deleted from a Basin Model set to work with a Meteorologic Model, or when they are renamed.
Subbasins added to a Basin Model will be automatically added to all Meteorologic Models set to work with
that Basin Model. Subbasins deleted from a Basin Model will be removed from all Meteorologic Models set
to work with that Basin Model, so long as the subbasin in not included in any other Basin Models connected
to a Meteorologic Model. Finally, renamed subbasins will also be renamed in the Meteorologic Model.
However, if other Basin Models connected to the Meteorologic Model contain subbasins with the same
name as the old name of the renamed subbasin, they will retain their original name and parameter data while
the renamed subbasin receives a copy of the data.

The Basins tab, part of the Component Editor for the Meteorologic Model, is used to connect Basin Models
to the Meteorologic Model. The Basins tab shows a table of all current Basin Models in the project. Each
Basin Model can be selected or unselected to work with the Meteorologic Model. The table is automatically
updated as Basin Models are created, renamed, or deleted.
14.2 Shortwave Radiation

Shortwave Radiation is a radiant energy produced by the sun with wavelengths ranging from infrared
through visible to ultraviolet. Shortwave radiation is therefore exclusively associated with daylight hours for a
particular location on the Earth's surface. The energy arrives at the top of the Earth's atmosphere with a Flux
(Watts per square meter) that varies very little during the year and between years. Consequently, the flux is
usually taken as a constant for hydrologic simulation purposes. Some of the incoming radiation is reflected
by the top of the atmosphere and some is reflected by clouds. A portion of the incoming radiation is
absorbed by the atmosphere and some is absorbed by clouds. The Albedo is the fraction of the shortwave
radiation arriving at the land surface that is reflected back into the atmosphere. The shortwave radiation that
is not reflected or absorbed above the land surface, and is not reflected by the land surface, is available to
drive hydrologic processes such as evapotranspiration and snowpack melting.
The Shortwave Radiation Method included in the Meteorologic Model is only necessary when Energy
Balance Methods are used for evapotranspiration or snowmelt. The options available cover a range of detail
from simple to complex. Simple specified methods are also available for input of a time-series gage or grid.
Each option produces the net shortwave radiation arriving at the land surface where it may be reflected or
absorbed. More detail about each method is provided in the following sections.
14.2.1 Bristow Campbell

The Bristow Campbell Method (Bristow and Campbell, 1984) uses a conceptual approach to estimating the
shortwave radiation at the land surface. During the daylight hours, any clouds present in the atmosphere will
block some portion of incoming solar radiation which reduces solar heating and results in a lower
temperature. Conversely, lack of clouds permits much more of the solar radiation to pass through the
atmosphere which allows greater heating and generally higher air temperatures. In theory, the daily
temperature range should be small on cloudy days and large on non-cloudy days. This correlation between
temperature range and incoming solar radiation is exploited as a simple way to compute shortwave radiation
using only air temperature.
The Bristow Campbell Method includes a Component Editor with parameter data for each subbasin in the
Meteorologic Model. The Watershed Explorer provides access to the Shortwave Component Editor using a
picture of solar radiation, as shown in the following figure.
An Air Temperature method must be selected in the meteorologic model.

329 A Meteorologic Model using the Bristow Campbell Shortwave Radiation Method with a Component Editor for each individual
subbasin
The Component Editor for each subbasin in the Meteorologic Model is used to enter parameter data, as
shown in the following figure. The Transmittance represents the maximum clear sky characteristics over the
watershed. The default value of the transmittance is 0.70. The Exponent controls the timing of the maximum
temperature and may vary from humid to arid environments. The default value of the exponent is 2.4.
The Average Monthly Temperature Range must be entered. This value is the difference between the average
monthly high temperature and the average monthly low temperature.

330 Entering atmosphere and temperature data for a subbasin using the Bristow Campbell Shortwave Radiation Method
14.2.2 FAO56
The FAO56 Method implements the algorithm detailed by Allen, Pereira, Raes, and Smith (1998). The
algorithm calculates the solar declination and solar angle for each time interval of the simulation, using the
coordinates of the subbasin, Julian day of the year, and time at the middle of the interval. The solar values
are used to compute the extra-terrestrial radiation for each subbasin. Total daylight hours are computed
based on the Julian day and compared to the number of actual sunshine hours. Shortwave radiation arriving
at the ground surface is then computed using the most common relationship accounting for reduction in
sunshine hours due to cloud cover.
The Watershed Explorer provides access to the Shortwave Component Editors using a picture of solar
radiation. The FAO56 Method includes a Component Editor with parameter data for all subbasins in the
Meteorologic Model. A Component Editor is also included for each subbasin, as shown in the following
figure.

331 A Meteorologic Model using the FAO56 Shortwave Radiation Method with a Component Editor for each individual subbasin
A Component Editor for all subbasins in the Meteorologic Model includes the Central Meridian of the Time
Zone, as shown in the following figure. There is currently no specification for the time zone so the meridian
must be specified manually. The central meridian is commonly the longitude at the center of the local time
zone. Meridians west of zero longitude should be specified as negative while meridians east of zero
longitude should be specified as positive. The meridian may be specified in decimal degrees or degrees,
minutes, and seconds depending on the Program Settings.
332 Entering the longitude of the central meridian of the local time zone
The Component Editor for each subbasin in the Meteorologic Model is used to enter parameter data
necessary to account for differences in cloud cover across the watershed. Cloud cover is considered through
a time-series of Sunshine Hours. Sunshine hours are defined as the number of decimal hours per full hour
where the shortwave radiation exceeds 120 watts per square meter (WMO, 2008).

333 Selecting a time-series gage for the sunshine hours
14.2.3 Gridded Hargreaves

The Gridded Hargreaves Method is the same as the regular Hargreaves Method (described in a later
section) except that the Hargreaves equations are applied to each grid cell using separate boundary
conditions instead of area-averaged values over the whole subbasin.
The Gridded Hargreaves Shortwave Method includes a Component Editor with parameter data for all
subbasins in the Meteorologic Model. The Watershed Explorer provides access to the Shortwave
Component Editor using a picture of solar radiation, as shown in the following figure.
334 A Meteorologic Model using the Gridded Hargreaves Shortwave Method with a Component Editor for all subbasins
The Component Editor requires the Central Meridian of the Time Zone. If the Basin Model spans multiple
time zones, then enter the central meridian for the time zone containing most of the Basin Model drainage
area. The central meridian is the longitude at the center of the local time zone. Meridians west of zero
longitude should be specified as negative while meridians east of zero longitude should be specified as
positive. The meridian may be specified in decimal degrees or degrees, minutes, and seconds depending on
the Program Settings.
The Component Editor requires a Hargreaves Shortwave Coefficient. The default Hargreaves shortwave
coefficient is 0.17 per square root of degrees Celsius; this is equivalent to 0.1267 per square root of degrees
Fahrenheit. The default Hargreaves shortwave coefficient of 0.17 per square root of degree Celsius is

implicit in the Hargreaves and Samani (1985) potential evapotranspiration formulation. The Hargreaves
shortwave coefficient can be adjusted by the user.
335 Component Editor for the Gridded Hargreaves Shortwave Method
336 (OLD) Component Editor for the Gridded Hargreaves Shortwave Method
14.2.4 Gridded Shortwave

The most common use of the method is to utilize gridded shortwave radiation estimates produced by an
external model, for example, a dynamic atmospheric model. If it is used with a Transform Method other than
ModClark, an area-weighted average of the grid cells in the subbasin is used to compute the shortwave
radiation time-series for each subbasin.
The Gridded Shortwave Method includes a Component Editor with parameter data for all subbasins in the
Meteorologic Model. The Watershed Explorer provides access to the Shortwave Component Editor using a
picture of solar radiation, as shown in the following figure.

337 A Meteorologic Model using the Gridded Shortwave Method with a Component Editor for all subbasins in the Meteorologic Model
A Component Editor for all subbasins in the Meteorologic Model includes the selection of the data source. A
Radiation Gridset must be selected for all subbasins. The current gridsets are shown in the selection list. If
there are many different gridsets available, you may wish to choose a gridset from the selector accessed
with the Grid button next to the selection list. The selector displays the description for each gridset, making it
easier to select the correct one.
338 Specifying the shortwave radiation data source for the Gridded Shortwave Method
14.2.5 Hargreaves
The Hargreaves Shortwave Method implements the shortwave radiation algorithm described by Hargreaves
and Samani (1982). The method calculates the solar declination and solar angle for each time interval of the
simulation, using the coordinates of the subbasin, Julian day of the year, and time at the middle of the
compute interval. The solar values are used to compute the extra-terrestrial radiation for each subbasin. The
daily temperature range, daily maximum temperature less daily minimum temperature, functions as a proxy
for cloud cover. Shortwave radiation arriving at the ground surface is computed as a function of
extraterrestrial radiation and the daily temperature range.
The Hargreaves Shortwave Method is parameterized for all subbasins in the Basin Model. Select the
Hargreaves Shortwave node in the Watershed Explorer to access the Hargreaves Shortwave Component
Editor, as shown in the following figure. A Temperature method must be selected in the meteorologic
model.

339 A Meteorologic Model using the Hargreaves Shortwave Radiation Method with a Component Editor for the basin
The Hargreaves Shortwave Component Editor is shown in the following figure. The user must enter the
Central Meridian of the Time Zone and the Hargreaves Shortwave Coefficient. If the Basin Model spans
multiple time zones, then enter the central meridian for the time zone containing most of the Basin Model
drainage area. The central meridian is the longitude at the center of the local time zone. Meridians west of
zero longitude should be specified as negative while meridians east of zero longitude should be specified as
the program settings. The default Hargreaves shortwave coefficient is 0.17 per square root of degrees
Celsius; this is equivalent to 0.1267 per square root of degrees Fahrenheit. The default Hargreaves
shortwave coefficient of 0.17 per square root of degree Celsius is implicit in the Hargreaves and Samani
(1985) potential evapotranspiration formulation. The Hargreaves shortwave coefficient can be adjusted by
the user.
340 Entering the longitude of the central meridian of the local time zone (US Pacific in this case) and Hargreaves shortwave radiation
coefficient
14.2.6 Specified Pyranograph

A Pyranometer is an instrument that can measure incoming solar shortwave radiation. They are not part of
basic meteorological observation stations, but may be included at first order stations. This method may be
used to import observed values from a pyranometer or it may be used to import estimates produced by an

external model. This is the recommended choice for use with the Priestley Taylor Evapotranspiration
Method, where an effective radiation is used which includes both shortwave and longwave radiation.
The Specified Pyranograph Method includes a Component Editor with parameter data for all subbasins in
the Meteorologic Model. The Watershed Explorer provides access to the Shortwave Component Editors
using a picture of solar radiation, as shown in the following figure.
341 A Meteorologic Model using the Specified Pyranograph Shortwave Method with a Component Editor for all subbasins
The Component Editor for all subbasins in the Meteorologic Model includes the time-series gage of
shortwave radiation for each subbasin. A Solar Radiation Gage must be selected for a subbasin. The current
gages are shown in the selection list.
342 Specifying the shortwave radiation time-series gage for each subbasin

14.2.7 Interpolated Shortwave

Gridded data better captures the meteorology temporally and spatially across a watershed when compared
to gage measurements at a single point. However, hourly or sub-hourly gridded meteorology products are not
always available, particularly for historic events of interest to the modeler. In these cases, a gridded dataset
can be created by interpolating point observations recorded at weather stations. The Interpolated Shortwave
Method allows the user to develop an interpolated shortwave radiation grid based on point radiation gage
data.
The Interpolated Shortwave Method includes a Component Editor with parameter data for all subbasins in
the Meteorologic Model. The Watershed Explorer provides access to the Shortwave Component
Editor. The Component Editor for each subbasin in the Meteorologic Model is used to enter parameter data
that defines the Interpolation Method and to select radiation gages to use in the
interpolation. The Interpolation Method can be selected from the dropdown menu. An interpolation method
must be selected. The user has four interpolation options briefly summarized below.
343 A Meteorologic Model using the Interpolated Shortwave Radiation Method
The Inverse Distance interpolation method assumes the weight, or influence, of a gage is equal to the
inverse of its distance from the interpolated cell. The Inverse Distance Squared interpolation method
assumes the weight of a gage is equal to the inverse of the square of its distance from the interpolated
cell. The Nearest Neighbor interpolation method simply assigns the nearest value to the cell center of
interest without considering values of other nearby points. Bilinear interpolation within HEC-HMS relies on
triangulation of the irregularly spaced gage locations. Based on the gage coordinates, a Triangulated
Irregular Network (TIN) is created to represent the gage network in the basin model coordinate system. This
TIN defines triangles, where each gage is a corner of one or more triangles. Given this TIN, a value at any
given point is computed by first identifying the triangle in which that point falls, then interpolating within that
triangle using Barycentric Coordinates. You must use three or more gages and the gages need to bound all
grid cells.
Select Radiation Gages in the dropdown rows under the Gage column. The Radius of Influence is an optional
parameter and represents the maximum interpolation distance. Beyond its radius of influence, the gage will
not affect the cell values of the interpolated grid. Radiation Gages used in this method must be loaded in
as Time-Series of Radiation Data with defined latitude and longitude information.

344 Interpolated Shortwave Radiation Component Editor
An interpolated shortwave radiation grid will be created once the simulation has been computed. Once the
compute is complete the interpolated grid will be saved with the same name as the Meterologic
Model in DSS format in the HEC-HMS project directory.
14.2.8 Reduced Solar Constant

The Reduced Solar Constant Shortwave Method implements the shortwave radiation algorithm described
within TVA (1972) and Follum et al, (2015). The method estimates the amount of shortwave radiation at a
specific location (grid cell or subbasin) by reducing the solar constant (1366 Watts / square meter) using
several factors including distance from the earth to the sun, atmospheric scattering, and slope/aspect of the
terrain. If the basin model is not georeferenced and/or doesn't have an associated terrain model, these
calculations will proceed assuming the location is at the equator and at sea-level.
The Reduced Solar Constant Shortwave Method includes a Component Editor with parameter data for all
subbasins in the Meteorologic Model. The Watershed Explorer provides access to the Reduced Solar
Constant Shortwave Editor using a picture of solar radiation, as shown in the following figure.
345 A Meteorologic Model using the Reduced Solar Constant Shortwave Radiation Method
The Reduced Solar Constant Shortwave Component Editor is shown in the following figure. The user must
select a solar declination, aspect reduction, earth distance reduction, and atmospheric absorption method.

346 Reduced Solar Constant Shortwave Method Component Editor
14.3 Longwave Radiation

All living and non-living bodies emit Longwave Radiation. The magnitude of the radiation is proportional to
the temperature (measured in Kelvin degrees) of the body raised to the fourth power. Significant sources of
longwave radiation in hydrologic applications include the atmosphere itself, and any clouds that may be
present locally in the atmosphere. Clouds usually have a higher heat content and higher temperature than
clear atmosphere, and therefore there is increased downwelling longwave radiation on cloudy days. Whether
the atmosphere and clouds are a net source of longwave radiation to the land surface depends on their
temperature relative to the land surface temperature. In most cases, the net longwave radiation is incoming
during the daylight hours, and outgoing during the night hours.
The Longwave Radiation Method included in the Meteorologic Model is only necessary when Energy
Balance Methods are used for Evapotranspiration or Snowmelt. The options available cover a range of detail
from simple to complex. Simple specified methods are also available for input of a time-series or grid. Each
option produces the Downwelling Longwave Radiation arriving at the land surface. Absorption and radiation
by the land surface is computed within the Subbasin Element. More detail about each method is provided in
the following sections.
14.3.1 FAO56
The FAO56 Method implements the algorithm detailed by Allen, Pereira, Raes, and Smith (1998). The
algorithm calculates the solar declination and solar angle for each time interval of the simulation, using the
coordinates of the subbasin, Julian day of the year, and time at the middle of the interval. The solar values
are used to compute the clear sky radiation for each subbasin. The computed shortwave radiation is then
divided by the calculated clear sky radiation to estimate the fraction of shortwave radiation reaching the
ground. Finally, the fraction of shortwave radiation reaching the ground is combined with the vapor pressure
to calculate a reduction to the downwelling longwave radiation based on the Stefan-Boltzmann equation.
The FAO56 Method includes a Component Editor with parameter data for all subbasins in the Meteorologic
Model; the same data is also shared with the FAO56 Shortwave Radiation Method. When FAO56 is used for
both shortwave and longwave radiation, the icon will preferentially show the Shortwave icon. A Component
Editor is also included for each subbasin. The Watershed Explorer provides access to the Longwave
Component Editors using a picture of cloud black body radiation.
Temperature (or Dew Point Temperature) and a Windspeed methods must be selected in the Meteorologic
Model. Actual Vapor Pressure is used as a humidity correction for emitted longwave radiation. Actual vapor
pressure can be calculated using the Dew Point Temperature, Relative Humidity, or Daily Minimum
Temperature. The Daily Minimum Temperature option should be used when relative humidity or dewpoint

data are not available; the daily minimum temperature option assumes the dewpoint temperature is equal to
the daily minimum temperature.
347 A Meteorologic Model using the FAO56 Longwave Method with a Component Editor for all subbasins, and a separate Component
Editor for each individual subbasin
A Component Editor for all subbasins in the Meteorologic Model includes the Central Meridian of the Time
Zone. There is currently no specification for the time zone so the meridian must be specified manually. The
central meridian is commonly the longitude at the center of the local time zone. Meridians west of zero
longitude should be specified as negative while meridians east of zero longitude should be specified as
348 The FAO56 Longwave Method requires the time zone central meridian
The Component Editor for each subbasin in the Meteorologic Model is shown below. Currently, the only
method for calculating the differences from clear sky radiation is based on elevation. A Representative
Elevation should be entered for each subbasin.

349 Specifying the representative elevation for a subbasin within the FAO56 Longwave Subbasin Component Editor
14.3.2 Gridded Longwave

The most common use of the method is to utilize gridded longwave radiation estimates produced by an
external model, for example, a dynamic atmospheric model. If a gridded longwave radiation estimate is used
with a transform method other than ModClark, an area-weighted average of the grid cells in the subbasin is
used to compute the longwave radiation time-series for each subbasin.
The Gridded Longwave Method includes a Component Editor with parameter data for all subbasins in the
Meteorologic Model. The Watershed Explorer provides access to the Longwave Component Editor using a
picture of downwelling radiation from clouds.
350 A Meteorologic Model using the Gridded Longwave Method with a Component Editor for all subbasins in the Meteorologic Model
A Component Editor for all subbasins in the Meteorologic Model includes the selection of the data source. A
Radiation Gridset must be selected for all subbasins. The current gridsets are shown in the selection list. If
there are many different gridsets available, you may wish to choose a gridset from the selector accessed
with the Grid button next to the selection list. The selector displays the description for each gridset, making it

easier to select the correct one.
14.3.3 Satterlund
The Satterlund Method (Satterlund, 1979) uses temperature and vapor pressure to estimate incoming
longwave radiation. While certain physical limits are enforced, the approach is fundamentally empirical. It
provides good estimates under mostly clear skies and continues to perform well even as temperature drops
below the freezing point. It has the advantage of requiring only readily available meteorologic data.
The Satterlund Method includes a Component Editor with parameter data for each subbasin in the
Meteorologic Model. The Watershed Explorer provides access to the Longwave Component Editors using a
picture of downwelling radiation from clouds.
Temperature, Windspeed, and Dew Point methods must be selected in the Meteorologic Model.
351 A Meteorologic Model using the Satterlund Longwave Method with a Component Editor for all subbasins in the Meteorologic Model
The Incoming Longwave Radiation is computed using a modified form of the equation for ideal black body
radiation. The Emissivity is calculated as a function of the temperature, where the Temperature Coefficient
has a default value of 2016 Kelvin. An Emissivity Coefficient is included for calibration, though the default
value of 1.08 is widely used. The Emissivity and Temperature Coefficients can be entered in the Component
Editor as shown in the following figure.

352 Specifying the thermodynamic properties for each subbasin
14.3.4 Specified Pyrgeograph

A Pyrgeometer is an instrument that can measure Downwelling Longwave Radiation. They are not part of
basic meteorological observation stations, but may be included at first-order stations. This method may be
used to import Observed Values from a Pyrgeometer or it may be used to import estimates produced by an
external model.
The Specified Pyrgeograph Method includes a Component Editor with parameter data for all subbasins in
the Meteorologic Model. The Watershed Explorer provides access to the Longwave Component Editors
using a picture of downwelling radiation from clouds.
353 A Meteorologic Model using the Specified Pyrgeograph Longwave Method with a Component Editor for all subbasins in the
Meteorologic Model
The Component Editor for all subbasins in the Meteorologic Model includes the Time-Series Gage of
Longwave Radiation for each subbasin. A Radiation Gage must be selected for a subbasin. The current
gages are shown in the selection list.

354 Specifying the longwave radiation time-series gage for each subbasin
14.3.5 Interpolated Longwave

can be created by interpolating point observations recorded at weather stations. The Interpolated Longwave
Method allows the user to develop an interpolated longwave radiation grid based on point radiation gage
data.
The Interpolated Longwave Method includes a Component Editor with parameter data for all subbasins in
the Meteorologic Model. The Watershed Explorer provides access to the Longwave Component
that defines the Interpolation Method and to select radiation gages to use in the interpolation.
The Interpolation Method can be selected from the dropdown menu. An interpolation method must be
selected. The user has four interpolation options briefly summarized below.
355 A Meteorologic Model using the Interpolated Longwave Radiation Method

grid cells.
Select Radiation Gages in the dropdown rows under the Gage column. The Radius of Influence is an optional
not affect the cell values of the interpolated grid. Radiation Gages used in this method must be loaded in
as Time-Series of Radiation Data with defined latitude and longitude information.
356 Interpolated Longwave Radiation Component Editor
An interpolated longwave radiation grid will be created once the simulation has been computed. Once the
compute is complete the interpolated grid will be saved with the same name as the Meterologic
14.3.6 Stefan Boltzmann Longwave

The Stefan Boltzmann Longwave Method implements the longwave radiation algorithm described within
TVA (1972) and Follum et al. (2015). The method estimates the amount of longwave radiation at a specific
location (grid cell or subbasin) using the air temperature and relative humidity. As such, this method requires
the use of a valid temperature and relative humidity method.
The Stefan Boltzmann Longwave Method includes a Component Editor with parameter data for all
subbasins in the Meteorologic Model. The Watershed Explorer provides access to the Stefan Boltzmann
Longwave Editor using a picture of downwelling radiation from clouds.

357 A Meteorologic Model using the Stefan Boltzmann Longwave Method
The Stefan Boltzmann Longwave Component Editor is shown in the following figure. The user must select
an atmospheric emissivity and saturation vapor pressure method. Currently, only the Bras (1993) option
is available for the Atmospheric Emissivity Method. This method computes atmospheric emissivity from
relative humdiity and saturation vapor pressure. Additional options will be added in the future. There are two
options for the Saturation Vapor Pressure Method: Smith (1993) and FAO56 (1998). The FAO56 (1998)
method uses the Clausius-Clapeyron equation to compute saturation vapor pressure from air temperature.
358 Stefan Boltzmann Longwave Component Editor
14.4 Precipitation
Precipitation is water falling over the land surface. It is caused when water vapor in the atmosphere
condenses on airborne nuclei such as dust particles. Condensation continues to add to the droplet forming
around the nuclei until the weight of the droplet exceeds the ability of wind currents to keep it aloft.
Precipitation can be caused by different Types of Storms including Stratiform, Convection, and Cyclone
which each have typical characteristics of Duration, Intensity, and Spatial Extent. Precipitation includes the
liquid form known as rain as well as a variety of Frozen Forms including Sleet, Snow, Graupel, and Hail. Most
hydrologic purposes can be met by limiting consideration to rain and snow. The determination of the rain or
snow state is made separately in the snowmelt portion of the Meteorologic Model.
The Precipitation Method included in the Meteorologic Model is required whenever a Basin Model includes
Subbasin Elements. The options available include several that Process Gage Measurements, a statistical
method that uses depth-duration data, several design storms options, and a gridded method that can be
used with radar rainfall data. Each option produces a hyetograph of precipitation falling over each subbasin.
More detail about each method is provided in the following sections.

14.4.1 Frequency Storm

The Frequency Storm Method is designed to produce a synthetic storm from statistical precipitation data.
The most common source of statistical data in the United States is the National Weather Service. Typically,
the data is given in the form of maps, where each map shows the expected precipitation depth at a given
point for a storm of specific duration and exceedance probability. This method is designed to use data
collected from the maps along with other information to compute a hyetograph for each subbasin.
The Frequency Storm Method includes a Component Editor with parameter data for all subbasins in the
Meteorologic Model, and a separate Component Editor for each individual subbasin. The Watershed
Explorer provides access to the Precipitation Component Editors using a picture of raindrops.
359 A Meteorologic Model using the Frequency Storm Method with a Component Editor for all subbasins, and a separate Component
Editor for each individual subbasin
The Component Editor for all subbasins in the Meteorologic Model includes parameter data to describe the
Frequency Storm (illustrated in the subsequent figure). The Frequency Storm Method is designed to accept
partial or annual-duration precipitation depth-duration data. A conversion factor, or Annual-Partial Ratio, can
be applied when the output, computed flow, is required to be different than the input precipitation. The
difference between frequency curves derived from partial and annual-duration information is extremely small
for exceedance probabilities 4% and smaller; annual and partial duration frequency curves usually converge
beyond the 10% exceedance probability. Adjustment factors are available for annual-partial duration
differences for the 10%, 20% or 50% exceedance probabilities. The following figure shows the available
options for annual to partial duration adjustments. Once the Annual-Partial Conversion option is selected in
the list, the Annual-Partial Ratio field is automatically populated with a ratio that is appropriate to the user
specified Annual-Partial Conversion option. By default, the None Annual-Partial Conversion option is
selected and a ratio of 1.0 is applied to the Precipitation Frequency Information. If the 50 Percent Annual to
Partial option is selected, then a ratio of 1.14 is applied to the Precipitation Frequency Information,
converting it from an annual duration frequency curve to a partial duration frequency curve. If the 50 Percent
Partial to Annual option is selected, then a ratio of 0.88 is applied to the precipitation frequency information,
converting it from partial duration frequency curve to an annual duration frequency curve.

360 Options available for converting between annual and partial duration frequency information
The Storm Duration determines how long the precipitation will last. The storm duration must be longer than
the Intensity Duration. Historic storms within the region can aid in setting an appropriate storm duration. The
intensity duration specifies the shortest time period of the storm. Usually the intensity duration should be set
equal to the time step of the simulation. It must be less than the total storm duration. If the Simulation
Duration is longer than the storm duration, then all time periods after the storm duration will have zero
precipitation.

361 Precipitation editor for all subbasins when the Frequency Storm Method is selected
The Intensity Position determines where in the storm the period of peak intensity will occur. Changing the
position does not change the total precipitation depth of the storm, but does change how the total depth is
distributed in time during the storm. You may select 25%, 33%, 50%, 67%, or 75% from the list of choices. If
the storm duration is selected to be 6 hours and the 25% position is selected, the peak intensity will occur 1.5
hours after the beginning of the storm. The default selection is 50%.
The Area Reduction determines the area-reduction curves for reducing point precipitation, from a
precipitation-frequency analysis performed using precipitation gage data, to precipitation over a storm area.
There are three options: None, TP40/TP49, and User-Specified. The None area reduction method would be
selected if the user already applied area reduction factors to the precipitation frequency information, or if the
user did not want area-reduction factors to be applied to the analysis. The TP40/TP49 area reduction option
will result in the program applying the area-reduction curves as presented in NOAA Technical Paper Number
40 (TP 40) and NOAA Technical Paper Number 49 (TP 49), where there are different area-reduction curves

for different storm durations. Caution should be used when applying this reduction method to drainage areas
greater than 400 square miles. Lastly, the User-Specified reduction method allows the user to specify an
area-reduction paired data table for each duration of the frequency storm as shown below. You can use the
same area-reduction function for multiple durations.
362 Frequency Storm Component Editor User-Specified
When the TP40/TP49 or User-Specified option is selected, then the Storm Area is used to automatically
compute the depth-area reduction factor for each storm duration. In most cases, the specified storm area
should be equal to the watershed drainage area at the point of evaluation. If the storm area is left blank, the
area of each subbasin in the Basin Model will be used to reduce the point depth (computed results would
only be accurate at the outlet of each subbasin). The depth-area analysis simulation can be used to quickly
analyze multiple analysis points (the user chooses the analysis points). The depth-area analysis simulation is
a multi-compute simulation where the storm area, precipitation hyetograph, and runoff is computed for each
analysis point.
Precipitation Depth values must be entered for all durations from the peak intensity to the total storm
duration. Values for durations less than the peak intensity duration, or greater than the total storm duration

are not entered. Values should be entered as the cumulative precipitation depth expected for the specified
duration.
The Component Editor for each individual subbasin in the Meteorologic Model is used to specify a separate
depth-duration curve for each subbasin. The depth-duration curve can only be entered for a subbasin if the
Spatial Distribution option is set to Variable by Subbasin. Using this option may be necessary if the
watershed is large and the depth-duration characteristics of the precipitation change significantly over the
watershed. For example, mountainous areas may have changes in the precipitation characteristics with
changes in elevation.
363 Frequency Storm Component Editor for a Subbasin Element
14.4.1.1 Precipitation Depth Calculator

The Frequency Precipitation Calculator can be used to obtain average precipitation depths for the entire
basin or by subbasin, depending on the selected Spatial Distribution option. The calculator requires basins
with Two-Dimensional Spatial Features, as well as Precipitation Frequency Grids. To open the calculator,
click on the Calculator icon on the right side of the table in the bottom half of the Component Editor.

364 The Calculator button
The Frequency Precipitation Calculator consists of a Basin selection box followed by grid selections for
each duration within the interval range specified in the Component Editor. Available grids will be those
imported as Precipitation-Frequency Grids.
365 Selecting grids for each duration in the Frequency Precipitation Calculator.
After clicking the Calculate button, average depths for each duration will be calculated using either the basin
or subbasin area, depending on the selected Spatial Distribution option. The Precipitation-Frequency Depths
table will then open. This table consists of a column for the location, followed by columns containing the
computed values for each of the chosen duration intervals. If the Spatial Distribution option is set to Variable

by Subbasin, there will be a row containing the computed depths for each subbasin. These computed values
can be accepted or edited manually.
Clicking Apply will add the values to the Component Editor, while clicking OK will add the values to the
Component Editor and close the table.
366 Viewing calculated depths in the Precipitation-Frequency Depths table
The Number of Significant Digits used to display the computed precipitation-frequency depths is controlled
by the Expression Calculator Precision setting that is available from the Compute tab in the Program
Settings editor (as shown below). The number of significant digits for a precipitation depth of 1.43 inches is
3. If the precision is too high or low, adjust the Expression Calculator Precision and then recompute the
precipitation depths using the Frequency Precipitation Calculator. The number of significant digits are
preserved when saving precipitation values from the Precipitation-Frequency Depths table to the

Component Editor.
14.4.2 Gage Weights

The Gage Weights Method is designed to work with recording and non-recording precipitation gages.
Recording gages typically measure precipitation as it occurs and then the raw data are converted to a regular
time step, such as 1 hour. Non-recording gages usually only provide an estimate of the total storm depth.
The user can choose any method to develop the weights applied to each gage when calculating the
hyetograph for each subbasin. For increased flexibility, the total storm depth and the temporal pattern are
developed separately for each subbasin. Optionally, an index depth can be assigned to each gage and
subbasin. The index is used to adjust for regional bias in annual or monthly precipitation.
The Gage Weights Method includes several options for processing precipitation gage data. The Indexing
option is used to adjust gage data when there are regional trends in precipitation patterns. Using the index
option requires the specification of an index value for each precipitation gage and each subbasin. The
average annual precipitation total is often used as the index at a gage, and the estimated average annual
precipitation over a subbasin area is often used as the index for a subbasin. Alternately, the monthly average
values may be used at each gage and each subbasin. The index values are used to adjust the precipitation
data for regional trends before calculating the weighted depth and weighted timing. The Total Override
option is used to adjust the precipitation depth at each gage. Without the override, the total depth at a gage
is the sum of the values in the gage record. With the override, the values in the gage record are proportionally
adjusted to have a sum equal to the specified total value.

367 Selecting options for the Gage Weights Precipitation Method
The Gage Weights Method includes a Component Editor with parameter data for all subbasins in the
Meteorologic Model. A Component Editor is also included for specifying the parameter data for precipitation
gages. Finally, a separate Component Editor is included for each individual subbasin in the Meteorologic
Model. The Watershed Explorer provides access to the Precipitation Component Editors using a picture of
raindrops, and provides access the Gage Component Editor using a picture of a measurement gage.
368 A Meteorologic Model using the Gage Weights Precipitation Method with a Component Editor for all subbasins, a Component Editor
for precipitation gages, and a separate Component Editor for each individual subbasin
The Component Editor for all subbasins in the Meteorologic Model includes the optional Index for each
subbasin (you must set the Use Indexing option to yes, this option is found on the meteorologic model's
Options tab, in order for the Component Editor shown below to become active). The parameter data for
indexing is only entered when the option is activated. In order to use the optional Index, an Index value must
be entered for each subbasin and precipitation gage.

369 Specifying indices for each subbasin using average total storm precipitation depths. Other methods may be used to estimate the
index.
The Component Editor for all precipitation gages in the Meteorologic Model includes the optional Total
Depth Override and optional Indexing. The parameter data for override and indexing is only entered when the
respective options are activated. The optional total depth override is entered for each gage. If no total depth
is entered, the depth will be the sum of the data actually stored in the precipitation gage. However, if a total
depth is entered, the exact pattern is maintained but the magnitude of precipitation at each time step is
adjusted so that the specified depth is applied over the entire simulation. Total depth can be specified for no
precipitation gages, one gage, many gages, or all gages. Turning off the Use Override option will remove all
total depth data for time-series precipitation gages.
370 (OLD) Entering optional total depth and index for the precipitation gages
The optional Index is entered for each gage. If you enter an index for a gage, it can only be used during a
simulation if you also specify an index for all gages used in a subbasin and also specify an index for the
subbasin. Turning off the Use Indexing option will remove all indexes from the Meteorologic Model.
Total Storm Gages are created and managed directly from the Meteorologic Manager. To create a new Total
Storm Gage, access the Total Storm Gages tab and enter a gage name in the first column of the last row.
The last row is always kept blank for creating new gages. You can rename a gage by typing over the name in
the first column. You can delete a gage by deleting its name from the first column and any data from the
other columns. You must always enter a Total Depth for the gage that represents the total precipitation
during the simulation.

371 Managing total storm gages for a Meteorologic Model
372 (OLD) Creating a total storm gage and entering the total storm depth and optional index
The Component Editor for each subbasin in the Meteorologic Model is used to select the precipitation gages
for that subbasin and to enter weights for each selected gage. The Gage Selections tab is where the gages
are selected. All of the available gages are shown in a table. The available gages are the precipitation time-
series gages defined in the Time-Series Data Manager plus any Total Storm Gages defined in the
Meteorologic Model. For each subbasin you must separately select which gages will be used for that
subbasin.
373 Selecting which gages to use for a subbasin

The Gage Weights tab is where the weights are specified for each gage selected for a subbasin. The gages
are shown in a table with a separate row for each gage. Only the gages selected previously on the Gage
Selections tab are included in the table. For each gage you can enter a Depth Weight. You can enter a time
weight for time-series gages. The values entered for the depth or time weights are automatically normalized
during the simulation. The value of the weights must be estimated separate from the program. Possible
methods for computing the weights include Thiessen Polygons, Inverse Distance, Inverse Distance Squared,
Isohyetal Mapping, or any method deemed appropriate.
374 Entering depth and time weights for the selected gages
14.4.3 Gridded Precipitation

The Gridded Precipitation Method is designed to work with the ModClark Gridded Transform. However, it
can be used with other Area-Average Transform Methods as well. The most common use of the method is
to utilize radar-based precipitation estimates. Using additional software, it is possible to develop a gridded
representation of gage data or to use output from atmospheric models. If it is used with a transform method
other than ModClark, an area-weighted average of the grid cells in the subbasin is used to compute the
precipitation hyetograph for each subbasin.
The Gridded Precipitation Method includes a Component Editor with parameter data for all subbasins in the
Meteorologic Model. The Watershed Explorer provides access to the Precipitation Component Editor using
a picture of raindrops.

375 A Meteorologic Model using the Gridded Precipitation Method with a Component Editor for all subbasins
gridded precipitation. Gridded precipitation data must be stored as a precipitation grid before it can be used
in the Meteorologic Model. The data may be from radar sources or could be the result of complex
calculations exterior to the program. Regardless, the grid data must be stored as a precipitation grid. Only
precipitation grids already defined will be shown in the selection list. If there are many different gridsets
available, you may wish to choose a gridset from the selector accessed with the Grid button next to the
selection list. The selector displays the description for each gridset, making it easier to select the correct
one.
376 Precipitation Component Editor for the Gridded Precipitation Method
Numerous tutorials demonstrating the usage of gridded precipitation data within HEC-HMS can
be found here: Working with Gridded Boundary Condition Data42.
42 https://www.hec.usace.army.mil/confluence/hmsdocs/hmsguides/working-with-gridded-boundary-condition-data

14.4.3.1 Time Shift

All calculations during a simulation are computed assuming an arbitrary local time zone that does not
observe summer time (daylight savings in the United States). It is common for gridded precipitation data to
be referenced in Coordinated Universal Time (UTC). Three Time Shift methods are included which can be
used to adjust gridded precipitation data in time.
14.4.3.1.1 None
The None time shift method should be used if all time series and grid data are referenced to the same time
zone. The gridded precipitation data will not be shifted in time when using this method.
14.4.3.1.2 User-Specified
The User-Specified time shift method can be used to correct for precipitation grids stored with a time zone
offset. To use this method, select the User-Specified option within the Time Shift method drop down menu,
as shown below.
377 Using the User-Specified Time Shift Method
Set the shift to zero if all the time-series and grid data is referenced in same local time zone. If other data
sources such as observed discharge or temperature are referenced in local time and the precipitation grid is
in UTC, select the correct shift so that the precipitation data will match the rest of the data.
Local time zones located to the West of the zero longitude line will use a positive shift when the
precipitation grid is referenced in UTC. Local time zones located to the East of the zero longitude
line will use a negative shift when the precipitation grid is referenced in UTC.
14.4.3.1.3 Normalize Start
The Normalize Start time shift method can be used to adjust the time of the first grid in a grid set to the start
time of the simulation. To use this method, select the Normalize Start option within the Time Shift method
drop down menu, as shown below.

378 Using the Normalize Start Time Shift Method
14.4.3.2 Transpose
The ability to shift a storm from one area to another nearby area with similar meteorologic characteristics
allows the user to apply precipitation data to desired locations with missing or unavailable records based on
spatial proximity. This is known as a substituting space for time. To use this method, select the Yes option
within the Transpose drop down menu and enter valid X- and Y-Coordinates, as shown below.
379 Transposing Gridded Precipitation
A tutorial demonstrating the use of the Transpose options can be found here: Transposing
Gridded Precipitation43.
In version 4.11, the specified X and Y coordinates must be in the same unit system as the
coordinate reference system of the precipitation data.
43 https://www.hec.usace.army.mil/confluence/hmsdocs/hmsguides/new-tutorials-to-check-out/transposing-gridded-precipitation

14.4.3.3 Bias Grid

Gridded precipitation can be adjusted using a bias correction grid. This option is typically used in
mountainous regions where terrain between weather stations plays a significant role in the magnitude of
precipitation, but it can be used any time the user wants to use a "bias" grid to adjust, or pattern, the
distribution of precipitation. Often PRISM 30-year normal or monthly grids are used as the bias grid. To use
this method, select a valid Precipitation Bias grid within the Bias Grid drop down menu, as shown below.
380 Using a Bias Grid
A tutorial detailing the gridded precipitation bias computations can be found here: Bias
Adjustment For Transposed Precipitation44.
HMR 52 Storm
The HMR 52 Storm is one approach to computing the probable maximum precipitation for a watershed as
detailed in Hydrometeorological Report No 52 (Hansen, Schreiner, and Miller, 1982). Concentric ellipses are
used to construct the storm spatial pattern where each ellipse represents an isohyet of precipitation depth.
The storm is located over the watershed by specifying the center of the pattern and the angle of the major
axis of the ellipses. Total precipitation depth is computed using a specified storm area and area-duration
precipitation curves. The total precipitation depth is converted to a temporal pattern based on the selected
placement of the peak intensity within the storm duration. The most intense 6-hour period of the storm is
constructed using the ratio of precipitation depth between the largest and sixth-largest hours.
HEC-HMS computes the precipitation hyetograph for each subbasin intersecting the polygon outline of the
subbasin with the storm. The geometric data for the polygon outline comes from the same source as GIS
features (See Drawing Elements and Labels). It is optional to use GIS features for drawing subbasin
elements in the Basin Map. However, the subbasin GIS features become required for using the HMR 52
storm.
The HMR 52 Storm Method includes several parameters to describe the location, orientation, and temporal
distribution of the storm plus additional information on the area reduction. The X and Y Coordinate
44 https://www.hec.usace.army.mil/confluence/hmsdocs/hmsguides/new-tutorials-to-check-out/transposing-gridded-precipitation/bias-
adjustment-for-transposed-precipitation

parameters are used to specify the center of the storm pattern. The coordinate values should be entered
using the same coordinate system as the geometric data for the subbasin polygons. The preferred
orientation is measured in degrees increasing clockwise from north. The actual orientation is also measured
in degrees increasing clockwise from North. Following guidelines in Hydrometeorological Report No 52
(HMR 52), a reduction is applied when the actual orientation deviates from the preferred orientation by more
than 40 degrees. As stated in HMR52, the storm orientation should be bounded by 135 and 315 degrees.
381 Precipitation Component Editor for the HMR 52 Storm
The HMR 52 Storm is 72 hours long and begins at the simulation start time. The Peak Intensity parameter
specifies the period within the 72-hour storm when the precipitation rate will be greatest. The 6-hour period
of peak intensity can be set to begin as early as hour 24 of the storm or as late as hour 60 of the storm. The
depth of rain falling during the period of peak intensity is subdivided into 1-hour increments using the
parameter for the Ratio of the 1-Hour to 6-Hour Depth.
The Total Storm Area must be specified. Additionally, a Duration-Precipitation function must be selected for
the range of possible storm areas. In general, the curves are constructed using data available in
Hydrometeorological Report No 51 (Schreiner and Riedel, 1978). Each duration-precipitation function must
be defined in the Paired Data Manager before it can be selected. You can press the Paired Data button next
to the selection list to use a chooser. The chooser shows all of the available duration-precipitation functions
in the project.
The HMR 52 Storm Method creates a storm from input specified by the user including storm center,
orientation, and area. The optimization trial compute option can be used to automatically select these
parameters in order to maximize peak runoff, or volume, or reservoir pool elevation.

14.4.4 Interpolated Precipitation

can be created by interpolating point observations recorded at weather stations. The Interpolated
Temperature Method allows the user to develop an interpolated temperature grid based on point
temperature gage data.
The Interpolated Precipitation Method includes a Component Editor with parameter data for all subbasins in
the Meteorologic Model. The Watershed Explorer provides access to the Precipitation Component
Editor with picture of raindrops.
The Component Editor for each subbasin in the Meteorologic Model is used to enter parameter data that
defines the Interpolation Method and to select precipitation gages to use in the interpolation.
grid cells.
An optional Adjustment Method can be set. Select Adjustment Method | Fixed and input the rate at which
the precipitation will change with elevation, in the appropriate units. The lapse rate will adjust interpolated
precipitation throughout the basin model based on the terrain data.
Select Precipitation Gages in the dropdown rows under the Gage column. The Radius of Influence is an
optional parameter and represents the maximum interpolation distance. Beyond its radius of influence, the
gage will not affect the cell values of the interpolated grid. Precipitation Gages used in this method must be
loaded in as Time-Series of Precipitation Data with defined latitude and longitude information.
14.4.5 Inverse Distance

The Inverse Distance Method was originally designed for application in real-time forecasting systems. It can
use recording gages that report on a regular interval like 15 minutes or 1 hour. It can also use gages that only
report daily precipitation totals. Because it was designed for real-time forecasting, it has the ability to
automatically switch from using close gages to using more distant gages when the closer gages stop
reporting data. The latitude and longitude of the gages is used to determine closeness to one or more nodes
specified in each subbasin. The distance at which gages are used for a subbasin is controlled by the search
distance. Optionally, an index depth can be assigned to each gage and subbasin node. The index is used to
adjust for regional bias in annual or monthly precipitation.
The Inverse Distance Method includes several options for processing precipitation gage data. The Indexing
option is used to adjust gage data when there are regional trends in precipitation patterns. Using the index
option requires the specification of an index value for each precipitation gage and each node in each

subbasin. The average annual precipitation total is often used as the index at a gage, and the estimated
average annual precipitation at a node location is often used as the index for a subbasin node. Alternately,
the monthly average values may be used at each gage and each node. The Search Distance option can be
used to limit the influence distance of precipitation gages. When no search distance is specified, the default
value of 1,000 kilometers is used. When an optional distance is entered, gages are only used at a subbasin
node if they are within the specified distance.
382 Selecting options for the Inverse Distance Precipitation Method
The Inverse Distance Method includes a Component Editor for specifying the parameter data for
precipitation gages. A Component Editor is also included for each individual subbasin in the Meteorologic
Model. The Watershed Explorer provides access to the gage component editor using a picture of a
measurement gage, and provides access to the Precipitation Component Editor for each subbasin with a
picture of raindrops.
383 A Meteorologic Model using the Inverse Distance Precipitation Method with a Component Editor for precipitation gages and a
separate component editor for each individual subbasin
The Component Editor for all precipitation gages in the Meteorology Model is used to select gages for
processing, control how they are processed, and enter optional indexing parameter data. All gages used in
the Inverse Distance Method must be setup in the Time-Series Data Manager before they can be used.

The Component Editor will subsequently show all available precipitation gages. You may determine which
gages will be used in the Meteorology Model by setting the appropriate choice in the Use Gage column.
384 Selecting which time-series gages to use for a subbasin included in a Meteorologic Model with the Inverse Distance Precipitation
Method Selected
385 (OLD) Selecting which time-series gages to use for a subbasin included in a Meteorologic Model with the Inverse Distance
Precipitation Method selected. The index precipitation is optional.
Each precipitation gage may use any of the allowable time intervals from 1 minute to 24 hours. When a gage
is selected as a daily gage, it is assumed during calculations that the daily precipitation depth is known but
there is no timing information. Usually daily gages are stored with a 24-hour time interval, but any interval
may be used. Daily gage data is only used during processing for days where the entire day is within the
simulation time window. When a gage is not selected as a daily gage, the data it contains is interpolated to
the simulation time step. The appropriate setting should be made in the Daily Gage column.
The Optional Index is entered for each gage. If you enter an index for a gage, it can only be used during a
simulation if you also specify an index for all gages used in a subbasin and also specify an index for each
node in that subbasin. Turning off the Use Indexing option will remove all indexes from the Meteorologic
Model.
The Component Editor for each subbasin in the Meteorologic Model is used to create one or more nodes and
enter the coordinates for each node. A minimum of one node is required. To create a new node, access the
Node Weights tab and enter a node name in the first column of the last row. The last row is always kept
blank for creating new nodes. You can rename a node by typing over the name in the first column. You can
delete a node by deleting its name from the first column and any data from the other columns. You must

always enter a weight for a node. The weight controls how the final hyetograph is computed for the subbasin
from the hyetographs computed at each node. If you have enabled the indexing option, you should also enter
the index for each node. The index is used to adjust for regional bias in annual or monthly precipitation.
All nodes that you have created will be shown on the Latitudes and Longitudes tabs. You must enter the
appropriate coordinate information for each node. Coordinates may be entered using degree-minute-second
format or alternately may be entered using decimal degree format. The data entry format is selected in
386 (OLD) Creating an inverse distance node in a subbasin
14.4.6 Hypothetical Storm

The Hypothetical Storm replaced the SCS Storm Method available in HEC-HMS version 4.2.1 and prior
versions. The Hypothetical Storm is a general approach that allows users to enter the Storm Duration, Depth,
Area Reduction Information, the Temporal Pattern, and Storm Area. The Component Editor with parameter
data for all subbasins in the Meteorologic Model can be accessed from the Watershed Explorer using a
picture of raindrops. In addition, a separate Component Editor has parameter data for each individual
subbasin.

387 Meteorologic model using Hypothetical Storm
The Component Editor for all subbasins in the Meteorologic Model specifies the parameter data for the
storm. The Method selection is required to set the temporal pattern approach for the hypothetical storm.
Options include the 4 Standard SCS Temporal Patterns (SCS Type 1, SCS Type 1A, SCS Type 2, and SCS
Type 3), a User-Specified Pattern, and an Area-Dependent Temporal Pattern. The following figure shows
the User-Specified Pattern option selected for the method. When this option is selected, the user must
define the Storm Pattern and the Storm Duration in addition to the Depth and Area-Reduction Information.
The user defined Storm Pattern is entered as a percentage curve in the Paired Data Manager. The
independent variable is percent of the total storm duration (values should be 0 to 100 percent) and the
dependent value is percent of the point depth (which is automatically reduced based on the area-reduction
information and storm area). The 4 standard SCS temporal patterns are built into HEC-HMS. Each of the SCS
storms are 24 hours long. The simulation must have a duration of 24 hours or longer. All precipitation values
after the first 24 hours will be zero. The Area-Dependent Pattern option is designed to work in conjunction
with the Depth-Area Analysis compute option. When Area-Dependent Pattern is selected, the user must
define a Number of Storm Temporal Patterns for different storm areas. HEC-HMS interpolates between the
temporal patterns using the user defined storm area, or the area for an analysis point in the Depth-Area
analysis.
388 Precipitation Component Editor for the Hypothetical Storm precipitation method, with Point Depth precipitation specification

The user can define the Storm Depth and Area-Reduction Information after the temporal pattern is selected.
There are two options for specifying the storm depth under the Precipitation Method. The first is Point
Depth, which requires the user to enter a single point depth value that will be used for every subbasin in the
Meteorologic Model , if Uniform For All Subbasins spatial distribution is selected, as shown in Figure above.
Alternatively, the user can enter a separate point depth for each subbasin in the Component Editor if the
Spatial Distribution option is set to Variable by Subbasin and the Precipitation Method is set to Point Depth.
A depth can only be entered in the individual subbasin's Component Editor as shown below. The user must
also specify a Storm Area when using the Point Depth Method.
389 Component editor to enter point depth for an individual subbasin if Variable by Subbasin spatial distribution is selected.
The second option for the precipitation method is Precipitation-Frequency Grid (shown in the following
figure), where the user can specify a Precipitation-Frequency Grid, created as a grid dataset. The user must
also specify a Computation Point for this method. This method can only be used with georeferenced Basin
Models, because HEC-HMS will automatically intersect the precipitation-frequency grid with the sub-basin
polygons to compute the basin-average precipitation value, as well as automatically compute the storm area,
equal to the drainage area above the computation point. If Variable by Subbasin spatial distribution is
selected with the Precipitation-Frequency Grid precipitation method, a separate precipitation depth value for
each subbasin is calculated rather than the basin-average.

390 Precipitation Component Editor for the Hypothetical Storm Precipitation Method, with Precipitation-Frequency Grid precipitation
specification
There is an Area Reduction Method, the user can choose between None, TP40, and User-Specified. The
None options means the Point Depth or Precipitation-Frequency Grid will be used to compute the subbasin
hyetograph. The 24-hour area reduction curve from TP40 is used when TP40 is selected for the Area
Reduction Method. The TP40 Area Reduction Method should only be selected when one of the SCS temporal
patterns is selected or when a 24-Hour Storm Duration with a User-Specified Temporal Pattern is selected.
A Storm Area is required for both the TP40 and User-Specified area reduction options. HEC-HMS will
interpolate the reduction factor from the TP40 or User-Specified area reduction curve to update the storm
depth.
The Hypothetical Storm will work with the Depth-Area Analysis compute option, similar to the Frequency
Storm Precipitation Method. The Drainage Area at each of the user-defined analysis points will replace the
storm area during the depth-area analysis simulation. The appropriate temporal pattern and precipitation
depth are computed for each storm area when the area-dependent temporal pattern option is selected. When
the Precipitation-Frequency Grid Precipitation Method is used, the Depth-Area Analysis will compute the
basin-average precipitation from the grid for each computation point as well. The Depth-Area Analysis will
also override any computation point selected in the Hypothetical Storm precipitation method and only use
those specified in the Depth-Area Analysis.
14.4.7 Specified Hyetograph

The Specified Hyetograph Method allows the user to specify the exact time-series to use for the hyetograph
at subbasins. This method is useful when precipitation data will be processed externally to the program and
essentially imported without alteration. This method is also useful when a single precipitation gage can be
used to represent what happens over a subbasin.
The Specified Hyetograph Method includes an option for processing precipitation gage data. The Total
Override option is used to adjust the precipitation depth at each gage. Without the override, the total depth at
a gage is the sum of the values in the gage record. With the override, the values in the gage record are
proportionally adjusted to have a sum equal to the specified total value.

391 Selecting options for the Specified Hyetograph Precipitation Method
The Specified Hyetograph Method uses a Component Editor with parameter data for all subbasins in the
Meteorologic Model. The Watershed Explorer provides access to the Component Editor using a picture of
raindrops.
392 A Meteorologic Model using the Specified Hyetograph Precipitation Method with a Component Editor for all subbasins
The Component Editor for all subbasins in the Meteorologic Model includes the Gage Selection for each
subbasin and the optional Depth Override for each subbasin. A Hyetograph must be stored as a precipitation
gage before it can be used in the Meteorologic Model. The data may actually be from a recording gage or
could be the result of complex calculations exterior to the program. Regardless, the hyetograph must be
stored as a gage. You may use the same gage for more than one subbasin. For each subbasin in the table,
select the gage to use for that subbasin. Only precipitation gages already defined in the Time-Series Data
Manager will be shown in the selection list.

393 Selecting a gage for each subbasin
394 (OLD) Selecting a gage for each subbasin. Total depth override is optional.
Optionally, you may enter a Total Depth for each subbasin. If no total depth is entered, the depth will be the
sum of the data actually stored in the precipitation gage. However, if a total depth is entered for a subbasin,
the exact pattern is maintained but the magnitude of precipitation at each time step is adjusted
proportionally so that the specified depth is applied over the entire simulation. Total depth can be specified
for no subbasins, one subbasin, many subbasins, or all subbasins. It is not required to enter the depth for all
subbasins in order to specify it for just one subbasin.
14.4.8 Standard Project Storm

The Standard Project Storm Method implements the requirements of Engineering Manual EM-1110-2-1411
(Corps 1965). While the methodology is no longer frequently used, it is included in the program for projects
where it may still necessary.
The Standard Project Storm Method includes a Component Editor with parameter data for all subbasins in
the Meteorologic Model. The Watershed Explorer provides access to the Precipitation Component Editors
using a picture of raindrops.

395 A Meteorologic Model using the Standard Project Storm Method with a Component Editor for all subbasins
storm. The Precipitation Index represents the depth of rainfall during the storm. This index is not the same
as the probable maximum precipitation and does not have an associated exceedance probability. The index
in selected from a map in the Engineering Manual.
The Storm Area is used to automatically compute the depth-area reduction factor, based on figures in the
Engineering Manual. In most cases the specified storm area should be equal to the watershed drainage area
at the point of evaluation.
The Distribution determines how the adjusted precipitation depth for each subbasin is shaped into a
hyetograph; it must be selected from the list of available choices. The Standard option uses the procedure
specified in the Engineering Manual to distribute the adjusted storm depth. The Southwest Division option
uses a different procedure that may be more applicable in some watersheds.
The Transposition Factor accounts for the location of a subbasin in the watershed, relative to the center of
the storm. The Engineering Manual contains an isohyetal map with concentric rings labeled in percent. If a
subbasin is generally covered by the 120% isohyetal line, then a factor of 1.20 should be entered n the
program.
396 Entering properties of the Standard Project Storm

397 Entering a transposition factor for each subbasin
14.5 Temperature
Temperature is the intensity of heat present in the air. Air temperature is affected by a variety of factors
including Latitude, Altitude, Topography, and the presence of Vegetation or Waterbodies. Temperature also
plays an integral role in several other meteorologic processes available to be modeled in HEC-HMS including
Evapotranspiration, Shortwave Radiation, Longwave Radiation, and Snowmelt.
The Temperature Method included in the Meteorologic Model is required when certain types of
Evapotranspiration, Shortwave Radiation, Longwave Radiation Methods are used. Three methods Gridded
Temperature, Interpolated Temperature and Specified Thermograph are available for adding Temperature
data to the Meterologic Model. More detail about each method is provided in the following sections.
14.5.1 Gridded Temperature

The most common use of the Gridded Temperature Method is to utilize radar-based temperature estimates.
Using additional software, it is possible to develop a gridded representation of temperature data or to use
output from atmospheric models. If it is used with a transform method other than ModClark, an area-
weighted average of the grid cells in the subbasin is used to compute the thermograph for each subbasin.
The Gridded Temperature Method includes a Component Editor with parameter data for all subbasins in the
Meteorologic Model. The Watershed Explorer provides access to the Temperature Component Editor.

398 A Meteorologic Model using the Gridded Temperature Method with a Component Editor for all subbasins
The Component Editor for all subbasins in the Meteorologic Model includes the selection of a datasource.
Gridded temperature data must be stored as a temperature grid before it can be used in the Meteorologic
Model. The data may be from radar sources or could be the result of complex calculations exterior to the
program. Regardless, the grid data must be stored as a temperature grid. Only temperature grids already
defined will be shown in the selection list. If there are many different gridsets available, you may wish to
choose a gridset from the selector accessed with the Grid button next to the selection list. The selector
displays the description for each gridset, making it easier to select the correct one.
399 Temperature Component Editor for the Gridded Temperature Method
Numerous tutorials demonstrating the usage of gridded temperature data within HEC-HMS can
be found here: Working with Gridded Boundary Condition Data45.
14.5.1.1 Time Shift

observe summer time (daylight savings in the United States). It is common for gridded temperature data to
45 https://www.hec.usace.army.mil/confluence/hmsdocs/hmsguides/working-with-gridded-boundary-condition-data

be referenced in Coordinated Universal Time (UTC). Three Time Shift methods are included which can be
used to adjust gridded temperature data in time.
14.5.1.1.1 None
The None time shift method should be used if all time series and grid data are referenced to the same time
zone. The gridded temperature data will not be shifted in time when using this method.
14.5.1.1.2 User-Specified
The User-Specified time shift method can be used to correct for temperature grids stored with a time zone
offset. To use this method, select the User-Specified option within the Time Shift method drop down menu,
as shown below.
400 Using the User-Specified Time Shift Method
Set the shift to zero if all the time-series and grid data is referenced in same local time zone. If other data
sources such as observed discharge or precipitation are referenced in local time and the temperature grid is
in UTC, select the correct shift so that the temperature data will match the rest of the data.
Local time zones located to the West of the zero longitude line will use a positive shift when the
temperature grid is referenced in UTC. Local time zones located to the East of the zero longitude
line will use a negative shift when the temperature grid is referenced in UTC.
14.5.1.1.3 Normalize Start
The Normalize Start time shift method can be used to adjust the time of the first grid in a grid set to the start
time of the simulation. To use this method, select the Normalize Start option within the Time Shift method
drop down menu, as shown below.

401 Using the Normalize Start Time Shift Method
14.5.2 Interpolated Temperature

Temperature Method allows the user to develop an interpolated temperature grid based on point
temperature gage data.
402 Selecting the Interpolated Temperature method in the meteorological model component editor.
The Interpolated Temperature Method includes a Component Editor with parameter data for all subbasins in
the Meteorologic Model. The Watershed Explorer provides access to the Temperature Component Editor.
defines the Interpolation Method and to select temperature gages to use in the interpolation.

403 Selecting the Inverse Distance Interpolation Method for Interpolated Temperature
grid cells.
An optional Adjustment Method can be set. Select Adjustment Method | Fixed and input the rate at which
the temperature will change with elevation, in the appropriate units. The Lapse Rate will adjust interpolated
temperature throughout the basin model based on the terrain data.
Select Temperature Gages in the dropdown rows under the Gage column. The Radius of Influence is an
gage will not affect the cell values of the interpolated grid. Temperature Gages used in this method must be
loaded in as Time-Series of Temperature Data with defined latitude and longitude information.

404 Choosing Lapse as the Adjustmnent Method, setting a Lapse Rate and selecting gages and Radius of Influence for the Interpolated
Temperature Method.
An interpolated temperature grid will be created once the simulation has been computed. Once the compute
is complete the interpolated grid will be saved with the same name as the Meterologic Model in DSS
format in the HEC-HMS project directory.
14.5.3 Specified Thermograph

The Specified Thermograph Method includes a Component Editor with parameter data for all subbasins in
the Meteorologic Model. The Watershed Explorer provides access to the Temperature Component Editors.
405 A Meteorologic Model using the Specified Thermograph Temperature Method with a Component Editor for all subbasins
Temperature for each subbasin. A Temperature Gage must be selected for a subbasin. The current gages
are shown in the selection list. An optional Adjustment Method can be set for each Subbasin.
Select Adjustment Method | Fixed and input the rate at which the temperature will change with elevation, in

the appropriate units. The Lapse Rate will adjust interpolated temperature throughout the basin model based
on the terrain data.
406 Selecting a temperature gage for each subbasin. The Lapse Rate Adjustment Method is optional.
14.6 Windspeed
Windspeed is a measure of how fast air is moving past a certain point. Windspeed is impacted by Pressure
Gradients and Air Temperature. Windspeed also plays an integral role in other meteorologic processes
available to be modeled in HEC-HMS including Evapotranspiration and Longwave Radiation.
The Windspeed Method included in the Meteorologic Model is required when certain types
of Evapotranspiration Methods or Longwave Radiation Methods are used. Three methods, Gridded
Windspeed, Interpolated Windspeed, and Specified Thermograph are available for adding windspeed data to
the Meterologic Model. More detail about each method is provided in the following sections.
14.6.1 Gridded Windspeed

The most common use of the Gridded Windspeed Method is to utilize radar-based windspeed estimates.
Gridded windspeed data may come from other software or be the output from atmospheric models. If
Gridded Windspeed is used with a transform method other than ModClark, an area-weighted average of the
grid cells in the subbasin is used to compute the thermograph for each subbasin.
The Gridded Windspeed Method includes a Component Editor with parameter data for all subbasins in the
Meteorologic Model. The Watershed Explorer provides access to the Windspeed Component Editor.

407 A Meteorologic Model using the Gridded Windspeed Method with a Component Editor for all subbasins
Gridded windspeed data must be stored as a windspeed grid before it can be used in the Meteorologic
program. Regardless, the grid data must be stored as a windspeed grid. Only windspeed grids already
408 Windspeed Component Editor for the Gridded Windspeed Method
The Time Shift can be used to correct for windspeed grids stored with a time zone offset. All calculations
during a simulation are computed assuming an arbitrary local time zone that does not observe summer time
(daylight savings in the United States). Set the shift to zero if all the time-series and grid data is referenced in
same local time zone. If other data sources such as observed discharge or precipitation are referenced in
local time and the windspeed grid is in referenced to a different time zone, select the correct shift so that the
windspeed data will match the rest of the data.
14.6.2 Interpolated Windspeed


Windspeed Method allows the user to develop an interpolated windspeed grid based on point windspeed
gage data.
The Interpolated Windspeed Method includes a Component Editor with parameter data for all subbasins in
the Meteorologic Model. The Watershed Explorer provides access to the Windspeed Component Editor.
defines the Interpolation Method and to select windspeed gages to use in the interpolation.
409 Selecting the Inverse Distance Interpolation Method for Interpolated Windspeed
grid cells.
Select Windspeed Gages in the dropdown rows under the Gage column. The Radius of Influence is an

gage will not affect the cell values of the interpolated grid. Windspeed Gages used in this method must be
loaded in as Time-Series of Windspeed Data with defined latitude and longitude information.
410 Selecting gages and Radius of Influence for the Interpolated Windspeed Method
An interpolated windspeed grid will be created once the simulation has been computed. Once the compute is
complete, the interpolated grid will be saved with the same name as the Meterologic Model in DSS format in
the HEC-HMS project directory.
14.6.3 Specified Anemograph

The Specified Anemograph Method includes a Component Editor with parameter data for all subbasins in
the Meteorologic Model. The Watershed Explorer provides access to the Windspeed Component Editors.
411 A Meteorologic Model using the Specified Anemograph Windspeed Method with a Component Editor for all subbasins

Windspeed for each subbasin. A Windspeed Gage must be selected for a subbasin. The current gages are
shown in the selection list.
412 Selecting a wind gage for each subbasin
14.7 Pressure
Pressure in meteorologic terms is the pressure exerted by the weight of the atmosphere. Pressure is
affected by a variety of factors including Air Temperature, Altitude, and Humidity. Pressure also plays an
integral role in several other meteorologic processes available to be modeled in HEC-HMS
including Evapotranspiration, Relative Humidity, Longwave Radiation, and Snowmelt.
The Pressure Method included in the Meteorologic Model is required when certain types
of Evapotranspiration Methods or Longwave Radiation Methods are used. Two methods Gridded Pressure
and Specified Barograph are available for adding pressure data to the Meterologic Model. More detail about
each method is provided in the following sections.
14.7.1 Gridded Pressure

The most common use of the Gridded Pressure Method is to utilize radar-based pressure estimates. Using
additional software, it is possible to develop a gridded representation of pressure data or to use output from
atmospheric models. If it is used with a transform method other than ModClark, an area-weighted average of
the grid cells in the subbasin is used to compute the thermograph for each subbasin.
The Gridded Pressure Method includes a Component Editor with parameter data for all subbasins in the
Meteorologic Model. The Watershed Explorer provides access to the Pressure Component Editor.

413 A Meteorologic Model using the Gridded Pressure Method with a Component Editor for all subbasins
The Component Editor for all subbasins in the Meteorologic Model includes the selection of a data source.
Gridded Pressure data must be stored as a pressure grid before it can be used in the Meteorologic Model.
The data may be from radar sources or could be the result of complex calculations exterior to the program.
Regardless, the grid data must be stored as a temperature grid. Only pressure grids already defined will be
shown in the selection list. If there are many different gridsets available, you may wish to choose a gridset
from the selector accessed with the Grid button next to the selection list. The selector displays the
description for each gridset, making it easier to select the correct one.
414 Pressure Component Editor for the Gridded Pressure Method
The Time Shift can be used to correct for pressure grids stored with a time zone offset. All calculations
during a simulation are computed assuming an arbitrary local time zone that does not observe summer time
(daylight savings in the United States). Set the shift to zero if all the time-series and grid data is referenced in
same local time zone. If other data sources such as observed discharge or precipitation are referenced in
local time and the pressure grid is in referenced to a different time zone, select the correct shift so that the
pressure data will match the rest of the data.
14.7.2 Specified Barograph

The Specified Barograph Method includes a Component Editor with parameter data for all subbasins in the
Meteorologic Model. The Watershed Explorer provides access to the Pressure Component Editors.

415 A Meteorologic Model using the Specified Barograph Pressure Method with a Component Editor for all subbasins
Pressure for each subbasin. A Pressure Gage must be selected for a subbasin. The current gages are shown
in the selection list.
416 Selecting a pressure gage for each subbasin.
14.7.3 Interpolated Pressure

can be created by interpolating point observations recorded at weather stations. The Interpolated Pressure
Method allows the user to develop an interpolated pressure grid based on point pressure gage data.
The Interpolated Pressure Method includes a Component Editor with parameter data for all subbasins in the
Meteorologic Model. The Watershed Explorer provides access to the Shortwave Component
that defines the Interpolation Method and to select radiation gages to use in the

417 A Meteorologic Model using the Interpolated Pressure Method
grid cells.
Select Pressure Gages in the dropdown rows under the Gage column. The Radius of Influence is an optional
not affect the cell values of the interpolated grid. Pressure Gages used in this method must be loaded in
as Time-Series of Pressure Data with defined latitude and longitude information.
418 Interpolated Pressure Component Editor

An interpolated pressure grid will be created once the simulation has been computed. Once the compute is
complete the interpolated grid will be saved with the same name as the Meterologic Model in DSS format in
14.7.4 Barometric Pressure

The Barometric Pressure Method implements the atmospheric pressure algorithm described within Follum
et al. (2015). The method calculates the atmospheric pressure at a specific location (grid cell or subbasin) by
altering standard atmospheric pressure at sea-level (101.325 kPa) using a defined lapse rate. If the basin
model is not georeferenced and/or doesn't have an associated terrain model, these calculations will proceed
assuming the location is at sea-level.
The Barometric Pressure Method includes a Component Editor with parameter data for all subbasins in the
Meteorologic Model. The Watershed Explorer provides access to the Barometric Pressure Editor, as shown
419 A Meteorologic Model using the Barometric Pressure Method
The Barometric Pressure Component Editor is shown in the following figure. The user must select a lapse
method and provide an appropriate parameterization.
420 Barometric Pressure Component Editor

14.8 Dew Point

Dew Point is the temperature below which droplets condense and form dew. Air temperature is affected by a
variety of factors including Latitude, Altitude, Topography, and the presence
of Vegetation or Waterbodies. The dew point also plays an integral role in several other meteorologic
processes available to be modeled in HEC-HMS including Evapotranspiration and Longwave Radiation.
The Dew Point Method included in the Meteorologic Model is required when certain types of
Evapotranspiration Methods or Longwave Radiation Methods are used. Seven methods (Gridded Dew Point
Temperature, Gridded Humidity, Interpolated Dew Point Temperature, Interpolated Humidity, Precipitation
Index Humidity, Specified Dew Point Thermograph, and Specified Humidograph) are available for adding
Dew Point data to the Meterologic Model. More detail about each method is provided in the following
sections.
14.8.1 Gridded Dew Point Temperature

The most common use of the Gridded Dew Point Temperature Method is to utilize radar-based temperature
estimates. Using additional software, it is possible to develop a gridded representation of temperature data
or to use output from atmospheric models. If it is used with a transform method other than ModClark, an
area-weighted average of the grid cells in the subbasin is used to compute the thermograph for each
subbasin.
The Gridded Dew Point Temperature Method includes a Component Editor with parameter data for all
subbasins in the Meteorologic Model. The Watershed Explorer provides access to the Dew Point Component
Editor.
421 A Meteorologic Model using the Gridded Dew Point Temperature Method with a Component Editor for all subbasins
Gridded temperature data must be stored as a temperature grid before it can be used in the Meteorologic
program. Regardless, the grid data must be stored as a temperautre grid. Only temperature grids already

The Time Shift Method can be used to correct timing for temperature grids stored with a time zone offset.
observe summer time (daylight savings in the United States). Normalize Start shifts the time of the first grid
in a gridset to the simulation start time.
User-Specified allows the user to set the Time Shift from the grid time zone to the local time zone. Set the
shift to zero if all the time-series and grid data is referenced in same local time zone. If other data sources
such as observed discharge or precipitation are referenced in local time and the temperature grid is
referenced to a different time zone, select the correct shift so that the temperature data will match the rest of
the data.
14.8.2 Gridded Humidity

The Gridded Humidity Method provides a spatially varied and continuous dataset of humidity
measurements. If it is used with a transform method other than ModClark, an area-weighted average of the
grid cells in the subbasin is used to compute the humidity for each subbasin.
The Gridded Humidity Method includes a Component Editor with parameter data for all subbasins in the
Meteorologic Model. The Watershed Explorer provides access to the Dew Point Component Editor.

422 A Meteorologic Model using the Gridded Humidity Method with a Component Editor for all subbasins
Gridded humidity data must be stored as a humidity grid before it can be used in the Meteorologic Model.
The data may be from radar sources or could be the result of complex calculations exterior to the program.
Regardless, the grid data must be stored as a humidity grid. Only humidity grids already defined will be
shown in the selection list. If there are many different gridsets available, you may wish to choose a gridset
from the selector accessed with the Grid button next to the selection list. The selector displays the
description for each gridset, making it easier to select the correct one.
The Time Shift Method can be used to correct timing for humidity grids stored with a time zone offset. All
calculations during a simulation are computed assuming an arbitrary local time zone that does not observe
summer time (daylight savings in the United States). Normalize Start shifts the time of the first grid in a
gridset to the simulation start time.
User-Specified allows the user to set the Time Shift from the grid time zone to the local time zone. Set the
shift to zero if all the time-series and grid data is referenced in same local time zone. If other data sources

such as observed discharge or precipitation are referenced in local time and the humidity grid is referenced
to a different time zone, select the correct shift so that the humidity data will match the rest of the data.
14.8.3 Interpolated Dew Point Temperature

can be created by interpolating point observations recorded at weather stations. The Interpolated Dew Point
Temperature Method allows the user to develop an interpolated dew point temperature grid based on point
dew point temperature gage data.
The Interpolated Dew Point Temperature Method includes a Component Editor with parameter data for all
that defines the Interpolation Method and to select dew point temperature gages to use in the
423 Selecting the Inverse Distance Interpolation Method for Interpolated Dew Point Temperature

grid cells.
Select Dew Point Temperature Gages in the dropdown rows under the Gage column. The Radius of
Influence is an optional parameter and represents the maximum interpolation distance. Beyond its radius of
influence, the gage will not affect the cell values of the interpolated grid. Dew point temperature gages used
in this method must be loaded in as Time-Series of Temperature Data with defined latitude and longitude
information.
424 Selecting gages and Radius of Influence for the Interpolated Dew Point Temperature Method
An interpolated temperature grid will be created once the simulation has been computed. Once the compute
is complete the interpolated grid will be saved with the same name as the Meterologic
14.8.4 Interpolated Humidity

can be created by interpolating point observations recorded at weather stations. The Interpolated Humidity
Method allows the user to develop an interpolated relative humidity grid based on point relative humidity
gage data.
The Interpolated Humidity Method includes a Component Editor with parameter data for all subbasins in the
Meteorologic Model. The Watershed Explorer provides access to the Humidity Component
that defines the Interpolation Method and to select humidity gages to use in the interpolation.

425 A Meteorologic Model using the Interpolated Humidity Method
grid cells.
Select Humidity Gages in the dropdown rows under the Gage column. The Radius of Influence is an optional
not affect the cell values of the interpolated grid. Humidity gages used in this method must be loaded in as
Time-Series of Humidity Data with defined latitude and longitude information.
426 Interpolated Humidity Component Editor
An interpolated humidity grid will be created once the simulation has been computed. Once the compute is
complete the interpolated grid will be saved with the same name as the Meterologic Model in DSS format in

14.8.5 Specified Dew Point Thermograph

The Specified Dew Point Thermograph Method includes a Component Editor with parameter data for all
Editors.
427 A Meteorologic Model using the Specified Dew Point Thermograph Dew Point Method with a Component Editor for all subbasins
Temperature for each subbasin. A Dew Point Temperature Gage must be selected for a subbasin. The
current gages are shown in the selection list.
428 Selecting a temperature gage for each subbasin
14.8.6 Specified Humidograph

The Specified Humidograph Method includes a Component Editor with parameter data for all subbasins in
the Meteorologic Model. The Watershed Explorer provides access to the Dew Point Component Editors.

429 A Meteorologic Model using the Specified Humidograph Dew Point Method with a Component Editor for all subbasins
Humidity for each subbasin. A Humidity Gage must be selected for a subbasin. The current gages are shown
in the selection list.
430 Selecting a humidity gage for each subbasin
14.8.7 Precipitation Index Humidity

The Precipitation Based Humidity Method implements the relative humidity algorithm described within
Follum et al, (2015). The method estimates the relative humidity at a specific location (grid cell or subbasin)
using the precipitation rate. As such, this method requires the use of a valid precipitation method.
The Precipitation Based Humidity Method includes a Component Editor with parameter data for all
subbasins in the Meteorologic Model. The Watershed Explorer provides access to the Precipitation Based
Humidity Editor, as shown in the following figure.

431 A Meteorologic Model using the Precipitation Index Humidity Method
The Precipitation Based Humidity Component Editor is shown in the following figure. The user must specify
a precipitation rate threshold (in/day or mm/day), wet humidity (%), and dry humidity (%). When the
precipitation rate at the location in question exceeds the specified threshold, the wet humidity will be used.
When the precipitation rate at the location in question is less than or equal to the specified threshold, the dry
humidity will be used.
432 Precipitation Index Humidity Component Editor
14.9 Evapotranspiration
Evapotranspiration is the the combination of evaporation from the ground surface and transpiration by
vegetation. It includes both evaporation of free water from the surface of vegetation and the land surface. It
also includes transpiration which is the process of vegetation extracting it from the soil through the plant
root system. Whether by evaporation or transpiration, water is returned from the land surface or subsurface
to the atmosphere. Even though evaporation and transpiration are taken together, transpiration is
responsible for the movement of much more water than evaporation. Combined evapotranspiration is often
responsible for returning 50 or even 60% of precipitation back to the atmosphere. The theoretical
evapotranspiration, also called the potential evapotranspiration, serves as the upper limit for what can
happen on the land surface based on atmospheric conditions. In all cases, the Meteorologic Model is
computing the potential evapotranspiration and subbasins will calculate actual evapotranspiration based on
soil water limitations.

The Evapotranspiration Method included in the Meteorologic Model is only necessary when using
continuous simulation loss rate methods in subbasins: Deficit Constant, Gridded Deficit Constant, Soil
Moisture Accounting, and Gridded Soil Moisture Accounting. If a continuous simulation loss rate method is
used and no evapotranspiration is specified in the Meteorologic Model, then zero potential
evapotranspiration is used in the subbasins. The options for evapotranspiration include a Physically-Based
Energy Balance Model (Penman Monteith), a Simplified Physically-Based Model (Priestley Taylor), the
Hargreaves and Hamon Temperature Only Methods, and a Simple Monthly Average approach. A specified
method is also included so that evapotranspiration can be calculated external to the program and imported.
Each option produces the potential evapotranspiration rate over the land surface where it can be used in the
subbasin element to compute evaporation from the canopy and surface, and transpiration from the soil.
More detail about each method is provided in the following sections.
14.9.1 Annual Evapotranspiration

The Annual Evapotranspiration Method is designed to work with a maximum daily rate combined with an
optional pattern of variation throughout the year. Specifying only a daily rate can produce good results for
simulations lasting days to weeks if evapotranspiration is fairly consistent each day. The optional pattern
can be used to adjust the applied evapotranspiration rate during simulations lasting weeks to years.
The Annual Evapotranspiration Method includes a Component Editor with parameter data for all subbasins
in the Meteorologic Model. The Watershed Explorer provides access to the Evapotranspiration Component
Editor using a picture of a water pan.
433 A Meteorologic Model using the Annual Evapotranspiration Method with a single Component Editor for all subbasins
The Component Editor for all subbasins in the Meteorologic Model includes the Daily Rate and optional
Pattern for each subbasin. When the optional percentage pattern is not used, the value entered for the daily
rate should generally be the average daily potential evapotranspiration rate over the duration of the
simulation. When a pattern will be added, the value entered for the daily rate should generally be the largest
potential evapotranspiration for any day occurring during the simulation.

434 Entering rates and selecting a percent pattern for each subbasin
The optional Pattern is specified as a percent pattern in the Paired Data Manager. The evapotranspiration for
each day of the simulation is computed by multiplying the entered rate by the percentage interpolated from
the percent pattern. The available percent patterns are shown in the selection list. If there are many different
patterns available, you may wish to choose a pattern from the selector accessed with the Paired Data button
next to the selection list. The selector displays the description for each percent pattern, making it easier to
select the correct one.
14.9.2 Gridded Hamon

The Gridded Hamon Method is the same as the regular Hamon Method (described in a later section) except
that the Hamon equations are applied to each grid cell using separate boundary conditions instead of area-
averaged values over the whole subbasin. The Gridded Hamon Method requires a temperature from
temperature method in the Meteorologic Model.
The Gridded Hamon Method includes a Component Editor with parameter data for all subbasins in the
Meteorologic Model. The Watershed Explorer provides access to the Evapotranspiration Component Editor
using a picture of a water pan.
The Component Editor requires a Hamon Coefficient be selected for all subbasins (shown in the following
figure). A default coefficient of 0.0065 inches per gram per meter cubed is provided; this is equivalent to
0.1651 millimeters per gram per meter cubed. The units inches per gram per meter cubed are implicit in the
Hamon (1963) formulation where the coefficient is presented as a constant: 0.0065. The coefficient can be
adjusted by the user in the Component Editor.

435 Component Editor for the Gridded Hamon Evapotranspiration Method
14.9.3 Gridded Hargreaves

The Gridded Hargreaves Method is the same as the regular Hargreaves Method (described in a later
section) except that the Hargreaves equations are applied to each grid cell using separate boundary
conditions instead of area-averaged values over the whole subbasin. Shortwave radiation is required in the
Hargreaves method so a Gridded Shortwave Radiation Method should also be selected in the Meteorologic
Model. The Gridded Hargreaves Method requires temperature from a temperature method in the
Meteorologic Model.
The Gridded Hargreaves Method includes a Component Editor with parameter data for all subbasins in the
using a picture of a water pan.
436 A Meteorologic Model using the Gridded Hargreaves Evapotranspiration Method with a Component Editor for all subbasins
The Component Editor for all subbasins includes a Hargreaves Evapotranspiration Coefficient (shown in the
following figure). A default coefficient of 0.0075 per degree Fahrenheit is provided; this is equivalent to
0.0135 per degree Celsuis. If the Gridded Hargreaves Evapotranspiration Method is combined with the
Gridded Hargreaves Shortwave Radiation Method, the resulting default coefficient is 0.0023 per degree
Celsius raised to the 3/2 power. This is equivalent to the form presented by Hargreaves and Allen (2003), Eq.
8.

437 Component Editor for the Gridded Hargreaves Evapotranspiration Method
14.9.4 Gridded Penman Monteith

The Gridded Penman Monteith Method is the same as the regular Penman Monteith Method (described in a
later section) except that the Penman Monteith equations are applied to each grid cell using separate
boundary conditions instead of area-averaged values over the whole subbasin. Shortwave and longwave
radiation are inputs to the Penman Monteith Method so both a Shortwave Radiation Method and a
Longwave Radiation Method should also be selected in the Meteorologic Model.
The Gridded Penman Monteith Method includes a Component Editor with parameter data for all subbasins
438 A Meteorologic Model using the Gridded Penman Monteith Evapotranspiration Method with a Component Editor for all subbasins
The Component Editor for all subbasins in the Meteorologic Model is shown in the following figure.
Temperature, Windspeed, Pressure, and Dew Point methods are also required.
A Reference Albedo is required for computing the energy balance at the ground surface. The same value is
applied to all grid cells in all subbasins. A default value of 0.23 is provided.

439 Component Editor for the Gridded Penman Monteith Evapotranspiration Method
14.9.5 Gridded Priestley Taylor

The Gridded Priestley Taylor Method is the same as the regular Priestley Taylor Method (described in a later
section) except the Priestley Taylor equations are applied to each grid cell using separate boundary
conditions instead of area-averaged values over the whole subbasin. Net shortwave radiation is an input to
the Priestley Taylor Method so a Shortwave Radiation Method should also be selected in the Meteorologic
Model.
The Gridded Priestley Taylor Method includes a Component Editor with parameter data. The Watershed
Explorer provides access to the Evapotranspiration Component Editor using a picture of a water pan.
440 A Meteorologic Model using the Gridded Priestley Taylor Evapotranspiration Method with a Component Editor for all subbasins
The Component Editor for all subbasins in the Meteorologic Model includes a Dryness Coefficient which
must be entered for all subbasins. The same coefficient is applied to all grid cells in all subbasins. The
coefficient is used to make small corrections based on soil moisture state. A coefficient should be specified
that represents typical soil water conditions during the simulation. A value of 1.2 can be used in humid
conditions while a value of 1.3 represents an arid environment.
A Temperature method must be selected in the meteorologic model.

441 Component Editor for the Gridded Priestley Taylor Evapotranspiration Method
14.9.6 Hamon
The Hamon Method (Hamon, 1963) is based on an empirical relationship where saturated water vapor
concentration, at the mean daily air temperature, adjusted by a day length factor, is proportional to potential
evapotranspiration. The day length factor accounts for plant response, duration of turbulence, and net
radiation. Daily Average Temperature is the only data requirement. The method has proven effective for
estimating potential evapotranspiration in data-limited situations. The method calculates daily potential
evapotranspiration given daily average temperature. For simulation time steps less than one day, potential
evapotranspiration is redistributed for each time step based on a sinusoidal distribution between sunrise and
sunset.
The Hamon Method includes a Component Editor with parameter data for each individual subbasin in the
using a picture of a water pan. A Temperature method must be selected in the meteorologic model.
442 A Meteorologic Model using the Hamon Evapotranspiration Method with a Component Editor for each individual subbasin
The Component Editor for each subbasin includes a Hamon Coefficient. A default coefficient of 0.0065
inches per gram per meter cubed is provided; this is equivalent to 0.1651 millimeters per gram per meter
cubed. The units inches per gram per meter cubed are implicit in the Hamon (1963) formulation where the

coefficient is presented as a constant: 0.0065. The coefficient can be adjusted by the user in the Component
Editor.
443 Entering the Hamon evapotranspiration coefficient for a subbasin
14.9.7 Hargreaves
The Hargreaves Evapotranspiration Method (Hargreaves and Samani, 1985) is based on an empirical
relationship where reference evapotranspiration was regressed with solar radiation and temperature data.
The regression was based on eight years of precision lysimeter observations for a grass reference crop in
Davis, CA. The method has been validated for sites around the world (Hargreaves and Allen, 2003). The
method is capable of capturing diurnal variation in potential evapotranspiration for simulation time steps
less than 24 hours. Combining the Hargreaves Evapotranspiration Method with the Hargreaves Shortwave
Radiation Method will yield the Hargreaves evapotranspiration form equivalent to Hargreaves and Allen
(2003) Eq. 8.
The Hargreaves Evapotranspiration Method includes a Component Editor with parameter data for each
individual subbasin in the Meteorologic Model. The Watershed Explorer provides access to the
Evapotranspiration Component Editor using a picture of a water pan (Figure 13). A Temperature method
must be selected in the meteorologic model.
444 A Meteorologic Model using the Hargreaves Evapotranspiration Method with a Component Editor for each individual subbasin
The Component Editor for each subbasin includes a Hargreaves Evapotranspiration Coefficient. A default
coefficient of 0.0135 per degree Celsius is provided; this is equivalent to 0.0075 per degree Fahrenheit. If the
Hargreaves Evapotranspiration Method is combined with the Hargreaves Shortwave Radiation Method, the

resulting default coefficient is 0.0023 per degree Celsius raised to the 3/2 power. This is equivalent to the
form presented by Hargreaves and Allen (2003) Eq. 8.
445 Entering the Hargreaves evapotranspiration coefficient for a subbasin
14.9.8 Monthly Average

The Monthly Average Method is designed to work with measured pan evaporation data. However, it can also
be used with data collected with the Eddy Correlation Technique or other modern methods. Regardless of
how they are collected, the data are typically presented as the average depth of evaporated water each
month. Maps or tabular reports can be found for each month and used with this method.
The Monthly Average Method includes a Component Editor with parameter data for each individual subbasin
446 A Meteorologic Model using the Monthly Average Evapotranspiration Method with a Component Editor for each individual subbasin
The Component Editor for each subbasin includes the Evapotranspiration Rate for each month of the year
(shown in the figure below). It is entered as the total amount of evapotranspiration for the month. Every time
step within the month will have the same evapotranspiration rate.

The Coefficient must also be entered for each month. The specified rate is multiplied by the coefficient to
determine the final potential rate for each month. The coefficient is usually used to correct actual
evaporation pan data to more closely reflect plant water use.
447 Entering rate and pan coefficient data for a subbasin in a Meteorologic Model using the Monthly Average Evapotranspiration
Method
14.9.9 Penman Monteith

The Penman Monteith Method implements the Penman Monteith equations for computing
evapotranspiration at less than a daily time interval as detailed by Allen, Pereira, Raes, and Smith (1998). The
equations are based on a combination of an energy balance with a mass transfer. The maximum possible
evapotranspiration is moderated by an aerodynamic resistance due to friction as air flows over the
vegetation. A bulk surface resistance is added in series with the aerodynamic resistance to account for
limitations to water vapor flow at the leaf surfaces and at the soil. The parameterization is entirely dependent
on the atmospheric conditions.
The Penman Monteith Method requires Shortwave Radiation, Longwave Radiation, Temperature,
Windspeed, and Dew Point be included in the Meteorologic Model. The algorithm of Allen, Pereira, Raes, and
Smith (1998) is followed most closely when the Specified Pyranograph Shortwave Method and the FAO56
Longwave Method are selected. When shortwave data is not available, Allen, Pereira, Raes, and Smith (1998)
recommend using the Hargreaves Shortwave Method.
The Watershed Explorer provides access to the Evapotranspiration Component Editor using a picture of a
water pan (shown in the following figure). An Air Temperature Gage and a Windspeed Gage must be
selected in the atmospheric variables for each subbasin.

The Component Editor for each subbasin includes a selection for the Reference Albedo.
448 Entering Penman Monteith properties for a subbasin
14.9.10 Priestley Taylor

The Priestley Taylor Method (Priestley and Taylor, 1972) uses a simplified energy balance approach where
the soil water supply is assumed to be unlimited. Simplified forms of latent and sensible energy are used.
The method is capable of capturing diurnal variation in potential evapotranspiration through the use of a net
solar radiation gage, so long as the simulation time step is less than 24 hours. Shortwave Radiation and
Temperature Methods must be selected in the Meteorologic Model. The Shortwave Radiation Method should
be configured to provide the net radiation; this is usually accomplished by computing the required value
externally and inputting it using a Radiation Time-Series Gage.
The Watershed Explorer provides access to the Evapotranspiration Component Editor using a picture of a
water pan.
The Component Editor for each subbasin includes a Dryness Coefficient. The coefficient is used to make
small corrections based on soil moisture state. A coefficient should be specified that represents typical soil
water conditions during the simulation. A default coefficient of 1.26 is provided. This coefficient has been
found to vary for regions around the world (Aschonitis, VG et al., 2017).

449 Entering Priestley Taylor properties for a subbasin
14.9.11 Specified Evapotranspiration

The Specified Evapotranspiration Method allows the user to specify the exact time-series to use for the
potential evapotranspiration at subbasins. This method is useful when atmospheric and vegetation data will
be processed externally to the program and essentially imported without alteration. This method is also
useful when a single evapotranspiration observation measurement can be used to represent what happens
over a subbasin.
The Specified Evapotranspiration Method uses a Component Editor with parameter data for all subbasins in
the Meteorologic Model. The Watershed Explorer provides access to the Gage Component Editor using a
picture of a water pan.
450 A Meteorologic Model using the Specified Evapotranspiration Method with one Component Editor for subbasins
The Component Editor for all subbasins in the Meteorologic Model includes the gage selection for each
subbasin. An Evapotranspiration Time-Series must be stored as an Evapotranspiration Gage before it can
be used in the Meteorologic Model. The data may actually be from daily pan measurements, hourly eddy
covariance measurements, or could be the result of complex calculations exterior to the program.

Regardless, the time-series must be stored as a gage. You may use the same gage for more than one
subbasin. For each subbasin in the table, select the gage to use for that subbasin. Only Evapotranspiration
Gages already defined in the Time-Series Data Manager will be shown in the selection list.
451 Selecting a time-series gage for each subbasin in a Meteorologic Model using the Specified Evapotranspiration Method
14.10 References: Meteorology Description

Allen, R.G., L.S. Pereira, D. Raes, and M. Smith. 1998. "Crop Evapotranspiration: Guidelines for Computing
Crop Water Requirements." FAO Irrigation and Drainage Paper No. 56, Rome, Italy.46
Aschonitis, VG et al. (2017): High-resolution global grids of revised Priestley-Taylor and Hargreaves-Samani
coefficients for assessing ASCE-standardized reference crop evapotranspiration and solar radiation. Earth
System Science Data, 9(2), 615-638.
Bristow, K.L. and G.S. Campbell. 1984. "On the Relationship Between Incoming Solar Radiation and Daily
Maximum and Minimum Temperature." Agricultural and Forest Meteorology, vol 31, pp 159-166.
Bras, R.L. 1990. Hydrology: An Introduction to Hydrologic Science. Addison-Wesley, Reading, MA.
Engineering Manual 1110-2-1411. March 1065. Standard Project Flood Determination. U.S. Army Corps of
Engineers, Davis, CA.
Follum, M. L., Downer, C.W., Niemann, J. D., Roylance, S. M., and Vuyovich, C. M.: A radiation-derived
temperature-index snow routine for the GSSHA hydrologic model, J. Hydrol., 529, 723–736, 2015.47
Hamon, W. R. 1963. Computation of direct runoff amounts from storm rainfall. Intl. Assoc. Scientific Hydrol.
Publ. 63: 52‐62
Hansen, E.M., L.C. Schreiner, and J.F. Miller. 1982. Application of Probable Maximum Precipitation Estimates
– United States East of the 105th Meridian. Hydrometeorological Report No. 52. National Weather Service,
Washington, D.C.
290988983_Crop_evapotranspiration_guidelines_for_computing_crop_requirements_FAO_Irrig_Drain_Report_modeling_and_application
47 https://www.researchgate.net/publication/281358823_A_Radiation-Derived_Temperature-
Index_Snow_Routine_for_the_GSSHA_Hydrologic_Model

Hargreaves, G. H., & Allen, R. G. 2003. History and evaluation of Hargreaves evapotranspiration equation.
Journal of Irrigation and Drainage Engineering, 129(1), 53–63.
Hargreaves, G.H. and Z.A. Samani 1982. Estimating potential evapotranspiration. J. Irrig. and Drain Engr.,
ASCE, 108(IR3):223-230.
Hargreaves, G.H. and Z.A. Samani, 1985. Reference crop evapotranspiration from temperature. Transaction
of ASAE 1(2):96-99.
Priestley, C.H.B. and R.J. Taylor. 1972. "On the Assessment of Surface Heat Flux and Evaporation Using
Large-Scale Parameters." Monthly Weather Review, vol 100, pp81-92.
Satterlund, D.R. 1979. "An Improved Equation for Estimating Long-Wave Radiation from the Atmosphere."
Water Resources Research, vol 15, no 6, pp 1649-1650.
Schreiner, L.C. and J.T. Riedel. 1978. Probable Maximum Precipitation Estimates, United States East of the
105th Meridian. Hydrometeorological Report No. 51. National Weather Service, Washington, D.C.
TVA, 1972. Heat and Mass Transfer Between a Water Surface and the Atmosphere. Tennessee Valley
Authority, Norris, TN.
World Meteorological Organization. 2008. "8. Measurement of Sunshine Duration." Guide to Meteorological
Instruments and Methods of Observations, Geneva, Switzerland.

15 Hydrologic Simulation
This section describes how watershed and meteorology information is combined to simulate the
Hydrologic response. The Simulation Run is the primary mode for performing simulations. In effect, the
Simulation Run applies the meteorology conditions to the watershed land surface to determine the runoff. In
addition to configuring and computing simulation runs, this section also describes how to access the
computed results.
15.1 Simulation Runs

Simulation Runs are the primary method of computing results. Each run is composed of one Meteorologic
Model, one Basin Model, and one Control Specifications. Results can be visualized as graphs, summary
tables, and time-series tables either through the Basin Map or from the Watershed Explorer. In addition to
selecting the meteorologic, basin, and control components, advanced features for controlling the run are also
included.
15.1.1 Creating a New Run

A new Simulation Run is created using a wizard that helps you navigate the steps to creating a new run.
There are two ways to access the wizard. The first way to access the wizard is to click on the Compute menu
and select the Create Compute | Simulation Run command; it is only enabled if at least one Basin Model, one
Meteorologic Model, and one Control Specifications exist. The wizard will open and begin the process of
creating a new Simulation Run. The second way to access the wizard is from the Simulation Run Manager.
Click on the Compute menu and select the Simulation Run Manager command. The Simulation Run
Manager will open and show any runs that already exist. Press the New button to access the wizard and
begin the process of creating a Simulation Run, as shown in the following figure.
Hydrologic Simulation – 523

452 Beginning the process of creating a new Simulation Run using the Simulation Run Manager
The first step of creating a Simulation Run is to provide the Name for the new run. A default name is
provided for the new Simulation Run; you can use the default or replace it with your own choice. After you
finish creating the run you can add a description to it. If you change your mind and do not want to create a
new Simulation Run, you can press the Cancel button at the bottom of the wizard or the X button in the upper
right corner of the wizard. The Cancel button can be pressed at any time you are using the wizard. Press
the Next button when you are satisfied with the name you have entered and are ready to proceed to the next
step.
The second step of creating a Simulation Run is to select a Basin Model. All of the Basin Models in the
project are shown and you must select one before proceeding to the next step. By default the first Basin
Model in the table is selected. The selected model is highlighted. You can use your mouse to select a
different Basin Model by clicking on it in the table of available choices. You can also use the arrow keys on
your keyboard to select a different model. Press the Next button when you are satisfied with the Basin Model
you have selected and are ready to proceed to the next step. Press the Back button if you wish to return to
the previous step and change the name for the new Simulation Run.
The third step of creating a Simulation Run is to select a Meteorologic Model. All of the Meteorologic
Models in the project are shown and you must select one before proceeding to the next step. By default, the
first Meteorologic Model in the table is selected. The selected model is highlighted. You can use your mouse
to select a different Meteorologic Model by clicking on it in the table of available choices. You can also use
the arrow keys on your keyboard to select a different model. Press the Next button when you are satisfied
with the Meteorologic Model you have selected and are ready to proceed to the next step. Press the
Back button if you wish to return to the previous step and select a different Basin Model.

453 Entering a name for a new Simulation Run. The remaining steps are to select a Basin Model, Meteorologic Model, and Control
Specifications.
The fourth and final step of creating a Simulation Run is to select a Control Specifications. All of the Control
Specifications in the project are shown and you must select one before proceeding to the next step. By
default the first Control Specifications in the table is selected. The selected specifications is highlighted. You
can use your mouse to select a different Control Specifications by clicking on it in the table of available
choices. You can also use the arrow keys on your keyboard to select a different specifications. Press
the Finish button when you are satisfied with the name you have entered and the components you have
selected, and are ready to create the Simulation Run. Press the Back button if you wish to return to the
previous step and select a different Meteorologic Model.
15.1.2 Copying a Run

There are two ways to copy a Simulation Run. Both methods for copying a run create an exact duplicate with
a different name. Once the copy has been made it is independent of the original and they do not interact.
The first way to create a copy is to use the Simulation Run Manager, which is accessed from
the Compute menu. Select the Simulation Run you wish to copy by clicking on it in the list of available
Simulation Runs. The selected run is highlighted after you select it. After you select a run you can press
the Copy button on the right side of the window. A new Copy Simulation Run window will open where you
can name and describe the copy that will be created. A default name is provided for the copy; you can use
the default or replace it with your own choice. A description can also be entered; if it is long you can use the
button to the right of the description field to open an editor. When you are satisfied with the name and
description, press the Copy button to finish the process of copying the selected Simulation Run. You cannot
press the Copy button if no name is specified. If you change your mind and do not want to copy the selected
Simulation Run, press the Cancel button or the X button in the upper right to return to the Simulation Run
Manager window.

454 Creating a copy of a Simulation Run
The second way to copy is from the Compute tab of the Watershed Explorer. Move the mouse over the
Simulation Run you wish to copy, then press the right mouse button. A context menu is displayed that
contains several choices including Copy. Click the Create Copy command. A new Copy Simulation
Run window will open where you can name and describe the copy that will be created. A default name is
selected Simulation Run. You cannot press the Copy button if no name is specified. If you change your mind
and do not want to copy the selected Simulation Run, press the Cancel button or the X button in the upper
right of the Copy Simulation Run window to return to the Watershed Explorer.
455 Copying a Simulation Run from the Watershed Explorer
15.1.3 Renaming a Run

There are two ways to rename a Simulation Run. Both methods for renaming a run change its name and then
all references to the old run name are automatically updated to the new name.
The first way to perform a rename is to use the Simulation Run Manager, which you can access from
the Compute menu. Select the Simulation Run you wish to rename by clicking on it in the list of available
the Rename button on the right side of the window. A new Rename Simulation Run window will open where
you can provide the new name. If you wish you can also change the description at the same time. If the new
description will be long, you can use the button to the right of the description field to open an editor. When

you are satisfied with the name and description, press the Rename button to finish the process of renaming
the selected Simulation Run. You cannot press the Rename button if no name is specified. If you change your
mind and do not want to rename the selected Simulation Run, press the Cancel button or the X button in the
upper right of the Rename Simulation Run window to return to the Simulation Run Manager window.
456 Renaming a Simulation Run
The second way to rename is from the Compute tab of the Watershed Explorer. Select the Simulation Run
over the selected run and click the left mouse button again. The highlighted name will change to editing
mode. You can then move the cursor with the arrow keys on the keyboard or by clicking with the mouse. You
can also use the mouse to select some or all of the name. Change the name by typing with the keyboard.
When you have finished changing the name, press the Enter key to finalize your choice. You can also finalize
your choice by clicking elsewhere on the Compute tab. If you change your mind while in editing mode and do
not want to rename the selected Simulation Run, press the Escape key.
457 Renaming a Simulation Run in the Watershed Explorer
15.1.4 Deleting a Run

There are two ways to delete a Simulation Run. Both methods for deleting a run remove it from the project,
automatically update all references to that run, and delete previously computed results. Once a run has been
deleted it cannot be retrieved or undeleted. Any references to the deleted run will switch to using no

Simulation Run, which is usually not a valid choice during a simulation. At a later time you will have to go to
those components and manually select a different Simulation Run.
The first way to perform a deletion is to use the Simulation Run Manager, which you can access from
the Compute menu. Select the Simulation Run you wish to delete by clicking on it in the list of available
to delete the selected run as shown in the following figure. Press the OK button to delete the run. If you
change your mind and do not want to delete the selected Simulation Run, press the Cancel button or
the X button in the upper right to return to the Simulation Run Manager window.
458 Preparing to delete a Simulation Run from the Simulation Run Manager
The second way to delete is from the Compute tab of the Watershed Explorer. Move the mouse over the
Simulation Run you wish to delete and press the right mouse button. A context menu is displayed that
contains several choices including delete. Click the Delete command. A window will open where you must
confirm that you wish to delete the selected run. Press the OK button to delete the run. If you change your
mind and do not want to delete the selected Simulation Run, press the Cancel button or the X button in the
upper right to return to the Watershed Explorer.

459 Deleting a Simulation Run in the Watershed Explorer
15.1.5 Importing a Run

A Simulation Run can be imported into the current project. The run to be imported is selected from a source
project. Once you select the run to be imported, all of the necessary simulation components will be imported
into the current project. This includes the Basin Model, Meteorologic Model, Control Specifications, and any
supporting data. The supporting data include background maps and grid cell file for the Basin Model, and
shared data such as time-series gages, paired data, and grid data used either in the basin or Meteorologic
Model. A Simulation Run will be created in the current project using the components that have been
imported.
To import a Simulation Run, begin by selecting the File | Import | Simulation Run menu command. Use the
file chooser to select the project file for the project that contains the Simulation Run you wish to import.

460 Selecting the source project to import a Simulation Run
You will then be provided a selection list of available Simulation Runs in that source project. Select the
Simulation Run that you wish to import and press the Import button.
461 Selecting the Simulation Run to be imported from the source project into the current project

Depending on the data used in the Basin Model and Meteorologic Model, you may be prompted to choose
how to treat time-series, paired, and gridded data. If you select to import the data, a copy of the data will be
made in the current project directory and appropriate gage, paired data, and grid components will be
automatically created. Any references in the Basin Model or Meteorologic Model to the time-series, paired,
and gridded data will be automatically updated to use the new shared component data in the current project.
If you choose not to import the data, the Basin Model and Meteorologic Model will be imported without any
of the data. In this second case, the current project should already include the necessary time-series, paired,
and gridded data necessary for the proper simulation of the Basin Model and Meteorologic Model.
Depending on the data used in the Basin Model and Meteorologic Model, you may be prompted to choose
how to treat external data. If you choose to localize external data, then copies of the files will be made in the
current project directory. Any references in the Basin Model or Meteorologic Model to external data will be
automatically updated to use the new copies in the current project. If you choose not to localize the external
data, the components in the current project will be updated to reference the files in their original locations.
15.1.6 Selecting Components

The principal task when creating a Simulation Run using the wizard is the selection of a Basin Model,
Meteorologic Model, and Control Specifications. However, you can change the components you wish to use
at any time using the Component Editor for a Simulation Run. Access the Component Editor from the
Compute tab of the Watershed Explorer. If necessary, click on the Simulation Runs folder to expand it and
view the available Simulation Runs. Click on the Simulation Run node you wish to edit and its Component
Editor will automatically be shown. The Component Editor contains three lists for selecting the Basin Model,
Meteorologic Model, and Control Specifications, respectively. The first selection list shows all of the Basin
Models currently available in the project. Likewise, the second list contains all of the Meteorologic Models
and the third list contains all of the Control Specifications. As the user, you are responsible for knowing
which components are intended to be used together to produce simulation results.
462 The Simulation Run Component Editor can be used to change a selected component after the run has been created
15.1.7 Simulation Results Output

All of the model components produce time-series results during the simulation process. Some components
also produce grid results. By default, all results are stored in the Output DSS File. The output DSS file can be

changed for each Simulation Run. To change the output file, specify a new file in the Component Editor.
Simulation output is configurable with options to write All Output, Minimal Output, and Selected Output. If
the Selected Output option is selected, the settings button becomes enabled as shown in the image below.
463 Enabling the Settings button with the Selected Option in the Component Editor
Click the Selected Output Settings button to open the selected results editor shown in the image below.
Results can be Selected, or De-Selected, for inclusion in the simulation output results file. Some results are
not available for de-selection. These must be written to the simulation output results file as a part of the
simulation compute. The Time Interval for each time-series can be modified. The default output interval is
equivalent to the simulation time interval. Additional output interval options are available that are multiples of
the simulation time interval. Filters are available at the top of the dialog, that filter the table for element or
time-series type. Edits can be saved in the selected results editor by clicking the Save button. You will be
prompted to save edits if you attempt to close the editor without saving first.
464 Selecting Simulation Output Results

Results that are not written to the simulation output results file will not be available on the HEC-
HMS Results tab.
If a change to the results configuration is made, HEC-HMS will clear simulation results from the
simulation output results file. The simulation must be re-computed to regenerate the results.
15.1.8 Precipitation and Flow Ratios

Using Precipitation and Flow Ratios is optional for a Simulation Run. If you do not use ratios, the simulation
results will be exactly determined by the meteorologic conditions specified in the Meteorology Model and the
watershed physical properties specified in the Basin Model. Optionally, you can apply a ratio to the
precipitation computed by the Meteorologic Model before the precipitation is applied to the Basin Model.
Alternately, you may instead apply a ratio to the outflow computed by Subbasin and Source Elements in the
Basin Model before routing the outflow downstream through the element network. You must choose
between applying no ratio, a precipitation ratio, or a flow ratio. The same ratio is applied to all elements.
The Ratio for the Simulation Run is accessed from the Compute tab of the Watershed Explorer. Click on the
Ratio node under the Simulation Run to display the Component Editor for the ratio. The Ratio and other
optional tabs are always shown whenever the Component Editor is shown. Select the Type of Ratio you wish
to apply from the available choices. If you select the Precipitation method, you can only choose to apply the
ratio to subbasins. If you select the Flow method, you can choose to apply the ratio to subbasins, sources, or
both element types. Finally, enter the Ratio Value. When working with a Precipitation Ratio, the precipitation
value for each time step computed by the Meteorologic Model is multiplied by the specified ratio before the
precipitation is applied to the subbasin elements. When working with a Flow Ratio, the outflow computed for
each time step by the Basin Model is multiplied by the specified ratio before the outflow is routed to the next
downstream element. You can only select whether to apply a ratio to Subbasins and Sources, and enter a
Ratio, if a ratio method is actually selected.
465 Entering a precipitation ratio for all of the subbasins in the Simulation Run

15.1.9 Start and Save States

The various mathematical equations used in the basin and Meteorologic Models all contain State Variables.
A State Variable is simply the current condition of the system at the end of a time interval. For example, the
State Variable in a reservoir is the amount of water in storage, usually measured as an elevation. In the soil
moisture accounting loss method, the State Variable is the amount of water currently held in each of the
layers. The State Variables change during a simulation in response to changing boundary conditions and the
dynamics of the mathematical equation governing the method.
The State Variables all must be specified at the beginning of a simulation, in which case they are called
Initial Conditions. Some methods allow you to specify the value you wish to use, such as the initial storage in
a reservoir. Some methods implicitly specify the initial condition, for example loss methods that allow you to
specify the amount of infiltration that must occur before surface runoff begins, often called the initial loss.
Many of the channel routing methods assume the initial condition that initial outflow equals the first inflow to
the reach, or the user can specify the initial outflow.
States have two main purposes: Breaking Long Simulations Into Smaller Time Periods, and Real-Time
Forecasting Operations. In the first case of long simulations, using states achieves exactly the same results
as one long simulation. Suppose that a long simulation covers all of 1995 and 1996. You could configure a
Simulation Run for 1995 and save states at the end of the simulation. You could then configure a simulation
for 1996 that uses as start states the states saved at the end of the 1995 run. The results obtained by
breaking the simulation into two runs and using states would be identical to the results obtained from a
single long run. This approach can be useful when performing continuous simulation for many years or
decades. In the second case of real-time forecasting operations, the typical approach is often to compute a
Simulation Run daily and forecast three to five days into the future. The simulation can be configured to run
for five days, saving the State Variables at the end of the first day. When the forecast is updated on the
subsequent day, it can start from the saved states of the previous day and continue forward. In this way,
continuously updated results can be obtained without requiring the simulation to start at the last known
watershed conditions which might be very old.
Saving out the Start State Variables during a Simulation Run, or starting a run from saved State Variables is
optional. If you do not use saved State Variables (start states), then the initial conditions will be specified
from the basin and Meteorologic Models. If you do use the start states, the initial conditions specified in the
basin and Meteorologic Models will be overridden by the values contained in the saved states used as the
start states. If you do not use save states, the simulation will run normally. If you do choose to save states,
the simulation will pause momentarily to save the State Variables and then continue normally. The save
states condition (file) that is created can be used for any simulation, the start date of the simulation does not
have to be similar to the date when the save states were created. The save states can be used across
different Simulation Runs, but you must make sure the basin and Meteorologic Models have similar
configurations (similar elements in the Basin Model and similar modeling methods in the basin and
Meteorologic Models) in order for the save states to be applicable.
Selecting optional start states for the Simulation Run is accessed from the Compute tab of the Watershed
Explorer. Open the Component Editor for the Simulation Run and then click on the States tab. The States and
other optional tabs are always shown whenever the Simulation Run Component Editor is shown. You can
choose to Save States and start the simulation with existing saved states. Start the simulation with saved
states by choosing the states you wish to use from the Start States selection list. Only states saved by
running a simulation configured to save states are shown. You will not be able to select start states unless
there are valid states available. A descriptive save states name can be helpful when selecting the states to
start a simulation. For example, a name of March 30 – 1200 was used when saving states when creating the
example in the following figure. The date and time the states were saved were used for the name to aid in
choosing these saved states in subsequent simulations.

466 Starting the simulation using a save states file
Creating optional save states for the Simulation Run is accessed from the Compute tab of the Watershed
Explorer. Open the Component Editor for the Simulation Run and then click on the States tab. The States and
other optional tabs are always shown whenever the Component Editor is shown. To create a save states file,
you must change the Save States option from No to Yes, as shown in the following figure. You must specify
a Name for the save states and optionally may enter a description. There are two ways to specify when the
states will be saved: at the End of the Simulation Run, or at a Specified Date and Time During the Simulation
Run. If you select to save states at the end of the run, the program will automatically determine the correct
date and time to save states. If you select to save states at a specific time, you must enter the date and time.
The specified date and time must be after the start and either at or before the end of the Simulation Run.
467 Configuring a Simulation Run to save states during the compute time window
15.2 Computing Results for a Run

Results for a Simulation Run are generated by computing it. Changes in all the components used in the run
are automatically tracked to determine if the results are current. When the results are no longer current, the

run must be recomputed in order to refresh the results. Computing results begins with selecting a Simulation
Run.
15.2.1 Selecting a Current Simulation Run

There are two ways to select the Current Simulation Run. Both methods set the run so that it can be
computed and results can be accessed from the Watershed Explorer and the Basin Map as soon as they are
available. The current Simulation Run is shown in the title of the Basin Map.
The first way to select the current Simulation Run is from the Toolbar. The Compute Selection Box shows all
of the Compute Components in the project; Simulation Runs appear first in the selection box. Each
Simulation Run in the selection box includes the prefix Run followed by the name of the Simulation Run. Click
on the toolbar selection box and choose a Simulation Run to become the current run.
The second way to select the current Simulation Run is from the Watershed Explorer, on the Compute tab.
Select the Simulation Run you wish to become the current run by clicking on it in the Watershed Explorer. The
Simulation Runs are listed alphabetically in the Simulation Runs folder.
15.2.2 Computing a Simulation Run

There are three ways to compute the currently selected Simulation Run. All methods automatically perform
parameter checking, and if no errors are generated, proceed to the actual computing of simulation results.
Additionally, the program is designed to be computationally efficient. Only components with data changes
since the last compute will be recomputed; the remainder of the components have not changed so previous
simulation results are still applicable. If you wish, you may force all components to be recomputed
regardless of data changes since the last compute using a choice in the Program Settings. (see page 90)
The first way to compute a Simulation Run is from the Compute menu. Click on the Compute menu and then
select the Compute Run command. The Name of the current Simulation Run is shown in brackets as part of
the menu command. If the command is not available, it is because there is no current Simulation Run; you
must first select a run. A window will automatically open that shows the progress of the compute. You will
need to manually close the window when the compute is done, whether it failed or was successful. If you
wish to force all components to be recomputed instead of just those with data changes, hold the CTRL key
while selecting the menu command.
The second way to compute a Simulation Run is from the Watershed Explorer, on the Compute tab. Select
the Simulation Run you wish to compute by clicking on it in the Watershed Explorer with the right mouse
button. A context menu is displayed that contains several choices including compute. Click
the Compute command. The progress window will automatically open. If you wish to force all components to
be recomputed instead of just those with data changes, hold the CTRL key while selecting the right mouse
menu command.
The third way to compute a Simulation Run is from the Toolbar. The Compute button is enabled whenever
there is a current run that can be computed. If the button is not available or shows a different type of
compute, you must first select a Simulation Run. Press the button to compute the current Simulation Run.
The progress window will automatically open. If you wish to force all components to be recomputed instead
of just those with data changes, hold the CTRL key while selecting the toolbar button.
15.2.3 Computing to a Computation Point

Any hydrologic element in a Basin Model can be designated as a Computation Point. Selecting a
computation point and unselecting a point is described in Computation Point (see page 232). It is also possible

to compute a Simulation Run to a computation point. This method of computing results only computes the
hydrologic element designated as a computation point. Any hydrologic elements upstream of the
computation point are also computed with it. This approach to computing results can save time by not
performing any calculations downstream of the computation point.
A Simulation Run can be computed to a point whenever at least one computation point has been designated
and a run is selected. Multiple ways in which users can compute to a point are available. For instance, users
can compute to a point from the Basin Model Map window by right-clicking on a computation point in the
map and selecting the Compute To Point command, as shown in the following figure.
468 Computing Simulation Run results to an element that has been designated a computation point
Additionally, users can select a computation point and all hydrologic elements upstream can be computed
from Global Parameter editors, as shown below.

469 Computing Simulation Run results to an element from a Global Parameter Editor
15.2.4 Using Calibration Aids at a Computation Point

Calibration Aids include the Custom Editor and the Custom results configured at a computation point.
Configuring a Custom Editor and results at a computation point is described in C48omputation Points49. Once
the customizable editor and result graphs have been configured, the aids can be used from the Basin Model
Map window whenever a Simulation Run is selected. Right-click on a computation point in the map and
select the Calibration Aids command, as shown in the following figure . The command can only be selected
when there is a current Simulation Run. Selecting the command will open the customizable editor and the
customized result graphs.
48 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/Computation+Points

470 Opening the calibration aids at a computation point
An example Custom Editor is shown in below.

471 Using the custom calibration editor at a computation point
Adjust a parameter value for an element using the Slider Bar for that parameter. Each slider bar is labeled
with the element name and parameter name, including units for the parameter. Change the value by clicking
with the mouse and dragging the slider. The precise selected value is shown on the right of each slider. You
may optionally change the value by typing in the editor field where the precise value is displayed.
The results for the computation point and all elements upstream of it are recomputed immediately after
changing a parameter value with a slider bar. In many watersheds, the computations require only a few
seconds to complete. However, some complex watersheds require more time to recompute the results. In
these cases you can use the checkbox in the upper right to control when results are recomputed. When the
checkbox is Engaged, results are recomputed after every slider change. When the checkbox is Disengaged,
results are only recomputed when the Apply button is pressed.
The Result Graphs will automatically update to reflect changes made with the Customizable Editor. Updated
results automatically replace the results shown in each graph as soon as a recompute is complete.
Sometimes you may wish to abandon all the parameter adjustments you have made and start over with the
calibration. Press the Reset button to return the parameter values in the customizable editor to the values in
place when the editor first opened.
15.2.5 Computing Multiple Runs

Multiple Simulation Runs can be computed in rapid succession. Each run included for simulation is internally
managed the same as if it were computed in isolation. The steps automatically performed for the user begin
with selecting the Simulation Run, checking parameters for the run, and finally computing the simulation.
This sequence is repeated in rapid succession for each Simulation Run in the selected set. Appropriate
feedback is provided through a progress bar.
The multiple Simulation Runs must exist before they can be selected for a multiple compute. Select
the Multiple Compute command on the Compute menu. A manager is used to select Simulation Runs, as
shown in the following figure. Make selections in the list and then press the Compute button to begin
computing the selected runs. A separate progress bar will be displayed for each Simulation Run as it is

computed. The progress bar may disappear automatically at the conclusion of a Simulation Run depending
on the configurations in the Program Settings. If errors are encountered while computing a run, the progress
bar will always remain visible after all selected runs have finished computing regardless of any other
settings.
472 Selecting multiple Simulation Runs for sequential compute
15.3 Viewing Results for the Current Run

A variety of Graphical and Tabular Results are available after a Simulation Run is computed. The program
tracks all of the data in the Simulation Run, the selected Basin Model, the selected Meteorologic Model, and
the selected Control Specifications. It also tracks any time-series data, paired data, or grid data used in the
basin and Meteorologic Models. Once a result is open for viewing, it will remain open until it is closed by the
user. It is possible that model components used by the simulation that produced are changed while the
result is open for viewing. In this case, the open result will immediately show an indication that data has
changed and the Simulation Run needs to be recomputed. After the run is recomputed the open results are
automatically updated with the new results and the indication is updated with the date and time of the most-
recent compute. You can also open results even if model components used within the simulation have been
changed. The results plot or table will indicate results are out of date and that the model needs to be
recomputed.
15.3.1 Global Summary Table

There are two ways to access the Global Summary Results for the current Simulation Run. Both methods
show the same results (shown in the following figure). Once the Global Summary Table is open, it will be
automatically updated whenever the Simulation Run is computed.

The first method for viewing Global Summary Results is to use the Results menu. Click the Results menu
and select the Global Summary Table command. The menu command will only be enabled if the results for
the current Simulation Run do not need to be recomputed. The Summary Table will automatically open after
selecting the menu command. The table includes one row for each element in the Basin Model and columns
for Element Name, Drainage Area, Peak Flow, Time of Peak Flow, and Total Outflow Volume. The table will
open to show only those elements selected when the result was requested. Selected elements are shown in
the Basin Map and also the Watershed Explorer. Optionally, you may switch to showing all elements using
the selection box above the table of results.
The second method for viewing Global Summary Results is to use the button on the Toolbar. Press the
toolbar button with a picture of a table plus a globe. The button will only be enabled if there is a current
Simulation Run with computed results.
473 Viewing the Global Summary Table for a Simulation Run
You can choose the units for volume results. Actual volume is shown in either Thousands of Cubic Meters
(THOU M3) or in Acre-Feet (AC-FT). You can use the buttons above the table of results to change volume
units.
You can view the elements listed either in Alphabetic or Hydrologic order. When hydrologic order is selected,
the elements are shown in the same order as in the Watershed Explorer. This order represents the order
determined from the flow network plus any manual adjustments. Optionally you can switch to viewing
elements in alphabetic order using the selection box above the table of results.
When sediment is enabled for a subbasin and is computed, two additional results columns will appear on the
Global Summary Table. Total sediment load (TONNE or TON) and total sediment volume (THOU M3 or
ACRE-FT) are listed for each hydrologic element.

474 Global Summary Table with Sediment Columns
15.3.2 Individual Elements

There are three ways to access results for Individual Elements in the current Simulation Run. All methods
show the same results. You must select one or more elements in the Basin Map before you can view results
for that element.
The first method for viewing Individual Element Results is to use the Results menu. You may need to first
open the Basin Model by clicking on it in the Watershed Explorer, on the Components tab. The current
Simulation Run is shown in brackets in the Basin Map Title Bar. Select one or more elements in the Basin
Map by clicking with the Arrow Tool. With an element selected in the Basin Map, click the Results menu and
select the Element Graph command, the Element Summary Table command, or the Element Time-Series
Table command. The appropriate result will automatically be shown in the Desktop area. The information
included in the graph varies by element type, but always includes Outflow. Optional items such as Observed
Flow, Computed Stage, and Observed Stage are also included.

475 Element graph for a subbasin

476 Element graph for a subbasin with observed flow data
477 Element graph for a reservoir with observed pool elevation data
The information included in the Summary Table also varies by element type but always includes the Peak
Flow, Time of Peak Flow, and Outflow Volume. If Observed Data are available, then information about the
observed data are presented, as well as Goodness-of-Fit Statistics which describe the degree of agreement

between the simulated time-series and the observed data. The Time-Series table includes the same
information as the graph but in numerical format. If you selected more than one element, then one result for
each element will open. The menu commands on the Results menu will only be enabled if the results for the
current Simulation Run do not need to be recomputed, and there is an element selection in the Basin Map.
478 Element summary table for a reach
479 Element summary table for a subbasin with observed data for flow, including goodness-of-fit statistics

480 Element summary table for a subbasin with observed data for snow water equivalent, including goodness-of-fit statistics

481 Element time-series table for a junction with observed flow
The second method for viewing Individual Element Results is to use the element icon in the Basin Map.
Again, you may need to open the Basin Model and select a current Simulation Run before attempting to view
results. Click on an element to highlight it. Keep the mouse over the element and press the right mouse
button. A context menu is displayed that contains several choices including View Results. The name of the
current Simulation Run is shown in brackets after the menu command. Move the mouse into the View
Results submenu and select any of the result commands: Graph, Summary Table, or Time-Series Table. The
appropriate result will open. If you selected more than one element, then one result for each element will
open. The View Results menu command will only be enabled if the results for the current Simulation Run do
not need to be recomputed.
The third method for viewing Individual Element Results is to use the Buttons on the Toolbar. First you must
open the Basin Model, select a current Simulation Run, and select one or more elements in the basin map by
clicking with the arrow tool. Once you have a selected element, click the Graph, Summary Table, or Time-
Series Table Buttons. The button for selecting a Graph shows a line plot. The button for the Summary Table
shows a plain table. The button for the Time-Series Table shows a table plus a clock. The appropriate result
will automatically open. If you selected more than one element, then one result for each element will be
added to the Desktop. The toolbar buttons for viewing element results will only be enabled if the results for

the current Simulation Run do not need to be recomputed, and there is an element selection in the Basin
Map.
15.4 Viewing Results for Other Runs

In addition to viewing results for the currently selected Simulation Run, it is also possible to view results for
other runs that are not the current selection. Those other runs are also tracked in the same way as the
current run to make sure data has not changed and results do not need to be recomputed. Results for other
Simulation Runs are accessed through the Watershed Explorer, on the Results tab.
To begin viewing results, go to the Results tab of the Watershed Explorer and click on the desired Simulation
Run icon. If necessary, click on the Simulation Runs folder to expand it and view the Simulation Runs in the
project. The Simulation Run icon will be disabled if results have not been computed. If any result is open at
the time data changes, the affected results will be automatically updated when the Simulation Run is
recomputed.
15.4.1 Global Summary Table

The Global Summary Table can be accessed by clicking on the Global Summary node in the Watershed
Explorer. The Global Summary Table will open. It is exactly the same table that can be viewed for the current
Simulation Run. The table includes one row for each element in the Basin Model and columns for Element
name, Drainage Area, Peak Flow, Time of Peak Flow, and Total Outflow Volume.

482 Accessing Simulation Run results from the Watershed Explorer

Each element in the Basin Model is shown in the Watershed Explorer under the Simulation Run node. These
elements are listed in hydrologic order below the Global summary table. The results for each element are
accessed by clicking on its node. The first item listed for each element is the Graph; click on the Graph node
to view the result (shown in the previous figure). It is exactly the same graph that can be viewed for the
current Simulation Run. The information included in the graph varies by element type but always includes
Outflow. Optional items such as Observed Flow, Computed Stage, and Observed Stage are also included.
Similarly, the Summary Table and Time-Series Table can also be accessed by clicking on the Summary
Table or Time-Series Table node, respectively.
15.4.3 Element Time-Series Preview Graph

All of the time-series data computed by an individual element are available for viewing. The time-series data
are listed under each element node in the Watershed Explorer. The first node under each element is the
Graph, followed by the Summary Table and Time-Series Table. The remaining nodes for each element
represent the different time-series data available at that element. Click on a Time-Series node to preview the
data in the Component Editor. You may select multiple time-series data by holding the shift or control key
while using the mouse to click on additional nodes (shown in the following figure). The selected time-series

may come from different elements in the same Simulation Run, the same element in different runs, or
different elements in different runs. The selected time-series data will automatically be partitioned into
groups by data type.
15.4.4 Time-Series Tables and Graphs

Preview graphs of selected time-series data can be opened as Graphs or Time-Series Tables within
the Desktop area. Begin by selecting the time-series you wish to include in the graph or table. Once you have
selected the desired time-series, you can press the Graph or Time-Series Table buttons on the toolbar. The
chosen time-series will be graphed or tabulated.
483 Selecting computed outflow from the same element in two different Simulation Runs

484 Custom graph created by selecting multiple time-series results for a preview and then pressing the graph button on the toolbar
After you have opened a time-series table or graph, you may add Additional Time-Series Results. Position
the mouse over the time-series result in the Watershed Explorer that you wish to add to the graph or table.
Press and hold the left mouse button and then drag the mouse over the top of the graph or table where you
want the result to be added. The mouse cursor will change to indicate which tables and graphs can accept
the additional time-series. Release the mouse button while it is over the desired table or graph and it will be
automatically updated to show the additional time-series results.
15.4.5 Changing Graph Properties

All of the graphs that can be accessed open with default properties for line color, line style, data symbols,
etc. These default properties have been selected to be appropriate for most situations. However, it is
possible to customize the properties in a graph. To change the properties, first click on the graph to select it.
Next go to the Results menu and select the Graph Properties command. An editor will open that can be used
to change the properties of the selected graph. The properties for each time-series curve can be changed. It
is also possible to change the properties for the Axis, Title, Gridlines, Patterns, and Legend.

485 Editing the drawing properties for an element graph
15.5 Viewing Spatial Results

The Spatial Results Toolbar provides options to visualize results for Basin Models that have been created
using GIS Features (Georeferenced Elements). Spatial results must be turned on within the Simulation Run's
Component Editor. Spatial results should be turned on after preliminary calibration has been completed. Use
of spatial results can assist in the calibration process and provide additional information about the
simulation. If you make edits to the basin geometry, edit model parameters, or change the simulation
configuration, the spatial results will be automatically re-computed during the simulation.

The following figure shows the Spatial Results Toolbar along with Snow Water Equivalent (SWE) results
displayed on top of the Basin Model. The Spatial Results toolbar includes options for Selecting Output
Results, an Animation Toolbar, Buttons for Controlling the Animation, Max and Min buttons, a display
settings button that opens an editor with options for animation, symbology, and display settings, and buttons
to export an animation and/or snapshot file.
486 Displaying Spatial Results
When a valid spatial result is selected, a tool tip containing the value and units for the specific time step and
grid cell over which the mouse is hovered will be displayed, as shown in the following figure.
487 A tool tip containing the value and units for a specific time step while hovered over a grid cell
When a valid spatial result is selected, the Plot Spatial Results option is available from its context menu for
tabulating the results for the specific grid cell which was clicked, as shown in the following figure.

15.5.1 Requirements for Spatial Results
488 Graph results from a specific grid cell
A Georeferenced Basin Model (Subbasin Elements must be georeferenced) is required to utilize spatial
results. A Georeferenced Basin Model can be created using the GIS Tools to delineate elements from a
Terrain Model. Another option to georeference a Basin Model is to use the Georeference Existing Elements
or Import Georeferenced Elements tools from the GIS menu. These two tools use geographic information in
shapefiles to georeference Subbasin Elements.
Spatial results can be visualized at the subbasin level, spatially averaged for the subbasin, or across the
model domain using the Discretization Method chosen for the subbasin elements (Structured Discretization
or Unstructured Discretization). Spatial results will be displayed at the Grid or Mesh Level when the
Transform Method is either ModClark or 2D Diffusion Wave and the Structured, Unstructured, and File-
Specified *.sqlite, *.HDF5, and *.HDF Discretization Methods are selected. Gridded spatial results cannot be
visualized for Subbasin Elements using the ModClark file option (under the File-Specified Discretization
Method). Instead, results will be displayed as a subbasin average value when the *.mod File option is used
for the File-Specified Discretization Method. Spatial results will be displayed at the Subbasin Level when
Transform Methods other than the ModClark or 2D Diffusion Wave Transform are used.
15.5.2 Activate Spatial Results

Spatial results can be displayed for both Simulation Runs and Forecast Alternatives. Spatial results must be
activated in the Simulation Run's Component Editor, as shown below. You can also set the Time Interval for
spatial results. The simulation time-step is used as the default interval. Spatial results are saved to an HDF5
file within the project's Results directory; results are saved to an *.H5 file. Turning on spatial results will add
additional time to the simulation due to additional output being generated and saved to disk. The additional
time can be up to 1/3 of the simulation time without spatial results activated.
The very first time an Output Result is selected in the Spatial Results Toolbar, the program will process the
simulation HDF5 and build animation tiles for display. A message will pop up the very first time the output
HDF file is processed indicating animation tiles are being created. The time it takes to build the animation
tiles can be large for larger model domains; however, the processing is only required the very first time

spatial results are displayed. The display time for subsequent simulations will be much quicker because
animation information already exists.
15.5.3 Spatial Results Toolbar

As shown in the figure below, the Spatial Results Toolbar is configured to 1) Select an Output Result to
Visualize, 2) Control the Animation, and 3) Edit the Display and Animation Properties. Results that can be
animated include Meteorologic Results, Snow Modeling Results, and Precipitation Excess and Loss.
Hydraulic Depth, Water Surface Elevation, and Cell Velocity can be displayed for subbasins that use the 2D
Diffusion Wave Transform Method. Statistical metrics comparing observed and computed data, if specified,
will be available as well. A full list of spatial variables is provided below (some results are only available when
running the program in debug mode):
Variable Process Method
Incremental Precipitation Precipitation All Precipitation Methods
Cumulative Precipitation Precipitation All Precipitation Methods
Air Temperature Snowmelt All Snowmelt Methods
SWE (Snow Water Equivalent) Snowmelt All Snowmelt Methods
Albedo Snowmelt Energy Balance
ATI (Antecedent Temperature Snowmelt Temperature Index

Index)

Cold Content Snowmelt Temperature Index
Cold Content ATI Snowmelt Temperature Index
Heat Deficit Snowmelt RTI/Hybrid
Liquid Water Content Snowmelt All Snowmelt Methods
Melt Rate ATI Snowmelt Temperature Index
Pack Energy Snowmelt Energy Balance
Pack Temperature Snowmelt Energy Balance
Snow Depth Snowmelt RTI/Hybrid and Energy Balance
Surface Temperature Snowmelt Energy Balance
Incremental Loss Loss All Loss Methods
Cumulative Loss Loss All Loss Methods
Incremental Excess Loss All Loss Methods
Cumulative Excess Loss All Loss Methods
Water Surface Elevation Transform 2D Diffusion Wave
Hydraulic Depth Transform 2D Diffusion Wave
Cell Velocity Transform 2D Diffusion Wave
Bed Change (Total) Sediment Transport 2D Sediment
Bed Change - Clay Sediment Transport 2D Sediment

Bed Change - Silt Sediment Transport 2D Sediment
Bed Change - Sand Sediment Transport 2D Sediment
Bed Change - Gravel Sediment Transport 2D Sediment
Sediment Concentration (Total) Sediment Transport 2D Sediment
Sediment Concentration - Clay Sediment Transport 2D Sediment
Sediment Concentration - Silt Sediment Transport 2D Sediment
Sediment Concentration - Sand Sediment Transport 2D Sediment
Sediment Concentration - Gravel Sediment Transport 2D Sediment
Snow - NSE Snowmelt All Snowmelt Methods w/ Observed

Data
Snow - PBIAS Snowmelt All Snowmelt Methods w/ Observed

Data
Snow - R2 Snowmelt All Snowmelt Methods w/ Observed

Data
Snow - RSR Snowmelt All Snowmelt Methods w/ Observed

Data
Flow - NSE All All Methods w/ Observed Data
Flow - PBIAS All All Methods w/ Observed Data
Flow - R2 All All Methods w/ Observed Data
Flow - RSR All All Methods w/ Observed Data
29 List of Spatial Variables

489 Controls for Spatial Results
The animation can be controlled through the Animation Control Slider Bar and Buttons. The slider bar can be
manually dragged right or left to advance or reverse results. The animation control buttons include a button
to go to the beginning of the animation, move forward one time interval, pause the animation, reverse the
animation one time interval, and go to the end of the animation.
15.5.4 Legend, Scale Bar, and North Arrow

A Legend, Scale Bar, and North Arrow can now be displayed within the Desktop when a valid spatial result is
selected. These options can be enabled/disabled through the View menu, as shown in the following image.
490 Draw Legend, Draw North Arrow, and Draw Scale Bar View Menu Options
Legend, Scale Bar, and/or North Arrow Properties can be edited by right clicking on the item of interest
within the map and selecting Edit Properties. Placement, Fill, and Border options can be adjusted, as shown
in the following image. Additionally, the North Arrow can be displayed relative to True North (default) or
Magnetic North when editing the North Arrow Properties.

491 Edit Legend Image Properties
15.5.5 Max/Min Buttons

The Max and Min buttons allow for quick visualization of the minimum or maximum of any spatial result
regardless of the time in which they were achieved. When selected, these buttons will be shown with a white
background, as shown in the following image.
492 Displaying Maximum Values
15.5.6 Export Animation and Snapshot Buttons

The Export Animation and Export Snapshot button can be used to export the current spatial result to be
viewed within another application.

15.5.6.1 Export Snapshot

The Export Snapshot button enables the user to export the currently selected spatial result as a single or
sequence of rasters to a DSS, GeoTIFF, or ASCII file. Upon clicking this button, a dialog will appear allowing
the user to export a single grid or a series of grids, a start date and end date (if exporting a series of grids), a
destination file type, and a destination file name, as shown in the following figure.
A ".dss", ".tiff", or ".asc" extension should be used when exporting to DSS, GeoTIFF, or ASCII,
respectively.
493 Export Snapshot Dialog
The resultant output files will be georeferenced and can be read by other applications (e.g., HEC-RAS, QGIS,
ArcGIS, etc).
This feature is commonly used to export a sequence of excess precipitation grids (i.e., the
amount of water that isn't infiltrated) for use in 2D HEC-RAS simulations.
15.5.6.2 Export Animation

The Export Animation button enables the user to export an animation of the currently selected spatial result.
Only the MP4 file format is currently supported when exporting animations.

To export an animation, a spatial result must be currently playing (i.e., click the green arrow
button).
The animation export process can be started by clicking the Export Animation button (this will be the start
time) and finished by clicking the button again (this will be the end time). Upon clicking the Export Animation
button for a second time, a dialog will appear allowing the user to specify the location and name of the
output, as shown below. The resultant animation will also include any currently displayed maps (e.g.
subbasin outlines, reservoir icons, terrain, etc) and can be opened within common media players (e.g.
Windows Media Player, Microsoft PowerPoint).
494 Export Animation Dialog
15.5.7 Display Settings

The Display Settings editor can be opened by clicking the Gear icon located on the right side of the Spatial
Properties Toolbar. The figure below shows the Playback tab in the Display Settings editor. You can change
the Frame Rate to control the speed of the animation. There is check box to control whether the animation is
looped or not.

495 Setting whether the animation is looped or not in the Display Settings
The figure below shows the Symbology tab. When the Stretch Symbology option is selected, you can edit the
Max and Min values and the Color Scheme.
496 Editing the Max and Min values and Color Scheme
The figure below shows how the Symbology editor is configured when the Classify Symbology option is
selected. There are three methods to choose from to subdivide classes, Natural Breaks (Jenks), Equal
Interval, and Manual. You can overwrite the Max and Min values when the Equal Interval option is selected.
You can edit the Upper values in the Classes table when the Manual method is selected. The Number of
Classes can only be edited when the Natural Breaks (Jenks) or Equal Interval methods are chosen. You can
edit the Color Scheme by choosing a palette from the drop down list, you can also edit individual colors by
clicking on them in the Classes table. Finally, Labels can be manually edited if needed.

497 Using the Classify Symbology option
The figure below shows the Display tab. You can control the Transparency setting, and whether to apply
hillshading or to invert the color ramp.
498 Setting transparency and whether to apply hillshading or inverting the color ramp
The Apply button must be pressed after edits are made to the display settings, then press the Close button
to close the editor.

15.6 Viewing Calibration Results

The Calibration Results can be visualized by choosing a Statistical Metric Variable through the Spatial
Results Toolbar. When the variable has been chosen, the subbasins on the map would be color-coded based
on the range that they fall into.
To view Calibration Results, navigate to the combo box (1) in the figure below, and choose a Statistical
Metric Variable.
499 Choosing a Statistic Metric Variable to view Calibration Results
To make edits to the Ranges and Colors, navigate to the Gear icon at (2), and a Display Settings dialog will
popup. One example of the dialog are shown below.
500 Display Settings dialog accessed for the selected Statistic Metric Variable

The color scales reflect the Moriasi et. al. 2007 and 2015 performance evaluation criteria. In particular, the
following criteria are used:
• Table 9 metrics in Moriasi et. al. 201550 paper for R2, NSE, and PBIAS
• Table 4 metrics in Moriasi et. al. 200751 paper for RSR
Below is a table showing the combined performance criteria from the two papers.
Performance Color Code R2 (2015) NSE (2015) RSR (2007) PBIAS (2015)
Rating
Very Good Dark Green 0.85 < R2 ≤ 0.80 < NSE ≤ 0.00 < RSR ≤ PBIAS < ±5
1.00 1.00 0.50
Good Light Green 0.75 < R2 ≤ 0.70 < NSE ≤ 0.50 < RSR ≤ ±5 < PBIAS ≤
0.85 0.80 0.60 ±10
Satisfactory Orange 0.60 < R2 0.50 < NSE ≤ 0.60 < RSR ≤ ±10 < PBIAS
≤ 0.75 0.70 0.70 ≤ ±15
Unsatisfactory Red R2 ≤ 0.60 NSE ≤ 0.50 RSR > 0.70 PBIAS ≥ ±15
30 Combined Performance Criteria
50 https://web.ics.purdue.edu/~mgitau/pdf/Moriasi%20et%20al%202015.pdf
51 https://swat.tamu.edu/media/1312/moriasimodeleval.pdf

16 Model Optimization
This section describes how observed data can be used to Optimize Model Performance by automatically
estimating parameters. HEC-HMS has two different approaches to model optimization: Deterministic, and
Stochastic. Deterministic optimization begins with initial parameter estimates and adjusts them so that the
simulated results match observed data as closely as possible. Stochastic optimization produces a collection
of equally-probable parameter sets which represent a sample from the joint distribution of the parameter
population.
HEC-HMS Optimization Tools offer two deterministic search algorithms that move from the initial parameter
estimates to the final best parameter estimates. A variety of objective functions are provided to measure the
goodness of fit between the simulated and observed data in different ways. One stochastic procedure for
generating samples from the joint distribution of the parameters is included. While parameter estimation
using optimization does not produce perfect results, it can be a valuable aid when calibrating models.
Deterministic and Stochastic Optimization are philosophically different approaches to the optimization
problem. Deterministic Optimization seeks to minimize the difference between the model outputs and
observed data by changing model parameters to find a single, optimum set. Parameters determined in this
way may be used as parameter values in an ordinary Simulation Run. With the same parameters, a
Deterministic Optimization will arrive at the same optimum parameters with each trial. Stochastic
Optimization infers what likely model parameter values are in light of the observed data, and can only do so
by creating a number of parameter sets. This approach treats the parameters with uncertainty and does not
return a single set of optimized parameters. In order to use parameter sets generated by a Stochastic
Optimization, the user must use an Uncertainty Analysis and populate tables of sampled parameters.
Stochastic optimizations will result in different parameter sets with each trial.
16.1 Optimization Trials

Parameter estimation is the process of adapting a general model to a specific watershed. Some parameters
can be estimated directly from field measurements. For example, the area that must be entered for a
Subbasin Element can be measured directly in the field using standard surveying procedures or from maps
developed through surveying. Other parameters can be estimated indirectly from field measurements. In this
case, the field measurement does not result in a value that can be input directly to the program. However, the
field measurement can provide a strong recommendation for a parameter in the program based on previous
experience. For example, measurements of soil texture are correlated with parameters such as hydraulic
conductivity. Finally, there are parameters that can only be estimated by comparing computed results to
observations such as measured streamflow or snow water equivalent. Even for parameters of the first two
types, there is often enough uncertainty in the true parameter value to require some adjustment of the
estimates in order for the model to closely follow the observed data.
The quantitative measure of the goodness-of-fit between the computed result from the model and the
observed data is called the Objective Function. Different Objective Functions measure the degree of variation
between computed and observed hydrographs in different ways. Some functions report a value that
decreases as the agreement between simulated and observed increases, and some do the opposite,
increasing as goodness-of-fit increases. The key to automated parameter estimation is a search method for
adjusting parameters to direct the Objective Function value towards better goodness-of-fit, and find optimal
parameter values. An optimal value for the Objective Function is obtained when the parameter values best
able to reproduce the observed hydrograph are found. Constraints are set to ensure that unreasonable
parameter values are not used.
Model Optimization – 567

Optimization Trials are one of the components that can compute results. Each trial is composed of a Basin
Model, Meteorologic Model, and Time Control Information. The trial also includes selections for the
Objective Function, Search Method, and Parameters to be adjusted in order to find an optimal model. A
variety of result graphs and tables are available from the Watershed Explorer for evaluating the quality of the
results.
The iterative parameter estimation procedure used by the program is often called Optimization. Initial values
for all parameters are required at the start of the Optimization Trial Time Window. A hydrograph is computed
at a target element by computing all of the upstream elements. The target must have an observed
hydrograph for the time period over which the Objective Function will be evaluated. Only parameters for
upstream elements can be estimated. The value of the Objective Function is computed at the target element
using the computed and observed hydrographs. Parameter values are adjusted by the search method and
the hydrograph and Objective Function for the target element are recomputed. This process is repeated until
the value of the Objective Function is sufficiently small, or the maximum number of iterations is reached.
Results can be viewed after the Optimization Trial is complete.
16.1.1 Creating a New Optimization Trial

A new Optimization Trial is created using a wizard that helps you navigate the steps to creating a new trial.
There are two ways to access the wizard. The first way to access the wizard is to click on the Compute menu
and select the Create Compute | Optimization Trial command; it is only enabled if at least one Basin Model
and Meteorologic Model exist. The wizard will open and begin the process of creating a new Optimization
Trial. The second way to access the wizard is from the Optimization Trial Manager. Click on
the Compute menu and select the Optimization Trial Manager command. The Optimization Trial
Manager will open and show any trials that already exist. Press the New button to access the wizard and
begin the process of creating an Optimization Trial, as shown below.
The first step of creating an Optimization Trial is to provide the name for the new trial (shown below). A
default name is provided for the new Optimization Trial; you can use the default or replace it with your own
choice. After you finish creating the trial you can add a description to it. If you change your mind and do not
want to create a new Optimization Trial, you can press the Cancel button at the bottom of the wizard or
the X button in the upper right corner of the wizard. The Cancel button can be pressed at any time you are
using the wizard. Press the Next button when you are satisfied with the name you have entered and are ready
to proceed to the next step.

501 Entering a name for a new optimization trial
The second step of creating an Optimization Trial is to select a Basin Model. All of the Basin Models that are
currently part of the project are displayed in alphabetical order. By default the first Basin Model in the table is
selected. The selected Basin Model is highlighted. You can use your mouse to select a different Basin Model
by clicking on it in the table of available choices. You can also use the arrow keys on your keyboard to select
a different Basin Model. Press the Next button when you are satisfied with the Basin Model you have
selected and are ready to proceed to the next step. Press the Back button if you wish to return to the
previous step and change the name for the new Optimization Trial.
The third step of creating an Optimization Trial is to select a Meteorologic Model. All of the Meteorologic
Models that are currently part of the project are displayed in alphabetical order. By default the first
Meteorologic Model in the table is selected. The selected Meteorologic Model is highlighted. You can use
your mouse to select a different Meteorologic Model by clicking on it in the table of available choices. You
can also use the arrow keys on your keyboard to select a different Meteorologic Model. You are responsible
for selecting a Basin Model in step 2 and a Meteorologic Model in this step that will successfully combine to
compute results. Press the Back button if you wish to return to the previous step and select a different Basin
Model. Press the Finish button when you are satisfied with the name you have entered, the Basin Model and
element you selected, the Meteorologic Model you selected, and are ready to create the Optimization Trial.
16.1.2 Copying an Optimization Trial

There are two ways to copy an Optimization Trial. Both methods for copying a trial create an exact duplicate
The first way to create a copy is to use the Optimization Trial Manager, which is accessed from
the Compute menu. Select the Optimization Trial you wish to copy by clicking on it in the list of current
Optimization Trials. The selected trial is highlighted after you select it. After you select a trial you can press
the Copy button on the right side of the window. You can enter a new name and description of the copy in the
Copy Optimization Trial window. A default name is provided for the copy; you can use the default or replace
it with your own choice. A description can also be entered; if it is long you can use the button to the right of
the description field to open an editor. When you are satisfied with the name and description, press
the Copy button to finish the process of copying the selected Optimization Trial. You cannot press
the Copy button if no name is specified. If you change your mind and do not want to copy the selected
Optimization Trial, press the Cancel button or the X button in the upper right to return to the Optimization
Trial Manager window.

502 Creating a copy of an optimization trial
Optimization Trial you wish to copy and press the right mouse button (shown below). A context menu is
displayed that contains several choices including copy. Click the Create Copy command. The Copy
Optimization Trial window will open where you can name and describe the copy that will be created. A
default name is provided for the copy; you can use the default or replace it with your own choice. A
of copying the selected Optimization Trial. You cannot press the Copy button if no name is specified. If you
change your mind and do not want to copy the selected Optimization Trial, press the Cancel button or
the X button in the upper right of the Copy Optimization Trial window to return to the Watershed Explorer.
503 Copying an optimization trial from the Watershed Explorer
16.1.3 Renaming an Optimization Trial

There are two ways to rename an Optimization Trial. Both methods for renaming a trial change its name and
perform other necessary operations.
The first way to perform a rename is to use the Optimization Trial Manager, which you can access from
the Compute menu. Select the Optimization Trial you wish to rename by clicking on it in the list of current
the Rename button on the right side of the window. The Rename Optimization Trial window (shown below)
will open where you can provide the new name. If you wish you can also change the description at the same

time. If the new description will be long, you can use the button to the right of the description field to open an
editor. When you are satisfied with the name and description, press the Rename button to finish the process
of renaming the selected Optimization Trial. You cannot press the Rename button if no name is specified. If
you change your mind and do not want to rename the selected simulation trial, press the Cancel button or
the X button in the upper right of the Rename Optimization Trial window to return to the Optimization Trial
Manager window.
504 Renaming an optimization trial
The second way to rename is from the Compute tab of the Watershed Explorer. Select the Optimization Trial
over the selected trial and click the left mouse button again. The highlighted name will change to editing
mode (shown below). You can then move the cursor with the arrow keys on the keyboard or by clicking with
can also finalize your choice by clicking elsewhere on the Compute tab. If you change your mind while in
editing mode and do not want to rename the selected Optimization Trial, press the Escape key.
505 Renaming an optimization trial in the Watershed Explorer

16.1.4 Deleting an Optimization Trial

There are two ways to delete an Optimization Trial. Both methods for deleting a trial remove it from the
project and automatically delete previously computed results. Once a trial has been deleted it cannot be
retrieved or undeleted.
The first way to perform a deletion is to use the Optimization Trial Manager, which you can access from
the Compute menu. Select the Optimization Trial you wish to delete by clicking on it in the list of current
to delete the selected trial as shown below. Press the OK button to delete the trial. If you change your mind
and do not want to delete the selected Optimization Trial, press the Cancel button or the X button in the
upper right to return to the Optimization Trial Manager window.
506 Preparing to delete an optimization trial from the Optimization Trial Manager
The second way to delete is from the Compute tab of the Watershed Explorer. Select the Optimization Trial
you wish to delete by clicking on it in the Watershed Explorer; it will become highlighted (shown below). Keep
the mouse over the selected trial and click the right mouse button. A context menu is displayed that contains
several choices including delete. Click the Delete command. A window will open where you must confirm
that you wish to delete the selected trial. Press the OK button to delete the trial. If you change your mind and
do not want to delete the selected Optimization Trial, press the Cancel button or the X button in the upper
right to return to the Watershed Explorer.

507 Deleting an optimization trial in the Watershed Explorer

One of the principal tasks when creating an Optimization Trial using the wizard is the selection of the
components that will be used to compute optimization results. The components include the Basin Model
and the Hydrologic Element in the Basin Model where the Objective Function will be computed. The
components also include the Meteorologic Model. These components are selected when creating a new
Optimization Trial with the wizard. However, you can change the Basin Model and Meteorologic Model you
wish to use at any time using the Component Editor for the Optimization Trial. Access the Component Editor
from the Compute tab of the Watershed Explorer (shown below). If necessary, click on the Optimization
Trials folder to expand it and view the available Optimization Trials. The Component Editor contains a Basin
Model selection list that includes all of the Basin Models in the project where the Basin Model has at least
one element with observed data. The Component Editor also contains a Meteorologic Model selection list
that includes all of the Meteorologic Models in the project. The Search and Objective tabs of the
Optimization Trial Component Editor are discuss in the following sections.

508 The Optimization Trial tab of the Component Editor
16.1.6 Entering a Time Window

You must enter a Start Date and Time and an End Date and Time for the Optimization Trial. The time control
information is not specified in the wizard used to create the Optimization Trial. The time control information
must be entered after the trial is created using the Component Editor for the Optimization Trial (shown
above). Enter the start date using the indicated format for numeric day, abbreviated month, and four-digit
year. Enter the end date using the same format. The start time and end time are entered using 24-hour time
format. Choose a time interval from the available options which range from 1 minute up to 1 day. The start
time and end time must each be an integer number of time intervals after the beginning of the day.
16.1.7 Search Methods: Deterministic

Two Deterministic Search Methods are available for optimizing the Objective Function and returning optimal
parameter values: Univariate Method and Simplex Method. The Univariate Method evaluates and adjusts
one parameter during the optimization simulation, the user can choose only one parameter for the program
to adjust when the Univariate Method is selected. The Simplex Method uses a downhill simplex to evaluate
all parameters simultaneously and determine which parameter to adjust. The default method is the Simplex
Method. When the Simplex Method is specified, at least two parameters must be selected.
Selecting the Search Method for the Optimization Trial is accessed from the Compute tab of the Watershed
Explorer in the Optimization Trial Component Editor. Click on the Optimization Trial node to display
the Component Editor for the Optimization Trial. If necessary, click on the Optimization Trials folder to
expand it and view the available Optimization Trials in the project.
Two methods are provided for controlling the search process, the Univariate or Simplex methods. Both
search methods function by iteratively adjusting parameter values to decrease the Objective Function value
(increase if the goal is maximization); each parameter adjustment is termed an Iteration. The Tolerance
determines the change in the Objective Function value between two successive iterations that will terminate
the search.

Two Tolerance Criterion types, Absolute and Relative, are available for use with the Simplex Method.
Convergence is assessed based on specified tolerance and tolerance type. When an Absolute criterion is
selected, convergence is assessed based on the absolute tolerance, or the absolute difference
between the nodes of the Simplex.
This means that the magnitude of the Objective Function affects the determination of convergence. For
example, a larger tolerance is needed for the Sum of Squared Errors (SSE) Objective Function than for the
Root Mean Square Error (RMSE) Objective Function for the trial to converge in a similar number of iterations
because values of the SSE function are generally orders of magnitude larger than for RMSE. When the
Relative criterion is selected, convergence is assessed based on the relative tolerance, or the relative
difference between the nodes of the Simplex. The Relative criterion is less sensitive to the magnitude of the
Objective Function values. In general, the Relative criterion is preferred, but the default option is Absolute for
backwards compatibility.
The Maximum Number of Iterations also can be used to limit the search. The search will stop when the
maximum number of iterations is reached regardless of changes in the Objective Function value or the
quality of the estimated parameters. The tolerance and maximum iterations are both entered on the Search
tab within the Optimization Trial Component Editor. Defaults are provided for both criteria. The initial default
values depend on the selected search method.
509 The Search tab of the Component Editor
16.1.8 Search Methods: Stochastic

Two Stochastic Search Methods are available: Differential Evolution and Markov Chain Monte Carlo.
However, the Markov Chain Monte Carlo option has been turned off in the HEC-HMS user interface.
The Differential Evolution (DE) Search Method behaves similarly to the Simplex Search Method; however,
Iterations of the search vary the parameters at random instead of in a deterministic way. This means that
two DE searches set up in an identical way may proceed in different ways, and reach convergence in a
different amount of time. However, any DE search will settle on a single optimal parameter set based on the
selected Objective Function and time series. The figure below shows the search configured using the DE
method.

510 The Search tab of the Component Editor
DE has three additional parameters beyond the two required for Simplex. The Population Size controls the
number of parameter sets (and therefore model evaluations) that occur in each iteration. The default value
of 30 is typically a good choice for hydrologic modeling applications. Using too few population members
makes it more difficult to assess convergence, and using too many makes the search take longer. When
there are a large number of parameters, or the problem is particularly complex, a higher value for Population
Size may help the search find the global optimum. The Seed Value initializes the pseudorandom number
generator that creates the parameter random samples in the search. A search with the same seed will
always produce the same random numbers, so two DE searches with the same settings and seed will always
produce the same results. The seed value is initialized by the system clock when a new DE search is
created. The Min Iterations setting requires the search to complete a minimum number of iterations before
assessing convergence. This can be used in conjunction with the Tolerance setting to achieve the desired
result. The Tolerance value of 0.01 is a good value to start with; however, if you find that there is still a
notable variability in the parameter traces in a converged trial, a smaller value may be required, or, use a
higher value for Min Iterations. Using too small of a value for Tolerance will increase the search time
without substantially improving parameter estimates. Using too large of a value will result in false
convergence.
Tolerance Setting
Each of the three search methods, Univariate, Simplex, and Differential Evolution, assess search
convergence in different ways. The Tolerance Setting is treated differently for each of these
three methods. Additionally, using different Objective Functions or applying a data
transformation may affect the rate of convergence due to the magnitude of the computed
Objective Function. Decreasing the tolerance setting will require additional iterations of the
search to be run and potentially increase the Optimization Trial run time. However, a smaller
tolerance value will result in parameter estimates that are closer to the Objective Function goal
with higher certainty.
Markov Chain Monte Carlo (MCMC) is the stochastic search method available in HEC-HMS. The general
principle of MCMC optimization is this: the algorithm seeks to visit the plausible parameter sets in a
parameter space by a random walk, and visit parameter sets that are more likely to have created the
observed dataset more often. MCMC search proceeds by generating a sequence of parameter values by
making random transitions from one state of a Markov Chain to another using a proposal distribution. Each
state is a set of model parameter values for the parameters being optimized. If the present state (parameter

values) of the Markov Chain implies good agreement between the simulated and observed data, then the
iteration is less likely to make large jumps away from the present state. This produces repeated samples
from a region of the parameter space that is associated with higher likelihood that the parameter set
produced the observed values. If the agreement is not good, then larger random leaps across the parameter
space are likely to occur. Multiple chains, which are initialized with different starting conditions, are used to
assess whether the samples have escaped the starting conditions and have begun to draw samples from the
highest-likelihood regions of the parameter space, which are unknown at the outset. The state of drawing
from the highest-likelihood region of the parameter space is called Equilibrium. It is desirable to have many
samples from this region in order to characterize the statistical properties of the parameters associated with
this high-likelihood space.
The MCMC Search requires additional parameterization in order to operate (shown below). Pool Size
controls the number of independent Markov Chains used in the simulation. Initial Sample controls the
number of burn-in samples to be taken before beginning to assess sample convergence. Min Iterations and
Max Iterations controls the allowable range of iterations for the simulation. Convergence allows the user to
set the value for the Gelman-Rubin statistic that discriminates between pre- and post-equilibrium samples
(the default value of 1.2 is generally sufficient; higher discrimination would be enforced using a lower
number not lower than 1.0). Equilibrium Sample controls the number of samples drawn after the simulation
has achieved a state of equilibrium.
Selecting the Search Method for the Optimization Trial is accessed from the Compute tab of the Watershed
Explorer in the Optimization Trial Component Editor. Click on the Optimization Trial node to display
the Component Editor for the Optimization Trial. If necessary, click on the Optimization Trials folder to
expand it and view the available Optimization Trials in the project.
511 The Search tab of the Component Editor when using Markov Chain Monte Carlo

16.1.9 Objective Function: Univariate, Simplex, and Differential Evolution

The Objective Function measures the goodness-of-fit between the computed results and observed data at
the selected element. For the Minimization Goal, there are fourteen different goodness-of-fit functions which
decrease as agreement between simulated and observed increases. The Maximization Goal can be used in
two different ways: to Maximize an Element Property such as flow volume or peak discharge, reservoir
stage, etc., or to Maximize a Goodness-of-Fit Statistic which increases in value as goodness-of-fit increases.
See the following table for Minimization Goal Objective Functions and the subsequent table for
Maximization Goal Objective Functions.
Objective Function Motivation
First Lag Autocorrelation Minimize systematic bias in residuals
Maximum of Absolute Residuals Minimize the largest single distance between observed and
simulated
Maximum of Squared Residuals Minimize the largest single distance between observed and
simulated
Mean of Absolute Residuals Minimize the average distance between observed and
simulated
Mean of Squared Residuals Minimize the average distance between observed and
simulated, with larger weight to larger errors
Peak-Weighted RMSE Minimize the average distance between observed and

simulated, with larger weight to data greater than the mean
Percent Error in Discharge Volume Minimize the difference between observed and simulated
volume
Percent Error in Peak Discharge Minimize the difference between observed and simulated
peak discharge value
Root Mean Square Error Minimize the average distance between observed and
simulated, with larger weight to larger errors; a classical
choice

Sum of Absolute Residuals Minimize the average distance between observed and
simulated
Sum of Squared Residuals Minimize the average distance between observed and
simulated, with larger weight to larger errors
Time-Weighted RMSE Minimize the average distance between observed and

simulated, with larger weight to data near the end of the
time window
Variance of Absolute Residuals Minimize the variation in residual values
Variance of Squared Residuals Minimize the variation in residual values, with larger weight
to larger residual values
31 Minimization Goal Objective Functions and their motivation
Coefficient of Determination Maximizes explained variance in observed data. Also called

R2 .
Discharge Volume Maximizes the total volume discharged over the Objective
Function time window.
Index of Agreement Maximizes the dimensionless Index of Agreement statistic.
Nash Sutcliffe Maximizes the dimensionless Nash-Sutcliffe Efficiency

statistic.
Peak Discharge Maximizes the single maximum discharge over the Objective
Function time window.
Peak Elevation Reservoir element only. Maximizes the single maximum

reservoir elevation over the Objective Function time window.

Relative Index of Agreement Maximizes the dimensionless Index of Agreement statistic

with less weight to large values
Relative Nash Sutcliffe Maximizes the dimensionless Nash Sutcliffe Efficiency

statistic with less weight to large values
32 Maximization Goal Objective Functions and their motivation
Maximization of an Element Time-Series Statistic, such as flow volume, peak discharge, or especially peak
reservoir pool elevation, is used in conjunction with hazard analyses such as those required for dam safety
studies. A particularly important optimization is when the trial is used in conjunction with the HMR 52 Storm
Precipitation Method to maximize a statistic. The Optimization Trial automatically adjusts HMR 52 Storm
parameters during the maximization trial, which replaces the need for many manual iterations of running
simulations to determine the optimal HMR52 Storm Parameter Set.
The figure below shows the Objective tab for the Optimization Trial Component Editor. Maximization is set
for the Goal of the optimization. The Location is the Basin Model Element where the user wants the
Optimization Trial to maximize the selected statistic. Any element within the Basin Model can be selected.
The Time-Series drop down list provides options based on the type of element selected for the location. If a
reach, subbasin, or junction is selected, then discharge is the only available time-series. If a reservoir element
is selected, then the user can choose between discharge and pool elevation. The Statistic is the computed
result that is maximized during the Optimization Trial. When Discharge is selected as the time-series, then
the user can choose a statistic of Discharge Volume or Peak Discharge. When Pool Elevation is selected as
the time-series, then the only statistic option is Peak Elevation.
512 Setting the Objective for an Optimization Trial
The HMR 52 Storm Parameters that can be adjusted in the Optimization Trial are Orientation, Area, X and Y
Coordinates, and the Peak Intensity Period. The figure below shows the the Parameter tab within the
Optimization Trial Component Editor. The Precipitation Parameters option is chosen for the Element (the
precipitation parameters are global to all subbasins in the Basin Model). The parameter list includes all
parameter available to be adjusted during the Optimization Trial. The initial value is the value specified in the
Meteorologic Model referenced by the Optimization Trial but the user can change the initial value. Default
minimum and maximum values are set by the program. The user should override these values with

information about the watershed. By default, the minimum and maximum x and y coordinates are defined
using coordinates from the subbasin GIS features.
513 Parameter options for an optimization trial configured to work with a HMR 52 Storm meteorologic model
Select the Objective Function Method for the Optimization Trial on the Component Editor for the Objective
Function (shown below). Access the Component Editor from the Compute tab of the Watershed Explorer. If
necessary, click on the Optimization Trials folder to expand it and view the available Optimization Trials in
the project. Click on the Optimization Trial node to expand it and see the Objective Function node. Click on
the Objective Function node to view the editor. Select the Objective tab within the Component Editor.
514 Setting a Minimization Goal in the Component Editor
An Element with Observed Data was selected at the time the Optimization Trial was created. This is the
location where the Objective Function will be evaluated. You can change the element location at any time
using the Component Editor for the Objective Function. The selection list shows all of the elements with
observed flow and/or snow water equivalent in the Basin Model selected for the Optimization Trial. Select a
different element in the list to change where the Objective Function will be evaluated. Recognize that
parameters can only be estimated at locations upstream of the selected element. Changing the location will

change which parameters can be estimated. In general, the observed data record at the selected element
location should not contain any missing data.
The Objective Function is evaluated over a Specified Time Window. The time window cannot begin before
the start time of the Optimization Trial. Also, the time window cannot end after the end time of the
Optimization Trial. However, you have the option of changing the time window to be narrower than the one
specified for the whole Optimization Trial. By default, the start and end time for the Objective Function will
default to the time window of the Optimization Trial.
16.1.10 Objective Function: Markov Chain Monte Carlo

Only one Goal and Objective Function are available for MCMC Optimization: Minimization Goal with the Sum
of Squared Residuals Objective Function. This combination allows the MCMC algorithm to assess the
likelihood that a particular parameter set is the one that produced the observed data. The figure below shows
this selection, which is populated by default when MCMC is selected.
515 The Objective tab of the Component Editor for MCMC optimization
16.1.11 Data Transformations

Three options are available for Data Transformations: No Transformation, Log Base 10, and Box-Cox. The
transform is applied both to the observed and simulated time series before the Objective Function is
computed. This will change the magnitude of the Objective Function in many cases. The figure below
shows the selection menu for data transformations. Both the Log Base 10 and Box-Cox transformation
methods require that the data being transformed are positive, so a Shift is applied in both cases to ensure
that all data are positive. This shift is automatically estimated. The Power parameter for the Box-Cox
transform is also automatically estimated using the method of maximum likelihood. If there are missing
observed data in the Objective Function time window, the transformation parameter(s) cannot be estimated,
and the search will default to the No Transform option.

516 Setting the Data Transformation in the Objective tab
16.1.12 Adding and Deleting Parameters

The parameters that will be automatically estimated must be at the selected element location or upstream of
it in the element network. When the selected location is changed, elements will be automatically deleted if
they are not upstream of the newly selected location. Parameters that can be chosen for estimation are a
selected set of the Canopy, Surface, Loss Rate, Transform, Baseflow Parameters in the Subbasin, Routing
Parameters in the Reach, and Snowmelt Parameters. Parameters that should be strictly measured in the
field are not allowed to be estimated. For example, it is not permissible to estimate subbasin area or a reach
length.
Care must be taken when selecting parameters for estimation. While it is possible to select the same
parameter more than once, it is not recommended. In this scenario, the search method attempts to improve
estimates by adjusting the same parameter value at different and sometimes conflicting points in the
search. This can lead to a so-called blocking condition where the search method cannot accurately
determine how to adjust parameters to improve the Objective Function and less than optimal results are
achieved.
Care must also be taken when selecting parameters at elements upstream of the observed data location. It
is possible to select multiple parameters that have similar affects on the computed hydrograph at the
evaluation location. In this case, adjustments to one parameter can off set adjustments in others. For
example, estimates of the time of concentration at multiple subbasins upstream of the evaluation location
often result in poor results. Special parameters called Scale Factors have been included that adjust all
similar parameters upstream of the evaluation location together in the same direction. However, care is still
required even with this special scaling. Scale factors can be used specifying the optimization location at a
downstream location from the elements to be scaled (e.g. a junction), adding a parameter, and selecting All
Subbasins as the element of interest. Then, the parameter entry will allow for selection of scale factors, as
shown below.

517 Parameter specification invoking scale factors
Add a new parameter to an Optimization Trial using the Watershed Explorer. Move the mouse over the
Optimization Trial and press the right mouse button (shown below). A context menu is displayed that
contains several choices including adding a parameter. Click the Add Parameter command. If you are using
the Univariate Search Method and a parameter has already been added to the Optimization Trial, additional
parameters will not be added. The following collection of tables show Subbasin Canopy Parameters,
Subbasin Surface Parameters, Loss Rate Parameters, Subbasin Transform Parameters, Baseflow
Parameters, Reach Routing Parameters, and Snowmelt Parameters that can be added.
518 Using the Add Parameter command from an Optimization Trial's context menu
Delete a parameter from an Optimization Trial using the Watershed Explorer. Select the parameter you wish
to delete by clicking on it in the Watershed Explorer; it will become highlighted. Keep the mouse over the
selected parameter and click the right mouse button (shown below). A context menu is displayed that
contains several choices including deleting a parameter. Click the Delete Parameter command.

519 Deleting a Parameter in the Watershed Explorer
Method Parameter
Dynamic Initial Storage
Maximum Storage
Gridded Simple Initial Storage
Simple Initial Storage
Maximum Storage
Crop Coefficient
33 Subbasin Canopy Parameters available for optimization
Method Parameter

Method Parameter
Maximum Storage
Maximum Storage
34 Subbasin Surface Parameters available for optimization
Method Parameter
Curve Number Initial Abstraction
Constant Rate
Deficit Constant Initial Deficit
Maximum Deficit
Constant Rate
Exponential Initial Range
Initial Coefficient
Coefficient Ratio
Exponent
Green Ampt Initial Content
Saturated Content
Suction

Method Parameter
Conductivity
Gridded Curve Number Initial Abstraction Ratio
Potential Retention Scale Factor
Gridded Deficit Constant Initial Deficit Ratio
Maximum Deficit Ratio
Constant Rate Ratio
Impervious Area Ratio
Gridded SMA Soil Initial Storage
Groundwater 1 and 2 Initial Storage
Initial Constant Initial Loss
Constant Rate
Smith Parlange Initial Content
Residual Content
Saturated Content
Bubbling Pressure
Pore Distribution
Conductivity
Beta Zero

Method Parameter
Soil Moisture Accounting Soil Initial Storage
Soil Storage
Soil Tension Storage
Soil Percolation
35 Subbasin Loss Rate Parameters available for optimization
Method Parameter
Clark Time of Concentration
Storage Coefficient
Kinematic Wave Plane Roughness
Subcollector, Collector, and

Main Channel Manning's n
ModClark Time of Concentration
Storage Coefficient
SCS Time Lag
S-Graph Time Lag
Snyder Peaking Coefficient
Standard Lag
36 Subbasin Transform Parameters available for optimization

Method Parameter
Bounded Recession Initial Flow Rate or Initial Flow Rate per Area 1
Recession Constant
Linear Reservoir Initial Flow Rate or

Initial Flow Rate per Area 1
Storage Coefficient
Number of Reservoirs / Steps
Nonlinear Boussinesq Initial Flow Rate or Initial Flow Rate per Area 1
Characteristic Length
Hydraulic Conductivity
Drainable Porosity
Threshold Ratio or Threshold Flow Rate 2
Recession Initial Flow Rate or Initial Flow Rate per Area 1
Recession Constant
37 Subbasin Baseflow Parameters available for optimization
1
The available parameter depends on the method selected for specifying the initial condition.
2
The available parameter depends on the method selected for specifying the recession threshold.

Method Parameter
Kinematic Wave Manning's n
Lag Lag
Modified Puls Subreaches
Initial Flow
Muskingum K
Subreaches
Muskingum Cunge Manning's n
Straddle Stager Lag
Duration
38 Reach Routing Parameters available for optimization
Method Parameter
Temperature Index PX Temperature
Base Temperature
Wet Meltrate *
Rain Rate Limit
ATI-Meltrate Coefficient
Dry Meltrate *

Method Parameter
Cold Limit
ATI-Coldrate Coefficient
Liquid Water Capacity
Ground Melt Rate
Hybrid Rain Threshold Temperature
Snow Threshold Temperature
Base Temperature
Melt Factor
Max Negative Melt Factor
ATI Coefficient
Wind Function
Energy Budget Rain Threshold Temperature
Snow Threshold Temperature
New Snow Albedo
Minimum Snow Albedo
Albedo Refresh Depth
Albedo Decay Coefficient

Method Parameter
Snow Thermal Conductivity
Snow Capillary Retention
Snow Hydraulic Conductivity
Effective Thermal Ground Depth
39 Snowmelt Parameters available for optimization
* Only Constant Value parameter types can currently be optimized
16.1.13 Specifying Parameter Information

A variety of information must be specified for each Optimization Parameter in order for the search method
to function. Select the parameter you wish to edit by clicking on it in the Watershed Explorer. Click on the
Optimization Trial node to expand it. The first node under the Optimization Trial will be the Objective
Function. Following the Objective Function will be a separate node for each parameter. Click on the desired
node in the Watershed Explorer to view the Component Editor for the optimization.
Each optimization parameter must select the Element where the desired parameter resides. All eligible
subbasin and reach elements upstream of the Objective Function evaluation location are shown in the
selection list. Eligible subbasins are those using the methods listed in the previous tables showing available
parameters. Eligible reaches are those using the methods listed in the Reach Routing Parameters available
for optimization (see table 38) table. Choosing an element from the list will update the list of available
parameters based on the methods in use at that selected element. You may also have the choice of selecting
the All Subbasins option in order to apply Scale Factors.
Each optimization parameter must select a specific Parameter for the chosen element. The available
choices are shown in the selection list. Once you make a choice from the list, the remainder of the data in
the Component Editor will become available for use (shown below).
520 Specifying Parameter information for an Optimization Trial

The Initial Value is the starting point for the parameter estimation process. The search method will begin
searching from that point for optimal parameter values. The default initial value is the parameter value in the
Basin Model that was selected for the Optimization Trial. You may change the initial value without affecting
the Basin Model.
Default Minimum and Maximum Values
The Minimum and Maximum values initially provided are the maximum allowed parameter range
in HMS. Do not use this range in a search. Any minimum and maximum value you provide must
be inside of this default range, but this initial range is far too wide for a successful search. A
narrow search range is much more likely to identify an optimal solution in a smaller number of
iterations than a wide one. The search methods are not always successful at traversing very
wide search ranges.
It is possible to Lock a parameter. When a parameter is locked, the initial value is used and no adjustments
are made during the search process.
The Minimum parameter value can be used to narrow the lower end of the range of values that will be used
by the search method. Likewise, the Maximum parameter value can be used to narrow the upper end of the
range of values that will be used by the search method. A good source of information for narrowing the
search range is preliminary estimates from field measurements or manual calibration. Default values for the
minimum and maximum are provided based on physical and numerical limits. The search may continue
outside the specified range. When it does so, a Penalty is applied to the Objective Function that is an
exponential function of the distance outside the specified range. The penalty nudges the search for optimal
parameter values back to the range between the specified minimum and maximum.
Parameter Ranges
The specified Parameter Ranges are not hard limits, and the search can potentially explore
parameter values outside of the range. The Penalty Function is a smooth continuous function in
order to prevent instabilities or issues with the solver, and the penalty factor can be small
depending on the magnitude of the parameter, the Objective Function, and other factors. If the
optimum parameter value is outside of the user specified range, and the improvement in the
Objective Function overcomes the magnitude of the penalty function, then the Trial will return
parameter values that are outside of the user specified range. This is an indication that the user
should carefully evaluate their parameter ranges, and potentially which parameters are involved
in the Optimization Trial.
Simplex Search Pro Tips

• No Optimization Search Method is perfect - it is limited by the complexity of the problem,

the sensitivity of the parameters you are optimizing, and the choice of initial guess and
parameter ranges you assign. The Nelder-Mead Simplex Search is efficient when the
problem is well-defined, but can become inefficient quickly with too many parameters, poor
initial guesses, and search ranges that are too large.
• The more parameters that you include in your search, the worse the performance of the
search. This is mainly due to the Curse of Dimensionality.
• Pick a meaningful Parameter Range and Initial Guess for your search. The best way to
speed up the search is to pick a small but meaningful range for each parameter. The next
best way is to provide a good initial guess. The search takes both into account at the
beginning of the trial.
• Avoid optimizing Initial Conditions if you can. If you add them as optimization parameters,
consider locking them and setting them yourself to improve the search.
• If you don't like your results the first time and think the search can do better, back-feed your
optimized parameters as initial guesses in the same search setup. The initial guesses are
important. Also consider reducing your tolerance, increasing the maximum number of
iterations, changing the Objective Function, and/or changing the time window where the
Objective Function are evaluated.
• Unfortunately, the Order of the parameters matters because it influences the initial setup of
the problem. If you are getting answers that don't make sense, consider changing the order
of the parameters in your search. The initial Simplex does its best to span each parameter
range but each parameter might not be equally dispersed in the initial state. Simplex is
really constrained in that it can only compare n+1 parameter values (where n is the number
of parameters) at any time, so choosing the parameter ranges well is crucial.
• If you are performing a Maximization Goal Search (e.g. maximizing peak discharge or
discharge volume), choose initial values close to the boundary that are likely to maximize
the search. For example, choose an initial value for constant loss rate that is close to the
lower bound.
• If you are using optimization to inform your model calibration, the Optimization Trials may
still be iterative in the same way as a manual calibration. You will want to adjust initial
values, parameter ranges, which parameters you include, the tolerance and number of
maximum iterations, what Objective Function you evaluate performance with, and/or the
Objective Function time window.
• Optimization is not automated calibration.
16.1.14 Resuming an Optimization Trial

Setting the Maximum Number of Iterations and Search Tolerance can be an iterative process. It might take a
few tries to identify the maximum number of iterations and a search tolerance small enough to converge to a
reasonable solution. With those larger models that take longer to run, starting out with a smaller maximum
number of iterations and larger tolerance can save time. In two situations, the Simplex and Differential
Evolution search methods can resume a search from a terminated state:
• If the search terminates without converging, because it has reached the maximum iteration limit

• If the search converges in fewer iterations than the maximum number of iterations
The user can continue a search that terminates by increasing the maximum number of iterations (for a
search that has not converged) or decreasing the search tolerance (for a search that has converged). To
resume the search, the user can only change either the maximum iteration (search has not converged) or the
tolerance (search has converged) setting. If the user changes any other setting (parameters, Objective
Function, etc.) the search state is no longer valid and the search will restart.
16.2 Computing Results for a Trial

Results for an Optimization Trial are generated by computing it. Changes in all the components used in the
trial are automatically tracked to determine if the results are current. When the results are no longer current,
the trial must be recomputed in order to refresh the results. Computing results begins with selecting an
Optimization Trial.
16.2.1 Selecting a Current Optimization Trial

There are two ways to select the current Optimization Trial. Both methods set the trial so that it can be
computed and results can be accessed from the Watershed Explorer and the Basin Map as soon as they are
available. The current Optimization Trial is shown in the title of the Basin Map.
The first way to select the current Optimization Trial is from the Toolbar. The compute selection box shows
all of the compute components in the project; Optimization Trials appear after Simulations Runs in the
selection box. Each Optimization Trial in the selection box includes the prefix Trial followed by the name of
the Optimization Trial. Click on the toolbar selection box and choose an Optimization Trial to become the
current trial.
The second way to select the current Optimization Trial is from the Watershed Explorer, on the Compute tab.
Select the Optimization Trial you wish to become the current trial by clicking on it in the Watershed Explorer.
The Optimization Trials are listed alphabetically in the Optimization Trials folder.
16.2.2 Computing an Optimization Trial

There are three ways to compute the currently selected Optimization Trial. All methods automatically
perform parameter checking, and if no errors are generated, proceed to the actual computing of optimization
results. Additionally, the program is designed to be computationally efficient. Only components with data
changes since the last compute will be recomputed; the remainder of the components have not changed so
previous optimization results are still applicable. If you wish, you may force all components to be
recomputed regardless of data changes since the last compute.
The first way to compute an Optimization Trial is from the Compute menu. Click on the Compute menu and
then select the Compute Trial command. The name of the current Optimization Trial is shown in brackets as
part of the menu command. If the command is not available, it is because there is no current Optimization
Trial; you must first select a trial. A window will automatically open that shows the progress of the compute.
You will need to manually close the window when the compute is done, whether it failed or was successful. If
you wish to force all components to be recomputed instead of just those with data changes, hold the CTRL
key while selecting the menu command.
The second way to compute an Optimization Trial is from the Watershed Explorer, on the Compute tab.
Select the Optimization Trial you wish to compute by clicking on it in the Watershed Explorer with the right
mouse button. A context menu is displayed that contains several choices including compute. Click

menu command.
The third way to compute an Optimization Trial is from the Toolbar. The Compute button is enabled
whenever there is a current trial that can be computed. If the button is not available or shows a different type
of compute, you must first select an Optimization Trial. Press the button to compute the current Optimization
Trial. The progress window will automatically open. If you wish to force all components to be recomputed
instead of just those with data changes, hold the CTRL key while selecting the toolbar button.
16.2.3 Computing Multiple Trials

Multiple Optimization Trials can be computed in rapid succession. Each trial included for simulation is
internally managed the same as if it were computed in isolation. The steps automatically performed for the
user begin with selecting the Optimization Trial, checking parameters for the trial, and finally computing the
simulation. This sequence is repeated in rapid succession for each Optimization Trial in the selected set.
Appropriate feedback is provided through a progress bar.
The multiple Optimization Trials must exist before they can be selected for a multiple compute. Select
the Multiple Compute command on the Compute menu. A manager is used to select Optimization Trials (see
figure). Make selections in the list and then press the Compute button to begin computing the selected trials.
A separate progress bar will be displayed for each Optimization Trial as it is computed. The progress bar
may disappear automatically at the conclusion of an Optimization Trial depending on the configurations in
the Program Settings. If errors are encountered while computing a trial, the progress bar will always remain
visible after all selected trials have finished computing regardless of any other settings.
521 Selecting Multiple Optimization Trials for Sequential Compute

16.3 Viewing Results for the Current Trial

A variety of Graphical and Tabular results are available after an Optimization Trial is computed. The same
results are also available for the current trial, so long as no data used in the simulation has changed. The
program tracks all of the data in the Optimization Trial and the selected Basin Model and selected
Meteorologic Model. It also tracks any Time-Series Data, Paired Data, or Grid Data used in the Basin and
Meteorologic Models. Results for an Optimization Trial can only be accessed when none of this data has
changed since the last time the trial was computed. If any of the data has changed, you will need to
recompute the Optimization Trial before you will be allowed to start accessing results.
Once a result is open for viewing it will remain open until it is closed by the user. It is possible that data used
during the simulation that produced the result could change while the result is open for viewing. In this case,
the open result will immediately show an indication that data has changed and the Optimization Trial needs
to be recomputed. After the trial is recomputed the open results are automatically updated with the new
results and the indication is updated with the date and time of the most-recent compute.
16.3.1 Objective Function Table

The Objective Function Table provides summary information about the Objective Function at the evaluation
location. It includes summary information such as the Basin Model and Meteorologic Model, Start Time, and
End Time. It indicates which Objective Function Method was used, the Start and End of the Evaluation
Period for the function, and the Final Value of the function when the search method finished. It gives the
Volume, Peak Flow, Time of peak flow, and Time to the Center of Mass of the computed and observed
hydrographs. Finally, it provides Volume and Peak Flow Differences between the computed and observed
hydrographs. The Objective Function Table is accessed from the Results menu. When the Basin Map is open
and a trial is selected, choose the Objective Function Summary command to view the results. Sample results
are shown in the following figure.
522 Objective function table for an optimization trial

16.3.2 Optimized Parameters Table

The Optimized Parameters Table provides summary information including the Basin Model, Meteorologic
Model, Start Time, and End Time. It lists in tabular form the parameters that were selected for optimization
with one row for each parameter. The table has columns for Element Name, Parameter Name, Units, Initial
Value, Optimized Value, and Sensitivity. The sensitivity is computed after the search method has finished; it
indicates the percentage change in the objective function value resulting from a one percent change in the
parameter value. The Optimized Parameters Table is accessed from the Results menu. When the Basin Map
is open and a trial is selected, choose the Optimized Parameters command to view the results. A sample set
of optimized parameters is shown in the following figure.
523 Optimized parameters table for an optimization trial
16.3.3 Parameter by Iteration Graph

The Iterative Evolution of a Parameter can be displayed by selecting the Parameter Graph in the results tree
view. For Deterministic Optimization, a single series is displayed, showing the parameter evolution
throughout the simulation. The decreasing variation in parameter values by iteration indicates that
convergence is occurring.

524 Parameter by iteration graph for deterministic optimization
For MCMC simulations, each chain in the pool is displayed on a single Plot of Iteration vs. Value (shown in
the following figure). Convergence to equilibrium is generally not visible on this plot. Instead, a special
Convergence Statistic Plot by Iteration is used instead (shown in the subsequent figure). Both of these plots
show a thinned version of the pre-equilibrium samples taken by the MCMC algorithm. Once the chains have
achieved equilibrium, then the sampler writes the specified number of equilibrium samples to a DSS record
for analysis or use later.
525 Parameter by iteration plot for MCMC optimization

526 MCMC convergence statistic plot by iteration
16.3.4 Observed Data Graphs

The Observed Data Graphs shows three different pieces of information: Computed Results and Observed
data at the Objective Function evaluation location, an Observed vs. Computed Scatter Plot, and a Residual
Time Series. The three graphs can be toggled between by selecting their respective tabs on the Observed
Data Graph window. These graphs allow visual comparison of how well the computed and observed
hydrographs match. Vertical Lines are drawn to show the Start and End of the Objective Function Time
Window. The Time-Series Graph can indicate the quality of the parameter estimation if good visual
agreement is achieved. If the computed results are exactly equal to the observed data, then the data will plot
exactly on a 45-degree line within the comparison graph. However, in virtually all cases the match is not
exact and there will be scatter in the data around the 45-degree line. Data points before the time of peak are
shown with Red Circles and Points and after the time of peak are shown with Blue Triangles. The amount of
scatter helps to indicate the quality of the parameter estimation. The Flow Residuals Graph shows the
difference between computed and observed for each time step. It is determined as the computed results
minus the observed data and may be positive or negative. Vertical lines are drawn to show the start and end
of the objective function time window. The magnitude of the Residuals helps to indicate the quality of the
parameter estimation. The residuals also help to indicate if there are Biases in the agreement between the
computed results and observed data. The Observed Data Graphs are accessed from the Results menu. When
the Basin Map is open and a trial is selected, choose the Observed Data command to view the results.
Sample Observed Data Graphs are shown in the following figures.

527 Observed Data Time-Series graph
528 Observed Data Comparison graph

529 Observed Data Residuals graph
16.3.5 Objective Function Graph

The Objective Function Graph shows the value of the Objective Function at Each Iteration of the search
method. The graph gives some indication of how fast the search method was able to converge to optimal
parameter values. In some cases it may show that the search method was not converging at all. The
Objective Function Graph is accessed from the Results menu. When the Basin Map is open and a trial is
selected, choose the Objective Function command to view the results. A sample Objective Function Graph is

530 Observed Data Residuals graph

There are three ways to access results for Individual Elements in the current Optimization Trial. All methods
show the same results. You must select one or more elements in the Basin Map before you can view results
for that element. However, not all elements in the Basin Map may have results. The Optimization Trial is
based on a Simulation Run that uses a specific Basin Model. The Optimization Trial works with the elements
upstream of the location where observed data is used to evaluate the Objective Function. The trial does not
perform simulations at any elements downstream of the element with observed data. Therefore, results will
only be available at elements upstream of the location with observed data. Any downstream elements will
have results shown as unavailable.
The first method for viewing individual element results is to use the Results menu. You may need to first
Optimization Trial is shown in brackets in the Basin Map Title Bar. Select one or more elements in the Basin
Map by clicking with the Arrow Tool. With an element selected in the Basin Map, click the Results menu and
select the Element Graph command, the Element Summary Table command, or the Element Time-Series
Table command. The appropriate result will automatically be shown in the Desktop area. The information
included in the graph (shown in the following figure) varies by element type, but always includes Outflow.
Optional items such as Observed Flow, Computed Snow Water Equivalent (SWE), and Observed SWE are
also included.

531 Element graph for a subbasin after an optimization trial
The information included in the Summary Table (Figure 11) also varies by element type but always includes
the Peak Flow, Time of Peak Flow, and Outflow Volume.
532 Element summary table for a subbasin after an optimization trial

The Time-Series Table includes the same information as the graph but in numerical format. If you selected
more than one element, then one result for each element will open. The menu commands on
the Results menu will only be enabled if the results for the current Optimization Trial do not need to be
recomputed, and there is an element selection in the Basin Map, and the selected element is upstream of the
objective function evaluation element with observed data.
533 Element time-series table for a subbasin after an optimization trial
The second method for viewing Individual Element Results is to use the Element icon in the Basin Map.
Again you may need to open the Basin Model before attempting to view results. Click on an element to
highlight it. Keep the mouse over the element and press the right mouse button. A context menu is displayed
that contains several choices including View Results. The name of the current Optimization Trial is shown in
brackets after the menu command. Move the mouse into the View Results submenu and select any of the
result commands: Graph, Summary Table, or Time-Series Table. The appropriate result will open. If you
selected more than one element, then one result for each element will open. The View Results menu
command will only be enabled if the results for the current Optimization Trial do not need to be recomputed,
and the selected element is upstream of the Objective Function evaluation element with observed flow.
The third method for viewing Individual Element Results is to use the Buttons on the Toolbar. First you must
open the Basin Model and select one or more elements in the Basin Map by clicking with the Arrow Tool.
Once you have a selected element, click the Graph, Summary Table, or Time-Series Table buttons. The
button for selecting a Graph shows a Line Plot. The button for the Summary Table shows a Plain Table. The
button for the Time-Series Table shows a Table Plus a Clock. The appropriate result will automatically open.
If you selected more than one element, then one result for each element will be added to the Desktop. The
toolbar buttons for viewing element results will only be enabled if the results for the current Optimization
Trial do not need to be recomputed, and there is an element selection in the Basin Map, and the selected
element is upstream of the Objective Function evaluation element with observed flow.

16.4 Viewing Results for Other Trials

In addition to viewing results for the currently selected Optimization Trial, it is also possible to view results
for other trials that are not the current selection. However, those other trials are also tracked in the same way
as the current trial to make sure data has not changed and results do not need to be recomputed. If any of
the data in an Optimization Trial changes, it will have to be recomputed before results can be viewed. Results
for other Optimization Trials are accessed from the Watershed Explorer, on the Results tab.
To begin viewing results, go to the Results tab of the Watershed Explorer and click on the desired
Optimization Trial icon. If necessary, click on the Optimization Trials folder to expand it and view the
Optimization Trials in the project. The Optimization Trial icon will be disabled if any data used in the trial has
changed and results need to be recomputed. If any result is open at the time data changes, the affected
results will be automatically updated.
16.4.1 Trial Results

The Objective Function Summary can be accessed by clicking on the Objective Function Summary node in
the Watershed Explorer. The table will be displayed. It is exactly the same table that can be viewed for the
current Optimization Trial. Similarly, the other results for Optimized Parameters, Hydrograph Comparison,
Flow Comparison, Flow Residuals, and Objective Function can also be accessed in the same way.
534 Viewing Optimization Results in the Watershed Explorer


Each element above the Objective Function Evaluation Location is shown in the Watershed Explorer under
the Optimization Trial node. These elements are listed in hydrologic order after the Objective Function
Graph. The results for each element are accessed by clicking on its node. The first item listed for each
element is the Graph; click on the Graph node to view the result (shown in the previous figure). It is exactly
the same graph that can be viewed for the current Optimization Trial. The information included in the graph
varies by element type but always includes Outflow. Optional items such as Observed Flow, Computed
Stage, and Observed Stage are also included. Similarily, the Summary Table and Time-Series Table can also
be accessed by clicking on the Summary Table or Time-Series Table node, respectively.

are listed under each Element node in the Watershed Explorer. The first node under each element is the
represent the different time-series data. Click on a Time-Series node to preview the data in the Component
Editor. You may select multiple time-series data by holding the shift or control key while using the mouse to
click on additional nodes. The selected time-series may come from different elements in the same
Optimization Trial, the same element in different trials, or different elements in different trials. Results can
also be combined from both Simulation Runs and Optimization Trials. The selected time-series data will
automatically be partitioned into groups by data type.
535 Viewing Optimization Trial Results in the Watershed Explorer


selected the desired time-series, you can press the Graph or Time-Series Table buttons on the Toolbar. The
chosen time-series will be graphed or tabulated.
536 Comparing Results from Two Different Optimization Trials
After you have opened a Time-Series Table or Graph, you may add Additional Time-Series Results. Position
the mouse over the time-series result you wish to add to the graph or table. Press and hold the left mouse
button and then drag the mouse over the top of the graph or table where you want the result to be added.
The mouse cursor will change to indicate which tables and graphs can accept the additional time-series.
Release the mouse button while it is over the desired table or graph and it will be automatically updated to
show the additional time-series results.

All of the graphs open with default properties for Line Color, Line Style, Data Symbols, etc. These default
properties have been selected to be appropriate for most situations. However, it is possible to customize the
properties in a graph. To change the properties, first click on the Graph to select it. Next go to the Results me

nu and select the Graph Properties command. An editor will open that can be used to change the properties
of the selected graph. The properties for each time-series curve can be changed. It is also possible to change
the properties for the Axis, Title, Gridlines, Patterns, and Legend. The editor used to change properties is the
same as used for Simulation Run Graphs shown in Viewing Results for Other Runs52.
52 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/Viewing+Results+for+Other+Runs

17 Forecasting Streamflow
Streamflow Forecasts are fundamental to effective operation of flood control reservoirs and levee systems.
Forecasts may also support emergency operations by providing estimates of the timing and extent of
expected hazardous or damaging flood conditions. Forecasts are based on recent meteorologic and
hydrologic conditions in the watershed, and may also incorporate predicted future meteorologic conditions.
Although most often used to predict anticipated flood conditions, streamflow forecasts may also support
water supply, hydropower, environmental flow requirements, and other operational needs.
17.1 Forecast Alternatives

Streamflow forecasting typically includes simulation of past and future conditions. The process begins with
the Selection of a Time of Forecast. Typically the time of forecast represents the last available time for
meteorologic observations of precipitation, temperature, and other variables. If observations of streamflow,
stage, or reservoir pool elevation are available, the last available value is also generally near the time of
forecast. The simulation is started hours or days before the time of forecast. Results computed between the
start time and the forecast time may be called the Look Back Period. When observations of current
watershed conditions are available, they may be compared with computed results from the look back period
to make calibration adjustments that improve model performance. Meteorologic observations are not
available after the time of forecast and predictions of future values are used. For example, a Quantitative
Precipitation Forecast (QPF) provides a meteorologic prediction of future precipitation depths. Similar
predictions are used for other meteorologic variables such as temperature. The future streamflow response
is simulated based on the predicted meteorologic conditions. This period of time in the future may be called
the Forecast.
Time is often of the essence when performing streamflow forecasting and modeling techniques must
consider this fact. During the development of a forecast it is common to group similar subbasins together
and apply parameter adjustments across each group. This is supported in Forecast Alternatives through the
use of Zones. Creating Zones is described in Z53ones54. Zones are used in a Forecast Alternative to quickly
set parameter adjustments when a group of subbasins have similar conditions. A parameter adjustment is
entered once and applied to all of the subbasins in the Zone. A local element override can be used if a
subbasin within a Zone diverges in behavior from the rest of the subbasins in that same Zone.
Forecast Alternatives are one of the components that can compute results. Each alternative is composed of
a Basin Model, Meteorologic Model, and Time Control Information. The alternative also includes Zone
Configurations for loss rate, transform, baseflow, and reach routing parameters. The alternative may
optionally include blending at elements with observed flow. Results are available at each element after the
simulation is complete.
A Forecast Alternative is constructed using the same initial conditions and parameters found in the Basin
Model selected in the Forecast Alternative. Then the parameter adjustments specified for each zone replace
the values taken from the Basin Model, with each subbasin or reach in the zone receiving the same
parameter adjustment. Any local element overrides are applied after zone adjustments. Initial baseflow may
then be set using observed flow and reservoir pool elevations set using observed stage. Also, initial reach
outflow may then be set using observed flow. Next, results are computed using the adjusted parameter
values and the selected Meteorologic Model. Finally the computed results are adjusted at elements with
observed flow and where blending has been selected.
53 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/Zones
54 https://www.hec.usace.army.mil/confluence/display/HMSDOCS/Zones
Forecasting Streamflow – 610

It is often necessary to prepare multiple forecasts with the same time of forecast. The multiple forecasts
provide alternative estimates of future conditions under different scenarios or assumptions. For example,
multiple alternatives could be used to explore the effect of different assumptions about the soil moisture
state of the watershed at the beginning of the look back period. In another example, several alternatives
could be used to explore the range of potential future flows depending on the amount of future precipitation.
One more example would be the development of multiple alternatives with different reservoir release
schedules in order to evaluate the impact of releases on downstream flows. Results from all considered
alternatives can be used as part of a decision support system to determine how reservoirs should be
operated, or to issue emergency flood warnings.
17.1.1 Creating a New Forecast Alternative

A new Forecast Alternative is created using a wizard that helps you navigate the steps to creating a new
alternative. There are two ways to access the wizard. The first way to access the wizard is to click on
the Compute menu and select the Create Compute | Forecast Alternative command; it is only enabled if at
least one Basin Model and Meteorologic Model exist. The wizard will open and begin the process of creating
a new Forecast Alternative. The second way to access the wizard is from the Forecast Alternative Manager.
Click on the Compute menu and select the Forecast Alternative Manager command. The Forecast
Alternative Manager will open and show any alternatives that already exist. Press the New button to access
the wizard and begin the process of creating a Forecast Alternative, as shown below.
537 Clicking the New button to create a Forecast Alternative
The first step of creating a Forecast Alternative is to provide the name for the new alternative (shown
below). A default name is provided for the new Forecast Alternative; you can use the default or replace it with
your own choice. After you finish creating the alternative you can add a description to it. If you change your
mind and do not want to create a new Forecast Alternative, you can press the Cancel button at the bottom of
the wizard or the X button in the upper right corner of the wizard. The Cancel button can be pressed at any
time you are using the wizard. Press the Next button when you are satisfied with the name you have entered
and are ready to proceed to the next step.

538 Entering a name for a new forecast alternative.
The second step of creating a Forecast Alternative is to select a Basin Model. All of the Basin Models that
are currently part of the project are displayed in alphabetical order. By default the first Basin Model in the
table is selected. The selected Basin Model is highlighted. You can use your mouse to select a different
Basin Model by clicking on it in the table of available choices. You can also use the arrow keys on your
keyboard to select a different Basin Model. Press the Next button when you are satisfied with the Basin
Model you have selected and are ready to proceed to the next step. Press the Back button if you wish to
return to the previous step and change the name for the new Forecast Alternative.
The third step of creating a Forecast Alternative is to select a Meteorologic Model. All of the Meteorologic
for selecting a Basin Model in step two and a Meteorologic Model in this step that will successfully combine
to compute results. Press the Next button when you are satisfied with the Meteorologic Model you have
selected and are ready to proceed to the next step. Press the Back button if you wish to return to the
previous step and select a different Basin Model for the Forecast Alternative.
The fourth step of creating a Forecast Alternative is to select a Time Interval and Zone Configurations. The
time interval must be selected from among the available choices. The default selection is 15 minutes, but
you may choose any of the available intervals. You may also select the Zone Configuration to use for loss
rate adjustments, transform adjustments, baseflow adjustments, and routing adjustments. The selection list
includes all of the Zone Configurations available in the Basin Model that was selected in step two. You may
use a different Zone Configuration for each type of adjustment. Alternately, you may use the same Zone
Configuration for loss rate, transform, baseflow, and routing adjustments. Press the Finish button when you
are satisfied with the name you have entered, the Basin Model and Meteorologic Model you selected, and are
ready to create the Forecast Alternative. Press the Back button if you wish to return to the previous step and
select a different Meteorologic Model.

17.1.2 Creating a New Automated Forecast

The Automated Forecast option automatically pulls data from the web, and generates a continuous forecast
with look back period data and forecast period data. As of v.4.9 the Automated Forecast option only
references data sources for the Continental United States. The Automated Forecast requires a connection to
the web. To run the Automated Forecast, you must have Basin Model with spatial elements (subbasin
elements must be georeferenced). Subbasin elements must use a structured or unstructured discretization
methods. The Basin Model should also be configured for continuous simulation. The figure below shows the
Automated Forecast option from the Forecast Alternative Manager.
539 Creating a new automated Forecast Alternative
On the first step of the Automated Forecast Wizard (shown below), a Name is selected by the user. A default
name is provided that corresponds with the time that the first wizard step was accessed. If the format of the
automatically generated name is maintained, the forecast and all related project components can be deleted
with a single click.
540 First step of the Automated Forecast Wizard

On the second step of the Automated Forecast Wizard (shown below), a Basin Model is selected. In the
Basin Model, Subbasin Elements must use the structured or unstructured discretization methods. The Basin
Model should also be configured for continuous simulation.
541 Second step of the Automated Forecast Wizard
If a valid USGS Station ID has been specified for discharge gages within the Basin Model, the Automated
Forecast will attempt to retrieve the latest flow data at that location. The figure below shows a station ID
specified for a USGS stream gage location.
542 Displaying the USGS Station ID for a time-series gage
On the third step of the Automated Forecast Wizard (shown below), look back period data is selected. At
least one data source must be selected to proceed.

543 Third step of the Automated Forecast Wizard
On the fourth step of the Automated Forecast Wizard (shown below), Forecast Period Data is selected. At
least one data source must be selected to proceed. If more than one dataset is selected, datasets will be
merged based on their precedence. Datasets are listed from top to bottom in order of highest to lowest
spatial and temporal resolution. Datasets with highest spatial and temporal resolution are given precedence
when merging.
544 Fourth step of the Automated Forecast Wizard
After selecting Next on the fourth step of the wizard, the Automated Forecast will begin downloading data
from the web. This can take up to several minutes depending on the size of the basin. The Automated
Forecast will merge datasets to create a continuous boundary condition. Precipitation and temperature
gridsets will be created with the same name as the forecast. A met model will be created with the same
name as the forecast and linked to the selected Basin Model. A new forecast will be created with the name
of the Automated Forecast. The data that is downloaded to run the forecast can be found in the Data
subdirectory of the project.

17.1.3 Copying a Forecast Alternative

There are two ways to copy a Forecast Alternative. Both methods for copying a trial create an exact
not interact.
The first way to create a copy is to use the Forecast Alternative Manager, which is accessed from
the Compute menu. Select the Forecast Alternative you wish to copy by clicking on it in the list of current
Forecast Alternatives. The selected alternative is highlighted after you select it. After you select an
alternative you can press the Copy button on the right side of the window. The Copy Forecast
Alternative window (shown below) will open where you can name and describe the copy that will be created.
A default name is provided for the copy; you can use the default or replace it with your own choice. A
of copying the selected Forecast Alternative. You cannot press the Copy button if no name is specified. If
you change your mind and do not want to copy the selected Forecast Alternative, press the Cancel button or
the X button in the upper right to return to the Forecast Alternative Manager window.
545 Creating a copy of a forecast alternative.
Forecast Alternative you wish to copy and press the right mouse button (shown below). A context menu is
displayed that contains several choices including Copy. Click the Create Copy command. The Copy Forecast
Alternative window will open where you can name and describe the copy that will be created. A default name
is provided for the copy; you can use the default or replace it with your own choice. A description can also be
selected Forecast Alternative. You cannot press the Copy button if no name is specified. If you change your
mind and do not want to copy the selected Forecast Alternative, press the Cancel button or the X button in
the upper right of the Copy Forecast Alternative window to return to the Watershed Explorer.

546 Copying a Forecast Alternative from the Watershed Explorer
17.1.4 Renaming a Forecast Alternative

There are two ways to rename a Forecast Alternative. Both methods for renaming an alternative change its
name and perform other necessary operations.
The first way to perform a rename is to use the Forecast Alternative Manager, which you can access from
the Compute menu. Select the Forecast Alternative you wish to rename by clicking on it in the list of current
alternatives. The selected alternative is highlighted after you select it. After you select an alternative you can
press the Rename button on the right side of the window. The Rename Forecast Alternative window (shown
below) will open where you can provide the new name. If you wish you can also change the description at the
same time. If the new description will be long, you can use the button to the right of the description field to
open an editor. When you are satisfied with the name and description, press the Rename button to finish the
process of renaming the selected Forecast Alternative. You cannot press the Rename button if no name is
specified. If you change your mind and do not want to rename the selected Forecast Alternative, press
the Cancel button or the X button in the upper right of the Rename Forecast Alternative window to return to
the Forecast Alternative Manager window.
547 Renaming a forecast alternative.
The second way to rename is from the Compute tab of the Watershed Explorer. Select the Forecast
Alternative you wish to rename by clicking on it in the Watershed Explorer; it will become highlighted. Keep
the mouse over the selected alternative and click the left mouse button again. The highlighted name will

change to editing mode (shown below). You can then move the cursor with the arrow keys on the keyboard
or by clicking with the mouse. You can also use the mouse to select some or all of the name. Change the
name by typing with the keyboard. When you have finished changing the name, press the Enter key to finalize
your choice. You can also finalize your choice by clicking elsewhere on the Compute tab. If you change your
mind while in editing mode and do not want to rename the selected Forecast Alternative, press
the Escape key.
548 Renaming a forecast alternative.
17.1.5 Deleting a Forecast Alternative

There are two ways to delete a Forecast Alternative. Both methods for deleting an alternative remove it from
the project and automatically delete previously computed results. Once an alternative has been deleted it
The first way to perform a deletion is to use the Forecast Alternative Manager, which you can access from
the Compute menu. Select the Forecast Alternative you wish to delete by clicking on it in the list of current
alternatives. The selected alternative is highlighted after you select it. After you select an alternative you can
press the Delete button on the right side of the window. A window will open where you must confirm that you
wish to delete the selected alternative as shown below. Press the OK button to delete the alternative. If you
change your mind and do not want to delete the selected Forecast Alternative, press the Cancel button or
the X button in the upper right to return to the Forecast Alternative Manager window.

549 Deleting a forecast alternative from the Forecast Alternative Manager.
The second way to delete is from the Compute tab of the Watershed Explorer. Select the Forecast
Alternative you wish to delete by clicking on it in the Watershed Explorer; it will become highlighted (shown
below). Keep the mouse over the selected alternative and click the right mouse button. A context menu is
displayed that contains several choices including delete. Click the Delete command. A window will open
where you must confirm that you wish to delete the selected alternative. Press the OK button to delete the
alternative. If you change your mind and do not want to delete the selected Forecast Alternative, press
the Cancel button or the X button in the upper right to return to the Watershed Explorer.
550 Deleting a Forecast Alternative in the Watershed Explorer


One of the principal tasks when creating a Forecast Alternative using the wizard is the selection of the
components that will be used to compute forecast results. The components include the Basin Model and the
Meteorologic Model. These components are selected when creating a new Forecast Alternative with the
wizard. However, you can change the Basin Model and Meteorologic Model you wish to use at any time using
the Component Editor for the Forecast Alternative. Access the Component Editor from the Compute tab of
the Watershed Explorer (shown below). If necessary, click on the Forecast Alternatives folder to expand it
and view the available Forecast Alternatives. The Component Editor contains a Basin Model selection list
that includes all of the Basin Models in the project. The Component Editor also contains a Meteorologic
Model selection list that includes all of the Meteorologic Models in the project.
551 Forecast Alternative Component Editor

552 (OLD) Forecast alternative component editor.

You must enter a Start Date and Time, a Forecast Date and Time, and an End Date and Time for the Forecast
Alternative. The time control information is not specified in the wizard used to create the Forecast
Alternative. The time control information must be entered after the alternative is created using
the Component Editor for the Forecast Alternative. Enter the start date using the indicated format for
numeric day, abbreviated month, and four-digit year. Enter the forecast date and end date using the same
format. The start time, forecast time, and end time are entered using 24-hour time format. Choose a time
interval from the available options which range from 1 minute up to 1 day. Finally, the start time, forecast
time and end time must all be an integer number of time intervals after the beginning of the day.
17.1.8 Selecting Zone Configurations

Zone Configurations are used to make parameter adjustments in a Forecast Alternative. A Zone
Configuration is defined in the Basin Model and the Basin Model may contain more than one Zone
Configuration. Each Zone Configuration contains either subbasin or reach elements but not both types of
elements. In turn, each Zone Configuration contains one or more zones. All of the subbasins or reaches in
the Basin Model should be assigned to a zone. The Zone Configuration is selected using the Component
Editor for the Forecast Alternative. A Zone Configuration can be selected for setting the lossrate
adjustments, the transform adjustments, the baseflow adjustments, and the routing adjustments. A different

Zone Configuration may be used for each selection, or the same Zone Configuration may be used more than
once. No parameter adjustments can be performed until Zone Configuration selections are made.
17.1.9 Start and Save States

The various mathematical equations used in the Basin and Meteorologic Models all contain State Variables.
A state variable is simply the current condition of the system at the end of a time interval. For example, the
state variable in a reservoir is the amount of water in storage, usually measured as an elevation. In the soil
moisture accounting loss method, the state variable is the amount of water currently held in each of the
layers. The state variables change during a simulation in response to changing boundary conditions and the
dynamics of the mathematical equation governing the method.
The State Variables all must be specified at the beginning of a simulation, in which case they are called
Initial Conditions. Some methods allow you to specify the value you wish to use, such as the initial storage in
a reservoir. Some methods implicitly specify the initial condition, for example loss methods that allow you to
specify the amount of infiltration that must occur before surface runoff begins, often called the initial loss.
Many of the channel routing methods assume the initial condition that initial outflow equals the first inflow to
the reach, or the user can specify the initial outflow.
States have two main purposes: Breaking Long Simulations into Smaller Time Periods, and Real-Time
Forecasting Operations. In the second case of real-time forecasting operations, the typical approach is often
to compute a simulation run daily and forecast three to five days into the future. The simulation can be
configured to run for five days, saving the state variables at the end of the first day. When the forecast is
updated on the subsequent day, it can start from the saved states of the previous day and continue forward.
In this way, continuously updated results can be obtained without requiring the simulation to start at the last
known watershed conditions which might be very old.
Saving out the start state variables during a Forecast Alternative, or starting a run from saved state variables
is optional. If you do not use saved state variables (start states), then the initial conditions will be specified
from the Basin and Meteorologic Models. If you do use the start states, the initial conditions specified in the
Basin and Meteorologic Models will be overridden by the values contained in the saved states used as the
start states. If you do not use save states, the Forecast Alternative will run normally. If you do choose to save
states, the Forecast Alternative will pause momentarily to save the state variables and then continue
normally. The save states condition (file) that is created can be used for any Forecast Alternative, the start
date of the Forecast Alternative does not have to be similar to the date when the save states were created.
The save states can be used across different Forecast Alternative runs, but you must make sure the Basin
and Meteorologic Models have similar configurations (similar elements in the Basin Model and similar
modeling methods in the Basin and Meteorologic Models) in order for the save states to be applicable.
Selecting optional start states for the Forecast Alternative is accessed from the Compute tab of
the Watershed Explorer. Open the Component Editor for the Forecast Alternative and then click on the States
tab (shown below). The States tab is always shown whenever the Forecast Alternative Component Editor is
shown. You can choose to save states and start the Forecast Alternative with existing saved states. Start the
simulation with saved states by choosing the states you wish to use from the Start States selection list. Only
states saved by running a Forecast Alternative configured to save states are shown. You will not be able to
select start states unless there are valid states available. A descriptive save states name can be helpful
when selecting the states to start a simulation. For example, a name of 28Dec2005 - 0800 was used when
saving states when creating the example shown below. The date and time the states were saved were used
for the name to aid in choosing these saved states in subsequent Forecast Alternatives.

553 Starting the forecast alternative using a save states file.
Creating optional save states for the Forecast Alternative is accessed from the Compute tab of
the Watershed Explorer. Open the Component Editor for the simulation run and then click on the States tab
(shown below). The States tab is always shown whenever the Component Editor is shown. To create a save
states file, you must change the Save States option from No to Yes, as shown below. You must specify a
Name for the save states and optionally may enter a Description. There are three ways to specify when the
states will be saved: At the End of the Simulation Run, At the Time of Forecast, or At a Specified Date and
Time During the Forecast Alternative. If you select to save states at the end of the run or at the time of
forecast, the program will automatically determine the correct date and time to save states. If you select to
save states at a specific time, you must enter the date and time. The specified date and time must be after
the start and either at or before the end of the simulation run.
A Forecast Alternative contains many tools for modifying initial conditions and parameters in the Basin
Model. These tools include Zonal Editors, Parameter Override Editors, Slider Bar Editors, and Initialization
Editors. Initial conditions pulled from the save states file will overwrite the initial conditions and parameter
adjustments computed by the Zonal Editors, Parameter Override Editors, and Slider Bar Editors. Initial
conditions computed by the Initialization Editors will overwrite initial conditions pulled from the save states
file.
554 Configuring a forecast alternative to save states during the compute time window.

17.2 Adjusting Parameters for the Forecast

The subbasins and reaches in a Forecast Alternative are initialized to default values using the parameter
values from the Basin Model. The parameter values in the elements may be adjusted for the forecast without
altering the original parameter values in the Basin Model. Note that it is not required to make parameter
adjustments during a forecast. When no parameter adjustments are made, the values taken from the Basin
Model are used without modification for the forecast. However, most forecasts will include parameter
adjustments to reflect current conditions in the watershed due to antecedent and meteorologic conditions.
17.2.1 Zone Parameter Adjustments

Adjustments are entered using the parameter editors for the Forecast Alternative. The editors are accessed
on the Compute menu by using the Forecast Parameter Tables command. Be sure to select a current
Forecast Alternative in order to access the editors. A separate parameter editor is shown for each loss rate,
transform, baseflow, and routing method used in the Basin Model. Adjustments are set for each zone using
the upper half of the parameter editor, as shown in the following figure. The upper half of of the editor
includes one row for each zone. Without zone adjustments, element results are calculated purely from the
Basin Model parameters.
Two columns are included for each editable parameter in the loss rate, transform, baseflow, routing, or snow
method. The first column labeled Zone Average shows the area-weighted average default parameter value
computed over all elements in the zone. A parameter adjustment can be entered in the second column
labeled Adjustment. If the adjustment is left blank, then the default parameter value will be used for each
element. You may add a fixed value to the parameter in all elements within the zone. For example, entering
an adjustment of +0.2 would increase the parameter value by 0.2 at each element in the zone. You may
subtract a fixed value from the parameter in all elements within the zone. For example, entering -2.1 would
decrease the parameter value by 2.1 at each element in the zone. You may multiply the parameter at each
element within the zone by a fixed value. For example, entering an adjustment of *0.8 would multiple the
parameter value by 0.8 at each element in the zone. Finally, you may replace the default parameter value at
each element within the zone by a fixed value. For example, entering an adjustment of 7.0 would set the
parameter value to 7.0 at each element in the zone. Press the Apply button when you have finished entering
zone parameter adjustments.

555 Entering parameter adjustments.
The bottom half of the parameter editor shows details about the parameter values for the elements in the
selected zone. Clicking on a row in the upper half of the parameter editor selects a zone. The lower half of
the editor will show one row for each element in the selected zone. Two columns are shown for each
parameter in the loss rate, transform, baseflow, or routing method. The first column labeled Base
Value shows the default parameter value taken from the Basin Model. The second column labeled Final
Value shows the adjusted parameter value that will be used during the forecast. Adjusted parameter values
are calculated using any zone adjustments entered in the upper half of the editor. The adjusted parameter
values are updated every time the Apply button is pressed. Finally, users can select a computation point and
all hydrologic elements upstream can be computed from this editor.
17.2.2 Element Parameter Overrides

Zone Parameter Adjustments provide a quick method for changing subbasin and reach parameters to
produce a forecast. However, sometimes one or more elements within a zone need a different adjustment
than the rest of the elements in that same zone. An Element Override may optionally be specified to use
different parameter values at an individual subbasin or reach within a zone. Without element overrides,
element results are calculated purely from the Basin Model parameters and zone adjustments.
To begin, you must Enable the Override for the desired element, as shown in the following figure. Within the
upper half of the parameter editor, click on the row for the Zone where the element is located. That zone will
become the current zone and the elements within the zone will be shown in the lower half of the parameter
editor. Next, click on the Override checkbox located in the lower half of the editor next to the element name.
Once the override is enabled, the Final Value column for each parameter will be editable for the selected
element. The default final value for each parameter is computed automatically by applying the zone
adjustment, if any, to the default value found in the Basin Model. During an override operation, the final value
of a parameter can be changed. You may choose to override only one parameter in the loss rate, transform,

baseflow, or routing method. Alternately, you may choose to override several parameters or all parameters.
Any override adjustments are removed when the checkbox for the element is cleared.
556 Entering an override for a specific element.
17.2.3 Slider Adjustments

A Slider Adjustment is an alternate way to view and change a Zone Parameter Adjustment or an Element
Parameter Override. An example of a slider adjustment is shown in the following figure. Instead of typing a
new value for the adjustment in a data entry table, the slider can be moved with the mouse to quickly obtain a
new factor. Slider adjustments enhance existing zone parameter adjustments and element parameter
overrides. Configuration information is required for each adjustment or override that will be manipulated with
a slider. Preparing to use a slider adjustment begins with selecting the adjustments or override and entering
configuration information.

557 Using the slider adjustments editor.
Slider Adjustments are part of the parameter data for a Forecast Alternative. They can be selected or
removed without affecting the zone parameter adjustments or element parameter overrides. The sliders for
the current Forecast Alternative are accessed on the Compute menu by using the Forecast Slider
Adjustments command. The forecast slider adjustments manager opens and shows a separate tab for each
loss rate, transform, baseflow, and routing method in the Basin Model used for the Forecast Alternative
(illustrated in the figure below). The upper table on the tab shows all of the zone parameter adjustments that
have been selected for a slider adjustment. Each adjustment that has been selected is shown on a separate
row. Parameters from multiple zones will all be shown in the table. The lower table shows all of the element
parameter overrides that have been selected for a slider adjustment. Each override has a separate row and
multiple elements in multiple zones are all shown together. The tables will be empty if no adjustments or
overrides have been selected for slider adjustments.

558 Viewing and managing the slider adjustments.
Select Slider Adjustments by clicking the Select button. A window will open where zone parameter
adjustments and element parameter overrides can be selected (shown in the following figure). A separate
tab is included for each loss rate, transform, baseflow, and routing method in the Basin Model used for the
Forecast Alternative.
Zone Parameter Adjustments are selected in the upper half of the screen. Clicking on a Zone Name will
display all of the parameter adjustments that are available for selection. There are multiple ways to select an
adjustment. You may click on a parameter adjustment and press the Select button. Alternately you may
double click on a parameter adjustment and it will be selected. To select multiple adjustments
simultaneously, hold the control key and click on each parameter adjustment. The selected adjustments are
highlighted. Press the Select button to choose all of the selected adjustments. Press the Close button when
you have finished selecting zone parameter adjustments.
Element Parameter Overrides are selected in the bottom half of the screen. Elements are only shown in the
bottom half if they are in the zone currently selected in the upper half. Click on a Zone Name in the upper half
to select it; the selected zone will remain highlighted until a different zone is selected. Move to the bottom
half and select an element by clicking on it. The available element parameter overrides will be shown after an
element is selected. Overrides are selected in the same way as zone parameter adjustments by pressing
the Select button or by double clicking on an override. Press the Close button when you have finished
selecting element override adjustments.

559 Selecting zone parameters for use as slider adjustments
Slider Adjustments can be removed from the Forecast Alternative using the Select Forecast Slider
Adjustments Manager (shown in the following figure). Access the manager for the current Forecast
Alternative by selecting the Compute menu and clicking the Forecast Slider Adjustments command. Remove
a slider for a zone parameter adjustment by clicking on the adjustment. The adjustment is highlighted when
it is selected. Press the Remove button and the slider will be removed from the slider adjustments. Slider
adjustments for element overrides can be removed the same way. Multiple slider adjustments can be
removed simultaneously by holding the control key and clicking on each of the adjustments before pressing
the Remove button.

560 Preparing to remove two slider adjustments
Selecting Slider Adjustments is the first step in preparing them for use. Each slider adjustment must also be
configured with the properties necessary to operate properly in the Slider Editor. Access the settings for the
current Forecast Alternative by selecting the Compute menu and clicking the Forecast Slider Settings
command. The table in the upper half shows the slider adjustments for zone parameters (shown in the
following figure). The first column displays the Zone Name while the second column shows the Parameter
Name. The next column shows the selected Adjustment Type. The type may be a value, increment, or factor.
The units of each zone parameter are shown for reference. The minimum value sets the left side of the slider
range while the maximum sets the right side of the range. The minimum and maximum values should be
specified carefully giving consideration to the nature of each parameter.
The table in the lower half shows the Slider Adjustments for Element Parameter Overrides. The Zone Name,
Element Name, and Parameter Name is shown for each slider adjustment. Use the same approach for
entering the settings for element parameter overrides as for zone parameters. The slider adjustment settings
can be closed when all configurations are complete.

561 Configuring settings for the selected slider adjustments
The Slider Adjustments can be opened from the Forecast Parameter Adjustment Editors. The editors are
accessed on the Compute menu by using the Forecast Parameter Adjustments command. Pressing
the Slider Adjustments button will open the Slider Editor. The button can only be pressed after the settings
have been configured in the Forecast Slider Settings.
17.3 Subbasin Baseflow Initialization

Baseflow typically sets the flow condition for subbasins at the beginning of a forecast simulation. All of the
available Baseflow Methods include an Initial Flow Condition at the Start of the Simulation. The initial
condition may be specified as an absolute flowrate (m3/s or ft3/s) or as a flowrate per area (m3/s per km2 or
ft3/s per mi2). The flow determined from the initial condition typically recedes until precipitation begins
generating surface flow.
Observed flow provides one good source for calculating the Baseflow Initial Condition at the start of the
simulation. In some cases observed flow may be available at the outlet of a subbasin and can be used
directly as the baseflow initial condition. It is more common that there will be multiple subbasins above the
observed flow location but this does not negate the use of observed flow. When there are multiple subbasins
above the observed flow location, a ratio can be applied to the observed flow to calculate the baseflow initial
condition for each subbasin. One approach to determing the ratio is to consider the subbasin area and the
drainage area at the observed flow location. Baseflow initial calculation from observed flow can be accessed
on the Compute menu using the Forecast Initial Baseflow. An example of the initial baseflow editor is shown
This Baseflow Initialization Feature is optional. When baseflow initialization is unused, subbasin flow is
calculated purely from the Basin Model parameters, zone adjustments, and element overrides. The
initialization feature may be applied at no subbasins, only one subbasin, several subbasins, or all subbasins.
Using the initialization feature supersedes the Basin Model parameters, zone adjustments, and element
overrides.

562 Using observed flow to automatically calculate initial baseflow
The Initial Baseflow editor uses the Baseflow Zone Configuration to assist in organizing data entry. The
current zone is selected in the upper left corner of the editor. Each subbasin in the zone is shown on a
separate row in the editor.
A Discharge Gage may be selected for each subbasin. Discharge gages must be created in the Time-Series
Gage Manager before they can be selected for a subbasin. Usually the selected gage will be at the outlet of
the subbasin or at some point downstream of the subbasin. The selected gage should be representative of
flow conditions at the subbasin. The observed flow rate at the gage will be shown for the start time of the
forecast alternative.
A Minimum and Maximum Flow Rate may be entered to qualify the use of the observed flow gage for
calculating the initial baseflow. The minimum and maximum values are used in conjunction with the Default
Flow Value. If the observed flow is less than the minimum, then the default value will be used instead. The
default will also be used if the observed flow is greater than the maximum. The minimum or maximum can
be left blank if the observed flow should be used without a lower or upper limit. Finally, the default value will
be used if the observed flow is missing at the start time of the forecast alternative.
The Observed Flow from the selected gage is multiplied by the specified Ratio in order to calculate the initial
baseflow estimated value. The ratio is only used if the observed flow is between the minimum and maximum
values or if the minimum or maximum values are left blank. It is required for the ratio to be greater than zero
and it may be greater than one. However, using a ratio greater than one should generally only be done if the
observed flow is not downstream of the subbasin and significant contributing drainage area exists between
the subbasin and the selected gage; this should be done only after careful analysis.
The Estimated Value is calculated from the observed flow gage using the ratio and substituting the default
value according to the minimum and maximum values. At first, the estimated value is also copied as the final
value. The Final Value can be edited to override the estimated value. Editing the final value may be necessary
if current flow conditions diverge from the assumptions used to develop the ratio. The final value for each
subbasin shown in the table will be reset to the estimated value when the Reset button is pressed.
17.4 Reach Outflow Initialization

All of the available Reach Routing Methods include an initial condition at the start of the simulation. The
initial condition may be used to set discharge equal to outflow or specified as an absolute flowrate (m3/s or

ft3/s). The flow determined from the initial condition typically recedes until runoff from upstream elements
begins generating inflow to the reach.
Observed flow provides one good source for calculating the initial outflow condition at the start of the
simulation. In some cases observed flow may be available at the upstream end of a reach and can be used
directly as the outflow initial condition. It is more common that there will be multiple elements between
observed flow locations but this does not negate the use of observed flow as a means to estimate the
outflow initial condition. When there are multiple elements between observed flow locations, a ratio can be
applied to the observed flow to calculate the outflow initial condition for each routing reach. One approach to
determining the ratio is to consider the upstream contributing drainage area for each reach within a zone and
compare against the total contributing drainage area at the observed flow locations. The reach outflow
initialization using the Reaches editor can be accessed on the Compute menu by selecting
the Forecast Initial Reach Outflow menu option. An example of the Reaches editor is shown in the following
figure.
This Reach Outflow Initialization Feature is optional. When reach outflow initialization is unused, reach
outflow is calculated purely from the basin model parameters, zone adjustments, and element overrides. The
initialization feature may be applied at no reaches, only one reach, several reaches, or all reaches. Using the
initialization feature supersedes the basin model parameters, zone adjustments, and element overrides.
563 Using observed flow to automatically calculate initial reach outflow
The Reaches editor uses the Reach Zone Configuration to assist in organizing data entry. The current zone
is selected in the upper left corner of the editor. Each reach in the zone is shown on a separate row in the
editor.
A Discharge Gage may be selected for each reach. Discharge gages must be created in the Time-Series
Gage Manager before they can be selected for a reach. Usually the selected gage will be at the upstream or
downstream end of the reach or at some nearby location. The selected gage should be representative of
initial flow conditions for the reach. The observed flow rate at the gage will be shown for the start time of the
forecast alternative.
A Minimum and Maximum Flow Rate may be entered to qualify the use of the observed flow gage for
calculating the initial reach outflow. The minimum and maximum values are used in conjunction with the
Default Flow Value. If the observed flow is less than the minimum, then the default value will be used
instead. The default will also be used if the observed flow is greater than the maximum. The minimum or

maximum can be left blank if the observed flow should be used without a lower or upper limit. Finally, the
default value will be used if the observed flow is missing at the start time of the forecast alternative.
The Observed Flow from the selected gage is multiplied by the specified Ratio in order to calculate the initial
reach outflow estimated value. The ratio is only used if the observed flow is between the minimum and
maximum values or if the minimum or maximum values are left blank. It is required for the ratio to be greater
than zero and it may be greater than one. However, using a ratio greater than one should generally only be
done if the selected gage is located a significant distance downstream of the reach and notable contributing
drainage area exists between the reach and the selected gage; this should be done only after careful
analysis.
The Estimated Value is calculated from the observed flow gage using the ratio and substituting the default
value according to the minimum and maximum values. At first, the estimated value is also copied as the final
value. The Final Value can be edited to override the estimated value. Editing the final value may be necessary
if current flow conditions diverge from the assumptions used to develop the ratio. The final value for each
reach shown in the table will be reset to the estimated value when the Reset button is pressed.
17.5 Reservoir Pool Initialization and Reset

Pool storage plays a key role in determining reservoir discharge. The initial storage must be specified in
every reservoir at the start of the forecast. By default the initial storage in each reservoir is taken from the
selected Basin Model. However, this value should be updated based on conditions at the start of the
forecast.
Storage often cannot be observed directly but can be calculated from the current pool elevation. A variety of
instruments are available for observing the pool elevation. The observed elevation provides the best method
for determining the pool storage at the start of the forecast. The observed elevation at the forecast time also
provides an opportunity for updating the pool storage if the simulated storage has diverged since the start
time.
All of the Reservoir Routing Methods provide multiple choices for specifying the Initial Pool Storage.
However, only Initial Elevation is used with the Forecast Alternative; initial elevation should be selected as
the initial condition for each reservoir in the Basin Model. Choosing the Initial Elevation option facilitates
adjusting storage directly for the Forecast Alternative using a special editor. The Forecast Reservoirs editor
is accessed from the Compute menu after a Forecast Alternative is selected. An example of the Forecast
Reservoirs editor is shown in the following figure.
The Forecast Reservoirs editor provides three choices for handling time-series data from the forecast time
to the end time. The same choice is applied to all reservoir elements in the Basin Model. It is used for any
discharge time-series selected at the reservoir. The Replace All With Zero choice will substitute zero
discharge for all time intervals after the forecast time even if some observed or specified values may be
available from the Time-Series manger. The Replace Missing With Zero choice will substitute zero for any
missing values between the forecast time and end time. The Replace Missing With Last choice will
substitute the last observed or specified value prior to the missing value during the period from the forecast
time to the end time.

564 Setting reservoir initial pool elevation at the forecast start time
The Forecast Reservoirs editor uses two tabs for separating initial pool elevation at the start time from
resetting the pool elevation at the forecast time. Each reservoir in the Basin Model is shown on a separate
row in the editor. The Start Time tab corresponds to the start time of the Forecast Alternative while the
Forecast Time tab is for the forecast time of the alternative.
The Start Time tab is where a Stage Gage may be selected for each reservoir. Pool elevation is taken from a
stage gage that must be created in the Time-Series Gage Manager before it can be selected for a reservoir.
The selected gage should represent a pool elevation observation at the reservoir. The observed elevation will
be shown for the start time of the Forecast Alternative.
A Minimum and Maximum Elevation may be entered to qualify the use of the observed stage gage for
calculating the initial storage. The minimum and maximum values are used in conjunction with the Default
Value. If the observed value is less than the minimum, then the default will be used instead. The default will
also be used if the observed value is greater than the maximum. The minimum or maximum can be left blank
if the observed value should be used without a lower or upper limit. A reasonable value for the minimum is
the lowest elevation in the reservoir pool, while a good value for the maximum is the highest allowable
elevation in the pool. Finally, the default will be used if the observed value is missing at the start time of the
Forecast Alternative.
The Estimated Value is calculated from the Observed Stage Gage by substituting the default value according
to the minimum and maximum values. At first, the estimated value is also copied as the final value. The Final
Value can be edited to override the estimated value. Editing the final value may be necessary if current
conditions compromise the pool elevation observation, such as during high winds. The final value for each
reservoir shown in the table will be reset to the estimated value when the Reset button is pressed.

565 Resetting the reservoir pool elevation at the forecast time
The Forecast Time tab allows the reservoir storage to be reset at the forecast time of the alternative, as
shown in the previous figure. The selection of the Stage Gage, Minimum Value, Maximum value, and Default
Value are shown for each reservoir. However, these properties are set on the Start Time tab and are only
repeated for easy reference.
The Forecast Time tab shows the Observed Elevation at the start time of the Forecast Alternative. The
observed value will be blank if the data is missing at the forecast time. The Estimated Value is calculated
from the observed stage gage by substituting the default value according to the minimum and maximum
values. The default value is also substituted if the observed value is missing. At first, the estimated value is
also copied as the final value. The Final Value can be edited to override the estimated value. The final value
for each reservoir shown in the table will be reset to the estimated value when the Reset button is pressed.
17.6 Blending Computed Flow with Observed Flow

The computed streamflow is never perfect. The accuracy of computed results will vary with the quality of the
model, expertise of the forecaster, knowledge of antecedent conditions in the watershed, accuracy of
precipitation and other meteorologic data, and other factors. Blending provides a method for systematically
using observed flow to adjust computed streamflow. Using observed flow for blending is optional. When
blending is unused, flow is calculated purely from the Basin Model parameters, zone adjustments, element
overrides, baseflow initialization, reach outflow initialization, and reservoir initialization and reset.
Blending is applied after outflow is computed at an element using the selected methods and specified
parameter values. The computed streamflow is replaced with the observed flow during the period from the
start time up to the time of forecast; this is the period during which observed data is available. There will be
some difference between the computed streamflow and the observed flow at the forecast time. A transition
from observed flow to computed streamflow is applied starting at the forecast time. The computed
streamflow is used after the transition is complete through to the end time. The final blended streamflow
becomes the outflow to the downstream element. The quality of the final blended streamflow depends
directly on the quality of the observed flow data and the quality of the model.

Three different options are available for performing the transition between observed flow and computed
streamflow. The Step option applies a fixed correction to the computed streamflow from the forecast time to
the end time. The difference between the observed flow and computed streamflow is calculated at the
forecast time. The difference (positive if observed flow is greater than computed streamflow, negative if
observed flow is less than computed streamflow) is added to the computed streamflow from the forecast
time to the end time. The Taper option applies a decreasing correction to the computed streamflow after the
forecast time. The difference between the observed flow and computed stream flow is calculated at the
forecast time. This initial difference is added to the computed streamflow at the forecast time. The
difference is then decreased linearly over the taper duration. At the end of the taper duration the applied
correction is exactly zero. The computed streamflow is then used from the end of the taper duration to the
Forecast Alternative end time. The None option applies no correction to the computed streamflow after the
forecast time. There will be an instantaneous jump from the observed flow to the computed streamflow at
the forecast time.
Blending is configured using the Blending editor for the Forecast Alternative. The editor is accessed on
the Compute menu by using the Forecast Blending command. A Blending editor is shown that includes all
elements in the Basin Model with observed flow, as shown in the following figure. Blending may be turned on
or off for each element. When Blending is off, the computed streamflow is used for the entire time window
from start time to end time even though observed flow is available. When blending is turned on, the blending
transition method must be selected from the available choices. A taper duration must be entered if the taper
blending option is selected. Additionally, an allowed missing percentage must be specified. If the
percentage of observed data during the lookback period is greater than this value, blending will not be
performed. Finally, users can select a computation point and all hydrologic elements upstream can be
computed from this editor.
566 Setting the blending properties for each element with observed flow

17.7 Computing Results for an Alternative

Results for a Forecast Alternative are generated by computing it. Changes in all the components used in the
alternative are automatically tracked to determine if the results are current. When the results are no longer
current, the alternative must be recomputed in order to refresh the results. Computing results begins with
selecting a Forecast Alternative.
17.7.1 Selecting a Current Forecast Alternative

There are two ways to select the current Forecast Alternative. Both methods set the alternative so that it can
be computed and results can be accessed from the Watershed Explorer and the Basin Map as soon as they
are available. The current Forecast Alternative is shown in the title of the Basin Map.
The first way to select the current Forecast Alternative is from the Toolbar. The Compute Selection Box
shows all of the compute components in the project; Forecast Alternatives appear after optimization trials in
the selection box. Each Forecast Alternative in the selection box includes the prefix Forecast followed by the
name of the alternative. Click on the Toolbar selection box and choose a Forecast Alternative to become the
current alternative.
The second way to select the current Forecast Alternative is from the Watershed Explorer, on the
Compute tab. Select the Forecast Alternative you wish to become the current alternative by clicking on it in
the Watershed Explorer. The Forecast Alternatives are listed alphabetically in the Forecast
Alternatives folder.
17.7.2 Computing a Forecast Alternative

There are three ways to compute the currently selected Forecast Alternative. All methods automatically
perform parameter checking, and if no errors are generated, proceed to the actual computing of Forecast
Alternative results. Additionally, the program is designed to be computationally efficient. Only components
with data changes since the last compute will be recomputed; the remainder of the components have not
changed so previous alternative results are still applicable. If you wish, you may force all components to be
The first way to compute a Forecast Alternative is from the Compute menu. Click on the Compute menu and
then select the Compute Forecast command. The name of the current Forecast Alternative is shown in
brackets as part of the menu command. If the command is not available, it is because there is no current
Forecast Alternative; you must first select an alternative. A window will automatically open that shows the
progress of the compute. You will need to manually close the window when the compute is done, whether it
failed or was successful. If you wish to force all components to be recomputed instead of just those with
data changes, hold the CTRL key while selecting the menu command.
The second way to compute a Forecast Alternative is from the Watershed Explorer, on the Compute tab.
Select the Forecast Alternative you wish to compute by clicking on it in the Watershed Explorer with the right
menu command.
The third way to compute a Forecast Alternative is from the Toolbar. The Compute button is enabled
whenever there is a current alternative that can be computed. If the button is not available or shows a
different type of compute, you must first select a Forecast Alternative. Press the button to compute the

current Forecast Alternative. The progress window will automatically open. If you wish to force all
components to be recomputed instead of just those with data changes, hold the CTRL key while selecting
the toolbar button.
17.7.3 Computing to a Computation Point

Any hydrologic element in a Basin Model can be designated as a Computation Point. Selecting a
computation point and unselecting a point is described in C55omputation Points56. It is also possible to
compute a Forecast Alternative to a computation point. This method of computing results only computes
the hydrologic element designated as a computation point plus any elements upstream of the point. It is
common for elements with observed flow to be designated as computation points. One approach to
performing calibration adjustments is to start at the most-upstream element with observed flow. After
adjusting parameters above the upstream point, calibration efforts are focused on the drainage between the
upstream point and the next point downstream. Computing to a point supports this calibration approach.
A Forecast Alternative can be computed to a point whenever at least one computation point has been
designated and an alternative is selected. Multiple ways in which users can compute to a point are
available. For instance, users can compute to a point from the Basin Model Map window by right-clicking on
a computation point in the map and selecting the Compute To Point command, as shown in the following
figure.

567 Computing forecast alternative results to an element that has been designated a computation point
Additionally, users can select a computation point and all hydrologic elements upstream will be computed
from Zone Parameter editors, as shown in the following figure (the selection is made in the lower left portion
of the Zonal Editor).

568 Computing forecast alternative results to an element from a Forecast Parameter Table
17.7.4 Computing Multiple Alternatives

Multiple Forecast Alternatives can be computed in rapid succession. Each simulated alternative is internally
managed the same as if it were computed in isolation. The steps performed for the user begin with selecting
the Forecast Alternative, checking parameters for the alternative, and finally computing the simulation. This
sequence is repeated in rapid succession for each Forecast Alternative in the selected set. Appropriate
feedback is provided through a progress bar.
The multiple Forecast Alternatives must exist before they can be selected for a multiple compute. Select
the Multiple Compute command on the Compute menu. A manager is used to select Forecast Alternatives,
as shown below. Make selections in the list and then press the Compute button to begin computing the
selected alternatives. A separate progress bar will be displayed for each Forecast Alternative as it is
computed. The progress bar may disappear automatically at the conclusion of a Forecast Alternative
depending on the configurations in the Program Settings. If errors are encountered while computing an
alternative, the progress bar will always remain visible after all selected analyses have finished computing
regardless of any other settings.

569 Selecting multiple forecast alternatives for sequential compute
17.8 Viewing Results for the Current Alternative

A variety of graphical and tabular results are available after a Forecast Alternative is computed. The same
results are also available for the current alternative, so long as no data used in the alternative has changed.
The program tracks all of the data in the Forecast Alternative and all of the data used in the Basin Model and
Meteorologic Model that are the basis of the Forecast Alternative. Results for a Forecast Alternative are only
available when none of this data has changed since the last time the alternative was computed. If any of the
data has changed, you will need to recompute the Forecast Alternative before you will be allowed to view
results.
the open result will immediately show an indication that data has changed and the Forecast Alternative
needs to be recomputed. After the Forecast Alternative is recomputed the open results are automatically
updated with the new results and the indication is updated with the data and time of the most-recent
compute.

There are three ways to access results for individual elements in the current Forecast Alternative. All
methods show the same results. You must select one or more elements in the Basin Map before you can
view results for that element.
Forecast Alternative is shown in brackets in the Basin Map Title Bar. Select one or more elements in the
Basin Map by clicking with the Arrow tool. With an element selected in the Basin Map, click the Results menu
and select the Element Graph command, the Element Summary Table command, or the Element Time-

Series Table command. The appropriate result will automatically be shown in the Desktop area. The
information included in the graph varies by element type, but always includes outflow. Also, a vertical marker
line will be included at the forecast time, as shown in the following figure. Optional items such as Observed
Flow, Computed Stage, and Observed Stage are also included.
570 Element graph for a junction after computing a forecast alternative
The information included in the Summary Table also varies by element type but always includes the Peak
Flow, Time of Peak Flow, and Outflow Volume, as shown in the following figure. If Observed Data are
available, then information about the observed data are presented, as well as Goodness-of-Fit Statistics
which describe the degree of agreement between the simulated time-series and the observed data.

571 Element summary table for a junction with observed data after computing a forecast alternative
The Time-Series Table includes the same information as the graph but in numerical format, as shown in the
following figure. If you selected more than one element, then one result for each element will open. The
menu commands on the Results menu will only be enabled if the results for the current Forecast Alternative
do not need to be recomputed, and there is an element selection in the Basin Map.

572 Element time-series table for a junction with observed data after computing a forecast alternative
The second method for viewing individual element results is to use the Element Icon in the Basin Map. Again
you may need to open the Basin Model and select a current Forecast Alternative before attempting to view
results. Click on an element to highlight it. Keep the mouse over the element and press the right mouse
button. A context menu is displayed that contains several choices including View Results. The name of the
current Forecast Alternative is shown in brackets after the menu command. Move the mouse into the View
appropriate result will open. If you selected more than one element, then one result for each element will
open. The View Results menu command will only be enabled if the results for the current Forecast
Alternative do not need to be recomputed.
The third method for viewing individual element results is to use the Buttons on the Toolbar. First you must
open the Basin Model, select a current Forecast Alternative, and select one or more elements in the Basin
Map by clicking with the Arrow tool. Once you have a selected element, click the Graph, Summary Table, or
Time-Series Table buttons. The button for selecting a Graph shows a Line Plot. The button for the Summary
Table shows a Plain Table. The button for the Time-Series Table shows a Table Plus a Clock. The
appropriate result will automatically open. If you selected more than one element, then one result for each

element will be added to the Desktop. The toolbar buttons for viewing element results will only be enabled if
the results for the current Forecast Alternative do not need to be recomputed, and there is an element
selection in the Basin Map.
17.9 Viewing Results for Other Alternatives

In addition to viewing results for the currently selected Forecast Alternative, it is also possible to view results
for other alternatives that are not the current selection. However, those other alternatives are also tracked in
the same way as the current Forecast Alternative to make sure data has not changed and results do not need
to be recomputed. If any of the data in a Forecast Alternative changes, it will have to be recomputed before
results can be viewed. Results for other Forecast Alternatives are accessed from the Watershed Explorer, on
the Results tab.
To begin viewing results, go to the Results tab of the Watershed Explorer and click on the desired Forecast
Alternative icon. If necessary, click on the Forecast Alternatives folder to expand it and view the alternative
in the project. The Forecast Alternative icon will be disabled if any data used in the alternative has changed
and results need to be recomputed. If any result is open at the time data changes, the affected results will be
automatically updated.

Each element in the Basin Model used in the Forecast Alternative is shown in the Watershed Explorer under
the Forecast Alternative node. These elements are listed in hydrologic order. The results for each element
are accessed by clicking on its node. The first item listed for each element is the graph; click on the Graph
node to view the result, as shown in the following figure. It is exactly the same graph that can be viewed for
the current Forecast Alternative. The information included in the graph varies by element type but always
includes Outflow. Optional items such as Observed Flow, Computed Stage, and Observed Stage are also
included. Similarly, the Summary Table and Time-Series Table can also be accessed by clicking on the
Summary Table or Time-Series Table node, respectively.

573 Viewing forecast alternative results in the Watershed Explorer

represent the different time-series data. Click on a Time-Series node to preview the data in the Component
Editor, as shown in the following figure. You may select multiple time-series data by holding the shift or
control key while using the mouse to click on additional nodes. The selected time-series may come from
different elements in the same Forecast Alternative, or the same element in different alternatives. Results
can also be combined from simulation runs, optimization trials, depth-area analyses, and Forecast
Alternatives. The selected time-series data will automatically be partitioned into groups by data type.


574 Viewing forecast alternative results in the Watershed Explorer

chosen time-series will be graphed or tabulated. An example is shown in the previous figure where results
from a Forecast Alternative with future precipitation (solid blue line) and a Forecast Alternative with no future
precipitation (dashed blue line) are compared against observed data (black line) at the same location for the
same time period.
575 Forecast streamflow at the same location
After you have opened a time-series table or graph, you may add additional time-series results. Position the
mouse over the time-series result you wish to add to the graph or table. Press and hold the left mouse button
and then drag the mouse over the top of the graph or table where you want the result to be added. The
mouse cursor will change to indicate which tables and graphs can accept the additional time-series. Release
the mouse button while it is over the desired table or graph and it will be automatically updated to show the
additional time-series results.


properties in a graph. To change the properties, first click on the graph to select it. Next go to
the Results menu and select the Graph Properties command. An editor will open that can be used to change
the properties of the selected graph. The properties for each time-series curve can be changed. It is also
possible to change the properties for the axis, title, gridlines, patterns, and legend. The editor used to change
properties is the same as those used for simulation run graphs shown in Viewing Results for Other Runs57.
17.10 Viewing Results for CWMS Alternatives

HEC-HMS may be used for hydrologic simulation within the Corps Water Management System (CWMS). The
CWMS includes tools for developing meteorologic scenarios based on weather forecasts. The CWMS also
includes other simulation models for reservoir operations, river hydraulics, and economic impact. Forecast
Alternatives created in HEC-HMS can be used in CWMS. An overarching CWMS Alternative includes a
meteorologic scenario with a HEC-HMS Forecast Alternative plus other simulation model alternatives. The
CWMS Alternative can be computed and results viewed through its own program interface. Information from
the CWMS Alternative is retained within the HEC-HMS Forecast Alternative, allowing for computing it and
viewing results at a later time.
To begin viewing results, go to the Results tab of the Watershed Explorer and click on the desired CWMS
Forecast Alternative icon. The CWMS Forecast Alternative includes the Alternative Label. The alternative
label is typically four characters, for example, N0A0. The original HEC-HMS Forecast Alternative will be
labeled as Default once it has been used in CWMS. If necessary, click on the Forecast Alternatives folder to
expand it and view the alternative in the project. The CMWS Forecast Alternative icon will be disabled if any
data used in the alternative has changed and results need to be recomputed. If any result is open at the time
data changes, the affected results will be automatically updated.

Each element in the Basin Model used in the CWMS Forecast Alternative is shown in the Watershed
Explorer under the CWMS Forecast Alternative node. These elements are listed in hydrologic order. The
results for each element are accessed by clicking on its node. The first item listed for each element is the
Graph; click on the Graph node to view the result, as shown in the following figure. It is exactly the same
graph that can be viewed for the default Forecast Alternative. The information included in the graph varies by
element type but always includes Outflow. Optional items such as Observed flow, Computed Stage, and
Observed Stage are also included. Similarly, the Summary Table and Time-Series Table can also be
accessed by clicking on the Summary Table or Time-Series Table node, respectively.

576 Viewing CWMS forecast alternative results in the Watershed Explorer

Graph, followed by the Summary Table and Time-Series table. The remaining nodes for each element
represent the different time-series data. Click on a time-series node to preview the data in the Component
click on additional nodes, as shown in the following figure. The selected time-series may come from different
elements in the same CWMS Forecast Alternative, or the same element in two different CWMS Alternatives,
or the same element in the default alternative and one or more CWMS Alternatives. Results can also be
combined from simulation runs, optimization trials, depth-area analyses, and Forecast Alternatives. The
selected time-series data will automatically be partitioned into groups by data type.

577 Viewing CWMS forecast alternative results in the Watershed Explorer

chosen time-series will be graphed or tabulated. An example is shown in the following figure where results
from a Forecast Alternative with future precipitation (solid blue line) and a Forecast Alternative with no future
precipitation (dashed blue line) are compared against observed data (black line) at a reservoir for the same
time period.

578 Forecast reservoir pool elevations for two different CWMS alternatives (N0S0 and O0S0)
17.11 Viewing Spatial Results for Forecast Alternatives

Spatial Results can be turned on for Forecast Alternatives. Refer to the Viewing Spatial Results (see page 553)
page in the Hydrologic Simulation section for information about configuring and viewing spatial results. The
modeler must be careful when setting the output interval for spatial results within the Component Editor for
the Forecast Alternative. As shown below, the modeler must choose the simulation time interval in the
Component Editor. The spatial results time interval cannot be smaller than the simulation time interval.

579 Turning on Spatial Results for a Forecast Alternative

18 Depth-Area Reduction
One of the principal results in many water resource studies is a flow-frequency curve. A common way to
develop a frequency curve is to use frequency precipitation events in combination with a hydrologic model. A
study of a large watershed usually includes multiple evaluation points in the stream network. The Depth-Area
Analysis automates the process of producing flow estimates due to frequency precipitation at multiple
points of interest within a watershed.
18.1 Depth-Area Analyses

A Depth-Area Analysis is designed to assist in the process of developing peak flows in a watershed due to
frequency precipitation. For example, it may be the goal to compute the streamflow expected to result from
the storm with 1% exceedance probability. The usual assumption is that the 1% precipitation will result in the
1% flow, and that the hydrology model can accurately simulate the conversion of precipitation to flow.
Developing the flow values throughout a watershed for a specific exceedance probability is a key step in
developing flow frequency curves.
Storm area is a key component of both the frequency storm and hypothetical storm precipitation methods.
The area is used to determine the appropriate depth-area reduction factor. The depth-area reduction factor is
used to account for the observation from empirical data that average precipitation intensity decreases as the
area of a storm increases. Thus the average precipitation intensity of a 200 km2 storm is generally much less
than the intensity of a 10 km2 storm. Proper determination of the flow at a given evaluation point in the
watershed requires that the frequency storm or hypothetical storm have an area equal to the drainage area at
that point. Failure to match the storm area to the drainage area can result in significant under or over
estimation of the flow. It is simple enough to setup a simulation run with the Meteorologic Model set to
compute flow at a particular evaluation point. However, it is often the case that the flow must be estimated
at many points in the watershed.
The Depth-Area Analysis automates the process of developing a separate frequency storm or hypothetical
storm for each evaluation point. The analysis requires the specification of an underlying Basin Model and a
Meteorologic Model. The Meteorologic Model must be set to use the Frequency Storm or Hypothetical
Storm Precipitation Methods. The analysis also includes the listing of various analysis points where the flow
should be evaluated. When the analysis computes, it automatically generates frequency storms based on the
one specified in the Meteorologic Model but with appropriate storm area for each analysis point. The
instantaneous peak flows at each analysis point are automatically collected and available in a tabular
display.
Depth-Area Analyses are one of the components that can compute results. Each Depth-Area Analysis is
based on a Basin Model and a Meteorologic Model. The Meteorologic Model selected must use the
Frequency Storm or Hypothetical Storm Precipitation Methods. The analysis also includes the definition of
the Simulation Time Window and Simulation Time Step, and the selection of Evaluation Points within the
Basin Model. A Summary Table with the key flow information necessary for constructing a flow-frequency
curve is available from the Watershed Explorer.
18.1.1 Creating a New Depth-Area Analysis

A new Depth-Area Analysis is created using a wizard that helps you navigate the steps to creating a new
analysis. There are two ways to access the wizard. The first way to access the wizard is to click on
Depth-Area Reduction – 655

the Compute menu and select the Create Compute | Depth-Area Analysis command; it is only enabled if at
least one Basin Model and Meteorologic Model exists. The wizard will open and begin the process of
creating a new Depth-Area Analysis. The second way to access the wizard is from the Depth-Area Analysis
Manager. Click on the Compute menu and select the Depth-Area Analysis Manager command. The Depth-
Area Analysis Manager will open and show any analyses that already exist. Press the New button to access
the wizard and begin the process of creating a Depth-Area Analysis, as shown in the following figure.
The first step of creating a Depth-Area Analysis is to provide the name for the new analysis. A default name
is provided for the new analysis; you can use the default or replace it with your own choice. After you finish
naming the analysis you can add a description to it. If you change your mind and do not want to create a new
Depth-Area Analysis, you can press the Cancel button at the bottom of the wizard or the X button in the
upper right corner of the wizard. The Cancel button can be pressed at any time you are using the wizard.
Press the Next button when you are satisfied with the name you have entered and are ready to proceed to
the next step.
580 Beginning the process of creating a new Depth-Area Analysis using the Depth-Area Analysis Manager

581 The first step of creating a new Depth-Area Analysis is to enter a name for the new analysis
The second step of creating a Depth-Area Analysis is to select a Basin Model. The third step of creating a
Depth-Area Analysis is to select a Meteorologic Model. All of the Meteorologic Models in the project are
contained in the list of Meteorologic Model. The Meteorologic Model should include the Frequency Storm or
Hypothetical Storm Precipitation Methods. By default, the Basin Model and Meteorologic Model are selected
in steps 2 and 3. You can use your mouse to select a different basin or Meteorologic Model by clicking on the
component in the table of available choices. You can also use the arrow keys on your keyboard to select a
different basin or Meteorologic Model. Press the Finish button when you are satisfied with the name you
have entered and the Basin and Meteorologic Models you have selected, and are ready to create the Depth-
Area Analysis. Press the Back button if you wish to return to the previous step.
18.1.2 Copying a Depth-Area Analysis

There are two ways to copy a Depth-Area Analysis. Both methods for copying an analysis create an exact
not interact.
The first way to create a copy is to use the Depth-Area Analysis Manager, which is accessed from
the Compute menu. Select the Depth-Area Analysis you wish to copy by clicking on it in the list of current
analyses. The selected analysis is highlighted after you select it. After you select an analysis you can press
the Copy button on the right side of the window. The Copy Depth-Area Analysis window (shown in the
following figure) will open where you can name and describe the copy that will be created. A default name is
provided for the copy; you can use the default or replace it with your own choice. A Description can also be
selected Depth-Area Analysis. You cannot press the Copy button if no name is specified. If you change your
mind and do not want to copy the selected Depth-Area Analysis, press the Cancel button or the X button in
the upper right to return to the Depth-Area Analysis Manager window.

582 Creating a copy of a Depth-Area Analysis
Depth-Area Analysis you wish to copy and press the right mouse button (shown in the following figure). A
context menu is displayed that contains several choices including Copy. Click the Create Copy command.
The Copy Depth-Area Analysis window will open where you can name and describe the copy that will be
created. A default name is provided for the copy; you can use the default or replace it with your own choice.
process of copying the selected Depth-Area Analysis. You cannot press the Copy button if no name is
specified. If you change your mind and do not want to copy the selected Depth-Area Analysis, press
the Cancel button or the X button in the upper right of the Copy Depth-Area Analysis window to return to
583 Copying a Depth-Area Analysis from the Watershed Explorer
18.1.3 Renaming a Depth-Area Analysis

There are two ways to rename a Depth-Area Analysis. Both methods for renaming an analysis change its
The first way to perform a rename is to use the Depth-Area Analysis Manager, which you can access from
the Compute menu. Select the Depth-Area Analysis you wish to rename by clicking on it in the list of current
the Rename button on the right side of the window. The Rename Depth-Area Analysis window (shown in the

following figure) will open where you can provide the new name. If you wish you can also change the
the Rename button to finish the process of renaming the selected Depth-Area Analysis. You cannot press
Depth-Area Analysis, press the Cancel button or the X button in the upper right of the Rename Depth-Area
Analysis window to return to the Depth-Area Analysis Manager window.
584 Renaming a Depth-Area Analysis
The second way to rename is from the Compute tab of the Watershed Explorer. Select the Depth-Area
Analysis you wish to rename by clicking on it in the Watershed Explorer; it will become highlighted. Keep the
mouse over the selected analysis and click the left mouse button again. The highlighted name will change to
editing mode (shown in the following figure). You can then move the cursor with the arrow keys on the
keyboard or by clicking with the mouse. You can also use the mouse to select some or all of the name.
Change the name by typing with the keyboard. When you have finished changing the name, press
the Enter key to finalize your choice. You can also finalize your choice by clicking elsewhere on the Compute
tab. If you change your mind while in editing mode and do not want to rename the selected Depth-Area
Analysis, press the Escape key.
585 Renaming a Depth-Area Analysis in the Watershed Explorer

18.1.4 Deleting a Depth-Area Analysis

There are two ways to delete a Depth-Area Analysis. Both methods for deleting an analysis remove it from
the project and automatically delete previously computed results. Once an analysis has been deleted it
The first way to perform a deletion is to use the Depth-Area Analysis Manager, which you can access from
the Compute menu. Select the Depth-Area Analysis you wish to delete by clicking on it in the list of current
to delete the selected analysis as shown in the following figure. Press the OK button to delete the analysis. If
you change your mind and do not want to delete the selected Depth-Area Analysis, press the Cancel button
or the X button in the upper right to return to the Depth-Area Analysis Manager window.
586 Preparing to delete a Depth-Area Analysis Manager
The second way to delete is from the Compute tab of the Watershed Explorer. Select the Depth-Area
Analysis you wish to delete by clicking on it in the Watershed Explorer; it will become highlighted (shown in
the following figure). Keep the mouse over the selected analysis and click the right mouse button. A context
menu is displayed that contains several choices including delete. Click the Delete command. A window will
open where you must confirm that you wish to delete the selected analysis. Press the OK button to delete the
analysis. If you change your mind and do not want to delete the selected Depth-Area Analysis, press

587 Deleting a Depth-Area Analysis in the Watershed Explorer

One of the principal tasks when creating a Depth-Area Analysis using the wizard is the selection of the
components that will be used to compute analysis results. The components include the Basin Model and the
Meteorologic Model. These components are selected when creating a new Depth-Area Analysis with the
wizard. However, you can change the Basin Model and Meteorologic Model you wish to use at any time.
Selecting the Basin Model for a Depth-Area Analysis after it has been created is accessed from the
Compute tab of the Watershed Explorer. Click on the Analysis node to display the Component Editor for the
Depth-Area Analysis. You may need to first click on the Analyses folder to expand it, then click on Depth-
Area Analyses folder. The Depth-Area Analysis tab is shown along with the Analysis Points tab, as shown in
the following figure. The selection list shows all of the Basin Models within the project. You can also press
the Basin Model button next to the selection list to bring up a chooser. The chooser helps to make a
selection by showing the description of Basin Model.
588 Selecting the Basin Model and Meteorologic Model used as the bases for the Depth-Area Analysis

Selecting the Meteorologic Model for a Depth-Area Analysis after it has been created is accessed from the
Compute tab of the Watershed Explorer. Click on the analysis node to display the Component Editor for the
Depth-Area Analysis. You may need to first click on the Analyses folder to expand it, then click on Depth-
Area Analyses folder. The Depth-Area Analysis tab is shown along with the Analysis Points tab, as shown in
the previous figure. The selection list shows all of the Meteorologic Models within the project. You can also
press the Meteorologic Model button next to the selection list to bring up a chooser. The chooser helps to
make a selection by showing the description of Meteorologic Model.
18.1.6 Entering a Time Window and Time Interval

You must enter a Start Date and Time and an End Date and Time for the Depth-Area Analysis. The time
control information is not specified in the wizard used to create the Depth-Area Analysis. The time control
information must be entered after the analysis is created using the Component Editor for the Depth-Area
Analysis. Enter the start date using the indicated format for numeric day, abbreviated month, and four-digit
year. Enter the end date using the same format. The start time and end time are entered using 24-hour time
format. The simulation time interval is required as well. Choose a time interval from the available options
which range from 1 minute up to 1 day. Finally, the start time and end time must each be an integer number
of time intervals after the beginning of the day. A default time interval of 1 Hour is selected when the analysis
is created.
18.1.7 Selecting Analysis Points

Selecting Analysis Points is done after a Depth-Area Analysis has been created using the wizard. Access
the Component Editor for the analysis points from the Compute tab of the Watershed Explorer. Click on the
analysis node to display the Analysis Points tab (shown in the following figure). You may need to first click
on the Analyses folder to expand it, and then click on the Depth-Area Analyses folder. The analysis points
are selected in a table. All elements in the Basin Model are available for selection. Select as many points as
necessary by selecting from the list for each point. To discontinue using a specific point, change the
selection for that point to None.
589 Selecting analysis points for a Depth-Area Analysis

18.2 Computing Results for an Analysis: Depth-Area Reduction

Results for a Depth-Area Analysis are generated by computing it. Changes in all the components used in the
analysis are automatically tracked to determine if the results are current. When the results are no longer
current, the analysis must be recomputed in order to refresh the results. Computing results begins with
selecting a Depth-Area Analysis .
18.2.1 Selecting a Current Depth-Area Analysis

There are two ways to select the current Depth-Area Analysis. Both methods set the analysis so that it can
be computed and results can be accessed from the Watershed Explorer and the Basin Map as soon as they
are available. The current Depth-Area Analysis shown in the title of the Basin Map.
The first way to select the current Depth-Area Analysis from the Toolbar. The compute selection box shows
all of the compute components in the project; Depth-Area Analysis appear after Forecast Alternatives in the
selection box. Each Depth-Area Analysis in the selection box includes the prefix Depth-Area followed by the
name of the analysis. Click on the toolbar selection box and choose a Depth-Area Analysis to become the
current analysis.
The second way to select the current Depth-Area Analysis from the Watershed Explorer, on the
Compute tab. Select the Depth-Area Analysis you wish to become the current analysis by clicking on it in
the Watershed Explorer. The Depth-Area Analysis are listed alphabetically in the Depth-Area Analysis folder.
18.2.2 Computing a Depth-Area Analysis

There are three ways to compute the currently selected Depth-Area Analysis. All methods automatically
perform parameter checking, and if no errors are generated, proceed to the actual computing of Depth-Area
Analysis results. Additionally, the program is designed to be computationally efficient. Only components with
data changes since the last compute will be recomputed; the remainder of the components have not
changed so previous analysis results are still applicable. If you wish, you may force all components to be
The first way to compute a Depth-Area Analysis from the Compute menu. Click on the Compute menu and
then select the Compute Depth-Area command. The name of the current Depth-Area Analysis shown in
Depth-Area Analysis ; you must first select an analysis. A window will automatically open that shows the
The second way to compute a Depth-Area Analysis from the Watershed Explorer, on the Compute tab.
Select the Depth-Area Analysis you wish to compute by clicking on it in the Watershed Explorer with the right
menu command.
The third way to compute a Depth-Area Analysis from the Toolbar. The compute button is enabled whenever
there is a current analysis that can be computed. If the button is not available or shows a different type of
compute, you must first select a Depth-Area Analysis . Press the button to compute the current Depth-Area

Analysis . The progress window will automatically open. If you wish to force all components to be
recomputed instead of just those with data changes, hold the CTRL key while selecting the toolbar button.
18.2.3 Computing Multiple Analyses

Multiple Depth-Area Analysis can be computed in rapid succession. Each analysis included for simulation is
user begin with selecting the Depth-Area Analysis , checking parameters for the analysis, and finally
computing the simulation. This sequence is repeated in rapid succession for each Depth-Area Analysis in the
selected set. Appropriate feedback is provided through a progress bar.
The multiple Depth-Area Analysis must exist before they can be selected for a multiple compute. Select
the Multiple Compute command on the Compute menu. A manager is used to select Depth-Area Analysis
(see figure below). Make selections in the list and then press the Compute button to begin computing the
selected analyses. A separate progress bar will be displayed for each Depth-Area Analysis as it is computed.
The progress bar may disappear automatically at the conclusion of a Depth-Area Analysis depending on the
configurations in the Program Settings. If errors are encountered while computing an analysis, the progress
bar will always remain visible after all selected analyses have finished computing regardless of any other
settings.
590 Selecting multiple Depth-Area Analyses for sequential compute
18.3 Viewing Results for the Current Analysis

A variety of Graphical and Tabular results are available after a Depth-Area Analysis is computed. The same
results are also available for the current analysis, so long as no data used in the analysis has changed. The
program tracks all of the data in the Depth-Area Analysis and selected Basin Model and Meteorologic Model
on which it is based. It further tracks all of the data used in the Basin Model and Meteorologic Model that is
the basis of the Depth-Area Analysis. Results for a Depth-Area Analysis are only available when none of this

data has changed since the last time the analysis was computed. If any of the data has changed, you will
need to recompute the Depth-Area Analysis before you will be allowed to view results.
Once a result is open for viewing it will remain open until it is closed by the user. It is possible that data or
model information used by the analysis that produced the result could change while the result is open for
viewing. In this case, the open result will immediately show an indication that data has changed and the
Depth-Area Analysis needs to be recomputed. After the Depth-Area Analysis is recomputed the open results
are automatically updated with the new results and the indication is updated with the data and time of the
most-recent compute.
18.3.1 Peak Flow Summary Table

The Peak Flow Summary Table shows certain information such as the Depth-Area Analysis Name,
underlying Basin Model and Meteorologic Model Names, and information about the Time Window. The
principal information is a table that includes one row for each Analysis Point. Columns are provided that give
the Name of the Analysis Point, Drainage Area, Peak Flow, and Time of Peak Flow. The data is obtained by
extracting results from the simulation that is performed for each analysis point. The Peak Flow Summary
Table is accessed from the Results menu. When the Basin Map is open and a Depth-Area Analysis is
selected, choose the Peak Flow Summary command to view the results. Sample results are shown in the
following figure.
591 Peak Flow Summary Table showing the computed peak flow for each analysis point

There are three ways to access results for individual elements in the current Depth-Area Analysis. All
methods show the same results. You must select one or more elements in the Basin Map before you can
view results for that element. However, not all elements in the Basin Map may have results. The Depth-Area
Analysis is based on a Basin Model and a Meteorologic Model. The Depth-Area Analysis works with selected
Analysis Points. The results are separate for each analysis point. Results for an analysis point are only

computed at the elements upstream of that analysis point; all other elements in the Basin Model will have no
results for that analysis point. When an element is upstream of more than one analysis point, you will need to
indicate the analysis point for which results are desired.
open the Basin Model by clicking on it in the Watershed Explorer, on the Components tab. The current Depth-
Area Analysis is shown in brackets in the Basin Map Title Bar. Choose the Analysis Point for which results
will be viewed, by selecting from the Results | Select Point menu. The currently selected analysis point is
shown in brackets in the menu. Next select one or more elements in the Basin Map by clicking with the
Arrow tool. With an element selected in the Basin Map, click the Results menu and select the Element
Graph command, the Element Summary Table command, or the Element Time-Series Table command. The
appropriate result will automatically be shown in the Desktop area. The information included in the Graph
(shown in the following figure) varies by element type, but always includes Outflow. Optional items such as
Observed Flow, Computed Stage, and Observed Stage are also included.
592 Element graph for a subbasin after a Depth-Area Analysis
The information included in the Summary Table (shown in the following figure) also varies by element type
but always includes the Peak Flow, Time of Peak Flow, and Outflow Volume.

593 Element Summary Table for a junction after a Depth-Area Analysis
The Time-Series Table (shown in the following figure) includes the same information as the Graph but in
numerical format. If you selected more than one element, then one result for each element will open. The
menu commands on the Results menu will only be enabled if the results for the current Depth-Area Analysis
do not need to be recomputed, and an Analysis Point has been selected on the Results menu.

594 Element time-series table for a reach after a Depth-Area Analysis
The second method for viewing individual element results is to use the Element icon in the Basin Map. Again
you may need to open the Basin Model before attempting to view results. You may also need to choose the
analysis point for which results will be viewed, by selecting from the Results | Select Point menu. Finally,
click on an element to highlight it. Keep the mouse over the element and press the right mouse button. A
context menu is displayed that contains several choices including View Results. The name of the current
Depth-Area Analysis is shown in brackets after the menu command. Move the mouse into the View
appropriate result will open. If you selected more than one element, then one result will open for each
element. The View Results menu command will only be enabled if the results for the current Depth-Area
Analysis do not need to be recomputed, and an analysis point has been selected on the Results menu.
The third method for viewing individual element results is to use the Buttons on the Toolbar. First you must
open the Basin Model, select a current analysis point on the Results menu, and finally select one or more
elements in the Basin Map by clicking with the Arrow tool. Once you have a selected element, click the
Graph, Summary Table, or Time-Series Table buttons. The button for selecting a Graph shows a Line Plot.
The button for the Summary Table shows a Plain Table. The button for the Time-Series Table shows a
Table Plus a Clock. The appropriate result will automatically open. If you selected more than one element,
then one result for each element will be added to the Desktop. The toolbar buttons for viewing element
results will only be enabled if the results for the current Depth-Area Analysis do not need to be recomputed,

and there is an element selection in the Basin Map, and the selected element is upstream of the analysis
point selected on the Results menu.
18.4 Viewing Results for Other Analyses

In addition to viewing results for the currently selected Depth-Area Analysis, it is also possible to view
results for other analyses that are not the current selection. However, those other analyses are also tracked
in the same way as the current Depth-Area Analysis to make sure data has not changed and results do not
need to be recomputed. If any of the data in a Depth-Area Analysis changes, it will have to be recomputed
before results reflect the current state of the model. Results for other Depth-Area Analyses are accessed
from the Watershed Explorer, on the Results tab.
To begin viewing results, go to the Results tab of the Watershed Explorer and click on the desired Depth-
Area Analysis icon. If necessary, click on the Depth-Area Analyses folder to expand it and view the analyses
in the project. If any result is open at the time data changes, the affected results will be automatically
updated, either a note will be added to the legend header stating the data has changed, or the results will be
updated with new results.
18.4.1 Peak Flow Summary Table

The Peak Flow Summary Table can be accessed by clicking on the Peak Flow Summary node in
the Watershed Explorer (shown in the following figure). The table will be displayed. It is exactly the same
table that can be viewed for the current Depth-Area Analysis.
595 Viewing Depth-Area Analysis results in the Watershed Explorer


Each Analysis Point is shown as a folder in the Watershed Explorer under the Depth-Area Analysis node.
The folder for each analysis point includes all of the elements above that analysis point. The results for each
element are accessed by clicking on its node. The first item listed for each element is the Graph; click on the
Graph node to view the result (shown in the previous figure). It is exactly the same graph that can be viewed
for the current Depth-Area Analysis. The information included in the graph varies by element type but always
includes Outflow. Optional items such as Observed Flow, Computed Stage, and Observed Stage are also
included. Similarly, the Summary Table and Time-Series Table can also be accessed by clicking on the
Summary Table or Time-Series Table node, respectively.

represent the different time-series data. Click on a time-series node to preview the data in the Component
click on additional nodes (shown in the following figure). The selected time-series may come from different
elements above the same analysis point, the same element for different analysis points, or different
elements in different analyses. Results can also be combined from simulation runs, optimization trials, and
Depth-Area Analyses. The selected time-series data will automatically be partitioned into groups by data
type.

596 Viewing Depth-Area Analysis results in the Watershed Explorer

the Desktop area. Begin by selecting the Time-Series you wish to include in the graph or table. Once you
have selected the desired time-series, you can press the Graph or Time-Series Table buttons on the Toolbar.
The chosen time-series will be graphed or tabulated (shown in the figure below).
After you have opened a Time-series Table or Graph, you may add additional time-series results. Position
the mouse over the time-series result you wish to add to the graph or table. Press and hold the left mouse
button and then drag the mouse over the top of the graph or table where you want the result to be added.
The mouse cursor will change to indicate which tables and graphs can accept the additional time-series.
Release the mouse button while it is over the desired table or graph and it will be automatically updated to
show the additional time-series results.

597 Comparing results from the same element at two different analysis points

properties in a graph. To change the properties, first click on the graph to select it. Next go to
the Results menu and select the Graph Properties command. An editor will open that can be used to change
the properties of the selected graph. The properties for each time-series curve can be changed. It is also
possible to change the properties for the Axis, Title, Gridlines, Patterns, and Legend. The editor used to
change properties is the same as used for simulation run graphs shown in Viewing Results for Other Runs58.

19 Assessing Model Uncertainty

It is widely known that hydrology models are rarely capable of perfectly simulating the watershed response.
The difference between the simulated response and the actual observed response is termed uncertainty and
may range from very small to excessively large. The uncertainty is usually due to a combination of factors
including inadequate meteorologic data, incongruities in model representation of physical processes, and
errors in identifying model parameter values. To a lesser degree, errors in observing the watershed response
may also contribute to Model Uncertainty. A quantitative assessment of the Model Uncertainty is a key
component of determining the reliability of the model predictions and critical to using the predictions with
risk-based engineering methodologies.
19.1 Uncertainty Analyses

Uncertainty Assessment is the process of determining the total error in the simulated watershed response,
for example, the flow at the outlet. The simulated flow at the outlet actually depends on many individual
components each with its own error. There is error in the meteorologic data because it is generally
impossible to accurately measure precipitation at the same spatial and temporal scale as the land surface
processes. There is error in the models of the hydrologic processes because it is generally impossible to
include every possible process at the scale it occurs, for example, animal burrows or plant transpiration.
There is error in the model parameter values because the equations are solved at a scale ranging from
meters up to whole subbasins and area-average values must be used. The error in the whole watershed
response includes all of these individual errors and the complex way in which they interact.
The watershed model is very complex and it may not be possible to attribute the total error to individual
components. An error in the precipitation data may be compensated with a corresponding error in the
infiltration parameter values. An error in the mathematical formulation of the infiltration or transpiration
process may be compensated with a corresponding error in the parameter values. An assumption about
process scale may lead to effective area-averaged parameter values that do not match values that would be
measured in the field. It is usually not possible to determine the exact error in each component or how the
errors are interacting and accumulating throughout the watershed model.
The error in an individual model parameter may be described with a probability distribution during an
Uncertainty Assessment. In one case the selected process model is well-suited to the watershed, the input
to the model is accurate, and the parameters can be estimated from field observations. In this first case
there is very little uncertainty in the parameter value. In another case the model is missing important
subtleties of the physical process, the input is poor, and parameter estimation is difficult. In this second case
there is a high degree of uncertainty in the parameter value. In both cases, a probability distribution can be
parameterized to reflect the uncertainty in the parameter, either small or large. Different model parameters
require differently formulated probability distributions and they may change from one watershed to another
or from one historical time period to another.
The Monte Carlo Method is one approach to estimating the uncertainty in the simulated watershed response
given the uncertainty in each of the model parameters. The Monte Carlo Method works by creating many
alternative models of the watershed using an automated sampling procedure. Each sample is created by
sampling the model parameters according to their individual probability distribution. Each sample is
simulated to obtain a watershed response corresponding to the sampled parameter values. All of the
responses from all of the samples can be analyzed statistically to evaluate the uncertainty in the simulated
watershed response. The program uses the Monte Carlo Method to perform the Uncertainty Assessment.
Assessing Model Uncertainty – 673

Within HEC-HMS, Uncertainty Analyses are one of the simulation components that can compute results.
Each analysis is composed of a Basin Model, Meteorologic Model, and Time Control Information. The
analysis also includes a selection of parameters to be evaluated and a description of the uncertainty for each
parameter. Several options are provided for how the uncertainty is described for each parameter. A variety of
results graphs are available from the Watershed Explorer for assessing the uncertainty in simulated
watershed response.
The Uncertainty Analysis primarily addresses the uncertainty in hydrologic model parameters which may be
due to incorrect parameter estimation, scale, or other problems. The user must identify each uncertain
parameter during the assessment and describe the uncertainty using an appropriate probability distribution.
Uncertainty in the meteorologic data is not specifically addressed within the program. Evaluation of
uncertainty in meteorology must be carried out using an assessment framework that integrates
meteorologic and hydrologic uncertainty. The Watershed Analysis Tool (HEC-WAT) modeling framework to
be capable of carrying out such an integrated assessment. The Uncertainty Analysis in HEC-HMS is designed
to work with HEC-WAT with expanded integration capabilities planned for future releases.
19.1.1 Creating a New Uncertainty Analysis

A new Uncertainty Analysis is created using a wizard that helps you navigate the steps to creating a new
the Compute menu and select the Create Compute | Uncertainty Analysis command; it is only enabled if at
least one Basin Model and Meteorologic Model exist. The wizard will open and begin the process of creating
a new Uncertainty Analysis. The second way to access the wizard is from the Uncertainty Analysis Manager.
Click on the Compute menu and select the Uncertainty Analysis Manager command. The Uncertainty
Analysis Manager will open and show any analyses that already exist. Press the New button to access the
wizard and begin the process of creating an Uncertainty Analysis, as shown in the following figure.
598 Beginning the process of creating a new uncertainty analysis using the Uncertainty Analysis Manager

The first step of creating an Uncertainty Analysis is to provide the Name for the new analysis (shown in the
following figure). A default name is provided for the new Uncertainty Analysis; you can use the default or
replace it with your own choice. After you finish creating the analysis you can add a description to it. If you
change your mind and do not want to create a new Uncertainty Analysis, you can press the Cancel button at
the bottom of the wizard or the X button in the upper right corner of the wizard. The Cancel button can be
pressed at any time you are using the wizard. Press the Next button when you are satisfied with the name
you have entered and are ready to proceed to the next step.
599 Entering a name for a new uncertainty analysis. The remaining steps are to select a basin model and a Meteorologic Model
The second step of creating an Uncertainty Analysis is to select a Basin Model. All of the Basin Models that
are currently part of the project are displayed in alphabetical order. By default the first Basin Model in the
table is selected. The selected Basin Model is highlighted. You can use your mouse to select a different
Basin Model by clicking on it in the table of available choices. You can also use the arrow keys on your
keyboard to select a different Basin Model. Press the Next button when you are satisfied with the Basin
Model you have selected and are ready to proceed to the next step. Press the Back button if you wish to
return to the previous step and change the name for the new Uncertainty Analysis.
The third step of creating an Uncertainty Analysis is to select a Meteorologic Model. All of the Meteorologic
for selecting a Basin Model in step two and a Meteorologic Model in this step that will successfully combine
to compute results. Press the Finish button when you are satisfied with the name you have entered, the
Basin Model and Meteorologic Model you selected, and are ready to create the Uncertainty Analysis. Press
the Back button if you wish to return to the previous step and select a different Basin Model.

19.1.2 Copying an Uncertainty Analysis

There are two ways to copy an Uncertainty Analysis. Both methods for copying an analysis create an exact
not interact.
The first way to create a copy is to use the Uncertainty Analysis Manager, which is accessed from
the Compute menu. Select the Uncertainty Analysis you wish to copy by clicking on it in the list of current
Uncertainty Analyses. The selected analysis is highlighted after you select it. After you select an analysis you
can press the Copy button on the right side of the window. The Copy Uncertainty Analysis window (shown in
the following figure) will open where you can name and describe the copy that will be created. A default
name is provided for the copy; you can use the default or replace it with your own choice. A description can
also be entered; if it is long you can use the button to the right of the description field to open an editor.
When you are satisfied with the name and description, press the Copy button to finish the process of copying
the selected Uncertainty Analysis. You cannot press the Copy button if no name is specified. If you change
your mind and do not want to copy the selected Uncertainty Analysis, press the Cancel button or the X button
in the upper right to return to the Uncertainty Analysis Manager window.
600 Creating a copy of an uncertainty analysis
Uncertainty Analysis you wish to copy and press the right mouse button (shown in the following figure). A
The Copy Uncertainty Analysis window will open where you can name and describe the copy that will be
process of copying the selected Uncertainty Analysis. You cannot press the Copy button if no name is
specified. If you change your mind and do not want to copy the selected Uncertainty Analysis, press
the Cancel button or the X button in the upper right of the Copy Uncertainty Analysis window to return to

19.1.3 Renaming an Uncertainty Analysis

There are two ways to rename an Uncertainty Analysis. Both methods for renaming an analysis change its
The first way to perform a rename is to use the Uncertainty Analysis Manager, which you can access from
the Compute menu. Select the Uncertainty Analysis you wish to rename by clicking on it in the list of current
the Rename button on the right side of the window. The Rename Uncertainty Analysis window (shown in the
the Rename button to finish the process of renaming the selected Uncertainty Analysis. You cannot press
Uncertainty Analysis, press the Cancel button or the X button in the upper right of the Rename Uncertainty
Analysis window to return to the Uncertainty Analysis Manager window.
601 Renaming an uncertainty analysis
The second way to rename is from the Compute tab of the Watershed Explorer. Select the Uncertainty
Analysis you wish to rename by clicking on it in the Watershed Explorer; it will become highlighted. Keep the
mouse over the selected analysis and click the left mouse button again. The highlighted name will change to
editing mode (show the following figure). You can then move the cursor with the arrow keys on the keyboard

or by clicking with the mouse. You can also use the mouse to select some or all of the name. Change the
name by typing with the keyboard. When you have finished changing the name, press the Enter key to finalize
your choice. You can also finalize your choice by clicking elsewhere on the Compute tab. If you change your
mind while in editing mode and do not want to rename the selected Uncertainty Analysis, press
the Escape key
602 Renaming an uncertainty analysis in the Watershed Explorer
19.1.4 Deleting an Uncertainty Analysis

There are two ways to delete an Uncertainty Analysis. Both methods for deleting an analysis remove it from
The first way to perform a deletion is to use the Uncertainty Analysis Manager, which you can access from
the Compute menu. Select the Uncertainty Analysis you wish to delete by clicking on it in the list of current
you change your mind and do not want to delete the selected Uncertainty Analysis, press the Cancel button
or the X button in the upper right to return to the Uncertainty Analysis Manager window.

603 Preparing to delete an uncertainty analysis from the Uncertainty Analysis Manager
The second way to delete is from the Compute tab of the Watershed Explorer. Select the Uncertainty
analysis. If you change your mind and do not want to delete the selected Uncertainty Analysis, press
604 Deleting an uncertainty analysis in the Watershed Explorer


One of the principal tasks when creating an Uncertainty Analysis using the wizard is the selection of the
components that will be used to compute uncertainty results. The components include the Basin Model and
the Meteorologic Model. These components are selected when creating a new Uncertainty Analysis with the
wizard. However, you can change the Basin Model and Meteorologic Model you wish to use at any time using
the Component Editor for the Uncertainty Analysis. Access the Component Editor from the Compute tab of
the Watershed Explorer (shown in the following figure). If necessary, click on the Uncertainty Analyses folder
to expand it and view the available Uncertainty Analyses. The Component Editor contains a Basin Model
Selection List that includes all of the Basin Models in the project. The Component Editor also contains a
Meteorologic Model Selection List that includes all of the Meteorologic Models in the project.
605 The uncertainty analysis component editor

You must enter a Start Date and Time and an End Date and Time for the Uncertainty Analysis. The time
control information is not specified in the wizard used to create the Uncertainty Analysis. The time control
information must be entered after the analysis is created using the Component Editor for the Uncertainty
Analysis (shown in the previous figure). Enter the start date using the indicated format for numeric day,
abbreviated month, and four-digit year. Enter the end date using the same format. The start time and end
time are entered using a 24-hour time format. Choose a time interval from the available options which range

from 1 minute up to 1 day. Finally, the start time and end time must each be an integer number of time
intervals after the beginning of the day.
19.1.7 Total Samples and Convergence

You must enter the Total Number of Samples for the Uncertainty Analysis. The number of samples is not
specified in the wizard used to create the Uncertainty Analysis. The total samples must be entered after the
analysis is created using the Component Editor for the Uncertainty Analysis (shown in the previous figure).
The number of samples specifies how many times the model parameters will be sampled during the
Uncertainty Assessment.
The Total Number of Samples must be large enough to accurately estimate the uncertainty in the watershed
response. The process of determining when the watershed response has been accurately estimated is called
Convergence. Convergence is achieved when statistical measures of the watershed response do not change
if more samples are computed. For example, one watershed response that is often considered is the
maximum pool elevation in a reservoir. The maximum pool elevation can be recorded for each sample and
the mean value can be computed over all samples. Convergence in the mean maximum pool elevation is
achieved when increasing the number of samples does not result in a change in the computed mean. If the
standard deviation in the maximum pool elevation were considered, then additional samples would have to
be computed until the computed standard deviation did not change. Fewer samples are required to estimate
the mean watershed response compared to the standard deviation in the response.
The user must select an appropriate Number of Samples to compute for the Uncertainty Analysis. The
number of samples required to achieve convergence depends on many factors including how a watershed is
modeled as well as which watershed response statistics are considered. Automatic convergence criteria are
not available at this time but are planned for a future release.
19.1.8 Adding and Deleting Parameters

The Parameters that will be sampled during the Uncertainty Assessment may be at any subbasin, reach, or
reservoir element in the Basin Model. Parameters that can be chosen for sampling are a selected set of the
canopy, surface, lossrate, transform, and baseflow parameters in the subbasin element. Selected parameters
can also be chosen for sampling from the routing parameters in the reach and from the components in the
reservoir. Two types of parameters can be selected for sampling. The first type includes Parameters in
Conceptual Models such as the time of concentration for a unit hydrograph. The second type includes
Parameters in Physically-Based Models subject to scaling issues, such as soil hydraulic conductivity or
channel bottom width. Most parameters in the Basin Model can be classified as one of these two types.
Add a new Parameter to an Uncertainty Analysis using the Watershed Explorer. Move the mouse over the
analysis and press the right mouse button (shown in the following figure). A context menu is displayed that
contains several choices including adding a parameter. Click the Add Parameter command. The parameters
are automatically named and numbered beginning with Parameter 1 and increasing the number as more
parameters are added.

606 Adding a parameter to an uncertainty analysis
The following tables list the Meteorologic Model (see table 40), Subbasin Canopy (see table 41), Subbasin
Surface (see page 0), Subbasin Loss Rate (see table 43), Subbasin Transform (see table 44), Baseflow (see table
45), Reach Routing (see table 46), and Reservoir (see table 47)parameters that can be added.
Method Parameter
HMR52 Precipitation X Coordinate
Y Coordinate
Storm Area
Storm Orientation
Peak Hour
Hypothetical Precipitation Storm Depth
Specified Precipitation Total Depth
Temperature Index Snow PX Temperature
Base Temperature

Method Parameter
Wet Meltrate *
Rain Rate Limit
ATI-Meltrate Coefficient
Dry Meltrate *
Cold Limit
ATI-Coldrate Coefficient
Ground Melt Rate
Initial Snow Water Equivalent
40 Meteorologic Model parameters available
* Only Constant Value parameter types can currently be sampled
Method Parameter
Maximum Storage
41 Subbasin Canopy parameters available for sampling

Method Parameter
Maximum Storage
42 Subbasin Surface parameters available for sampling
Method Parameter
Curve Number Initial Abstraction
Constant Rate
Impervious Area
Deficit Constant Initial Deficit
Maximum Deficit
Constant Rate
Impervious Area
Exponential Initial Range
Initial Coefficient
Coefficient Ratio
Exponent
Impervious Area

Method Parameter
Green Ampt Initial Content

Saturated Content
Suction
Conductivity
Impervious Area
Gridded Curve Number Initial Abstraction Ratio
Potential Retention Scale Factor
Gridded Deficit Constant Initial Deficit Ratio
Maximum Deficit Ratio
Constant Rate Ratio
Impervious Area Ratio
Gridded SMA Soil Initial Storage
Initial Constant Initial Loss
Constant Rate
Impervious Area
Smith Parlange Initial Content
Residual Content
Saturated Content

Method Parameter
Bubbling Pressure
Pore Distribution
Conductivity
Beta Zero
Impervious Area
Soil Moisture Accounting Soil Initial Storage
Soil Storage
Soil Percolation
Groundwater 1 and 2 Storage
Groundwater 1 and 2 Percolation
Groundwater 1 and 2 Coefficient
Impervious Area
43 Subbasin Lossrate parameters available for sampling

Method Parameter
Clark Time of Concentration
Storage Coefficient
Kinematic Wave Plane Length
Plane Slope
Plane Roughness
Subcollector, Collector, and Main Channel Length
Subcollector, Collector, and Main Channel Slope
Subcollector, Collector, and Main Channel Manning's n
Subcollector, Collector, and Main Channel Bottom

Width 1
Subcollector, Collector, and Main Channel Side Slope 2
ModClark Time of Concentration
Storage Coefficient
SCS Time Lag
S-Graph Time Lag
Snyder Peaking Coefficient
Standard Lag
44 Subbasin Transform parameters available for sampling
1
Bottom width can be selected for cross section shapes: deep, rectangle, trapezoid.
2
Side slope can be selected for cross section shapes: trapezoid, triangle.

Method Parameter
Bounded Recession Initial Flow Rate or Initial Flow Rate per Area 1
Recession Constant
Linear Reservoir GW 1, 2 and 3 Initial Flow Rate or Initial Flow Rate per Area 1
Groundwater 1, 2 and 3 Storage Coefficient
Groundwater 1, 2 and 3 Number of Steps
Groundwater 1, 2 and 3 Fraction
Nonlinear Boussinesq Initial Flow Rate or Initial Flow Rate per Area 1
Characteristic Length
Hydraulic Conductivity
Drainable Porosity
Recession Initial Flow Rate or Initial Flow Rate per Area 1
Recession Constant
45 Subbasin Baseflow parameters available for sampling
1
2
The available parameter depends on the method selected for specifying the recession threshold.

Method Parameter
Kinematic Wave Initial Outflow
Energy Slope
Manning's n
Diameter 1
Bottom Width 2
Side Slope 3
Lag Initial Outflow
Lag
Modified Puls Initial Outflow
Subreaches
Muskingum Initial Outflow
Subreaches
Muskingum Cunge Initial Outflow
Energy Slope
Manning's n
Diameter 1

Bottom Width 2
Side Slope 3
Normal Depth Initial Outflow
Energy Slope
Manning's n
Diameter 1
Bottom Width 2
Side Slope 3
Straddle Stager Initial Outflow
Lag
Duration
46 Reach Routing parameters available for sampling
1
Available for the circle cross section.
2
Available for deep, rectangle, and trapezoid cross section.
3
Available for trapezoid and triangle cross section.
Method Parameter
Initial Condition Initial Elevation 1
Initial Outflow 1
Initial Storage 1

Orifice Outlet Coefficient
Culvert Entrance Coefficient
Exit Coefficient
Manning's n
Level Dam Top Coefficient
Broad Crested Spillway Coefficient
Overtop Breach Top Elevation
Bottom Elevation
Bottom Width
Left Side Slope
Right Side Slope
Development Time
Piping Breach Top Elevation
Bottom Elevation
Piping Elevation
Bottom Width
Left Side Slope
Right Side Slope
Piping Coefficient

Development Time
Nonlevel Dam Top Coefficient
47 Reservoir parameters available for sampling
1
Delete a Parameter from an Uncertainty Analysis using the Watershed Explorer. Select the parameter you
wish to delete by clicking on it in the Watershed Explorer; it will become highlighted. Keep the mouse over the
selected parameter and click the right mouse button (shown in the following figure). A context menu is
displayed that contains several choices including deleting a parameter. Click the Delete
Parameter command.
607 Deleting a selected parameter from an uncertainty analysis
19.1.9 Specifying Parameter Information

Information must be specified for each selected parameter. The first selection is the Element (shown in the
following figure). The element selection list includes all of the elements in the Basin Model where at least
one parameter is available for selection. The Parameters available for selection will depend on the methods
that have been selected. Once the element has been selected, the second selection is the parameter at the
chosen element. All of the available parameters at the selected element are included in the list. If the
element selection is changed, then a new parameter selection will also need to be made.

608 Choosing an element where a parameter will be sampled, and selecting the parameter at that element
There are four different methods for sampling the selected parameter. The Component Editor will display the
appropriate property information depending on the sampling method that you choose. The Simple
Distribution Sampling Method allows you to choose a probability distribution and then samples the
parameter independently of all other parameters selected in the Uncertainty Analysis. The Monthly
Distribution Sampling Method allows you to choose an analytical probability distribution and enter unique
distribution properties for each month; the parameter is sampled independently of all other parameters in the
analysis. The Regression With Additive Error Sampling Method allows you to choose a previously selected
parameter and then define a linear relationship between this dependent parameter and the previously
selected parameter; an epsilon error term can be added to the linear relationship. The Specified Values
Sampling Method allows the user to specify a paired data curve for each of the selected parameters. The
program will systematically go through the list of parameter values when sampling values for the Uncertainty
Analysis. If multiple parameters are selected, then the same row from the parameter value paired data tables
will be selected during a parameter sample. This sampling method was designed to use results from an
MCMC optimization trial, but can be used with any parameter sets provided by the user. The information
specified for each of the four sampling methods is explained in the following sections.
19.1.9.1 Simple Distribution

The Simple Distribution Sampling Method can be used to define the uncertainty in a parameter
independently of all other parameters in the analysis. The sampling process is defined by the selection of a
Probability Distribution. There are eight analytical functions available with the choices shown in the
following table (see table 48). There is also the option of choosing an empirical function (User-Specified). The
empirical function must be defined in the paired data manager as a Cumulative Probability Distribution
before it can be selected in the sampling method. A new parameter value is sampled for each iteration of the
analysis, with draws coming from the specified probability distribution and distribution parameters.
The selection of a Probability Distribution determines which additional parameters must be entered. An
example of the Component Editor is shown in the following figure. Several of the distributions have a
minimum value of zero, but may need to be applied with parameters that typically begin their range at a value
greater than zero. A shift parameter is included with these functions for this purpose.

609 Setting sampling properties for a parameter using the Simple Distribution method
All of the available distribution choices include a Minimum and Maximum Value. These limits are imposed
as constraints on the parameter sampling process. If the value computed for a sample falls below the
minimum or above the maximum, then a new value is sampled. This process is repeated until a sampled
parameter value is generated that falls between the minimum and maximum, which effectively truncates the
distribution. These constraints are separate from the mathematical features of the selected distribution. The
limits are useful for enforcing physical process limitations or restricting the sampling to a reasonable range
for the selected parameter.
19.1.9.2 Monthly Distribution

The Monthly Distribution Sampling Method can be used to define the uncertainty in a parameter that shows
seasonal variation. The sampling process is defined by the selection of a Probability Distribution along with
Separate Distribution Parameter Values for Each Month. The eight available choices of probability
distribution are shown in the following table (see table 48). A new parameter value is sampled from the
specified probability distribution for each iteration in the analysis. The simulation start date and time of the
Uncertainty Analysis will be used to determine which monthly distribution parameter will be used in the
sampling process.
Function Formula
Beta
is the Beta function
Exponential

Function Formula
Gamma
Shape=α, Scale=β
is the Gamma function
Generalized Extreme Value

(Simple Distribution only)
Location = ξ, Scale = α, Shape = κ
Gumbel
Location = ξ, Scale = α
Kappa
(Simple Distribution only)
is the CDF
Location = ξ, Scale = α, Shape 1 = κ, Shape

2=h
Log-normal
Normal

Function Formula
Triangular
Lower = a, Upper = b, Mode = c
Uniform
Lower=a, Upper=b
Weibull
Shape=k, Scale=λ
48 Analytical probability distribution functions available for parameter sampling ang epsilon error term sampling. Parameter labels used
in the program are shown below the formula.
The selection of a Probability Distribution determines which additional parameters must be entered. An
example of the Component Editor is shown in the following table. A table is used to enter the probability
distribution parameter values for each month. A Shift parameter is included with probability distribution
functions that begin at zero to account for parameters that for physical reasons should begin at a value
greater than zero.

610 Setting sampling properties for a parameter using the Monthly Distribution method
All of the available probability distribution choices include Minimum and Maximum Limits that are imposed
on the parameter sampling process. The parameter will be repeatedly sampled until a value is obtained that
falls between the minimum and maximum, which effectively truncates the probability distribution. These
constraints are separate from the mathematical features of the selected probability distribution. The limits
are useful for enforcing physical process limitations or restricting the sampling to a reasonable range for the
selected parameter. The same minimum and maximum is used for all months of the year.
19.1.9.3 Regression With Additive Error

The Regression With Additive Error Sampling Method can be used to define the uncertainty in a parameter
that has a dependency linkage to another parameter in the analysis. The sampling process is defined by
selecting an Independent Parameter which will become the basis for generating the sampled value at this
parameter. In order for a regression element to be selected, a parameter with an independent sampling
method (i.e., simple distribution, monthly distribution or specified parameters) must be created first. A
Regression Relationship is defined between the two parameters. The calculation process proceeds for a
sample by first accessing the value computed for the independent parameter. Then the regression is applied
to calculate the preliminary parameter value for this parameter. An epsilon error term is then calculated using
one of the eight available probability distribution choices (listed in the previous table (see table 48)). The
sampled epsilon error is added to the preliminary parameter value to produce the value used for a sample.
From sample to sample, the values that vary are the sampled value for the independent regression parameter
and the error term. For realization of regression parameter xi, user-specified slope m, user-specified
intercept b and value sampled from the specified error distribution εi, the sampled parameter value Yi is:

A regression element, Reg Element, must be selected as shown in the Component Editor (shown in the
following figure). The available choices will be taken from the parameters that have been previously defined
in the Uncertainty Analysis. Once a regression element is selected, the regression parameter in the
regression element can be selected. The parameter choices will include all of the parameters in the
Uncertainty Analysis at the selected regression element.
611 Setting sampling properties for a parameter using the Dependent Plus Error method
A Relationship is used to define the linkage from the selected regression parameter to this parameter. The
first possibility for the relationship is a Linear one. Alternatively, a Semi-Logarithmic relationship may be
selected. In both cases, you must enter the Slope and Intercept for the relationship. If the linear relationship
is selected, the slope and intercept values should be appropriate for Normal space. If the log-linear
relationship is selected, the slope and intercept values should be appropriate for Natural Logarithmic space.
An Epsilon Error Term is added to the preliminary parameter value calculated from the regression parameter
and the linear or semi-logarithmic relationship. The epsilon term represents the error in the fitting
relationship between the regression parameter and this parameter. You may choose any one of the nine
analytical probability distributions to represent the error term. Based on the selected distribution, parameter
coefficients must be entered to define the distribution. You may also select a constant value (for example,
0). This means that the relationship between the two variables is deterministic, with uncertainty in both
parameters completely controlled by the sampling of the regression element.
19.1.9.4 Specified Values

The Specified Values Sampling Method allows the user to specify one or more sequences of parameter
values via a Parameter Value Samples Paired Data record. The paired data records can be created using the
Paired Data Component manager. The following figure shows the Component Editor for a Parameter Value
Samples Paired Data record. The primary use for this sampling method is to allow a user to sample
parameter values previously generated using a stochastic optimization scheme like Markov Chain Monte
Carlo. However, any means for generating a parameter set may be employed.

612 Default settings for a new Parameter Value Samples Paired Data record
A Parameter Value Sample Paired Data record can be used in an Uncertainty Analysis by selecting the
Specified Values Method for the Uncertainty Analysis Method and selecting the Paired Data record for the
Parameter Value (shown in the following figure). The Uncertainty Analysis editor will allow the user to select
any Parameter Value Sample Paired Data record; however, if a record with a mismatched parameter is used,
then an error will be thrown at compute informing the user that the parameter type is not an appropriate
match. For example, trying to use a Paired Data record for Initial Deficit values when sampling Time of
Concentration will produce an error. An error will also result if the Paired Data record does not contain any
entries. The Paired Data record can be any length relative to the selected number of total samples for the
Uncertainty Analysis: if the Paired Data record is shorter, then the list of parameters will be recycled until the
requisite number of samples is met; if it is longer, then not all values will be sampled.
613 Specified Values Uncertainty Analysis set up with a Parameter Value Paired Data record
Sampling of parameter values proceeds index-wise. If more than one parameter is varied using this method,
then samples will follow the order of parameters contained in all of the Paired Data records (i.e. index 1 for
all parameters, then index 2 if it exists, and so on). If one record is shorter than another, then it will begin
recycling values before the other parameters.
When maintaining correlation between parameters is desired, such as when applying sampled parameter
sets generated using Markov Chain Monte Carlo or a parameter set determined through manual calibration,
then each row of each Parameter Value Paired Data record is intended to represent a single set of
parameters. The intention is that the relationship between parameters is maintained to reflect the correlation
between variables as estimated by the MCMC procedure or manual calibration process. Often two or more
different parameters will have opposite or canceling effects on the goodness-of-fit, so it is more likely that
they will be sampled in a manner that reflects this variability.

If the user wishes to use parameter sets generated by a Markov Chain Monte Carlo Optimization Trial, then
the Parameter Sample Creator, available in the Tools menu after running the Optimization Trial (see Figure
18), can help.
614 Selecting the Parameter Sample Creator
In the Parameter Sample Creator dialog, the available MCMC Optimization Trials are shown (Figure 19). If the
user highlights one and selects Create…, the user is prompted to enter a name and a description. Once
created, the set of Parameter Value Sample Paired Data Records is available for use in an Uncertainty
Analysis with the Specified Values sampling method.
615 Parameter Sample Creator dialog box with available MCMC Optimization Trials for selection
19.2 Computing Results for an Uncertainty Analysis

Results for an Uncertainty Analysis are generated by computing it. Changes in all the components used in
the analysis are automatically tracked to determine if the results are current. When the results are no longer
selecting an Uncertainty Analysis.

19.2.1 Choosing Output Results

The Uncertainty Analysis is the only computation method that requires choosing Output Results. Results are
automatically stored for all elements in the simulation run, optimization trial, forecast alternative, and depth-
area analysis. These other computation methods can store results for all elements because the amount of
computed output is relatively compact. Conversely, if results were stored for all elements in the Uncertainty
Analysis, the amount of computed output would be significant and potentially overwhelming. Choosing the
elements in the Uncertainty Analysis where output results will be stored saves space and improves
manageability. Uncertainty output is configurable within the Uncertainty Analysis Component Editor, as
shown below.
616 Click the Select Specific Time Series And Interval button to choose output
Click the Select Specific Time Series And Interval button to open the selected results editor as shown
below.

617 Uncertainty Analysis Output Selection
Results can be selected or de-selected for inclusion in the Uncertainty Output Results file. Results that are
not written to the uncertainty output results file will not be available on the Results tab.
If HMS outputs are used as part of HEC-WAT for Model Linking, the HMS output must be
selected in the Uncertainty Output Results. The outputs from HMS will not be shown in the HEC-
WAT Model Linking editor if the results are not selected.
The Time Interval for each time-series can be modified. The default output interval is equivalent to the
simulation time interval. Additional output interval options are available that are multiples of the simulation
time interval. Filters are available at the top of the dialog that filter the table for element or time-series type.
Edits can be saved in the selected Results editor by clicking the Save button. You will be prompted to save
edits if you attempt to close the editor without saving first. If a change to the results configuration is made,
HEC-HMS will clear simulation results from the uncertainty output results file. The Uncertainty Analysis must
be re-computed to regenerate the results.

Presently, the only time-series that will be retained in the Uncertainty Analysis are Element
Outflow, Subbasin LWASS and SWE, and Reservoir Pool Elevation.
19.2.2 Selecting a Current Uncertainty Analysis

There are two ways to select the current Uncertainty Analysis. Both methods set the analysis so that it can
be computed and results can be accessed from the Watershed Explorer as soon as they are available. The
current Uncertainty Analysis is shown in the title of the Basin Map even though results cannot currently be
selected through the map.
The first way to select the current Uncertainty Analysis is from the Toolbar. The Compute Selection Box
shows all of the compute components in the project; Uncertainty Analyses appear after Depth-Area Analyses
in the selection box. Each Uncertainty Analysis in the selection box includes the prefix Uncertainty followed
by the name of the analysis. Click on the toolbar selection box and choose an Uncertainty Analysis to
become the current analysis.
The second way to select the current Uncertainty Analysis is from the Watershed Explorer, on the
Compute tab. Select the Uncertainty Analysis you wish to become the current analysis by clicking on it in
the Watershed Explorer. The Uncertainty Analyses are listed alphabetically in the Uncertainty
Analyses folder.
19.2.3 Computing an Uncertainty Analysis

There are three ways to compute the currently selected Uncertainty Analysis. All methods automatically
perform parameter checking, and if no errors are generated, proceed to the actual computing of Uncertainty
changed so previous alternative results are still applicable. If you wish, you may force all components to be
The first way to compute an Uncertainty Analysis is from the Compute menu. Click on the Compute menu
and then select the Compute Uncertainty command. The name of the current Uncertainty Analysis is shown
in brackets as part of the menu command. If the command is not available, it is because there is no current
Uncertainty Analysis; you must first select an analysis. A window will automatically open that shows the
The second way to compute an Uncertainty Analysis is from the Watershed Explorer, on the Compute tab.
Select the Uncertainty Analysis you wish to compute by clicking on it in the Watershed Explorer with the right
mouse button. A context menu is displayed that contains several choices including Compute. Click
menu command.
The third way to compute an Uncertainty Analysis is from the Toolbar. The Compute button is enabled
whenever there is a current analysis that can be computed. If the button is not available or shows a different
type of compute, you must first select an Uncertainty Analysis. Press the button to compute the current
Uncertainty Analysis. The progress window will automatically open. If you wish to force all components to be


Multiple Uncertainty Analyses can be computed in rapid succession. This feature should be used carefully
because the time required to compute an Uncertainty Analysis is much longer than all other compute types.
Each simulated analysis is internally managed the same as if it were computed in isolation. The steps
performed for the user begin with selecting the Uncertainty Analysis, checking parameters for the analysis,
and finally computing the simulation. This sequence is repeated in rapid succession for each Uncertainty
Analysis in the selected set. Appropriate feedback is provided through a progress bar.
The multiple Uncertainty Analyses must exist before they can be selected for a multiple compute. Select
the Multiple Compute command on the Compute menu. A manager is used to select Uncertainty Analyses
(shown below). Make selections in the list and then press the Compute button to begin computing the
selected analyses. A separate progress bar will be displayed for each Uncertainty Analysis as it is computed.
The progress bar may disappear automatically at the conclusion of an Uncertainty Analysis depending on the
settings.
618 Selecting multiple uncertainty analyses for sequential compute
19.3 Viewing Results for an Analysis

A variety of Graphical and Tabular Results are available after an Uncertainty Analysis is computed. The
program tracks all of the data in the Uncertainty Analysis, the selected Basin Model, and the selected
Meteorologic Model. It also tracks any time-series data, paired data, or grid data used in the basin and
Meteorologic Models. Results for an Uncertainty Analysis can only be accessed when none of this data has
changed since the last time the analysis was computed. If any of the data has changed, you will need to
recompute the Uncertainty Analysis before you will be allowed to start accessing results.

the open result will immediately show an indication that data has changed and the Uncertainty Analysis
needs to be recomputed. After the analysis is recomputed the open results are automatically updated with
the new results and the indication is updated with the date and time of the most recent compute.
19.3.1 Sampled Parameters

The Uncertainty Analysis includes a number of Parameters That Are Sampled during the simulation. A new
parameter value is sampled for each sample of the simulation. The sequence of sampled values from the
first sample to the last sample is stored separately for each parameter and may be viewed in a table. Each
parameter sample can be accessed by clicking the Parameter node on the Results tab of the Watershed
Explorer (shown in the following figure).
619 Watershed Explorer showing parameter sample results for an uncertainty analysis

The Parameter Sample Table will open. The table includes one row for each sample of the simulation. The
first column of the table displays the sample number while the second column displays the sampled
parameter value. An example of a parameter sample is shown below.
620 A parameter sample showing the sampled parameter value for each sample of the uncertainty analysis simulation

The Uncertainty Analysis may include one or more locations where output results have been selected.
Special tabular and graphical results may be viewed when Outflow or Pool Elevation is selected. The
Element Outflow is available at all seven element types including Subbasin, Reach, Junction, Source,
Diversion, Reservoir, and Sink. The Pool Elevation is only available at Reservoir elements where the storage
is specified with an elevation-storage or elevation-area curve. Other computed time-series may be selected

and will be stored in the Uncertainty Analysis output HEC-DSS file. These other computed time-series may be
viewed and analyzed using the HEC-DSSVue software.
Two different tables are available when Outflow is selected for a location. The first table displays the
Maximum Outflow for each sample of the Uncertainty Analysis. The second table displays the Outflow
Volume for each sample. The tables can be accessed by expanding the element node on the Results tab of
the Watershed Explorer (shown in the following figure) and clicking on the Result node. The selected table
will open.
621 Watershed Explorer showing outflow results for a selected location in an uncertainty analysis
Each table includes one row for each sample of the simulation. The first column of the table displays the
Sample Number while the second column displays either the Maximum Outflow or the Outflow Volume. An
example of the Outflow Volume Table is shown below.

622 A statistic output showing the outflow volume for each sample of the uncertainty analysis simulation
An Outflow Graph is also available when Outflow is selected for a location. The graph represents a statistical
analysis of the outflow time-series computed for each sample of the simulation. The minimum and
maximum value across all samples is determined for each interval of the simulation time window.
Additionally, the mean and standard deviation are computed for each time interval. The graph presents the
data as the Mean, Mean Plus the Standard Deviation, Mean Minus the Standard Deviation, Maximum, and
Minimum. An example graph is shown below. The graph can be accessed by clicking on the node under the
selected element location.

623 Graph presenting the data as the Mean, Mean Plus the STandard Deviation, Mean Minus the Standard Deviation, Maximum, and
Minimum
A Table and a Graph are available when Pool Elevation is selected for a reservoir location. The table displays
the Maximum Pool Elevation for each sample of the Uncertainty Analysis. The first column of the table
displays the Sample Number while the second column shows the Maximum Pool Elevation. The table can be
accessed by expanding the Reservoir node in the Watershed Explorer and clicking on the Result node in the
same way described above for accessing outflow results. An example of a Maximum Pool Elevation Table is
shown below.

624 A statistic output showing the maximum pool elevation in a reservoir for each sample of the uncertainty analysis simulation
The Pool Elevation Graph represents a statistical analysis of the pool elevation time-series computed for
each sample of the simulation. The analysis is presented as the Mean Pool Elevation, Mean Plus the
Standard Deviation, Mean Minus the Standard Deviation, Maximum, and Minimum for each time interval of
the simulation. The graph can be accessed by clicking on the node under the selected reservoir location. An
example of a Pool Elevation Graph is shown below.

625 Pool elevation result graph for an uncertainty analysis showing the mean and other statistical measures for each time interval

20 Ensemble Simulations
Ensemble modeling is a process whereby multiple base models are created and simulated in a collective
fashion to predict an outcome. In HEC-HMS, base models may currently consist of either a Simulation Run or
a Forecast Alternative. Each base model may include different basin configurations, modeling methods,
parameter sets, initial conditions, and/or boundary conditions. As long as the base models are diverse and
independent, the prediction error of the base models decrease when the ensemble modeling approach is
used. While the ensemble model is composed of multiple models, it acts and performs as a single model.
20.1 Ensemble Analyses

An Ensemble Analysis is a tool used to analyze multiple member models and to aggregate the results. In
HEC-HMS, member models can currently consist of either Simulation Runs or Forecast Alternatives which
can, in turn, be comprised of different boundary condition data, antecedent conditions, paremeterizations,
modeling methods, and/or hydraulic structure configurations. One of the key aims of the Ensemble Analysis
is to reduce uncertainty in the modeled predictions.
For example, several Forecast Alternatives could be created as member models in HEC-HMS, each with a
different precipitation forecast used as boundary condition data. As long as the forecasts are diverse and
largely independent of each other, the prediction error of the member models decreases when using the
ensemble approach. An ensemble approach with respect to precipitation forecasts can more accurately
encompass the "what if" scenarios that are present in each individual member model.
While selecting member models, also referred to as ensemble members, is an important part of carrying out
an Ensemble Analysis, aggregating the results of each member model into a single ensemble result is also
an important step to consider. Currently in HEC-HMS, Ensemble Analyses can aggregate member model
results and output an ensemble time-series of average, minimum, maximum, and +/- one standard deviation.
20.1.1 Creating a New Ensemble Analysis

A new Ensemble Analysis is created using a wizard that helps you navigate the steps to creating a new
the Compute menu and select the Create Compute | Ensemble Analysis command; it is only enabled if at
least two Simulation Runs or Forecast Alternatives already exist in the project. The wizard will open and
begin the process of creating a new Ensemble Analysis. The second way to access the wizard is from the
Ensemble Analysis Manager. Click on the Compute menu and select the Ensemble Analysis
Manager command. The Ensemble Analysis Manager will open and show any analyses that already exist.
Press the New button to access the wizard and begin the process of creating an Ensemble Analysis, as
Ensemble Simulations – 712

626 Ensemble Analysis Manager
The first step of creating an Ensemble Analysis is to provide the name for the new analysis. A default name
is provided for the new analysis; you can use the default or replace it with your own choice. Also, Ensemble
Analyses can contain either Simulation Runs or Forecast Alternatives. Choose one. The option will only exist
if at least two instances are present in the project. In the below figure, only Simulation Run is available
because Forecast Alternatives have not been created in the project. If you change your mind and do not want
to create a new Ensemble Analysis, you can press the Cancel button at the bottom of the wizard or
the X button in the upper right corner of the wizard. The Cancel button can be pressed at any time you are
using the wizard. Press the Next button when you are satisfied with the name you have entered and are ready
to proceed to the next step.
627 Create Ensemble Analysis Step 1

The second step of creating an Ensemble Analysis is to select the ensemble members, also referred to as
base models, to be included in the analysis. To add an ensemble member, click on it in within the left window
and then click the right-arrow to toggle your selection over to the right window. Repeat until you have chosen
your desired ensemble members and then press Next and then Finish to create the Ensemble Analysis.
628 Create Ensemble Analysis Step 2
The last necessary step in setting up an Ensemble Analysis is to select the ensemble member time-series
results that you wish to be aggregated and output to DSS. Navigate to the Watershed Explorer and select
the Compute tab. Expand the Ensemble Analyses node and select the Ensemble Analysis that you just
created. Now select the gear icon, as seen below, to open the output results control dialog. Only the selected
time-series will have results available for analysis after compute.
Ensemble Analysis Results
Ensemble Analyses can be file intensive especially if they are comprised of many ensemble
members. Be sure to select only the elements and time-series that you are interested in. The
selected time-series will be included in the results. Optionally, you can specify the output interval
that you would like to be written to DSS. If not, the Ensemble Analysis simulation interval will
default to the interval of its members.
Ensemble Output Control Dialog
In an Ensemble Analysis, if results are desired at a given element then that element must be
present in all of the ensemble member basin models. Otherwise, the element will not appear in
the Output Control Dialog for selection.

629 Ensemble Analysis Component Editor
630 Ensemble Analysis Output Control Dialog

20.1.2 Copying an Ensemble Analysis

There are two ways to copy an Ensemble Analysis. Both methods for copying an analysis create an exact
duplicate with a different name. Once the copy has been made it is independent of the original, and they do
not interact.
The first way to create a copy is to use the Ensemble Analysis Manager, which is accessed from
the Compute menu. Select the Ensemble Analysis you wish to copy by clicking on it in the list of current
the Copy button on the right side of the window. The Copy Ensemble Analysis window (shown in the
following figure) will open where you can name and describe the copy that will be created. A default name is
provided for the copy; you can use the default or replace it with your own choice. A Description can also be
selected Ensemble Analysis. You cannot press the Copy button if no name is specified. If you change your
mind and do not want to copy the selected Ensemble Analysis, press the Cancel button or the X button in the
upper right to return to the Ensemble Analysis Manager window.
631 Copy Ensemble Analysis
The second way to copy is from the Compute tab of the Watershed Explorer. Move the mouse over
the Ensemble Analysis you wish to copy and press the right mouse button (shown in the following figure). A
The Copy Ensemble Analysis window will open where you can name and describe the copy that will be
process of copying the selected Ensemble Analysis. You cannot press the Copy button if no name is
specified. If you change your mind and do not want to copy the selected Ensemble Analysis, press
the Cancel button or the X button in the upper right of the Copy Ensemble Analysis window to return to the
Watershed Explorer.

632 Copy Ensemble Analysis Right-click Option
20.1.3 Renaming an Ensemble Analysis

There are two ways to rename a Ensemble Analysis. Both methods for renaming an analysis change its
The first way to perform a rename is to use the Ensemble Analysis Manager, which you can access from
the Compute menu. Select the Ensemble Analysis you wish to rename by clicking on it in the list of current
the Rename button on the right side of the window. The Rename Ensemble Analysis window (shown in the
the Rename button to finish the process of renaming the selected Ensemble Analysis. You cannot press
Ensemble Analysis, press the Cancel button or the X button in the upper right of the Rename Ensemble
Analysis window to return to the Ensemble Analysis Manager window.
633 Rename Ensemble Analysis
The second way to rename is from the Compute tab of the Watershed Explorer. Select the Ensemble
Analysis you wish to rename by right-clicking on it in the Watershed Explorer. A context menu is displayed
that contains several choices including Rename. Click the Rename command. The Rename Ensemble
Analysis window will open where you can edit the existing name and/or description. When you are satisfied

with the new name and description, press the Rename button to finish the process of renaming the selected
Ensemble Analysis. You cannot press the Rename button if no name is specified. If you change your mind
and do not want to rename the selected Ensemble Analysis, press the Cancel button or the X button in the
upper right of the Rename Ensemble Analysis window to return to the Watershed Explorer.
634 Rename Ensemble Analysis Right-click Option
20.1.4 Deleting an Ensemble Analysis

There are two ways to delete an Ensemble Analysis. Both methods for deleting an analysis remove it from
The first way to perform a deletion is to use the Ensemble Analysis Manager, which you can access from
the Compute menu. Select the Ensemble Analysis you wish to delete by clicking on it in the list of current
you change your mind and do not want to delete the selected Ensemble Analysis, press the Cancel button or
the X button in the upper right to return to the Ensemble Analysis Manager window.

635 Ensemble Analysis Manager
The second way to delete is from the Compute tab of the Watershed Explorer. Select the Ensemble
analysis. If you change your mind and do not want to delete the selected Ensemble Analysis, press
636 Delete Ensemble Analysis Right-click Option

20.1.5 Adding/Removing Ensemble Members

Ensemble members can be added (or removed) to an existing Ensemble Analysis via the Ensemble
Members tab. Select the Ensemble Analysis in the Compute Tab of the Watershed Explorer to access
the Component Editor for the Ensemble Analysis. Then select the Ensemble Members tab as seen in the
below figure. To insert a new member, click the empty last row and select the desired member. Alternatively,
you can remove a member by right-clicking its row and selecting Delete Row(s).
637 Ensemble Member Table
20.2 Computing Results for an Ensemble Analysis

Results for an Ensemble Analysis are generated by computing it. Changes in all the components used in the
analysis are automatically tracked to determine if the results are current. When the results are no longer
selecting an Ensemble Analysis .
20.2.1 Selecting a Current Ensemble Analysis

There are two ways to select the current Ensemble Analysis. Both methods set the analysis so that it can be
computed and results can be accessed from the Watershed Explorer.
The first way to select the current Ensemble Analysis is from the Toolbar. The compute selection box shows
all of the compute components in the project; Ensemble Analyses will be the last compute type to appear in
the selection box. Each Ensemble Analysis in the selection box includes the prefix Ensemble followed by the
name of the analysis. Click on the toolbar selection box and choose an Ensemble Analysis to become the
current analysis.
The second way to select the current Ensemble Analysis is from the Watershed Explorer, on
the Compute tab. Select the Ensemble Analysis you wish to become the current analysis by clicking on it in
the Watershed Explorer. The Ensemble Analyses are listed alphabetically in the Ensemble Analysis folder.

20.2.2 Computing an Ensemble Analysis

There are three ways to compute the currently selected Ensemble Analysis. All methods automatically
perform parameter checking, and if no errors are generated, proceed to the actual computing of Ensemble
changed so previous analysis results are still applicable. If you wish, you may force all components to be
The first way to compute an Ensemble Analysis is from the Compute menu. Click on the Compute menu and
then select the Compute Ensemble command. The name of the current Ensemble Analysis will be shown in
Ensemble Analysis; you must first select an analysis. A window will automatically open that shows the
The second way to compute an Ensemble Analysis is from the Watershed Explorer, on the Compute tab.
Select the Ensemble Analysis you wish to compute by clicking on it in the Watershed Explorer with the right
menu command.
The third way to compute an Ensemble Analysis is from the Toolbar. The compute button is enabled
whenever there is a current analysis that can be computed. If the button is not available or shows a different
type of compute, you must first select a Ensemble Analysis . Press the button to compute the current
Ensemble Analysis . The progress window will automatically open. If you wish to force all components to be

Multiple Ensemble Analyses can be computed in rapid succession. Each analysis included for simulation is
user begin with selecting the Ensemble Analysis, checking parameters for the analysis, and finally computing
the simulation. This sequence is repeated in rapid succession for each Ensemble Analysis in the selected
set. Appropriate feedback is provided through a progress bar.
The multiple Ensemble Analyses must exist before they can be selected for a multiple compute. Select
the Multiple Compute command on the Compute menu. A manager is used to select Ensemble Analysis (see
figure below). Make selections in the list and then press the Compute button to begin computing the
selected analyses. A separate progress bar will be displayed for each Ensemble Analysis as it is computed.
The progress bar may disappear automatically at the conclusion of an Ensemble Analysis depending on the
settings.

638 Ensemble Analysis Multiple Compute
20.3 Viewing Results for an Ensemble Analysis

A variety of Graphical and Tabular results are available after an Ensemble Analysis is computed. All results
from an Ensemble Analysis are accessed via the Results tab of the Watershed Explorer. The same results
are also available for the current analysis, so long as no data used in the analysis has changed. The program
tracks all of the data in the Ensemble Analysis including its ensemble members (Simulation Runs or
Forecast Alternatives) and each of their Basin Models and Meteorologic Models. If any of the data has
changed, you will need to recompute the Ensemble Analysis to update and refresh the results.
Once a result is open for viewing it will remain open until it is closed by the user. It is possible that data or
model information used by the analysis that produced the result could change while the result is open for
viewing. In this case, the open result will immediately show an indication that data has changed and
the Ensemble Analysis needs to be recomputed. After the Ensemble Analysis is recomputed the open results
are automatically updated with the new results and the indication is updated with the data and time of the
most recent compute.
Ensemble Analysis Results
The results available for a computed Ensemble Analysis are based on the user's selections from
the output control dialog accessed via the Compute tab of the Watershed Explorer as seen
below.

639 Ensemble Analysis Component Editor
640 Ensemble Analysis Output Control Dialog
20.3.1 Graphical Results

Below is an example of an Outflow plot from a junction element present in each of the ensemble member
base models. The traces of the ensemble member outflow results are shown in colored lines for reference.
The dashed black lines are aggregated results computed from the ensemble analysis. The aggregated

results include outflow mean, mean plus one standard deviation, mean minus one standard deviation,
maximum, and minimum.
641 Ensemble Analysis Outflow Plot
20.3.2 Tabular Results

Tabular results from an ensemble analysis are also included and will depend on the time-series selected by
the user in the output control dialog prior to compute. Below is an example of a Maximum Outflow table
from a junction element present in each of the ensemble member base models. The maximum outflows
from each of the ensemble member base models are shown for quick comparison. In this example, most of
the ensemble members show a similar computed maximum outflow value. The exception is ensemble
member 4 which shows a much higher maximum outflow value.

642 Ensemble Analysis Outflow Table

21 Erosion and Sediment Transport

When water flows over the land surface and through stream channels, it affects the landscape in significant
ways. Shallow surface flow erodes soil and carries the material overland to headwater streams. Steep
headwater streams have high flow velocity that leads to stream bed erosion. Eroded surface soil and bed
material can be carried by the stream flow to lower reaches of the watershed. Sediment is often deposited in
the lower reaches where the flow velocity slows. Reservoirs in the watershed will trap some or most of the
sediment that enters with the inflow. Diversion structures can also affect the movements of sediment
through the watershed. Erosion and Sediment Transport lead to a number of problems best evaluated in
conjunction with hydrologic simulation.
21.1 Watershed Sediment Properties

Sediment method is optional component in the Basin Model. By default, the component features are
deactivated. Data entry tools for sediment are not visible in the program interface, and no sediment results
are computed during a simulation. The sediment features become accessible when they are activated for the
Basin Model. Activate the features on the Component Editor for the Basin Model (shown in the following
figure). Access the Component Editor by clicking the Basin Model on the Components tab of the Watershed
Explorer. Change Sediment to Yes to activate the sediment features. A Sediment tab will appear to the right
of the Basin Model Component Editor. You must enter values in the parameter data at each element
(subbasin, reach, reservoir, source, and diversion) in the Basin Model. When Sediment is set to No, all
parameter data for the sediment methods will be deleted from the Basin Model and its elements. Once the
sediment components have been deactivated, it is not possible to recover the deleted settings or parameter
values.
643 Activating the Erosion and Sediment Transport features in the Basin Model
Erosion and Sediment Transport modeling requires a number of properties to be specified. These global
properties are applied to all elements in the Basin Model. The properties are presented on a
separate Component Editor from the Basin Model editor. The Sediment editor is always shown next to the
Basin Model editor (shown in the following figure).
Erosion and Sediment Transport – 726

644 Selecting important Sediment Methods and entering parameter data that will be applied to all elements within the Basin Model
The Transport Potential59 specifies which method to use to calculate the stream flow sediment carrying
capacity for non-cohesive sediments. Different methods have been proposed for calculating the transport
potential. Each method has been developed for a particular sediment grain-size distribution and
environmental condition. The selected transport potential method will be used at all reaches within the Basin
Model. The available choices are shown in the table below.
A cohesive transport potential method can also be selected. When selected, transport of cohesive sediment
is computed in addition to the non-cohesive sediment.
Method Type Method Reference
Ackers-White NC SP Ackers and White, 1973
Engelund-Hansen NC SP Engelund and Hansen, 1967
Laursen-Copeland NC ES Laursen, 1958; Copeland and

Thomas, 1989
Meyer-Peter Muller NC ES Meyer-Peter and Müller, 1948
Toffaleti NC RE Toffaleti, 1968
Wilcock NC ES Wilcock and Crowe, 2003
59 https://www.hec.usace.army.mil/confluence/rasdocs/rassed1d/1d-sediment-transport-user-s-manual/entering-and-editing-sediment-
data/initial-conditions-and-transport-parameters/transport-function

Yang NC SP Yang, 1984
Krone Parthenaides CO ̶ Krone, 1962; Parthenaides, 1962
Sediment Delivery Ratio NC/CO ̶ Pak and Lee (2012)
49 Transport potential functions for calculating the amount of sediment that can be carried by the stream flow. Type is non-cohesive
(NC) or cohesive (CO). Method is excess shear (ES), stream power (SP), or regression (RE).
The Specific Gravity must be specified and a default value of 2.65 is provided. The default value should be
changed if another value is more appropriate for the watershed.
Sediment unit weights or densities are used to convert deposited or eroded masses into volumes. This is one
of the only parameters that is different for SI and US customary units. US customary is defined in terms of
unit weights (lb/ft3) while SI is defined in terms of density (kg/m3). HEC-HMS converts between density and
unit weight internally.
The Unit Weight/Density of Clay must be specified as appropriate for the selected unit system. The default
density is 481 kg/m3 (metric units) while the default specific weight is 30 lb/ft3 (U.S. Customary) . The same
density is used for all size subclasses of clay. The default value should be changed if another value is more
appropriate for the watershed.
The Unit Weight/Density of Silt must be specified as appropriate for the selected unit system. The default
density is 1,041 kg/m3 while the default specific weight is 65 lb/ft3. The same density is used for all size
subclasses of silt. The default value should be changed if another value is more appropriate for the
watershed.
The Unit Weight/Density of Sand must be specified as appropriate for the selected unit system. The unit
weight specified for the Sand will be applied to Gravel, Cobble, and Boulder. The same density is used for all
size subclasses from very fine sand to large boulders. The default dry density is 1,490 kg/m3 while the
default dry specific weight is 93 lb/ft3. The default value should be changed if another value is more
appropriate for the watershed.
Some of the Transport Potential Methods require calculating the Fall Velocity60. Fall velocity is also used in
several of the Sediment Settling Methods for the reservoir element. All reaches and reservoirs that require
the calculation of a fall velocity will use the method selected in the sediment properties. The available
methods for calculating fall velocity include Report 12 (Interagency Committee, 1957), Rubey (1933),
Toffaleti (1968), and Van Rijn (1993). The default selection is Rubey.
The Sediment Delivery Ratio Transport Potential Method require a ratio of each grain class (Clay, Silt, Sand,
and Gravel when Grade Scale is selected as Clay Silt Sand Gravel and Clay, Silt, Sand, and Gravel, Cobble,
and Boulder when Grade Scale is selected as AGU 20). A Ratio number is greater than 1 represents an
erosional situation, a Ratio number less than 1 represents a depositional situation, and a Ratio number equal
to 1 is an equilibrium situation.
60 https://www.hec.usace.army.mil/confluence/rasdocs/rassed1d/1d-sediment-transport-technical-reference-manual/continuity-limiters/
temporal-deposition-limiter/fall-velocity

Two different Grade Scale systems are available. The selected system will determine the number of grain
sizes used for calculating Erosion and Sediment Transport throughout the Basin Model. Erosion, deposition,
settling velocities, and transport processes are computed separately for each size. The Clay Silt Sand Gravel
System only recognizes four broad size classifications. The AGU 20 recognizes 20 different size
classifications, generally breaking each of the four broad size classifications into sub-classifications.
It should be noted that the gradation scale option needs to be considered once the gradation curve range is
known. The results for the sediment load/volume are calculated independently of the gradation curve,
however, the chosen gradation scale may limit the reported sediment load/volume for that subbasin, as
illustrated in the following table.
Grade Scale
Gradation Curve Range Clay Silt Sand Gravel (0.002 mm – 64 mm) AGU 20 (0.002 mm –
2048 mm)
Clay (0.002mm) to Gravel Covers all grain classes – no sediment load/ Covers all grain classes
(64 mm) volume limitations – no sediment load/
volume limitations
Clay (0.002mm) to Large Underestimates sediment load/volume Covers all grain classes
Boulder (2048 mm) (excludes volume associated with all grain – no sediment load/
classes > 64mm) – reported sediment load/ volume limitations
volume is reduced by the percent of the grain
sizes larger 64 mm

21.2 Subbasin Sediment

A Subbasin Element represents a catchment where precipitation falls and causes surface runoff. Erosion
within the catchment will result from a combination of several different physical processes including post-
fire conditions. Rain drops cause erosion when they impact the ground surface and break apart the top layer
of the soil, dislodging soil particles to move with the overland flow. Overland flow also imparts an erosive
energy to the ground surface that may further break apart the top soil layer. As the overland flow rate
increases, the flow becomes concentrated in rills which focuses erosive energy and further erodes the
surface. Total erosion is closely linked to precipitation rate, land surface slope, and condition of the surface.
In some cases, soil eroded high in the catchment may deposit before reaching the outlet of the subbasin.
Certain simulation features are common to all of the Surface Erosion Methods available for the subbasin
element. Each Erosion Method computes the total sediment load transported out of the subbasin during a
storm. This calculation process is repeated for each storm during the simulation time window. The sediment
load must be distributed into a time-series of sediment discharge from the subbasin. The distribution of
sediment is based on the computed hydrograph and the power function approach of Haan et al. (1994). The
power function is given by:
where ct is the sediment concentration at time t, ki is the proportion of the load for the current event i to the
total annual load, Qt is the subbasin discharge (flowrate) at time t, and a is an exponent entered by the user.
Also common to all of the Surface Erosion Methods is the approach to Grain Size Distribution. All of the
methods first compute the bulk Sediment Discharge which includes all grain sizes. A Gradation Curve
specifies the proportion of the total sediment discharge that should be apportioned to each grain size class
or subclass. A gradation curve must be defined by the user and selected at each subbasin. A different
gradation curve can be used at each subbasin to represent differences in the erosion, deposition, and
resuspension processes within each subbasin. The combination of these processes is often represented by
an Enrichment Ratio.
21.2.1 Selecting an Erosion Method

The Erosion Method for a subbasin is selected on the Component Editor for the subbasin element (shown in
the following figure). Access the Component Editor by clicking the Subbasin Element icon on the
element icon in the Basin Map, if the map is currently open. You can select an Erosion Method from the list
of seven available choices. If you choose the None method, the subbasin will not compute any erosion and
all sediment discharges from the element will be zero. Use the selection list to choose the method you wish
to use. Each subbasin may use a different method or several subbasins may use the same method.

645 Selecting the Surface Erosion Method for a subbasin element
The parameters for each Erosion Method are presented on a separate Component Editor from the Subbasin
Element editor. The Erosion editor is always shown next to the Baseflow editor. The information shown on
the Erosion editor will depend on which method is currently selected.
21.2.2 Build-up Wash-off

The Build-Up Wash-Off Erosion Method is designed for urban environments. In these environments,
sediment accumulates in street curbs due to wind deposit and erosion from pervious areas adjacent to the
curbs. The sediment accumulates during dry periods between storms. During a storm, the accumulated
sediment is flushed from the street curbs by stormwater runoff. The method may optionally include street
sweeping operations designed to mechanically remove accumulated sediment. A typical example of source
data for parameterizing the method is Breault et al. (2005) though data sources should always be recognized
as highly local. The Component Editor is shown below.

646 Build-Up Wash-Off Erosion Method Editor at a subbasin element
The Initial Time is an initial condition for the method. It specifies the number of days since the last sweeping
operation when the simulation begins.
The Half Time specifies the number of days required for half of the maximum solids to accumulate in the
street curb under continuously dry conditions.
The Maximum Solids Amount is the limit to the accumulated sediment in the street curb under continuously
dry conditions. Sediment will not exceed this amount even if there is no precipitation for an extended period
of time.
This Erosion Method includes four parameters to describe the street sweeping operations within the
subbasin. The Density specifies the total length of street curb whether or not the curb is subject to sweeping
operations. The density should consider whether the street has curbs on one side or both sides of the street.
The Sweeping Percentage specifies the percentage of the curb length subject to sweeping. The percentage
should account for the possible presence of parked cars which result is missed curb. The Efficiency
Percentage specifies the efficiency of the sweeping equipment at removing accumulated sediment. Finally,
the Interval specifies the number of days between scheduled sweeping operations.
The Wash-Off Coefficient determines how quickly the accumulated sediment is removed from the street
curb during a storm event.
The Exponent is used to distribute the sediment load into a time-series sedigraph. A small value flattens the
sedigraph compared to the hydrograph. A large value heightens the sedigraph compared to the hydrograph.
The Gradation Curve defines the distribution of the total sediment load into grain size classes and
subclasses. The gradation curve is defined as a diameter-percentage function in the Paired Data Manager.
The current functions are shown in the selection list. If there are many different functions available, you may
wish to choose a function from the selector accessed with the paired data button next to the selection list.
The selector displays the description for each function, making it easier to select the correct one.

21.2.3 Modified USLE

The Modified USLE Method (Williams, 1975) was adapted from the original Universal Soil Loss Equation.
The original equation was based on precipitation intensity, and consequently could not differentiate between
storms with low or high infiltration. With high infiltration, there is little surface runoff and little accompanying
surface erosion. Conversely, low infiltration events have relatively more surface runoff and consequently
more surface erosion. The modifications to the original USLE equation changed the formulation to calculate
erosion from surface runoff instead of precipitation. The other components of the original formulation
remained the same. The method works best in agricultural environments where it was developed. However,
some users have adapted it to construction and urban environments. The Component Editor is shown in the
following figure.
647 Modified USLE Erosion Method Editor at a subbasin element
The Erodibility Factor describes the difficulty of eroding the soil. The factor is a function of the soil texture,
structure, organic matter content, and permeability. Typical values range from 0.05 for unconsolidated loamy
sand to 0.75 for silty and clayey loam soils.
The Topographic Factor describes the susceptibility to erosion due to length and slope. It is based on the
observation that long slopes have more erosion than short slopes, and steep slopes have more erosion than
flat slopes. Typical values range from 0.1 for short and flat slopes to 10 for long or steep slopes.
The Cover Factor describes the influence of plant cover on surface erosion. Bare ground is the most
susceptible to erosion while a thick vegetation cover significantly reduces erosion. Typical values range from
1.0 for bare ground, to 0.1 for fully mulched or covered soils, to as small as 0.0001 for forest soils with a
well-developed soil O horizon under a dense tree canopy.
The Practice Factor describes the effect of specific soil conservation practices, sometimes called best
management practices. Agricultural practices could include strip cropping, terracing, or contouring.
Construction and urban practices could include silt fences, hydro seeding, and settling basins. It is difficult to
establish general ranges for these practices as they are usually highly specific.

Only some precipitation events will cause surface erosion. The Threshold can be used to set the lower limit
for runoff events that cause erosion. Events with a peak flow less than the threshold will have no erosion or
sediment yield.
wish to choose a function from the selector accessed with the Paired Data button next to the selection list.
21.2.4 LA Debris Method EQ1

The Los Angeles District Debris Method - Equation 1 (Gatwood et al., 2000) was developed from statistical
analysis of data from watersheds with an area from 0.1 mi2 to 3.0 mi2. The equation was developed based
on 349 observations from 80 watersheds located in Southern California. All factors in the equation were
significant at the 0.99 level of confidence. The LA Debris Method EQ 1 works best in arid or semi arid regions
of Southern California where it was developed. The Component Editor is shown in the next two figures.
648 LA Debris Method EQ 1 Editor with User-Specified Fire Factor Method

649 LA Debris Method EQ 1 Editor with Pak & Lee Fire Factor Method
The Adjustment-Transposition (A-T) Factor describes the difference in geomorphology between the subject
watershed and the original watershed from which the regression equation was generated. This factor
considers the surficial geology, soils, hillslope, and channel morphology. Watersheds of the San Gabriel
Mountains from which the regression equation was developed have an A-T factor of 1.0. Watersheds in
areas with higher debris potential would have an A-T factor greater than 1.0, while areas of lesser debris yield
capacity would have an A-T factor less than 1.0.
The Relief Ratio describes the susceptibility to debris yield due to length and slope. It is based on the
difference in elevation between the highest point in the watershed (measured at the end of the longest
stream) and the lowest point (at the debris collection site) and dividing the difference between these two
locations by the maximum stream length as measured along the longest stream.
The Fire Factor Method has two options including the User-Specified Fire Factor for event simulation and
the Pak & Lee Fire Factor for continuous simulation. The fire factor describes the occurrence of wildfire on
surface erosion. Information about the User-Specified Fire Factor is presented in Figure 2 (page 17) of the
Los Angeles District Debris Method (Gatwood et al., 2000). Typical values range from 6.5 for within 1-year
since 100% burn to 3.0 for more than 10-years since 100% burn. In order to apply the Pak & Lee Fire Factor
method, two additional input parameters are required. The first one is the date which is the Finish Date of the
Most Recent Wildfire and the second one is the Burn Percentage of Subbasin.
The Flow Rate Threshold can be used to divide storm events for the continuous simulation by setting the
lower limit for direct runoff flow rate. A debris flow event starts when the direct runoff is above the flow rate
threshold. The event ends when direct runoff falls below the threshold.

21.2.5 LA Debris Method EQ 2-5

The Los Angeles District Debris Method - Equation 2 Through 5 (Gatwood et al., 2000) was developed from
statistical analysis of data from watersheds with an area from 3.0 to 200.0 mi2. This method may also be
used for drainage areas less than 3 mi2. The Los Angeles District Debris Method EQ 2-5 works best in arid or
semi arid regions of Southern California where it was developed. The Component Editor is shown in the next
two figures.
650 LA Debris Method EQ 2-5 Editor with User-Specified Fire Factor Method
651 LA Debris Method EQ 2-5 Editor with Pak & Lee Fire Factor Method
watershed and the original watershed from which the regression equation was generated. This factor
considers the surficial geology, soils, hillslope, and channel morphology. Watersheds of the San Gabriel

surface erosion. Information about the User-Specified Fire Factor is presented in Figure 2 (page 17) of the
since 100% burn to 3.0 for more than 10-years since 100% burn. In order to apply the Pak & Lee Fire Factor
method, two additional input parameters are required. The first one is the date which is the Finish Date of the
Most Recent Wildfire and the second one is the Burn Percentage of Subbasin.
21.2.6 Multi-Sequence Debris Prediction Method (MSDPM)

The Multi-Sequence Debris Prediction Method (Pak and Lee, 2008) was developed based on debris clean
out data (1938 to 2002) obtained for 80 debris basins located in Southern California. The method can be
used for the continuous debris yield simulation for relatively small watersheds from 0.1 mi2 to 3.0 mi2 in
area. MSDPM is based on three main physical processes: the critical condition to entrained sediment, the
transport capacity to move sediment toward the concentration point (debris basin), and the antecedent
precipitation condition coupled with subsequent rainfall events. MSDPM works best in arid or semi arid
regions of Southern California where it was developed. The Component Editor is shown in the next two
figures.

652 Multi-Sequence Debris Prediction Method Editor with User-Specified Fire Factor Method at a subbasin element
653 Multi-Sequence Debris Prediction Method Editor with Pak & Lee Fire Factor Method at a subbasin element
watershed and the original watersheds from which the regression equations were generated. This factor
considers the surficial geology, soils, and hillslope and channel morphology. Watersheds of the San Gabriel

The Threshold Maximum 1-hr Rainfall Intensity (TMRI) describes the critical condition for entrainment of
sediment. Not all rainfall events can generate sediment because some minimum energy is needed to entrain
sediment particles. Therefore, rainfall events are screened by TMRI as a calibration factor to select those
events where effective rainfall exceeds the critical value to entrain sediment particles.
The Total Minimum Rainfall Amount (TMRA) describes the transport capacity to move sediment to the
concentration point. Not all rainfall events can lead to significant sediment transport. Once sediment has
become entrained, a certain amount of additional energy is needed to move the sediment to the
concentration point. Therefore, rainfall events are screened again by TMRA as a calibration factor to select
effective rainfall events that can provide the required energy.
surface erosion. The information for the User-Specified Fire Factor is presented in Figure 2 (page 17) of the
since 100% burn to 3.0 for more than 10-years since 100% burn. In order to apply Pak & Lee Fire Factor
method, two additional pieces of information are required. The first one is the Finish Date of the Most
Recent Wildfire and the second one is the Burn Percentage of Subbasin.
21.2.7 USGS Long-Term Debris Model

The USGS Long-Term Debris Model (Gartner et al., 2014) was developed from a database of 344 volumes of
sediment deposited by debris flows and sediment-laden floods with no time limit since the most recent fire.
The sediment volume dataset represents a broad sample of conditions found in Ventura, Los Angeles and
San Bernardino Counties, California. The Component Editor for this method is shown below.

654 USGS Long-Term Debris Model Editor at a subbasin element
The Relief describes the amount of energy available for transporting material down slope. It is the maximum
amount of relief (maximum elevation minus minimum elevation) found within the watershed.
The Date is the finish date of the most recent wildfire.
The Burn Area is the total area of watershed burned by the most recent wildfire.
21.2.8 USGS Emergency Assessment Debris Model

The USGS Emergency Assessment Debris Model (Gartner et al., 2014) was developed from a subset of the
complete dataset consisting of 92 volumes of sediment deposited by debris flows within two years of a fire.
The sediment volume dataset represents a broad sample of conditions found in Ventura, Los Angeles and
San Bernardino Counties, California. The Component Editor for this method is shown in the following figure.

655 USGS Emergency Assessment Debris Model Editor at a subbasin element
The Relief describes the amount of energy available for transporting material down slope. It is the maximum
amount of relief (maximum elevation minus minimum elevation) found within the watershed.
The Burn Area is the watershed area burned at moderate and high severity.
wish to choose a function from the selector accessed with the Paired Data button next to the selection list.
21.2.9 2D Sediment Transport

The 2D Sediment Transport was developed to work within the subgrid framework of the 2D transform model,
and computes subgrid erosion and deposition rates, bed change, bed sorting, and bed layering. Sediment
transport is computed with a non-equilibrium total-load formulation. The total-load transport equation is
solved with implicit Finite-Volume methods on the same unstructured polygonal mesh as the 2D flow solver.
The Component Editor for the 2D sediment transport method is shown below.

656 2D Sediment Transport editor at a subbasin element
The Total Load Scaling Factor allows the user to scale or calibrate different transport formula and is applied
the same to all the transport functions. The recommended range for total load scaling factor is 0.2 to 5.0.
The Critical Mobility Scaling Factor is multiplied by the threshold for incipient motion (albeit a critical shear,
reference shear, or Shield number). Therefore, a mobility factor larger than 1 reduces the mobility and a
mobility factor smaller than 1 increases mobility. The recommended range for the Critical Mobility Scaling
Factor is 0.5 to 2.0.
The Sheet & Splash Erodibility Coefficient is set to a single value in HEC-HMS. Splash and sheet flow
erosion occurs in the "hydraulically dry" portion of each computational cell which is above the water surface
elevation but has precipitation and surface runoff. The sheet and splash erosion is computed with a modified
form of the rangeland erosion formula developed by Wei et al. (2009). The 2D sediment transport model has
the option to use the Wei et al. (2009). The units of the erodibility coefficient are kg∙m-3.644∙s0.644. Wei et al.
(2009) reported values for the sheet and splash erosion coefficient between 1124 and 2555 kg
∙m-3.644∙s0.644 for 3 grassland rangeland plots in Arizona (all variables in the International System of Units).
However, its value can vary by orders of magnitude for different soil types and cover characteristics.
The Sediment Total Roughness Factor is user-specified with Manning's Roughness Coefficient. The
sediment total roughness factor may be separated into roughness due to (1) grains, (2) sediment transport,
and (3) bedform. The grain-related roughness is the skin roughness caused by the sediment grains on the
bed. It is necessary for many of the sediment transport formulas. The sediment transport roughness is a
friction loss caused by the moving particles near the bed. The transport roughness is usually small
compared to the other components and is ignored here. The bedform roughness is the form roughness and
can have a large range of values. The sediment total roughness factor is specified in HEC-HMS with the
Manning's roughness coefficient. It is important to note that the bed roughness is assumed constant in time
and does not change according to bed composition and bedforms. This is a common engineering approach
which can be justified by the lack of data to initialize the bed composition and the large error in estimating
the bed composition evolution and bedforms. In addition, using a constant bottom roughness simplifies the
model calibration. The sediment total roughness factor used for hydrodynamics may not be the same as that
which is used for the sediment transport calculations because the hydrodynamic roughness may include
vegetation and other sources of drag which do not represent bottom roughness. The recommended range
for the sediment total roughness factor is 0.5 to 1.0.
The Adaptation Coefficient is applied only for the hydraulic flow erosion (non-cohesive sediment) and is a
function of the total-load adaptation length. There are several options to calculate the total-load adaptation
length. The simplest option is to utilize a constant adaptation length and calibrate the parameter using field
measurements. Experience has shown that for most field applications, this approach is sufficient. However,
several other methods are available with varying degrees of complexity. The total-load adaptation length may

also be determined. The advection coefficient takes into account several processes which affect the velocity
and direction of the sediment transport including the vertically non-uniform distribution of the horizontal
current velocity and sediment concentration profiles and bed-slope effects. The recommended range for the
adaptation coefficient is 0.5 to 2.0.
The Gradation Curve defines the grain size distribution of the bed. Gradation curves are defined as diameter-
percent finer curves in the Paired Data Manager. A single gradation curve for the whole subbasin is selected
from the drop-down menu with the list of available gradation curves.
21.2.10 Global Editing

Global editors can be used to quickly edit information for all subbasins and reaches instead of editing
individual element Component Editors. Erosion Methods can be edited globally from the Parameters |
Erosion menu.
The following image shows the global editor for a Basin Model where all subbasins are set to use the LA
Debris Method Equation 1.
657 Global Editors for subbasin sediments
21.3 Reach Sediment

Sediment processes within a reach are directly linked to the stream flow and its capacity to carry eroded soil.
The transport capacity of the stream can be calculated from flow and sediment properties. If the stream can
transport more sediment than is contained in the inflow, additional sediment will be eroded from the stream
bed and entrained in the flow. However, if the flow in the reach cannot transport the sediment, entrained
sediment will settle and deposit in the reach bed.
The sediment transport capacity is calculated based off a transport potential method. Any Basin Model that
uses Muskingum-Cunge or Kinematic Wave routing methods will need to carefully choose an index flow or

an index celerity for each reach element. The index flow and celerity is used to subdivide the reach into an
equal number of length segments (dx) as expressed in the courant condition. The Volume Ratio and Linear
Reservoir sediment routing methods are very sensitive with “dx” and may drastically change computed
sediment results.
Deposition of sediment from the water column to the stream bed requires time. The Fall Velocity for a grain
size class describes how much time is expected for sediment to settle from the water column to the stream
bed. The settling velocity is calculated and multiplied by the time interval to determine the settling distance in
one time interval. This settling distance is then compared to the flow depth calculated during flow routing in
order to determine the fraction of calculated deposition which is actually permitted during a time interval.
The approach here is similar to the one used in HEC-RAS.
The erosion of sediment from the stream bed and entraining into the stream flow requires time. Limits to
erosion have been observed. An empirical rule is used by selecting a characteristic flow length necessary for
erosion. Erosion is limited when the length of the reach divided by the flow depth is less than 30. This
empirical rule is similar to one used in HEC-RAS61.
The reach bed is represented by a two-layer model. The upper layer represents the top of the stream bed
which actively interacts with the flow field. This layer responds relatively quickly to changes to the flow rate.
The lower layer is linked to the upper layer with a simple bed mixing algorithm. The lower layer represents the
underlying substrate of the reach. Long-term processes that lead to a reach being either a sediment sink or
sediment source within the watershed are represented through the lower layer. The two-layer model is also
capable of representing an "armoring" condition, which reduces the rate of erosion as the upper layer
coarsens.
The cross section shape of the channel is assumed fixed. Changes to the reach from sediment and flow
dynamics are not represented during the simulation. A characteristic width and depth of the sediment bed is
used to represent the two-layer model.
21.3.1 Selecting a Sediment Method

The Sediment Method for a reach is selected on the Component Editor for the Reach Element (shown in the
following figure). Access the Component Editor by clicking the Reach Element icon on the Components tab
of the Watershed Explorer. You can also access the Component Editor by clicking on the element icon in the
Basin Map. You can select a Sediment Method from the list of five available choices. If you choose None, the
reach will not compute any sediment and all sediment discharges from the element will be zero. Use the
selection list to choose the method you wish to use. Each reach may use a different method or several
reaches may use the same method.
61 https://www.hec.usace.army.mil/confluence/rasdocs/rassed1d/1d-sediment-transport-technical-reference-manual/continuity-limiters/
temporal-erosion-limiter

The parameters for each Sediment Method are shown on the Sediment tab of the Component Editor. The
Sediment editor is always shown next to the Routing editor. The information shown on the Sediment editor
will depend on which method is currently selected.
21.3.2 Fisher's Dispersion

The Fisher's Dispersion Method is based on an analysis of advection and diffusion of sediment within a
reach (Fisher et al., 1979). This is the most detailed of the sediment routing methods and requires more data
than the other available methods. Advection and diffusion, represented as Travel and Dispersion parameters,
need to be specified for each grain size class. This permits large-grained sediments to move slower than
fine-grained sediments. For each time interval, sediment from the upstream elements are added to the
sediment already in the reach. After erosion or deposition is calculated, the remaining available sediment is
translated in the reach by a Travel Time and attenuated through a diffusion process. The advection and
diffusion of sediment are linked to the velocity of water in the reach which is calculated during the flow
routing. The Component Editor is shown in the following figure.

658 Fisher's Dispersion Sediment Method Editor at a reach element
Dispersion Coefficient must be specified for each grain class (clay, silt, sand, gravel). The Dispersion
coefficient indicates the diffusion of the particles during transit through the reach and is dependent on the
channel geometry. The dispersion coefficient can vary over several orders of magnitude and often must be
adjusted during calibration. Some guidance is available for estimating the dispersion coefficient from
Kashefipour and Falconer (2002). The Travel Time must also be specified for each grain class and is often
close to the travel time for water in the reach. When the AGU 20 grain size classification is used, the same
dispersion and retention values are used for all subclasses of grain classes.
The Initial Gradation Curve defines the distribution of the bed sediment by grain size at the beginning of the
simulation. The same curve is used in both the upper and lower layers of the two-layer bed model. The
gradation curve is defined as a Diameter-Percentage function in the Paired Data Manager.
The Erosion Limit is optional. If the erosion limit is selected as None, erosion is limited only by the transport
capacity of the flow. When the Erosion Limit is selected as Yes, erosion is reduced when the ratio of the
reach length to flow depth is less than 30. Erosion limits are usually encountered in very short reaches.
The Deposition Limit is optional. When the deposition limit is deactivated, sediment in excess of the
transport capacity is deposited completely. When the Deposition Limit is selected to Yes, sediment is limited
by the flow depth calculated during flow routing and the fall velocity of each grain size. The fall velocity is
computed using the method selected within the Basin Model properties. Selecting a Deposition Limit
requires users to select a Temperature Method. Users may specify a fixed water temperature (Average) or
select a temperature time-series gage (Time Series). Temperature gages must be created in the Time-Series
Data Manager before they can be used.
The Bed Width must be specified. The width should be representative of the entire reach. The width is used
to compute the volume of the upper and lower layers of the bed model. The Bed Depth must also be

specified. The depth should be representative of the reach depth for both the upper and lower layers,
representing the maximum depth of mixing over very long time periods.
The Active Layer Factor is used to calculate the depth of the upper layer of the bed model. At each time
interval, the upper layer depth is computed as the d90 of the sediment in the upper layer, multiplied by the
active layer factor.
21.3.3 Linear Reservoir

The Linear Reservoir Method uses a simple linear reservoir to route each grain size through the reach. For
each time interval, sediment is calculated from the upstream sediment and local erosion or deposition. The
available sediment in each grain size class is routed through a linear reservoir independently of the
hydrologic routing of the flow. This allows sediment of different grain sizes to move at different speeds
through the reach. Calibration with observed data is recommended to assign parameter values.
The Retention parameter is equivalent to the storage coefficient and is used to route the sediment through
the reach. The routing is performed separately for clay, silt, sand, and gravel. When the AGU 20 grain size
classification is used, the same retention is used for all subclasses of each class. The value of the retention
parameter is analogous to the median length of time for each sediment class to move through the reach. The
Retention value may change for each sediment size class but is often close to the travel time for water in the
reach.
659 Linear Reservoir Sediment Method Editor at a reach element

21.3.4 Muskingum
The Muskingum Method uses a simple conservation of mass approach to route sediment/debris through the
stream reach. For each time interval, available sediment is calculated from the upstream sediment and local
erosion or deposition. The available sediment in each grain size class is routed using the Muskingum routing
parameters, Attenuation Coefficient and Travel Time. This allows sediment of different grain sizes to move
at different speeds and as well as approximate attenuation through the reach. Calibration with observed data
is recommended to assign parameter values. The Component Editor is shown in the following figure.

The Attenuation Coefficient of each grain class is the weighting between inflow and outflow influence; it
ranges from 0.0 up to 0.5. In practical application, a value of 0.0 results in maximum attenuation and 0.5
results in no attenuation. Most stream reaches require an intermediate value found through calibration.
The Travel: (HR) of each grain class is essentially the travel time through the reach. It can be estimated from
knowledge of the cross section properties and flow properties. It may be a calibration parameter in some
cases.

21.3.5 Uniform Equilibrium

The Uniform Equilibrium Method assumes the sediment is translated instantaneously through the reach. It is
the simplest method because it does not compute any temporal lag for the sediment passing through the
reach. Sediment enters the reach from upstream elements. The transport capacity for each grain size is
calculated to determine whether the stream is depositing or eroding. The available sediment is computed
subject to the limitations on deposition and erosion. The remaining sediment is then routed regardless of the
velocity. The Component Editor for the Uniform Equilibrium method is shown in the following figure.
660 Uniform Equilibrium Sediment Method Editor at a reach element

21.3.6 Volume Ratio

The Volume Ratio Method directly pairs the sediment transport to the streamflow. For each time interval,
sediment from the upstream elements is added to the sediment already in the reach. Deposition or erosion is
calculated for each grain size to determine the available sediment for routing. The proportion of available
sediment that leaves the reach in each time interval is assumed equal to the proportion of stream flow that
leaves the reach during that same interval. This means that the all grain sizes are transported through the
reach at the same rate, even though erosion and deposition are determined separately for each grain size.
This assumption essentially limits the advection velocity of the sediment to the bulk water velocity.
Therefore, this method is a higher fidelity option than the Uniform Equilibrium Method (without requiring
much more data) but less precise than the other available methods which require substantially more data.
This method is similar to the approach used in the Soil and Water Assessment Tool Model (Gassman, 2007).
661 Volume Ration Sediment Method Editor at a reach element

21.4 Reservoir Sediment

A reservoir provides an ideal environment for removing sediment from water. Quiescent water, or completely
still water, has no capacity to suspend sediment because the horizontal velocity of the water is zero.
Therefore, given enough time all sediment in the water column will settle to the bottom of the reservoir. Time
is important because sediment does not settle instantaneously. There is a very small amount of friction
between each sediment grain and the water molecules that surround it. This friction creates a turbulent
environment that slows the descent of each sediment grain. The velocity at which a particular grain will
settle is due to its size and to a lesser extent, the density and shape of the grain. Large grains will settle very
quickly while small grains will settle slower. The very fine-grained sediments such as silt and clay may
require years to settle from the water column. The greater the residence time of the reservoir, the higher the
percentage of the inflowing sediment will settle to the bottom. However, the very smallest clay particles may
never settle due to electrical charges in the minerals composing the particles and the charges in water
molecules caused by hydrogen bonding.
Sediment entering a reservoir and settling to the bottom eliminates some of the storage space of the
reservoir. Over time the cumulative storage lost to sediment settling may be significant. If you select a
Reservoir Capacity Method, the program will compute the sediment balance in the reservoir over time and
update the Elevation-Area and Elevation-Storage curves for each time step using efficient trap methods
based on the sediment and debris inflow from the upstream watersheds.

The Sediment Method for a reservoir is selected on the Component Editor for the Reservoir Element (shown
in the following figure). Access the Component Editor by clicking the Reservoir Element icon on the
element icon in the Basin Map, if the map is currently open. You can select a Sediment Method from the list
of five available choices. Use the selection list to choose the method you wish to use. Each reservoir is
treated separately and should use an appropriate method for the size of the reservoir compared to the inflow
volume. Very large reservoirs typically trap nearly all incoming sediment. Small reservoirs often trap gravel
and sand, while allowing silt and clay to pass through with some attenuation of the sediment pulses.

662 Selecting a Sediment Method for a reservoir element
The program will compute the sediment balance in the reservoir over time and update the Elevation-Area and
Elevation-Storage curves for each time step based on the deposited sediment amount on the reservoir
bottom.
The parameters for each Sediment Method are presented on a separate Component Editor from the
Reservoir Element editor. The Sediment editor is shown next to the Reservoir editor once a Sediment
Method has been selected. The information shown on the Sediment editor will depend on which method is
currently selected, though some methods have no parameters to enter.
21.4.2 Complete Sediment Trap

The Complete Sediment Trap Method settles all incoming sediment to the bottom of the reservoir with no
sediment remaining in the outflow. This method may be used for reservoirs that have a large residence time
which is sufficient for even silt and clay particles to settle. Suitability of the method may be verified by
computing the settling velocity of small sediment particles, dividing the reservoir depth by the settling
velocity, and comparing to the estimated residence time. A reference such as Jiménez and Madsen (2003)
may be used to compute settling velocity. There are no parameters for the method.
21.4.3 Specified Sediment

The Specified Sediment Method uses observations of sediment at the outlet of the reservoir to compute the
sediment leaving the reservoir at each time interval. The sediment observed at the outlet may be more or
less than the incoming sediment during a time interval. Settling is presumed to occur when the observed
sediment is less than the incoming sediment. When the observed sediment is more than the incoming
sediment, resuspension and discharge is presumed to occur. The actual physical processes are not

significant; the observed sediment at the outlet of the reservoir is simply specified as a time-series.
663 Specified Sediment Method Editor at a reservoir element
The total sediment discharge from the reservoir is specified with a Time-Series of Sediment Load. The time-
series should represent the total of all grain size classes. The time-series data must be defined in the Time-
Series Data Manager before it can be selected in the Sediment editor. The Time-Series button next to the
selection list can be used to assist in selecting the correct sediment gage.
The total sediment discharge from the reservoir is apportioned into grain size classes using a Grain Size
Distribution Curve. The grain size distribution curve is specified with a diameter-percentage function. The
function data must be defined in the Paired Data Manager before it can be selected in the Sediment editor.
The Paired Data button next to the selection list can be used to assist in selecting the correct function.
21.4.4 Chen Sediment Trap

The trap efficiency of a reservoir is the sediment load retained in the reservoir divided by the total sediment
load entering the reservoir. The trap efficiency can be estimated by comparing the settling velocity of the
sediment to a critical settling velocity (Chen, 1975). The settling velocity is computed using the method
selected for the Basin Model. The critical settling velocity is computed as the discharge rate from the
reservoir divided by the surface area. The computations are performed separately for each grain size class or
subclass. In order to compute the surface area for each time interval of the simulation, this method can only
be used if the reservoir storage characteristics are specified with the elevation-area method. The Component

664 Chen Sediment Trap Method Editor at a reservoir element
The main parameter for the Chen Sediment Trap Method is the depth-averaged temperature of the water in
the reservoir. You may specify a Fixed Temperature or select a Temperature Time-Series Gage.
Temperature gages must be created in the Time-Series Data Manager before they can be used for the
Sediment Method.
The Reservoir Capacity Method is the option for simulating the dynamic reservoir/debris basin volume
reduction using trap efficient methods based on sediment/debris inflow from the upstream watersheds.
When selecting Yes for the reservoir capacity method, two deposition shape options (V-Shape and
Elongated Taper) are available.
The V-Shape update the elevation-storage curve and elevation-area curve from the reservoir bottom
elevation based on the siltation volume by each grain size (Clay, Silt, Sand, and Gravel) at each time step.
The Elongated Taper update the elevation-storage curve and elevation-area curve from the reservoir bottom
for fine particles (Clay and Silt) and from the reservoir top elevation for the granular materials (sand and
gravel) based on the siltation volume at each time step.
21.4.5 Brune Sediment Trap

The trap efficiency of a reservoir is the sediment load retained in the reservoir divided by the total sediment
load entering the reservoir. Brune (1953) developed the curve with the relation between trap efficiency and
reservoir capacity-annual inflow ratio (C/I). The computations are performed separately for each grain size
class or subclass. The Component Editor is shown in the following figure.

665 Brune Sediment Trap Method Editor at a reservoir element
The Annual Inflow Volume describes the mean annual inflow volume to the reservoir.
The Capacity Elevation describes the elevation of reservoir at the reservoir capacity.
Typical value range of Constant A is from 95 to 100.
Typical value range of Constant B is from 5,37 to 7.71.
The Reservoir Capacity Method is the option for simulating the dynamic reservoir/debris basin volume
reduction using trap efficient methods based on sediment/debris inflow from the upstream watersheds.
When selecting Yes for the reservoir capacity method, two deposition shape options (V-Shape and
Elongated Taper) are available.
The V-Shape update the elevation-storage curve and elevation-area curve from the reservoir bottom
elevation based on the siltation volume by each grain size (Clay, Silt, Sand, and Gravel) at each time step.
The Elongated Taper update the elevation-storage curve and elevation-area curve from the reservoir bottom
for fine particles (Clay and Silt) and from the reservoir top elevation for the granular materials (sand and
gravel) based on the siltation volume at each time step.
21.4.6 Zero Sediment Trap

The Zero Sediment Trap Method passes all incoming sediment to the outlet with no settling. The incoming
sediment load for each grain size is totaled for the upstream elements at the end of each time interval. The
total time interval sediment load for each grain size class is then transferred to the outlet of the reservoir. No
settling happens for any of the grain size classes during the time interval. This may lead to large differences
in the sediment concentration at the inlet and outlet of the reservoir if the inflow rate is different from the
discharge rate. This method is only recommended for very small reservoirs with a residency time
approximately equal to the simulation time interval. There are no parameters for the method.

21.5 Source Sediment

A Source Element provides a way to introduce inflow to the channel network. Usually the inflow represents a
portion of the upstream watershed that is not explicitly modeled in the basin model. Sometimes the inflow is
computed in a separate simulation model, where the outflow hydrograph from that model becomes the
inflow at the source element. Other times the inflow is observed at a flow measurement station and
becomes the inflow at the source element. It is critical in a basin model that contains a source element to
introduce both the water and sediment inflow at the source.

The Sediment Method for a source is selected on the Component Editor for the Source Element (shown in
the following figure). Access the Component Editor by clicking the Source Element icon on the
of three available choices. If you choose the None method, the source will not compute any sediment and all
sediment discharges from the element will be zero. Use the selection list to choose the method you wish to
use. Each source is treated separately and should use an appropriate method for the area of the watershed
above the source and the duration of the simulation.
666 Selecting a Sediment Method for a source element
The parameters for each Sediment Method are presented on a separate Component Editor from the Source
Element editor. The Sediment editor is shown next to the Inflow editor once a Sediment Method has been
selected. The information shown on the Sediment editor will depend on which method is currently selected.
21.5.2 Annual Load

The Annual Load Method applies an average annual sediment load to the discharge hydrograph with a
methodology that may be suitable for continuous simulation applications where the land use is not changing
in time. The total load must be distributed into a time-series in a manner that is consistent with the outflow

hydrograph at the source. The method adopted in the program is to use an exponential form developed by
Haan et al. (1994). The exponential equation is given by:
where ct is the sediment concentration at time t, k is the ratio of the total sediment load for the time window
to the total discharge for the time window, Qt is the source discharge at time t, and a is an exponent entered
by the user. The Component Editor is shown in the following figure.
667 Annual Load Sediment Method Editor at a source element
The Total Load specifies the accumulated sediment over all grain size classes for a typical year. The total
load depends on the land use of the area upstream of the source element and can be highly variable due to
local conditions. The load is fixed for the simulation time window.
21.5.3 Specified Load

The Specified Sediment Method uses observed sediment load time-series data to determine the sediment to
add to the flow at the source element. Observations of sediment are less common than observations of
stream flow. In cases where observations are not available at the location of the source element, this method
could be used for sediment computed from an external model of sediment discharge. The Component

668 Specified Load Sediment Method Editor at a source element
The total sediment discharge at the source is specified with a Time-Series of Sediment Load. The time-
series should represent the total of all grain size classes. The time-series data must be defined in the Time-
Series Data Manager before it can be selected in the Sediment editor. The Time-Series button next to the
selection list can be used to assist in selecting the correct sediment gage.
The total sediment discharge at the source is apportioned into grain size classes using a Grain Size
21.6 Junction Sediment

A Junction Element is used to combine the outflow from multiple upstream elements in order to produce
one outflow. The outflow from the junction is usually connected downstream to a reach or other elements.
All water that enters a junction must leave the junction because no water is stored at the junction. Therefore,
all of the inflows to the junction are added together in order to compute the total inflow hydrograph to the
junction. Similarly, all sediment in each of the inflows is added to compute the total sedigraph. The total
inflow hydrograph and total inflow sedigraph are connected to the downstream element.
21.7 Diversion Sediment

A Diversion Element is used to represent a hydraulic control structure that directs some of the stream flow
out of the channel and into a storage pond or side channel. The Diversion Method calculates the amount of
flow to be diverted and subtracts it from the inflow to the element. The diverted flow may be connected to a
downstream location in the channel network. After the diverted flow is subtracted from the inflow, the
remaining flow continues downstream through the channel network. Sediment is managed in much the same
manner. The inflow to the diversion element is accompanied by sediment entering the element. Some of the
sediment may be taken with the diverted flow. The remaining sediment continues downstream with the
channel flow that passes through the diversion element. The physical properties of the diversion structure
control the amount of sediment that goes with the diverted flow as compared to the amount of sediment
remaining in the channel.


The Sediment Method for a diversion is selected on the Component Editor for the Diversion Element (shown
in the following figure). Access the Component Editor by clicking the Diversion Element icon on the
of three available choices. If you choose the None method, the source will not compute any sediment and all
sediment discharges from the element will be zero. Use the selection list to choose the method you wish to
use. Each diversion is treated separately and should use an appropriate method for the configuration of the
diversion structure and its ability to pass sediment with the diverted flow.
669 Selecting a Sediment Method for a diversion element
The parameters for each Sediment Method are presented on a separate Component Editor from the
diversion element editor. The Sediment editor is shown next to the Divert editor once a Sediment Method
has been selected. The information shown on the Sediment editor will depend on which method is currently
selected.
21.7.2 Passage Efficiency

Diversion structures are usually designed primarily to control the movement of water, redirecting some
portion of the inflow away from the main channel. In general, the d50 of the sediment in the diverted flow is
smaller than the d50 of the sediment in the main channel. The Passage Efficiency Method provides a simple
approach to controlling the differential sediment movement that typically occurs at diversion structures.
The Clay Percentage in the diverted flow must be specified. The incoming clay load to the diversion element
is converted to a concentration. Subsequently the clay concentration in the diverted flow is calculated as the
incoming concentration multiplied by the specified percentage. A mass balance is then performed in order to

calculate the load in the diverted flow and the load remaining in the channel. When the AGU 20 grain size
classification is used, the same percentage is used for all subclasses of clay.
670 Passage Efficiency Sediment Method Editor at a diversion element
The Silt Percentage in the diverted flow must be specified. The silt percentage may be close to the clay
percentage if the velocity through the diversion structure is high. When the AGU 20 grain size classification is
used, the same percentage is used for all subclasses of silt.
The Sand Percentage in the diverted flow must be specified. Unless the diversion structure is specifically
designed to direct sediment from the main channel, the sand percentage will be much smaller than the
percentage for clay and silt. When the AGU 20 grain size classification is used, the same percentage is used
for all subclasses of sand.
The Gravel Percentage in the diverted flow must be specified. The percentage for gravel is often close to
zero. When the AGU 20 grain size classification is used, the same percentage is used for all subclasses of
gravel.
21.7.3 Specified Load

The Specified Sediment Method uses observed sediment load time-series data to determine the sediment to
remove from the inflow to the diversion element and transfer with the diverted flow. Remaining sediment
remains in the channel and continues to be routed downstream of the diversion. If observations of sediment
are not available where the diverted flow is discharged out of the channel, then an external model could be
used to compute the sediment load. The Component Editor is shown in the following figure.
671 Specified Load Sediment Method Editor at a diversion element

The total sediment discharge for the diverted flow is specified with a Time-Series of Sediment Load. The
time-series should represent the total of all grain size classes. The time-series data must be defined in
the Time-Series Data Manager before it can be selected in the Sediment editor. The Time-Series button next
to the selection list can be used to assist in selecting the correct sediment gage.
The total sediment discharge in the diverted flow is apportioned into grain size classes using a Grain Size
21.8 Sink Sediment

A Sink Element is used to mark the outlet of a watershed model. No water leaves the sink. Therefore, all of
the inflows to the sink are added together in order to compute the total inflow hydrograph to the sink. Just as
water cannot leave the sink, sediment also cannot leave the sink. Similar to the water, all sediment in each of
the inflows is added to compute the total sedigraph.
21.9 Viewing Erosion and Sediment Results

The primary results from erosion and sediment components are time-series. Available results depend on the
type of element, but always include both the total sediment load and the total sediment volume leaving the
element. The total sediment load and volume are also separated out by grain size class or subclass. These
results are accessed in the Watershed Explorer on the Results tab. When erosion and sediment components
are activated, a special folder for erosion and sediment results is added under each element icon.
All of the erosion and sediment time-series data computed by an individual element are available for viewing.
Click on a time-series node to preview the data in the Component Editor. You may select multiple time-series
data by holding the shift or control key while using the mouse to click on additional nodes. The selected
time-series may come from different elements in the same simulation, or the same element in different
simulations. Results can also be combined from different types of simulations including Simulation Runs,
Optimization Trials, Depth-Area Analyses, and Forecast Alternatives. The selected time-series data will
automatically be partitioned into groups by data type if the erosion and sediment results are combined with
other types of results such as flow or stage.
21.9.1 Subbasin
The Erosion Results for each subbasin include the time-series of total sediment load and total sediment
volume leaving the subbasin. The total sediment time-series are the sum of all grain size classes. Also
included are individual time-series of sediment load in each grain size class and sediment volume in each
grain size class. The total sediment concentration in the outflow is also included among the results. The bulk
flow result is an estimate of the combined water and sediment flow rates. The organization of the results is

672 Sediment results for a subbasin element

21.9.2 Reach
The Sediment Results for each reach include the time-series of total sediment load and total sediment
volume entering the reach, and the total sediment load and total sediment volume leaving the reach. The
total sediment time-series area the sum of all grain size classes. Also included are the time-series of
sediment load and sediment volume broken down into each grain size class both coming into the reach and
leaving the reach. Furthermore, time-series results for reaches are available for active and inactive bed
sediemnt as well as total bed sediment and suspended sediment. The bulk flow result is an estimate of the
combined water and sediment flow rates. The organization of the results is shown in the following figure.

673 Sediment results for a reach element

21.9.3 Reservoir
The Sediment Results for each reservoir include the time-series of total sediment load entering the reservoir,
and the total sediment load leaving the reservoir. Additionally, the time-series of total sediment load settled
to the bottom of the reservoir is available, along with the time-series of sediment load in suspension in the
reservoir pool. For each of the all categories, the total sediment is the sum of all grain size classes. Also
included is the time-series of sediment load in each grain size class for each of the all categories of
sediment at a reservoir. The bulk flow result is an estimate of the combined water and sediment flow rates.
The organization of the results is shown in the following figure.

674 Sediment results for a reservoir element

21.9.4 Source
The Sediment Results for each source include the time-series of total sediment load and the time-series of
total sediment volume leaving the source. These both represent the sum of all grain size classes. Results are
also available broken down into each grain size class for sediment load and volume. The bulk flow result is
an estimate of the combined water and sediment flow rates. The total sediment concentration in the outflow
is also included among the results.
21.9.5 Junction
The Sediment Results for each junction include the time-series of total sediment load and the time-series of
total sediment volume leaving the junction. These both represent the sum of all grain size classes. Results
are also available broken down into each grain size class for sediment load and volume. The bulk flow result
is an estimate of the combined water and sediment flow rates.
21.9.6 Diversion
The Sediment Results for each diversion include the time-series of total sediment load entering the
diversion, and the total sediment load leaving the diversion. Similarly, the time-series of total sediment
volume entering and leaving the diversion are also included. These both represent the sum of all grain size
classes. Results are also available broken down into each grain size class for sediment load and volume.
Additionally, the total sediment load in the diverted flow is available. The bulk flow result is an estimate of
the combined water and sediment flow rates.
21.9.7 Sink
The Sediment Results for each sink include the time-series of total sediment load entering the sink and the
time-series of total sediment volume entering the sink. The total sediment load (and volume) time-series is
the sum of all sediment load (and volume) from each of the upstream elements. Also included is the time-
series of sediment load for each grain size class, computed similarly to the total load but specific to each
grain size. Sediment volume is also broken down according to each grain size class. The bulk flow result is
an estimate of the combined water and sediment flow rates.
21.10 References: Erosion and Sediment Transport

Ackers, P. and W.R. White. 1973. "Sediment Transport: New Approach and Analysis." Journal of the
Hydraulics Division, vol 99, no HY11, pp 2040-2060.
Breault, R.F., K.P. Smith, and J.R. Sorenson. 2005. Residential Street-dirt Accumulation Rates and Chemical
Composition, and Removal Efficiencies by Mechanical- and Vacuum-type Sweepers, New Bedford,
Massachusetts, 2003-04. U.S. Geological Survey, Scientific Investigations Report 2005-5184.
Brune, G.M. 1953, Trap Efficiency of Reservoir, Am. geophys. Union Trans. 34(3), 407-417

Chen, C.N. 1975. "Design of Sediment Retention Basins." Proceedings of the National Symposium on Urban
Hydrology and Sediment Control, pp 285-298.
Copeland, R.R. and W.A. Thomas. 1989. Corte Madera Creek Sedimentation Study, Numerical Model
Investigation. U.S. Army Corps of Engineers, Waterways Experiment Station, Technical Report HL-89-6.
Engelund, F. and E. Hansen. 1967. A Monograph on Sediment Transport in Alluvial Streams. Danish Technical
University, Hydraulics Laboratory.
Fischer, H.B., E.J. List, R.C.Y. Koh, J. Imberger, and N.H. Brooks. 1979. Mixing in Inland and Coastal Waters.
Academic Press, San Diego.
Gartner, J.E., Cannon, S.H. and Santi, P.M. 2014. Empirical models for predicting volumes of sediment
deposited by debris flows and sediment-laden floods in the transverse ranges of southern
California. Engineering Geology 176, 45-56
Gassman, P.W., M.R. Reyes, C.H. Green, and J.G. Arnold. 2007. "The Soil and Water Assessment Tool:
Historical Development, Applications, and Future Research Directions." Transactions of the ASABE, vol 50, no
4, pp 1211-1250.
Gatwood, E., Pederson, J. and Casey, K. 2000. Los Angeles district method for prediction of debris yields.
U.S. Army Corps of Engineers, Los Angeles District.
Haan, C.T., B.J. Barfield, and J.C. Hayes. 1994. Design Hydrology and Sedimentology for Small Catchments.
Academic Press, New York.
Interagency Committee. 1957. Some Fundamentals of Particle Size Analysis: A Study of Methods Used in
Measurement and Analysis of Sediment Loads in Streams. Interagency Committee on Water Resources,
Subcommittee on Sedimentation, St. Anthony Falls Hydraulic Laboratory, Minneapolis, Minnesota.
Jiménez, J.A. and O.S. Madsen. 2003. "A Simple Formula to Estimate Settling Velocity of Natural
Sediments." Journal of Waterway, Port, Coastal, and Ocean Engineering, vol 129, no 2, pp 70-78.
Kashefipour, S.M. and R.A. Falconer. 2002. "Longitudinal Dispersion Coefficient in Natural Channels." Water
Research, vol 36, pp 1596-1608.
Krone, R.B. 1962. Flume Studies of the Transport of Sediment in Estuarial Shoaling Processes. Hydrologic
Engineering Laboratory, University of California, Berkeley.
Laursen, E.M. 1958. "The Total Sediment Load of Streams." Journal of the Hydraulics Division, vol 84, no HY1,
pp 1-36
Meyer-Peter, E. and R. Müller. 1948. "Formulas for Bed-Load Transport." Proceedings of the 2nd Meeting of
the International Association for Hydraulic Research, pp 39-64.

Pak, J.H. and Lee, J.J. 2008. A statistical sediment yield prediction model incorporating the effect of fires
and subsequent storm events. J. Am. Water Resour. Assoc. 44 (3), 689–699.
Pak, J.H. and Lee, J.H. 2012. A Hyper-concentration Sediment Yield Prediction Model Using Sediment
Delivery Ration for Large Watersheds. KSCE Journal of Civil Engineering (2012) 16(5):883-891.
Parthenaides, E. 1962. A Study of Erosion and Deposition of Cohesive Soils in Salt Water. PhD Dissertation,
University of California, Berkeley.
Rubey, W.W. 1933. "Settling Velocities of Gravel, Sand, and Silt Particles." American Journal of Science
5th Series, vol 25, no 148, pp 325-338.
Toffaleti, F.B. 1968. A Procedure for Computation of Total River Sand Discharge and Detailed Distribution, Bed
to Surface. U.S. Army Corps of Engineers, Committee on Channel Stabilization, Technical Report 5.
Van Rijn, L.C. 1993. Principles of Sediment Transport in Rivers, Estuaries, Coastal Seas and
Oceans. International Institute for Infrastructural, Hydraulic, and Environmental Engineering, Delft,
Netherlands.
Wilcock, P.R. and J.C. Crowe. 2003. "Surface-based Transport Model for Mixes-Size Sediment." Journal of
Hydraulic Engineering, vol 129, no 2, pp 120-128.
Williams, J.R. 1975. "Sediment-yield Prediction with Universal Equation Using Runoff Energy Factor."
In Present and Prospective Technology for Predicting Sediment Yield and Sources: Proceedings of the
Sediment Yield Workshop. USDA Sedimentation Laboratory, Oxford, Mississippi.
Yang, C.T. 1984. "Unit Stream Power Equatioin for Gravel." Journal of the Hydraulics Division, vol 110, no 12,
pp 1783-1797.

22 Data Storage in HEC-DSS

The Project DSS file stores time-series and paired data generated in the project. Data is stored in blocks
called records that are identified with a unique pathname. Predefined descriptors are used in the C-Part of
the pathname. This appendix describes the C-part descriptors for each data type.
22.1 Descriptors
AREA Computed area for a reservoir element.
ATI-COLD Computed antecedent temperature index for cold content in the

snowmelt method.
ATI-COLDRATE Manually entered antecedent temperature index versus coldrate

function for a paired data function.
ATI-MELT Computed antecedent temperature index for meltrate in

snowmelt.
ATI-MELTRATE Manually entered antecedent temperature index versus meltrate

function for a paired data function.
COLD CONTENT Computed cold content in snowmelt.
CROP COEFFICIENT Manually entered time-series of crop coefficient for a time-series

gage.
DISTANCE-ELEVATION Manually entered cross section in the paired data manager.
ELEVATION Computed pool elevation for a reservoir element.
ELEVATION-OBSERVED Observed pool elevation for a reservoir element using the optional
observed elevation time-series gage.
ELEVATION-RESIDUAL Residual elevation for a reservoir element with observed

elevation. The residual is calculated as computed flow minus the
observed elevation.
Data Storage in HEC-DSS – 771

ELEVATION-AREA A manually entered elevation-area function defined in the paired

data manager.
ELEVATION-FLOW An elevation-discharge curve defined in the reservoir element. No

longer used in the current program version.
ELEVATION-STORAGE A manually entered elevation-storage function defined in the

paired data manager.
ET-CANOPY Computed actual evapotranspiration from the canopy layer in the

soil moisture accounting loss method.
ET-POTENTIAL Potential evapotranspiration for a subbasin element as computed

by the meteorologic model.
ET-SOIL Computed actual evapotranspiration from the soil layer in the soil
moisture accounting loss method.
ET-SURFACE Computed actual evapotranspiration from the surface depression

layer in the soil moisture accounting loss method.
EXCESS-CANOPY Computed incremental precipitation minus canopy interception in

the soil moisture accounting loss method.
FLOW Final computed flow for an element.
FLOW-AUX Outflow from a reservoir through the auxiliary discharge.
FLOW-BASE Computed baseflow for a subbasin element.
FLOW-COMBINE Computed total inflow to an element.
FLOW-DIRECT Surface flow computed by transforming excess precipitation for a

subbasin element.
FLOW-DIVERSION Computed diversion flow for a diversion element.
FLOW-IN Total inflow to a reach element.

FLOW-LOCAL Local flow at a junction when the basin model is set to compute
local flow at junctions.
FLOW-LOCAL-SIM Computed local flow without blending for a junction when

observed flow is present, blending is used, and the basin model is
set to compute local flow at junctions.
FLOW-LOSS At a reach, the computed channel losses.
FLOW-OBSERVED Observed flow for an element using the optional observed flow
time-series gage.
FLOW-RESIDUAL Residual flow for an element with observed flow. The residual is
calculated as computed flow minus the observed flow.
FLOW-SIM Computed flow without blending at an element when observed

flow is present and blending is used.
FLOW-UNIT GRAPH Manually entered unit hydrograph in the paired data manager.
GROUNDMELT Manually entered annual groundmelt pattern in the paired data

manager.
INFILTRATION Computed infiltration from the surface layer to the soil in the soil
moisture accounting loss method. Also, the amount of loss
attributed to infiltration in the deficit constant loss method.
LIQUID WATER Computed liquid water in the snowpack in snowmelt.
MELTRATE Manually entered annual meltrate pattern in the paired data

manager.
MOISTURE DEFICIT Computed moisture deficit in the deficit constant and gridded
deficit constant loss methods.
OUTFLOW-GW Computed outflow from a groundwater layer to channel baseflow

in the soil moisture accounting loss method.
PERC-SOIL Computed percolation from the soil layer to the upper

groundwater layer in the soil moisture accounting loss method.

PERC-GW Computed percolation from the upper groundwater layer to the

lower groundwater layer or from the lower groundwater layer out
of the system in the soil moisture accounting loss method.
PERCENT-GRAPH Manually entered percentage curve in the paired data manager.
PRECIP-EXCESS At a subbasin, incremental precipitation minus losses.
PRECIP-EXCESS-CUM At a subbasin, cumulative precipitation minus cumulative losses.
PRECIP-CUM Cumulative precipitation for a time-series gage.
PRECIP-INC Incremental precipitation for a time-series gage or subbasin

element.
PRECIP-LOSS At a subbasin, the incremental precipitation that was converted to

loss during loss calculations.
PRECIP-LOSS-CUM At a subbasin, the cumulative precipitation that was converted to

loss during loss calculations.
PRECIP-LWASS The liquid water available at the soil surface calculated for a
subbasin by a snowmelt method.
PRECIP-LWASS-CUM The cumulative liquid water available at the soil surface

calculated for a subbasin by a snowmelt method.
PRECIP-STAND DEV At a subbasin, the standard deviation of incremental precipitation

for each time interval computed using gridded precipitation.
RECOVERED DEFICIT Computed recovery of the deficit by evapotranspiration in the

deficit constant and gridded deficit constant loss methods.
SATURATION FRACTION The percentage of the soil layer that is saturated in the deficit and
constant or soil moisture accounting loss methods.
SOLAR RADIATION Manually entered time-series of solar radiation for a time-series

gage.

STAGE Computed stage for an element when the optional elevation-

discharge curve is used. Also, manually entered time-series of
stage for a time-series gage.
STAGE-CHANNEL Stage computed in the channel at a diversion element.
STAGE-FLOW A manually entered elevation-discharge function defined in the

STAGE-OBSERVED Observed stage for an element using the optional observed stage
time-series gage.
STAGE-RESIDUAL Residual stage for an element with observed stage. The residual
is calculated as computed flow minus the observed flow.
STAGE-SIM Stage at a reach using the modified Puls or Muskingum Cunge

routing methods computed using the simulated flow depth.
STAGE-TAILWATER The computed tailwater stage at a reservoir element.
STAGE-TW-AUX The computed tailwater stage at the auxiliary discharge from a

reservoir element.
STORAGE Computed storage for a reservoir element.
STORAGE-CANOPY Computed storage depth of the canopy layer in the soil moisture
accounting loss method.
STORAGE-ELEVATION A storage-elevation curve defined in the reservoir element. No

longer used in the current program version.
STORAGE-FLOW A manually entered storage-discharge function defined in the

STORAGE-GW Computed storage depth of a groundwater layer in the soil

moisture accounting loss method.
STORAGE-SOIL Computed storage depth of the soil layer in the soil moisture

STORAGE-SURFACE Computed storage depth of the surface layer in the soil moisture
SWE Computed snow water equivalent in snowmelt.
SWE-OBSERVED Observed snow water equivalent for a subbasin element using the
optional observed SWE time-series gage.
SWE-RESIDUAL Residual snow water equivalent for a subbasin element with

observed SWE. The residual is calculated as computed flow
minus the observed SWE.
TEMPERATURE Computed temperature for a subbasin elevation band in

snowmelt. Also, manually entered time-series of temperature for a
time-series gage.
50 C-Part descriptors for each data type

23 Utilities
23.1 Calculator
The Calculator utility is launched from the Tools | Data | Calculator menu in HEC-HMS.
A project does not have to be open to access the Calculator.
23.1.1 Step 1: Select Source Variables

Select a Source Grid file using the File Browse button (1). When a source file is selected, its variables will be
displayed in the Available Variables column (2). Variables can be moved from the Available Variables
column to the Selected Variables column (2 to 3) by double-clicking the variable or using the arrows to move
the selected variable.
675 Selecting a Source Grid file
At least one variable must be selected to proceed.
Utilities – 777
23.1.2 Step 2: Set Math Operation to Calculate

(1) Set a number to Multiply with.
(2) Set a number to Divide with.
(3) Set a number to Add with.
(4) Set a number to Subtract with.
676 Setting the math operation to calculate
The input can be an integer or a double.
Only one operation may be chosen. If two or more operations are chosen, an error message will
pop up as shown below.
Utilities – 778
677 Error produced when choosing two or more operations
23.1.3 Step 3: Select Destination

The File Browse button (1) can be used to browse to a Destination file. If the destination file is HEC-DSS
format, additional options are presented for specifying pathname parts. Some pathname parts can not be
edited. These will be populated automatically.
678 Selecting Destination file
23.1.4 Step 4: Processing

After Next has been selected in Step 3, a progress bar will display, indicating the progress of the operation.
Utilities – 779
679 Progress bar while processing data
23.1.5 Step 5: Calculator Complete

After the calculator is complete, the wizard will automatically progress to step 5, indicating that the
calculation is complete. There are buttons to Restart or Close the wizard. The result of the calculation will be
saved to the user-selected DSS file (chosen in step 3)
680 Calculator Wizard reporting a completed calculation
23.2 Clipper
The Clipper utility clips grids to a shapefile or other geometry layer.
The Clipper utility is launched from the File | Import | Clipper menu in HEC-HMS.
Utilities – 780
A project does not have to be open to access the Clipper.
23.2.1 Step 1: Select Source File

Use the File Browse button (1) to select the source file in HEC-DSS format.
681 Select source file
23.2.2 Step 2: Select Source Grids

The pane on the left (1) includes a set of Source Grids available in the source HEC-DSS file. The pane on the
right (2) includes the source grids that have been selected for clipping. Source grids can be moved from the
Available Grids column to the Selected Grids column by double-clicking the grid or using the arrows to move
the selected grid. At least one grid must be selected to proceed.
Utilities – 781
682 Select source grids
Make sure that the source grids are in a Projected Coordinate System. The clipper will not work
with Geographic Coordinate Systems. Click here for more information on projected coordinate
systems in HEC-HMS62.
23.2.3 Step 3: Select Clipping Datasource

Click the File Browse button (1) to select the Shapefile that will be used to clip the selected source grids. The
shapefile should be in the same projected coordinate system as the source grid.
683 Select clipping datasource
62 https://www.hec.usace.army.mil/confluence/display/HMSUM/.Coordinate+Reference+Systems+v4.7
Utilities – 782

Click the File Browse button (1) to browse to a Destination file. If the destination file is in HEC-DSS
684 Select destination

After Next has been selected on Step 4, a progress bar will display, indicating the progress of the clip.
685 Clipper Wizard showing the process status
Utilities – 783
23.2.6 Step 6: Clipper Complete

After the clip is complete, the wizard will automatically progress to step 6. There are buttons
to Restart or Close the wizard. The clipped gridded data will be saved to the user selected HEC-DSS file
chosen in step 4. You will need to create a gridded data object63 within the HEC-HMS project and link the
object to one of the grid data records in the DSS file to use the gridded data within an HEC-HMS simulation.
686 Clipper complete
23.3 Gridded Data Import

The Gridded Data Importer utility is launched from the File | Import | Gridded Data menu in HEC-HMS.
A project does not have to be open to access the Gridded Data Importer.
23.3.1 Step 1: Select Files

Select files using the File Browse button (1). One or more files can be selected. Files can be removed by
selecting the file and pressing the delete button on the keyboard.
63 https://www.hec.usace.army.mil/confluence/display/HMSUM/.Grid+Data+v4.7.1
Utilities – 784
687 Selecting files for the Gridded Data Import
23.3.2 Step 2: Select Variables

The pane on the left (1) includes a set of Variables that were found when scanning through the files. The
pane on the right (2) includes variables that have been selected for import. Variables can be moved from the
Available Variables column to the Selected Variables column by double-clicking the variable or using the
arrows to move the selected variable. At least one variable must be selected to proceed.
688 Selecting variables
23.3.3 Step 3: Select Re-sampling Options

An Optional Clipping Data Source can be selected (1). The clipping data source will be used to clip the grids
on import.
Utilities – 785
An Optional Target Projection Well-Known-Text (WKT) string can be provided. The target WKT specifies the
projection that the incoming grids will be reprojected to. A projection, *.prj, file can be selected using the File
Browse button. The Globe icon (2) can be used to select common SHG or UTM projections.
An Optional Target Cell Size can be specified. The target cell size is the size that the incoming grids will be
resampled to. The grid button (3) can be used to select from a list of common grid cell sizes.
A Resampling Method can be specified (4). Resampling options include Bilinear, Nearest Neighbor, and
Average.
689 Selecting re-sampling options

edited and will be populated automatically.
690 Selecting Destination file
Utilities – 786

After Next has been selected in Step 4, a progress bar will display, indicating the progress of the import.
691 Gridded Data Import Wizard displaying the processing status
23.3.6 Step 6: Import Complete

After the import is complete, the wizard will automatically progress to step 6, indicating that the import is
complete. There are buttons to Restart or Close the wizard. The gridded data will be saved to the user-
selected DSS file (chosen in step 4). The user will need to create a gridded data object within the HEC-HMS
project and link the object to one of the grid data records in the DSS file in order to use the gridded data
within an HEC-HMS simulation.
692 Gridded Import Wizard reporting a completed process
Utilities – 787
23.4 Grid to Point Converter

The Grid-to-Point-Converter converts gridded data to basin-average time-series data.
The Grid-to-Point-Converter is launched from the Tools | Data | Grid To Point menu in HEC-HMS.
A project does not have to be open to access the Grid-to-Point-Converter.

Select a Source Grid file using the File Browse button (1). When a source file is selected, its Variables will be
693 Selecting source variables
23.4.2 Step 2: Select the Zones shapefile

Select a Zones Shapefile using the File Browse button (1). When a zones shapefile is selected, its fields will
display in the Field combo box (2). Select a field in the field combo box (2). The selected field will be the
basis for the B-Part of the DSS time series records that are created. If you want a total watershed average
Utilities – 788
time-series then you will need to create a shapefile where subbasins have been merged together (there
should be only one polygon for the entire watershed). If you want average time-series for each subbasin, then
the shapefile should contain a polygon with a unique name for each subbasin.
694 Selecting the Zones shapefile
A Zones Shapefile and Field must be selected to proceed.

format, additional options are presented for specifying pathname parts (2). Some pathname parts cannot be
edited and will be populated automatically. There are also options for changing the DSS Units (3) and DSS
Data Type (4).
Utilities – 789
695 Selecting a Destination file

After Next has been selected on Step 4, a progress bar will display, indicating the progress of the Grid-to-
Point-Converter.
696 The Grid to Point Wizard displaying the processing status
23.4.5 Step 5: Grid To Point Converter Complete

After the Grid-to-Point-Converter is complete, the wizard will automatically progress to step 5, indicating
that the conversion is complete. There are buttons to Restart or Close the wizard. The time-series data will
be saved to the user selected DSS file (chosen in step 3). The user will need to create a time-series gage
object within the HEC-HMS project and link the object to one of the time-series records in the DSS file in
order to use the time-series data within an HEC-HMS simulation.
Utilities – 790
697 The Grid to Point Wizard reporting a completed process
23.5 Image Exporter

The Image Export utility exports gridded data from HEC-DSS format to image formats.
The Image Export utility is launched from the Tools | Data | Image Exporter menu in HEC-HMS.
A project does not have to be open to access the Image Exporter.

Select a Source Grid file using the File Browse button (1). When a source file is selected, its variables will be
displayed in the Source Grids column (2). Grids can be moved from the Source Grids column to the Selected
Grids column (2 to 3) by double-clicking the variable or using the arrows to move the selected variable.
Utilities – 791
698 Selecting a Source File Grid
At least one source grid must be selected to proceed.
23.5.2 Step 2: Set Export Location, Filename Prefix, and Format

(1) Set the Destination directory. By default, this will be set to the directory containing the Source file.
(2) Set a Filename Prefix. By default, this will be set to the name of the Source file.
(3) Select a Format. Options are TIFF and ASC.
699 Selecting the destination directory, filename prefix, and image format.
Utilities – 792

700 Progress bar while processing data
23.5.4 Step 4: Image Export Complete

After the export is complete, the wizard will automatically progress to step 4, indicating that the export is
complete. There are buttons to Restart or Close the wizard. The result of the export will be saved to the user-
selected directory (chosen in step 2).
701 Image Export Wizard reporting a completed export
Utilities – 793
23.5.5 Step 5: File Saved

After closing the Image Export Wizard, a File Saved dialog will display the location of the saved images with
options to Copy and Open the directory.
702 File Saved dialog
23.6 Normalizer
The Normalizer tool can be used to adjust grid cell values in one grid with information in another grid. A
common application is to adjust, or scale, precipitation values in a gridset that has values at a short time
interval, like every 1 hour, with gridded precipitation information from a gridset that has data at longer
durations.
23.6.1 Theory
23.6.1.1 Equation
For each grid cell, the value at the source grid time interval is scaled by the ratio of the value of the
accumulated normals grid cell value over the normalization period, divided by the value of the accumulated
source grid cell value over the normalization period.
Definitions
• Pc corrected precipitation for the source interval

• Vn normals grid cell accumulated volume over the normalization interval
• Vs source grid cell accumulated volume over the normalization interval
• Ps volume of source grid cell over the source interval
Utilities – 794
23.6.1.2 Example 1
In Example 1, the source and normal grids consist of a single grid cell. The source grids are 12 hours,
beginning at time 0000, and the normal grids are 24 hours, beginning at time 0000. The user has selected a
Normalization Interval of 1 day.
703 Normalization with the interval of 1 day
23.6.1.3 Example 2
Normalization Interval of 2 days.
704 Normalization with the interval of 2 days
Utilities – 795
23.6.1.4 Example 3
Normalization Interval of 1 day. The 0-12 hour source cell has No Data.
705 Normalization with the interval of 1 day and not having data for a source cell
If no data exists for the source grid cell, the normalized grid cell also contains no data. If no data
exists for the normal grid cell, the value of the source grid cell is adopted in the normalized grid.
23.6.1.5 Example 4
Normalization Interval of 1 day. The 0-24 hour normal cell has No Data.
706 Normalization with the interval of 1 day and the normal cell has no data
Utilities – 796
23.6.2 Usage
The Normalizer utility is launched from the Tools | Data | Normalizer menu in HEC-HMS.
A project does not have to be open to access the Normalizer.
23.6.2.1 Step 1: Select Source Variables

23.6.2.2 Step 2: Select Normal Variables

Select a Normal Grid file using the File Browse button (1). When a normal file is selected, its Variables will be
extracted to (2) the Available Variables column. Variables can be moved from the Available Variables
Utilities – 797
708 Selecting normal variables
23.6.2.3 Step 3: Set Normalization Period & Normalization Interval

The Start/End Date for the Normalization Period can be set at (1). The format for the date is: [m/d/yyyy]
The Start/End time for the Normalization Period can be set at (2). The format for the time is: [hhmm]
The Normalization Interval can be set at (3).
The Time Unit for the Normalization Interval can be set at (4). Time unit options include: Days, Hours,
Minutes, Seconds.
Utilities – 798
23.6.3
709 Setting the normalization period and normalization interval
23.6.3.1 Step 4: Select Destination

The File browse button (1) can be used to browse to a Destination file. If the destination file is HEC-DSS
710 Selecting a Destination file
23.6.3.2 Step 5: Processing

When the progress reaches 100%, the Restart and Close buttons will be enabled. The gridded data will be
Utilities – 799
saved to the user selected DSS file (chosen in step 4). The user will need to create a gridded data object
within the HEC-HMS project and link the object to one of the grid data records in the DSS file in order to use
the gridded data within an HEC-HMS simulation.
711 The Grid Normalizer Wizard displaying the processing status
23.7 Sanitizer
The Sanitizer utility screens and replaces values above or below a threshold.
The Sanitizer utility is launched from the Tools | Data | Sanitizer menu in HEC-HMS.
A project does not have to be open to access the Sanitizer.

Select a source grid file using the file browse button (1). When a source file is selected, its variables will be
displayed in the available variables column (2). Variables can be moved from the available variables
column to the selected variables column (2 to 3) by double-clicking the variable or using the arrows to move
Utilities – 800
23.7.2 Step 2: Select Thresholds and Replacement Values

The upper checkbox (1) is selected to filter and replace lower values. Use the text fields to enter the value of
the lower threshold (2) and a lower replacement value(3).
The lower replacement value must be greater than the specified threshold.
The second checkbox (4) is selected to filter and replace upper values. Use the text fields to enter the value
of the upper threshold (5) and an upper replacement value (6).
The upper replacement value must be less than the specified threshold.
Utilities – 801

The file browse button (1) can be used to browse to a destination file. If the destination file is HEC-DSS
format, additional options are presented for specifying pathname parts (2). Some pathname parts cannot be
edited. These will be populated automatically. There are also options for changing the DSS units (3) and DSS
data type (4).

After Next has been selected on Step 4, a progress bar will display, indicating the progress of the sanitizer.
Utilities – 802
23.7.5 Step 5: Sanitizer Complete

After the sanitization is complete, the wizard will automatically progress to step 5, indicating that the
sanitization is complete. There are buttons to Restart or Close the wizard. The gridded data will be saved to
the user selected DSS file (chosen in step 3). The user will need to create a gridded data object within the
HEC-HMS project and link the object to one of the grid data records in the DSS file in order to use the gridded
data within an HEC-HMS simulation.
23.8 Time-Shifter
The Time-Shifter tool can be used to adjust the time and date of gridded records in a DSS file. The Time-
Shifter tool will move the grid in time by the span of time chosen by the user. Shifts can either be forward or
backward in time, and the shift can be completed in Days, Hours, Minutes, or Seconds.
Utilities – 803
23.8.1 Usage
The Time-Shifter utility is launched from the Tools | Data | Shifter menu in HEC-HMS.
A project does not have to be open to access the Time-Shifter.
23.8.1.1 Step 1: Select Source Variables

23.8.1.2 Step 2: Determine the Time-Shift

Determine the Amount of Time to Shift the Grid (1). If the value chosen is Positive then the grid will be
shifted Forward in time. If the value chosen is Negative the grid will be shifted Backward in time (2). This
dropdown allows the user to choose the Unit of Time for the time-shift. Options include Days, Hours,
Minutes, or Seconds.
Utilities – 804
713 Determining the Time-Shift
23.8.1.3 Step 3: Select Destination

714 Selecting the Destination file
23.8.1.4 Step 5: Processing

After Next has been selected on Step 4, a progress bar will display, indicating the progress of the import.
When the progress reaches 100%, the Restart and Close buttons will be enabled and will replace the Back,
Next, and Cancel buttons. The gridded data will be saved to the user selected DSS file (chosen in step 4).
Utilities – 805
The user will need to create a gridded data object within the HEC-HMS project and link the object to one of
the grid data records in the DSS file in order to use the gridded data within an HEC-HMS simulation.
715 The Time-Shifter Wizard displaying the processing status
Utilities – 806
24 Reports
Report options are available from the Tools | Reports menu, as shown below. The Standard Report shows
information about the selected Basin Model and Simulation Run. The Statistics Report includes model
performance metrics for the selected Simulation Run.
716 Accessing the Reports menu
24.1 Standard Report

The Standard Report option creates an HTML report with options to include Global Parameter Summary
Tables, a Global Results Summary Table, Element Parameter Summary Tables, and Result Graphs for each
basin element. Content can be customized using check box selections in the user interface. The report is
written in HTML format and can be rendered in a browser.
Reports – 807
717 Standard Report dialog
The Global Summary Results Table shows summary results for each element. The image below shows an
example Global Summary Results Table.
Reports – 808
718 Example Global Summary Results Table
Global Parameter Summary Tables show, for a given method, parameterization for each element. The image
below shows the Global Parameter Summary Table for Mod Clark Transform:
719 Example Global Parameter Summary Table
Element Parameter Summary Tables show, for a given element, all parameterizations. The image below
shows an example Element Parameter Summary Table.
Reports – 809
720 Example Element Parameter Summary Table
Element Summary Results are shown by default:
Reports – 810
721 Example Element Summary Results
Additional Time-Series Graphs can be added to the report by selecting variables in the Element Time-Series
Graphs section of the Standard Report dialog.
24.2 Statistics Report

The Statistics Report option creates an HTML report with Summary Statistics for all observed flow locations
in a simulation. Summary statistics included in the report are: Coefficient of Determination (R2), Nash
Sutcliffe Efficiency (NSE), Root Mean Squared Error Ratio (RSR), and Percent Bias (PBIAS). The following
figure shows the Statistics Report editor. A Simulation run must be selected, all locations with observed flow
will be included in the report. An output html file must be defined to store the summary results.
Reports – 811
722 Statistics Report dialog
The following figure shows a Statistics Report for a large Basin Model that included a number of elements
with observed flow.
723 Example Statistics Report for a large Basin Model
The default color codes for each statistic are presented below:
Color Code R2 NSE RSR PBIAS
Dark Green 0.65<R2≤1.00 0.65<𝑁𝑆𝐸≤1.00 0.00<𝑅𝑆𝑅≤0.60 𝑃𝐵𝐼𝐴𝑆< ±15
Light Green 0.55<𝑅2≤0.65 0.55<𝑁𝑆𝐸≤0.65 0.60<𝑅𝑆𝑅≤0.70 ±15≤𝑃𝐵𝐼𝐴𝑆<±20
Reports – 812
Orange 0.40<𝑅2≤0.55 0.40<𝑁𝑆𝐸≤0.55 0.70<𝑅𝑆𝑅≤0.80 ±20≤𝑃𝐵𝐼𝐴𝑆<±30
Red 𝑅2≤0.40 𝑁𝑆𝐸≤0.40 𝑅𝑆𝑅>0.80 𝑃𝐵𝐼𝐴𝑆≥±30
51 Default color codes for Statistics Reports
Reports – 813
25 Scripting
HEC-HMS is written in Java and has public Application Programming Interface (API) methods that programs
or scripts can be written against. See the Jython and Java API references below.
Jython API64
Java API65
64 https://www.hec.usace.army.mil/software/hec-hms/javadoc/hms/model/JythonHms.html
65 https://www.hec.usace.army.mil/software/hec-hms/javadoc/hms/model/Project.html
Scripting – 814
26 Grid Cell File Format

The ModClark transform method requires either the structured discretization or a file specified discretization
that points to either a sqlite file or a *.mod file created by HEC-HMS. The file defines cells for each subbasin.
Parameters for each cell are also included in the grid-cell file. This appendix describes the *.mod grid-cell file
format. The file can be produced using available geographic information system (GIS) tools. The *.mod file is
no longer recommended. Instead, it is recommended that you use the structured discretization option.
26.1 File Definition

The grid-cell file begins with the keyword "Parameter Order" followed by a colon and parameter keywords
indicating the order for reading parameters from the file (see figure below). The keyword "End" must be on a
line by itself after the "Parameter Order" line. Valid parameter keywords are shown in the table below.
Parameter keywords are not case sensitive and are separated by spaces. If the parameter order is not
defined, it is assumed to be: Xcoord Ycoord TravelLength Area. The coordinate system of Xcoord and Ycoord
used in the file must match the coordinate system used in the gridded DSS records. Typically the coordinate
system will be either hydrologic rainfall analysis project (HRAP) or standard hydrologic grid (SHG).
Parameter keyword definitions.
Keyword Definition Units
XCoord x-coordinate of the southwest corner of integer value

the cell
YCoord y-coordinate of the southwest corner of the integer value

cell
TravelLength travel time index from the cell to the kilometers

subbasin outlet
Area area of cell within the subbasin square kilometers
The data for a subbasin begins with the keyword "Subbasin" followed by a colon and the subbasin identifier.
One line beginning with the keyword "Grid Cell" follows for each cell in the subbasin. Data for the subbasin
ends with the keyword "End". Keywords are not case sensitive and may contain spaces. Blank lines can be
included and lines beginning with "#" are ignored as comments. The same grid-cell file can be referenced by
more than one subbasin, allowing data for many subbasins to be stored in the same file. The identifier for a
subbasin must be exactly the same in the grid-cell file as it is in the basin model.
Parameter Order: Xcoord YCoord TravelLength Area
Grid Cell File Format – 815

End:
Subbasin: 85
Grid Cell: 633 359 88.38 3.76
Grid Cell: 634 359 84.51 0.18
Grid Cell: 633 358 85.55 16.13
Grid Cell: 632 358 82.55 12.76
Grid Cell: 625 348 13.75 12.07
Grid Cell: 626 348 17.12 0.09
Grid Cell: 622 347 21.19 3.26
Grid Cell: 623 347 15.56 9.96
End:
Subbasin: 86
Grid Cell: 637 361 59.13 6.79
Grid Cell: 638 361 59.04 6.95
Grid Cell: 636 361 56.68 1.17
Grid Cell: 636 360 55.08 16.38
Grid Cell: 636 347 67.96 2.45
Grid Cell: 637 347 71.72 7.41
Grid Cell: 638 347 72.57 8.78
Grid Cell: 639 347 73.32 0.04
End:
Sample grid cell file.
Grid Cell File Format – 816

27 HEC-HMS and HEC-1 Differences

Development of the Hydrologic Modeling System (HEC-HMS) was initiated as part of the Next Generation
Software Project to succeed the aging HEC-1 program for simulating the rainfall-runoff process. However, it
was not designed to simply add a graphical user interface to the old program. Instead it was designed to use
advances in engineering and computer science wherever possible to improve the quality of simulation
results. The modernization process has therefore resulted in some changes in how computations are
performed. While these modernizations result in computation differences between the two programs, the
HEC-HMS results are preferred because of the modern techniques that have been implemented. Changes in
parameter specifications or computations are detailed in the following sections.
27.1 Recession Baseflow

The recession baseflow method includes a recession constant for specifying the rate at which recession
flow decreases with time. In HEC-HMS the parameter is defined as the ratio of the current recession flow to
the recession flow one day earlier. The HEC-1 parameter, called RTIOR, is defined as the ratio of the current
recession flow to the flow one hour later. The following equation can be used to convert an HEC-1 recession
constant for use in HEC-HMS:
This conversion is automatically applied when importing a HEC-1 file.
27.2 Clark Unit Hydrograph

The Clark method produces a unit hydrograph that theoretically has an infinite number of ordinates, because
each ordinate on the tail of the unit hydrograph is computed by multiplying the preceding ordinate by a
constant fraction. In both HEC-HMS and HEC-1, the tail of the unit hydrograph is truncated when the volume
represented by the unit hydrograph exceeds 99.5% of the unit depth. In HEC-HMS the ordinates are then
adjusted using a flow weighting scheme to produce a volume of exactly 100%. No adjustment was made in
HEC-1.
27.3 Muskingum Cunge Routing

Hydraulic properties of channels and cross sections are computed differently in HEC-HMS and HEC-1.
27.3.1 General Channel Properties

In HEC-HMS, properties are computed from the physical properties of the channel, whereas in HEC-1 the
properties are computed with formulas based on the kinematic wave assumption. In HEC-HMS the cross-
sectional flow area is computed as:
HEC-HMS and HEC-1 Differences – 817

and the ratio of wave speed, c, to flow velocity, v, is:
where w is the bottom width, z is the side slope, and y is the flow depth. Velocity is computed using
Manning's formula and the properties of the cross section.
In HEC-1 the cross-sectional flow area is computed as:
and the wave speed, c, is computed as:
where and m are kinematic parameters based on the channel shape.
27.3.2 Eight Point Cross Sections

In HEC-HMS the flow depth for a given discharge is determined from the cross section properties and then
area, top width, and wave speed are computed for that depth using the cross section properties. In HEC-1 the
discharge, area, top width, and wave speed are computed for 20 depths and stored in a table. During the
routing process, area, top width, and wave speed were interpolated from the table for each discharge value.
HEC-HMS guarantees that the area, top width, and wave speed are computed exactly for each discharge
value.
27.4 Kinematic Wave Routing

Extensive testing of the kinematic wave routing method determined that an error exists in the method as
implemented in HEC-1 whereas the calculations are performed correctly in HMS. For each time step, the
cross sectional flow area must be calculated at each node in the reach. In HEC-1 this was done incorrectly
for the first node, where it used the inflow from the previous time step to compute area instead of the inflow
for the current time step. This seemingly small difference in the routing algorithms can lead to differences in
the routed peak flow. So far differences of up to 5% have been observed.

27.5 Ogee Spillway Flow

Calculation of the flow coefficient for the spillway is typically broken into several ranges, with different
equations used to calculate the coefficient for each range. HEC-1 used two main ranges separated by the
criteria of effective head equal to 1.3 times the design head. Below the criteria, the flow coefficient was
calculated using results from laboratory experiments. Above the criteria, the coefficient was calculated using
a normal depth assumption. The low end of the upper range resulted in calculated spillway flows less than
the flow at design head. A linear smoothing was used to transition between the two ranges. HMS uses only a
single range, computing the flow coefficient only from experimental results. The HMS results do not have
any breaks or transitions in flow as the head on the spillway increases above the design head.
27.6 Green and Ampt Infiltration

Computing infiltration using the Green and Ampt method includes computing the time to ponding. The time
to ponding is the length of time required for the precipitation to saturate the soil so that surface runoff
begins. In some circumstances, the precipitation rate may decrease after the ponding condition is satisfied.
Once this happens, there may not be enough precipitation to maintain the ponding condition. When the
precipitation rate increases again the calculations must be adjusted to resatisfy the ponding condition.
HEC-1 did not perform this adjustment correctly and would convert all precipitation to excess during any time
step when the adjustment was required. HEC-HMS correctly switches between ponded and unponded
conditions.

28 Terms and Conditions of Use

Use of the program is governed by the terms and conditions of use. They limit what can be done with the
program software, waive warranty, limit liability, and indemnify the developers and the United States
government. The program cannot be used unless the terms and conditions of use are accepted; the full text
is given below.
The United States Government, US Army Corps of Engineers, Hydrologic Engineering Center ("HEC") grants to
the user the rights to install Hydrologic Modeling System (HEC-HMS) "the Software" (either from a disk copy
obtained from HEC, a distributor or another user or by downloading it from a network) and to use, copy and/
or distribute copies of the Software to other users, subject to the following Terms and Conditions of Use:
All copies of the Software received or reproduced by or for user pursuant to the authority of this Terms and
Conditions of Use will be and remain the property of HEC.
User may reproduce and distribute the Software provided that the recipient agrees to the Terms and
Conditions for Use noted herein.
HEC is solely responsible for the content of the Software. The Software may not be modified, abridged,
decompiled, disassembled, unobfuscated or reverse engineered. The user is solely responsible for the
content, interactions, and effects of any and all amendments, if present, whether they be extension modules,
language resource bundles, scripts or any other amendment.
The name "HEC-HMS" must not be used to endorse or promote products derived from the Software.
Products derived from the Software may not be called "HEC-HMS" nor may any part of the "HEC-HMS" name
appear within the name of derived products.
No part of this Terms and Conditions for Use may be modified, deleted or obliterated from the Software.
No part of the Software may be exported or re-exported in contravention of U.S. export laws or regulations.
Waiver of Warranty
THE UNITED STATES GOVERNMENT AND ITS AGENCIES, OFFICIALS, REPRESENTATIVES, AND
EMPLOYEES, INCLUDING ITS CONTRACTORS AND SUPPLIERS PROVIDE HEC-HMS \"AS IS,\" WITHOUT ANY
WARRANTY OR CONDITION, EXPRESS, IMPLIED OR STATUTORY, AND SPECIFICALLY DISCLAIM ANY
IMPLIED WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-
INFRINGEMENT. Depending on state law, the foregoing disclaimer may not apply to you, and you may also
have other legal rights that vary from state to state.
Limitation of Liability
IN NO EVENT SHALL THE UNITED STATES GOVERNMENT AND ITS AGENCIES, OFFICIALS,
REPRESENTATIVES, AND EMPLOYEES, INCLUDING ITS CONTRACTORS AND SUPPLIERS, BE LIABLE FOR
LOST PROFITS OR ANY SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF OR IN
CONNECTION WITH USE OF HEC-HMS REGARDLESS OF CAUSE, INCLUDING NEGLIGENCE.
THE UNITED STATES GOVERNMENT'S LIABILITY, AND THE LIABILITY OF ITS AGENCIES, OFFICIALS,
REPRESENTATIVES, AND EMPLOYEES, INCLUDING ITS CONTRACTORS AND SUPPLIERS, TO YOU OR ANY
THIRD PARTIES IN ANY CIRCUMSTANCE IS LIMITED TO THE REPLACEMENT OF CERTIFIED COPIES OF
HEC-HMS WITH IDENTIFIED ERRORS CORRECTED. Depending on state law, the above limitation or exclusion
may not apply to you.
Indemnity
Terms and Conditions of Use – 820

As a voluntary user of HEC-HMS you agree to indemnify and hold the United States Government, and its
agencies, officials, representatives, and employees, including its contractors and suppliers, harmless from
any claim or demand, including reasonable attorneys' fees, made by any third party due to or arising out of
your use of HEC-HMS or breach of this Agreement or your violation of any law or the rights of a third party.
Assent
By using this program you voluntarily accept these terms and conditions. If you do not agree to these terms
and conditions, uninstall the program and return any program materials to HEC (If you downloaded the
program and do not have disk media, please delete all copies, and cease using the program.)
Terms and Conditions of Use – 821

29 Release Notes
29.1 v4.11.0 Release Notes

Initial beta release: 12 Sep 2022
Final version release: 14 Jul 2023
29.1.1 New Features
29.1.1.1 Gridded Precipitation Storm Center Parameterization

The Precipitation Gridset shared component data has been enhanced to allow you to parameterize storm
center x coordinate and y coordinate. A calculate option has been included that allows you to automatically
calculate the coordinates where the greatest precipitation accumulation occurs over the temporal extent of
the gridset. This feature supports the gridded storm transposition feature that is also included in this release.
Release Notes – 822

724 Define the gridded precipitation X and Y coordinates
For more, see Transposing Gridded Precipitation66.

This feature was funded by the USACE General Investigations program. Initial code implementation was
performed by Lauren Coe and Tom Brauer. Documentation and testing was performed by Lauren Coe, Greg
Karlovits, and Tom Brauer.
29.1.1.2 Gridded Storm Transposition

The Gridded Precipitation method in the meteorologic model has been enhanced to allow transposition of
gridded precipitation. The storm center of the gridded precipitation record is transposed to the new location
specified in the gridded precipitation component editor.
66 https://www.hec.usace.army.mil/confluence/display/HMSGUIDES/Transposing+Gridded+Precipitation

For more, see Transposing Gridded Precipitation67.

performed by Tom Brauer. Documentation and testing was performed by Lauren Coe, Greg Karlovits, and
Tom Brauer.
29.1.1.3 Gridded Storm Optimization

New capability has been added to the Gridded Precipitation method and Optimization Trial to allow
optimization of storm center coordinates. The optimization framework can iteratively transpose the storm
center to maximize flow or stage at a specified location in the basin model.

For more, see Optimizing Gridded Precipitation68.

performed by Tom Brauer. Documentation and testing was performed by Lauren Coe, Greg Karlovits, and
Tom Brauer.
29.1.1.4 Gridded Storm Uncertainty and Stochastic Storm Transposition

New capability has been added to the Gridded Precipitation method and Uncertainty Analysis to allow
gridded precipitation datasets and storm center coordinates to be sampled, and for summary statistics of
each random sample to be captured. This works similarly to the Optimization Trial, without having a directed
goal of maximization or minimization of an objective function. Randomly selecting precipitation gridset, x
coordinate, and y coordinate can be used to achieve stochastic storm transposition (SST). For more, see
https://youtu.be/AZMGbCK4d7w.
68 https://www.hec.usace.army.mil/confluence/display/HMSGUIDES/Optimizing+Gridded+Precipitation

Additionally, Parameter Value Sample paired data were created for storm x and y coordinates so that the
Specified Values sampler can be used in the uncertainty analysis:

This work was funded by FEMA through the Future of Flood Risk Data (FFRD) initiative. Initial code
implementation was performed by Tom Brauer. Documentation and testing was performed by Greg
Karlovits, and Tom Brauer.
29.1.1.5 Optimization of Total Storm Precipitation

The option to optimize a Precipitation time-series and Total Precipitation statistic was added to the
Optimization Trial Objective Function. The use case is to allow the user to determine storm properties that
maximize precipitation volume over an element, independent of any hydrologic processes. This would allow
for optimization of any storm parameters that change the amount of precipitation applied to an element, for
example HMR-52 parameters or gridded precipitation centering.
This work was funded by FEMA through the Future of Flood Risk Data (FFRD) initiative. Code,
documentation, and testing was performed by Greg Karlovits.

29.1.1.6 Spatially Variable Hypothetical Storm

The storm depth for the Hypothetical Storm meteorologic model can now be entered or calculated from
precipitation-frequency grid separately for each subbasin. The user can select either the Variable By
Subbasin or Uniform For All Subbasins option from the Spatial Distribution menu.
725 New 'Spatial Distribution' option for the Hypothetical Storm
If Variable by Subbasin option is selected, the point depths can be entered separately for each subbasin in
the subbasin meteorology editor or calculated automatically by HEC-HMS. HEC-HMS will average grid cell
values in the frequency-precipitation grid within each subbasin's extent.
726 Entering depth in subbasin meteorologic model editor

For more, see A69pplying New Hypothetical Storm Enhancements70 and Applying the Hypothetical Storm Met
Model in HEC-HMS71.
29.1.1.7 Precipitation-Frequency 10-min, 30-min, and 3-day depths

The Frequency Storm method now allows users to add 10 minute, 30 minute, and 3 day depths for creating a
balanced hyetograph.
70 https://www.hec.usace.army.mil/confluence/display/HMSGUIDES/Applying+New+Hypothetical+Storm+Enhancements
71 https://www.hec.usace.army.mil/confluence/display/HMSGUIDES/Applying+the+Hypothetical+Storm+Met+Model+in+HEC-HMS

In HEC-HMS version 4.10 and below, the 10 minute and 30 minute depths were computed internally using the
Hydro-35 equations. When migrating HEC-HMS projects version 4.10 and below, HEC-HMS will compute 10
minute and 30 minute depths and add them to the component editor using the Hydro-35 equation which will
maintain the same frequency storm in 4.11. If users have the Storm Duration set to 4 days or higher and
migrating to 4.11, HEC-HMS will compute the 3-day depth based off a log interpolation between the
"unreduced" 2-day depth and 4-day depth. The inclusion of this 3-day depth will likely create a slightly
different balanced hyetograph than the balanced hyetograph created in prior versions. Benchmark tests
have shown differences less than 1% but could vary depending on the watershed. More information on how
the Frequency Storm computes its depths is described here72.
29.1.1.8 Precipitation Frequency Depths Tabular Export

The Frequency Precipitation Calculator was added in v.4.10 and is used to quickly calculate average
precipitation depths and apply new precipitation depths at either the watershed or subbasin level. These
calculated values are displayed in the Precipitation-Frequency Depths Table Dialog. New features have been
added to the Frequency Depths Table Dialog including an Edit and Export button. The Export button will allow
the unedited precipitation depths to be exported to a CSV file. The user can enable editing to change
precipitation depth values in the table with the Edit button. Editing values will disable the Export button.
The generated CSV file will contain a header with pertinent model data and the Precipitation-Frequency
Depths Table. Header data will include a timestamp of when the depths were exported, Basin Model name,
and Meteorologic Model name.
72 https://www.hec.usace.army.mil/confluence/display/HMSTRM/Frequency+Storm+3-Day+Depth+Compute

29.1.1.9 Interpolated Longwave Radiation, Humidity, and Atmospheric Pressure

Interpolation methods were added for longwave radiation, humidity, and atmospheric pressure within the
meteorologic model. These options interpolate between one or more gaged locations and create a series of
grids (if interpolating over a gridded domain) or time-series at point locations (if interpolating over a non-
gridded domain). The interpolation methods include inverse-distance squared, inverse-distance, nearest-
neighbor, and bilinear. The interpolated result is cached to disk in an HEC-DSS file. The cached result is
accessed on subsequent computes unless a parameterization change occurs invalidating the cache and
triggering a re-compute. The time-series gages that are selected for interpolation must be parameterized
with a valid longitude and latitude.
This feature was funded by the Northwestern Division (NWD) - Columbia River office, the Mississippi River
Geomorphology & Potamology (MRGP) program, and the USACE Arid Regions Work Unit within the Flood and
Coastal Systems Research and Development (R&D) program. Initial code implementation was completed by
Mike Bartles. Documentation and testing was completed by Mike Bartles and Matt Fleming.
29.1.1.10 Stefan Boltzmann Longwave Radiation

This new meteorologic method allows for the estimation of longwave radiation based upon the air
temperature and relative humidity of the location in question (i.e., grid cell and/or subbasin). This method is
described within TVA (1972) and Follum et al, (2015)73.
This feature was funded by NWD, MRGP, and Arid Regions R&D Work Unit. Initial code implementation was
completed by Mike Follum, Dan Hamill, Mike Bartles, and Tom Brauer. Documentation and testing was
completed by Mike Bartles, Dan Hamill, Avital Breverman, Paul Ely, and Tom Brauer.
29.1.1.11 Reduced Solar Constant Shortwave Radiation

This new meteorologic method allows for the estimation of shortwave radiation based upon the elevation,
slope, and aspect of the location in question (e.g., grid cell and/or subbasin). This method is described
within TVA (1972) and Follum et al, (2015)74.

completed by Mike Bartles, Dan Hamill, Avital Breverman, and Tom Brauer.
29.1.1.12 Precipitation Index Humidity

This new meteorologic method allows for the estimation of relative humidity based upon precipitation of the
location in question (e.g., grid cell and/or subbasin). This method is described within Anderson (2006)75 and
Follum et al, (2015)76.
completed by Mike Bartles, Dan Hamill, Avital Breverman, Paul Ely, and Tom Brauer.
29.1.1.13 Barometric Atmospheric Pressure

This new meteorologic method allows for the estimation of atmospheric pressure based upon the elevation
of the location in question (e.g., grid cell and/or subbasin). This method is described within Anderson
(2006)77 and Follum et al, (2015)78.
completed by Mike Follum, Dan Hamill, and Mike Bartles. Documentation and testing was completed by
Mike Bartles, Dan Hamill, Avital Breverman, and Paul Ely.
29.1.1.14 Atmospheric Pressure, Wind Speed, Humidity, Longwave Radiation, and

Net Shortwave Radiation Spatial Results
Atmospheric Pressure, wind speed, humidity, longwave radiation, and net shortwave radiation have been
added to the list of available spatial results when using the energy budget snowmelt method.
completed by Mike Bartles. Documentation and testing was completed by Mike Bartles and Matt Fleming.
29.1.1.15 Optimization Trial Improvements
29.1.1.15.1 Relative Simplex Tolerance
For the Simplex search method in the Optimization Trial, the option to assess convergence based on relative
tolerance was added. Previously, the convergence was assessed based on absolute tolerance, which
checked to see if the absolute difference between objective function values at nodes of the simplex were all
below the specified criterion. This meant that the magnitude of the objective function affected the
determination of convergence. For example, the user would need to set a larger value for tolerance for the
Sum of Squared Errors objective function than for the RMSE function for the trial to converge in a similar
75 https://www.weather.gov/media/owp/oh/hrl/docs/22snow17.pdf
77 https://www.weather.gov/media/owp/oh/hrl/docs/22snow17.pdf

number of iterations because values of the SSE objective function are generally orders of magnitude larger
than for RMSE. Now the user can choose the Relative tolerance criterion, which compares relative
differences between the nodes of the simplex, and is less sensitive to the magnitude of the objective
function values. For general use, the Relative option is preferred, but the default option is Absolute for
backwards compatibility.
For more, see Apply Simplex Search Optimization Trials79.

This work was funded by the HH&C Science and Engineering Technology (SET) program. Code,
29.1.1.15.2 Run Final Iteration of Optimization Trial with Best Parameter Set
In prior versions of HEC-HMS, the results shown for a Trial reflected the last evaluation of the search prior to
termination, which was generally not the best parameter set. This meant that Element summaries such as a
Graph view or Summary Table did not reflect the optimized parameter set. In HEC-HMS 4.11, when the
search terminates because it has converged, the Trial will run one final evaluation of the model using the
optimized parameter set, which updates all Trial results to reflect a simulation using that best parameter
set. This ensures that all results in an Optimization Trial are finalized using the optimized parameter set
shown in the Optimized Parameters table.
727 Final parameter set from optimization trial
79 https://www.hec.usace.army.mil/confluence/hmsdocs/hmsguides/working-with-optimization-trials/applying-simplex-and-differential-
evolution-optimization-to-single-event-calibration/applying-the-simplex-optimization-search-method-for-single-event-calibration/apply-
simplex-search-optimization-trials

29.1.1.15.3 Optimization Results Reported by Evaluation Instead Of Iteration
Previously, values for the objective function and parameters were stored to the project DSS file (and shown
in the results graphs and tables) for each iteration based on the last evaluated parameter set for that
iteration. This tended to understate the variability in the parameters and objective function value as the
search was reaching convergence, and fail to communicate the range over which a Trial was searching
parameters. Now, the results are stored and displayed for each evaluation (every time the model runs with a
new parameter set) so that the actual variability in the parameters and objective function are visible as the
search proceeds.
728 Objective function values saved for each evaluation
29.1.1.15.4 Parameter Scale Factor Optimization
The option to use scale factors on all subbasins in an optimization trial already exists for a number of
processes and methods, such as Deficit and Constant loss. The framework is being expanded to include
other processes and methods to facilitate parameter optimization in complex watershed models. Scale
factor optimization was enabled for the three Simple Canopy parameters: Initial Storage, Max Storage, and
Crop Coefficient and for Clark transform Time of Concentration and Storage Coefficient.

729 Ability added to use scale factors when choosing canopy parameters within an optimization trial
Parameter Scale Factor Optimization was funded by the HH&C Science and Engineering Technology (SET)
program. Code, documentation, and testing was performed by Greg Karlovits.
29.1.1.15.5 Differential Evolution Optimization Minimum Iterations Setting
An additional setting was added to the Differential Evolution optimization search method to require the
search to complete a minimum number of iterations regardless of if it hits the termination (convergence)
criterion. This can avoid the situation where the user has to set a very tiny tolerance in order to get desirable
results. If a search terminates due to converging, and the user raises the minimum number of iterations
above the current number of iterations, the search will pick up where it left off and continue until it hits at
least the new minimum iteration limit.
730 Minimum iterations option for a trial using the differential evolution search method
This feature was funded by the HH&C Science and Engineering Technology (SET) program. Code,
29.1.1.16 Ensemble Compute

A new compute type called the Ensemble Compute has been added to HEC-HMS. Ensemble modeling is a
process whereby multiple base models are created and simulated in a collective fashion to predict an
outcome. Each base model may include different basin configurations, modeling methods, parameter sets,

initial conditions, and/or boundary conditions. As long as the base models are diverse and independent, the
prediction error of the base models decrease when the ensemble modeling approach is used. While the
ensemble model is composed of multiple models, it acts and performs as a single model. Currently, the
ensemble compute can be made up of different simulation runs or forecast alternatives. The time-series
output types that are currently compatible within an ensemble analysis in HEC-HMS include outflow,
reservoir elevation, incremental precipitation, LWASS, SWE, cumulative outflow, cumulative precipitation,
moisture deficit, and air temperature.
The below plot shows how flow computations at a basin element vary for a specific event depending on the
precipitation data source used (AORC, MRMS, Interpolated Gages, etc.). The plot shows the individual
ensemble traces (simulation run results) as well as several statistical time-series computed from the traces
(mean, max, min, etc.).
For more, see E80nsemble A81nalysis Simulations in HEC-HMS82.

Initial code and implementation were done by Josh Willis. Testing and documentation were done by Matt
Fleming and Josh Willis.
29.1.1.17 Snow Modeling Improvements
29.1.1.17.1 Temperature Index Zonal Editors
The new Temperature Index Zonal Editor allows for editing of Snow Method parameters that utilize
Temperature Index or Gridded Temperature Index methods within a Forecast Alternative. Parameter
81 https://www.hec.usace.army.mil/confluence/display/HMSGUIDES/Ensemble+Analysis+Simulations+in+HEC-HMS
82 https://www.hec.usace.army.mil/confluence/display/HMSGUIDES/Ensemble+Analysis+Simulations+in+HEC-HMS

adjustments can be made within defined zones (groups) of elements, or to individual elements within the
zones.
For more information, see Adjusting Parameters for the Forecast83.

This feature was funded by the Corps Water Management System (CWMS) National Implementation
Program. Initial code and implementation were done by Daniel Black. Testing was done by Matt Fleming
and Mike Bartles.
29.1.1.17.2 Hybrid / Radiation-derived Temperature Index (RTI) Snowmelt
The Hybrid snowmelt method (also known as the Radiation-derived Temperature Index, RTI, method) utilizes
additional factors to compute a proxy energy available for snowmelt. This representative energy is derived
from radiation computations that include simple estimates of net shortwave and longwave radiation (Follum
et al, 201584). Net shortwave radiation includes topographic, cloud cover, vegetation, and albedo effects
while net longwave radiation includes contributions from the air, vegetation, cloud cover, and approximate
snow temperature. Currently, no additional meteorologic boundary conditions are required to use this
method within HEC-HMS. In order to compute net shortwave radiation, topographic shading must be
preprocessed. These topographic shading computations are only required once and can be reused in
subsequent simulations. Outputs that are computed by this method include:
• Liquid Water at the Soil Surface (LWASS)
• Snow Water Equivalent (SWE)
• Effective Albedo
• Liquid Water Content (LWC)
• Antecedent Temperature Index
• Heat Deficit
• Radiation Temperature
Colorado can be found here: Evaluating Gridded Hybrid/RTI Snowmelt Parameter Sensitivity85.
83 https://www.hec.usace.army.mil/confluence/hmsdocs/hmsum/4.11/forecasting-streamflow/adjusting-parameters-for-the-forecast
using-the-uncertainty-analysis/evaluating-gridded-hybrid-rti-snowmelt-parameter-sensitivity

A tutorial and guide demonstrating the use of the Gridded Hybrid snow method can be found
here: Gridded Hybrid: Upper Truckee River86.
A presentation describing this new snow method can be found here: http://youtube.com/watch?
v=TLCKDxQUhyY
This feature was funded by the USACE Arid Regions work unit within the Flood and Coastal Systems
Research and Development program. Initial code implementation was performed by Dan Hamill, Mike
Bartles, Avital Breverman, Bill Scharffenberg, and Mike Follum. Documentation and testing was completed
by Dan Hamill, Mike Bartles, and Avital Breverman.
29.1.1.17.3 Energy Budget Snowmelt
A new Energy Budget snowmelt method was added for version 4.11. This new method is based on the Utah
Energy Budget (UEB) Model developed at Utah State University by Tarboton et al (1995)87. A single layer is
used within this method to represent the energy stored in the snowpack and the upper part of the ground
which has a thermal interaction with the snowpack. The snowpack has a depth-averaged temperature which
is related to the stored energy. An energy budget is computed between the snowpack surface and surface
temperature, then the surface temperature is used to compute the change in the snowpack energy content
over a time interval. The change in snow water equivalent is affected by the energy content for the time
interval.
Boundary conditions that are required to use this method include:
• Shortwave Radiation
• Longwave Radiation
• Precipitation
• Air Temperature
• Wind Speed
• Atmospheric Pressure
• Relative Humidity
Outputs that are computed by this method include:
• LWASS
• SWE
• Albedo
• Snow Pack Energy
• Snow Pack Temperature
• Snow Surface Temperature
• Snow Pack Condensation
• LWC
• Snow Depth
86 https://www.hec.usace.army.mil/confluence/hmsdocs/hmsguides/modeling-snowmelt/calibrating-gridded-snowmelt-upper-truckee-
river-california/option-2-gridded-hybrid-upper-truckee-river
87 https://hydrology.usu.edu/snow/uebgrid/
#:~:text=The%20Utah%20Energy%20Balance%20(UEB,of%20water%20and%20energy%20balance.

Colorado can be found here: Evaluating Energy Budget Snowmelt Parameter Sensitivity88.
A tutorial and guide demonstrating the use of the Banded Energy Budget snow method can be
found here: Energy Budget: Swamp Angel Study Plot, Colorado89.
A tutorial and guide demonstrating the use of the Gridded Energy Budget snow method can be
found here: Gridded Energy Budget: Upper Truckee River90.
A presentation describing this new snow method can be found here: http://youtube.com/watch?
v=TLCKDxQUhyY
This feature was funded by the Northwestern Division - Columbia River office. Initial code implementation
was performed by Mike Bartles, Avital Breverman, Paul Ely, and Bill Scharffenberg. Documentation and
testing was completed by Mike Bartles, Avital Breverman, Matt Fleming, Jeremy Giovando, and Chandler
Engel.
29.1.1.17.4 Expanded Parameter Selection for Uncertainty Analysis Snowmelt Parameter Value
Samples
The Uncertainty Analysis compute type had a limited selection of snowmelt parameters to select from when
using the Specified Values option. The full suite of snowmelt parameters can now be selected in the Paired
Data and as a Parameter in the Uncertainty Analysis.
using-the-uncertainty-analysis/evaluating-energy-budget-snowmelt-parameter-sensitivity
89 https://www.hec.usace.army.mil/confluence/hmsdocs/hmsguides/modeling-snowmelt/calibrating-point-snowmelt-swamp-angel-
study-plot-colorado/option-3-energy-budget-swamp-angel-study-plot-colorado
90 https://www.hec.usace.army.mil/confluence/hmsdocs/hmsguides/modeling-snowmelt/calibrating-gridded-snowmelt-upper-truckee-
river-california/option-3-gridded-energy-budget-upper-truckee-river

29.1.1.18 Dynamic Surface and Gridded Dynamic Surface

Dynamic Surface and Gridded Dynamic Surface were added to the Surface method for post wild-fire
conditions. This method allows the infiltration rate to change over time to account for changes to the
infiltration as a result of watershed burn and recovery. Infiltration rates eventually will return to their pre-fire
rates. There are currently three infiltration methods within Dynamic Surface to limit and recover infiltration
rates: Pak & Lee, User-Specified, and None option. The purpose of this new surface capability is to model the
recovery of infiltration after a fire to which directly impacts runoff generation. This method can be used for
predicting flash floods over burned watersheds and debris flows.

For more information, see Applying the Dynamic Surface | Pak and Lee Method for Post-wildfire Hydrologic
Modeling91.
This feature was funded by the USACE Arid Regions work unit within the Flood and Coastal Systems
Research and Development program. Initial code implementation was performed by Jay Pak and Paul Ely.
The Component Editor Interface was performed by Nick Van and David Ho. Global Editor Interface was
performed by David Ho. Documentation and testing were completed by Jay Pak and David Ho.
29.1.1.19 2D Diffusion Wave and Sediment Transport Enhancements
29.1.1.19.1 Multiple 2D Meshes within a Single Basin Model
The ability to use multiple 2D meshes within a single basin model was added within version 4.11. This
allows for the use of the 2D Diffusion Wave transform within multiple subbasins in a single simulation.
This work was funded by FEMA through the FFRD initiative. Initial code implementation, documentation, and
testing was performed by Mike Bartles.
29.1.1.19.2 2D Solver
Both the HEC-RAS and HEC-HMS team make continual improvements to the shared 2D Solver and this
release contains the latest rollup of fixes and improvements. These changes were made to improve
computational speed, stability, and accuracy of the 2D results. As such, you may notice subtle changes in
hydraulic results. Please see the latest HEC-RAS v6.4 Release Notes92 for further details.
91 https://www.hec.usace.army.mil/confluence/display/HMSGUIDES/Applying+the+Dynamic+Surface+
%7C+Pak+and+Lee+Method+for+Post-wildfire+Hydrologic+Modeling
92 https://www.hec.usace.army.mil/confluence/rasdocs/rasrn/hec-ras-6-4-new-features

Initial code implementation and documentation for this feature was performed by Alejandro Sanchez and
Mike Bartles. Testing was completed by Alejandro Sanchez, Jay Pak, Natasha Sokolovskaya, and Mike
Bartles.
29.1.1.20 Separate Output for Linear Reservoir Baseflow Layers

The Linear Reservoir Baseflow method allows users to set up to 3 subsurface layers when modeling
baseflow. Results from each baseflow layer can now be viewed in the Results tab in HEC-HMS and in the
output HEC-DSS file.
731 Subbasin element results highlighting separate results for each linear reservoir baseflow layer

732 Linear reservoir layer 1 and 2 results
This feature was funded by the Omaha District, USACE (NWO). Initial code implementation was completed by
David Ho. Documentation and testing was completed by David Ho and Matt Fleming.
29.1.1.21 Sediment Modeling Improvements
29.1.1.21.1 Sediment Volume Time-Series Type
When sediment is enabled for a basin model and a simulation is computed, sediment load computations are
converted to sediment volume estimates using user-specified unit weights for each soil texture type (clay,
silt, sand, etc.). The time-series results are written to disk and can be viewed on the Results tab under the
Sediment node. The Sediment Volume Time-Series results were added by Josh Willis. Documentation and
testing were completed by Josh Willis and Jay Pak.

733 Sediment Volume Time-Series Results
Changes were made to the C-Part of the DSS pathname when writing sediment volume time-series to an
output HEC-DSS file. "SEDIMENT-COMBINE" entries which used to represent incoming sediment loads are
now written as "SEDIMENT LOAD-COMBINE" to differentiate from "SEDIMENT VOLUME-COMBINE". The C-
Part name "SEDIMENT-OUT" used to represent outgoing sediment load but now are written as "SEDIMENT
LOAD-OUT" to differentiate from "SEDIMENT VOLUME-OUT".

734 Sediment Results Stored in DSS
29.1.1.21.2 Bulk Flow Time-Series Type
When sediment is enabled for a basin model and a simulation is computed, bulk flow time-series
computations are performed. To create the bulk flow time-series, the total sediment volume time-series is
converted to an instantaneous value and combined with the flow (water-only) time-series. In watershed
where high rates of erosion are computed, the bulk flow time-series can be noticeably larger than the flow
(water-only) time-series. The bulk flow results are written to disk and can be viewed on the Results tab under
the Sediment node. The Bulk Flow Time-Series results were added by Josh Willis. Documentation and
testing were completed by Josh Willis and Jay Pak.

735 Bulk Flow Time-Series Results
29.1.1.21.3 Sediment Global Summary Table
When sediment is enabled for a basin model, sediment load and sediment volume results are computed
during simulation runs. Total sediment load and total sediment volume results can be seen in the Global
Summary Table for each element. Additional sediment volume results, such as a breakdowns of each soil
texture type (clay, silt, sand, etc.), are stored within the .results text file. The Global Summary Table was
updated by Josh Willis. Documentation and testing were completed by Josh Willis and Jay Pak.

29.1.1.21.4 Sediment Delivery Ratio Transport Potential Method
The Sediment Delivery Ratio (SDR) method was added to the Sediment Transport Potential method option
for simulating the amount of sediment/debris by user-specified delivery ratio for each grain size.
The Sediment Delivery Ratio method requires the ratio of each grain class (Clay, Silt, Sand, and Gravel for
the Clay Silt Sand Gravel System/Clay, Silt, Sand, and Gravel, Cobble, and Boulder for the AGU 20 System). A
Ratio number is greater than 1 represents an erosional situation, a Ratio number less than 1 represents a
depositional situation, and a Ratio number equal to 1 is an equilibrium situation.
The Sediment Delivery Ratio (SDR) method was funded by the USACE Arid Regions work unit within the Flood
and Coastal Systems Research and Development program. The initial code implementation was done by
Paul Ely. Documentation was written by Jay Pak. Testing was done by Jay Pak. The Component/Global
Editor Interface was performed by Danial Black, Nick Van and David Ho.
29.1.1.21.5 Muskingum Sediment Reach Routing Method
The Muskingum method was added to the sediment reach routing method option to route sediment/debris
through the stream reach. For each time interval, available sediment is calculated from the upstream
sediment, local erosion, and local deposition. The available sediment in each grain size class is routed using
the Muskingum routing parameters, Attenuation Coefficient and Travel time. This allows sediment of
different grain sizes to move at different speeds and allow for attenuation through the reach.

The Muskingum method was funded by the USACE Arid Regions work unit within the Flood and Coastal
Systems Research and Development program. The initial code implementation was done by Paul
Ely. Documentation was written by Jay Pak. Testing was done by Jay Pak. The Component/Global Editor
Interface was performed by Danial Black, Nick Van and David Ho.

29.1.1.22 Rule-Based Reservoir Operations and Related Features

A simple implementation of rule-based reservoir operations has been added to HEC-HMS. The method
extends the Outflow Structures reservoir method and allows the reservoir to operate moveable gates to
achieve simple rule-based objectives. For the reservoir's release logic to be able to modify releases, the
General Outlet and Gated Orifice Outlet have been added to the rule-based reservoir operations outlet types
(see below). Spillway gates now have the option to be moved by an operations controller, or by time-series
or pattern (see below).
736 Rule-based operations reservoir method
Using rule-based operations requires the user to define at least one operations zone, which houses a set of
homogeneous rules. Each zone is defined by a maximum elevation, which is a new Paired Data curve type,
the Daily Elevation Pattern.

737 Zone component editor
Each zone has a storage objective, which is also a new Paired Data curve type, the Storage Pattern.
738 Storage objective component editor
Zones may have zero or more rules (they may be set to only operate to the storage pattern, or rule curve, with
no other rules for operation.)
739 Rule component editor
There are 10 types of rules, including Maximum Auxiliary Release, Maximum Downstream Flow, Maximum
Main Release, Maximum Rate Flow Change, Minimum Auxiliary Release, Minimum Downstream Flow,
Minimum Main Release, Specified Auxiliary Release, Specified Downstream Flow, and Specified Main
Release (plus a "None" rule.) Note that any method that has a downstream flow target requires specification
of an element downstream of the reservoir that is used as a target for the operations. The reservoir releases
must iterate in order to achieve a target downstream flow, and this can be computationally expensive.

The two new outlet types are the General Outlet, a simple tool for reproducing reservoir outflow rating curves
in water control manuals, and the Gated Orifice Outlet.
740 New general outlet that can be used to model gated structures
741 Adjustable gates added to orifice outlets

Previously, broad-crested and ogee spillways had the option to use sluice or radial gates, except only with a
fixed opening setting that does not vary throughout the simulation. The ability to operate those gates was
enabled in v4.11.
742 Adjustable gates added to spillways
Disclaimer
The rule-based reservoir operations feature in HEC-HMS is intended to model simple reservoir
operations. Watersheds with complex reservoir operations, including multiple control points,
reservoirs operated as systems, and so on, should be modeled with a more appropriate tool
such as HEC-ResSim.
For more information, see Rule-Based Option for an HEC-HMS Reservoir Element93.
The rule-based reservoir operations method and related features were funded by the USACE Risk
Management Center. The initial implementation and user interface code was completed by Bill
Scharffenberg, Paul Ely, Greg Karlovits, and Nick Van. Documentation was written by Greg Karlovits. Testing
was performed by Matt Fleming and Greg Karlovits.
29.1.1.23 Drainage Area Added to the Basin Element Inventory Table

Cumulative drainage areas are now displayed in the Basin Element Inventory Table, and the formatting of the
table has been generally improved.
93 https://www.hec.usace.army.mil/confluence/display/HMSGUIDES/Rule-Based+Option+for+an+HEC-HMS+Reservoir+Element

743 Drainage area added to the element table
29.1.1.24 Global Editor sorting relabeled from "Hydrologic" to "Watershed Explorer"

The hydrologic order can be rearranged in the Watershed Explorer. This can be considered a "user-specified"
hydrologic order. HEC-HMS does not store multiple states for the HEC-HMS-determined hydrologic order,
and the user-specified hydrologic order. The "Hydrologic" order in the global editors has been relabeled to
"Watershed Explorer" to indicate that the global editor will simply be replicating the order of the elements in

744 The Global Editor will mirror the sorting in the Watershed Explorer
29.1.1.25 Display global editors outside of desktop program setting

The "Display global editors outside desktop" program setting has been removed. With the new global editor
framework global editors are always displayed outside the desktop.
29.1.1.26 Warnings Generated When Flow or Precipitation Ratios Are Applied

Flow and Precipitation Ratios are a setting on the Simulation Run that change the input precipitation or
generated discharge from elements. Occasionally a ratio is set and forgotten about, resulting in unexpected
model results. HEC-HMS did not indicate to the user during a Simulation Run that they were being applied.
Now, HEC-HMS throws a warning when ratios of any kind are applied.

745 Precipitation ratio applied to subbasins in the basin model
746 Warning message showing a ratio was applied to the simulation
29.1.1.27 DSS 7 Migration Utility

A DSS 7 Migration Utility has been added to the Tools | Data | DSS | Migrate to DSS 7 menu. If a project is
open, the utility will default to the project directory. The utility will attempt to migrate all files in a directory
and its subdirectories to HEC-DSS version 7. HEC-DSS version 7 has demonstrated increased performance
over HEC-DSS version 6 and HEC-DSS version 7 is more serviceable by the HEC-DSS team. We recommend
migrating your projects to HEC-DSS version 7.
747 Utility to migrate DSS files to DSS version 7
The initial code implementation completed by Thomas Brauer with review by Nick Van. Documentation was
written by Thomas Brauer. Testing was performed by Matt Fleming.

29.1.1.28 User Interface Themes

A user interface theme selections has been added to the Tools | Program Settings, General tab. The standard
theme is "System" which gives a look and feel consistent with the operating system. Alternative themes
include "Dark" and "Light." The dark theme is shown in the image below.
748 Dark theme UI
29.1.1.29 Vortex Image Exporter

Vortex's Image Exporter utility has been added to the HEC-HMS user interface. The utility exports gridded
data from DSS format to tiff and asc formats. This tool is accessible by navigating to Tools | Data | Image
Exporter. Launch scripts for Vortex utilities are also available when HEC-HMS is closed by navigating to
<hec-hms root>/bin/vortex.
29.1.2 Bugs Fixed

The following bugs were present in previous versions and have been fixed within version 4.11.

29.1.2.1 Snowmelt Parameter Optimization Trials

Support for snowmelt parameters in Optimization Trials was inadvertently removed during the migration of
snowmelt methods from the Meteorologic Model to the Basin Model. Snowmelt parameters are now
available again within Optimization Trials.
29.1.2.2 Snowmelt Uncertainty Analyses

Support for snowmelt parameters in Uncertainty Analyses was inadvertently removed during the migration of
snowmelt methods from the Meteorologic Model to the Basin Model. Snowmelt parameters are now
available again within Uncertainty Analyses. The following snow time series are available as output options
in an Uncertainty Analysis: Snow Water Equivalent (SWE) and Liquid Water at the Soil Surface (LWASS). In
addition, incorrect upper and lower limits were applied to the snowmelt parameters in the Uncertainty
Analysis. The allowable upper and lower limits of the parameters have been corrected.
When performing an Uncertainty Analysis combined with a basin model using the Banded Temperature
Index, Gridded Temperature Index, or Energy Budget snowmelt methods, incorrect upper and lower limits were
applied to the snowmelt parameters. This bug was caused by the migration of snowmelt methods from the
Meteorologic Model to the Basin Model and has been fixed in version 4.11.
When using the Specified Parameter Values Uncertainty Analysis method, the compute type was not
sampling from the Paired Data Table for elevation band temperature index parameters. The bug was caused
by not having the temperature index parameter values set in the Paired Data Editor Panel class and by
references made to the legacy snowmelt methods in the Meteorological Model. This bug has been fixed in
4.11. In addition, Energy Budget and Gridded Hybrid snowmelt parameters can now be selected in the
Specified Parameter Values Uncertainty Analysis method.
29.1.2.3 Subbasin Point Storm Depths would not Clear in Frequency Storm
Meteorologic Model
The storm depths in subbasin met model editor for the Frequency Storm would linger even after the spatial
distribution of the storm was set to be 'Uniform for all Subbasins'. The editor would then re-populate with the
defunct depths when the 'Variable by Subbasin' option was selected again. The error was fixed and the old
depths now clear from the editor.
29.1.2.4 Manual Entry Paired Data Values were not being Saved
Manual entry unit hydrograph paired data curves were not being correctly saved after the modeler created a
new paired data object and then manually entered the data. This behavior could have been seen with other
paired data types as well. The issue was fixed, the program saves manual entry paired data values.
29.1.2.5 Aborted Simulations when New Basin Models Contained Subbasin

Elements Set to use the None Discretization Method
Basin models were missing the Basin_name.sqlite file when all subbasin elements had the None
discretization method selected. This caused aborted simulations. The issue was fixed.

29.1.2.6 Re-delineating Subbasins that use the 2D Diffusion Wave Transform

Method
When re-delineating a basin model that contained at least one subbasin that used the 2D Diffusion Wave
transform method, errors were encountered and the delineation process failed. This error has been rectified
such that the delineation process works as intended.
29.1.2.7 Using Reservoir Elements with a Tailwater Option within the CAVI/HEC-
WAT Model Linking Editor
When attempting to query the available output from a basin model with one or more reservoir elements that
had a tailwater option other than "Assume None" selected, a non-descript error message was thrown. This
error was only encountered within the CAVI/HEC-WAT Model Linking Editor. This error has been fixed such
that the available output is correctly shown.
29.1.2.8 Calibration Summary Table Values are Blank When Element Names
Contain Commas
Previously, calibration summary statistics were not computed if the basin element names contained
commas. This would result in blank values within the calibration summary results table. This omission has
been fixed so that calibration summary statistics are computed whether or not commas are present in the
basin element names.
29.1.2.9 Exporting Table to a non *.csv File Resulted in Corrupt File

The Table Export Dialog was modified to limit table export to an *.csv file. The export was fixed to actually
create a comma delimited file when *.csv export option is selected. Previously, the values were exported to a
tab-delimited file.
29.1.2.10 Not Including *.crs File with a Precipitation Grid Resulted in Abort with no
Message
A clarifying error message was added to both hypothetical storm compute and frequency depth calculator to
indicate when a precipitation frequency grid is missing projection *.crs file.
29.1.2.11 Frequency Precipitation Calculator Aborted with no Message if *.dss File

Was Provided as Source for Precipitation Frequency Grid Data
Frequency precipitation calculator was improved to calculate storm depths from grids with *.dss source
files.

29.1.2.12 Reach Characteristics Table Shows As Blank When a non-Reach Element

is Selected in the Watershed Explorer
Previously when a non-reach element was selected in the watershed explorer, the reach characteristics table
was still accessible and showed up as blank. The logic was corrected to disable access to the reach
characteristics table when a non-reach element is selected. This now mirrors the functionality associated
with subbasin characteristics.
29.1.2.13 Subbasin Characteristics Computations are Aborted with Missing GIS

Data
Previously, if a subbasin boundary did not intersect with the elevation raster data, subbasin characteristics
calculations would immediately abort. Checks have now been added that allow the subbasin characteristics
calculations to proceed to completion. There are checks in place for the subbasin boundary being contained
within the elevation dataset, the subbasin area being sufficiently large enough when compared to the
elevation dataset resolution, and the presence of no-data elevation values within a subbasin boundary. If any
of these cases are present, NaN entries are populated in the subbasin characteristics table and a message
dialog now appears with a description of why NaN values were computed.
29.1.2.14 Modified Puls routing method requiring Elevation-Discharge curve

The elevation-discharge functional curve is an optional selection for Modified Puls routing method but the
compute would show an error stating the elevation-discharge curve was missing when set to None or when
no elevation-discharge curve was present in the model. The issue is fixed where the elevation-discharge
input is optional to compute the simulation.
29.1.2.15 Time-series selection for Uncertainty Analysis not stored

A subset of time-series selected in the uncertainty analysis were not being stored after compute. The code
has been updated such that all time-series results selected in the output results dialog are stored after
computing the uncertainty analysis.
29.1.2.16 Meteorologic time-series not selectable in output results dialog

Meteorologic time-series were not selectable in output results dialog in some cases. This typically occurred
the first time the output results dialog was opened. Subsequent openings of the dialog allowed for
meteorologic results to be selected. This has been addressed so that meteorologic results are always
selectable when the are available.
29.1.2.17 Error 10000 when copying and pasting basin elements

Pasting a copied element would sometimes result in Error 10000. The issue was fixed.

29.1.2.18 Precipitation grid time shift with non-gridded subbasins

Grid time shifts for precipitation were not being properly applied when working with non-gridded (e.g. Clark)
subbasins. Gridded precipitation is typically used in conjunction with gridded (e.g. ModClark) subbasins,
which worked without issue. This issue has been addressed such that grid time shifts for precipitation work
with both gridded and non-gridded subbasins.
29.1.2.19 v2.2 project hangs on open

A v2.2 project hung on open when attempting to convert deficit recovery to evapotranspiration. This issue
has been resolved allowing the v2.2 project to open.
29.1.2.20 Connect upstream subbasin to downstream junction for subbasin-split

with insert junction setting on
On subbasin split, connect the upstream subbasin to the downstream junction when the insert junctions
setting is selected and the subbasin split point is coincident with a reach. Previously the upstream subbasin
was connected to the downstream reach rather than the downstream junction.
29.1.2.21 Switching data source to *.dss for grid data would not save to file
When switching to 'Single Record HEC-DSS' data source from another data source in grid editor, the new data
source file name and pathname would not save to disk. The issue has been fixed.
29.1.2.22 Error 10000 when running a frequency analysis compute

For a frequency ordinate, if the user forgot to specify a meteorologic model or other parameter (i.e. "--None–"
was selected) an Error 10000 was generated during compute. Now this is checked prior to compute and a
useful error note is displayed in the console.
29.1.2.23 Old DSS output remained after changing the number of samples and
recomputing an uncertainty analysis
Previously, if a user reduced the total sample size and reran an uncertainty analysis, some results from the
old run were not overwritten and remained. Logic was added to clean the Uncertainty Analysis DSS output
file when changing the total sample size.
29.1.2.24 Program hangs on open when attempting to forward migrate pre-v4.3

projects with groundmelt pattern in temperature-index snowmelt
The program would hang/freeze on open when attempting to open a pre-v4.3 project in v4.10 or v4.11 if the
project included a groundmelt pattern in the temperature-index snowmelt method. This occurred because
both the groundmelt pattern migration and the migration of snowmelt from the meteorologic model to the
basin model were competing for meteorologic model resources. This issue has been fixed in v4.11.

29.1.2.25 Incorrect error message displayed with FAO56 shortwave and longwave
radiation methods
In some cases the wrong error message was presented when errors were encountered with the FAO56
shortwave or longwave methods.
29.1.2.26 Selecting a 2D Connection as an Reservoir Auxiliary Connection

In previous versions, 2D Connections were not allowed to be selected as an Auxiliary Connection within a
Reservoir element. This issue has been fixed within v4.11.
29.1.2.27 Global editors not opening for multiple basins with similar names
A global editor would not open for a basin if there was one already open for a basin with a name containing
the selected basin's name (e.g. Basin and Basin-1). The issue has been fixed.
29.1.2.28 Terrain reconditioner stalls at times when a smooth drop buffer is

specified
When creating a reconditioned terrain with a smooth drop buffer specified by the user, occasionally HEC-
HMS would stall out. A fix was added to help the operation to proceed to completion.
29.1.2.29 Filtered entries in File Reference Dialog not editable

Filtered reference dialog table entries would not be editable if the filter was applied while a row in the table
was selected that's beyond than the filtered table size. This was fixed.
29.1.2.30 2D Connection description would load to Subbasin description

Description entered for a 2D Connection dialog would load into the subbasin description. This was fixed.
29.1.2.31 Switching between 2D Connection nodes in different basins would lead

to errors
The 2D Connection editor would not update or would cause the program to break if the user switched
between two 2D Connection nodes in different basin models. The error was fixed.
29.1.2.32 Optimization Trial plots, if open, would not update when the objective
time-series and statistic were changed
This issue occurred only when the objective plot (or any of the parameter plots) was open, the user changed
the objective time-series and statistic, and then the user recomputed an optimization trial. Previously, the
plot objective title did not update based on the new objective. The issue has been fixed.

29.1.2.33 Temperature node was not displayed in results for gridded subbasin
This issue occurred when temperature was computed in the meteorology model, but snow was not being
computed in the basin model and the subbasin transform was gridded. Temperature is now displayed in the
results if snow is not computed.
29.1.2.34 Missing Resource for Error 21487

Fixed a missing error resource for Error 21487, switching it to 21451 and updating text to "Gridded or
interpolated precipitation must be used for gridded snow melt."
29.1.2.35 Sediment Results with AGU 20 were not properly calculated

This issue occurred when sediment/debris results were converted from volume to mass in the sediment
model. All 20-grain classes for AGU 20 were not converted in volume to mass unit conversion. Sediment
mass and volume are now displayed consistently for both AGU 20 and Simple 4 (Clay, Silt, Sand, Gavel).
29.1.2.36 Incorrect maximum SWE values saved for an uncertainty analysis

The program was not correctly saving the maximum SWE from the computed SWE time-series. The
computed SWE time-series was correct, but the wrong maximum SWE was reported in the uncertainty
analysis summary table.
29.1.2.37 Grid to Point tool not correctly computing averages for shapefiles with
multiple polygons
The grid to point tool was not computing a separate time series for each polygon in the selected zones
shapefile. Now, the program creates a separate time-series for each polygon using the name attribute as the
b-part pathname.
29.1.2.38 Error in Specified ET when compute buffer length is less than simulation
time window
Specified ET was being written to one time series for a simulation, but the basin model was retrieving the
reference ET from a different time series. Specified ET and the basin model are now working with the same
time series.
29.1.2.39 Rule-Based Reservoir Route method aborts when nothing is changed

Rule-Based reservoir routing will compute 2 or more times to adjust releases when release is based on a
downstream flow condition. While checking if release rules were based on downstream flow, the program
was only looking at rules for the last storage zone that was used. If nothing has changed, the simulation
does not recompute and the last storage zone is not defined. The program was changed to look at release
rules for all storage zones to see if there are rules based on downstream flow.

29.1.2.40 Empty paired data curves causing a fatal error

Selecting an empty paired data curve within the Watershed Explorer and then clicking another component
would cause an error and freeze the program. This issue has been fixed and the program correctly handles
empty manual entry paired data tables.
29.1.2.41 Unknown error when a compute had None basin model, meteorological
model or specifications
Checks were added to produce a proper error message during compute if 'None' was selected for basin
model, met model or specifications in several compute types, including simulation runs, optimization trials,
depth-area-analyses, uncertainty analysis and forecast alternatives.
29.1.2.42 Setting independent parameter to none in uncertainty editor for

regression with additive error would not save
The selection of 'None' would not save for the uncertainty analysis with the 'Regression with Additive Error'
method selection. The error was fixed.
29.1.2.43 New checks added to the Bilinear Interpolation method

The bilinear interpolation method would seem like it failed to interpolated point values. New checks were
added to stop the interpolation and issue error messages when there are less than three gages selected for
interpolation or when the gages do not cover, or bound, all cells in the grid.
29.1.2.44 Debris Flow does not compute sediment when only one runoff value is
above threshold value
A debris flow event is created when runoff is above a threshold value. The event end time was not set
correctly when there is only one runoff value above the threshold value. This has been corrected so sediment
is computed for an event with only one runoff value above the threshold.
29.1.2.45 Flaky UI behavior with rule-based reservoir UI

The program occasionally switches to the Zone tab when editing in the Rule tab. The problem has been
resolved, and the mentioned behavior is no longer present.
29.1.2.46 Synchronize Clark transform component editor and global editor changes
Synchronize Clark transform component editor and global editor changes. This includes all Clark transform
implementations: Standard, Variable, and Maricopa.

29.1.2.47 Header - data mismatch when reordering columns within the Global
Summary Results Table
When the user changed the column order in the Global Summary Results Table and then performed an action
such as sorting the rows alphabetically, the column headers would reset to their default order creating a
mismatch between the column headers and the data underneath them. This issue is now resolved.
29.1.2.48 Synchronize Snow Method Global Editor Changes

When modifying certain parameters or initial conditions in the Snow method global editors, applied changes
were not being recognized within the corresponding component editors. This has been rectified within
v4.11-beta.12.
29.1.2.49 Using the Field Calculator to Estimate Snow Method Parameters

Parameter estimates were not being correctly populated when using the Field Calculator within the Snow
method global editors. This has been rectified within v4.11-beta.12.
29.1.2.50 LA Debris EQs 2-5 did not work with a gridded subbasin
This issue occurred when LA Debris EQs 2-5 was used with the gridded transform method like a Mod-Clark
method. This has been rectified within v4.11-beta.10.
29.1.2.51 Correct graph editor window titles for optimization parameter and
frequency analysis results
Dialog titles were corrected for the optimized parameter results graph and the frequency analysis graph.
29.1.2.52 USGS Long Term Model Global Editor

USGS Long Term Model Global Editor was not opening after changing the method. Global Editor for USGS
Long Term Model now shows up when selected.
29.1.2.53 Changing Linear Reservoir baseflow to another baseflow method

A mesh linear reservoir interflow option was added in v4.8. With this addition, bad user-interface code was
added that prevented changing from Linear Reservoir baseflow to other baseflow methods. This has been
fixed in this version.
29.1.2.54 Global Editors reflect unit system changes

Previously if a global editor was open and the basin or meteorology unit system was changed, that change
would not be reflected in the global editor. This has been fixed in this version.

29.1.2.55 Use Precipitation Parameters for Regression with Additive Error

When attempting to compute an uncertainty analysis using Precipitation Parameters as the independent
variable, the compute would fail. The code was updated so meteorology variables can be used as the
independent variable for Regression with Additive Error.
29.1.2.56 File References table filtering for non-DSS grid

In the File References table, when filtering for grids, the filter would exclude non-DSS gridded data. This has
been fixed so that all gridded data sources are included when filtering.
29.1.2.57 Jython scripting against the Windows-installed version of HEC-HMS

In recent Windows-installed versions of HEC-HMS, some users were unable to pass scripts to HEC-HMS.cmd
due to a class not found exception regarding hms.jar. This bug was not observed with portable versions of
HEC-HMS. This has been rectified within v4.11-beta.12.
29.1.2.58 Missing Observed Data plots for maximization goal optimization

Observed Data plots were not being produced for goodness-of-fit types of maximization goal optimization
(for example, maximization of Normalized Nash Sutcliffe efficiency.) This has been fixed in v4.11-beta.12.
29.1.2.59 Units reverting when trying to change for Paired Data

Units were reverting back to the original default units when switching (i.e. if default was metric and switched
to USCS, after accepting change, would revert back to metric system units). This has been fixed in v4.11-
beta.12.
29.1.2.60 Global Editors do not track rename

Global editors for the Basin Model and Meteorologic Model and the Subbasin and Reach Characteristics
views did not track renames. This has been fixed in v4.11-beta.12.
29.1.2.61 Attempts to rename a basin or meteorological model to a name that is

already in use would remove the basin or meteorological model from the
project
Renaming a basin or meteorologic model to a name that is already in use within the project caused the basin
or meteorologic model to be removed from the project. This has been fixed in v4.11-beta.12.

29.1.2.62 Decreasing number of iterations in optimization search sometimes

caused unknown error
Unspecified error message when decreasing number of iterations in optimization trials was fixed in v4.11-
beta.13.
29.1.2.63 Automatic removal of empty values when pasting from Excel/CSV/Text

causes data misalignment
Any empty values were automatically removed when pasting data from Excel into the program, causing the
pasted data to be condensed and misaligned with the correct timestamps. This problem also occurred when
copying and pasting from CSV or.txt files. This has been fixed in v4.11-beta.13.
29.1.2.64 Broken functionality in Uncertainty Analysis results graphs

Results graphs for Uncertainty Analysis had broken functionality including Zoom To All, View | Hide/Show
Legend, Plot Properties, and Configure Plot Layout. This functionality has been restored in v4.11-beta.13.
29.1.2.65 No error message for incorrectly defined objective function time window
Time window not within the allowable range for the objective function in optimization trial resulted in exiting
compute with an unspecified error message. Checks were added to notify the appropriate error message.
29.1.2.66 Point/Zoom mouse adapter in results plots

Fixed issue in results plots where the zoom/pointer mouse functionality does not persist between computes.
29.1.2.67 Observed sediment load was not accessible from the results tab
Observed sediment load was added to results in v4.11-beta.13.
29.1.2.68 Missing values when using Output Control

When using the output control feature to increase the time step of written results, in some cases the entire
output record was not written. This has been fixed in v4.11-beta.14.
29.1.2.69 Basin and Met Models did not track renames of Gridded Data and Paired
Data
When a Gridded Data or Paired Data is renamed, the elements inside Basin and Met models failed to register
the new gridded data or paired data name. This has been fixed in v4.11-beta.14.

29.1.2.70 Graphs did not open from basin map

When right-clicking on an element to display results graph, the graph did not open. This has been fixed in
v4.11-beta 14.
29.1.2.71 Graph results shown as out-of-date

After a simulation is computed, a graph would show that the results were out-of-date. This has been fixed in
v4.11-beta 14.
29.1.2.72 Sediment results differ with different buffer size

Changing the simulation buffer size caused changes in the sediment results. An error in how the sediment
time series was set for small buffer sizes was fixed in v4.11-beta 14.
29.1.2.73 Changing simulation time window caused differences in debris flow

calculations
Changing the simulation time caused differences in calculated debris flow. This issue was fixed in v4.11-beta
14 by resetting the accumulated rainfall for a debris flow event to zero when direct runoff went to zero.
29.1.2.74 Simulation fails when using ratio of precipitation

When the ratio of precipitation is different from 1.0, the simulation would sometimes fail. This issue has
been fixed in v4.11-beta 14.
29.1.2.75 Results graph for subbasin with a 2D connection wouldn't display

properly
When opening a graph for the time series results for a subbasin with a 2D connection, the time series for the
2D connection would display instead. This has been fixed in 4.11-beta 14.
29.1.2.76 Results graphs for reservoir components did not display

Time series results for outlet, spillway and dam reservoir components would not display. Introduced with the
fix of the above issue in 4.11-beta 14. Fixed in final release.
29.1.2.77 Drop in Pak & Lee Infiltration Limit

The infiltration rate abruptly dropped to the original infiltration rate after 138 rainfall events. The infiltration
rate should continue to increase with time since the last burn date. This has been fixed in v4.11-beta 14.

29.1.2.78 Muskingum-Cunge Global Editor table would not appear

The Muskingum-Cunge global editor table does not appear after changing routing method to another
method, then switching back to Muskingum-Cunge. This issue has now been resolved in v4.11 beta 15.
29.1.2.79 Error looking for time-series gage record when running CWMS forecast in
HMS standalone
HMS reports invalid gage data for some gage types when gage data is in CWMS forecast.dss file. This issue
was fixed in v4.11-beta 15.
29.1.2.80 Renaming Parameter Value Sample drops selection from Uncertainty

Analysis Parameter editor panel
If a Parameter Value Sample was selected in the Uncertainty Analysis Parameter editor panel, and the
Parameter Value Sample was renamed the Parameter Value selection would be dropped in the editor panel.
This issue has been addressed such that renaming Parameter Value Sample is tracked in the Uncertainty
Analysis Parameter editor panel.
29.1.2.81 Copying Parameter Value Sample fails with Error 10000

Attempting to copy a Parameter Value Sample failed with Error 10000 (generic error) in the console. This
issue has been addressed such that Parameter Value Sample paired data can now be renamed.
29.1.2.82 User Interface Typo When Copying Simulations

When copying simulations from any of the Run Managers, the Name label incorrectly contained two semi-
colons. This typo has been addressed.
29.1.2.83 HEC-HMS as first in program order for CWMS/HEC-RTS model causing

Error 10000
When HEC-HMS is the first program in the program order, a check was causing an Error 10000 due to the
alternative pathname syntax of the CAVI. This error has been fixed in v4.11-beta 15.
29.1.2.84 Gridded loss methods fail when parameter grids use another unit system
Gridded loss methods were prone to failure when referencing parameter grids that used a different unit
system than the basin model coordinate system. This was because a proper unit system conversion was not
being applied. This bug was introduced in v4.9 and fixed in v4.11.

29.1.2.85 Check parameters missing for gridded loss methods

Check parameters was not being called for gridded loss methods. This triggered general error messages at
simulation time if the gridded loss methods were not properly parameterized. This issue has been fixed so
that meaningful error messages are presented if gridded loss methods are not properly parameterized.
29.1.2.86 Gridded records with invalid values cause Automated Forecast to fail
In some cases the data retrieved by the automated forecast would include grids with entirely no data values.
These grids are now being filtered out and replaced with interpolated grids of valid values.
29.1.2.87 Terrain Reconditioner fails with large terrain rasters

The terrain reconditioner was prone to out of memory errors when applied to large datasets, ~3 GB and
beyond. A buffered raster reader has been implemented that alleviates the memory burden for raster
processing. The terrain reconditioner has been successfully tested on datasets greater than 3 GB.
29.1.2.88 Unknown error when changing between basin models in optimization

trials
Unknown error occurred when trying to update parameters after changing a basin model within an
optimization trial. The issue was fixed by removing all parameters from the optimization trial when changing
the basin model.
29.1.2.89 Incorrect sediment statistics in Global Summary

Sediment statistics were not correct when recomputing a basin model without computing all elements.
Subbasin erosion is computed at the end of the first pass through the basin model. A second pass is used to
route sediment downstream from the subbasins. Code to re-initialize sediment calculations was modified for
the second pass so the correct statistics are calculated.
29.1.2.90 Changes in 2D connection outlet editor parameters didn't notify results

and cause recompute on next run
Changes in 2D connection outlet editor now trigger DATA CHANGED, RECOMPUTE warning in Subbasin
results graphs and tables. Running compute after the changes will trigger results to be recomputed with the
new values.
29.1.2.91 Uncertainty Analysis Output Control dialog fails to open when basin
model does not contain spatial 2D features
When attempting to open the Uncertainty Analysis Output Control dialog with a non-spatial 2D basin, the
Uncertainty Analysis Output Control dialog failed to open. This issue was introduced in v4.8 and resolved in
v4.11-beta.16.

29.1.2.92 Zero diameter in Gradation Curve yields erroneous results

If a zero diameter is entered in a Gradation (Diameter-Percent) Curve, computed sediment results have
unknown values because the program is trying to get the logarithm of zero. The zero-diameter value is
replaced by the minimum diameter of the smallest sediment grade in the sediment grade scale.
29.1.2.93 Unable to open Element Graph when Element Summary Table and/or
Element Time-Series Table were open
If an Element Summary Table and/or Element Time-Series Table were open, the Element Graph could not be
opened. This issue was introduced in v4.11 and fixed in the final release of v4.11.
29.1.2.94 Sediment Discharge with No Outflow from Reservoir

When there was no inflow or outflow for time period, the residence time for sediment in the reservoir was set
to 1 second causing suspended sediment to be released from the reservoir. The residence time was
changed to 109 seconds when there is not inflow or outflow. Suspended sediment is retained in the reservoir.
29.1.2.95 Reservoir volume reduction did not use Cobble and Boulder grain sizes
Cobble and boulder grain sizes were not included in calculation of reservoir volume reduction due to
siltation. The calculations were updated to include cobbles and boulders.
29.1.2.96 Suspended sediment did not settle to bottom of reservoir

Settling time was based on the residence time in the reservoir. If the residence time is large, the fraction of
suspended sediment that settles to the reservoir bottom in a time period is small. This calculation was
changed to use the lesser of residence time or sediment fall time from the water surface to the reservoir
bottom. In most cases the fall time is used to calculate the fraction of suspended sediment that settles to
the bottom.
29.1.2.97 Simulation stalls when computing sediment in reach with Kinematic

Wave route method
Sediment is computed on the second pass through the stream network. There was an error in the Kinematic
Wave router that prevented it from computing routed flows during the second pass. This error caused the
sediment router to go into an infinite loop. This error has been corrected.

29.1.3 Known Issues
29.1.3.1 Interpolated Meteorologic methods re-compute grids when there are

changes to parameters in the basin model
The interpolation methods create gridsets based on point values. The gridsets should be computed the first
time a simulation is computed and then re-used for subsequent simulations. The grids do not need to be re-
computed when there are subbasin, reach, or reservoir parameters change in the basin model. Future work
will correct this issue and only re-compute the interpolated gridsets when necessary.
29.1.3.2 Time series results table doesn't open for time series with different end
time
A blank time series dialog opens if time series results for multiple computes with different end times are
selected. We will fix the issue in the future releases to enable opening time series dialogs for computes with
different end time.
29.1.3.3 Cannot compute sediment and unregulated flow in the same basin model
Sediment and unregulated flow both require computing the stream network twice. Eroded sediment from
subbasins is computed at the end of the first pass through stream network. The eroded sediment is routed
through the stream network on the second pass. Regulated flow is computed during the first pass through
the stream network, and unregulated flow computed during the second pass. Sediment cannot be routed
through the stream network using regulated flow if the unregulated flow option is selected.
29.1.3.4 Draw properties editor for raster layers does not show up for some non US
region
Draw properties editor for raster layers does not show up for some non US regions, where a region is set by
the user's computer settings.
29.1.3.5 Occasional erroneous precipitation when using subbasins with multi-part

feature geometries and HMR52 precipitation method
Occasionally, erroneous precipitation values may be produced when using subbasins with multi-part features
(i.e., holes within the subbasin) when combined with the HMR52 precipitation method.
29.1.3.6 Occasional Aborted Computes when Using Energy Budget Snow

Occasionally, simulations that use the Banded or Gridded Energy Budget Snow method will fail with a
"WARNING 15303: Aborted run" message. This is likely due to a time series being written to disk that hasn't
been properly initialized. To avoid this issue within v4.11, users should increase the Output Results Buffer
Length. This issue will be fully rectified within v4.12.

29.1.4 Beta Releases
Rel Date Features Bug Fixes

eas
e
beta 12 Sep • Gridded storm transposition and optimization.

.1 2022 • Variable depths by subbasin in the hypothetical
storm.
• Frequency Depths tabular export to CSV.
• Added zonal editors for temperature-index snow.
beta 23 Sep • New HEC-DSS files will be created as version 7. ▪ Fixed point storm
.2 2022 Previously new files were created as version 6. depths not clearing
Existing HEC-DSS files are not automatically in Frequency Storm
migrated from version 6 to 7. meteorologic model.
• The behavior of the automatic forecast was
modified to allow forecast-only simulations.
Previously, a look back period data was required.
This modification was made to support
forecasting in areas where look back period data
is limited.
beta 30 Sep • Initial implementation of ensemble analysis • Fixed an issue where

.3 2022 compute. the program was not
saving manual entry
unit hydrograph
paired data curves.
• Corrected the default
snow albedo used
within the Gridded
Energy Budget
snowmelt method to
be 0.2. This now
matches the default
snow albedo used
within the Banded
Energy Budget
snowmelt method.
• Fixed several
compute issues
within the Hybrid
snowmelt method.


eas
e
beta 24 Oct • Added Optimization and Uncertainty Analysis • Fixed an issue where
.4 2022 support when using the Hybrid, Banded Energy incorrect upper and
Budget, and Gridded Energy Budget snowmelt lower limits were
methods. applied to
• Updated the Icon | Reset Location logic in the Temperature Index
basin map to use elevation rather than flow snowmelt
accumulation for determining upstream and parameters.
downstream ends of reaches. This is more robust • Fixed an issue where
for geometries that have been imported into HEC- wind speed was not
HMS. being converted
correctly from the
input units of
kilometers per hour
to the computational
units of meters per
second.
• Fixed an issue in
which some combo
boxes would not
select the selected
option if that option
was renamed.
• Added support for
snowmelt
parameters in
Uncertainty Analyses
and Optimization
Trials.
• Added SWE and
LWASS as output
time series in
Uncertainty
Analyses.


eas
e
beta 25 Oct • Added error handling in Hypothetical Storm with • Parameters from the
.5 2022 Precipitation-Frequency grid for condition that Banded Temperature
subbasin geometries are not polygons. Index, such as Initial
SWE and Cold
Content, can now be
selected as a
parameter for the
Parameter Value
Samples Paired Data
Table Type.
• Elevation band
parameters from the
Parameter Value
Sample Table are
sampled for each
realization.
• When adding a new
elevation band to a
subbasin and
navigating to the
Uncertainty Analysis
compute type, the
Parameter selection
now update to show
elevation band
parameters without
having to close and
reopen the hms
project.


eas
e
• When computing a
forecast alternative
that contains one or
more reservoirs
using the Outflow
Curve method,
erroneous messages
were reported
indicating that a
negative initial
storage was found.
This bug has been
fixed such that the
correct initial
reservoir state is
determined and no
erroneous error
messages are
reported.
• Fixed an issue that
was causing errors
loading the Subbasin
component editor.


eas
e
beta 18 Nov • Relabeled the "Hydrologic" sorting method to • Some result nodes
.6 2022 "Watershed Explorer." This relabeling indicates to were not active on
the user that the the Results tab even
sorting in the watershed explorer will be replicated though you could
in the global editor. click on the node and
see the results time-
series. The issue
was traced back to
changes in the DSS 7
E-part pathnames
and has been
resolved.
• The Regression with
Additive Error
sampling option was
not correctly
computing initial
SWE for the
temperature index
snowmelt method.
• Starting in beta.4,
users were required
to enter an ATI-Cold
Content relationship
when using the
Temperature Index
snowmelt method.
In previous versions,
this relationship was
optional. Logic was
changed to make
this relationship
optional and avoid
error messages
when computing
with no relationship
specified.
• Fixed an issue where
an error was
encountered when
re-delineating
elements that used
the 2D Diffusion
Wave transform
method.


eas
e
was encountered
within the CAVI/HEC-
WAT Model Linking
Editor when using a
reservoir element
that had a tailwater
option other than
"Assume None"
selected.
• Global Editors for the
Transform method
were not properly
sorted when initially
opened.
• When an HEC-HMS
project containing an
ensemble analysis
was open, and then a
subsequent project
was opened, the
ensemble analysis
directory was never
updated to reflect
the newly opened
project which led to
an Error 10000. A fix
was added to
correctly update the
directory.
was preventing the
snowmelt graph
from being properly
displayed when a
forecast alternative
did not contain any
snowmelt zones.
• Limited Table Export
Options to only allow
export to *.csv files.
The data was fixed
to export as comma
delimited instead of
tab delimited.


eas
e
• Fixed an issue with
the Ensemble
compute where
results were not
being correctly
copied to version 7
DSS files.


eas
e
beta 02 Dec • A clarifying error

.7 2022 message was added
to both hypothetical
storm compute and
frequency depth
calculator to indicate
when a precipitation
frequency grid is
missing projection
*.crs file.
• Frequency
precipitation
calculator was
improved to
calculate storm
depths from grids
with *.dss source
files.
• Energy Budget and
Gridded Hybrid
snowmelt
parameters can now
be selected in the
Parameter Value
Samples Paired Data
Table Type.
• Parameters from the
Energy Budget
elevation band(s),
such as Initial SWE
and Initial Snow
Depth, can now be
selected in the
Uncertainty Analysis.
• A repeat 'ERROR:
ERROR' text in the
error message for
attempting to use a
duplicate name in
Rename Element
Dialog was caused
by code changes in
beta.6. It was
corrected in beta.7.


eas
e
• Fixed Error that
would appear when
computing projects
with Modified Puls
with None selected
for elevation-
discharge
• Select time-series in
not stored.
beta 09 Dec • Added support for multiple 2D meshes within a • Error 10000 no
.8 2022 single basin model. longer posts when
• Rule-based reservoir control. copying and pasting
basin elements.
• Precipitation grid
time shift with non-
gridded subbasins.
• v2.2 project hangs
on open.
• Glitch in Elevation-
Area curve editors
with DSS 7 files. This
issue was fixed in
the javaHeclib
dependency.


eas
e
beta 27 Jan • Added ability to sample precipitation gridsets • Connect upstream

.9 2023 from a parameter value sample. subbasin to
• Added warning message if canopy is configured downstream junction
but the met model does not have an ET method for subbasin-split
selected. with insert junction
• Added warning message if lat/lon is missing when setting on.
using Gridded Hamon. • Simulation failure
• Added Snow Pack Condensation time series and when running
spatial variable when using the Energy Budget gridded temperature-
snowmelt method. index snow with
spatial results
enabled.
• Save grid data
source information
when switching to
Single Record HEC-
DSS from ASCII or
geoTIFF.
• Mass balance issue
in RTI compute when
liquid precipitation
was being double
counted when the
snowpack melts out.
• Performance issue
with font in the basin
map. This issue was
introduced in v4.11-
beta.4.
• Performance issue
when displaying
spatial results for
multiple 2D flow
subbasins. This
issue was introduced
in v4.11-beta.8.
• Removed inaccurate
warning message for
computed
transpiration when
using Layered Green
and Ampt loss
method.


eas
e
• Fixed logic in the
meteorologic model
that incorrectly
triggered a DATA
CHANGED,
RECOMPUTE
message in
meteorologic results
graphs. Also fixed
logic that prevented
certain components
of the meteorologic
from recomputing.
• Forward migration
logic for pre-v4.3
projects that
included a
groundmelt pattern
in the temperature-
index snowmelt
method.
• Incorrect error
message displayed
with FAO56
shortwave and
longwave radiation
methods.
• Global editors did
not open for multiple
basins with similar
names.
• Failure to save
specified time-shift
for gridded
meteorologic
methods when
attempting to save
time-shift method of
specified and non-
zero time shift at the
same time. This
in v4.11-beta.8.
• Fixed some filtered
entries freezing for
editing in File
References dialog.


eas
e
• Fixed 2D Connection
description not
loading properly.
• Display temperature
in results when snow
is not computed for
a gridded subbasin.
• Fixed a missing error
resource for Error
21487, switching it
to 21451 and
updating text to
"Gridded or
interpolated
precipitation must be
used for gridded
snow melt."


eas
e
beta 17 Feb • The basin sediment

.10 2023 editor panel grade
scale combo box
had "None" as an
option instead of
"AGU 20". This issue
was introduced in
v4.11-beta.9.
• When right-clicking
on a frequency
analysis in the
compute tree, the
rename and copy
buttons did not work
correctly. This issue
was introduced in
v4.11-beta.3.
• After a failed
frequency analysis
compute, a
subsequent compute
would sometimes
fail without any
errors or console
output. This issue
was introduced in
v4.11-beta.8.
• The statistical time-
series data
generated via the
ensemble analysis
and uncertainty
analysis simulations
did not previously
transform the data
correctly if the time-
step from the results
output control dialog
differed from the
computation time
interval. Logic was
added to correctly
transform the data to
the desired output
time interval. This
in v4.11-beta.3.


eas
e
• Fixed sediment/
debris results for the
AGU 20 grade scale
method.
• The program is now
reporting the correct
maximum SWE from
each iteration in an
uncertainty analysis.
• When applying a
time shift to
precipitation grids,
the subbasin
average loss time-
series was not
correctly shifted.
Computed results
were still correct.
This issue was
beta.8.
was preventing the
Gridded Shortwave
component editor
from opening
correctly.
disabled the Snow
Config combo box
when a new
selecting a new
configuration.
• Fixed performance
issues when
recomputing a model
with no parameter
changes. These
issues were
beta.9.


eas
e
• There were some
instances where the
algorithm that
computes outflow
would use a pool
elevation that was
above the inlet
elevation, but the
final elevation for a
period was below the
inlet. This resulted in
an erroneous value
in the outlet flow
time series. The
code has been
modified so outlet
flow is computed
based on the current
pool elevation.
• LA Debris EQs 2-5
did not worked with
the gridded
transform method.


eas
e
beta 10 Mar • Added DSS 7 Migration utility. • Fixed an issue where

.11 2023 • Added global editors for the Banded and Gridded the atmospheric
Energy Budget snow methods. pressure U.S.
• Added a global editor for the Hybrid snow method. Customary units
resulting from unit
conversion of a time
series in HEC-
DSSVue were not
being read correctly.
The following
atmospheric
pressure units are
now accepted: inhg,
in hg, and in-hg.
• Correctly interpret
atmospheric
pressure grids using
units of "inhg", "in
hg", and/or "in-hg".
• The Grid to Point tool
correctly computes
an average time-
series for each
polygon in the
selected shapefile.
The name attribute is
used for the b-part
pathname.
• The compute was
not watching if
changes were made
to the percentage
gage used for the
surface infiltration.
• In order to increase
the stability of the
Energy Budget snow
melt method, check
for and replace 1)
atmospheric
pressures > 125 kPa
and 2) snowpack
densities less than 0.


eas
e
• Adjustable Gate
Control was removed
from Outflow
Structures reservoir
routing - the
capability was only
meant to be used
with Rule-Based
Reservoir Routing.
• Kinematic Wave
global editor area
unit labels now
match the unit labels
displayed in the
component editor.
• Grid time shift was
not properly applied
for gridded
temperature, dew
point, humidity,
atmospheric
pressure, shortwave
radiation, longwave
radiation, and
windspeed. This was
beta.10 and fixed in
v4.11-beta.11.


eas
e
• When using rule-
based reservoir
operations and the
computed reservoir
elevation surpassed
the highest defined
zone, a vague error
message was
presented i.e. ERROR
46300: Storage guide
curve name is not set
for reservoir
"Reservoir 1". Now, a
more diagnostic
error message is
presented i.e. ERROR
46300: The
computed elevation
of "1000.00 ft" for
reservoir "Reservoir
1" exceeds the
highest defined zone
elevation for
"03JAN2000,
20:00". This was
beta.8.
• Added or fixed
compute checks for
basin or met model
'None' selection for
all compute types.
• Added logic to check
for existing slope,
aspect, and/or solar
shading rasters prior
to recomputing. If
they're found, issue a
warning. If the user
elects to continue,
overwrite the
existing rasters with
updated information.


eas
e
• PER-AVER and PER-
CUM observed data
was not plotting
appropriately (i.e.
stair-stepped
pattern). This was
beta.1 and fixed in
v4.11-beta.11.
• PX, Base, and
Forecast Time line
markers update in
graph panels after a
simulation is
recomputed if their
values were
changed.
• New checks were
added for the bilinear
interpolation method,
there must be three
or more gages, and
gages should cover,
or bound, all grid
cells.


eas
e
beta 07 Apr • Added user-interface theme selections to Tools | • For non-subbasin

.12 2023 Program Settings, General tab: System, Light, and basin element plots,
Dark. the program was
• Added Muskingum sediment debris routing opening duplicate
method. plots of model
• Added new sediment hindered settling velocity results. The program
factors based on 1.) Richardson and Zaki, and 2.) should keep all plots
Kumbhakar et al. up to date with latest
• Enabled a minimum iteration setting for the results, multiple
Differential Evolution optimization search method. plots of the same
• Added Simple Shortwave Radiation meteorologic element is not
method. needed.
• Results would go out
of date when clicking
from a subbasin with
an observed SWE
gage to another
element in the basin
model. This issue
has been fixed and
the software is no
longer tracking a
change to the basin
model when simply
clicking from one
element to another.
• Flaky UI behavior
when editing in the
Rule tab of the Rule-
based Reservoir. The
problem has been
resolved, and the
erratic behavior is no
longer present.
• PX Temperature and
Base Temperature
marker lines are now
labelled correctly
within the Snowmelt
Graph.


eas
e
• Snow Threshold
Temperature and
Rain Threshold
Temperature marker
lines are now
labelled correctly
within the Snowmelt
Graph.
• Synchronize Clark
component editor
and global editor
changes.
• Modified snowmelt
global editor
behavior to be
consistent with
component editor
when no grid or
pattern is selected.
• Fixed units for Snow
Depth spatial results
when using the
Energy Budget Snow
method.
• Meteorologic time-
series not selectable
in output results
dialog.
• Corrected dialog
titles for the
optimized parameter
results graph and the
frequency analysis
graph.
• USGS Long Term
Model Global Editor
was not opening
after changing the
method. Global
Editor for USGS Long
Term Model now
shows up when
selected.


eas
e
• The selection of
'None' would not
save for the
uncertainty analysis
with the 'Regression
with Additive Error'
method selection.
• Fixed errors from
switching between
2D Connection
nodes in different
basins.
• Changing Linear
Reservoir baseflow
to another baseflow
method.
• Header and data
became mismatched
when reordering
columns within the
Global Summary
Results Table.
• Global Editors reflect
unit system
changes.
• Hamon ET subbasin
nodes removed from
meteorologic model.
This was introduced
in v4.11-beta.1.
• Use Precipitation
Parameters for
Regression with
Additive Error.
• File References table
filtering for non-DSS
grid.
• Missing Observed
Data plots for
maximization goal
optimization.
• Units reverting when
trying to change for
Paired Data.


eas
e
• Missing Sediment
Method UI option for
Reservoir when
Basin Sediment
Routing is Enabled.
• The selection of
multiple time-series
nodes for plotting in
the Results tab
would lead to
glitches when
creating the plot in
the preview results
panel. This issue
was introduced in
v4.11-beta.3, but it
has now been
rectified.
• Storm Center user
interface is displayed
even when the grid is
not a Precipitation
Grid.
• Show units for Travel
Time in Release Rule
Editor.
• Global Editors do not
track rename.


eas
e
beta 19 Apr • Removed display global editors outside desktop • Decreasing number
.13 2023 program setting. With the new global editor of iterations in
framework global editors are always displayed optimization search
outside the desktop. sometimes caused
• Added Precipitation Index Humidity meteorologic unknown error.
method. • Automatic removal
of empty values
when pasting from
Excel/CSV/Text
caused data
misalignment.
• Attempts to rename
a basin or
meteorological
model to a name that
is already in use
would remove the
basin or
meteorological
model from the
project.
• Broken functionality
in Uncertainty
Analysis results
graphs.
• Fixed precipitation
index value in Energy
Budget snow method
such that it updates
correctly when basin
units change
• Added checks to
notify error if the
time window was
incorrect for the
optimization
analysis.
• Fixed empty
sediment results
plots for sink
elements.


eas
e
• Fixed one-off
sediment volume
time-series error.
Peak sediment load
and peak sediment
volume now occur at
the same time.
• Fixed Energy Budget,
Gridded Energy
Budget, and Gridded
Hybrid snow global
editors such that
they update correctly
when one or more
subbasin names are
changed.
• Fixed bug where
Standard Report tool
does not open.
• Fixed bug where grid
cell or subbasin
elevations were not
being properly
converted to metric
units before being
used within the
Simple Shortwave
Radiation
meteorologic
method.
• Fixed bug in energy
and mass balance
computations
in Energy
Budget snowmelt
method.
• Fixed issue in results
plots where the
zoom/pointer mouse
functionality does
not persist between
computes.
• Observed sediment
load added to results


eas
e
beta 15 May • Added ability to zoom out in a results graph if the • Fixed 2D Diffusion
.14 2023 computed extents increase in the x or y direction. Wave transform
• Added the ability to export spatial results to water surface and
GeoTIFF, ASCII, and/or DSS. volume tolerance
• Renamed the Simple shortwave radiation method parameters such
to Reduced Solar Constant. that the values and
• Added the Stefan Boltzmann longwave radiation labels correctly
method. update when
• Added the Barometric atmospheric pressure changing the unit
method. system of the basin
model.
• When using the
output control
feature to increase
the time step of
written results, in
some cases the
entire output record
was not written.
• Fixed issue where
storm center
coordinates for
gridded precipitation
failed to compute in
cases where the
gridded precipitation
dataset was close to
the projection origin.
• Properly handled
corrupt HEC-DSS
files that are
referenced by an
HEC-HMS project.
The files are now
flagged upon
opening the project
and are added as an
Invalid Reference to
the File Reference
dialog. In at least
one case, the
referencing of these
corrupt files called
simulation runs to
fail and resulted in
the loss of paired
data.


eas
e
• Fixed issue that did
not allow
optimization
parameter changes
after setting basin-
meteorology linking
and then changing
the linking.
basin and met
models did not
register new name
for the renamed
gridded and paired
data.
• Output separate time
series and spatial
results for snowpack
sublimation and
condensation when
using the Energy
Budget snow
method.
plots would not open
the first time.
a simulation would
have to be run a
second time in order
for the program to
correctly identify all
elements as being up
to date.
• Fixed an error in how
sediment time series
were set when using
a small simulation
buffer.
debris flow
calculations using
different simulation
times.


eas
e
was preventing 2D
Connections with
blank or null rating
curves from saving
correctly.
was preventing 2D
Connections or
Unstructured
discretizations from
drawing correctly.
• Fixed an issue when
using ratio of
precipitation other
than 1.0.
• Fixed results graph
for subbasin with a
2D Connection not
displaying properly.
the Pak & Lee
infiltration rate.
was preventing
Temperature Index
Parameter Value
Pattern combo
boxes from filling
correctly.
• Removed Gridded
Hybrid Snow from
the list of available
snow methods when
creating a Parameter
Value Pattern.
• Fixed global editors
for gridded and
banded temperature
index snow methods
to track changes in
subbasin editors and
paired data curves.
• Fixed the starting
albedo when using
the Gridded Hybrid
snow method.


eas
e
beta 01 Jun • Added the ability to use sediment total load and • Parameter grids are
.15 2023 sediment total volume time-series' within an not recognized by
ensemble analysis. expression
• Added the ability to define lapse rate for each calculator. E.g. "SCS
subbasin when using the Barometric atmospheric Curve Number" vs.
pressure method. "Curve Number". This
in v4.11-beta.13.
• Fixed issue with
gage data not being
found when data is
in CWMS
forecast.dss file for
certain gage types.
• Renaming Parameter
Value Sample drops
selection from
Parameter editor
panel.
• Copying Parameter
Value Sample fails
with Error 10000.
• Allow for the Gridded
Dew Point and/or
Interpolated Dew
Point methods when
using the Energy
Budget and/or Hybrid
Snow methods.
• Reduce inefficient
memory usage when
computing using the
Reduced Solar
Constant Shortwave,
Barometric
Pressure, Precipitatio
n Index Humidity,
Energy Budget and/
or Hybrid Snow
methods.
• Snyder global editor
failed to open. This
was introduced in
v4.11-beta.12 and
fixed in this version.


eas
e
• The Muskingum-
Cunge global editor
table does not
appear after
changing routing
method to another
method, then
switching back to
Muskingum-Cunge.
• When copying
simulations from any
of the Run Managers,
the Name label
incorrectly contained
two semi-colons.
This typo has been
addressed.
• When computing an
ensemble analysis
from the Compute
tab, the label text
was missing from
ProjectInterfaceReso
urces.properties
leading to a UI error.
This UI text error was
beta.3 and now has
been addressed.
• HEC-HMS as the first
program in the
program order for
CWMS/HEC-RTS
model causing Error
10000 due to f-part
syntax from the
CAVI.
• Unit conversions not
recognized for
Parameter Value
Samples paired data.
• Gridded loss
methods fail when
parameter grids use
another unit system.


eas
e
was preventing
simulations from
successfully
computing when the
2D Diffusion Wave
transform was used
in combination with
very large mesh
sizes (e.g., > 30000
cells).
• Gridded records with
no valid values
cause automated
forecast to fail.
• Check parameters
missing for gridded
loss methods.
• Terrain
Reconditioner fails
with large terrain
rasters.
• Exported
precipitation
accumulation raster
had an undefined
minimum value when
input precipitation
contained negative
values.
• Fixed unknown error
when changing
between basin
models in
optimization trials
• Fixed errors in
calculating sediment
statistics.
was preventing solar
shading from being
utilized correctly
within the Hybrid and
Energy Budget snow
methods.


eas
e
beta 12 Jun • Added the Vortex Image Exporter tool. • Fixed an issue that
.16 2023 was preventing
cumulative flow
hydrographs from
being correctly
computed when not
using the force
compute option.
• Changes in 2D
connection outlet
editor trigger
recompute.
required an
Elevation-Discharge
table to be in the
model in order to use
Modified-Puls
routing.
• Fixed an issue in the
Reservoir
component editor
that prevented
saving changes to
the description and
downstream
connection.
Global Editor for
Muskingum-Cunge
displaying the 8-
point cross-section
to NONE.
was preventing the
correct initial surface
temperature grid
from loading within
the Gridded Energy
Budget snow
method.


eas
e
was incorrectly
stating that the initial
snow depth grid was
changed within the
Gridded Energy
Budget snow global
editor.
• Updated the
acceptable data
types for initial
albedo grids to
include INST-VAL.
was preventing initial
snowpack energy
grids from being
correctly used by the
Gridded Energy
Budget snow
method.
Output Control
dialog failed to open
when the basin
model did not
include spatial
features.
zoom extents in
results graphs when
zooming in then
zooming back out.
The zoom extents
are now limited to
valid values.


eas
e
the Gridded
Precipitation met
model when storm
center x and y
coordinates were left
as blank. This
caused the
Transposition
parameter to
incorrectly switch
from Yes to No after
closing and re-
opening HEC-HMS.
transposing
precipitation where
some out-of-bounds
transpositions called
the compute to fail
with an unknown
error.


eas
e
final 13 Jul • Fixed an issue with

2023 zero diameter in
sediment gradation
curve.
an Element Graph
would not plot if an
Element Summary
Table or Time-Series
Table were open.
missing units on
Optimization results
plots and tables that
relate to optimized
storm center x and y
coordinates. Avoided
an Error 10000
thrown upon opening
an HEC-HMS project
that occurs when a
file exists for gridded
data but there are no
records in the file.
was preventing 2D
Connections from
saving/loading
correctly when they
were set to use the
None method.
• Fixed an issue in the
Energy Budget snow
method that was
preventing the
appropriate surface
heat conduction
equations from
being used each
time step.


eas
e
Irregular Interval
observed data was
causing the program
compute to abort.
Now the program
issues a Warning
message and does
not attempt to use
the irregular interval
data. You can use
HEC-DSSVue to
convert irregular
interval data to a
regular interval and
re-link the time
series gage to the
regular interval
record in an external
DSS file.
• Fixed time series
results not displaying
for reservoir
components.
• Fixed issues related
to sediment
calculations in a
reservoir and
reservoir volume
reduction.
• Fixed issues
preventing spatial
results from being
exported DSS, ASCII,
or GeoTIFF in certain
situations.
• Fixed error in
Kinematic Wave flow
router that prevented
sediment
calculations in a
reach.

29.2 v.4.10.0 Release Notes

Beta released: 28 Jan 2022
Final release: 28 Jul 2022
29.2.1 New Features
29.2.1.1 Frequency Analysis Compute

The new Frequency Analysis compute option in HEC-HMS is similar in nature to the existing Depth-Area
Analysis framework but with a different end goal in mind. Instead of analyzing multiple points within a
watershed at a single frequency, the Frequency Analysis compute option allows the user to analyze a single
point over a range of different frequencies. A Frequency Analysis can have one to many ordinates defined,
each with their own assigned annual exceedance probability, meteorologic model, and basin model.
Currently, the analysis can be used to generate a flow frequency curve or a stage frequency curve at the point
of interest.
749 Frequency Analysis Compute Component Editor

This feature was funded by the HQ General Investigations (GI) program. Initial code and implementation
were done by Josh Willis. Testing was done by Greg Karlovits, Josh Willis, and Matt Fleming.
29.2.1.2 Interpolated Meteorology

An interpolation option was added to the precipitation, temperature, windspeed, solar radiation, and
evapotranspiration methods in the meteorologic model. The interpolation option interpolates between gaged
locations and creates a series of grids if interpolating over a gridded domain, or time-series at point locations
if interpolating over a non-gridded domain. The interpolation methods include inverse-distance squared,
inverse-distance, nearest-neighbor, and bilinear. There is an option to bias correct a precipitation
interpolation, and lapse adjust a temperature interpolation. The interpolated result is cached to disk in an
HEC-DSS file. The cached result is accessed on subsequent computes, unless a parameterization change
occurs invalidating the cache and triggering a re-compute. The time-series gages that are selected for
interpolation must be parameterized with a valid longitude and latitude.

750 Interpolated precipitation component editor
The interpolated result is shown using the spatial results feature:

751 Results from an interpolated precipitation simulation
This feature was funded by through the Mississippi River Geomorphology & Potamology program. Initial
code implementation was performed by Caleb DeChant, and Thomas Brauer. Documentation and testing
was completed by Matt Fleming, Tom Brauer, Mike Bartles, and Simon Evans.
29.2.1.3 Snow Migration

Snow methods were migrated from the meteorologic model to the basin model. Snowpack accumulation
and ablation are a land surface process. Snow parameters now belong to the subbasin and can be adjusted
in the subbasin component editor framework and the basin global editor framework. In future versions of the
program, snow parameters will be accessible from zonal editors, similar to other basin processes.
Snow parameters will be forward migrated automatically for projects upgrading from prior versions. For
every meteorology model that includes snow, linked basin models are copied, and snow parameters are
migrated to the basin model copy. Simulations are updated to reference the copied basin model. Lapse rate
parameters are migrated from the snow parameterization to the gage air temperature parameterization in
the meteorologic model.
The image below illustrates Temperature-Index Snow parameters that have been migrated to the basin
model.

752 Temperature index snow parameters in the basin model
In the example below, copies of the Long_Term_Forecast and Winter_Forecast basin models would be
created to accommodate snow parameters from Winter_Forecast_wSnow.

753 Example migration of temperature index information to basin models
In the message log, Warning 20399 is displayed whenever snow parameters are migrated from the
meteorologic model to the basin model. The program will only migrate snow parameters to the basin model
copies (the basin model name with have "Copy" in the name). The original basin model will remain as it was
prior to migrating to HEC-HMS 4.10 or newer, no snow parameters will be migrated to the original/base basin
model. You might see multiple copies of the basin model because different meteorologic models, each with
snowmelt activated, were linked to the same basin model. After migrating to HEC-HMS 4.10 or newer, you
can delete any unnecessary basin model or rename basin models.
The figure below shows a project after it was migrated from version 4.9 to version 4.10. The
Gridded_Jan1997 and Gridded_Jan1997_bias meteorologic models were linked to the Tule_Jan1997 basin
model. The following Warning messages were generated when migrating to version 4.10. Since the snow
parameters were the same in both meteorologic models, the Tule_Jan1997 - Copy (1) and Tule_Jan1997 -
Copy (2) basin models were duplicates. The Tule_Jan1997 basin model was manually deleted. The
Tule_Jan1997 - Copy (1) basin model was renamed to Tule_Jan1997.
• WARNING 20399: Snow parameters from Meteorologic model "Gridded_Jan1997" have been moved
to Basin model "Tule_Jan1997 - Copy (1)".
• WARNING 20399: Snow parameters from Meteorologic model "Gridded_Jan1997_bias" have been
moved to Basin model "Tule_Jan1997 - Copy (2)".

This feature was funded by the CWMS National Implementation Program. Initial code and implementation
were done by Tom Brauer. Testing was done by the HEC-HMS team.
29.2.1.4 Cached Meteorology

As a means to decrease simulation run times, meteorology time-series are cached for subbasins. If the
meteorologic model is not updated, the cached time-series will be accessed on subsequent computes.
Note: This only applies for subbasin-average methods; Gridded methods will recompute the meteorology for
each grid cell with every compute.
Note: A consequence of cached meteorology is that meteorologic time-series must be written to disk for
subsequent access. Meteorologic time-series can not be disabled in the custom time-series results option.
29.2.1.5 Meteorologic Grid Time Shift

As part of snow migration, grid time shift parameters were added to all gridded meteorologic methods. When
gridded snow projects are forward migrated to v4.10, the grid time shift parameter in the snow method will
be migrated to the gridded air temperature method.

754 Time shift option added to all gridded meteorology options
This feature was funded by the CWMS National Implementation Program. Initial code implementation were
done by Paul Ely. Testing was done by Tom Brauer.
29.2.1.6 Frequency Storm Enhancements
29.2.1.6.1 Precipitation-Frequency Grid Importer
Multiple precipitation frequency grids can now be imported to the project's grid data simultaneously from the
Precipitation Frequency Grid Importer dialog. This feature also internalizes external source files for the grids
by copying them to Project/data directory. To access the dialog, go to File | Import | Gridded Data |
Precipitation Frequency.

755 Precipitation Frequency Grid Importer dialog
29.2.1.6.2 Frequency Precipitation Calculator
The Frequency Precipitation Calculator can be used to quickly calculate average precipitation depths and
apply new precipitation depths at either the watershed or subbasin level. The figure below shows the
Frequency Precipitation Calculator is accessed by clicking the calculator button in the Frequency Storm
Component Editor. The Frequency Depths Calculator button is only active if the meteorologic model has
been linked to a subbasin model that contains georeferenced subbasin elements.

The following figure shows the Frequency Precipitation Calculator. The first step is to select a basin model.
The program uses the geometry from the selected basin model to compute the average precipitation depth
values. You must also select the correct precipitation-frequency grid for each duration. Once the
precipitation-frequency grids are selected, click the compute button to compute average precipitation
depths.

The following figure shows the average precipitation depth for each subbasin in the selected basin model.
You can edit values in the table. Click the Apply button and the program will copy the precipitation depth
values to the Frequency Storm Component Editor. By default, the program will round the precipitation depth
values using the expression calculator precision defined in the Program Settings.
29.2.1.6.3 User-Specified Depth-Area Reduction
The frequency storm meteorologic model now allows for a User-Specified area reduction method to be
applied. This new method allows the user to specify a depth area-reduction function and apply it to each of
the inner durations of a frequency storm.

This feature was funded by the USACE Ft. Worth District in partnership with the Texas General Land Office.
Initial code implementation was done by Thomas Brauer, Natasha Sokolovskaya, Daniel Black, Josh Willis,
and David Ho. Testing was done by the HEC-HMS team, Simeon Benson, USACE-SWF, and Landon Erikson,
USACE-SWF.
29.2.1.7 Hypothetical Storm Computed Depth Area Checks

Parameter checks were added to the storm depth and storm area values calculated above the computational
point for Hypothetical Storm with Precipitation-Frequency Grid precipitation method. The new checks mirror
the existing checks in place for user-entered point depth and area reduction.

29.2.1.8 Legend, Scale Bar, and North Arrow

A legend, scale bar, and north arrow can now be displayed within the desktop when a valid spatial result or
calibration metric is selected. These options can be enabled through the View menu. An example of these
new visualization items is shown in the following figure:
756 Legend, Scale Bar, and North Arrow Example
This feature was funded by the Federal Emergency Management Agency (FEMA). Initial code
implementation was performed by Shannon Newbold and Caleb DeChant. Testing was completed by Mike
Bartles and Thomas Brauer. Documentation was completed by Mike Bartles.
29.2.1.9 Time Series Plot Enhancements

Within previous versions, after modifying any part of a plot and recomputing, the changes were removed and
the plot was redrawn. Now, users can now modify line styles, add/remove viewports, add/remove marker
points/lines, and zoom in/out (amongst other capabilities), and the changes will persist after recomputing.
This feature was funded by FEMA. Initial code implementation was performed by Caleb DeChant, Bryson
Spilman, and Shannon Newbold. Testing was completed by Mike Bartles, Thomas Brauer, and Matt Fleming.
Documentation was completed by Mike Bartles.

29.2.1.10 Display Minimum and Maximum Spatial Results

Min and Max buttons were added to the Spatial Results toolbar that allow for quick visualization of the
minimum or maximum of any spatial result regardless of the time in which they were achieved. An example
of these new visualization items is shown in the following figure:
757 Maximum Spatial Result Example
This feature was funded by FEMA. Initial code implementation was performed by Caleb DeChant and
Shannon Newbold. Testing was completed by Mike Bartles, Thomas Brauer, Daniel Black, and Matt Fleming.
Documentation was completed by Mike Bartles.
29.2.1.11 Export Spatial Results

An Export Snapshot button and an Export Recording button were added to the Spatial Results toolbar. The
Export Snapshot button, when pressed, will allow the user to export the currently selected spatial result at
the current display time step as a GeoTIFF file. The resultant file will be georeferenced and can be read by
common GIS software (e.g. QGIS, ArcGIS). The Export Recording button, when pressed, will allow the user to
export an animation of the currently selected spatial result to either AVI or MP4 file. The resultant animation
will also include any currently displayed maps (e.g. subbasin outlines, reservoir icons, terrain, etc).
This feature was funded by FEMA. Initial code implementation was performed by Caleb DeChant, Shannon
Newbold, and Mike Bartles. Testing was completed by Mike Bartles, Thomas Brauer, Daniel Black, and Matt
Fleming. Documentation was completed by Mike Bartles.

29.2.1.12 Brune Trap Efficiency Method

The Brune's sediment trap efficiency method (Brune, 1953) was added to the reservoir sediment method. To
estimate, the trapping efficiency is based on the ratio of reservoir capacity to mean annual discharge. The
Brune's sediment trap efficiency method can calculate the reservoir sediment trap efficiency rate using four
input parameters (average annual inflow volume, reservoir capacity elevation, and two constant values (a
and b) for use in the Brune curve estimation). The below figure shows the Brune's sediment trap efficiency
method has been included in the list of Erosion Methods for a reservoir element. By adding Brune’s trap
efficiency method in HEC-HMS, USACE District offices can easily replace their manual excel spreadsheet to
estimate the long-term reservoir siltation with HEC-HMS.
The Brune trap efficiency method was funded by the USACE Arid Regions work unit within the Flood and
Coastal Systems Research and Development program. The initial code implementation was done by Paul Ely.
Documentation was written by Jay Pak. Testing was done by Jay Pak.
29.2.1.13 Dynamic Reservoir Volume Reduction Method

The Dynamic reservoir volume reduction method was added to Chen's and Brune's trap efficiency methods
for simulating the reservoir/debris basin volume reduction based on sediment/debris inflow from the

upstream watersheds. The Dynamic reservoir volume reduction method can update the Elevation-Storage
and Elevation-Area curves using two different deposition shape options (Tapered and V-shape). The below
figure shows the deposition shape options included in the two sediment methods (Chen's and Brune's trap
efficiency methods) for a reservoir element.
The Dynamic reservoir volume reduction method was funded by the USACE Arid Regions work unit within the
Flood and Coastal Systems Research and Development program. The initial code implementation was done
by Paul Ely. Documentation was written by Jay Pak. Testing was done by Jay Pak.
29.2.1.14 Simplex Optimization Improvements

The Simplex optimization method received a number of enhancements that improve the parameter search
process. The initial simplex used in the search is now based on the the minimum and maximum values
provided by the user, as well as the initial parameter value as before. This change improves the Simplex
search's coverage of the parameter value range, but requires that a thoughtful parameter range is set. It also
improves the search when the optimum parameter set is at the specified minimum or maximum value. An
adaptive search method94 was implemented that improves the stability and efficiency of the search with a
larger number of parameters. It has the trade-off of potentially making an optimization trial take longer, but
the search is less likely to get stuck in local minima.
These improvements were part of ongoing work on Optimization and Uncertainty in HEC-HMS, and were
funded by the HH&C Science and Engineering Technology (SET) program. Initial code, implementation, and
testing were done by Greg Karlovits.
29.2.1.15 Resume Differential Evolution Optimization

The Differential Evolution solver can now pick up where it left off when the solver terminates in two
situations:
• If the solver halts without converging by running out of iterations, the user can increase the maximum
number of iterations and the routine will resume the search from where it terminated, as long as the
user does not change any other settings.
94 https://www.webpages.uidaho.edu/~fuchang/res/ANMS.pdf

• If the solver halts by converging prior to reaching the maximum number of iterations, and the user
decreases the search tolerance, the routine will resume the search from where it terminated, as long
as the user does not change any other settings.
These improvements were part of ongoing work on Optimization and Uncertainty in HEC-HMS, and were
funded by the HH&C Science and Engineering Technology (SET) program. Initial code and implementation
were done by Greg Karlovits. and testing was done by Greg Karlovits and Matt Fleming.
29.2.1.16 Normalized Nash-Sutcliffe Efficiency Optimization Objective Function

The Nash-Sutcliffe objective function was replaced in the Optimization Trial only (not elsewhere in the
software) with the Normalized Nash-Sutcliffe Efficiency95, which has better properties for bounded
optimization and avoids issues that arise with penalizing the regular Nash-Sutcliffe objective function for out-
of-range parameters. Maximizing the Normalized Nash-Sutcliffe will always maximize the regular Nash-
Sutcliffe objective function but will not run into numerical issues when parameter values are close to their
bounds.
This change was part of ongoing work on Optimization and Uncertainty in HEC-HMS, and were funded by the
HH&C Science and Engineering Technology (SET) program. Initial code, implementation, and testing were
done by Greg Karlovits.
29.2.1.17 Peak-Weighted Variable Power Optimization Objective Function

An experimental objective function was added to the Optimization Trial with the intent of better
differentiating between high- and low-flow periods. It is similar in intent and computation to the peak-
weighted root-mean-square error objective function already utilized in HEC-HMS, but much more
substantially penalizes the objective function during periods where the observed data are high in magnitude
and the model error is high. The Peak-Weighted Variable Power objective function can be used with the
minimization goal.
First, range-normalize the observed flow time series , and create a new time series . Each value
of is on the range .
Then, compute the absolute residual for each time step, raised to the power of for the time step.
Call the exponentiated absolute residual for timestep with model parameters , .
The exponent has a value of 1 for any timestep where the observed flow is at the minimum observed flow,
and a value of 2 for any timestep when the observed flow is at the maximum observed flow. The objective
function is computed as , and for optimization this objective is minimized.
This feature was part of ongoing work on Optimization and Uncertainty in HEC-HMS, and was funded by the
HH&C Science and Engineering Technology (SET) program. Initial code, implementation, and testing were
done by Greg Karlovits.
95 https://ui.adsabs.harvard.edu/abs/2012EGUGA..14..237N/abstract

29.2.1.18 Calibration Results Map Layer for Flow and SWE

This feature adds new visual aids for at-a-glance assessment of the calibration state of a basin model.
Computed statistical metrics, such as Nash Sutcliffe Efficiency (NSE), Coefficient of Determination (R2),
Root Mean Square Error / Standard Deviation (RSR), and Percent Bias (PBIAS), are used to color-code each
subbasin.
This feature can be accessed via HEC-HMS's Spatial Results Toolbar as shown above. For more information,
refer to Viewing Calibration Results (see page 565).
This feature was implemented as a part of ongoing GIS work. Funding sources include the Corps Water
Management System (CWMS) National Implementation Program and the Risk Management Center (RMC).
Initial code implementation and documentation was performed by Nick Van. Testing was completed by
Thomas Brauer and Mike Bartles.
29.2.1.19 Global Basin Editors

Global Basin Editors have been added for all methods in the following processes: Discretization, Canopy,
Snow, Surface, Loss, Transform, Baseflow, Channel Routing, and Evapotranspiration. The new basin global
editors launch an expression calculator whenever the basin is composed of two-dimensional spatial
elements. For more, see Parameter Estimation (see page 275).

Initial code implementation was performed by Thomas Brauer, Caleb DeChant, Bryson Spilman, Natasha
Sokolovskaya, and Mike Bartles. Documentation and testing was completed by the entire HEC-HMS team.
29.2.1.20 Snowmelt Plot

A new plot is now available for simulations that use a valid snowmelt method. The snowmelt plot contains
three viewports that display Precipitation, Air Temperature, and Observed and Computed Snow Water
Equivalent (SWE). The Air Temperature viewport also includes marker lines for the selected subbasin's PX
and Base Temperature parameters.

758 Default Snowmelt Graph
The Snowmelt Plot can be accessed by selecting Snowmelt Graph either through the Results Menu or by
right-clicking the desired subbasin icon within the basin map. The option to select the Snowmelt Graph will
only be displayed for Simulation Runs, Forecast Alternatives, Depth Area Simulations, or Optimization Trials
that include a valid snowmelt method.
Funding sources for this feature included the Corps Water Management System (CWMS) National
Implementation Program. Initial code implementation was done by Simon Evans, Mike Bartles, and Tom
Brauer. Documentation was done by Simon Evans. Testing was completed by Mike Bartles.
29.2.1.21 Air Temperature Spatial Result

Air Temperature has been added to the list of available spatial results when using a snowmelt method, as
shown in the following image.

759 Air Temperature Spatial Result
Funding sources for this feature included the HH&C Science and Engineering Technology (SET) program.
Initial code implementation and documentation was performed by Mike Bartles. Testing was completed by
Matt Fleming.
29.2.1.22 2D Diffusion Wave Transform and 2D Sediment Transport Enhancements

hydraulic results. Please see the latest HEC-RAS v6.2 Release Notes96 for further details.
Mike Bartles. Testing was completed by Alejandro Sanchez, Jay Pak, Matt Fleming, Tom Brauer, and Mike
Bartles.
29.2.1.23 Basin Element Area Variable Added to the Global Editor Expression
Calculator
A basin element area variable can now be selected in the global editor expression calculator in conjunction
with basin characteristics and grids. The funding source for this enhancement includes the HH&C Science
96 https://www.hec.usace.army.mil/confluence/rasdocs/rasrn/hec-ras-6-2-new-features

and Engineering Technology (SET) program. Initial code implementation and testing were performed by Tom
Brauer and Josh Willis.
29.2.1.24 Units Added to Slopes in the Subbasin and Reach Characteristics Editors
In previous versions of HEC-HMS, flowpath slopes were listed as unitless ratios (rise/run). For clarification,
flowpath, basin, and reach slopes are now listed in either FT/FT or M/M.
760 Subbasin Characteristics Editor
29.2.1.25 Added Ability to Enable/Disable Messages to OS Console in Program

Settings
The user can now choose to write messages (Errors/Warnings/Notes) to their OS console by setting it
in Tools | Program Settings | Messages.
29.2.1.26 Improvements added for Processing and Applying Gridded Temperature

The gridded Hamon ET method required gridded temperature for the entire day. The program processes the
gridded temperature data and computes a daily average temperature grid. The program would stop a
simulation and issue an error message if temperature grids were not available for the entire first day of the
simulation. An enhancement was added where the program will compute the average daily temperature for
the first day of the simulation even if temperature grids are not defined starting at the beginning of the day.
29.2.1.27 Relaxed Requirement for User-Defined Pattern Hypothetical Storm

Patterns to be Strictly Increasing
In the User-Specified Pattern method for the Hypothetical Storm, the requirement that the depth percentage
pattern be strictly increasing has been relaxed so that it can now be non-decreasing instead. The time
percentage pattern must still be strictly increasing. This allows for users to specify repeating values of total
depth percents which imply that the incremental precipitation is zero.
29.2.1.28 Added File Override Warning and File Saved Dialogs

When saving files (e.g. shapefiles, GeoTIFF, .html, etc) to disk, if a file with the specified path and name
already exist, a warning dialog will be shown. Also, when the file is successfully saved, a success dialog will

be shown which contains two buttons: one that can copy the path to the file to the clipboard and another that
will open a file explorer to the location of the saved file.
29.2.1.29 Exposed Differential Evolution Initial Random Seed in the User Interface
The Differential Evolution search method in the Optimization Trial relies on random generation of parameter
values to create the initial population and each iteration of the search. The random generation relies on a
pseudorandom number generator, which can be seeded with an initial seed value that allows the random
generation sequence to be repeated. If a DE search is run with the same settings and seed, the results will
always be the same.
29.2.2 Bugs Fixed

29.2.2.1 Optimization Trial would Fail to Find Reasonable HMR 52 Storm

Parameters when using the Simplex Search Method
The initialization scheme for the simplex used in the Simplex search in previous versions of HEC-HMS would
sometimes place several nodes of the simplex (and therefore the storm) far outside the watershed boundary,
resulting in no rainfall applied to the watershed for those nodes and a false convergence of the search. The
new initialization scheme ensures that the storm will begin within the user-specified coordinate ranges and
generally prevents this issue from occurring. It is however incumbent upon the user to specify good
parameter ranges for the HMR storm prior to beginning the search.
29.2.2.2 No evapotranspiration computed when gridded meteorologic methods are

combined with non-gridded transform
In v4.9, no evapotranspiration was computed when the met model used gridded air temperature and gridded
evapotranspiration, but the subbasin used a non-gridded transform. In HMS v410, since the subbasin is non-
gridded (i.e. lumped), area-weighted temperature is calculated for the subbasin. Then evapotranspiration is
calculated for the subbasin using the area-weighted temperature and the subbasin latitude and longitude.
There is a slight difference in the calculated evapotranspiration between v 4.8 and v4.10, since temperature
is averaged before calculating evapotranspiration, and the subbasin latitude and longitude are used instead
of the grid cell latitude and longitude.
29.2.2.3 Sliver Polygons within the Subbasin Boundary would Generate

Unreasonable Flow when Applying the HMR 52 Storm
In some cases, small sliver polygons around the boundary of a subbasin element would cause the HMR 52
Storm computation to return unrealistic precipitation values. As described in this post, https://
discourse.hecdev.net/t/hmr-52-storm-issue-when-subbasin-element-has-sliver-polygons/2041, the work
around was to manually remove the sliver polygon outside of HEC-HMS and then update the HEC-HMS
geometry. A check was added when the program reads in the subbasin geometry and if the sliver polygons
are encountered then the vertices that make of the slivers are removed.

29.2.2.4 Failure to Copy Terrain when Reprojection Required

When associating a Terrain Data with a Basin Model, copying terrain data to the basin GIS folder failed
whenever a reprojection was required to convert from the terrain Coordinate Reference System (CRS) to the
basin CRS. This resulted in no terrain data visible in the basin map. This issue was introduced in v4.9 and has
been fixed in v4.10.
29.2.2.5 Raster Properties Editor Minor UI Fixes

In the Raster Properties Editor, labels now persist after saving the display properties. Color ramps that do not
have a default scale will be using the data min and max by default.

Method
Simulations containing the Hamon Evapotranspiration method would compute successfully without an Air
Temperature method selected. If the Hamon Evapotranspiration method is selected in the Meteorologic
model, and an Air Temperature method is not selected, the simulation would still run successfully. This
would occur if the "Replace Missing" option in the Meteorologic model is set to either Abort Compute or Set
to Default. This has been fixed so that the simulation correctly aborts when no Air Temperature method is
selected.
29.2.2.7 Initial Outflow Parameter was not Available for Kinematic Wave Routing
The Initial Outflow parameter was not available in the Paired Data Dialog for Parameter Value Samples
paired data, resulting in no selectable parameters for the Kinematic Wave routing method. This caused the
Paired Data Dialog to not function properly (reset back to previously selected method) if the Kinematic Wave
routing method was selected. The bug was fixed and Initial Outflow is now available as one of the paired
data options for calibration.
29.2.2.8 Reach Characteristics not Fully Computing after Re-delineation of an

Existing Basin
If reach characteristics were already computed on an existing basin and then the basin was modified by re-
delineation, errors were encountered when re-computing reach characteristics on the newly re-delineated
elements. A fix was implemented that now allows the reach characteristics computations to successfully
compute for all reach elements in the basin, new and existing.
29.2.2.9 Spatial Results would not be Displayed in Basin Models that Mix Clark and
ModClark Transform Methods.
An issued was encountered where spatial results were not displayed within a basin model where a majority
of the subbasins used the ModClark transform method and then a few used the Clark transform method.
This issue has been corrected. Spatial results are now displayed when mixing gridded and lumped transform
methods.

29.2.2.10 Calibration Results (Flow) Would Not Be Displayed if One Out of Many
Subbasin Does Not Have an Observed Flow
An issue was encountered where calibration results were not displayed if one of the subbasin does not have
an Observed Flow. This issue has been corrected. Calibration Results (Flow) should now color as intended
based on statistics metrics, and would not be colored if there is no observed flow for that subbasin.
29.2.2.11 Color Scales Updated to Reflect Moriasi ET. al. 2007 and 2015
Performance Evaluation Criteria
The Calibration Results display properties editor used outdated performance evaluation criteria. The color
scales have now been updated to reflect the Moriasi et. al. 2007 and 2015 performance evaluation criteria. In
particular, the following criteria are used:
• Table 9 metrics in Moriasi et. al. 201597 paper for R2, NSE, and PBIAS
• Table 4 metrics in Moriasi et. al. 200798 paper for RSR
Below is a table showing the combined performance criteria from the two papers.
Performance Color Code R2 (2015) NSE (2015) RSR (2007) PBIAS (2015)
Rating
Very Good Dark Green 0.85 < R2 ≤ 0.80 < NSE ≤ 0.00 < RSR ≤ PBIAS < ±5
1.00 1.00 0.50
Good Light Green 0.75 < R2 ≤ 0.70 < NSE ≤ 0.50 < RSR ≤ ±5 < PBIAS ≤
0.85 0.80 0.60 ±10
Satisfactory Orange 0.60 < R2 0.50 < NSE ≤ 0.60 < RSR ≤ ±10 < PBIAS
≤ 0.75 0.70 0.70 ≤ ±15
Unsatisfactory Red R2 ≤ 0.60 NSE ≤ 0.50 RSR > 0.70 PBIAS ≥ ±15
29.2.2.12 Illegal Character in File Path would Freeze the Program

An illegal character in a file path, such as an extra ":", entered into a file path of the Paired Data Editor or
Precipitation Grid Importer would freeze the program. The issue was corrected and such a character now
would result in the path highlighting red to be corrected.

29.2.2.13 Error 10000 When Loading Project Using Uncertainty Analysis With
Layered Green-Ampt Loss
If a project was set up to run an Uncertainty Analysis with any parameters from the Layered Green-Ampt loss
rate method, the program would fail to load those parameters from file and throw an Error 10000. The
program now loads those parameters correctly.
29.2.2.14 Optimization Trial Parameters With Lower Bounds Less Than Upper
Bounds Incorrectly Throwing Error 17506: "Maximum value is less than
minimum value for parameter"
In certain situations, HEC-HMS would incorrectly throw Error 17506 "Maximum value is less than minimum
value for parameter" even when the maximum value was greater than the minimum value for an optimization
parameter. This bug mainly occurred when one of the values was entered with a decimal place and the other
as an integer.
29.2.2.15 Paths to Some Grid Data and Terrain Data not Updating when Renaming
Project
The paths to terrain data file and to non-DSS gridded data files would not update when renaming a project.
The paths were also not updating for any gridded data that had its data editor window open. These file paths
now update properly.
29.2.2.16 Hypothetical Storm Becomes Uneditable After Renaming Basin

In v4.6 a precipitation-frequency grid option was added to the hypothetical storm. With the precipitation-
frequency grid option there is an option to select a computation point for determining the area of depth-area
reduction calculations. The computation point selection requires knowledge of the basin models associated
with the meteorologic models, and the computation points within each basin. An issue was found when
users renamed a basin model, the hypothetical storm editor panel would not update based on the basin
model rename. This issue has been resolved for v4.10.
29.2.2.17 Hypothetical SCS-Type and Area-Dependent Pattern Storm does not

Compute Following a Run with Precipitation Method Set to Precipitation-
Frequency Grid
Attempting to run SCS-Type or Area-Dependent Pattern Hypothetical Storm would sometimes result in
aborted run with a non-specific message sent to the console. This happened following a run with the 'User-
Specified Pattern' and 'Precipitation-Frequency Grid' methods selected for the same storm. The issue was
corrected by properly resetting precipitation method to 'Point depth' when the 'SCS-Type' or 'Area-Dependent
Pattern' are selected.

29.2.2.18 Map Did Not Display the Updated Identified Streams When the Stream
Threshold Was Updated
The map failed to display the identified streams with the new stream threshold when the stream threshold
was updated. This issue was limited to visualization only, as the underlying raster was properly updated and
subsequent GIS processing steps were not effected. This bug has been resolved, and the map will now
display the raster correctly when the stream threshold changes.
29.2.2.19 Some Reservoir Element Time-Series Table Fails to Open

A bug was discovered in which some reservoir element time-series tables failed to open and displayed a
blank dialog. This issue has been resolved for v4.10.
29.2.2.20 Non-SHG Albers gridded precipitation compute fail

Special handling logic was added to HEC-HMS to handle the case of Non-SHG Albers gridded precipitation.
HEC-DSS does not define a valid Coordinate Reference System for the non-SHG Albers projection. Logic was
added to HEC-HMS to recognize the projection as Non-SHG Albers and build a Coordinate Reference System
from projection parameters.
29.2.2.21 Raster Properties Editor to Use Basin Map Tooltip Precision for Precision
Raster Properties Editors in HEC-HMS have been updated to use the precision set in Tools | Program
Settings | Basin Map | Basin Map Tooltip Precision.
29.2.2.22 Error 10000 When No Parameter Set In Uncertainty Analysis

In the Uncertainty Analysis, if an uncertainty element was set but not the specific parameter type, an Error
10000 would be produced and HMS would need to be restarted. A more helpful error message to capture
this situation was added.
29.2.2.23 Error 46551 When Los Angeles Debris Method EQ 2-5 is selected for
areas out of 3.0 to 200.0 square miles.
If the Los Angeles Debris Method EQ 2-5 is selected for areas out of 3.0 to 200.0 square miles, a Warning
message will be produced instead of the Error 46551 message.
29.2.2.24 Rename Project Drops Non-HEC-HMS files Located in the Project

Directory
In prior versions of HEC-HMS, renaming a project would result in the deletion of some non-HEC-HMS files
located in the project directory and sub-directories (i.e. spreadsheets, Word documents, etc.). This issue has
been resolved for v4.10.

29.2.2.25 Negative flows computed when Diversion has no Downstream Element

Fixed an error that prevented access to the diverted flow if the downstream node was not defined. This issue
manifested with WARNING 41201: Negative inflows passed to reach.
29.2.2.26 Animation Framerate Did Not Change When Saved

Fixed a bug where the Animation Toolbar properties editor's frame rate was not applied when set.
29.2.2.27 Debris Volume Did Not convert for each grain size based on the unit
weight
Fixed an issue with the Debris Volume Conversion Calculation by replacing the specific gravity with unit
weight. Because the specific gravity approach calculation overestimates the debris volume by considering a
solid soil volume.
29.2.2.28 Reach Hydraulic State for Sediment Routing

Reach flows at nodes are passed to the reach sediment computer using a reach state container. The code
that initializes the reach state container was modified so it is correctly initialized for the second pass through
the stream network.
29.2.2.29 Muskingum-Cunge Routing on Second Pass through Stream Network

Muskingum-Cunge routing has an internal time variable that tracks time from the beginning of the
simulation. This variable is reset for each pass through the stream network.
29.2.2.30 Kinematic Wave Routing

Kinematic wave routing was using the minimum number of subreaches instead of the number of subreaches
calculated from index flow and celerity. The code has been changed to use the number of subreaches
calculated from index flow and celerity.
29.2.2.31 Kinematic Wave Routing and Sediment Calculations

In previous versions, the reach hydraulic states generated by kinematic wave routing was not being retrieved
correctly when calculating sediment transport. This issue has been fixed.
29.2.2.32 Sediment Deposition Limit

Muskingum-Cunge and Kinematic Wave routing use adjustable time steps to compute flow routing. For each
computational period, the last time step is truncated to match the end-of-period time. A sediment deposition
limit based on flow depth, fall velocity, and time step was calculating a lower deposition limit for the

truncated time step. This resulted in excess sediment outflow. The code was modified to calculate the
deposition limit using the time step before the truncated time step.
29.2.2.33 Volume Ratio Sediment Routing

In certain cases, the outflow volume is greater than the volume of water in the channel. The volume ratio
routing method would then generate more sediment than is available in the channel. The method was
modified so the outflow sediment is not greater than the available sediment.
29.2.2.34 Failure to Abort Compute when Gridded Hamon ET Encountered Missing

Temperature Data
When missing temperature data was encountered by the Gridded Hamon ET method, the simulation would
fail to abort when missing temperature data was encountered, but would instead continue to compute with
ERROR 24150 displayed in the console for each time step. This has been fixed so that the simulation aborts
at first occurrence of missing data.
29.2.2.35 Meteorology Model Component Editor Basins Tab Did Not Respond to
Method Selection
The Basins tab did not appear and disappear as expected when switching between Gridded Precipitation and
other precipitation methods within the same meteorology model. The issue has been fixed and Basins tab
disappears when Gridded Precipitation is selected and comes back on when another precipitation method is
selected.
29.2.2.36 Import Georeferenced Elements could cause HEC-HMS to crash

In previous versions, HEC-HMS would crash if the user specified a GIS shapefile without a text attribute field
(used to name the imported elements). A user-prompt was added to remind the user that a field definition
(text field) must be selected. The software crash is now avoided in this scenario.
29.2.2.37 2D Diffusion Wave Component Editor Unit Labels

In previous versions, when changing the basin model unit system, the units within the 2D Diffusion Wave
component editor labels didn't properly update. Now, these labels change whenever the basin model unit
system is changed.
29.2.2.38 Standard Report Fails to Generate Report for Depth-Area Analysis

Simulations
Fixed a bug where the standard report fails to generate report for depth-area analysis simulations.

29.2.2.39 Spatial Results Fail to Update when Computing to Point

In previous versions spatial results failed update when using the compute to point option. Spatial results are
now updated upstream of the computation point when using the compute to point option. Spatial results
downstream of the computation point remain unchanged.
29.2.2.40 Draw Properties for Shapefiles Not Saving Correctly

Previous software versions allowed you to edit the draw properties for a shapefile displayed in a basin
model. A bug was reported that draw properties were not being correctly applied for the case where the
same shapefile was selected across multiple basin models. This issue has been fixed, the program correctly
tracks the draw properties for each shapefile independent of the basin model.
29.2.2.41 2D Diffusion Wave and Gridded Loss Methods

Model simulations would abort when using the 2D Diffusion Wave transform and gridded loss methods (e.g.
Gridded Curve Number). The program was not able to correctly find the correct value for each cell in the 2D
mesh. This issue has been fixed, the program can correctly overlay the 2D mesh with the parameter value
grids.
29.2.2.42 User Specified Pattern Hypothetical Storm - Bad Interpolation Values

If the user-specified dimensionless (%-%) storm time pattern for the User Specified Pattern Hypothetical
Storm lacked a 0, 0 entry to begin the table, first timestep interpolation would result in nonsensical large
negative values if the model timestep length was shorter than the time to the first ordinate. Tables lacking a
0, 0 and/or a 100, 100 entry now throw an error and halt the simulation.
29.2.2.43 Failure to Update all Subbasins when Changing Discretization Method

from File-Specified to Structured
When attempting to change the discretization method for all subbasins from the Parameters | Discretization |
Change Method menu, the process would fail to update all subbasins when changing from file-specified
discretization to structured discretization.
29.2.2.44 Failure to Compute Downstream Elements when Computing to a

Computation Point
By default the "Compute all components even if unchanged" program setting is selected. When selected, the
program computes all elements in the basin model when you compute a simulation. When this option is
unchecked, the program keeps track of when basin model elements were last modified and will only re-
compute those elements that were modified since the last simulation or those downstream of the element
that change. The compute to point option (right click on a computation point and choose compute to point)
is a quick way to run only a portion of the hydrologic network. There has been a bug in the logic the program
used to determine if elements needed to be recomputed when running to the model to an computation point.

The logic has been improved and the program correctly re-computes elements when using the compute to
point feature.
29.2.2.45 Depth Area Analysis Time-Series Results for Elements using Special
Characters in Element Names
We found that time-series table results would not be available for elements with special characters in the
name, like "/". This issue has been fixed and now time-series results are displayed when special characters
are used in element names.
29.2.2.46 Difficulty Moving a Break Point

Break points must fall on top of grid cells making up the Identified Streams layer. We found an issue where it
seemed like trying to move a break point was impossible. This issue was caused by having multiple raster
layers visible in the basin model map and hillshading activated in the display properties. This issue has been
fixed, you can easily move break points regardless of the visible GIS raster layers.
29.2.2.47 Feature Labels for Shapefiles

The editor for displaying shapefiles in the basin model map contains a tab for activating display of labels.
The drop down menu for displaying which attribute to use for the labels was not working. This issue has
been fixed, you can now select attributes to use as labels for point, line, and polygon shapefiles.
29.2.2.48 Store Gridded State Variable Results Option Removed from Program
Settings
The Results tab in the Program Settings editor contained an option to store gridded state variables. This
option use to work in HEC-HMS version 4.4 and when turned on, the program would write gridded snow state
variables, and other state variables, to the output DSS file. This capability was replaced with the new spatial
results option. Gridded state variables are no longer written to the output DSS file; therefore, this option was
removed from Program Settings.
29.2.2.49 Gridded Temperature with non-Gridded Hamon ET

Warning messages were generated the first time a simulation was computed that used gridded temperature
with non-gridded Hamon ET. The program was not passing the subbasin average temperature and no
evapotranspiration was computed by the Hamon ET method. This issue only happened the very first time a
simulation was computed. The issue has been repaired, gridded temperature is processed to compute
subbasin average temperature which is passed to the Hamon ET method.
29.2.2.50 Undefined NoData Value in the Base Elevation Raster

In previous versions, the terrain reconditioner would fail without warning if the base elevation raster
contained undefined NoData values. Prior to launching the Terrain Reconditioning wizard, HEC-HMS now
checks that the base elevation raster contains a defined NoData value. If not, the user is advised that this
value must be defined prior to proceeding.

29.2.2.51 Area Reduction Factor Paired Data Incorrect Unit Conversion

When working with the area reduction factor paired data component editor, changing the units from km2 to
mi2 and selecting the "Relabel Only" option incorrectly changed the area values within the paired data table.
This has been fixed.
29.2.2.52 Null Pointer Exception thrown in Optimization Trial Editor

When using the maximization goal with a flow statistic (peak flow, flow volume, peak stage, etc.) an NPE
would be thrown when saving the Optimization Trial. An error message would only be noticed when running
in the IDE. The exception has been caught appropriately.
29.2.2.53 Optimization results get lost after editing search criteria and force
computing
In situations where a force compute in an Optimization Trial using Univariate search should have reset the
iteration counter, it was not reset, resulting in results for the trial not being written correctly and blank plots
occurring as a result. The iterations were properly reset when the Univariate search was not continuing from
a previous state.
29.2.2.54 Change Method to Multi-Sequence Debris Prediction Method in the

Global Editor
The Change Method did not work when selecting Multi-Sequence Debris Prediction Method in the Global
Editor. This function now works and users can change to MSDPM for all subbasins.
29.2.2.55 Optimization Trial Continuation Overrides Force Compute

In a small number of situations, when running an Optimization Trial and it was in a condition where it could
continue from a prior state, force computing was not resetting the search to the start and instead continuing,
by-passing the force compute. This behavior has been fixed - force computes will always start a trial over.
29.2.2.56 Warning 15303 Aborted Run When Attempting to Run a Simulation With a
New Subbasin
Fixed issue where Warning 15303 was generated when attempting to run a simulation with a newly created
subbasin, with no discretization.
29.2.2.57 Cumulative Volume Flatlines for Muskingum-Cunge Channels in Long

Simulations
Fixed issue where cumulative volume ceased to increase in the Muskingum-Cunge routing method for long
simulations. Time was being stored as a single precision integer. Now it is stored as a double precision
integer.

29.2.2.58 Special Characters in Meteorologic Model Name

Fixed issue where a special character in the meteorologic model name resulted in the program not being
able to pass precipitation to the basin model.
Release Date Features Bug Fixes
beta.1 28 Jan • Initial beta release

2022

beta.2 04 Mar • Added Min and Max buttons to • Vortex library update that
2022 the Spatial Results toolbar includes fixes to the Calculator
• Added Legend, Scale Bar, and and Grid-To-Point-Converter
North Arrow utilities. See notes here99.
• Added global editors for • Fixed issue with missing data
Discretization, Canopy, Surface, and the new interpolated grid
Loss, Transform, Baseflow, Chan Meteorologic Model option. If
nel Routing, Snowmelt, and the Replace Missing option is set
Evapotranspiration methods to Abort Compute, the program
• Added Dynamic reservoir volume will stop the simulation if a
reduction method to Chen's and missing value is encountered. If
Brune's trap efficiency methods the Replace Missing option is set
for simulating the reservoir/ to Set to Default, the program
debris basin volume reduction ignores any gage values that are
using trap efficient methods missing and uses only valid
based on sediment/debris inflow values for interpolation.
from the upstream watersheds. • Fixed an issue where calibration
In previous versions of HEC- results for Flow would not be
HMS, sediment was computed displayed if one out of many
for all time after hydrology was subbasin does not have an
computed for all time. In this observed flow.
version, sediment is calculated • Updated color scales to reflect
for all elements for each time the performance evaluation
step, before moving on to the criteria for statistical metrics
next time step. from Moriasi et. al. 2015100 and
Moriasi et. al. 2007101 papers.
• Fixed an issue where multiple
global editors for a given
modeling method (e.g.
Muskingum channel routing) and
basin model could be opened.
Now, if the user attempts to
open multiple instances of a
global editor for a given
modeling method and basin
model, the open instance will be
brought to the forefront. This
issue was related to global
editors that were migrated to the
new global editor framework, so
not an issue for previous
releases.
99 https://github.com/HydrologicEngineeringCenter/Vortex/releases/tag/v0.10.27


• Fixed issue where flow and
stage values that were
maximized using the Differential
Evolution optimization trial were
reporting as the negative of the
value in summary tables.
beta.3 30 Mar • Added logic to remove gages

2022 from the interpolated
meteorology editor panel if the
gage selection is None.
• Fixed an issue with the
Frequency Depth Calculator
where values outside of the
selected interval range were
being calculated and displayed
in results tables.
• Fixed program freezing if illegal
character is entered into a file
path of a Paired Data Editor or
Precipitation Frequency Grid
Importer.
• Updated SLF4J dependencies to
prevent log file from being
created in the program root.

beta.4 14 Apr • Migrated snow methods from • Error 10000 When Loading
2022 the meteorologic model to the Project Using Uncertainty
basin model. Analysis With Layered Green-
• Added time shift for all gridded Ampt Loss
meteorologic methods • Optimization Trial Parameters
• Added Export Spatial Results With Lower Bounds Less Than
buttons (Snapshot and Upper Bounds Incorrectly
Animation) to the Spatial Results Throwing Error 17506
toolbar • Paths to Some Grid Data and
• Added Snowmelt Plot Terrain Data not Updating When
• Added Air Temperature to the Renaming Project
list of available spatial results • Fixed an issue with the Debris
when using a snowmelt method Volume Conversion Calculation
• Added Time Series Plot by replacing the specific gravity
enhancements with unit weight. Because the
• Include calibration metrics in the specific gravity approach
legend calculation overestimates the
debris volume by considering a
solid soil volume.
• Uneditable hypothetical storm
editor panel after basin model
rename.
• Error 11003 after copying and
running a Frequency Analysis
• Error 10000 after renaming a
basin model. If the renamed
basin model was tied to a
frequency ordinate in a
Frequency Analysis, the basin
connection was lost. Logic was
added to update basin and
meteorologic model names tied
to a frequency ordinate if they
are renamed.
• Fixed an issue where the map
failed to display the identified
streams with the new stream
threshold when the stream
threshold was updated. This
issue was visualization only,
such that the underlying raster
was properly updated but the
changes were not displayed on
the map, and subsequent GIS
processing steps were not
effected.
• Fixed an issue where some
reservoir element time-series
tables would not open


• Added handling logic for Non-
SHG Albers projections
• Added logic in Raster Properties
Editor to use the precision set
in Tools | Program Settings |
Basin Map | Basin Map Tooltip
Precision.
• Error 10000 When No Parameter
Set In Uncertainty Analysis
• The x and y axis properly shows
labels when printing graphs.
• No evapotranspiration computed
when gridded meteorologic
methods are combined with non-
gridded transform.

beta.5 03 May • Added explicit error message for • Removed snow selection from
2022 the case that delineation fails Meteorology Model component
because the basin coordinate editor.
system is geographic. • Copy and pasting numbers with
• An option was added on the commas into paired data tables
Break Point Import editor where and time series tables
the modeler can choose to snap • Terrain data copy failure when
new break points to the identify reprojection required.
stream layer or not. As of HEC- • Negative flows computed when
HMS version 4.10, break points Diversion has no Downstream
must be located on top of grid Element
cells within the identified • Fixed an issue where the
streams raster. Animation Toolbar properties
• Added an option to display the editor's frame rate was not
north arrow relative to true applied when set
north. Previously, the only • Fixed case where Basin Element
available option was magnetic Graph would not open from the
north. Compute Toolbar whenever the
Basin Element Summary Table
was open.
• When copying a basin, trimmed
the basin name before adding a
copy number suffix. This
eliminates issues with finding a
unique name when the basin
name is at or near the maximum
character limit.
• Fixed an issue that was
preventing 2D meshes and
boundary condition lines
generated within HEC-RAS v6.2
from being imported to HEC-
HMS
• Fixed issue with Frequency
Storm rainfall depths passing
NaN values causing the method
to not work
• Fixed issue in the meteorology
model component editor where
basins tab did not respond to
method selections.


• Reach flows at nodes are
passed to the reach sediment
computer using a reach state
container. The code that
initializes the reach state
container was modified so it is
correctly initialized for the
second pass through the stream
network.
• Muskingum-Cunge routing has
an internal time variable that
tracks time from the beginning
of the simulation. This variable is
reset for each pass through the
stream network.
• Fixed an issue where basin
element summary graph would
not open if there was already a
general time-series plot or
element summary table open.
This issue was introduced in
v.4.10-beta.4.
• Performing a Save As on an
HMS project with a Depth Area
Analysis compute type no longer
deletes the Depth Area Analysis
compute
• Fixed an issue where the Plot
Spatial Results menu was shown
when right clicking on a basin
element even though no spatial
result was selected
• Updated the DSS path browse
dialog. This fixes some issues
that were introduced in a shared
library update that went into
v4.10-beta.4.
• Fixed an issue where duplicate
results were added to a time-
series results plot after re-
computing a simulation. This
issue was introduced in v.4.10-
beta.4.

beta.6 10 May • A slight improvement was made • Failure to abort the compute
2022 to the Hypothetical Storm met when Gridded Hamon ET
model parameter check during a encountered missing
compute. If a grid is selected as temperature data.
the precipitation method with a • Kinematic wave routing was
'user-specified' area reduction, using the minimum number of
the area reduction function subreaches instead of the
paired data table is now checked number of subreaches
for properly ascending values calculated from index flow and
and to ensure that the table celerity. The code has been
extends to an area large enough changed to use the number of
to cover the storm size (if subreaches calculated from
specified). index flow and celerity.
• Added ability to enable/disable • In previous versions, the reach
messages to Operating System hydraulic states generated by
(OS) console in Program kinematic wave routing was not
Settings (Tools | Program being retrieved correctly when
Settings | Messages) calculating sediment transport.
This issue has been fixed.
• Muskingum-Cunge and
Kinematic Wave routing use
adjustable time steps to
compute flow routing. For each
computational period, the last
time step is truncated to match
the end-of-period time. A
sediment deposition limit based
on flow depth, fall velocity, and
time step was calculating a
lower deposition limit for the
truncated time step. This
resulted in excess sediment
outflow. The code was modified
to calculate the deposition limit
using the time step before the
truncated time step.
• In certain cases, the outflow
volume is greater than the
volume of water in the channel.
The volume ratio routing method
would then generate more
sediment out flow than is
available in the channel. The
method was modified so the
outflow sediment is not greater
than the available sediment.


• The selected spatial result was
not automatically reset when a
different simulation was
selected. Now, the program
automatically changes the
selected spatial result to none
when selecting a different
simulation.
• Within the Frequency Storm
meteorologic model if the Area
Reduction method was set to
'None', an error was thrown at
runtime (Error 20045: Storm area
is not set for frequency storm).
This issue has been fixed and
the error is no longer incorrectly
thrown.
• Made subbasin sediment
selection visible in the subbasin
component editor. It was not
visible in v4.10 beta-4 and
beta-5, after the migration of
snow to the basin model.
• Fixed an issue where the
program would become
unresponsive when selecting a
forecast alternative with no
basin model selected. Now the
program will open the forecast
alternative's component editor
regardless of whether a basin
model has been selected.
• Spatial Results fail to update
when simulation is renamed or
deleted. This issue was
introduced in v4.10-beta.2 and
fixed in v4.10-beta.6.

beta.7 03 Jun • All compute types (uncertainty • Copying a time-series gage and
2022 analysis, depth-area analysis, converting from the HEC-DSS
optimization, frequency analysis) data source to the Manual Entry
now will show the total runtimes data source could result in the
after the compute is completed wrong data type or units. Now,
in the console and log file. the correct units and data source
• The program will now activate are saved when changing the
results (time-series nodes) on time-series data source.
the results tab only when the • Enabled the multiple compute
results are available in the option when a frequency
output DSS file. In prior versions, analysis exists or is added to a
the program would show active project.
nodes on the results tab after a • Previous versions set a limit
simulation was computed. when zooming in using the
However, the user can modify Zoom tool but not when using
whether individual time-series the mouse scroll wheel. This
are written to the output DSS file limit was removed and now the
(output control) and the program Zoom tool and mouse scroll
uses visual queues on the wheel function similarly.
results tab to let you know • Fixed an issue in the Frequency
whether certain results are Analysis compute where
available or not. computation results were only
• Added the ability to export an written to the default DSS output
animation of spatial results file even if another one was
animation to an MPEG-4 file. specified.
• Added the ability to export a • Enabled multiple time-series
snapshot of spatial results to a results to be plotted on the same
GeoTIFF file. graph within the Frequency
• Relaxed requirement for User- Analysis compute type, both in
Defined Pattern Hypothetical an internal and external frame.
Storm patterns to be strictly
increasing (are now checked to
be non-decreasing)


• Fixed an issue with the 'Time-
Series Table' results when
loading a project with a
previously computed Frequency
Analysis. The table no longer
shows up as empty.
• In previous betas, when using
the interpolated temperature
meteorologic model option, sub-
daily temperature gage data was
being treated as PER-AVER even
if it was input as INST-VAL.
Now, grids that are written to the
meteorologic model output DSS
file will be INST-VAL if all input
temperature time series are
INST-VAL. If one or more input
temperature time series are PER-
AVER, the output grids will be
PER-AVER.
• Fixed an issue in the Frequency
Analysis compute that
sometimes inhibited multiple
frequency analyses to be ran in
succession.
• Fixed an issue in the Frequency
Analysis compute where some
ordinates were not always
computed even after being
updated.
• An issue was fixed with the
minimum and maximum spatial
results that was introduced in
version 4.10-beta.2. The
program will now update the
minimum and maximum spatial
results without forcing the
simulation to recompute.
standard report tool fails to
generate report for depth-area
analysis simulations.
• Fixed SCS-Type or Area-
Dependent Pattern Hypothetical
Storm not running following a
run with the 'User-Specified
Pattern' and 'Precipitation-
Frequency Grid' methods
selected.


• An issue was fixed that was
introduced in 4.10-beta.4 where
elevation bands were not added
to the temperature index snow
method if all other subbasin
methods were set to none. Now,
elevation bands can be added
even if other subbasin methods
are set to none.
• Spatial Results fail to update
when computing to point.
• Fixed issue where discretization
geometries were deleted
downstream of a computation
point when computing to a point.
• The HMR 52 Storm optimization
could generate a message about
missing or invalid precipitation
when the storm was moved
outside the watershed and the
ModClark transform method
selected. Now the program
assumes 0 inches of
precipitation when the storm is
not over a gridded subbasin.
• Users must now specify a 0, 0
and a 100, 100 entry in a user-
specified dimensionless %-%
storm pattern for use in the User
Specified Pattern Hypothetical
Storm.
• Time-series plot enhancements
were added to version 4.10-
beta.4. These enhancement
broke a feature with certain
optimization plots (objective
function and parameter value
plots) where the plots were
updated at the end of the
optimization trial. Also, if you
had these plots open, you would
notice they updated
automatically after 25 iterations
during the optimization
simulation. Optimization plots
were update for the version 4.10-
beta.7 release to mimic past
behavior.


• In v4.10-beta.6 DSS files with
non-lowercase extensions were
recognized as invalid. In v4.10-
beta.7 the file name inspection
is case insensitive.
• Failure to update all subbasins
when changing discretization
method from file-specified to
structured.
• Failure to open the Gridded
Green & Ampt component editor.
This issue was introduced in
v4.10-beta-4.
• Out of memory when running
interpolated meteorology with
file-specified discretization.
• Fixed issue where interpolated
meteorologic options were
computing each time the
simulation ran even if existing
interpolated grids were still valid.
Now, the interpolated grids are
only computed when the user
forces the re-compute or if
something changes in the
meteorologic model.

beta.8 14 Jun • Added File Override Warning and • Setting the reservoir routing
2022 File Saved Dialogs. method to None would cause an
• Finalized cached meteorology error message when attempting
implementation by restricting to reopen the reservoir element's
meteorologic time-series in component editor.
custom time-series output • Saving gridded state variables to
selection. DSS was replaced with spatial
• Added checks for depth and results. Some work for beta.7 to
reduction area calculated above update the user interface to
the computation point for the remove unused components
hypothetical storm met model. inadvertently left some error
checks in place. Additional
unused code was removed,
including unused error checks.
• An issue was fixed with a
configuration where an
upstream reservoir passed
auxiliary flow to a downstream
reservoir, and the downstream
reservoir had no downstream
connection.
• An issue was fixed that could
potentially lead to an unhandled
exception when using a Source
element within a Forecast
Alternative that had missing flow
values.

beta.9 13 Jul • The Linear Reservoir Fraction • For beta.5, the program was
2022 parameters are now available in modified so numbers with
the Linear Reservoir Baseflow commas could be pasted into
Zonal Editor. time-series and paired data
• Exposed Differential Evolution tables. We found that under
initial random seed in the user some circumstances when using
interface a comma as the decimal
separator, the program would
add a extra zero to the left side
of the decimal separator when
saving the project. Now the
program is correctly handling
paired data when using either a
decimal or comma separator.
• In beta.8, parameter checks
were added for Hypothetical
storm's reduction area,
calculated above the
computation point. Under some
conditions these checks were
found to result in inconsistent
comparison with the user-
specified area reduction table
because of rounding during unit
conversion. The issue was fixed
by performing all comparisons in
SI units.
• A Null Pointer Exception thrown
in Optimization Trial Editor when
maximizing a flow statistic has
been caught.
• Univariate optimization results
no longer get lost after editing
search criteria and force
computing
• The Change Method did not
work when selecting Multi-
Sequence Debris Prediction
Method in the Global Editor.
This function now works and
users can change to MSDPM for
all subbasins
• Repaired an issue where force
computing an Optimization Trial
was not resetting the search to
the start and instead continuing
from a prior state, by-passing the
force compute.


• Repaired an issue where lapse
rates were not being saved
under that condition that
snowmelt migrations were
attempted when a met model
was not linked to any basin
models.
• Always set Apply to
subbasins to Yes when the
simulation ratio method
is Precipitation.
• Updated observed flow
resampling logic to only
interpolate between two defined
values. If one of the values
bounding the interpolation point
is undefined, the interpolated
value will be undefined.
• Warning 15303 when attempting
run a simulation with a newly
created lumped subbasin.
• Fixed issues that prevented
optimization of SWE parameters
in Gridded Temperature Index
Snow.
• Fixed some linetype issues that
occasionally occurred in the
Optimization Observed Data
graph.

Final 28 Jul • Fixed issue where cumulative

2022 volume ceased to increase in the
Muskingum-Cunge routing
method for long simulations.
Time was being stored as a
single precision integer. Now it is
stored as a double precision
integer.
• Fixed issue where multiple reach
routing methods were causing
the Combined Parameter Editor
(accessed through the CAVI
within CWMS or HEC-RTS) to not
load correctly.
• Fixed issues that prevented
optimization of SWE parameters
in Gridded Temperature Index
Snow.
• Fixed issue where a special
character in the meteorologic
model name results in
precipitation data not being
written to DSS.

Beta release: 06 May 2021
Final release: 21 Jan 2022
29.3.1 New Features
29.3.1.1 Multiple Element Merge

In previous versions of HEC-HMS, merging elements was limited to two elements at a time. The merge logic
has been re-written so that the number of elements that can be merged is unrestricted. To be eligible for
merge, the elements must be of the same type and contiguous in hydrologic order. In the images below, the
image on the left shows multiple elements selected for merge. The image on the right shows the resultant
delineation after merging.

This feature was implemented as a part of ongoing GIS work. Funding sources include the Corps Water
Management System (CWMS) National Implementation Program. Initial code implementation and
documentation were done by Thomas Brauer. Testing was done by Thomas Brauer, Matt Fleming, and Mike
Bartles.
29.3.1.2 Enhanced Element Split

In previous versions of HEC-HMS, splitting elements was limited to locations that coincided with the
identified streams layer. The element split logic was been re-written to be more robust, more performant, and
allow subbasin element splitting from any location within the selected subbasin.
If the selected element is a headwater subbasin, a reach will be created that connects the upper subbasin to
the outlet.
If the selected element is an intermediary subbasin, a reach will be created that connects the upper subbasin
to the existing stream network.

This feature was also implemented as a part of ongoing GIS work. Funding sources include the CWMS
National Implementation Program. Initial code implementation and documentation were done by Thomas
Brauer. Testing was done by Thomas Brauer, Matt Fleming, and Mike Bartles.
29.3.1.3 Basin Reproject

In previous versions of HEC-HMS, the basin model coordinate system could not be changed once initialized.
In this version, the basin model coordinate system can now be changed in the Coordinate System Dialog,
accessed from the GIS | Coordinate System menu. When a new coordinate system is set for the basin
model, all GIS files associated with the basin model are reprojected and the basin map is re-rendered.
This feature was also implemented as a part of ongoing GIS work. Funding sources include the CWMS
National Implementation Program. Initial code implementation and documentation were done by Thomas
Brauer. Testing was done by David Ho.

29.3.1.4 Automated Forecast

An automated forecast option has been added that automatically pulls data from the web, and generates a
continuous forecast with look back period data and forecast period data. The automated forecast option is
built to be extensible but currently only references data sources for the Continental United States. To run the
automated forecast, you must have basin model with spatial elements (georeferenced subbasin elements).
Subbasin elements should use a structured or unstructured discretization. The basin model should also be
configured for continuous simulation.
The automated forecast option is available in the Forecast Alternative Manager shown below. The Forecast
Alternative Manager can be accessed from Compute | Forecast Alternative Manager.
The automated forecast wizard is four steps. In the wizard the user selects a name for the forecast, the basin
model for the forecast, look back period data, and forecast period data. The image below shows step four of
the wizard where forecasting data is selected. The look back and forecast data is automatically merged in
order of precedence.
This feature was funded by through the USACE General Investigations program and the Mississippi River
Geomorphology & Potamology program. Initial code implementation and documentation were done by
Thomas Brauer. Testing was done by Thomas Brauer.

29.3.1.5 Output Control

The new Output control options includes minimal, all, and selected options. If the minimal option is selected,
only the minimum output required by HEC-HMS will be written. If the all option is selected, all time-series
results will be written. If the selected option is chosen, the user can specify which time-series will be written,
and select the output interval for the written results. There are some results, like flow from an element, that
cannot be turned off. The output control option is available for all compute types. The output control
selection on the simulation run component editor is shown below.
The image below shows the custom output editor. The custom output editor is available by selecting the
settings icon next to the output selection. Time-series output can be controlled for each element and time-
series-type combination. There are table filters for element and time-series type.
For more details regarding customizable output for a simulation run, see Simulation Results Output (see page
531).
This feature was implemented as a part of ongoing runtime reduction work. Funding partners include the
U.S. Army Corps of Engineers Northwestern Division (Columbia River Basin). Initial code implementation was
done by Caleb DeChant, Contractor, Paul Ely, Contractor, and Thomas Brauer. Documentation was completed
by Thomas Brauer, Matt Fleming, and Mike Bartles. Testing was performed by the entire HEC-HMS team.

29.3.1.6 Generalized Meteorologic Processes

In previous versions of the program, some meteorologic boundary conditions were treated as a modeling
method, while others were treated as input to a modeling method. In the example below, air temperature and
windspeed are selected as parameters to the Penman-Monteith evapotranspiration modeling method.
The meteorologic model has been generalized so that all meteorologic processes are treated as a modeling
method. In the example below, modeling methods have been enabled for air temperature and windspeed.
These will be used as inputs to the Penman-Monteith evapotranspiration method.
Funding partners for this feature include the CWMS National Implementation Program. Initial code
implementation was done by Paul Ely, Contractor and Thomas Brauer. Documentation was completed by
Thomas Brauer. Testing was performed by the entire HEC-HMS team.
29.3.1.7 Basin-Meteorology Linking

In previous versions, meteorologic models and basin models had to be linked for a simulation to proceed.
Failing to link the basin and meteorolgic model would result in ERROR 15256 at simulation time indicating
that the meteorologic model is not set up to work with the basin model. In this version basin-meteorology

linking is not required unless the meteorology needs subbasin-level parameterizations. Subbasin
parameterizations in the meteorologic model are common for subbasin-average methods and are
uncommon for gridded methods. If the meteorologic model uses predominantly gridded methods, the basin-
metorologic linking will likely not be required and the Basins tab will disappear from the component editor. If
the meteorologic model requires basin-metorologic linking, the Basins tab will be present in the component
editor and must be parameterized. The component editor on the left illustrates a meteorologic model that
uses the Specified Thermograph temperature method and requires a basin-meteorologic model linking. The
component editor on the right illustrates a meteorologic model that uses all gridded methods and does not
require basin-meteorologic linking.
Funding partners for this feature include the CWMS National Implementation Program and the USACE
Environmental R&D Program. Initial code implementation was done by Paul Ely, Contractor and Thomas
Brauer. Documentation was completed by Thomas Brauer. Testing was performed by the entire HEC-HMS
team.
29.3.1.8 Normalizer Utility

Vortex's Normalizer has been integrated into HEC-HMS as the Grid Normalizer Utility. Its main purpose is to
scale grid cells in the source grid by the value of the accumulated normals grid cell over the normalization
period, divided by the value of the accumulated source grid cell over the normalization period. This tool is
accessible by navigating to Tools | Data | Normalizer.
For more details regarding the Normalizer Utility and its functionality, visit Normalizer Wizard Manual102.
102 https://www.hec.usace.army.mil/confluence/display/HMSUM/.Normalizer+v4.9

Geomorphology & Potamology program. Initial code implementation was done by Thomas Brauer and Nick
Van. Testing and documentation was done by Garrett Blomstrand, USACE-MVP, and Brett Hultgren, USACE-
MVP.
29.3.1.9 Gridded Data Processing Utilities

In addition to the Normalizer, the Vortex Calculator, Clipper, Grid-to-Point-Converter, Sanitizer, and Shifter
utilities have been added to the HEC-HMS user interface. The data processing utilities are available from the
Tools | Data menu. You do not have to have a project open to launch the data processing utilities.
User's Manual documentation to come.
Geomorphology & Potamology program. Vortex development is led by Thomas Brauer. User interfaces for
HEC-HMS were implemented by Nick Van and Daniel Black. Testing and documentation was done by
Thomas Brauer, Nick Van, Daniel Black, Natasha Sokolovskaya, and Simon Evans, USACE-NAB.

29.3.1.10 Generalized Extreme Value and Four-Parameter Kappa Distributions

The Generalized Extreme Value (GEV) and four-parameter kappa distributions were added to the Uncertainty
Analysis - Simple Distribution list of distributions. They are mainly intended to be used with precipitation
parameters, especially the Hypothetical Storm Point Depth parameter as shown below.
Code implementation, documentation, and testing for this feature was performed by Greg Karlovits. This
feature was funded by the USACE F&CS R&D program.
29.3.1.11 Constant Value Error Term - Regression With Additive Error

A "constant value" option was added to the distribution choices for the Regression With Additive Error
sampling method in the Uncertainty Analysis. This allows the user to specify a completely deterministic
relationship between two variables in the sampling scheme. Typically, the constant value will be zero, but
the user may specify any value. An example is shown below that ensures, for a single subbasin, the time of
concentration (which is controlled by a Simple Distribution method sampler) and the storage coefficient will
always be related using the following equation: .

29.3.1.12 Additional Baseflow Parameters Available in Uncertainty Analysis

Parameters for the Linear Reservoir layer fractions were added to the Uncertainty Analysis so that the user
can simulate the effects of flow being split between the various groundwater layers. The layer fractions
must add up to a value between zero and one, so care must be taken in sampling these values. It is
recommended to use the Specified Values sampling method for these parameters to ensure this inequality
holds. Alternatively, using the beta distribution paired with the regression with additive error and constant
value epsilon term can ensure the fractions add up to a constant value.
The Linear Reservoir baseflow method was expanded to include a third layer in version 4.4; however, its
parameters were not made available to the Uncertainty Analysis. In this release, the Groundwater 3
coefficient, number of steps, fraction, and initial condition are available for use in the Uncertainty Analysis.
29.3.1.13 Simple Canopy Crop Coefficient Available in Optimization Trial and

The crop coefficient parameter is important for computing actual evapotranspiration in continuous
simulations. It can now be optimized using an optimization trial, or its sensitivity explored using the
29.3.1.14 Global File Reference Table

A new global file reference table displays file references for shared data and simulations. The global file
reference table is available from the File | References menu. The file path field of the global file reference
table is editable by the user.

If a file reference is missing when the project loads, the global file reference table will be launched and
filtered for invalid references. This gives the user an opportunity to correct bad file references. In previous
versions of HEC-HMS, repetitive dialogs were displayed for each missing file reference.
implementation and documentation was done by Thomas Brauer. Testing was done by Alex Davis.
29.3.1.15 Default Behavior when File is Missing

In previous versions of the program, if a shared component file was missing, the file path would be
automatically changed to the project DSS file. This caused computes to fail at runtime but would introduce
confusion when trying to determine to the original file. In this version, the default behavior has been changed
so that the path to the missing file is maintained. The compute will fail at runtime, as it should, but the path
to the original file will be more obvious to the user.
Missing file references typically occur when file references are made external to the HEC-HMS project. This
practice is discouraged by the HEC-HMS team. A data directory has been added to the HEC-HMS project
directory. This location is intended to house data that is referenced by the HEC-HMS project.
implementation and documentation was done by Thomas Brauer. Testing was completed by Thomas Brauer
and Mike Bartles.
29.3.1.16 Visual Cues for File References

Visual cues have been added to indicate whether a file reference is external to the project, or missing. In the
filename text field: if the text is orange, the file exists but is external to the project. If the text is red, the file
does not exit. As in previous versions, blue text indicates that the text field has changed since that last time it
was saved.

implementation and documentation was done by Thomas Brauer. Testing and documentation was
completed by Thomas Brauer and Mike Bartles.
29.3.1.17 2D Diffusion Wave Transform Enhancements

hydraulic results, most notably to stage hydrographs. Please see the latest HEC-RAS v6.0 release
notes103 for further details.
Mike Bartles. Testing was completed by Alejandro Sanchez, Jay Pak, Matt Fleming, and Mike Bartles.
29.3.1.18 2D Flow Support for macOS and Linux

Starting from this version, you will be able to take advantage of the advanced 2D flow capabilities in HEC-
HMS when working on Windows, macOS, or Linux.
Initial code implementation and documentation for this feature was performed by Richard Rachiele,
Contractor and Nick Van. Testing was completed by Nick Van, Alejandro Sanchez, Thomas Brauer, and Mike
Bartles.
29.3.1.19 Pre-packaged Native Dependencies for Linux

Previously, you would have to run a script to install the necessary dependencies for HEC-HMS on Linux. With
this update, the native dependencies for HEC-HMS Linux are packaged within the distribution; thereby
eliminating the need for you to run the said script. The packaged natives have been tested on Ubuntu 20.04
LTS, and should also work for the more recent versions of Ubuntu.
Initial code implementation, documentation, and testing for this feature was performed by Nick Van.
103 https://www.hec.usace.army.mil/confluence/rasdocs/rasrn

29.3.1.20 Optimization using Snow Water Equivalent Time Series

HEC-HMS optimization tools offer two deterministic search algorithms that move from the initial parameter
estimates to the final "best" parameter estimates using a variety of objective functions. You can now utilize
snow water equivalent (SWE) time series to optimize snowmelt parameters (e.g. Base Temperature, PX
Temperature, Wet Meltrate, etc). Five statistical metrics, which measure goodness of fit between simulated
and observed time series in a different way, have been implemented for use with SWE time series
optimization: Mean of Absolute Residuals, Max of Squared Residuals, Sum of Squared Residuals, Peak-
Weighted Root Mean Square Error, and Percent Bias.
Initial code implementation and documentation for this feature was performed by Mike Bartles. Testing was
completed by Mike Bartles, Greg Karlovits, and Matt Fleming.
29.3.1.21 Maricopa Tools

Three new tools designed to facilitate a specific work flow adopted by Maricopa County have been added to
HEC-HMS under Tools | Data | Maricopa. Each of the Maricopa tools (Clark, S-Graph, and Green-Ampt)
launch a wizard where the user can point to tabular soil and land-use data as well as geospatial soil, land-
use, and flow-path data. At the end of the wizard, HEC-HMS performs various table joins and geometry
intersections to compute subbasin average parameters. The appropriate global editors and component
editors are automatically populated with the computed parameters.
Initial code implementation and documentation for this feature was performed by Thomas Brauer and Josh
Willis. Testing was completed by Thomas Brauer, Josh Willis, and Matt Fleming.
29.3.1.22 Debris Yield Global Editors

The Global Editor is now available for 5 Debris Yield methods: LA Debris Method EQ1, LA Debris Method EQ
2-5, Multi-Sequence Debris Prediction Method (MSDPM), USGS Long Term Debris Model, and the USGS
Emergency Assessment Debris Model. These method parameters previously needed to be entered for each
subbasin element but users can now add and modify parameter values in the Global Editor panel.

The debris yield global editors were funded by the USACE Arid Regions work unit within the Flood and
Coastal Systems Research and Development program. Initial code implementation, documentation, and
testing for this feature was performed by David Ho, Thomas Brauer, and Jay Pak,
29.3.1.23 Calibration Summary Table

A calibration summary table with statistics can now be accessed via Results | Calibration Summary Table or
via the Results tab of the watershed explorer window. RMSE Stdev, Nash Sutcliffe, Percent Bias, and R2
statistics are available for each computation point with observed flow data. This table has been
implemented for simulation and forecast alternative compute types.
Initial code implementation and testing for this feature was performed by Josh Willis and Thomas Brauer.
29.3.1.24 Differential Evolution Optimization Search Method

The Differential Evolution104 global optimization method was added as a search method to the Optimization
Trial. This search method is more robust for multiple parameter optimization than the Simplex search
method.
Initial code implementation and documentation for this feature was performed by Greg Karlovits. Testing of
this feature was performed by Greg Karlovits and Matt Fleming. Haden Smith (USACE Risk Management
Center, RMC) provided an algorithmic prototype of the Differential Evolution algorithm, and unit test
examples. This feature was funded by the USACE F&CS R&D program.
29.3.1.25 Optimization Data Transforms

Two data transformation options were added to the Optimization Trial: log base 10, and Box-Cox105. These
transforms are applied to the observed and simulated data before computing the objective function. Both
transforms estimate a shift parameter to ensure the transformation is always computed on positive values.
The Box-Cox transform automatically estimates the power (lambda-1) parameter using a maximum
likelihood approach.
104 https://en.wikipedia.org/wiki/Differential_evolution
105 https://en.wikipedia.org/wiki/Power_transform#Box%E2%80%93Cox_transformation

Initial code implementation, documentation, and testing for this feature was performed by Greg Karlovits.
Haden Smith (RMC) provided an algorithmic prototype of the Box-Cox transformation and parameter
estimation. This feature was funded by the USACE F&CS R&D program.
29.3.1.26 Spatial Results Tooltips and Time Series

When valid spatial results are selected and you hover over a valid cell, a tooltip denoting the value and units
for the selected variable and time step will be shown. Within the following image, Cell Velocity has been
selected within the Animation Toolbar, the slider bar has been advanced to 03Jan1997:0200, and the mouse
hovered over a cell which contains valid results:
Also, when valid spatial results are selected, a right-click option allows for the display of a time series of the
selected variable for the entire simulation time window. Within the following image, Snow Water Equivalent
(SWE) has been selected within the Animation Toolbar and the time series plotted by right clicking within a
cell that contains valid results and selecting Plot Spatial Results:
Initial code implementation for this feature was performed by Shannon Newbold, Caleb Dechant, and Mike
Bartles. Documentation and testing was performed by Mike Bartles and Tom Brauer. This feature was
funded by the USACE RMC.

29.3.1.27 2D Sediment Transport

The 2D Sediment Transport method was developed to work with the subgrid framework of the 2D Diffusion
Wave transform method106. This Erosion method computes subgrid erosion and deposition rates, bed
elevation, gradation, and bed layering. Sediment transport is computed with a non-equilibrium total-load
formulation. The total-load transport equation is solved with implicit Finite-Volume methods on the same
unstructured polygonal mesh as the 2D flow solver. The Component Editor for this method is shown in the
following figure.
761 2D Sediment Transport Component Editor
Spatial variables specific to 2D Sediment Transport including total/clay/silt/sand/gravel sediment

concentration and total/clay/silt/sand/gravel bed change can be displayed within the map. In the following
image, clay sediment concentration is shown throughout a subbasin that uses the 2D Sediment Transport
Erosion method. Also, videos of total sediment concentration and silt bed change during a flood event are
shown below.
762 Clay Sediment Concentration
106 https://www.hec.usace.army.mil/confluence/hmsdocs/hmsum/latest/subbasin-elements/selecting-a-transform-method

Sorry, the video is not supported in this export.

Movie URL not available.

Only the Clay Silt Sand Gravel grade scale may be used with this Erosion method. More information
pertaining to this feature can be found here107. A presentation regarding 2D Flow and 2D Sediment
Transport features was made on September 29th, 2021. Materials used during this presentation can be
found here108 while a recording of the presentation can be viewed here109.
Initial code implementation, documentation, and testing for this feature was performed by Jay Pak, Alex
Sanchez, and Mike Bartles. This feature was funded by the USACE Flood and Coastal R&D program.
29.3.1.28 Rename Basin Model Elements

An option was added to rename multiple basin elements from a Rename Basin Elements table that can now
be accessed by right-clicking a basin name in the Components tab of the Watershed Explorer, as shown in
Within this table, multiple basin elements can be renamed at once. Tools to filter by element type (e.g.
Subbasin, Junction, etc.) and sort either hydrologically or alphabetically are included to aid in identifying the
element(s) of interest.
107 https://www.hec.usace.army.mil/confluence/hmsdocs/hmsum/latest/erosion-and-sediment-transport/subbasin-sediment
108 https://www.hec.usace.army.mil/confluence/hmsdocs/hmstr/hec-hms-usace-hh-c-cop-webinar-series-51479129.html
109 https://youtu.be/wTu3eRz0bn8

A demonstration of this new feature can be found here:
Sorry, the widget is not supported in this export.

http://youtube.com/watch?v=vNco8VmgB80
Initial code implementation for this feature was performed by Natasha Sokolovskaya. Documentation and
testing were performed by Natasha Sokolovskaya, Mike Bartles, and Tom Brauer.
29.3.1.29 Updated Raster Display Settings Editor

The Raster Display Settings Editor has been redesigned to become more intuitive. With the new editor, the
user can choose between two Symbology types: 'Classify' and 'Stretch'. The 'Classify' symbology option
allows the user to specify color bins to display the data. An example of the 'Classify' UI is shown below.

Meanwhile, the 'Stretch' option allows the user to specify the max and the min values, and each data point
would be mapped to a color corresponding to its position between max and min. For example, in the UI for
'Stretch' option below, if the data value is '16.999' (i.e. the min), it would be mapped to the left-most color of
the color scheme (purple-ish in this case).
More information pertaining to spatial results can be found here110.

Initial code implementation for this feature was performed by Nick Van. Documentation and testing were
performed by Nick Van, Mike Bartles, Tom Brauer, and Matt Fleming.
29.3.1.30 DSS Grid Record Validator

A DSS Grid Record Validator utility was added to help modelers identify issues within their gridded boundary
conditions (e.g. precipitation, temperature, SWE, etc) that would prevent a simulation from
successfully completing.
Requirements for gridded datasets include:
• number of rows and number of columns remain constant throughout the simulation,
• lower left corner coordinates remain constant throughout the simulation,
• projection (e.g. SHG) remains constant throughout the simulation, and
• grid cell size remains constant throughout the simulation.
Additionally the grid record validator validates each grid record based on the grid type specified. Record
requirements are specified in Grid Data (see page 167) and include:
• valid data type (e.g. PER-CUM, INST-VAL),
• valid C-Part,
• valid units, and
• valid start and end times.
This utility can be launched from the Grid Data Manager or by right clicking the Gridset of interest and
selecting Validate, as shown in the following image.
110 https://www.hec.usace.army.mil/confluence/hmsdocs/hmsum/latest/hydrologic-simulation/viewing-spatial-results

763 Validating a Precipitation Gridset
The utility will loop over all records contained within the referenced DSS file and check for issues like those
noted above. If any issues are encountered, error messages will be shown informing the user, as shown in
the following image.
764 Grid Data Validation Results
Initial code implementation for this feature was performed by Tom Brauer. Documentation and testing were
performed by Mike Bartles, Tom Brauer, and Matt Fleming.
29.3.2 Bugs Fixed


29.3.2.1 Subbasin and Reach Characteristics Not Sorted Correctly

When initially computing subbasin and/or reach characteristics, the resulting list of characteristics was not
sorted using hydrologic order though it was reported as such. Logic was added to automatically sort the list
of characteristics in hydrologic order.
29.3.2.2 Outflow for Normal Depth Reach Routing Method Equal to Zero
When using the Normal Depth reach routing method and the initial flow value was equal to zero, all
subsequent values were set equal to zero regardless of the inflow to the reach element. The solver has been
modified to rectify this error.
29.3.2.3 Flow Rate Threshold value in Debris Yield Methods

When using the Flow Rate Threshold value in debris yield methods with English units, storm events were not
divided correctly for continuous simulation by setting the lower limit for direct runoff flow rate. This occurred
due to a unit conversion issue and has been corrected.
29.3.2.4 No-Data Value Dropped When Computing A Reconditioned Terrain

When using the Terrain Reconditioner, if the original elevation raster file had a No-Data value other than
3.40282e38 it was incorrectly being dropped when writing the reconditioned raster file. This has been
corrected so that the reconditioned raster file now maintains the No-Data value from the elevation raster.
29.3.2.5 Using the Terrain Reconditioning Tool on a Basin Model Name that
Contains Hyphens.
When using the terrain reconditioning tool, the "reconditioned.tif" file was not correctly written to disk when
the Basin Model name contained hyphens. This has been fixed so that hyphens are correctly handled.
29.3.2.6 Observed Stage Time Series

Observed and computed stage time series were duplicating observed and computed flow time series. This
bug has been fixed such that stage time series are now correctly written to disk and available for graphing/
plotting within the user interface.
29.3.2.7 Importing a 2D Mesh

Three errors were addressed that could be encountered when importing a 2D mesh from an HEC-RAS plan
HDF file (i.e. .p##.hdf):
1. If the coordinate reference system (CRS) of the HDF file did not match that of the Basin model, errors
could arise when attempting to compute. This has been addressed such that the CRS of the HDF file

is compared against that of the Basin model when importing. If they are not equivalent, the import is
halted and an error message is thrown.
2. Currently, HEC-HMS only supports external 2D Connections or boundary condition lines. Previously,
no checks were made to ensure that the selected 2D area contained only external boundary condition
lines. This has been addressed with a check when importing; if any internal boundary condition lines
are encountered, the import is halted and an error message is thrown.
3. If the area encompassed by the 2D mesh differs by more than 1% when compared to the selected
subbasin, you can now opt to set the subbasin area equal to the area encompassed by 2D mesh. If
the area encompassed by the 2D mesh differs by more than 10% when compared to the selected
subbasin, the import will now be halted.
29.3.2.8 Renaming a Subbasin that Uses the 2D Diffusion Wave Transform

Within previous versions, when a subbasin was renamed, the mesh information within the associated .hdf file
was not renamed. If you attempted to compute after renaming a subbasin, an error 10000 message was
thrown. Now, both the subbasin and mesh information is renamed appropriately.
29.3.2.9 Standard Report Unable to Generate Report for Depth Area Simulations
The standard report was not generated for Depth Area simulations. This has been fixed so that the Standard
Report can generate reports for Depth Area simulations.
29.3.2.10 Subbasin latitude and longitude assignment after delineation

The subbasin latitude and longitude were incorrectly assigned to subbasin elements after delineation. This
bug was introduced in v4.4.
29.3.2.11 Temperature Index Snowmelt Spatial Results

When writing and/or viewing spatial results for simulations that utilized temperature index snowmelt, the
values within Meltrate ATI and Cold Content ATI grids were incorrect. Specifically, Meltrate ATI spatial result
values were not being converted to the basin model unit system and Cold Content ATI spatial result values
were being treated as depths instead of temperatures. Now, both values are treated correctly.
29.3.2.12 Univariate Search Parameter Value Unit Conversions

There was a unit conversion error that affected the search values within the Univariate search method (in an
Optimization Trial) when the basin model was in the U.S Customary unit system. Specifically, parameters
with units that differ between USCS and metric (for example infiltration rate) would not convert correctly
during the search. The error would potentially prevent search convergence. The unit conversion issue was
fixed.

29.3.2.13 CAVI/HEC-RTS Annual Pattern Paired Data Issue

When attempting to extract a new forecast using CAVI or HEC-RTS, an error message was thrown indicating
that Annual Pattern paired data was not being correctly copied to the new forecast. In actuality, the data was
being correctly copied and the error message was unnecessary. This erroneous error message has been
fixed and all paired data are correctly copied to the forecast directory.
29.3.2.14 Tabulating Results for a 2D Connection

Within previous versions, when a 2D Connection time series was tabulated, multiple columns were created
within the resultant table. Now, only the selected time series for the 2D Connection will be shown within the
table.
29.3.2.15 Gridded Curve Number Loss Method

In previous versions, the Gridded Curve Number loss method was assumed to only be used with gridded
meteorologic models (i.e. meteorologic models that use gridded boundary conditions). If you attempted to
compute a simulation that used the Gridded Curve Number loss method with a non-gridded meteorologic
model, the simulation failed with no error message. Now, the Gridded Curve Number loss method can be
used with both gridded and non-gridded meteorologic models.
29.3.2.16 Using an Objective Function that Conflicts with the Optimization Trial
Compute Window
In previous versions, an Objective Function with a time window that conflicted with the compute window of
an Optimization Trial was allowed. For example, an Objective Function that evaluated model performance
from 01Jan2000 00:00 to 10Jan2000 00:00 could be used with an Optimization Trial that computed results
from 02Jan2000 00:00 to 03Jan2000 00:00. Now, the compute will halt and an error message will be thrown
indicating that the Objective Function time window must be within the Optimization Trial compute window.
More information pertaining to Optimization Trials can be found here111.
29.3.2.17 Standard Report Failure Due to Error When Attempting to Reformat

Project's Title
When attempting to reformat a project name that contains unsupported characters, the Standard Report
generator would fail and exit midway through the process. This has been fixed, such that if the program fails
to reformat the project name, it would use the original project name.
29.3.2.18 Standard Report Missing Subbasins

In previous versions, the Standard Report would fail to recognize basin files that did not follow a certain
naming convention. Now, the Standard Report is able to locate the correct files based on the selected
simulation.
111 https://www.hec.usace.army.mil/confluence/hmsdocs/hmsum/latest/model-optimization/optimization-trials

29.3.2.19 Malformed State Serialization with Gridded Soil Moisture Accounting

Loss Method
The Gridded Soil Moisture Accounting loss method was incorrectly saving its state file causing problems
initializing states when using a start state file. The Gridded Soil Moisture Accounting loss method now
correctly serializes its state. This issue is limited to projects that use Save/Start states with the Gridded Soil
Moisture Accounting loss method.
29.3.2.20 Renaming ASC/GeoTIFF grids from the Grid Data Manager

Support for ASC/GeoTIFF grid data file types was added in a recent version. A bug was fixed that prevented
renaming these grids from the Grid Data Manager.
29.3.2.21 The Percent Impervious Area Adjustment was Applied Twice to Losses
Sent to the Linear Reservoir Baseflow Method
The Linear Reservoir baseflow method is passed infiltration or percolation time-series from the selected loss
method. A bug was fixed where the incorrect infiltration was being passed to the linear reservoir baseflow
method, the impervious area adjustment was applied twice for subbasin elements using the Initial and
Constant, SCS, Exponential, Green and Ampt, and the Smith Parlange loss methods.
29.3.2.22 Optimization Trial Returning Parameter Values Outside the User-

Specified Range
The objective function's linear penalty function for out-of-range parameters was not punitive enough to
prevent searches from returning optimum parameter values outside of the user-specified range for the
parameters. A new penalty function that is exponential instead of linear creates a steeper penalty to the
objective function for out-of-range parameters, vastly decreasing the likelihood of the Trial returning
optimum parameters that are out of range.
29.3.2.23 Selecting a New Downstream Connection

In previous versions, when the Downstream connection was changed for a given basin element (e.g.
junction), the drop down menu selection would revert to None. This issue has been fixed such that a new
downstream connection is correctly saved on the first try without first reverting to None.
29.3.2.24 Copying a Maximization Goal Optimization Trial Causes a Time Window

Error
If a maximization goal optimization trial was copied, changing the time window in the new trial and running it
resulted in an error. The error was fixed by adding an additional check for the maximization goal
optimization trial time window at runtime.

29.3.2.25 Grid Editor Panel fails to open on Ubuntu

A NullPointerExecption prevented the Grid Editor Panel from opening on Ubuntu. Logic was added to avoid
the NullPointerException and allow the editor to open.
29.3.3 Known Issues

Method
Simulations containing the Hamon Evapotranspiration method will compute successfully without an Air
Temperature method selected. If the Hamon Evapotranspiration method is selected in the Meteorologic
model, and an Air Temperature method is not selected, the simulation will still run successfully. This will
occur if the "Replace Missing" option in the Meteorologic model is set to either Abort Compute or Set to
Default.
29.3.3.2 Grid-to-Point-Converter & Calculator Utility

The Vortex Grid-to-Point-Converter was added to HEC-HMS in v4.9. A bug was introduced in the utility in an
attempt to update a progress bar in the user interface. As a result the progress bar is inaccurate and the
performance of the utility is impacted.
The Vortex Calculator was added to HEC-HMS in v4.9. A bug was found in the utility when attempting to
multiply, divide, add or subtract with floating point values. While the user could enter a float value, the
compute would not create a DSS file with the updated grids.
Users who want to use the Grid-to-Point-Converter utility or the Calculator Tool are encouraged to use Vortex
version 0.10.27 or greater. Standalone versions of vortex can be downloaded here112. Alternatively portable
distributions of HEC-HMS v4.9 can be updated by deleting the vortex-0.10.26 and vortex-ui-0.10.26 jars and
adding vortex and vortex-ui jars, v0.10.27 or greater.
Downloads:
• vortex-0.10.27.jar113
• vortex-ui-0.10.27.jar114
beta.1 05 May • Initial beta release

2021
112 https://github.com/HydrologicEngineeringCenter/Vortex/releases
113 https://www.hec.usace.army.mil/nexus/repository/maven-public/mil/army/usace/hec/vortex/0.10.27/vortex-0.10.27.jar
114 https://www.hec.usace.army.mil/nexus/repository/maven-public/mil/army/usace/hec/vortex-ui/0.10.27/vortex-ui-0.10.27.jar

beta.2 25 May • Cached reprojection logic • Avoided array index out of bounds
2021 in meteorologic model exception when there is missing
compute to make compute data at the end of a compute. This
more efficient. issue was observed with a Gridded
• Added breakpoint import Hamon compute. Gridded Hamon
option in Breakpoint is a function of daily average
Manager. temperature so tries to find
• Added option to specify temperature grids for the entire
lookback period in day.
automated forecast wizard. • Improved the memory efficiency
of the terrain reconditioner.
• The new output control option lets
the modeler save results at a
coarser output interval than the
simulation time step. Flow results
were incorrectly being saved as an
instantaneous value. This was
corrected for the beta 2 release,
flow is now saved as an average
over the selected time step
duration.
beta.3 14 Jun • Added layer export option • Added handling for the case where
2021 for breakpoints and the terrain associated with a basin
discretizations. model is deleted or the user
• Enhanced element split. attempts to link a new terrain data
• Added 2D Flow support for to an existing basin model.
macOS and Linux.
• Packaged native
dependencies in Linux
distribution.
• Right-click, zoom to
element option from
element in watershed
explorer.

beta.4 22 Jun • Right-click, clear messages • Check the input terrain file for a
2021 option from the message valid Coordinate Reference
log. System rather than the processed
• Added visual cues for file- terrain file. This caused the
referencing text fields. process terrain file to not be set
• Snow water equivalent time and the terrain shared data
series optimization. component was not selectable
• Added Maricopa Clark, S- from the basin model component
Graph, and Green-Ampt editor.
tools. • Trim text when renaming
components. This eliminates
situations where the name ends in
an empty character.
• The standard report tool was not
able to run for Depth Area
simulations. This bug has been
fixed.

beta.5 29 Jul • Basin reproject logic • When using the new output
2021 enabled from the control option with an Uncertainty
Coordinate System dialog. analysis, output could not be
• Clear messages when saved and the simulation would
project closes. fail to compute. This bug has
• New global editors for been fixed.
MUSLE and build up wash • When attempting to use any of the
off erosion. four gridded loss methods in
• Generalized Junctions → combination with the 2D Diffusion
Snap to Downstream to Wave transform method, the
Icons → Reset Location. compute would fail. Now, you are
This resets the locations able to make use of the Gridded
for all icons. Deficit Constant, Gridded Green
• Added Calibration Ampt, Gridded SCS Curve Number,
Summary Table. and Gridded Soil Moisture
Accounting loss methods with 2D
flow.
• Fixed logic time-series table
initialization logic for outflow
structures' time-series.
• Added checks for NaN values in
gridded temperature index initial
grids.
• Added more robust relative path
logic in cmd and exe launchers.
• Overhauled the time series results
framework to key off of a time
rather than a common index
position. This is intended to
accommodate customizable
output control.
• Corrected reach length label from
"M" to "KM" in global reach
characteristics dialog.

beta.6 23 Aug • Reproject features to basin • Fix logic for establishing the reach
2021 model coordinate system split tolerance. The previous logic
when features are imported wrongly triggered the following
via GIS | Import error message when attempting to
Georeferenced Elements. split reaches: Could not split the
• Add option to recompute element because the split point did
latitude and longitude for not intersect the element.
basin elements from GIS | • Corrected subbasin latitude and
Compute menu. longitude assignment for subbasin
• Debris Yield Method Global elements after delineation.
Editor Previously latitude was set as
• Global file reference table longitude and vice versa.
accessible from File | • Fixed the Compute to Point
References menu. feature when using gridded
boundary conditions. Previous
changes to the meteorologic
model had temporarily disabled
this feature.

beta.7 07 Oct • Updated Raster Display • Fixed missing text string

2021 Settings Editor resources for GEV distribution
labels within the Uncertainty
analysis
• Disabled AGU20 grade scale when
using the 2D Sediment Erosion
method. Only the Clay Silt Sand
Gravel grade scale may be used
with this method.
• Fixed units within spatial results
time series plots and tool tips for
average cell velocity, sediment
concentration, and water surface
elevation.
• When plotting water surface
elevation spatial results time
series plots, choose an
appropriate minimum value for
this variable. Previous beta
versions used an initial value of 0
which caused plots to be
unreadable when large water
surface elevation values were
computed and shown.
• Fixed an issue with subbasin
latitude/longitude coordinates
being backwards when importing
elements from a shapefile.
• Fixed a units conversion issue
with the Univariant Search
method.
software's program file would be
deleted when renaming a project.

beta.8 16 Nov • Added vortex utilities to • Fixed missing temperature index

2021 Tools | Data menu parameters within Optimization
Trial Parameter component editor.
• Fixed blank wizard pane when
clicking GIS | Export Layers.
• Fixed incorrect snow
accumulation within grid cells
when using 2D Diffusion Wave
transform.
• Fixed error where Standard Report
fails to generate reports for some
projects.
• Fixed missing subbasins when
generating a Standard Report.
• Fixed copies of the original being
saved when renaming
Optimization Trials, Uncertainty
Analyses, and Forecast
Alternatives.
• Fixed issue with Optimization Trial
results always displaying out of
date.
• Fixed issue with Gridded Soil
Moisture Accounting loss
serialization when using save
states.
• Added Precipitation-Frequency
grid entry in project interface
properties file.
• Write relative humidity, dew point,
and windspeed time series to
meteorologic DSS file from a
gridded meteorologic simulation.
This makes the humidity, dew
point, and windspeed results
available from the results tab.
• Fixed incorrect infiltration being
passed to the linear reservoir
baseflow method, the impervious
area adjustment was applied twice
for subbasin elements using the
Initial and Constant, SCS,
Exponential, Green and Ampt, and
the Smith Parlange loss methods.
• Fixed incorrect units for wind
speed in the gridded Penman
Monteith evapotranspiration
method.


• Fixed issue that prevented
renaming ASC/GeoTIFF grids.
• Added handling logic for case
where ASC/GeoTIFF raster does
not exist when attempting to save.
• Fixed issue where subbasin
rename in the basin model was
not reflected in the meteorologic
model.
• Fixed issue where snow
accumulated interception did not
show up in result graphs.
beta.9 18 Nov • Fixed issue where downstream

2021 connections were not saved
correctly
beta.10 02 Dec • Fixed issue where a computed

2021 stage time series was being
tabulated as an observed flow
time series.
• Fixed issue where computed and/
or observed stage time series
were being plotted with a missing
y-axis label.

Beta released: 15 Jan 2021
Final release: 08 Apr 2021
29.4.1 New Features
29.4.1.1 Build Walls/Burn Streams

Building walls and burning streams can now be achieved entirely in HEC-HMS with the Terrain
Reconditioning tool located within the GIS menu. This tool is very similar to the Build Walls and DEM
Reconditioning tools that are available in HEC-GeoHMS.
The first step of terrain reconditioning involves building walls. The user can input shapefile boundary data
that is used to specify where the cell elevations should be raised in the base terrain dataset. This is
particularly useful if the user wants the HEC-HMS subbasin delineations to exactly match existing datasets

such as subbasin boundaries used in prior studies or the hydrologic units found within the USGS's Watershed
Boundary Dataset (WBD).
The second step of terrain reconditioning involves burning streams to force a stream network onto a terrain.
This is often desirable when the base terrain dataset does not sufficiently capture channel definition within a
watershed. Similar to the build walls step, the user can input a stream shapefile to specify where and how
much to lower cell elevations in the terrain. A sharp drop height can be entered to abruptly lower a single line
of stream cell elevations and/or a smooth drop height and buffer can be entered to gradually lower
neighboring cell elevations so that there is a seamless transition from the center of the stream to the
overbank.
The below figures demonstrate a comparison of a base terrain dataset (below left) and a HEC-HMS
reconditioned dataset with exaggerated, sharp walls and a smoothly burned channel (below right).

For more, see GIS Menu: Terrain Reconditioning115.

The terrain reconditioning tool was implemented as a part of ongoing GIS work. Funding sources include the
CWMS National Implementation Program. Initial code implementation and documentation were done by
Josh Willis and Thomas Brauer. Testing was done by Josh Willis, Thomas Brauer, and Matt Fleming.
29.4.1.2 Subbasin Characteristics Layer Display and Export

After a subbasin characteristics compute is complete, the longest flowpath, centroidal flowpath, 10-85
flowpath, and subbasin centroid layers are saved to the basin model's sqlite file and automatically added to
the map layers for viewing in Basin Model Map. The layers can optionally be exported to shapefile using GIS |
Export Layer.
29.4.1.3 Junctions "Snap to Downstream" and Export

A new "Snap to Downstream" tool can be accessed by right clicking in the Basin Model Map. If junction
elements have a reach as a downstream connection, this tool will snap them to the nearest end of the reach.
Additionally, junctions can now be exported to shapefile via GIS | Export Layer.
115 https://www.hec.usace.army.mil/confluence/display/HMSUM/.GIS+Menu+v4.8

29.4.1.4 USGS Emergency Assessment Debris Model

The USGS Emergency Assessment debris yield model (Garter, Cannon, and Santi, 2014) was added to the
erosion method to predict volume of debris yield due to debris flows within two years of a fire. The USGS
Emergency Assessment debris model can calculate debris yield volume based on three input parameters
(peak 15-minute rainfall intensity, watershed area burned at moderate and high severity, and relief). The
below figure shows the USGS Emergency Assessment Debris Method has been included in the list of Erosion
Methods for a subbasin element.

The USGS Emergency Assessment debris yield method was funded by the USACE Arid Regions work unit
within the Flood and Coastal Systems Research and Development program. The initial code implementation
was done by Jay Pak with testing by Jay Pak.
29.4.1.5 Los Angeles Debris Method EQ 2-5

The Los Angeles District Debris Method EQ 2-5 (Gatwood et al., 2000) was added to the erosion method. The
equation used by this method was developed from statistical analysis of data from areas between 3.0 mi2
and 200.0 mi2 square miles. This method may also be used for drainage areas less than 3 mi2 if peak flow
data available. The Los Angeles District Debris Method EQ 2-5 can calculate debris yield volume based on

four input parameters (peak runoff, drainage area, relief ratio, and fire factor). The Los Angeles District Debris
Method EQ 2-5 works best in arid or semi arid regions of Southern California where it was developed. The
below figure shows the Los Angeles District Debris Method EQ 2-5 has been included in the list of Erosion
Methods for a subbasin element.
The Los Angeles District Debris Method EQ 2-5 was funded by the USACE Arid Regions work unit within the
Flood and Coastal Systems Research and Development program. The initial code implementation was done
by Jay Pak with testing by Jay Pak.

29.4.1.6 Flow Rate Threshold for Debris Yield Methods

The flow rate threshold option was added to four of the HEC-HMS debris yield methods. The threshold was
added to divide storm events when simulating continuous hydrologic conditions that include both dry and
wet periods. A debris flow event starts when the direct runoff is above the flow rate threshold. The event
ends when direct runoff falls below the threshold. The below figure shows the Flow Rate Threshold value has
been included in the subbasin element's Erosion tab.
The Flow Rate Threshold feature was funded by the USACE Arid Regions work unit within the Flood and
Coastal Systems Research and Development program. The initial code implementation was done by Jay Pak
and Paul Ely with testing by Jay Pak.
29.4.1.7 Unregulated Outputs

The ability to produce "unregulated" outputs (e.g. flow, stage, velocity, etc) has been added to HEC-HMS.
Downstream of regulating structures (reservoirs and/or diversion elements), outputs are considered to be
"regulated". However, unregulated outputs are commonly required for use within flood risk management
studies and forecasting applications, amongst others. For instance, unregulated outputs can be compared
against regulated outputs to estimate benefits/damages due to regulation. Also, when fitting a Log Pearson
Type III analytical probability distribution to an annual maximum series of observed peak streamflow using
Bulletin 17C procedures (England, et al., 2019), an annual maximum series of unregulated peak flow is
recommended for use. Removing regulation effects to produce a homogenous, independent, and identically
distributed sample prior to fitting an analytical distribution helps to ensure that inferences of quantile
information (e.g. flow) at rare annual exceedance probabilities (i.e. less than 1/100) are valid and statistically
sound. In the following image, regulated flow (blue line) and unregulated flow (red line) is compared against
observed flow (black line) at a location within the West Branch Susquehanna River for a flood event in
September 2018.

765 Unregulated Outputs
Initial code implementation was done by Paul Ely and Mike Bartles. Documentation and testing were done by
Mike Bartles.
29.4.1.8 New Linear Reservoir Baseflow Option when Paired with the 2D Diffusion
Wave Transform Method
As shown below, a new option was added to the Linear Reservoir Baseflow method that allows the user to
set the groundwater layer to Interflow or Baseflow. By default, the Baseflow option is selected. The Interflow
option can only be chosen when the transform method is set to use the 2D Diffusion Wave method. The
interflow option is an initial attempt to integrated surface-subsurface flow for 2D modeling. If the user
chooses Baseflow, then the routed subsurface water is added to the total flow at the outlet(s) of the
subbasin. If the user chooses Interflow, then the subsurface water is only routed within the 2D cell, where the
infiltration happened. The routed interflow is added to the cell's surface flow and routed on the 2D surface to
downstream grid cells (where it can be infiltrated again). We found this approach could provide adequate
results at the subbasin outlet, and at interior cells within the 2D area. See the example application116.
116 https://www.hec.usace.army.mil/confluence/hmsdocs/hmsguides/applying-the-new-linear-reservoir-baseflow-option-with-2d-surface-
flow

29.4.2 Bugs Fixed

29.4.2.1 Sample project extract from Help | Install Sample Projects

Fixed the issue where Help | Install Sample Projects does not install the sample project to the chosen
directory. The logic has been updated so that the program successfully extracts 'samples.zip' to the
specified directory.
29.4.2.2 Import from projection file in Gridded Data Import Wizard

When adding a target projection from the browse prj button in the Gridded Data Import Wizard, the string
returned from the selected prj file was simply the path to the prj file. This has been corrected so that the
contents are read from the prj file and displayed as the target well-known-text projection string.

29.4.2.3 Grid cell file validation logic

In some cases, a failure to generate structured discretization grid cells, or error 40064, would occur because
of bad grid cell file validation logic. The validation logic has been updated.
29.4.2.4 Out of memory issue when Store gridded state variable results program
option is turned on
The traditional "store gridded state variable results" program setting caused problems when attempting to
run with new Structured/Unstructured discretizations. Logic has been updated so that the program option
will only work when a traditional mod Clark grid cell file is used. The new spatial results feature in HEC-HMS
can be used to store and visualize spatial results.
29.4.2.5 Reach characteristics compute failure when reach name is null

If a reach name was null in the basin SQLite file, reach characteristics would fail to calculate for all reaches.
Logic has been updated so that the reach characteristics compute proceeds if there is a reach named null.
29.4.2.6 Subbasin can-merge failure with self-intersecting polygons

Fixed issue with subbasin merge when a delineated subbasin intersects another delineated subbasin.
Previously the can-merge logic only tested if subbasins touched. The updated logic allows a merge if the
subbasins touch or intersect. This allows a subbasin merge whenever isolated cells are left on the boundary
of the polygon after delineation.
29.4.2.7 Subbasin merge failure with self-intersecting polygons

Previously, attempts to merge self-intersecting polygons would fail. Logic has been updated to allow the
merge to proceed.
29.4.2.8 Frequency storm re-compute after parameterization change

Changes to settings in the Frequency Storm precipitation method in the meteorological model were not
being detected at simulation time, so model results would not update with the selected options or
parameters unless the user used force-compute. This was due to a switch in how controls for the
precipitation method were being handled at the subbasin level, and has been repaired.
29.4.2.9 Green & Ampt display keys in Optimization Trial compute

Added display keys for the Green & Ampt loss method in an Optimization Trial compute. Previously,
placeholder values were being used which made it unclear which parameter was selected.

29.4.2.10 Alphabetical sort in new global editor framework

Changed the alphabetical sort in the new global editor framework to be consistent with the alphabetical sort
that is used in other parts of the program.
29.4.2.11 Failure to launch from CAVI/HEC-WAT after successive launch attempts

Errors were encountered when attempting to launch the HEC-HMS user interface multiple times from CAVI or
HEC-WAT. Users can now successfully open the HEC-HMS interface repeatedly from CAVI or HEC-WAT.
29.4.2.12 CAVI/HEC-WAT Internet Maps issue

When attempting to load an internet map within CAVI or HEC-WAT, an error message was thrown indicating
that the internet map could not be displayed. This issue was due to the fact that HEC-HMS cannot currently
display internet maps and has been fixed.
29.4.2.13 Missing Coordinate Reference System (CRS) for 2D Mesh

When importing a 2D mesh from an HDF file, a CRS may or may not be available for the HDF file. If a valid
CRS is found within the HDF file, it will be used to project the coordinates of the 2D mesh. If no valid CRS is
found within the HDF file, a prompt is now shown to the user asking if they'd like to assume the basin
model's CRS when importing the 2D mesh.
29.4.2.14 Sediment transport time series write error

When simulating sediment transport over a long time span and/or using a small buffer length, errors were
encountered when attempting to write the computed results to disk. This occurred due to a missing output
unit system and has been corrected.
29.4.2.15 Basin copy with structured discretization

Fixed issue with structured and unstructured discretizations when a basin model is copied. Previously the
discretization maintained a file reference to the original basin SQLite or HDF file. Now, the reference gets
updated to the new basin SQLite or HDF file.
beta.1 15 Jan • Initial beta release

2021

beta.2 21 Jan • Added shapefile export for • Updated the PROJ library
2021 subbasin characteristics, i.e. version on Windows to fix
longest flowpath, centroidal Albers ft reprojection issue
flowpath, 10-85 flowpath, and • Fixed the sample projects
basin centroids extract logic
• Added unregulated flow compute
• Added captions in compute
progress bar
beta.3 01 Feb • Update check dialog on launch, • Out of memory error when
2021 flowpaths and centroids map preparing simulation grids for
layer added after characteristics non-mod Clark subbasins
compute
• Mesh linear reservoir interflow
option when transform is 2D
Diffusion Wave
• Persisted browse location to
buttons in gridded data import
wizard
• Identified streams polyline
export
• Subbasin characteristics pre-
compute check for sink fill raster
• Expanded version support for
HEC-RAS mesh import (users
can now import meshes created
within HEC-RAS 6.0-beta)
beta.4 11 Feb • Linear reservoir global editor • WKT read from PRJ file in
2021 support for mesh linear reservoir Gridded Data Import Wizard
interflow • Grid cell file validation logic. In
• Determinate progress bar during some cases, a failure to
gridded data import generate structured
• Export stream bin layer as vector discretization grid cells or error
file 40064 would occur because of
• Junctions snap to downstream the bad grid cell file validation
and export logic.
• Reach characteristics compute
when reach name is null. If a
reach name was null in the
reach SQLite file, reach
characteristics would fail to
calculate for all reaches. Logic
has been updated so that the
reach characteristics compute
proceeds.

beta.5 19 Feb • Added attributes exported • Fixed location of update

2021 junctions shapefile, and exported notification dialog to pop over
characteristics shapefile HEC-HMS
• Added handling for condition
where corrected DEM
elevation is equal to the no
data value of the raster
Reconditioned Terrain layer
was added to map prior to
completion of terrain
reconditioner wizard
• Fixed issue where changed
draw properties were being
reverted
• Fixed issue with merging self-
intersecting polygons
• Fixed issue with User's Manual
launch
beta.6 22 Feb • Fixed unit conversion issues

2021 when reading/writing 2D Mesh
data from/to HDF. Please
reimport your mesh using this
beta or newer to resolve any
issues.

beta.7 26 Feb • Added LA District Debris Yield • Fixed issue where the HEC-
2021 Equations 2-5 HMS user interface failed to
• Added terrain import when basin open when called from CAVI or
with linked terrain is imported HEC-WAT multiple times.
using File | Import | Basin Model Users can now successfully
• Added "Description" element to open the HEC-HMS interface
results XML file repeatedly from CAVI or HEC-
WAT.
• Fixed issue where frequency
storm was not recomputed
after parameter change
• Fixed issue where the mesh
linear-reservoir interflow
variant of linear reservoir
baseflow was initialized for a
non-2D Diffusion Wave
subbasin
• Fixed issue where extra white
space was added to a
component name when
copying. Leading and trailing
white space will now be
removed from component
name when copying.
• Fixed issue where Layered
Green & Ampt display keys
were missing in Optimization
Trial compute
beta.8 01 Mar • Fixed issue with inconsistent

2021 alphabetical sort in new global
editor framework
• Fixed issue where opening
multiple instances of CAVI or
HEC-WAT caused errors
launching HEC-HMS. Users
can now successfully launch
multiple instances of CAVI or
HEC-WAT.

beta.9 09 Mar • Fixed issue related to output

2021 control update that prevented
precipitation from being
applied to subbasins
• Fixed issue that was
encountered when connecting
and/or hydrologically sorting a
basin model that contained a
subbasin that used the 2D
Diffusion Wave transform.
beta.10 15 Mar • Fixed issue with time-series

2021 results writes. Previously some
results were not being written
to the simulation DSS file and
were not available on the
results tab after computing a
simulation.
beta.11 16 Mar • Fixed issue with structured

2021 and unstructured
discretizations when a basin
model is copied. Previously the
discretization maintained a file
reference to the original basin
SQLite or HDF file. Now, the
reference gets updated to the
new basin SQLite or HDF file.
• Fixed issue with subbasin
merge when a delineated
subbasin intersects another
delineated subbasin.
Previously the can-merge logic
only tested if subbasins
touched. The updated logic
allows a merge if the
subbasins touch or intersect.
This allows a subbasin merge
whenever isolated cells are left
on the boundary of the polygon
after delineation.

beta.12 25 Mar • When importing a 2D mesh from • When attempting to load an

2021 an HDF file, a CRS may or may internet map within CAVI or
not be available for the HDF file. HEC-WAT, an error message
If a valid CRS is found within the was thrown indicating that the
HDF file, it will be used to project internet map could not be
the coordinates of the 2D mesh. displayed. This issue was due
If no valid CRS is found within to the fact that HEC-HMS
the HDF file, a prompt is now cannot currently display
shown to the user asking if internet maps and has been
they'd like to assume the basin fixed.
model's CRS when importing the • When simulating sediment
2D mesh. transport over a long time
span and/or using a small
buffer length, errors were
encountered when attempting
to write the computed results
to disk. This occurred due to a
missing output unit system
and has been rectified.
• Fixed synchronization of
subbasin characteristics, and
subbasin characteristics
displays after changing the
basin delineation.
discretizations when a new
project was opened in an HEC-
HMS session having a basin
model of the same name as
the previous project. The
discretization cache is now
cleared when a new project is
opened.
• Fixed File | Save As issue that
prevented all project
components from being
copied into the new project.
This issue manifested itself
when importing a project from
CAVI/WAT.
29.4.4 General Acknowledgments

Many engineers, computer specialists, and student interns have contributed to the success of this project.
Each one has made valuable contributions that enhance the overall success of the program. Nevertheless,
the completion of this version of the program was overseen by Matthew Fleming while Christopher N. Dunn
was Director of the Hydrologic Engineering Center. Michael Bartles served as HEC-HMS team lead and
Thomas Brauer served as HEC-HMS lead developer during the Version 4.8 release cycle. HEC-HMS team

members include Thomas Brauer, Michael Bartles, David Ho, Gregory Karlovits, Jang (Jay) Pak, Alejandro
Sanchez, Nick Van, and Josh Willis.

Release: 15 Jan 2021
29.5.1 Features
29.5.1.1 Enhanced macOS distribution

HEC-HMS's macOS distribution now comes with all the necessary dependencies bundled. This alleviates the
need to run a script to download the necessary dependencies, which may consume a significant portion of
time. Users can now install HEC-HMS by simply downloading the .dmg installer, then drag and drop to the
Application folder.
29.5.2 Bug Fixes
29.5.2.1 Special characters in project name when generating standard report

When using the Standard/Statistics Report option, the program was not able to find simulation results files if
they contain special characters in their filenames. A fix have been implemented to resolve that issue. Since
4.6.
29.5.2.2 Notes and warnings control when called via the HMS command server
Console output for notes and warnings can be controlled in the program settings on the messages tab. This
setting was not being honored by the command server that interfaces with HEC-WAT and HEC-RTS/CWMS.
This resulted in excessively large output volume when called repeatedly from HEC-WAT. Since unknown.
29.5.2.3 Project Save As and CWMS / HEC-WAT import missing grid cell file
When using the File | Save As option, some project files were not being saved correctly. For instance, terrain
files with a *.tif extension were not saved to the new project directory. This also affected the import process
of HEC-HMS projects within the Corps Water Management System (CWMS) and HEC-WAT. This bug has
been fixed such that the File | Save As option and the HEC-HMS import process within CWMS and HEC-WAT
will now correctly write all pertinent files to the new project directory. Since v.4.7.
29.5.2.4 Grid cell file read fails when grid cell file has no extension
In previous versions of HEC-HMS, a mod Clark grid cell file could be specified as a file with no extension.
This functionality was broken in v.4.7 and has been fixed in this version. If a grid cell file has no extension it
is assumed to be a traditional ASCII grid cell file. Since v.4.7.

29.5.2.5 Grid cell file validation fails when subbasins within the grid cell file are
denoted with all caps
Grid cell file validation logic was added in v.4.7. The validation logic failed when subbasins were specified in
the ASCII grid cell file in all caps, i.e. "SUBBASINS" rather than "Subbasins". The logic has been updated to be
case-insensitive. Since v.4.7.
29.5.2.6 Characteristics compute fails when characteristic value is NaN or Infinity

In cases where the computed characteristics was of value NaN or Infinity the entire compute would fail
resulting in the indefinite progress bar spinning indefinitely or the characteristics table failing to populate
after the progress dialog closed. This has been fixed so that if the resultant characteristics value is NaN or
Infinity, that value is displayed in the table. Since v.4.7.
29.5.2.7 Met mode tree not updated after initialization

When a new meteorologic model was initialized in an HMS session, only the precipitation node was added
and updated in the watershed explorer tree. The program would have to be re-started for the tree to updated.
This has been fixed so that the tree responds to updates, such as new basin model linkages to the
meteorologic model. Since unknown.
29.5.2.8 Tool tip settings not reflected in basin map

The basin map tooltips program setting was ignored in lieu of displaying x, y coordinates in the tooltip when
hovering over the basin map. This has been updated such that the appropriate tool tip is shown based on the
selection in program settings. Currently, If None is selected the x, y coordinates will display by default. Since
v.4.4.
29.5.2.9 Spatial Results file grows with each compute

When writing spatial results to disk, the results from previous simulations were not being cleared correctly.
As such, the size of the spatial results file grew with each compute. A fix was instituted that deletes the
existing spatial results file (e.g. *.h5 file) prior to a new compute. Since v.4.7.
29.5.2.10 2D Diffusion Wave spatial results visualization wet area fraction set
incorrectly
When using the 2D Diffusion Wave transform method, the fraction of cells that contained surface water was
not being set correctly. This bug only affected the visualization of spatial results and did not affect the
actual surface water routing computations. The wet area fraction is now being set correctly when writing
spatial results using the 2D Diffusion Wave transform method. Since v.4.7.

29.5.2.11 2D Diffusion Wave discretization erroneous error message

An error message was being incorrectly thrown when using the 2D Diffusion Wave transform method with an
incompatible baseflow method. This transform method can only be used with the None, Linear Reservoir,
and/or Constant Monthly Baseflow methods. The incorrect error message led users to believe that an
incompatible discretization method was being used. This bug has been fixed and the correct error message
is now thrown. Since v.4.7.
29.5.2.12 2D Diffusion Wave computed results discrepancy

hydraulic results. However, the changes are expected to be very minor. Please see the latest HEC-RAS v6.0
release notes117 for further details. Since v.4.7.

Beta release: 25 Sep 2020
Final release: 04 Dec 2020
29.6.1 New Features
29.6.1.1 2D Diffusion Wave transform

The two-dimensional (2D) flow computational engine that was originally developed for use within HEC-RAS
has been made available for use within HEC-HMS as a transform method. This transform method explicitly
routes excess precipitation throughout a subbasin element using a combination of the continuity and
momentum equations. Unlike unit hydrograph transform methods, this new transform method can be used
to simulate the non-linear movement of water throughout a subbasin when exposed to large amounts of
excess precipitation (Minshall, 1960). Currently, only the 2D diffusion wave equations can be used within
HEC-HMS. This transform method can be combined with all Canopy, Surface, and Loss methods that are
currently within HEC-HMS. However, only the None, Linear Reservoir, and Constant Monthly Baseflow
methods can be used with this transform method. For instance, the Deficit and Constant Loss method can
be used to convert precipitation to excess precipitation, the Simple canopy method can extract infiltrated
water through evapotranspiration processes, the 2D Diffusion Wave transform method can be used to route
surface flow, and the Linear Reservoir baseflow method can be used to re-introduce infiltrated water as
baseflow at the subbasin outlet. Additionally, precipitation that does not initially infiltrate and becomes
runoff can infiltrate at a later time or within another grid cell. Spatial variables specific to 2D, such as water
surface elevation, hydraulic depth (computed as the volume of water within a cell / wetted area of the cell),
and average velocity within a cell, can be displayed within the map. In the following image, hydraulic depth is
shown throughout a subbasin that uses the 2D Diffusion Wave transform. Also, videos of hydraulic depth,
average cell velocity, and water surface elevation during a flood event are shown below.
117 https://www.hec.usace.army.mil/confluence/display/RASUM/v.6.0+Release+Notes




Within HEC-HMS, 2D Connections are used to supply boundary conditions as well as link other elements to/
from the 2D mesh. Four types of 2D Connections are available for use: Flow, Normal Depth, Rating Curve,
and Stage. For instance, if the user wanted to allow flow to leave the 2D mesh using a normal depth
assumption, a Normal Depth | 2D Connection could be used. Also, if the user wanted to apply a time series
of flow to a 2D mesh, a Flow Hydrograph | 2D Connection could be used. Users must create and link all
associated meteorologic boundary conditions (e.g. gridded precipitation, temperature, and/or snow) within
HEC-HMS.
The 2D Diffusion Wave transform can only be used with Unstructured or File-Specified Discretizations. As
was previously mentioned, an Unstructured Discretization can be created by importing a 2D mesh from an
HEC-RAS Unsteady Plan HDF file using the File | Import | HEC-RAS HDF File... option. Unsteady Plan HDF

files have extensions of ".p##.hdf" where "p##" corresponds to the specific plan of interest. Currently, users
must create a 2D mesh and any associated normal depth, flow, stage, and/or rating curve boundary
conditions within HEC-RAS (version 5.0.7 or newer) and then import to HEC-HMS. In the future, users will be
able to create and modify both 2D meshes and boundary conditions entirely within HEC-HMS. When
importing a 2D mesh from an HEC-RAS Unsteady Plan HDF file, any accompanying boundary conditions for
the selected 2D mesh (except for precipitation time series) will be imported and used to create new 2D
Connections with the same parameterization. If a File-Specified Discretization is used, the backing file must
be in an HDF 5 format and created using either HEC-RAS or HEC-HMS. Pathnames to the HDF file must be
limited to a maximum of 256 characters.
Two examples detailing the creation of simple and complex HEC-HMS projects that use the new 2D Diffusion
Wave transform can be found here: Creating a Simple 2D Flow Model within HEC-HMS118 and Creating a
Complex 2D Flow model within HEC-HMS119. For more see Selecting a Transform Method (see page 344).
The 2D Diffusion Wave transform capability was funded by the USACE Flood and Coastal R&D program. The
project was led by Michael Bartles. Initial code implementation was done by Michael Bartles, Alex Sanchez,
and Paul Ely, Contractor. Documentation was done by Michael Bartles. Testing was done by Michael Bartles
and Matthew Fleming.
29.6.1.2 Discretizations
The discretization method defines how a subbasin is discretized. Traditionally, the Mod Clark grid cell file
has been used to define the spatially-discrete elements of a subbasin. One limitation of the Mod Clark grid
cell file is that it does not use absolute spatial references. Grid cell locations are referenced from an arbitrary
lower left corner. Structured and Unstructured discretizations provide spatial-awareness to spatially-discrete
subbasin elements. Advantages of the spatially-aware approach include the ability to view discrete elements,
the ability to sample values from other geospatial data, and the ability to visualize results for discrete
elements.
There are four types of Discretization: Structured, Unstructured, File-Specified, and None.
The Structured Discretization creates a Cartesian grid within the bounds of the subbasin. The Structured
Discretization gives options for Standard Hydrologic Grid (SHG) or Universal Transverse Mercator (UTM)
projections and 50, 100, 200, 500, 1000, 2000, 5000, or 10000 meter grid cell sizes.
Unstructured Discretizations can have any coordinate reference system and the grid can be unstructured. The
backing file format for an Unstructured Discretization is an HDF5 file with identical schema to HEC-RAS, such
that files are interoperable. Unstructured grids can be imported from an HEC-RAS Unsteady Plan HDF file
(using HEC-RAS version 5.0.7 or newer). The plan file has an extension of ".p##.hdf", where "p##"
corresponds to the specific plan of interest. Unstructured grids are most commonly used with the 2D
Diffusion Wave transform method.
File-Specified Discretizations were introduced to support the traditional Mod Clark grid cell file, but also
support valid Structured Discretization and Unstructured Discretization files. When a File-Specified
Discretization is used, the path to a grid-defining file is provided by the user.
The None Discretization represents the entire subbasin as one discrete element within the larger modeling
context. This configuration is commonly referred to as a "lumped-parameter." The reality is that all
discretization approaches do some amount of spatial-averaging. The amount of spatial-averaging depends
on the extent of discrete elements, such as subbasin size or cell size.
The Punxsutawney basin model shown below uses an SHG projection with 1000 meter grid cell size for the
lower subbasin and 2000 meter grid cell size for the upper subbasins.
118 https://www.hec.usace.army.mil/confluence/display/HMSGUIDES/Creating+a+Simple+2D+Flow+Model+within+HEC-HMS
119 https://www.hec.usace.army.mil/confluence/display/HMSGUIDES/Creating+a+Complex+2D+Flow+model+within+HEC-HMS

The RedwoodCreek subbasin shown below uses an unstructured discretization.

For more, see Selecting a Discretization Method (see page 283).

The Discretizations feature was performed as a part of ongoing GIS work. Funding sources include the Flood
Control District of Maricopa County, Arizona and the CWMS National Implementation Program. Initial code
implementation and documentation were done by Thomas Brauer. Testing was done by Thomas Brauer,
Michael Bartles, and Matthew Fleming.
29.6.1.3 Basin characteristics

Subbasin and reach characteristics were added to the Parameters | Characteristics menu. To calculate
characteristics, the basin model must have spatial features (georeferenced subbasin and reach elements)
and flow direction and flow accumulation grids must be calculated. The characteristics are calculated on-
the-fly the first time a Characteristics global editor is opened. The characteristics can be re-computed by
clicking the button in the lower left of the global editor and the characteristics can be manually edited as
well. Characteristics are available as variables in the Expression Calculator. The image below shows
subbasin characteristics for the MiddleColumbia_WY1997 basin model.
For more, see Basin Characteristics (see page 267).

The basin characteristics feature was performed as a part of ongoing GIS work. Funding sources include the
Flood Control District of Maricopa County, Arizona and the CWMS National Implementation Program. Initial
code implementation and documentation were done by Thomas Brauer and Josh Willis, USACE Ft. Worth
District. Testing was done by Thomas Brauer, Josh Willis, Michael Bartles, and Matthew Fleming.
29.6.1.4 Expanded ASCII/GeoTIFF grid support

The grid management framework was updated (see page 1019) in v.4.6 to accommodate ASCII format
precipitation-frequency grids. In this release, all parameter grids were updated to accept ASCII and GeoTIFF
data sources in addition to the HEC-DSS format. The ASCII and GeoTIFF options were not added to gridsets,

or time-series of grids, like precipitation and temperature gridsets. ASCII and GeoTIFF parameter grids can
be sampled in the new Expression Calculator.
The image below shows a GeoTIFF percolation parameter grid selected in the component editor.
For more information, seethe Grid Data (see page 167) and Parameter Estimation (see page 275) sections in the
User's Manual. The expression calculator has only been implemented for a few subbasin methods.
The expanded parameter grid feature was performed as a part of ongoing GIS work. Funding sources include
the Flood Control District of Maricopa County, Arizona and the CWMS National Implementation Program.
Initial code implementation and documentation were done by Thomas Brauer. Testing was done by Thomas
Brauer, Michael Bartles, and Matthew Fleming.
29.6.1.5 GIS parameter estimation

An Expression Calculator has been added to facilitate parameter estimation from GIS data. The Expression
Calculator can be launched from select global basin editors. This release includes an initial implementation
for Deficit and Constant and Green and Ampt loss and Mod Clark, Clark, and S-Graph transform global editors.
The expression calculator requires the basin model to have spatial features (georeferenced subbasin
elements). In the Expression Calculator, grids and characteristics and can be used as variables. When a grid
is included in the expression, a zonal average value for the feature-grid combination is used in the
calculation. When a characteristic is used in the expression, the characteristic value for the feature (subbasin
element) is used in the calculation.
In the image below, a Parameter Grid has been included the expression. The program will compute the
average value per subbasin (using a zonal average GIS function) and populate the constant loss rate
parameter for all subbasins.

In the image below, the subbasin characteristics (longest flowpath, centroidal flowpath, and flowpath slope)
have been included in the expression to compute the time of concentration for each subbasin.

The Expression Calculator is launched from the Calculator... button at the bottom of a global editor.

For more, see Parameter Estimation (see page 275)

The expression calculator feature was performed as a part of ongoing GIS work. Funding sources include the
Flood Control District of Maricopa County, Arizona and the CWMS National Implementation Program. Initial
code implementation was done by Thomas Brauer and Nick Van. Documentation was done by Thomas
Brauer. Testing was done by Thomas Brauer, Michael Bartles, and Matthew Fleming.
29.6.1.6 Gridded Data Import Wizard

A new utility Gridded Data Import Wizard has been added to HEC-HMS to convert supported data formats,
e.g. NetCDF, GRIB, HDF, and ASC, to the HEC-DSS format. The utility is based on the Vortex Importer utility.
The Import Wizard can be launched from the HEC-HMS File | Import | Gridded Data menu.
For more information, see Gridded Data Import (see page 784).
The Vortex R&D project has been funded by the USACE General Investigations program. Thomas Brauer has
been principal investigator for the project. Nick Van performed the Gridded Data Importer Wizard user
interface implementation for HEC-HMS.
29.6.1.7 Spatial results visualization

A new capability to visualize computed results has been added to HEC-HMS. The following figure shows the
Spatial Results toolbar along with SWE results displayed on top of the basin model. The Spatial Results
toolbar includes options for selecting output results, an animation toolbar, buttons for controlling the
animation, and an Animation Setting button that opens an editor with options for color ramps, scale,
animation speed, and whether the animation should loop. Spatial results will only be available for simulations
that have basin models with georeferenced subbasin elements. A georeferenced basin model is one where
either the subbasins and reaches were delineated using the GIS tools, or one where subbasin elements were
georeferenced using a shapefile (Georeference Existing Elements or Import Georeferenced Elements).
Gridded spatial results cannot be visualized for subbasin elements using the ModClark file option (under the
Specified File discretization method). Instead, results will be displayed as a subbasin average value when the
*.mod file option is used. Gridded spatial results can be visualized for the structured, unstructured, and File-
Specified *.sqlite, *.HDF5, and *.HDF discretization options.

Spatial results can be displayed for both simulation runs and forecast alternatives. Spatial results must be
activated in the simulation's Component Editor, as shown below. There is an option to choose the time
interval for the spatial results. By default, the time interval is the simulation run time step; however, a larger
interval can be selected to reduce the amount of output. Spatial results are saved to an HDF5 file within the
project's "results" directory. The very first time an output result is selected in the Spatial Results toolbar, the
program will process the simulation HDF5 and build animation tiles for display. The animation can be
controlled through the animation toolbar, and the visual properties of the results can be changed as well.
For more see Viewing Spatial Results (see page 553).

The spatial results feature was funded by the the USACE Flood and Coastal R&D program. The project was
managed by Thomas Brauer. Initial code implementation was performed by Caleb Dechant, Contractor, and
Paul Ely, Contractor. Documentation was done by Matthew Fleming. Testing was done by Thomas Brauer,
Michael Bartles, and Matthew Fleming.

29.6.2 Bug Fixes
29.6.2.1 Reservoir storage is incorrect when using FT:FT2 or M:M2 elevation-area

function
This bug was incorrectly reported as fixed in v.4.4. Storage volumes and discharge were incorrect due to an
incorrect unit conversion when using FT:FT2 or M:M2 as an elevation-area function in the reservoir routing
method.
29.6.2.2 Gridded Green and Ampt: Incorrect parameterization in the component

editor
The Green and Ampt Loss Component Editor has two options for the initial soil moisture, Initial Deficit and
Initial Content. The user must select Initial Content and Saturated Content grids when the Initial Content
option is selected. The user must select an Initial Deficit grid when the Initial Deficit option is selected. There
was a bug where the program required a Saturated Content grid when the Initial Deficit option was selected.
Now, the program no longer requires the user to specify a Saturated Content grid when the Initial Deficit
option is selected.
29.6.2.3 Standard Report: Incorrect Units Displayed

In the report generated by the Standard Report option, the system of units (U.S Customary or Metric) used in
the basin model was not reflected in the "Global Results Summary" section of the report. Previously, only U.S
Customary units were used regardless of the system of units. The bug has been fixed such that data reported
is consistent with the system of units used in the basin model.
29.6.3 Beta releases

Initial beta released 25 Sep 2020
1. 09 Oct 2020 Updated spatial results: better handling for lumped vs gridded methods, default
color ramps and scales set per variable, and control over output write interval. Added indexed value
mapper for roughness grid. Added re-indexing logic for gridded precipitation on lumped subbasin
with structured discretization. Migrated linear reservoir baseflow editor to new framework. 2D flow
capabilities: added default color ramps and scales for 2D flow spatial variables (depth, MMC depth,
water surface elevation, and cell velocity), bugfixes and updates to the 2D Connection component
editor.
2. 22 Oct 2020 Features: Added met data import wizard. Added new global editor framework for
linear reservoir baseflow, Clark UH, Green & Ampt, user-specified S-graph. Added additional
characteristics/units to "stats" tab of Expression Calculator. Added ASCII/GeoTIFF option for all
static grid types. 2D bugfixes/features branch merged. Bugfixes: Force recompute meteorology if
discretization changes. Re-index grid cells when gridded precipitation is used with non-gridded
subbasin. Recompute simulation if spatial results interval changes. Avoid subsetting raster during
sampling when raster is already clipped to subbasin. Initialize Global Basin Editor and Global

Characteristics View to hydrologic order. Use the correct S-graph lag parameter when the Maricopa/
regression approach is used. Correctly adjust reservoir area provided as meters squared to thousand
meters squared. 2D bugfixes/features branch merged. 2D flow capabilities: added cumulative
outflow and stage time series, bugfixes, and updates to the 2D Connection component editor.
3. 02 Nov 2020 Added Gridded Data import option from the File | Import menu. The Gridded Data
import option was adapted from the HEC-Vortex Importer utility. 2D flow capabilities: improved
visualization of downstream connections for 2D Connections, fixed 2D spatial results bugs, and
added error checks when importing a 2D mesh from HEC-RAS. Fixed a bug where reports generated
by the Standard Report option only displayed US Customary units in 'Global Results Summary'
section.
4. 24 Nov 2020 Added Expression Calculator Precision setting to Tools | Program Settings,
Compute tab. Added handling logic for the case where a discretization geometry calculation is
attempted and there is no flow direction grid. 2D flow capabilities: fixed a bug that incorrectly
removed the downstream connection when saving a 2D mesh and improved error checking prior to a
compute. Fixed a bug within the Initial Deficit grid selection when using the Gridded Green-Ampt loss
method. Added logic to allow for more intuitive interaction with the spatial results animation tool bar.

was Director of the Hydrologic Engineering Center. Thomas Brauer led the HEC-HMS team during the Version
4.7 release cycle. HEC-HMS team members include Thomas Brauer, Michael Bartles, David Ho, Gregory
Karlovits, Jang (Jay) Pak, Alejandro Sanchez, Nick Van, and Josh Willis.

Final Release: 18 Sep 2020
29.7.1 Bug Fixes
29.7.1.1 Program hang after pre-processing drainage with multiple processors

A bug was introduced in v.4.6 that caused the GIS | Preprocess Drainage step to hang. The issue is thought to
be isolated to cases where multiple processors were used during computation; the issue was not observed in
small domain test cases. The issue has been fixed in the v.4.6.1 release so that the thread executing the
TauDEM aread8 command is closed when the process finishes. Under normal program operation, the
indefinite progress window closes and flow direction and flow accumulation rasters are created in the
<project root>/gis/<basin name> directory.

29.7.1.2 "Could not delineate elements because the break points did not intersect the
stream network" error with ESRI WKT projection
A "Could not delineate elements because the break points did not intersect the stream network" error was
erroneously given when an ESRI WKT projection was used with the input terrain data. Several entry points in
the code were updated to morph the input ESRI WKT to an OGC WKT allowing the delineation step to
proceed. The bug was found using an ESRI WKT for the Kentucky State Plane North projection. It is likely the
bug would occur with other ESRI WKT projections.
29.7.1.3 Terrain File path updated after import

An issue was found when referencing Terrain Data when the path to the original base terrain data file broke.
Logic was updated in the Terrain Data management to reference the terrain data file that is created upon
import to HEC-HMS. These files are located in the <project root>/terrain directory.
29.7.1.4 Missing data on sediment load results from USGS Long-Term debris yield
method
An issue was found when the last burn date was set to be after the simulation end date. In this case, the
USGS Long-Term method was trying to use negative number of years since last burn and the computed
sediment yield was NaN. Also, if the direct runoff event starts on the burn date, the USGS Long-Term Debris
Flow method was using zero days since the burn and the calculated sediment yield was zero. The issue has
been fixed in the v.4.6.1 release so that (1) if the last burn date is after the simulation end date, an error
message is generated, (2) if the last burn date is after an erosion event date, the debris yield will be set to
zero and (3) if direct runoff starts on the same day as the burn date, the number of days since the burn date
is set to 1.
29.7.1.5 Statistics Report Generator - Terminates for Datasets with Elements That
Did Not Have Results
An issue was found when attempting to generate a statistics report if a source was used in the basin model.
Sources do not have results causing the report generation to fail. New handling logic was added for this case
allowing report generation to proceed.
29.7.1.6 Standard Report Generator - Overlapping X-Axis (Time) in Several Plots

An issue was found where plots had two axes resulting in overlapping time strings. An example is shown
below.

The second axis has been removed so that time strings do not overlap.
29.7.1.7 Standard Report Generator - Incorrectly Display Time Series Plots with
Missing Data for Certain Dates
An issue was found in plots that had missing results for several dates. The missing results were filled with a
non-NaN negative value. This caused the plots to look as shown in the image below:
To resolve this issue, the missing results were refilled with NaN values, so that the plotting library would
ignore those values. This solution mirrors the plots produced in HEC-HMS. Below is an example of a plot
after changes have been made.


Beta release: 19 Jun 2020
Final release: 28 Aug 2020
29.8.1 New Features
29.8.1.1 ASCII precipitation-frequency grid

A new precipitation-frequency parameter grid type was added to support the new precipitation-frequency grid
option in the hypothetical storm. The program's grid management framework was generalized to support
alternative file formats to the traditional HEC-DSS format. The initial implementation allows for an ASCII
formatted, precipitation-frequency grid, which is the format distributed in NOAA Atlas 14. The
grid Component Editor allows the user to select data units and a multiplication factor that represents the
multiplication factor that is applied to persisted data. For example, precipitation-frequency data is commonly
distributed in terms of 1/1,000 (NOAA Atlas 14) inches or 1/100,000 inches (NOAA Atlas 2). It is anticipated
that the revised grid management framework will be used to accommodate other raster formats, such as
GeoTIFF, in the future.
The ASCII precipitation-frequency grid was funded through an agreement with the Flood Control District of
Maricopa County, Arizona. The initial code implementation was done by Thomas Brauer with testing by
Gregory Karlovits and Thomas Brauer.
For more information see Grid Data (see page 167).
NOAA Atlas 14 precipitation-frequency grid referenced in the Grid Data component editor:

29.8.1.2 Precipitation-frequency grid option in hypothetical storm

In addition to specifying a single point depth value to be reduced to a watershed average, the hypothetical
storm now allows specification of precipitation-frequency parameter grid. When the precipitation-frequency
grid option is used within the Hypothetical Storm precipitation method, the program will extract the average
value from the precipitation-frequency grid (using a zonal statistics computation). This area-average point
precipitation depth will be reduced using the selected area reduction method, along with the drainage area
above the computation point (the storm area is assumed to equal the drainage area). The option to use a
precipitation-frequency grid will only work with basin models that have GIS elements for the subbasin
elements.
The precipitation-frequency grid option in the hypothetical storm was funded through an agreement with the
Flood Control District of Maricopa County, Arizona. The initial code implementation was done by Thomas
Brauer and Gregory Karlovits.
For more information see Precipitation (see page 458).
Precipitation-frequency grid option in the Hypothetical Storm editor panel:
29.8.1.3 Depth-area analysis with precipitation-frequency grid hypothetical storm

The Hypothetical Storm meteorologic model can now be used in conjunction with the Depth-Area Analysis
simulation type so that several analysis points can be specified. When a precipitation-frequency grid is used
within the Hypothetical Storm, the Depth-Area Analysis will automatically compute 1) the corresponding
area-average point precipitation-frequency value for the drainage area above the analysis point using the
precipitation-frequency grid, and 2) the area reduction factor associated with the analysis point by computing
the drainage area above the point, and setting it equal to the storm area for the area reduction factor lookup.
The depth-area analysis with precipitation-frequency grid in the hypothetical storm was funded through an
agreement with the Flood Control District of Maricopa County, Arizona. The initial code implementation was
done by Gregory Karlovits.

For more information see Applying Depth-Area Analysis to Precipitation-Frequency Grids120.

Depth-area-analysis results from precipitation-frequency grid hypothetical storm:
29.8.1.4 Gumbel Distribution in Uncertainty Analysis

The Gumbel distribution121 was added to the list of probability distributions that are available for random
sampling in the Uncertainty Analysis.
The initial code implementation was done by Gregory Karlovits.
Example of the Gumbel distribution sampling point precipitation depth for the Hypothetical Storm:
29.8.1.5 Standard Reports

An HTML report generator has been added to the HEC-HMS Tools | Reports menu. The Standard Report
option allows the user to create an HTML report with global parameter summary tables, a global results
120 https://www.hec.usace.army.mil/confluence/display/HMSGUIDES/Applying+Depth-Area+Analysis+to+Precipitation-Frequency+Grids
121 https://en.wikipedia.org/wiki/Gumbel_distribution

summary table, element parameter summary tables and result graphs for each basin element. Users are able
to customize the report using check box selections in the user interface.
The standard reports feature was funded through an agreement with the Flood Control District of Maricopa
County, Arizona. The initial code implementation was done by Nick Van and Thomas Brauer.
For more information see Reports (see page 807).
Subbasin results content in the standard HTML report:
29.8.1.6 Global Monthly Average Evapotranspiration Editor

A global editor was added for the monthly-average evapotranspiration method. Previously, 12 monthly-
average evaporation rates and 12 pan coefficients had to be entered for each subbasin. With the global
editor, users can now enter the values once for all subbasins using tabular-fill options to assist in the
process.
This feature was funded through the USACE technical engineering support account and through the CWMS
National Implementation Program. The initial code implementation was done by Thomas Brauer.
For more information see Program Screen (see page 68).
Monthly-average evapotranspiration global editor:

29.8.1.7 macOS Portable Distribution

A macOS portable distribution was added, in addition to our Windows and Linux distributions. See the
Installation (see page 61) section of the User's Manual for instructions on installing and running on macOS.
macOS user interface:
29.8.1.8 Beta Releases
1. 23 Jun 2020 Initial beta release.

2. 24 Jun 2020 Fixed an issue where log messages were not being flushed to the project log file.
Previously, the project log file was often empty because log messages were not being flushed. Now
the project log file should have content similar to the message log in the user interface.
3. 25 Jun 2020 Updated GDAL library version to 2.4. It is anticipated this this will help with GDAL
library load issues.

4. 30 Jun 2020 Fixed an issue where where only the lower half of icon-style reaches were being
displayed. This issue was related to library updates and refactoring done in the previous beta release.
5. 01 Jul 2020 Updated standard reports logic to accommodate all simulation types. Fixed bug
where some debris-yield results were being written as NaN rather than 0.
6. 08 Jul 2020 Updated standard report format.
7. 17 Jul 2020 Fixed an issue where TauDEM binaries were compiled as "Debug" and failed at
runtime if Visual C++ debug dependencies were not found. The TauDEM binaries distributed with
HEC-HMS were updated to "Release." Updated GDAL binaries to a newer release of v.2.4.4. Fixed an
issue in the previous beta release that prevented the statistics report from generating. Generalized
some parts of the code in preparation for a macOS X release.
8. 23 Jul 2020 Added global monthly-average evapotranspiration editor.
9. 03 Aug 2020 Updated standard report format.
10. 08 Aug 2020 Added protections for raster file types without coordinate reference system.
Removed zoom limit when zooming in with mouse wheel.
11. 10 Aug 2020 Fixed issue in case of subbasin computation point in precip-frequency grid
hypothetical storm. Previously the subbasin was not being included in upstream elements.
12. 10 Aug 2020 Fixed issue of null projection in gridded precipitation frequency storm computer.
13. 21 Aug 2020 Fixed minor error checking and UI interaction issues with precip-frequency grid
hypothetical storm. Added DSS precipitation-frequency grid support. Added Gumbel distribution to

Karlovits, Jang (Jay) Pak, Alejandro Sanchez, and Nick Van.

Beta release: 15 May 2020
Final release: 23 Jun 2020

29.9.1 New Features
29.9.1.1 Global temperature-index snow editors

Global temperature-index snow editors were added to facilitate rapid calibration of large temperature-index
snow models. Global editors can be accessed from the Parameters | Snowmelt menu, whenever a
meteorologic model with temperature-index snowmelt is selected in the Watershed Explorer. A filter was
added to the global editor to allow users to quickly filter elements by computation point or zone.
The global temperature-index snow editors were funded by the Corps Water Management System (CWMS)
National Implementation Program. The initial code implementation was done by Thomas Brauer with testing
by Matthew Fleming, Michael Bartles, and Gregory Karlovits.
29.9.1.2 Time-variable wet-meltrate

Capability was added to model the temperature-index wet-meltrate parameter as variable in time. This
capability supports dam safety studies that might want to adjust the wet-meltrate during highly dynamic
storms. This capability also allows the the wet-meltrate parameter to change seasonally.
The time-variable wet meltrate was funded through an agreement with California Department of Water
Resources (DWR), Division of Safety of Dams (DSOD). The initial code implementation was done by Thomas
Brauer with testing by Matthew Fleming and Thomas Brauer.
29.9.1.3 Debris yield methods

It is now possible to evaluate debris yield/flow under post-wildfire situations within the watershed. Subbasin
elements have three debris yield methods based on precipitation, topography, and soil burn severity
information for event and continuous simulation. Reach and reservoir elements are being further developed
for debris/hyper-concentration flow routing analysis.
Meanwhile existing sediment features (reach and reservoir elements) can be used to evaluate debris flow
effects throughout the watershed with certain limitations. The results of the analysis can also be used
upstream as inflow boundary conditions to non-Newtonian numerical modeling capabilities within HEC-RAS
in order to evaluate complex debris/mud flow problems.
The debris yield methods were funded by the USACE Arid Regions work unit within the Flood and Coastal
Systems Research and Development program. The initial code implementation was done by Jay Pak and
Paul Ely with testing by Jay Pak.
29.9.1.4 Number of cores user interface selection

A number of cores selection was added to the user interface in Tools | Program Settings, Defaults tab. This
selection allows users to adjust the number of cores used in native processes, which is currently limited to
the GIS raster and delineation processes. Increasing the number of cores should result in better
performance for Preprocess Sinks, Preprocess Drainage, Identify Streams, and Delineate Elements menu
items. It is anticipated that this setting will be used to control the default number of cores for other native
processes in the future. Note: there are many instances in the code where parallelization is handled by Java

based on the resources available to the Java Runtime Environment; The default number of cores setting will
have no effect in this situation.
29.9.1.5 Java 11
For v.4.5, HEC-HMS was migrated from Java 8 to Java 11. Java 11 has shown much better performance on
highly-scaled and high-resolution displays. A previous known issue guided users through overriding the DPI
scaling behavior when attempting to use HEC-HMS on a highly-scaled display. Java 11 should help eliminate
the need to make any scaling adjustments.
29.9.2 Bug Fixes
29.9.2.1 Error 14703: No data source is specified for unit hydrograph when
attempting to use a user-specified unit hydrograph
An issue was found in the DSS Pathname validation logic for the unit hydrograph paired data curve. This
caused a No data source is specified for unit hydrograph error during the pre-run validation check, even
though valid DSS file and pathname were provided. The validation was updated to correct the false negative.
29.9.2.2 Unit hydrograph interval and duration are not saved in the Paired
Data editor
An issue was found where the unit hydrograph interval and duration were overridden by defaults in the Paired
Data editor upon save. This issue was corrected so that the interval and duration can be updated by the user,
and the updates are persisted during save.
29.9.2.3 Failed copy + paste in the unit hydrograph Paired Data editor
An issue was found where attempting to copy + paste in the unit hydrograph paired data editor failed. The
issue was traced back to the underlying write logic for storing time patterns. The time pattern write logic was
updated fixing the copy + paste functionality.
29.9.2.4 Missing or reduced-area mod Clark grid cells when generating a grid cell
file with target projection differing from the basin model coordinate
referencing system
An issue was observed during testing where some mod Clark grid cells were missing or reduced in area
when the target projection was different from the basin model coordinate referencing system, and the
projected grids were highly-oblique, e.g. UTM 17N basin model coordinate system to Standard Hydrologic
Grid (SHG) target projection. The missing or reduced-area cells were limited to a subset of the perimeter
cells. Interior grid cells and most perimeter grid cells were unaffected. There was no issue when the basin
model coordinate system and target coordinate system were the same, or, the same but used different linear
units, e.g. SHG Feet vs SHG Meters. The grid cell file creation logic was updated to use a vector-geometry-
based intersection which eliminates the issue. The vector geometry approach may take slightly more
processing time than the previous raster-based approach.


Karlovits, Jang (Jay) Pak and Alejandro Sanchez.

Final release: 15 May 2020
29.10.1 New Features
29.10.1.1 No data handling during grid accumulations

An issue was discovered when using gridded precipitation at a 1-hour time step while the simulation was set
to use a 3-hour time step. Ideally, the hourly precipitation grids would be accumulated over the three hour
time step for this scenario. However, it was discovered that a precipitation value of 0 inches was used for the
3-hour time step if any of the 1-hour precipitation grid cells had missing data. Capability was added when the
program processes the precipitation grids and accumulates them to treat missing values as defined in the
meteorologic model. Options include abort compute or assume a value of 0 inches or mm when missing
data is encountered. With this added capability, the program will accumulate all valid values when the user
chooses to use a value of 0 inches or mm when missing data is encountered. Functionality was added to
pass the Replace Missing: Set to Default status from meteorologic model to the grid accumulation logic. This
allows grid accumulations to assume 0 where when one of the accumulation grids has a value of NaN.
29.10.1.2 Coordinates tool tip added to the basin map

The coordinates tool tip was removed in v.4.4 in order to display raster information for delineation. For
example, if the user selects a raster map layer, like elevation, the tool tip will show the elevation value of the
raster. The coordinates tool tip has been added back into v.4.4.1 for the case when a raster map layer is not
selected.
29.10.1.3 Install dependencies shell script added to Linux build

A shell script was added to the Linux build to install dependencies on Ubuntu 18.04.4 LTS.

29.10.2 Bug Fixes
29.10.2.1 Cumulative time series results reset to zero at forecast time

When displaying cumulative time series (e.g. cumulative precipitation, LWASS, loss, etc) that were computed
using a forecast alternative, the results were being "reset" to a value at or near zero at the forecast time. This
bug was introduced in v4.2. Cumulative time series will no longer reset at the forecast time and will display
as expected.
29.10.2.2 Paste from the clipboard fails in some tabular editors

Attempting to copy/paste multiple rows of data into the global editor for Muskingum-Cunge channel routing
caused one row to be deleted from the table with no clipboard data successfully pasted. The issue was
traced back to the paste-from-clipboard logic that is used by all global editors. A fix was implemented and
tested in the Muskingum-Cunge channel routing global editor. This fix could have implications for all tabular
editors in the program. It is unknown when this bug was introduced.
29.10.2.3 Compute to point is not forced when control button is pressed

HEC-HMS includes an option to compute elements in a basin model to a user selected computation point.
This functionality was added to reduce simulation run times when calibrating a model. The program has
included an option to force the re-compute of all elements when holding down the Control key when pressing
the compute button. It was found that forcing a simulation to re-compute the elements was not happening
when computing to a computation point. New minor capability was added so that forcing a compute to a
computation point now works.
29.10.2.4 Name text field is collapsed in Create New Project dialog

On some displays, in the Create New Project dialog, the text field corresponding to Name is collapsed
horizontally to the point it is difficult or impossible to enter text. This issue was reproduced on a system with
4K monitors and 150% scaling on display. A fix was made to horizontally grow the text field based on the
size of it's parent container.
29.10.2.5 Recent projects list grows unbounded after opening projects repeatedly
in the same HEC-HMS instance
A user-interface bug was introduced in v.4.4 where repeated recent project selections from the File menu, in
the same HEC-HMS instance, caused the recent projects list to grow, duplicating the recent projects with
each selection. A fix was implemented to prevent duplication of recent projects in the File menu.
29.10.2.6 Flow ratio applied to source is not observed

A computational bug was introduced in v.4.3 where a flow ratio applied to a source element was not
observed by the computation engine. Versions affected include v.4.3 and v.4.4. A fix has been implemented

in v.4.4.1. This could cause a change in results for projects that were created or run in v.4.3 or v.4.4 and
apply a flow ratio to a source element.
29.10.2.7 MUSLE is not valid to grid cell

The following error message was observed when "ModClark" transform method which represents the
subbasin as a collection of grid cell run with "MUSLE" erosion method: ERROR: "MUSLE" is not valid for grid
cells. This issue was resolved by automatically setting to NONE for cell erosion method inside code when a
lumped erosion method such as MUSLE is specified for a gridded subbasin. This issue was introduced in
v.4.4.
29.10.2.8 Sediment results discrepancy for reservoirs

There are two errors are related in sediment results discrepancy for reservoirs. The first error is in the
calculation of fall velocity in v.4.2 Temperature in degrees Cesius is converted to degrees Fahrenheit for the
fall velocity calculation. This conversion is degF = 9 / 5 * degC + 32, but 9/5 is evaluated using integer
arithmetic, so the formula becomes degF = 1 * degC + 32. This error has been corrected in HMS v4.4. the
second error is that the minimum grain size for clay was increased from 0.00024 to 0.002 mm because
smaller clay particles flocculate into clumps. This change in the minimum grain size means that the mean
grain size in increased, and the fall velocity is also increased. It is unknown when this bug was introduced.
29.10.2.9 MPI Error when running terrain processing tasks from GIS menu
The following MPI error was observed when attempting to run terrain processing tasks from the GIS
menu: ERROR: Failed to post close command error 1726 & ERROR: unable to tear down the job tree. exiting.
This issue was observed in the case that the user had an alternative MPI installation on their machine and
the Windows library load sequence found an alternative version of smpd.exe. This issue was resolved by
moving the MPI libraries into the same directory as the TauDEM executables. This issue was introduced in
v.4.4.
29.10.2.10 Component Editor freezes when changing element connections

A Component Editor freeze was observed when deleting a downstream connection and attempting to re-
connect elements. This issue was traced back to an unhandled exception in the code that manages element
order in the Watershed Explorer (element tree). A fix was implemented to allow proper re-sorting of elements
and avoid the component editor freeze. It is unknown when this bug was introduced.
29.10.2.11 Unable to select Linear Reservoir baseflow parameters in Forecast

Slider Adjustments editor
Users were previously unable to select linear reservoir baseflow parameters within the Forecast Slider
Adjustments editor. It is unknown when this bug was introduced. This issue was rectified such that linear
reservoir baseflow parameters can now be used within forecast slider calibration aids.


Version 4.3 of the Hydrologic Modeling System (HEC-HMS) was completed in November 2018 and released
for general use shortly thereafter. A number of new capabilities have been under development since 2018.
The most significant addition to the program is the new GIS toolkit for subbasin and reach delineation. The
new delineation tools process terrain information, digital elevation models, and allow the modeler to
customize subbasin and reach outlets while preserving the element connectivity. The HEC-HMS team is
migrating similar functionality from HEC-GeoHMS directly into HEC-HMS. The team believes the GIS tools
will improve the workflow for creating new projects while also improving long term code maintenance. HEC-
HMS version 4.4 includes delineation options, future releases will include options for computing physical
characteristics of subbasins and reaches and tools for estimating model parameters from common GIS data
sets. This release also contains new hydrologic process simulation options and improvements to existing
options. The new Layered Green and Ampt loss method can be used for continuous simulation. The linear
reservoir baseflow option was enhanced and now provides an additional groundwater layer and options for
specifying the distribution of infiltrated water between the groundwater layers. HEC-HMS version 4.4 allows
modelers to define snowmelt parameters for each subbasin element and new evapotranspiration options.
Finally, HEC-HMS version 4.4 contains improvements to the simulation framework that should translate into
noticeable reductions in the simulation run time. A list of new options are described later in this document.
Users have reported some difficulties with several features. The development team has also continued
careful and systematic testing of the program. The results of that testing in combination with reports from
users have allowed the identification and repair of various problems. Some of these problems affected
simulation results and are described in detail later in this document.
The combination of new capabilities and error corrections is this Version 4.4 release. It is currently available
for the Microsoft Windows® operating system and the Linux® operating system.
The HEC-HMS program has been designed to be easy to use. However, an understanding of how the
program works is critical to producing accurate results. It is suggested that a new user read the HMS Quick
Start Guide (see page 1030) (Version 4.4 March 2020). The guide briefly describes the basic features of the
program in enough detail to begin using it. The guide also includes a step-by-step tutorial.
29.11.1 Installation
The installation package and all documentation are available on the HEC website at https://
www.hec.usace.army.mil/software/hec-hms/downloads.aspx. This new release is installed independently
of any previous versions of the program so you will need to uninstall the previous versions if you do not wish
to use them anymore. However, you may keep different versions of the program installed for parallel use or
testing if you choose. This new version will automatically open projects developed with any previous version
of the program. However, once a project has been opened in Version 4.4, it will not be possible to open it
with older versions of the program.
29.11.2 New Capabilities
29.11.2.1 GIS Delineation Tools

Basic watershed delineation tools are now provided, which allow the user to create a basin model from a
digital elevation model. After assigning a terrain data component to a basin model, the user can apply tools
to remove sinks, compute flow direction and accumulation, identify streams by drainage area, define break

points, and finally, delineate a watershed. Once the watershed has been delineated, the user also has tools to
merge and split sub-basin and reach elements. For more, see GIS Delineation Tools (see page 245).
29.11.2.2 Layered Green and Ampt Loss Method

A Green and Ampt option has been available in HEC-HMS for computing precipitation losses. An additional
layered Green and Ampt loss method was added in v4.4. This method uses two soil layers to account for
continuous changes in moisture content and is based upon algorithms originally developed for the Guelph
Agricultural Watershed Storm-Event Runoff (GAWSER) model. Using the layered Green Ampt method allows
for continuous simulation when used in conjunction with a canopy method that will extract water from the
soil in response to potential evapotranspiration computed in the meteorologic model. For more, see Layered
Green and Ampt Loss Method (see page 322).
29.11.2.3 Gridded Hamon Evapotranspiration Method

A gridded implementation of Hamon evapotranspiration was added in v.4.4. This adds spatial complexity to
the subbasin-average Hamon evapotranspiration method that was added in v.4.3. The method uses average
daily temperature data combined with latitude and longitude to compute evapotranspiration according to the
methodology of Hamon, 1963, Eq. 2. The Hamon coefficient is set to a default value of 0.0065 and can be
adjusted by the user. If the simulation time interval is sub-daily the daily evapotranspiration amount is
distributed between sunrise and sunset according to a sinusoidal pattern. For more, see Gridded Hamon
Evapotranspiration Method (see page 509).
29.11.2.4 Gridded Hargreaves Evapotranspiration Method

A gridded implementation of Hargreaves evapotranspiration was added in v.4.4. This adds spatial complexity
to the subbasin-average Hargreaves evapotranspiration method that was added in v.4.3. The method uses
average daily temperature data combined with solar radiation to compute evapotranspiration according to
the methodology of Hargreaves and Samani, 1985, Eq. 1. The coefficient is set to a default value of 0.0135
and can be adjusted by the user. When the Hargreaves evapotranspiration method is combined with the
Hargreaves radiation method the evapotranspiration calculation takes the form of Hargreaves and Samani,
1985, Eq. 8. The user can control the coefficient through the Hargreaves shortwave and evapotranspiration
methods. For more, see Gridded Hargreaves Evapotranspiration Method (see page 509).
29.11.2.5 Green and Ampt Loss Method

Two methods for specifying the initial soil moisture state at the beginning of a simulation have been added
to v4.4: Initial Content and Initial Deficit. The initial content was the only option available in v4.3. The Initial
Content method allows the user to specify the initial soil moisture state in terms of a moisture content.
Conversely, the Initial Deficit method allows the user to specify the initial soil moisture state in terms of a
deficit. For more, see Green and Ampt Loss Method (see page 322).
29.11.2.6 Linear Reservoir Baseflow Method

Enhancements were made to the linear reservoir baseflow method for v4.4. The user can now control the
number of layers from 1 to 3. Prior to v4.4, up to two layers were available. The other enhancement is the
ability to assignable a fraction of infiltrated water to each of the linear reservoir layers. The assigned
fractions of infiltrated water do not have to add up to one, and the sum cannot be larger than one. When the

sum is less than one, the model is simulating a portion of the infiltrated water going to a deep aquifer and not
contributing to runoff. For more, see Linear Reservoir Baseflow Method (see page 368).
29.11.2.7 Clark Transform Maricopa County AZ Method

The Clark unit hydrograph method now contains a Maricopa County AZ USA option. The Maricopa County
option uses physical characteristics of the watershed and precipitation intensity to compute the time of
concentration and the storage coefficient. The user must enter the length of the hydraulically longest flow
path, the watercourse slope of the longest flow path, and a resistance coefficient. The program will
automatically compute the time of concentration and storage coefficient using the physical characteristics
and equations defined in the Maricopa County Drainage Design Manual. A copy of the Hydrology chapter in
the Maricopa County Drainage Design Manual can be opened from the following website, https://
www.maricopa.gov/546/Engineering-Tools. For more, see Clark Transform Maricopa County AZ Method (see
page 344).
29.11.2.8 Compute to Point Expansion

When elements are designated as Computation Points, additional computation options become available.
One of these options is Compute To Point, which only computes the hydrologic element designated as a
computation point plus any elements upstream of the point. This computation option allows users to more
quickly perform simulations, evaluate chosen modeling processes, and calibrate model parameters, which is
especially useful when forecasting during times of flooding. While users can still access the Compute To
Point feature by right-clicking on a computation point in the Basin Model Map and selecting Compute To
Point, additional means by which users can access this feature have been made available within v4.4. For
instance, within the Zone Parameter editors, a Computation Point can be selected and all hydrologic
elements upstream can be computed. This new feature is also available within all global parameter editors
and forecast initialization editors. For more, see Compute to Point Expansion (see page 638).
29.11.2.9 Melt Rate Options for Temperature Index Snow Method

In past versions, the antecedent temperature index - meltrate (ATI-meltrate) parameter was specified as a
paired data function. Two new ATI-meltrate options were added: ATI-meltrate can now be specified as a
constant value or a time-variable pattern. To use a constant value, Constant Value should be used for the
temperature-index snowmelt dry melt method. To use a time-variable pattern, Annual Pattern should be used
for temperature-index snowmlet dry melt method. The time-variable pattern is entered as a Parameter Value
Pattern paired data. For more, see Melt Rate Options for Temperature Index Snow Method (see page 293).
29.11.2.10 Subbasin Level Temperature Index Parameterization

In past versions, temperature-index snowmelt was parameterized with a single set of parameters for the
entire basin. Now, temperature index parameters (i.e. PX temperature, base temperature, wet meltrate, ATI-
meltrate function, etc) are specified for each subbasin. This gives the modeler greater control for situations
where parameters might vary throughout the modeling domain. For pre-v.4.4 projects, opened in v.4.4, basin
parameters will be applied to all subbasins in the basin model. For more, see Subbasin Level Temperature
Index Parameterization (see page 293).

29.11.2.11 Hypothetical Storm Enhancements

New temporal pattern options were added to the hypothetical storm precipitation method. In addition to the
standard 24-hour SCS temporal patterns, the user can select a user-defined temporal pattern or define a
series of temporal patterns for increasing storm areas. The user defined temporal pattern is entered as a
percentage curve in the Paired Data Manager. The independent variable is percent of the total storm duration
(values should be 0 to 100 percent) and the dependent value is percent of the point depth (which is
automatically reduced based on the area-reduction information and storm area). The area-dependent
temporal pattern option is designed to work in conjunction with the Depth-Area analysis compute option.
When the area-dependent pattern option is selected, the user must define a number of storm temporal
patterns for different storm areas. HEC-HMS interpolates between the temporal patterns using the user
defined storm area, or the area for an analysis point in the Depth-Area analysis. The hypothetical storm
precipitation method can now function within the depth-area analysis simulation. The drainage area at each
analysis point is used to update the temporal pattern (if it is a function of area) and/or the precipitation depth
(if the TP40 or user-specified area-reduction options are chosen). For more, see Hypothetical Storm
Enhancements (see page 458).
29.11.2.12 Terrain Data

A new shared data element for defining terrain data has been created. The terrain data component stores a
single, continuous digital elevation model (DEM) and its vertical units, and can be linked to one or many basin
models to be used for watershed delineation. When linked to a basin model, the elevation data will be
displayed as a raster in the basin map window. For more, see Terrain Data (see page 180).
29.11.2.13 Color Ramp and Scale Editor

Enhanced tools for visualizing raster data in the basin map have been created

• Raster visualization is controlled by a combination of a color ramp, which defines the colors that
values in the raster are mapped to, and a color scale, which determines how values in the raster are
mapped.
• A number of default color ramps and color scale schemes are provided. Users cannot modify existing
ones but can copy them, or create entirely new ones.
• Color scales are defined as relative (0 - 1 scale representing a fraction) or absolute (predefined
values.) They may also be discrete (same color for a range of values) or stretched (interpolated.)
Absolute scales may have units.
• Users can change transparency, invert the color ramp and apply hillshading as toggled options.
• Colors used to identify out of range (above or below the scale) or values that are invalid can be set by
the user.
• Users can interact with the full color scale by setting the "thumbs", which are reference points that
define how the color ramp, or the scale, change throughout the range of the raster values.
• Users can add, delete, and equally distribute thumbs. For color ramp thumbs, users can set the color.
For color scale thumbs, users can set the scale value.
For more, see Color Ramp and Scale Editor (see page 199).
29.11.3 Enhancements and Revisions

Occasionally it becomes necessary to revise how an existing feature operates in order to create more
capability or correct a problem. Several changes of this nature have occurred since the last software
release. A complete description of each enhancement or revision is given below. In general, revisions result
in changes in the computed results when compared to previous program versions.

29.11.3.1 Basin Map Mouse Controls

The Arrow, Pan and Zoom tools have been removed from the Components toolbar. Instead of box-selection
being the default behavior of the click-and-drag action in the basin map, the behavior is now to pan instead.
The mouse scroll wheel still controls the zoom, but now the "+" and "-" controls also increase and decrease
the zoom level, respectively.
29.11.3.2 Sediment Channel Routing Computations with Index Flow/Celerity

Any reach element that uses Muskingum-Cunge or kinematic wave routing will need to carefully identify
either the index flow or index celerity parameters when sediment transport is being modeled. The computed
flow has been found to not be sensitive to the index flow and celerity parameters, but sediment transport has
been found to be sensitive to the index flow and celerity parameters. As described in the User's Manual, the
index flow and celerity parameters are used to subdivide the reach element into a number of equal length
segments (dx). The volume ratio and linear reservoir sediment routing methods are very sensitive to the
number of reach segments; therefore, care will need to be taken when defining the index flow or celerity and
the model will need to be calibrated. For more, see Sediment Channel Routing Computations with Index
Flow (see page 743)/Celerity (see page 743).
29.11.3.3 Parallelization of Sub-basin and Reach Network Computation

Simulation performance has been increased through parallelization of the sub-basin and reach network
computations. Performance gains are larger in more dendritic models, and the gain drops off as the number
of diversions and auxiliary flows increases. Improvements of up to 50% in simulation time have been
demonstrated, and models with more elements have shown the greatest increases.
Name Type Area Dur Compute Time

(sq mi) atio
n of
v4.3 v4.4 Compu
Sim
te
ulati
Time
on
Reduct
(day
ion (%)
s)
Garrison Dam Dam Safety 123,659 121 23 min 2 sec 19 min 11 sec 16.7
Delaware River Forecasting 13,635 31 43 sec 33 sec 23.3
Upper Forecasting 4,938 20 25 sec 13 sec 48.0

Susquehanna River
Potomac River Forecasting 11,898 30 27 sec 14 sec 48.1

Upper Snake River Planning 35,872 365 17 min 31 sec 17 min 18 sec 1.2
Lower Snake River Planning 38,231 365 9 min 5 sec 5 min 31 sec 39.3
Middle Columbia Planning 25,830 365 4 min 25 sec 2 min 53 sec 34.7
River
Willamette River Planning 11,464 365 2 min 59 sec 1 min 44 sec 41.9
29.11.3.4 Control of Messages

Users can now choose to suppress notes and warnings (but never errors) in the program console and the log
file through the Messages tab of the Program Settings menu.
29.11.4 Problems Repaired

Several errors were found in the program and repaired. Complete descriptions of each error are given below.
29.11.4.1 Summary Information for Total Diverted Flow was Not Correct
Diversion volumes were being reported incorrectly for diversion elements due to a bug related to checking
unit systems. This problem has been repaired.
29.11.4.2 Unrecognized Changes in Objective Function

Changing some properties of an Optimization Trial objective function were not marking the optimization as
needing to be recomputed. This problem has been repaired.
29.11.4.3 Missing Inflow to a Diversion

Error checking was added to prevent diversion elements from attempting to divert flow with missing data
when missing values are not allowed in the basin model.
29.11.4.4 Renaming Junctions Adds Element to List of Subbasin Zone Elements

When junctions were renamed, the junction element was added to the list of subbasins in all zones, which
should not include junction elements. This problem has been repaired.

29.11.4.5 Blending Allowed Missing Percentage

Entered values for Allowed Missing were disappearing when the Apply button was being clicked in the
combined parameter editor. This problem has been repaired.
29.11.4.6 Report Drainage Area Precision

Drainage areas in simulation run reports were being reported to two decimal places regardless of how it was
set in the basin model. It has been modified to use the same precision for output as it received for the input.
29.11.4.7 Optimization of Manning's n Value

Attempting to optimize a reach element with the Muskingum-Cunge routing method allows the user to select
Manning's n value as a ratio to the start value. When attempting to actually run the trial, an
IllegalArgumentException was being thrown. This problem has been repaired.
29.11.4.8 Reservoir Storage Is Incorrect When Using FT:FT2 Elevation-Area

Function
A bug related to checking the units for elevation-area table data was repaired so that FT:FT2 units will now
compute correctly.
29.11.4.9 Un-editable Text Boxes

A bug that made a text field unresponsive to anything except deleting default text the first time a text field
was encountered in a new project was repaired.
29.11.4.10 Out-of-Memory Error from Opening and Closing the Basin Map
A memory leak related to the basin map window was repaired. Changing or closing and opening a large
number basin maps could previously result in an OutOfMemory error.
29.11.4.11 Renaming Control Specifications

The right-click option to rename control specifications would fail to rename the control specification, instead
taking on a default value. This problem has been repaired.
29.11.4.12 Saving Kinematic Wave Transform Parameters

In some situations, Kinematic Wave Transform parameters were not being saved to the basin model from
the global editor. Both the global and component editors now save changes to the parameters.

29.11.4.13 Forecast Blending when Observed Data Is Missing

Previously, when a forecast alternative was computed and 1) missing data was encountered at the start of
the simulation for the junction(s) in question and 2) no allowed missing percentage (or an allowed missing
percentage greater than 50%) was specified within the blending editor, no blending was actually performed.
Blending will now occur if missing data is encountered at the start of the simulation but the amount of
observed data is still less than or equal to the specified allowed missing percentage.
29.11.4.14 NegativeArraySizeException in Kinematic Wave Channel Routing

A warning message was added when the free water surface assumption is violated in a circular cross
section in the Kinematic Wave routing method, instead of halting the simulation with an exception.
29.11.4.15 Error 10000 when Adding New Precipitation Gage

A bug was fixed where an Error 10000 was thrown when attempting to add a new precipitation gage in a
project that used hypothetical storm precipitation in the met model.
29.11.5 Documentation
The Hydrologic Modeling System HEC-HMS: Quick Start Guide (Version 4.4 March 2020) provides a brief
description of the program for new users. It describes the different parts of the interface and the basic steps
necessary to obtain simulation results. A tutorial takes the user through the creation of a new project and
shows how to obtain results.
The Hydrologic Modeling System HEC-HMS: User's Manual (Version 4.4 March 2020) contains extensive
information on installing and using the program. Details on the use of each of the features and capabilities
in the program are included. The manual has been updated with information describing new features added
to the program for this Version 4.4 release.
The Hydrologic Modeling System HEC-HMS: Validation Guide (Version 4.3 August 2018) contains information
on the procedures used to certify the software for release. The manual describes the tests that have been
established and the procedures used for determining the correct result for each test. An accompanying data
kit includes all of the project data necessary to replicate the tests performed at HEC prior to certifying a new
release for distribution.
The Hydrologic Modeling System HEC-HMS: Applications Guide (March 2015) illustrates how to apply the
program in a variety of different studies. Data requirements, calibration procedures, and typical results
presentation styles are provided for studies ranging from flood risk management to sediment yield.
The Hydrologic Modeling System HEC-HMS: Technical Reference Manual (March 2000) continues to
accurately describe the mathematical models included in the program. New simulation capabilities have
been added to the program and are not included in the manual. The manual is currently undergoing a major
revision to expand documentation of existing mathematical models and fully describe the newly added
models.

29.11.6 Support Policy

Technical support for program users within the U.S. Army Corps of Engineers is provided through an annual
subscription service. Subscribing offices can expect full support from HEC staff in the routine application of
the program. Users are strongly urged to consult with HEC staff on the technical feasibility of using the
program before beginning a project with unique requirements such as grid cell hydrology, snow melt,
continuous simulation, sediment transport, or water quality. Special guidance is also available for the
development of models for flow forecasting. Extended support for large or complex projects can be
arranged under a separate reimbursable project agreement.
Support cannot be provided to users outside the U.S. Army Corps of Engineers. Several companies and
organizations offer varying levels of support, some through a fee-for-service support similar to the support
provided to subscribing Corps offices. Such service agreements are between the user and the vendor and do
not include HEC staff. Vendors can be located through internet searches.
Reporting of suspected program errors is unrestricted and we will reply to all correspondence concerning
such errors. We are continuously working to improve the program and possible bugs should always be
reported. Reports should include a written description of the steps that lead to the problem and the effects
that result from it. If we cannot reproduce the reported problem, we may ask you to send a copy of your
project.
Request support or report program errors through the following channels:
• Visit our web site at http://www.hec.usace.army.mil122.
• Send email to hms@usace.army.mil123.
• Call +1.530.756.1104, 7:30 am to 4:30 pm Pacific Time Monday through Friday.
122 http://www.hec.usace.army.mil/
123 mailto:hms@usace.army.mil

HEC HMS - User's - Manual v4.11 20231018

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HEC HMS - User's - Manual v4.11 20231018

Uploaded by

Copyright:

Available Formats

HEC-HMS User's Manual

HEC-HMS Users Manual

1 Report Documentation Page ..................................................................... 49

4.3.2 Linux Operating System ............................................................................ 63

5.2.8 Exporting Values from Global Editor Table .............................................. 89

6.2.1 Files Generated by the Program ............................................................. 114

7.1.9 Elevation ................................................................................................... 144

7.4.1 Creating Terrain Data............................................................................... 181

8.4.2 Copying an Element ................................................................................. 205

8.7.3 Selecting Calibration Parameters ........................................................... 236

9.2.1.6 Relief Ratio (RR) ....................................................................................... 272

10.3.1.3 Required Meteorologic Model Boundary Conditions............................. 297

10.5.3 Exponential Loss...................................................................................... 326

10.6.7 User-Specified Unit Hydrograph Transform ........................................... 360

12.2.2 Initial Condition ........................................................................................ 392

12.4.12.1 Monthly Evaporation................................................................................ 412

14.1.2 Copying a Meteorologic Model ............................................................... 431

14.3.5 Interpolated Longwave ............................................................................ 456

14.8 Dew Point ................................................................................................. 501

15.1.7 Simulation Results Output....................................................................... 531

16 Model Optimization ................................................................................. 567

16.4.2 Individual Elements.................................................................................. 607

17.8.1 Individual Elements.................................................................................. 642

18.4.2 Individual Elements.................................................................................. 670

20.1.1 Creating a New Ensemble Analysis ........................................................ 712

21.3.4 Muskingum............................................................................................... 748

22 Data Storage in HEC-DSS ........................................................................ 771

23.5 Image Exporter......................................................................................... 791

23.8.1.2 Step 2: Determine the Time-Shift ............................................................ 804

29.1.1.8 Precipitation Frequency Depths Tabular Export .................................... 830

29.1.2.46 Synchronize Clark transform component editor and global editor

29.2.1.7 Hypothetical Storm Computed Depth Area Checks .............................. 919

29.2.2 Bugs Fixed ................................................................................................ 930

29.2.2.40 Draw Properties for Shapefiles Not Saving Correctly............................ 937

29.3.1.2 Enhanced Element Split........................................................................... 957

29.3.1.30 DSS Grid Record Validator....................................................................... 974

29.3.2.23 Selecting a New Downstream Connection............................................. 979

29.5.2.12 2D Diffusion Wave computed results discrepancy.............................. 1005

29.10 v.4.4.1 Release Notes ............................................................................ 1027

1 Report Documentation Page

1. REPORT DATE 2. REPORT TYPE 3. DATES COVERED (From -

4. TITLE AND SUBTITLE 5a. CONTRACT NUMBER

5c. PROGRAM ELEMENT NUMBER

6. AUTHOR(S) 5d. PROJECT NUMBER

5F. WORK UNIT NUMBER

7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) 8. PERFORMING

Report Documentation Page – 49

9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/ MONITOR'S

11. SPONSOR/ MONITOR'S

12. DISTRIBUTION / AVAILABILITY STATEMENT

13. SUPPLEMENTARY NOTES

15. SUBJECT TERMS

16. SECURITY CLASSIFICATION OF: 17. LIMITATION 18. NUMBER 19a.

Report Documentation Page – 50

Report Documentation Page – 51

3.3.1 Watershed Physical Description

3.3.2 Meteorology Description

3.3.3 Hydrologic Simulation

3.3.4 Parameter Estimation

3.3.5 Forecasting Future Flows

3.3.6 Evaluating Depth-Area Effects

3.3.7 Building Frequency Curves

3.3.8 Assessing Uncertainty