1.- New Requests: ================= 1.1.- Request #139 (S. Zuzlewski): ---------------------------------- ----------------------------------------------------------------- --> Integration of double difference hypocenters - We propose to update the following type in the Origin.Type field: H --> Hypocenter (with phases). And also to add the following new type: D --> Hypocenter (double difference). - We propose adding a new table EventPrefOrigin: EVID Event Identifier ORID Origin Identifier TYPE Origin Type LDDATE Load Date This new table specifies the preferred origin of a given type for an event. * In the case where a double difference origin is preferred for a event, applications such as jiggle will need to query the EventPrefOrigin table in order to retrieve the preferred origin that has phases associated with it (type 'H'). * It has been suggested that the Origin.algorithm field could be used to track the double-difference type (DD, DDRT): DD - DD base catalog using traditional DD. DDRT - The DDRT algorithm solution. * Another suggestion is to use the Origin.subsource field to store the DD base catalog version (for example DD200912.1). * This proposal does not encompass the computational information that was used to produce the DD origin. Extra fields will be required in order to store this information. ----------------------------------------------------------------- ----------------------------------------------------------------- ==> Approved. ----------------------------------------------------------------- 1.2.- Request #140 (A. Walter): ------------------------------- ----------------------------------------------------------------- --> Adding station delay corrections to the database Right now the station delay corrections are obtained from flat files put in the solserver's hypoinverse directory setup. However, it might be worth discussing the topic as to whether or not this kind of data should also be available from the database, and if so, whether a new table is needed to map delays to a specific location application and velocity model instance etc. One option is to add a new "corr_type" to the StaCorrections table, which is probably better than creating a separate new table for station traveltime delays. ----------------------------------------------------------------- 2.- Review of pending requests: =============================== 2.1.- Request #53 (D. Given): ----------------------------- --> Add integer attribute for each channel to hold COSMOS "Table 6" value. ------------------------------------------------------------------------ ==> Allan sent a new version of the Cosmos schema. - Stephane loaded the Cosmos schema on a test database and updated createv0_xml to use those tables. Other applications could benefit from those tables. For example: v02mseed, Shakemap. - NC & SC will start writing an application to populate the main table (C_ChannelData) for their respective networks. - Stephane updated the tables with new values from the Cosmos documentation. Sent out new version of the schema. - Stephane sent an initial spreadsheet for BK sites to Peggy. Outstanding issue concerning borehole sites. - Tony said that code 52 should be used for boreholes. - SC will go through their site codes. Current SC algorithm for assigning site codes: IF depth < 10 m THEN 4 ELSE 52 - Stephane started working on an application to populate the Cosmos schema main table. ==> Needs mapping between SEED SNCL & CGS S# C#. Pete proposed to add 2 fields to C_Channel_Data table: * Channel number. * Channel location description. Needs input from CGS. Resume discussion in DIWG. ==> Kick this request to DIWG. Who is responsible for the mapping? Engineers who designed the layout of the sensors should assign channel numbers. ------------------------------------------------------------------------