SourceSpec Event File
The SourceSpec Event File format is a custom format, based on YAML, which allows specifying the source properties for one ore more given events. The following properties can be specified:
event_id
(mandatory): the event ID.Note
This field must be preceded by a dash (
-
).name
(optional): the event namehypocenter
(mandatory): hypocentral location and origin timemagnitude
(optional): the event magnitude (used whenMw_0_from_event_file
in the Configuration File is set toTrue
)Note
If a scalar moment or a moment tensor is given, a Mw magnitude will be (re)computed from it.
scalar moment
(optional): event scalar moment (used whenMw_0_from_event_file
in the Configuration File is set toTrue
)Note
If a moment tensor is given, the scalar moment will be (re)computed from it.
focal_mechanism
(optional): event focal mechanism (used for computing radiation pattern when the optionrp_from_focal_mechanism
in the Configuration File is set toTrue
).Note
If a moment tensor is given, the focal mechanism will be (re)computed from it.
moment_tensor
(optional): event moment tensor (used for computing focal planes and radiation pattern when the optionrp_from_focal_mechanism
in the Configuration File is set toTrue
; also used for computing moment magnitude, to be used whenMw_0_from_event_file
is set toTrue
)
See the sample SourceSpec Event File below for more details on the format.
Sample SourceSpec Event File
A sample SourceSpec Event File can be obtained through the command:
source_spec --samplesspevent
or
source_spec -y
The content of the sample SourceSpec Event File is shown below:
# SourceSpec Event File
#
# One or more events can be defined in this file.
# Each event must have a unique "event_id".
# Each event description starts with a dash (-) and is followed by a mandatory
# "event_id" field. The "hypocenter" field is mandatory, all the other fields
# are optional.
# Optional fields can be empty or commented out.
# The indentation of the fields must be respected.
#
# For a minimal working file, replace the placeholders between "<" and ">" with
# the appropriate values.
#
# This is a YAML file. For more information on the format, see
# https://en.wikipedia.org/wiki/YAML
# Mandatory event_id, preceded by a dash (-)
- event_id: <EVENT_ID>
# Optional event name
name:
# Mandatory hypocenter information
hypocenter:
longitude:
value: <LONGITUDE>
# currently, only decimal degrees are supported
units: deg
latitude:
value: <LATITUDE>
# currently, only decimal degrees are supported
units: deg
depth:
value: <DEPTH>
# units can be one of the following: km, m
units: km
origin_time: <ORIGIN_TIME>
# Optional magnitude value.
# If a scalar moment or a moment tensor is given, a Mw magnitude will be
# (re)computed from it
magnitude:
value:
# magnitude type is a free string, e.g. Mw, mb, Ms, etc.
mag_type:
# Optional scalar moment.
# If a moment tensor is given, the scalar moment will be (re)computed
# from it
scalar_moment:
value:
# units can be one of the following: N-m, dyne-cm
units:
# Optional focal mechanism, in terms of strike, dip and rake (in degrees)
# of one of the two focal planes.
# If a moment tensor is given, the focal mechanism will be (re)computed
# from it
focal_mechanism:
# currently, only decimal degrees are supported
units: deg
strike:
dip:
rake:
# Optional moment tensor, in up-south-east convention (USE)
moment_tensor:
# units can be one of the following: N-m, dyne-cm
units:
# moment tensor components, in moment units defined above
m_rr:
m_tt:
m_pp:
m_rt:
m_rp:
m_tp:
# You can specify as many events as you want, as long as they have unique
# event_id's
# - event_id: <EVENT_ID2>
# hypocenter:
# longitude:
# value: <LONGITUDE2>
# units: deg
# latitude:
# value: <LATITUDE2>
# units: deg
# depth:
# value: <DEPTH2>
# units: km
# origin_time: <ORIGIN_TIME2>
# etc...