Calibrated TC impact functions (Eberenz et al. 2021) were fit on winds with double-counting fixed in #833
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Read ImpfSetTropCyclone.from_calibrated_regional_ImpfSet() and calibrated_regional_vhalf() and trace how they expose the Eberenz et al. 2021 values. Check the wind model history around #833 and the issue's cited damage comparison. Done means the calibration caveat is clearly documented in both functions, or a warning is added, so users understand the mismatch between calibrated curves and corrected winds.
Written by the indexing model from the issue text.
Description
CLIMADA is such an important resource, thank you for maintaining it!
While working with tropical cyclone hazard rasters produced by older versions of CLIMADA, we found a mismatch between the current TC wind model and the calibrated impact functions CLIMADA ships.
- Before 4.1.0, the Holland 2008/2010 wind models counted the storm's translational velocity twice (fixed in #833, Jan 2024).
ImpfSetTropCyclone.from_calibrated_regional_ImpfSet()andcalibrated_regional_vhalf()return thev_halfvalues from Eberenz et al. 2021 (https://doi.org/10.5194/nhess-21-393-2021). Those were calibrated on CLIMADA v1.4.1, which still had the double count. The values are unchanged through 6.1.0, and #833 doesn't mention them.
So the current default workflow (≥4.1 H08 winds + calibrated regional impact functions) pairs corrected winds with curves fit to inflated winds, and underestimates damage:
- With the 2020 NA2
v_half, post-fix winds give damage fractions 40–70% too low at 40–60 m/s. - The bias isn't a constant scale factor: the extra wind equals forward speed, so fast-moving storms are affected more than slow ones.
Might be worth adding a note to the docstrings of the calibration functions that raises the calibration issue, or adding a warning to them until they can be calibrated again.
PR #692 mentions issues reproducing NA1’s curve, possibly related!
- Dominant language
- Jupyter Notebook
- Stars
- 478
- Forks
- 166
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CLIMADA-project/climada_python
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
CLIMADA-project/climada_python#1336 ·
-
CartoDB basemaps now need an API key (somewhat urgent)Possibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
CLIMADA-project/climada_python#1332 · 4 comments · 1 reaction ·
-
warnings
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
CLIMADA-project/climada_python#1241 ·
-
ResourceWarningOpenwarnings
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
CLIMADA-project/climada_python#1239 ·
-
warnings
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
CLIMADA-project/climada_python#1226 ·
All issues in CLIMADA-project/climada_python
Similar issues
-
backend refactor
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
NIAEFEUP/tts#927 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ash-project/spark#303 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
modelscope/modelscope#1833 ·
Maintainers usually reply within 1 day