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.

Sign up for GitHub

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

Jump to bottom

implement threshold validation for model-based earthquakes #32

Closed
ghost opened this issue Nov 2, 2021 · 0 comments · Fixed by #69
Closed

implement threshold validation for model-based earthquakes #32

ghost opened this issue Nov 2, 2021 · 0 comments · Fixed by #69
Labels
new feature A brand new feature to be added
Milestone
1.9.0

Comments

@ghost
Copy link

ghost commented Nov 2, 2021

We have implemented it for all hazards except model based eqs. We should decide if it is enough to just define a threshold for each demand, by exlcuding period.

is it enough to just define threshold for "SA", instead of 3 different thresholds for "0.3", "0.2" and "1.0"
@ghost ghost added this to the 1.7.0 milestone Nov 2, 2021
@ghost ghost added the new feature A brand new feature to be added label Nov 2, 2021
@ghost ghost self-assigned this Nov 3, 2021
@ghost ghost modified the milestones: 1.7.0, 1.8.0 Nov 23, 2021
@ghost ghost modified the milestones: 1.8.0, 1.9.0 Jan 24, 2022
@ghost ghost linked a pull request Mar 1, 2022 that will close this issue
32: Eq threshold management - removed period and used common method #69
Merged
@ghost ghost closed this as completed in #69 Mar 24, 2022
@ghost ghost mentioned this issue Mar 25, 2022
Merged
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
new feature A brand new feature to be added
Projects
None yet
Milestone
1.9.0
Development

Successfully merging a pull request may close this issue.

32: Eq threshold management - removed period and used common method IN-CORE/incore-services
0 participants