1.- Requests #104 & #105 (D. Oppenheimer - PENDING): ==================================================== ----------------------------------------------------------------- --> Expand "event types" definitions. --> Add "ecategory" field. ----------------------------------------------------------------- ------------------------------------------------------------------------ The "EventType" table contains the categories that an event type belong to as well as a general description of the type. CREATE TABLE "EventType" ( "etype" VARCHAR2(7) NOT NULL, "category" VARCHAR2(25) NOT NULL, "description" VARCHAR2(80) NULL ); No list constraints (this is a reference table which allows future expansion). Key = etype, category This allows an etype to exist in multiple categories, e.g. we can create a "volcanic" category that groups tremor, tornillo, lp events, & eruption while allowing lp events to remain in the "earthquake" category as well. Continue use of 2-char etypes, they are seldom seen by people and leaving them 2-char won't upset existing output formats. - Example contents of EventType: etype Description Category ------------------------------------------------------ th thunder atmospheric sn sonic blast atmospheric co mine/tunnel collapse earth movement av debris avalanche earth movement ls landslide earth movement rb rock burst earth movement rs rockslide earth movement ve volcanic eruption earth movement le local earthquake earthquake lp long period volcanic earthquake earthquake re regional earthquake earthquake se slow earthquake earthquake ts teleseismic earthquake earthquake ce calibration explosion explosion ex chemical explosion explosion nt nuclear test explosion qb quarry blast explosion sh refraction/reflection shot explosion bc building collapse impact mi meteor impact impact pc plane crash impact vt tornillo (volcanic tremor) tremor/tornillo tr non-volcanic tremor tremor/tornillo st subnet trigger unknown uk unknown event unknown ot other unknown - Notes: * Codes can get a list of valid etypes with: SELECT DISTINCT etype FROM EventType; * Codes can get a list of valid categories with: SELECT DISTINCT category FROM EventType; * To select events for a particular etype, e.g. 'le': SELECT FROM Event WHERE etype = 'le'; * To select events for a particular category, e.g. 'explosion': SELECT FROM Event WHERE etype IN (SELECT etype FROM EventType WHERE category = 'explosion'); ------------------------------------------------------------------------ ------------------------------------------------------------------------ ==> Follow up issue with Peggy (tornillo vs tremor). Allan to send new etypes (snow, ice). Ellen to come up with new table structures. Fixed parameters should go into a different table (AP schema). ------------------------------------------------------------------------ 2.- Request #120 (D. Given - NEW): ================================== ----------------------------------------------------------------- --> Add new CubeMessageText table to application schema. Cube message codes need site-specific info to compose event emails. This is used by the Java HeaderMessage and CubeFormat classes. ----------------------------------------------------------------- ------------------------------------------------------------------------ ==> Discussed. Doug G. to send table structure; could be approved via email. Doug N. does not like the table name. ------------------------------------------------------------------------ 3.- Request #119 (E. Yu - NEW): =============================== ----------------------------------------------------------------- --> Remove amp02 constraint (amplitude > 0) from amp table. Paul Friberg has asked this constraint be disabled on HVO servers. I am wondering if this should apply to SCEDC/NCEDC as well. According to Paul, the meaning of a negative amplitude is fabs() was not run on it. ----------------------------------------------------------------- ------------------------------------------------------------------------ ==> Discussed. Ellen to go back to Paul for more information. ------------------------------------------------------------------------ 4.- Request #10 (D. Given - PENDING): ===================================== ----------------------------------------------------------------- --> Add new column "nread" to NETMAG table. ----------------------------------------------------------------- ------------------------------------------------------------------------ Every magnitude in the dbase has an attribute called "NSTA". Most programs write the number of *observations* (amps, codas) contributing to the magnitude in this field. One program (TriMag) writes the number of *stations*. So the field name doesn't match its most common usage. This will be confusing to future developers. The WG considered just changing TriMag to write # of observations and leaving the misleading column name (NSTA) as it is. This may cause difficulties as the software propagates out to other networks. The WG is now proposing to "fix" the situation by doing the following: * add a new field called NOBS for # observations * retroactively rewrite NSTA and populate NOBS in the dbase to reflect this change * change all codes to use the new NOBS field and interpret NSTA as # stations This change would require changes to several codes. For example, TriMag, data import and load programs, Jiggle, STP, dbselect, EWmag2CISN, magPref package, alarm rules, and more. QUESTION: Do you think it is worth the effort to change the code to fix the 'misnamed' NSTA field and record both the number of observations and the number of stations? ------------------------------------------------------------------------ 5.- Request #19 (D. Given - PENDING): ===================================== ----------------------------------------------------------------- --> Add "timequality" to WAVEFORM. Need to store waveform time quality (Currently must retrieve SEED timeseries data and read headers to get this info). ----------------------------------------------------------------- ------------------------------------------------------------------------ Doug G. to go back to Egill for more information. ------------------------------------------------------------------------