1.- Review of pending requests: =============================== 1.1.- Request #135 (J. Pechmann): --------------------------------- --> Arrival table FM column constraint: allow lower quality first motions to be specified as "+","-". ----------------------------------------------------------------- ==> Approved. High quality (c,d); Low quality (+,-). Add c,d,+,- to the constraint & enforce it. Update jiggle,hypophasedump,fprun,dbselect,stp,quakeML & Mung. ----------------------------------------------------------------- ----------------------------------------------------------------- ==> Jiggle & dbselect were updated. - Update documentation. ----------------------------------------------------------------- 1.2.- Request #134 (A. Walter): ------------------------------- --> Use Coda table's IPHASE column, or rename it, to store a character key mapped to a lookup table. When not null, flag value indicates how tau column value was derived. ----------------------------------------------------------------- ==> Discussed. Allan to bring up issue with Standards group. Ask Dave O. about station shadow format. Is there any reason to discriminate between P & S? What is the meaning of Coda.iphase? ----------------------------------------------------------------- ----------------------------------------------------------------- ==> Withdrawn. After feedback from Standards group, there is no real active support for this request. - Update documentation with CNSS Table 15: duration type: P -> P-wave S -> S-wave ----------------------------------------------------------------- 1.3.- Request #131 (E. Yu): --------------------------- --> Store categories of applications in an AppCategory and AssocAppCat table (similar to event types). ----------------------------------------------------------------- ==> Ellen sent a link to a GUI. People to look at it and come back with some feedback. http://jishin.gps.caltech.edu/sis/stations/appcatg/ ----------------------------------------------------------------- 1.4.- 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 - Ellen is working on an application to populate the Cosmos schema main table. ----------------------------------------------------------------- 1.5.- Request #128 (S. Zuzlewski): ---------------------------------- --> Allow NULL for Amp.datetime. ------------------------------------------------------------------------ Amplitude times in the database are only approximations and therefore are not reliable. Affected readings are: - NC WA amplitudes readings from pre-CISN software. - ALL CISN SGM spectral acceleration times imported from CISN partners. ==> Approved. After seeking guidance from the Standards group, the following was approved: - Allow NULL values in the Amp.datetime field and make use of the existing fields 'wstart' (Window start) and 'duration' to represent respectively the approximate time and its associated error. * For each amplitude where we know the time and the window (ex: current RT): We can set all the fields (datetime, wstart, duration). * For each amplitude where we know the time but not the window: Amp.datetime = Amp.wstart Amp.duration = 0 * For each amplitude where we don't know the time nor the window: Amp.datetime = NULL Amp.wstart = Amp.duration = NULL - Action Items: * Caltech will use 'wstart' to partition the Amp table. * Pete will look at affected RT apps (trimag, ampgen). * Allan will look at PP (jiggle, ampgen_pp, hypomag) & SGM import apps. * Each DC will look at its historic data and update appropriately the Amp fields datetime, wstart & duration. * Databases: - Remove NOT NULL constraint on Amp.datetime. - Add NOT NULL constraint to Amp.wstart. * RT apps: - datetime: actual time of pick. - wstart: start of window. - duration: filling in. - Need to be changed to use the correct API's (nominal vs. true). * PP apps: - Need to update gmp2db & db2gmp. - NC added the datetime constraint. Wstart constraint cannot be added yet because some values are NULL. - Pete checked/updated RT apps. Allan checked/updated PP apps. SGM import apps are waiting for the new version of the SGM packets. - Everybody is sending the new version of the SGM packets except for CGS. - Pete & Stephane came up with a plan to update historic data in NC. - DB historic updates done in NC (except for SGM). ----------------------------------------------------------------- 1.6.- Request #10 (D. Given): ----------------------------- --> Add new column "nobs" to NETMAG table. ------------------------------------------------------------------------ ==> Request has been approved. - This change has eventual implications for the following applications: Trimag, EC, Jiggle, MT, dbselect, Stored Procedures, STP(SC), RTMd(SC). - Ellen tested and documented a procedure to perform a DDL operation in a replication environment. - Ellen used the procedure to add the new field in SC. - Allan updated Jiggle & the stored procedures. - NC added the new field to its production databases. - Historic data need to be updated in the database. - Pete updated trimag, EC & TMTS. New version of dbselect cannot be installed until historic data is corrected. - No change is needed for STP. - Allan will implement a stored procedure to update historic data. ------------------------------------------------------------------------ 1.7.- Request #130 (S. Zuzlewski): ---------------------------------- --> AppChannels vs Config_Channel. ------------------------------------------------------------------------ Issue of config_channel/program tables use by RT programs and applications/appchannels by post proc. We should ideally create one set of tables and both should use the same set. It will simplify the schema, and avoid the confusion of what tables to populate for program's channel lists. - In NC, Pete created a script to reconfigure channel list Id's and names. Also Config_Channel is now a view of AppChannels and Program a synonym of Applications. - Ellen sent a link to a GUI interface to better manage channel lists. * Test interface with NC data: http://surtsey.gps.caltech.edu/stationui/sandbox/ * Read-only interface with SC data: http://surtsey.gps.caltech.edu/stationui/readonly/ ----------------------------------------------------------------- 1.8.- Request #129 (S. Zuzlewski): ---------------------------------- --> Add hardware ownership information. ------------------------------------------------------------------------ We want to add hardware ownership information to the HT schema in order to identify which piece of hardware belongs to whom (similar to the 'owners' table in SIS). It would require a new table: ownerid int (PK) name string contact string lddate date We would then add the field 'ownerid' as a foreign key in the Sensor, Filamp & Datalogger tables. - D. Given pointed out that contact information can change often. NC to discuss some more about it. - Currently waiting on ANSS looking at SIS. ------------------------------------------------------------------------