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 |  | 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 |  | 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(4, 3) | 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(9, 4) | 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.
seaz |  | NUMERIC(4, 1) | YES | Event to station azimuth. This attribute is calculated from the event and station locations. It is measured clockwise from North
in_wgt |  | NUMERIC(4, 3) | YES | Input weight. Hypoinverse station archive card columns 17 & 50: 0, 1, 2, 3 --> 1.00 4, 5, 6, 7, 8, 9 --> 0.00
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. Raw values from hypoinverse columns 39 & 64
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
ema |  | NUMERIC(5, 2) | 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
slow |  | 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, in Oracle date datatype

assocaro Keys

Key Name | Key Type | Keys
assocarokey01 | PrimaryKey | orid, arid

assocaro Relationships

Parent Relationships:

Entity Name | Type | Cardinality | Business Name | VerbPhrase | InversePhrase | Foreign Keys | Is Supertype
arrival | Identifying | One To Zero or More |  |  |  | arid | NO
origin | Identifying | One To Zero or More |  |  |  | orid | NO
remark | Non-Specific |  |  |  |  |  | NO

Child Relationships:

Entity Name | Type | Cardinality | Business Name | VerbPhrase | InversePhrase | Foreign Keys | Is Subtype

assocaro Check Constraints

Check Constraint Name | CheckConstraint
assocaro02 | delta >= 0.0
assocaro03 | ema >= 0 and ema <= 180
assocaro04 | importance >= 0.0 and importance < 1.0
assocaro05 | seaz >= 0.0 and seaz <= 360.0
assocaro06 | slow >= 0.0
assocaro07 | timeres >= 0.0
assocaro09 | ccset < 1
assocaro10 | rflag in ('a','h','f','A','H','F')