Innovative Earthquake Monitoring Application PDL2AQMS in Action
PDL2AQMS
NetOps XI
Ellen, Lind, & Paul
Coding by Ellen Yu, Mike Hagerty, & Aparna Bhaskaran
PDL2AQMS
ISTI Python application that allows QuakeML to be injected into an AQMS database.
Works on both Oracle and Postgres systems (orig developed for Postgres by MH)
Motivation:
Originally for PRSN to ingest USGS NEIC PDL solutions to compare in
Jiggle against local AQMS and EarlyBird solutions.
PDL drives it via command line options (listens for origins, mags, arrivals, amps).
Also allows command line QuakeML injection as a pure loader process.
Allows filtering of events by depth, magnitude, location, and originating network.
PDL2AQMS - Mww usage
The finer points of Mww ingest
●
ANSS Large Magnitude policy requires RSN’s to use Mww from NEIC for events
with M >= 6.0 as preferred Magnitude
●
NEIC is producing automatic moment tensors with Mww and distributing via PDL
●
PDL2AQMS can automatically assoc origins in AQMS using “eventassoc” table
●
Assoc of origins is local solution with NEIC origin+Mww
●
Assoc happens using PDL Indexer <OR> brute force configuration - dx,dy,dz,dOT.
●
RSN retains local solution,
●
Currently, setting Mww be the pref magnitude is a manual operation via a Flask
App
●
Automating this process requires 3 modifications to AQMS, adding
eventassoc
table, and Mww rules for
magprefpriority
table, stored procedure updates.
AQMS Mww - Flask App
AQMS Mww - Flask App
AQMS Mww - Flask App
AQMS Mww - Flask App
PDL2AQMS
SCSN Implementation
●
Oracle port -
https://gitlab.com/aqms-swg/aqms-db-ora
●
Running in production since 3/2021
○
Database insert of solution automatic. No auto association of magnitude
●
Current settings chosen to gather more use cases. Likely to be refined when process is
automated.
○
selectflag=0
○
Magnitude >=3.5
○
Lat 31-41, lon -113, -126 (CA, NV region)
○
All network sources
○
Imported 108 events - but only 2 candidate events (i.e. those with Mw’s) - other RSNs encouraged to try
either database port
AQMS via Docker Containers
Netops XI
Paul Friberg
Coding by Serhiy Vasilyev and deployment testing by Mitch Gold
Docker, what is it?
●
Docker is a virtualized environment which is “Platform As A Service”
(PAAS) to deploy applications.
●
Effectively a mini-light-weight VM that contains just what is needed to
run a single software program
●
Docker instances are called
Containers
●
Containers allow easy deployment anywhere, on bare-metal, VMs, and
in the cloud.
●
Communicate with each other using well defined channels & share data
over Volumes.
●
Provides developers with a consistent build environment for testing.
AQMS Database containers
Gitlab repo:
https://gitlab.com/aqms-swg/docker-playground
●
Postgres 10,11,12
●
Oracle 18.4 (developer release)
All containers have copy of the AQMS database schema.
Next step: enter scripts to populate metadata, reference tables (for example
magprefpriority etc) into gitlab
AQMS containers
ISTI has been testing a fully containerized AQMS for CGS & ISTI
●
Tested so far:
CMS, Earthworm, Winston, & AQMS DB postgres
●
Currently being tested:
alarming, ec, rcg, pws, & wa
●
To be developed:
trig2db, tc
All internal to ISTI gitlab, but will be pushed to AQMS-SWG gitlab once tested.
ISTI versions: fdsn eventservice, fdsn dataselect service
Provides a clean way to build AQMS software suite from gitlab repo
EW + AQMS RPMs
ISTI has been building RPMs for the Earthworm distro
We are awaiting the results of docker AQMS testing because that will obviate
the need for AQMS RPMs.
PDL2AQMS is a Python application designed for injecting QuakeML data into AQMS databases, supporting both Oracle and Postgres systems. Developed by a team including Ellen Yu, Mike Hagerty, and Aparna Bhaskaran, this tool enables comparison of earthquake solutions and automates association processes. The application integrates Mww ingestion policies and Flask app functionalities for enhanced earthquake monitoring capabilities.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
PDL2AQMS NetOps XI Ellen, Lind, & Paul Coding by Ellen Yu, Mike Hagerty, & Aparna Bhaskaran
PDL2AQMS ISTI Python application that allows QuakeML to be injected into an AQMS database. Works on both Oracle and Postgres systems (orig developed for Postgres by MH) Motivation: Originally for PRSN to ingest USGS NEIC PDL solutions to compare in Jiggle against local AQMS and EarlyBird solutions. PDL drives it via command line options (listens for origins, mags, arrivals, amps). Also allows command line QuakeML injection as a pure loader process. Allows filtering of events by depth, magnitude, location, and originating network.
PDL2AQMS -Mww usage The finer points of Mww ingest ANSS Large Magnitude policy requires RSN s to use Mww from NEIC for events with M >= 6.0 as preferred Magnitude NEIC is producing automatic moment tensors with Mww and distributing via PDL PDL2AQMS can automatically assoc origins in AQMS using eventassoc table Assoc of origins is local solution with NEIC origin+Mww Assoc happens using PDL Indexer <OR> brute force configuration -dx,dy,dz,dOT. RSN retains local solution, Currently, setting Mww be the pref magnitude is a manual operation via a Flask App Automating this process requires 3 modifications to AQMS, adding eventassoc table, and Mww rules for magprefpriority table, stored procedure updates.
PDL2AQMS SCSN Implementation Oracle port -https://gitlab.com/aqms-swg/aqms-db-ora Running in production since 3/2021 Database insert of solution automatic. No auto association of magnitude Current settings chosen to gather more use cases. Likely to be refined when process is automated. selectflag=0 Magnitude >=3.5 Lat 31-41, lon -113, -126 (CA, NV region) All network sources Imported 108 events -but only 2 candidate events (i.e. those with Mw s) -other RSNs encouraged to try either database port
AQMS via Docker Containers Netops XI Paul Friberg Coding by Serhiy Vasilyev and deployment testing by Mitch Gold
Docker, what is it? Docker is a virtualized environment which is Platform As A Service (PAAS) to deploy applications. Effectively a mini-light-weight VM that contains just what is needed to run a single software program Docker instances are called Containers Containers allow easy deployment anywhere, on bare-metal, VMs, and in the cloud. Communicate with each other using well defined channels & share data over Volumes. Provides developers with a consistent build environment for testing.
AQMS Database containers Gitlab repo: https://gitlab.com/aqms-swg/docker-playground Postgres 10,11,12 Oracle 18.4 (developer release) All containers have copy of the AQMS database schema. Next step: enter scripts to populate metadata, reference tables (for example magprefpriority etc) into gitlab
AQMS containers ISTI has been testing a fully containerized AQMS for CGS & ISTI Tested so far: CMS, Earthworm, Winston, & AQMS DB postgres Currently being tested: alarming, ec, rcg, pws, & wa To be developed: trig2db, tc All internal to ISTI gitlab, but will be pushed to AQMS-SWG gitlab once tested. ISTI versions: fdsn eventservice, fdsn dataselect service Provides a clean way to build AQMS software suite from gitlab repo
EW + AQMS RPMs ISTI has been building RPMs for the Earthworm distro We are awaiting the results of docker AQMS testing because that will obviate the need for AQMS RPMs.
