HVO needed a change to alarmdec, criteria based on event.etype

[Paul Friberg]

Hi all,

HVO had a need for a new criteria to be added to alarmdec, so I whipped off
this change using the RT/linux-dev/branch as the base for this. I will
check the code back in once I get someone to review what I did.  Any
volunteers? This has been tested at HVO on an Oracle instance, but I don't
anticipate any issues on a Postgres version..since there was no  major SQL
change involved.

The basis of the change was that HVO needed an extra criteria based on the
event.etype value to be tested...NEIC only wants to receive QuakeML updates
via PDL for actual earthquakes (not tremor or rockfall etc)....the new
criteria is named "EventTypes" and allows a comma separated list of types
from the database schema. This will allow the post-processing of only
Finalized earthquakes (etype=="eq") to be sent to PDL.

One thing I noticed during this new criteria implemented is that there
doesn't appear to be too many codes using the lib/rtevent/include/Event.h
specification for event types.....since it only lists 6 of them:

*// Definition of an origin list*
*typedef std::list<Origin> OriginList;*

*// Enumeration of the valid types of events*
*typedef enum {EVENT_UNKNOWN, EVENT_QUAKE,*
*      EVENT_QUARRY, EVENT_NUCLEAR, EVENT_SONIC,*
*      EVENT_SUBTRIG} eventType;*

*// Definition of the maximum event type enumeration*
*const int EVENT_MAX_TYPE = 6;*

*// String descriptions of each event type*
*const char eventTypeStrings[EVENT_MAX_TYPE][16] = {"Unknown", "Quake",*
*   "Quarry", "Nuclear",*
*   "Sonic", "SubTrig"};*

*// Database string descriptions of each event type*
*const char eventTypeDBStrings[EVENT_MAX_TYPE][DB_MAX_EVENTTYPE_LEN+1] =
{"uk",*
* "eq",*
* "qb",*
* "nt",*
* "sn",*
* "st"};*


--

===================================
Paul Friberg   p.fr...@isti.com
CEO/Seismologist
ISTI==Instrumental Software Technologies, Inc.
Phone 845.256.9290  FAX 845.256.9299   Mobile +1.914.489.4888

[Peter Lombard]

Paul,

I would volunteer for code review but I'm heading out of the country tomorrow
night. If you still need help, let me know when I get back 15 July.

Pete

Paul Friberg writes:
> Hi all,
>
> HVO had a need for a new criteria to be added to alarmdec, so I whipped off
> this change using the RT/linux-dev/branch as the base for this. I will
> check the code back in once I get someone to review what I did. Any
> volunteers? This has been tested at HVO on an Oracle instance, but I don't
> anticipate any issues on a Postgres version..since there was no major SQL
> change involved.
>
> The basis of the change was that HVO needed an extra criteria based on the
> event.etype value to be tested...NEIC only wants to receive QuakeML updates
> via PDL for actual earthquakes (not tremor or rockfall etc)....the new
> criteria is named "EventTypes" and allows a comma separated list of types
> from the database schema. This will allow the post-processing of only
> Finalized earthquakes (etype=="eq") to be sent to PDL.
>
> One thing I noticed during this new criteria implemented is that there

> doesn't appear to be too many codes using the *lib/rtevent/include/Event.h*

> specification for event types.....since it only lists 6 of them:
>
>
>
>
>
>
>
>
>
>
>
>
>

> **// Definition of an origin list**typedef std::list<Origin>
> OriginList;**// Enumeration of the valid types of events**typedef enum
> {EVENT_UNKNOWN, EVENT_QUAKE,** EVENT_QUARRY, EVENT_NUCLEAR,
> EVENT_SONIC,** EVENT_SUBTRIG} eventType;**// Definition of the maximum
> event type enumeration**const int EVENT_MAX_TYPE = 6;**// String
> descriptions of each event type**const char eventTypeStrings[EVENT_MAX_TYP*
>
>
>
>
> *E][16] = {"Unknown", "Quake",** "Quarry", "Nuclear",** "Sonic",
> "SubTrig"};**// Database string descriptions of each event type**const char
> eventTypeDBStrings[EVENT_MAX_T*
>
>
>
>
>
> *YPE][DB_MAX_EVENTTYPE_LEN+1] ={"uk",** "eq",** "qb",** "nt",** "sn",**
> "st"};**

>
>
> --
> ===================================
> Paul Friberg p.fr...@isti.com
> CEO/Seismologist
> ISTI==Instrumental Software Technologies, Inc.
> Phone 845.256.9290 FAX 845.256.9299 Mobile +1.914.489.4888
>

> --
> You received this message because you are subscribed to the Google Groups "AQMS" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to anss-aqms+...@googlegroups.com.
> To post to this group, send email to anss...@googlegroups.com.
> Visit this group at https://groups.google.com/group/anss-aqms.
> To view this discussion on the web visit https://groups.google.com/d/msgid/anss-aqms/CALsXm6X%3DVtHYEdN4X56cta1qKfo0T91dSQLwMjC3h8MNHtGdrg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

[Paul Friberg]

Thanks Pete, I think Renate will look it over so we can get it all going in Gitlab.com shortly.

Enjoy your holiday!

Paul

To view this discussion on the web visit https://groups.google.com/d/msgid/anss-aqms/23829.17117.949381.158180%40gargle.gargle.HOWL.

For more options, visit https://groups.google.com/d/optout.

[Gee, Lind]

Have a great trip!

Thanks.

Lind

Lind S. Gee
U.S. Geological Survey
345 Middlefield Road - MS 977
Menlo Park, CA 94025

lg...@usgs.gov
650-329-5656
650-329-4732 fax

To view this discussion on the web visit https://groups.google.com/d/msgid/anss-aqms/23829.17117.949381.158180%40gargle.gargle.HOWL.