matamadio
commented
3 weeks ago I can produce the config files for each hazard type, I just need some guidance on how to frame it.
E.g. I guess each config should list which variables are loaded and set some default parameters.
Floods_config:
- Default flood model: FATHOMv3
- Hazard type: 5 flood types (processing is equivalent) ['FLUVIAL_UNDEFENDED'; 'FLUVIAL_DEFENDED', 'PLUVIAL_DEFENDED, 'COASTAL_UNDEFENDED'; 'COASTAL_DEFENDED']
- Historical (2020)+ projections (period: [2030, 2050, 2080], scenario:[SSP1, SSP2, SSP3, SSP5])
- Return periods: [5, 10, 20, 50, 100, 200, 500, 1000]
- All exposure types allowed
- All approaches allowed
Cyclones_config:
- Default flood model: STORM
- Hazard type: strong wind
- Historical (1979-2014)+ projections (2015-2050)
- Return periods: [10, 20, 50, 100, 200, 500, 1000]
- Allowed approaches:
- Function x Built-up
- Classes x Pop, Agri
Heat_config:
- Default flood model: VITO
- Hazard type: heat stress
- Historical (1980-2009)
- Return periods: [5, 20, 100]
- Allowed approaches:
- Allowed approaches:
- Classes x Pop, Agri
Is your feature request related to a problem? Please describe. There is some duplication of code and configuration files in the current codebase. This makes it hard to maintain and to further extend codebase in the future.
Describe the solution you'd like In the best case, we can split configurations and code into common and task-specific files.
Describe alternatives you've considered Not relevant.
Additional context Not relevant.