TUM project seminar
Uncertainty Quantification in Hydrology
A team seminar connecting HBV rainfall-runoff calibration, local and global sensitivity analysis, and input/output uncertainty propagation.
- Role
- Group contributor; individual ownership of assignment results is not claimed
- Classification
- Group coursework
- Institution
- Technical University of Munich
01Problem
Why this work exists
A calibrated hydrological model can still hide large uncertainty from forcing data, rating curves, parameters, and model structure.
02Contribution
What I can claim
Contributed within a three-person TUM seminar team to a progressive workflow covering differential-evolution calibration, sensitivity analysis, precipitation perturbation, and rating-curve uncertainty. Individual assignment ownership is not claimed.
Method
Where an interval comes from
An uncertainty band is not produced by widening a line. It is what disagreement looks like once it has been summarised.
Perturb the rain834 of 2,000 still beat the reference
Perturb the ruler0 of 2,000 beat the reference
Simulate
Several members are run from the same starting point under different assumptions.
Diverge
They agree near the start and separate through the middle of the horizon, which is where the modelled system is genuinely hardest.
Summarise
The spread is collapsed into a band. The band is a description of the disagreement, and it is only as honest as the ensemble that produced it.
What this does not show
An ensemble only explores the assumptions it was given. Agreement between members is not evidence of correctness - it can equally mean they share a blind spot.
03System
Workflow and decisions
- 01HBV baseline
- 02Parameter calibration
- 03Local sensitivity
- 04Global sensitivity
- 05Input and output uncertainty
- Python
- NumPy
- SciPy
- SALib
- pandas
- Matplotlib
- LaTeX
04Evidence
What is actually versioned
Versioned group-seminar result for the calibrated HBV baseline.
The seminar report finds rating-curve uncertainty more consequential than the tested precipitation noise.
05Quality controls
How the work is checked
- Versioned reports, figures, and result artifacts
- Explicit environment variables replace machine-specific data paths
- Repository integrity checker validates key seminar artifacts
- Team authorship and unavailable course inputs are documented
06Limitations
Where the evidence stops
- Group coursework; individual ownership of each result is not established
- Course-provided forcing data and the hmg package are not redistributable
- Full scientific reruns require authorized course inputs
What this changed in my practice
Calibration quality cannot stand in for uncertainty analysis; observation and transformation errors can dominate parameter uncertainty.