Abstract
AbstractReal‐time ground motion alerts, as can be provided by Earthquake Early Warning (EEW) systems, need to be both timely and sufficiently accurate to be useful. Yet how timely and how accurate the alerts of existing EEW algorithms are is often poorly understood. In part, this is because EEW algorithm performance is usually evaluated not in terms of ground motion prediction accuracy and timeliness but in terms of other metrics (e.g., magnitude and location estimation errors), which do not directly reflect the usefulness of the alerts from an end user perspective. Here we attempt to identify a suite of metrics for EEW algorithm performance evaluation that directly quantify an algorithm's ability to identify target sites that will experience ground motion above a critical (user‐defined) ground motion threshold. We process 15,553 recordings from 238 earthquakes with M > 5 (mostly from Japan and southern California) in a pseudo‐real‐time environment and investigate two end‐member EEW methods. We use the metrics to highlight both the potential and limitations of the two algorithms and to show under which circumstances useful alerts can be provided. Such metrics could be used by EEW algorithm developers to convincingly demonstrate the added value of new algorithms or algorithm components. They can complement existing performance metrics that quantify other relevant aspects of EEW algorithms (e.g., false event detection rates) for a comprehensive and meaningful EEW performance analysis.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.