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

link the aggregate_wl and incorporate event type in the LossesBase #526

Closed
Tracked by #518
sahand-asgarpour opened this issue Jul 16, 2024 · 0 comments
Closed
Tracked by #518
Assignees
Labels
bug Something isn't working
Milestone

Comments

@sahand-asgarpour
Copy link
Contributor

sahand-asgarpour commented Jul 16, 2024

In the LossesBase, EV1 is hard-coded, while multiple event-based hazard maps can be introduce, or multiple hazard maps wih return-periods can be input. Hence, the LossesBase can not currently handle these situations.

Moreover, aggregate_wl is linked to analysis_config_data while this exists in the network_config_data.

So link the aggregate_wl to the network_config_data and incorporate event type (RP, or EV) in the LossesBase.

@sahand-asgarpour sahand-asgarpour mentioned this issue Jul 16, 2024
1 task
@sahand-asgarpour sahand-asgarpour self-assigned this Jul 16, 2024
@sahand-asgarpour sahand-asgarpour added bug Something isn't working Launch labels Jul 16, 2024
@sahand-asgarpour sahand-asgarpour added this to the Launch 2024 milestone Jul 16, 2024
@sahand-asgarpour sahand-asgarpour changed the title link the aggregate_wl to the network_config_data and incorporate event type (RP, or EV) in the LossesBase link the aggregate_wl and incorporate event type in the LossesBase Jul 16, 2024
@sahand-asgarpour sahand-asgarpour linked a pull request Jul 16, 2024 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant