Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Experiment with damages and losses without input files #654

Open
5 tasks done
ArdtK opened this issue Dec 12, 2024 · 1 comment
Open
5 tasks done

Experiment with damages and losses without input files #654

ArdtK opened this issue Dec 12, 2024 · 1 comment
Assignees
Labels
architecture refactoring Architectural changes to be addressed by the GAP team enhancement New feature or request

Comments

@ArdtK
Copy link
Contributor

ArdtK commented Dec 12, 2024

Goal
Being able to run damages and losses analyses without input files to make the fully scriptable.

Context
For repetitive executions of analyses like damages and losses (e.g. for uncertainty or adaptation) it is currently a hassle to produce all required input files with their variations (e.g. damage curves, resilience curves).

Scope

@ArdtK ArdtK added this to the Sprint 2024 Q4.4 milestone Dec 12, 2024
@ArdtK ArdtK self-assigned this Dec 12, 2024
@ArdtK
Copy link
Contributor Author

ArdtK commented Dec 12, 2024

Oveview of inputs

Analysis Input Reader Dataclass Read in init Remark
Damages Damage Functions Only for "MAN"
LossesBase Hazard names Via AnalysisInput
LossesBase Resilience curves
LossesBase Traffic intensities
LossesBase Values of time

@Carsopre Carsopre added enhancement New feature or request architecture refactoring Architectural changes to be addressed by the GAP team labels Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
architecture refactoring Architectural changes to be addressed by the GAP team enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants