Repository navigation
CHESS DET
Workflow selector: config.workflow = 2 (Deterministic). It replaces the former EVA alias.
Main functions: chess_det_formater.m (forcing), Structure_Reponses/Deterministic/chess_det.m (responses).
DET is a calculator: "what does each storm in the database do to this structure?" Every storm of the requested storm type and datasets is used once, as recorded. There are no replicates, no forcing uncertainty, no sampling and no hazard curves.
Use it to:
- Inspect individual storms (which storms overtop, and by how much).
- Check a PSE before running PROS or LCS.
- Compare Peaks with Timeseries for the same storm.
- Trace a hazard curve value back to the storms behind it.
| Step | DET behaviour |
|---|---|
| Forcing |
chess_det_formater.m: every storm once, with its storm ID and time |
| Uncertainty | Skipped (u_engine = 1); manual uncertainty prompts are skipped and missing values set to 0. Bias prompts are unchanged |
| Adjustments | As configured: sea level rise, random tides, depth limitation, dry toe (Model Conventions) |
| Responses |
chess_det.m: compute_structure_response.m on the adjusted forcing |
Tides. apply_random_tides = 1 is allowed. The start hours drawn for each storm are saved in the config (tide_indx_xc, tide_indx_tc) and shared by the Peaks and Timeseries versions of a storm. Peaks get the tide at the start hour, while Timeseries get the tide series from that hour on, so the tide at the storm peak differs between the two. The Peaks vs Timeseries plot shows this on purpose.
Floodwall responses (P2, P3, Pu, nappe) are computed directly from the equations for each storm. There is no frequency-base step.
PSE/<struc_id>/<case_name>/DET/<db>_DET_{config_file,project_forcing,project_responses}.mat (Model Outputs).
Resp.(Peaks|Timeseries).(Default|WLP|WHP).(XC|TC) holds, per storm:
| Field | Meaning |
|---|---|
storm_id, time, dt
|
Storm identity and time steps |
SWL, Hm0, Tp
|
Forcing after adjustments; Hm0 is the database value |
Hm0_DL |
Depth-limited wave height used by the equations |
h, Rc
|
Toe depth SWL − toe_elevation and freeboard crest_elevation − SWL
|
| every computed response | Full history: one value per time step (Peaks have one step) |
Max |
One value per storm: the maximum of each field independently (Rc uses the minimum) |
From Visualization/det_methods.m via CHESSPlots:
-
response_vs_forcing_plot: any response against any forcing, coloured by a third field. -
response_table: a pop-out table of every storm's values. -
peaks_vs_timeseries_plot: the same response from Peaks and from Timeseries, storm by storm.
See Visualization for examples.
DET reads the same input file as PROS. The pros_*, mcs_* and csr_* fields are ignored. See config_reference.
Run-up & Overtopping
- Wave Run-up (R2%)
- Overtopping Discharge (q)
- Overtopping Volume (Q_vol)
- Overtopping Damage Classification
- Run-up Exceedance (z1%)
- Crest Velocity Exceedance (u1%)
Transmission
Wall Loads
Armor Stability
Damage Progression (LCS)
Hazard Metrics