official-apps/SeismicHazardForecasting
10
0
Fork 1
Code Issues Pull Requests Activity

M_max validation #14

New Issue
Closed
opened 2025-06-09 17:20:55 +02:00 by ftong · 2 comments
ftong commented 2025-06-09 17:20:55 +02:00
Member
Copy Link

For implementation in the seismic hazard forecasting app, the following maximum magnitude limits are recommended for each Ground Motion Model (GMM) to avoid forecasting unrealistic ground motion values:

Lasocki (2013)
Atkinson (2015)
Convertito (2012) – Geysers

These models are based on anthropogenic seismicity and were developed using empirical data for magnitudes up to M ~ 4.0. A realistic upper limit of M = 4.5 is suggested.

Akkar and Bommer (2010)

This model is based on natural seismicity and is valid for magnitudes up to M = 8.0, so no restriction is required.

TODO: add input validation check that M_max <=4.5 when forecasting is selected EXCEPT if the AkkarBommer2010 ground motion model is selected

For implementation in the seismic hazard forecasting app, the following maximum magnitude limits are recommended for each Ground Motion Model (GMM) to avoid forecasting unrealistic ground motion values: Lasocki (2013) Atkinson (2015) Convertito (2012) – Geysers These models are based on anthropogenic seismicity and were developed using empirical data for magnitudes up to M ~ 4.0. A realistic upper limit of M = 4.5 is suggested. Akkar and Bommer (2010) This model is based on natural seismicity and is valid for magnitudes up to M = 8.0, so no restriction is required. TODO: add input validation check that M_max <=4.5 when forecasting is selected EXCEPT if the AkkarBommer2010 ground motion model is selected
ftong self-assigned this 2025-06-09 17:20:55 +02:00
ftong commented 2025-07-02 15:43:33 +02:00
Author
Member
Copy Link

Fixed in f4d2cfc3cd

Fixed in https://epos-apps.grid.cyfronet.pl/official-apps/SeismicHazardForecasting/commit/f4d2cfc3cd31e7efb499a121f4a3ec7a89d48adb
ftong closed this issue 2025-07-02 15:43:33 +02:00
asia commented 2025-07-02 20:54:58 +02:00
Owner
Copy Link

This has to be merged to the main branch for the fix to be visible to everybody, please create a merge request

This has to be merged to the main branch for the fix to be visible to everybody, please create a merge request
Login to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
ftong
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: official-apps/SeismicHazardForecasting#14
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?