assocamm

Logical Entity Name | assocamm
Default Table Name | assocamm
Definition | Data associating amplitudes with magnitudes

assocamm Columns

ColumnName | Domain | Datatype | NULL | Definition
magid |  | NUMBER(15, 0) | NO | Magnitude identifier. This key is used to identify a magnitude in the Netmag relation. It is required for every magnitude
ampid |  | NUMBER(15, 0) | NO | Amplitude identification. Each amplitude is assigned a unique positive integer identifying it. This number is used in the AssocAmO relation along with the origin identifier to link Amp and Origin. This number is used also in the AssocAmM relation along with the magnitude identifier to link Amp and Netmag
commid |  | NUMBER(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 |  | VARCHAR2(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 |  | VARCHAR2(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
weight |  | NUMBER(4, 3) | YES | Magnitude weight
in_wgt |  | NUMBER(4, 3) | YES | Input weight
mag |  | NUMBER(5, 2) | YES | Magnitude for this station reading
magres |  | NUMBER(5, 2) | YES | Magnitude residual
magcorr |  | NUMBER(5, 2) | YES | Magnitude correction for this channel
importance |  | NUMBER(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
rflag |  | VARCHAR2(2) | YES | This flag describes whether an observation was generated automatically, by a human, or has been finalized
lddate |  | DATE | YES | Load date. Date and time that the record was created, in Oracle date datatype

assocamm Primary and Unique Keys

Key Name | Key Type | Keys
assocammkey01 | PrimaryKey | magid, ampid

assocamm Foreign Keys

Parent Relationships:

Table Name | Type | Cardinality | Constraint Name | VerbPhrase | InversePhrase | Foreign Keys | Is Supertype | Deferrable | Initially Deferred
amp | Identifying | One To Zero or More | Aam_Amp |  |  | ampid | NO | NO | NO
netmag | Identifying | One To Zero or More | Aam_Net |  |  | magid | NO | NO | NO

Child Relationships:

Table Name | Type | Cardinality | Constraint Name | VerbPhrase | InversePhrase | Foreign Keys | Is Subtype | Deferrable | Initially Deferred

assocamm Check Constraints

Check Constraint Name | CheckConstraint
assocamm01 | mag >= -10.0 and mag <= 10.0
assocamm02 | magcorr >= -10.0 and magcorr <= 10.0
assocamm03 | magid > 0
assocamm05 | weight >= 0.0 and weight <= 1.0
assocamm06 | in_wgt >= 0.0 and in_wgt <= 1.0
assocamm07 | importance > 0.0 and importance <= 1.0
assocamm08 | rflag in ('a','h','f','A','H','F')