1.- Pending schema change requests: =================================== #60 (P. Lombard): Units table: "integral of velocity squared" is not a meaningful description. ----------------------------------------------------------------- Several different length and time combinations could be used for "integral of velocity squared". Is the velocity in cm/sec, or m/sec? Is the integral with respect to time, or distance? ----------------------------------------------------------------- ------------------------------------------------------------------------ ==> Discussed. Caltech tasked to find out what are the exact units. One option is to ask Hiroo Kanamori. ------------------------------------------------------------------------ #116 (S. Zuzlewski): Add table ProxyWsMap. ----------------------------------------------------------------- A new table ProxyWsMap needs to be added in order to use the proxy wave server. The table has the following structure: CREATE TABLE ProxyWsMap ( net VARCHAR2(8) NOT NULL, sta VARCHAR2(8) NOT NULL, seedchan VARCHAR2(8) NOT NULL, location VARCHAR2(8), wstype VARCHAR2(15) NOT NULL, wsgroup VARCHAR2(15) NOT NULL, datetime_on NUMBER(25,10) NOT NULL, datetime_off NUMBER(25,10) NOT NULL, lddate DATE DEFAULT (SYSDATE) NOT NULL ); ----------------------------------------------------------------- ------------------------------------------------------------------------ ==> Discussed. Doug G. proposed to use the AppChannels table rather than creating a new one. Pete L. to look into this idea. ==> Refused. AppChannels & Application tables will be used instead. ------------------------------------------------------------------------ 2.- New schema change requests: =============================== #118 (A. Walter): Add datetime_on number column to magprefpriority table. ----------------------------------------------------------------- Historic events need different magnitude priority criteria than used for recent events (e.g. the acceptable minimum reading count), thus we need a date to delimiter. ----------------------------------------------------------------- ------------------------------------------------------------------------ ==> Approved. Fields datetime_on & datetime_off will be added to the MagPrefPriority table. ------------------------------------------------------------------------ #117 (E. Yu): Change length of station_data.staname to varchar2(60) from varchar2(50). ----------------------------------------------------------------- In southern California station_data.staname is mapped to blockette 50's field 9 (Site name). This field in SEED format is 60 characters in length. We would like station_data.staname to match this length. ----------------------------------------------------------------- ------------------------------------------------------------------------ ==> Approved. Field Station.staname will be increased as well. ------------------------------------------------------------------------ #102 (S. Zuzlewski): Increase AssocArO.importance precision. ----------------------------------------------------------------- The AssocArO.importance has currently a datatype of F2.1. We are populating this field with hypoinverse station archive columns 101 (Importance of P arrival) & 105 (Importance of S arrival) and they are defined as F4.3. This means that any "importance" less than 0.05 maps to 0 in the F2.1 format, which gives the impression that the reading was not used. The proposal is to increase the field's precision to F4.3. ----------------------------------------------------------------- ------------------------------------------------------------------------ ==> Approved. Field AssocAmM.importance will be updated as well. ------------------------------------------------------------------------ #99 (D. Given): Clarify meaning of Netmag.Uncertainty. ----------------------------------------------------------------- Doc says: "Magnitude uncertainty. This is the standard deviation of the accompanying magnitude measurement". Jiggle has been writing the stddev. Everything else (CUSP, Hypoinverse) seems to use median absolute Difference or MAD. I don't know what the RT system does. Suggestion: change Jiggle to write MAD and change the schema doc wording. ----------------------------------------------------------------- ------------------------------------------------------------------------ ==> Approved. Jiggle actually does write the MAD. A. Walter to come up with a definition: "Netmag.uncertainty is the median of the absolute values of the channel magnitude residual deviations from the channel magnitude's median, the summary magnitude." ------------------------------------------------------------------------ 3.- Possible use of SVN for tracking schema related documentation: ================================================================== * DDL scripts (SQL): a) Schema creation (PI,WF,HT,IR,SIS): - Should we just store the logical model of the schemas? NC & SC physical models are different. b) Alternate tables (RT, post processing): - Does SC already store them in svn? - NC should do the same (ChannelMap, AssocWfRc, ...). c) Views: - NC & SC have different versions of some views (md_magparms_view, ...). d) Packages: - Does SC already store them in svn? - Berkeley should do the same (Truetime, ...). * ER/Studio files (HTML). ------------------------------------------------------------------------ 2008/03/21 We decided in a 1st pass to store only the logical views of the DDL scripts. Ellen volunteered to come up with a draft for the SVN structure. 2008/04/25 Ellen came up with a strawman for the repository structure. ----------------------------------------------------------------- I just spoke with Rae Yip concerning using SVN to store the database creation scripts. Rae tells me that the scope of this SVN repository is to store source code and not site-specific configurations. So it seems that we would only check scripts concerning relational properties (and not physical or table properties) into this repository. Here is a strawman for these scripts. Current SVN repository structure for database scripts: DB ->trunk ->branches (there is a leap second dev branch - currently only storedprocedures is under this branch) Under "->trunk" ->storedprocedures ->tables ->types ->views ->snapshots Other scripts that are site-specific: 1. sequences 2. users 3. grants 4. table site-specific storage parameters ----------------------------------------------------------------- 2008/05/30 Ellen started copying over core schema tables into SVN. ----------------------------------------------------------------- I've started checking table creation scripts into SVN - DB/trunk. These scripts are based on the work to make the CISN build and have no references to tablespace names. I'll try to keep the cisn-commit emails to a minimum. I'm making subdirectories under tables for each of the schema groups we have - parametric, waveform, hardware tracking, application, instrument response. Allan Walter had checked in a number of table creation scripts in the past directly under "trunk", I'll touch base with him about moving those scripts to the correct subdirectory. ----------------------------------------------------------------- 2008/07/11 Ellen copied all of the core tables into SVN. However, some of the tables are SC specific and don't reflect the SCWG approved requests. The group agreed that the version of the tables in SVN should reflect all of the approved changes, regardless of whether those changes have been implemented in NC or SC. ------------------------------------------------------------------------