assocaro 
Logical Entity Name  assocaro 
Default Table Name  assocaro 
Definition  Data associating arrivals with origins 

assocaro Attributes 
Attribute/Logical Rolename  Domain  Datatype  NULL  Definition 
orid(PK)(FK)    NUMERIC(15, 0)  NO  Origin identification. Each origin is assigned a unique positive integer which identifies it in the database. The orid is used to identify one of the many hypotheses of the actual location of the event 
arid(PK)(FK)    NUMERIC(15, 0)  NO  Arrival identifier. Each arrival is assigned a unique positive integer identifying it. This number is used in the AssocArO relation along with the origin identifier to link Arrival and Origin 
commid    NUMERIC(15, 0)  YES  Comment identification. This is a key used to point to free-form comments entered in the Remark relation. These comments store additional information about a tuple in another relation. Within the Remark relation, there may be many tuples with the same commid and different lineno, but the same commid will appear in only one other tuple among the rest of the relations in the database 
auth    VARCHAR(15)  NO  The auth field specifies the source of the information. This may be a network identifier (FDSN or otherwise), or any other string indicating the source of the information in the record 
subsource    VARCHAR(8)  YES  A second identifier to specify the system or process that derived the data. e.g., the origin's AUTH is CI, but the subsource (the solution) was computed by JIGGLE 
iphase    VARCHAR(8)  YES  Reported phase. This eight-character field holds the name initially given to a seismic phase. Standard seismological labels for the types of signals (or phases) are used (e.g., P, PKP, PcP, pP). Both upper and lower case letters are available and should be used when appropriate, for example, pP or PcP 
importance    NUMERIC(2, 1)  YES  This attribute denotes the importance of a phase/amplitude reading towards an origin/magnitude. 0.0 means no importance, 1.0 implies extremely important 
delta    NUMERIC(5, 1)  YES  Source-receiver distance. This attribute is the arc length, over the earth’s surface, of the path the seismic phase follows from source to receiver. The location of the origin is specified in the origin record referenced by the attribute orid. The attribute arid points to the record in the Arrival relation that identifies the receiver. The value of the attribute can exceed 180 degrees, it can even exceed 360 degrees, the geographic distance between source and receiver is delta mod(180) 
seaz    NUMERIC(4, 1)  YES  Station to event azimuth. This attribute is calculated from the station and event locations. It is measured clockwise from North 
in_wgt    NUMERIC(4, 3)  YES  Input weight 
wgt    NUMERIC(4, 3)  YES  Location weight. This attribute gives the final weight assigned to the allied arrival by the location program. It is used primarily for location programs that adaptively weight data by their residuals 
timeres    NUMERIC(5, 2)  YES  Time residual. This attribute is a travel time residual, measured in seconds. The residual is found by taking the observed arrival time (saved in the Arrival relation) of a seismic phase and substracting the expected arrival time. The expected arrival time is calculated by a formula based on earth velocity model, an event location and origin time, the distance to the station, and the particular seismic phase 
azres    NUMERIC(5, 3)  YES  Azimuth residual. This is the difference between the measured station-to-event azimuth for an arrival and the true azimuth. The “true” azimuth is the bearing to the inferred event origin 
emares    NUMERIC(5, 3)  YES  Emergence angle residual. This attribute is the difference between an observed emergence angle and the theorical prediction for the same phase, assuming an event location as specified by the accompanying orid 
slores    NUMERIC(8, 4)  YES  Slowness residual. This attribute gives the difference between an observed slowness (saved in the Arrival relation) and a theorical prediction. The prediction is calculated for the related phase and event origin described in the record 
vmodelid    NUMERIC(3, 0)  YES  Velocity model identification 
scorr    NUMERIC(6, 4)  YES  Station correction 
sdelay    NUMERIC(7, 4)  YES  Station delay 
rflag    VARCHAR(2)  YES  This flag describes whether an observation was generated automatically, by a human, or has been finalized 
ccset    VARCHAR(1)  YES  This field describes whether the clock correction has been added or applied to the arrivals in computing a hypocenter solution 
lddate    DATE  YES  Load date. Date and time that the record was created or last modified, in Oracle date datatype 

assocaro Relationships 
Parent Entity  Child Entity  Type  Foreign Keys 
arrival  assocaro  Identifying  arid 
origin  assocaro  Identifying  orid 
remark  assocaro  Non-Specific   

assocaro Check Constraints 
Check Constraint Name  CheckConstraint 
assocaro01  azres >= -180.0 and azres <= 180.0 
assocaro02  delta >= 0.0 
assocaro03  emares >= -90 and emares <= 90 
assocaro04  importance >= 0.0 and importance < 1.0 
assocaro05  seaz >= 0.0 and seaz <= 360.0 
assocaro06  slores >= 0.0 
assocaro07  timeres >= 0.0 
assocaro08  wgt >= 0.0 and wgt <= 1.0 
assocaro09  ccset < 1 
assocaro10  rflag in ('a','h','f','A','H','F')