HEC references for capability planning¶
Use these references before choosing boundary types, meteorological inputs, mapping semantics, or land-surface methods. HEC manuals describe HEC-RAS behavior and methods; installed RAS Commander, fast-dss, fast-map, and ras2cng contracts establish which operations the current environment exposes. A manual link does not establish API support or qualify a project.
Choose the applicable version¶
Record the engine version, solver, model dimensions, task, and relevant package versions in the plan. Start at the HEC-RAS documentation portal and select the engine's manual version. The links below were opened and checked on November 17, 2026. RAS links use the explicit 6.6 manual baseline, not a moving latest URL; use the matching version for a 7.x or older project and record any changed method or control. A page can retain historical version wording within its body, so inspect both its version selector and the relevant section.
These are passive, reader-activated citations. Do not add automatic fetching, embeds, mirrored manuals, or citation-driven network calls to modeling workflows. During planning research, open only the relevant official sections; report unavailable evidence instead of inventing a replacement URL.
Planning matrix¶
| Workflow and planning question | Official reference and version | Decision informed and applicability check |
|---|---|---|
| Boundary conditions: which external, internal, and global boundaries are appropriate? | 2D boundary and initial conditions, 6.6 | Distinguish stage/flow hydrographs, normal depth, rating curves, and spatial meteorology. Check inflow/outflow direction and initial state; normal-depth and rating-curve conditions are described for outflow locations. Do not apply these 2D rules automatically to a 1D boundary. |
| Gridded precipitation: uniform rainfall excess or spatial meteorology? | Global boundary conditions, 6.6 | Select the intended precipitation mode and source, coordinate/units treatment, and active stations. Plan incremental and accumulated input checks plus plan-specific Event Conditions inspection. Avoid applying losses twice when using rainfall excess. |
| Other meteorology: which variable and input mode does this engine consume? | Global boundary conditions, 6.6; 6.6 new features: Wave Forcing | Inspect the variable-specific control and solver applicability. Wind, evapotranspiration, pressure, and wave forcing are distinct inputs; storage of a variable in DSS does not prove the engine can consume it. Release notes identify 6.6 wave-force grids and NetCDF/DSS-7 inputs; follow the detailed method before configuring them. |
| Vortex/native conversion: what transformation is needed before a DSS file is attached? | Vortex utilities, HEC-HMS Technical Reference Manual; Creating gridded boundary conditions, HEC-HMS guide | Select variables, clipping, CRS, cell size, resampling, and data-type/units treatment. The guide demonstrates MRMS conversion and DSSVue inspection. These pages are not pinned to a Vortex release; check the installed tool. HMS-specific grid requirements are not automatically RAS requirements, and Vortex coverage is not proof of native fast-dss coverage. |
| DSS exchange: what do pathnames and time bounds mean? | General concepts for HEC-DSS, DSSVue User's Manual | Distinguish regular/irregular time-series, paired, and grid conventions. Grid records use start/end times rather than the regular-series interval convention; inspect header units/data type and UTC grid bounds. A valid catalog alone does not establish complete forcing coverage. This web manual is not a fast-dss API contract. |
| Mapping: which quantity, saved profile, terrain, and output mode are being compared? | Creating results maps, RAS Mapper 6.6 | Select quantity/profile/output mode and associated terrain. Screen-dependent dynamic maps and terrain-resolution stored maps need not agree pixel-for-pixel. Plan parity against equivalent stored products, with matching terrain, grid, profile, interpolation, wet mask, and thresholds; a map export is not an independent hydraulic solve. |
| Land use and roughness: how do classifications become model parameters? | Land classification layers, RAS Mapper 6.6 | Check classification IDs/names, source priority, raster resolution, classification polygons, parameter tables, and geometry association. Land-cover categories are a surrogate for roughness, not calibrated channel roughness. Retain the class-to-parameter lookup and verify final preprocessed values. |
| Soils and infiltration: which method and initial estimates are justified? | Infiltration methods, 2D User's Manual 6.6; Land classification layers, RAS Mapper 6.6 | Choose SCS Curve Number, Deficit Constant, or Green and Ampt based on the intended application and available inputs. Distinguish soil groups from texture classes and identify required method-specific units/initial conditions. HEC's tabulated estimates need project calibration and validation; do not silently assign them as final values. |
| Infiltration overrides: what actually reaches each cell? | Infiltration parameters, RAS Mapper 6.6 | Distinguish the base layer, geometry-wide overrides, regional overrides, and final-value raster. Plan separate readback and preprocessed-cell checks rather than assuming a changed source table changed the active geometry. |
| ras2cng delivery: what hydraulic meaning must an exported asset preserve? | Mapping results, RAS Mapper 6.6; Creating results maps, RAS Mapper 6.6 | Preserve plan/profile, quantity, terrain, units, CRS, and map semantics. Use ras2cng's own installed contracts for packaging and serving; HEC does not document or certify that project's export formats. |
Terrain, HMS handoff, and consequence planning¶
These official sections were opened on November 17, 2026. Use current package contracts for the implementation; the HEC sources establish modeling concepts and checks rather than support for third-party engines.
| Workflow and planning question | Official reference and version | Decision informed and applicability check |
|---|---|---|
| Terrain acquisition and association: which surface drives geometry and mapping? | Terrain layer, RAS Mapper 6.6 | Record bathymetric coverage, terrain sources/priority, rounding, vertical conversion, stitching, CRS, and geometry/plan associations. Terrain resolution and computational mesh resolution are separate choices; a displayable VRT alone does not establish the terrain used by preprocessing. |
| Terrain modifications: what is the effective surface and what must travel with a clone? | Terrain modification, RAS Mapper 6.6 | Choose replacement, high-ground/channel, or additive modification behavior deliberately; retain source terrain and modification definitions. Virtual clones reference the base terrain, so their dependencies must remain available. Compare effective elevations and downstream preprocessing/mapping, not only the vector edit. |
| HMS-to-RAS handoff: where should the hydrograph enter the hydraulic model? | Internal boundary conditions: Use with HEC-HMS Results, 2D User's Manual 6.6 | Identify the HMS subbasin outlet and whether upstream routing is already represented. Avoid distributing an already-routed outlet hydrograph along a long reach or area, which can route it twice. Check inflow location, incremental versus total contributions, units, time coverage, and the RAS boundary's cell allocation. |
| Consequences: which hydraulic outputs and exposure assumptions support an event estimate? | HEC-FIA overview; HEC-FIA features | The official overview identifies depth/arrival grids and DSS stage hydrographs as hydraulic event inputs; the features page distinguishes event consequences, inventories, loss functions, and uncertainty. Verify event/scenario, elevation/depth datum, inventory provenance, valuation basis, and function applicability. These web pages are not version-pinned technical contracts. They describe HEC-FIA, not go-consequences: no feature parity, interchangeability, regulatory acceptance, or HEC endorsement of go-consequences is implied. Use the installed go-consequences contracts and qualified examples for its actual supported methods. |
Flood-science research planning¶
The following sections were also opened on November 17, 2026. Use them to design experiments and evidence collection before scheduling an ensemble. They do not supply universal acceptance thresholds or establish that a particular workflow is implemented in RAS Commander.
| Research question | Official reference and version | Planning decision and applicability |
|---|---|---|
| Are results sensitive to mesh and computational timestep? | Selecting an appropriate grid size and time step, 2D User's Manual 6.6; 6.6 solver changes | Plan mesh/time refinement together, preserve key flow barriers, and compare decision-relevant output quantities. Identify the selected equation set and actual timestep history. Read the release-specific solver changes before applying Courant guidance: the 6.6 manual retains explicit SWE-EM wording, while its release notes describe a semi-implicit advection change. Record this discrepancy; do not turn either passage into a universal stability limit. |
| Which changes measure numerical sensitivity versus physical uncertainty? | Model accuracy, stability, and sensitivity, User's Manual 6.6 | Separate experiments changing timestep, spacing, or numerical settings from those changing roughness, boundary inputs, or physical parameters. Retain baseline, run messages, conservation diagnostics, and comparable output metrics. This section addresses 1D unsteady analysis; its cross-section and theta guidance does not automatically apply to a 2D solver. |
| What observations and events support calibration and independent evaluation? | Calibration of unsteady flow models, User's Manual 6.6 | Examine observation datum, time basis, rating-curve limitations, high-water-mark quality, and geometry before fitting parameters. Use physically defensible parameter ranges and reserve other events or periods for evaluation. HEC calls this latter step verification; retain that source terminology while defining the study's validation/evaluation terms. If evaluation prompts retuning, disclose it and rerun the affected comparisons. The manual's 1D examples are not a universal 2D calibration protocol. |
| What does an uncertainty ensemble represent? | Uncertainty analyses, HEC-HMS User's Manual 4.14 | For HMS-to-RAS research, distinguish sampled hydrologic parameters from uncertain meteorology, boundaries, terrain, and hydraulic structure. Record distributions, dependencies, sampling policy, and omitted uncertainty sources. This chapter describes HMS parameter uncertainty and identifies separate integrated assessment needs for meteorology; it is not evidence of a native RAS uncertainty-trial API. A sensitivity range alone is not a probabilistic confidence interval. |
For a flood-science study, define the hypothesis, comparison quantities, observational support, calibration/evaluation split, numerical sensitivity design, and uncertainty assumptions before execution. Record failed or excluded runs and their reasons; execution success, input readback, and mapping parity establish different things from agreement with observations. The repository notebooks below demonstrate mechanisms and particular qualification checks, not general validation of a flood model or universal research conclusions.
Connect the manual to executable examples¶
Use the repository's domain-skill references for current API calls. These examples show where the planning decisions become observable checks; read notebook source cells and retained evidence rather than rerunning them just to look up a workflow.
- 310: DSS boundary extraction connects project boundary inventory to catalog records, extracted series, plots, and exports. 322: native DSS records and recovery separates native backend selection, round trips, and recovery; its documented unsupported-operation behavior is not a fallback guarantee.
- 728: extend gridded DSS forcing window is the forcing-window reference. Check its declared source interval and extension policy before changing event coverage.
- 602: Rust horizontal mapping comparison compares depth/WSE products using equivalent profiles and pixel-depth filtering. Its horizontal qualification does not establish sloping-interpolation parity.
- 211: final Manning's n and infiltration anchors final-value inspection. 218: infiltration base override authoring distinguishes base and regional signals, preprocessing, and final plan-HDF evidence. Use those distinctions when planning an infiltration edit.
Planning handoff¶
Return a bounded note containing the task and engine version, chosen method/input mode, the relevant official section links and manual versions, project assumptions (units, datum, time basis, CRS), and the API/example evidence supporting the proposed operation. List unresolved applicability or capability gaps separately. A documentation finding does not authorize project mutation, model execution, downloads, or publication.