sceval¶

gempa module to evaluate the goodness of origins setting the origin status or comments

Description¶

sceval provides multiple evaluation methods to identify and to flag real and fake origins or to identify origins that have particular properties. Flagging is achieved by changing the origin status. Comments are set to document properties and the method. Origins from real and fake events are flagged as confirmed and rejected, respectively. Origins that cannot be flagged by one of the evaluation methods are kept unflagged.

sceval also provides the plugin evsceval for scevent [4] for evaluating origin comments and status.

Evaluation Methods¶

Various evaluation methods evaluate the quality of the origins setting either the status of the origin or adding a comment to the origin. The comment can be evaluated by scevent [4] using the plugin evsceval. The plugin is provided by the sceval package.

The origin evaluation is performed in the following order:

minPhase: Number of used phases below threshold, set the origin status.
minDepth: Minimum depth, set the origin status.
maxDepth: Maximum depth, set the origin status.
maxRMS: Maximum RMS, set the origin status.
minPhaseConfirm: Number of used phases reached threshold, set the origin status.
maxGap: Maximum azimuthal gap, add an origin comment
Station - distance evaluation: set the origin status (main evaluation method).
Extended gap criterion: set the origin status.

Phases, hence arrivals, are considered used when any parameter of pick time, slowness or backazimuth is used.

The evaluation methods set the status of an origin to confirmed or to rejected or add a comment to the origin. If the method neither allow confirmation or rejection, the origin status remains unchanged. The evaluation is finished when one method explicitly declares the status of an origin. Only the extended Gap check may re-evaluate origins after the station - distance evaluation. The re-evaluation by the extended Gap check allows to confirm origins which where rejected before. Such origins are typically found in remote areas, e.g. mid-ocean ridges.

Figure 1: Methods for origin evaluation.¶

By default manually processed origins are excluded from evaluation. Manually processed origins can be explicitly evaluated by setting the origin.manual parameter.

For evaluation of origins by their arrivals only arrivals with weight > 0 are considered.

minPhase: Minimum number of used phases¶

Declares: rejection

An origin is rejected if the number of used phases (arrivals) is less than minPhase. Unused phases, i.e. phases with zero weight, are not counted.

minPhase may be over-ruled by distanceProfilesMinPhase: Unless distanceProfilesMinPhase <= 0, the test is skipped if the number of used phases >= distanceProfilesMinPhase allowing for the station - distance evaluation.

Background¶

Setting minPhase allows locator tools such as scautoloc [2] or scanloc [1] to publish origins with only few arrivals. Those origins can be later safely rejected by sceval but are kept in the database for manual evaluation.

minDepth: Minimum origin depth¶

Declares: rejection

An origin is rejected if the depth of the origin is less than minDepth.

maxDepth: Maximum origin depth¶

Declares: rejection

An origin is rejected if the depth of the origin is larger than maxDepth.

Background¶

Seismic networks sometimes detect teleseismic phases from large events. The location from such detections may result in very deep events. The same is true for networks monitoring mines or blasts. Those origins can be later safely rejected by sceval but are kept in the database for manual evaluation.

maxRMS: Maximum RMS residual¶

Declares: rejection

An origin is rejected if the RMS residual of the origin is larger than maxRMS.

Background¶

Large RMS residuals may be indicative of low-quality origins. While modules like scautoloc [2] or scanloc [1] check the RMS as a quality measure before sending an origin others may not do so. Origins with large RMS can be safely rejected by sceval but are kept in the database for later evaluation.

minPhaseConfirm: Number of used phases reaches a threshold¶

Declares: confirmation

An origin is confirmed if the number of used phases (arrivals) is equal or larger than minPhaseConfirm. Unused phases, i.e. phases with zero weight, are not counted.

Background¶

The methods applies to areas with dense station coverage but variable data quality. It usually happens that origins with few arrivals nearby the event are confirmed by the Station - distance evaluation. If the event is large enough it may be recorded at more distance stations with sufficiently low background noise while others with higher noise at similar distance do not provide detections. In such cases sceval may not confirm such origins and scevent [4] may prefer the confirmed origin with viewer arrivals over the origin with more arrivals. However, if the number of arrivals is large, you may wish to safely confirm an origin. Set minPhaseConfirm sufficiently high and according to the network layout and quality to cope with such situations.

maxGap: Maximum azimuthal gap¶

Declares: property - sets the comment maxGap.

Origins receive the comment “maxGap” if the maximum azimuthal gap exceeds maxGap. The comment is evaluated by scevent [4] if the plugin evsceval loaded.

Background¶

The maximum azimuthal gap is the largest azimuthal distance between two neighboring stations with respect to the origin. The stations are sorted by their azimuth (Figure: Gap criterion).

Station - distance evaluation¶

Declares: rejection or confirmation

The station - distance evaluation is only performed if distanceProfiles contains at least one valid profile and if the origin has a higher number of arrivals with non-zero weight than distanceProfilesMinPhase. sceval currently only evaluates stations that have P-wave arrivals.

The number of available stations within configurable distance intervals are compared with the number of stations that have picked arrivals of P waves associated to the tested origin. The distance intervals and the weights for the intervals are given by distanceProfile.$name.weights.

Background¶

For real origins, thus real seismic events, the number of arrivals typically decreases with distance as compared to the number of available stations (Figure: real event).

Example of an origin for a real seismic event with number of available stations, picks (arrivals) and the distance-dependent weights (distanceProfile.$name.weights).

For fake origins, distant stations may have a proportionally higher number of arrivals as compared to close stations (Figure: fake event).

Example of a fake origin with number of available stations, picks (arrivals) and the distance-dependent weights (distanceProfile.$name.weights).

Based on the distance profile a mismatchScore is computed and compared against limits in order to origins confirm as real seismic events or to reject origins. For a mismatchScore lower or equal to mismatchScore.confirmed, the origin is flagged confirmed. For a mismatchScore lower or equal to mismatchScore.rejected, the origin is flaged rejected.

It is expected that closer stations have a higher chance to detect real earthquakes thus have a higher chance to have arrivals.

The mismatchScore is therefore calculated as a distance-dependent weighted mismatchScore comparing the number of available stations with the number of stations that have arrivals in a weighted scheme.

$mismatchScore =\ &\frac{\sum_{i=1}^{10}weight_i*\frac{stationCount_i - arrivalCount_i}{stationCount_i}}{\sum_{i=1}^{10}weight_i}$

where

i is the index over the intervals within the configurable distance range,
stationCount is the number of available stations,
arrivalCount is the number of associated arrivals and
weight is the configurable weight (distanceProfile.$name.weights)

within a defined distance interval.

Setup¶

Distance-dependent weight profiles for distances less than distanceProfile.$name.max can be defined and included by the profile name given using distanceProfiles.

The usage of the distance-dependent weight profile is controlled by the largest epicentral distance of stations with P phase picks for a considered event. The profile among all profiles is used that has the smallest distanceProfile.$name.max that is larger than the largest epicentral distance. If the largest epicentral distance is larger than the largest distanceProfile.$name.max from all available profiles, then the default profile is used as non-configurable fallback.

Note

Parameters of the default profile:

distanceProfile.$name.max = 180.0
distanceProfile.$name.weights = "1.0,0.75,0.5,0.25,0.01,0.01,0.01,0.01,0.01,0.01".

The weights (distanceProfile.$name.weights) are configured for equally-spaced distance intervals. The distance intervals are dynamically bound between 0 degree and the maximum epicentral distance for a considered event. The number of distance intervals is given by the number of weights (distanceProfile.$name.weights). Typically, 10 intervals are used. Higher weight should be given to lower distances.

Extended gap criterion¶

Declares: confirmation

Origins are confirmed if the number of used observed phases (arrivals) $\ge$ : gapMinPhase AND the maximum azimuthal gap $\le$ : maxGap. Setting gapMinPhase <= 0 disables the extended gap criterion. Unused phases, i.e. phases with zero weight, are not counted. The confirmation overwrites the origin status if set to rejected by the station - distance evaluation.

Background¶

Origins meeting the gap criterion may be later rejected, e.g. by the station - distance evaluation. Rejection may even happen for real events when the epicentral distances to the closest stations are large, e.g. for remote earthquakes at mid-ocean ridges.

Origins of those events may be explicitly confirmed by the extended gap criterion.

Origin Evaluation Status¶

The evaluation status of an origin will be updated upon its change due to the evaluation methods and a descriptive origin comment is written to the origin.

However, the evaluation status may be changed at different times by different modules. In order to track this history a journal entry is created and sent when running sceval with a connection to the SeisComP messaging or added to the XML output long with the origins. In future versions of SeisComP such journal entries will be accessible in scolv [6].

Origin Comments in Events List¶

The different algorithms add comment fields to the origin objects which can be used to identify the processing. When an evaluation methods triggers an ection, a comment indicating the algorithm is added to the origin parameters:

scevalMethod - the evaluation algorithm that has changed the origin status
mismatchScore - the mismatch score resulting from the Station - Distance evaluation
maxGap - comment indicating that the station GAP exceeds the configured maxGap.

The comments can be shown in the Events list, e.g. of scolv, in a custom column.

../_images/sceval_scolv_custom_column.png

Figure 5: scolv with a custom column showing the mismatchScore.¶

Configuration of Events list:

Showing the mismatchScore in the Events table. Add to scolv.cfg or to global.cfg:

eventlist.customColumn = "mismatchScore"

# Define the default value if no comment is present
eventlist.customColumn.default = "-"

# Define the comment id to be used
eventlist.customColumn.originCommentID = mismatchScore

Show the comment scevalMethod in the Events table.

eventlist.customColumn = "evaluation method"

# Define the default value if no comment is present
eventlist.customColumn.default = "-"

# Define the comment id to be used
eventlist.customColumn.originCommentID = scevalMethod

Station selection by QC parameters¶

During real-time evaluation of origins by station - distance statistics sceval [3] accounts for relevant data conditions given by the waveform quality control (QC) parameters and the bindings configuration (CONFIG). Only stations with status enabled and which have a binding of the setup configured by setupName are considered. Typically, setupName defines the phase detector, e.g. :cite::t`scautopick`. Use default for all streams configured by the global bindings. Thus, setupName is used to define the module which delivers the picks. The restriction to a pick module allows to confine sceval specifically to a particular processing pipeline. From the accepted streams only those are considered where the QC parameters meet the value ranges defined in qc.parameters.

Station status updates (station enabled or disabled) are received and considered through the message group CONFIG. When origins arrive with arrivals from disabled stations, then the stations are automatically activated.

In real time, the QC parameters are provided by scqc [7] through the QC message groups of the SeisComP messaging. sceval must therefore subscribe to the message groups of the sending QC system and of the modules sending the origins and arrivals, e.g.:

QC
CONFIG
LOCATION

Note

The names of the message groups may be different by configuration of scmaster [5] and the sending modules.
scqc [7] must be running at all times when running sceval in real time and it must compute the requested QC parameters.
To ignore unavailable QC parameters activate
- qc.sloppy: only consider available QC parameter but ignore missing ones or
- qc.noQC: ignore all QC parameters.

Pipelines, Redundancy/Import¶

In systems with multiple processing pipelines or where external origins are imported from other SeisComP systems origins may have been generated with unconsidered setups (setupName). Typically, they shall not be evaluated.

Pipelines¶

In a pipeline system generate multiple instances of sceval, one for each pipeline. Example:

seiscomp alias create l1sceval sceval

Configure sceval and l1sceval them seperately, including setupName and connection.subscriptions.

External origins¶

External origins can be received from another system, e.g. by the LOCATION or the IMPORT_GROUP message groups. On the other system, the station setup, waveform QC parameters and the configurations in general may be different. Therefore, the local instance of sceval may be inappropropriate for processing the external origins. Confinement to origins from particular systems and modules can can be achieved by configuration of origin.agencyWhiteList and origin.authorWhiteList. Whitelist either agencies or authors or both for ignorig origins from other agencies or authors, respectively.

Playbacks¶

sceval can be used in real-time playbacks or XML-based offline playbacks.

Considerations¶

At the time of the playback, some waveform QC parameters, e.g. latency, availabilty, delay, measured at the time of waveform recording may not be available preventing stations to be active for evaluation. The data availability, delay and latency are generally different from values at the time of the data recording.

Activate qc.sloppy or use --sloppy to activate stations as soon as waveform QC parameters are received and they are in range.
In XML-based real-time playbacks without waveform and offline XML playbacks the waveform QC parameters are generally unavailable for the considered XML data.

Activate qc.noQC or use --noQC to ignore all QC messages and to activate all stations which have bindings parameters defined by setupName.
In tuning mode or when using XML playback, QC messages are generally ignored and all stations which have bindings parameters defined by setupName are active.

Real-time playbacks¶

sceval can be used in real-time playbacks of waveforms or in XML playbacks using playback_picks provided with the scanloc package. Waveform QC parameters may be unrealistic during such playbacks. Therefore, the QC parameter ranges defined in qc.parameters should be configured with -inf,inf and the parameter qc.sloppy should be activated by configuration or as commandline option.

XML-based offline playbacks¶

sceval can be used in offline playbacks for fast data processing of event XML files. The evaluation of waveform QC parameters is inactive during XML-based offline playbacks.

scevent [4] considers the origin status when determining the preferred origin. With the evsceval plugin it may also set the event certainty and type. Therefore, in XML-based playbacks sceval should be executed after running the locator, e.g. scanloc [1], but before scevent (compare with scanloc playbacks [1]):

scanloc --ep picks.xml -d type://user:passwd@host/database --debug > origins.xml
sceval --ep origins.xml -d type://user:passwd@host/database --debug > origins_eval.xml
...
scmag ...
scevent --ep mags.xml -d type://user:passwd@host/database --debug > events.xml

You may also confine evaluation to one or more origins. Provide the option -O with a comma-separated list of their IDs, e.g.:

sceval -d localhost --ep origins.xml -O Origin/abc,Origin/xyz > origins_sceval.xml

Tuning: during runtime¶

The results from the station - distance evaluation, specifically the mismatchScore can be observed during runtime without setting the origin status. The mismatchScore can be observed and compared with the event status set by operators. Eventually, the score limits, mismatchScore.confirmed and mismatchScore.rejected can be configured after a comparison.

Deactivate mismatchScore.use to calculate the mismatchScore without setting the event status. Active a custom column in the Events table in scolv to view the mismatchScore.

Self-Tuning¶

sceval has a tuning mode for finding an optimum weight profile and thresholds parameters for the station - distance evaluation which can be used to eventually configure sceval:

Thresholds: mismatchScore.confirmed, mismatchScore.rejected,
Weights of distance proiles: distanceProfile.$name.weights.

For convenience the auxiliary tool sceval-tune is provided as a wrapper to run sceval in tuning mode. sceval-tune considers

A particular instance of sceval, e.g. in a pipeline system.
A particular distance profile from distanceProfiles defining distanceProfile.$name.max.
The configuration parameters not related to the station - distance evaluation.
Evaluated preferred origins of given events

Invoke the help (-h) to learn about command-line options

sceval-tune -h

Known limitations¶

In the current version the tuning mode has limitations:

QC parameters are not considered.

Work Flow¶

Recommended work flow for tuning:

Identify the sceval instance to be tuned.
Adjust the configuration of this instance. Set the parameters which are unrelated to the station - distance evaluation and which will evaluate origins before the station - distance evaluation takes an effect (understand figure Methods for origin evaluation. ).
Manually review and evaluate the origin status for many events. Choose “confirmed”, “rejected” or leave the Origin status unflagged.

Use scolv to manually evaluate the preferred origins of events by setting the origin status. During evaluation set the origin status to confirmed, rejected or unset (if flagging is not reasonable). For tuning of sceval do not add new picks on stations that were not picked and associated by the automatic system. Otherwise the origins with arrivals will not be representative of the automatic system. The considered time window should be long enough to contain a significant number of each rejected and confirmed origins, e.g. 50 rejected and 50 confirmed origins.
Create an event XML file from the events that are manually reviewed.

Generate the event XML file, e.g. eventlist.xml, from the evaluated events. Choose any file name. The file name is provided through parameters.

Use scxmldump [8] to dump the events into a XML file. Choose any file name. The file name is provided to sceval through parameters.
Create a configuration XML file containing the bindings configuration.

Use scxmldump -C to dump the binding configuration into a XML file. Choose any file name. The file name is provided to sceval through parameters.

Create an inventory XML file

Use scxmldump -I to dump the station inventory into a XML file. Choose any file name. The file name is provided to sceval through parameters.

Example code for generating the XML files in the previous steps:

#!/bin/bash

# database
db=mysql://sysop:sysop@localhost/seiscomp

# dump events
evtList=`scevtls -d $db --begin '2021-05-22 12:00:00' --end '2021-06-30 23:59:59' |\
awk '{for (i=1;i<=NF;i++)  printf("%s,", $i)}' | sed 's/,$//'`

scxmldump -d $db -E $evtList -PAMf -o eventlist.xml
# dump configuration
scxmldump -d $db -C -o config.xml
# dump inventory
scxmldump -d $db -I -o inventory.xml

Generate the list of weight profiles.

Use sceval-tune to create a list of profiles considered for finding the best-performing weight profiles. Choose a sufficient number of distance intervals, e.g. 5 - 10 intervals and a list of weight values. sceval-tune will find all meaningful permutations of weights for all distance intervals. Default value may be used. Save the profile list in a file. Review and adjust the profile list if desired.

Required parameters for generating the list of profiles by sceval-tune:
- -g
  
  Generate the list of profiles.
- -f arg
  
  arg: Name of the file containing the created profile list.
Optional parameters:
- -n arg
  
  arg: Maximum number of distance intervals. Uses default if -n is not set. Default: 10
- -w arg
  
  arg: Weight profile to be tested. Uses default if -w is not set. Default: 1,0.75,0.5,0.25,0.1,0.01
Example for creating the list of weight profiles:
```
sceval-tune -f profiles.txt -g -n 6 -w 1,0.5,0.1
```
Tune the configuration parameters for the distance profile also defined in the distanceProfiles.

Run sceval-tune in a command-line terminal to find the optimum configuration parameters for one of the distance profiles given in distanceProfiles. Repeat the tuning for all profiles individually. The tuning is relies on a sufficient number of manually confirmed and rejected events.

For tuning provide the considered weight profiles in the profile list file. These weight profiles are evaluated identifying the best-performing weight profile and the associated threshold values mismatchScore.confirmed and mismatchScore.rejected. The best-performing weight profile and the threshold values are determined by optimizing the automatic w.r.t. the manual evaluation. As a measure, the misfit is minimized.

The configuration parameters and quality parameters are printed on the command line. Based on the suggested configuration parameters, the percentages indicate the number of events that would be confirmed or rejected by the automatic system w.r.t. the manual evaluation. The main plot figure is generated to review the performance of the tuning and the configuration parameters. The optional additional plot figure shows the results for the 9 best-performing weight profiles.

Two possible values for mismatchScore.rejected are provided based on the confirmed or on the unflagged origins. Both values should be similar but the value for the confirmed origins should typically be chosen.

If mismatchScore.confirmed and mismatchScore.rejected are largely separated, many origins may remain unflagged by sceval. Increasing mismatchScore.confirmed or decreasing mismatchScore.rejected will reduce the number of unflagged origins but will possibly result in wrong automatic flagging of real and fake events.

Required parameters for tuning by sceval-tune:
- -p arg
  
  arg: Bame of the distance profile that is to be tuned. The profile must be configured. The name must be contained in the configuration parameter distanceProfile.
- -f arg
  
  arg: Name of the file containing the profile list.
- --ep arg
  
  arg: name of event XML file
- --config-db arg
  
  arg: name of the configuration XML file.
- --inventory-db arg
  
  arg: Name of the inventory XML file.
Optional parameters:
- --time-window arg
  
  arg: Time window of the considered events.
- --use-defaults arg
  
  Ingore the configuration of the tuned sceval instance and use defaults.
- --addplots
  
  Show results from the 9 best-matching weight profiles.
- --debug
  
  Print all debug output from sceval.
Example:
```
sceval-tune -f profiles.txt --inventory-db inventory.xml --config-db config.xml --ep events.xml -p 180 --addplots
```
Configuration of sceval

Configure the distance profile of the tuned sceval instance using the proposed parameter values.

Tuning results¶

sceval-tune provides the configuration parameters and the tuning statistics on the command terminal where it was executed. In addition, one main and one additional (–addplots) figure are created for visual inspection of the tuning results.

Figure 6: Main figure showing results for the best-performing weight profile. Solid line: mismatchScore values based on flagged events. Dashed line: mismatchScore values based on flagged and unflagged events.¶

Figure 7: Additional figure showing results for the 9 best-performing weight profiles. Generated when using –addplots. Solid line: mismatchScore values based on flagged events. Dashed line: mismatchScore values based on flagged and unflagged events.¶

Module Configuration¶

etc/defaults/global.cfg
etc/defaults/sceval.cfg
etc/global.cfg
etc/sceval.cfg
~/.seiscomp/global.cfg
~/.seiscomp/sceval.cfg

sceval inherits global options.

Note

Modules/plugins may require a license file. The default path to license files is @DATADIR@/licenses/ which can be overridden by global configuration of the parameter gempa.licensePath. Example:

gempa.licensePath = @CONFIGDIR@/licenses

minPhase¶

Default: 0

Type: integer

Minimum number of phase arrivals (P or S) used for locating. Origins with arrivals fewer than minPhase and fewer then distanceProfilesMinPhase are rejected. Only consider arrivals with weight > 0.

minDepth¶

Default: -10.0

Unit: km

Type: double

Minimum depth criterion: origins with depth less than minDepth are rejected.

maxDepth¶

Default: 745.0

Unit: km

Type: double

Maximum depth criterion: origins with depth greater than maxDepth are rejected.

maxRMS¶

Default: 3.5

Unit: s

Type: double

Maximum RMS: origins with RMS residual larger than maxRMS are rejected.

maxGap¶

Default: 360.0

Unit: deg

Type: double

Gap criterion: maximum allowed azimuthal gap between adjacent stations providing arrivals to one origin. Origins with a larger gap receive a comment. The status remains unchanged. Only consider arrivals with weight > 0.

minPhaseConfirm¶

Default: -1

Type: integer

Minimum phase confirmation: Origins having at least the configured number of arrivals (associated phase picks) are confirmed. -1 disables the method.

gapMinPhase¶

Default: -1

Type: integer

Extended gap criterion: Origins with gap lower than maxGap and more than gapMinPhases arrivals are confirmed.

gapMinPhase <= 0: ignore check.

distanceProfiles¶

Type: list:string

Registration of distance profiles for station - distance evaluation. An empty list disables the station - distance evaluation.

distanceProfilesMinPhase¶

Default: 0

Type: integer

Minimum number of P-phase arrivals for applying the station - distance evaluation. Only consider arrivals with weight > 0.

distanceProfilesMinPhase <= 0: ignore parameter.

setupName¶

Default: scautopick

Type: list::string

List of configuration setup names used for the initial setup of the active station list. Use commas to separate names. E.g. in pipelines use the names of all modules contributing picks.

“scautopick”: consider all stations with scautopick bindings and the streams defined therein.

“default” or “global”: consider all stations with global bindings and the streams defined therein.

Note

qc.* Waveform quality control (QC) parameters. Ensure sceval subscribes to the message groups, e.g. QC, CONFIG, LOCATION.

qc.parameters¶

Type: list:string

Defines QC parameters to observe and the value ranges to consider streams. Each QC parameter is associated with a value range. If any of the defined ranges is exceeded, the corresponding station is disabled. Use ‘-Inf’ resp. ‘Inf’ if no upper or lower bound should exist. scqc must be running. Typical parameters: rms, latency, delay, availability, gaps count, overlaps count, timing quality, offset, spikes count. Find the examples in $SEISCOMP_ROOT/etc/defaults/sceval.cfg.

To effectively disable QC parameters set the ranges to -Inf,Inf.

qc.sloppy¶

Default: false

Type: boolean

At startup of sceval waveform QC parameters may be initially missing preventing immediate station evaluation. If sloppy is active, a station is activated as soon as one QC parameter arrives which is in range. Out-of-range parameters deactivate the station.

Recommended use: waveform playbacks, frequent restarts of sceval. Consider adjusting qc.parameters, e.g. disable the availability check.

qc.noQC¶

Default: false

Type: boolean

Do not consider QC parameters. This will activate all stations which have a binding configuration defined by setupName.

Activate in real-time playbacks without waveforms.

qc.useDatabase¶

Default: false

Type: boolean

Load QC parameters from the database during startup. Setting to true may slow down the start up.

Note

origin.* Limit the range of origins to be evaluated.

origin.agencyWhiteList¶

Type: list:string

Agency IDs for filtering origins. Separate by comma. Only evaluate origins with one of the given agency ID. If unset, no filtering is applied.

origin.authorWhiteList¶

Type: list:string

Author names for filtering origins. Separate by comma. Only evaluate origins with one of the given author names. If unset, no filtering is applied.

origin.ignoreStatus¶

Default: rejected,reported,preliminary,confirmed,reviewed,final

Type: list:string

Ignore an origin if its status has any of the given states. The option is ignored for manual origins if origin.manual = true.

origin.manual¶

Default: false

Type: boolean

Enable evaluation of origins where the evaluation mode is set MANUAL. Default: disable. Check the box to enable the evaluation.

Note

mismatchScore.* Threshold parameters for the station-distance evaluation. They apply to all distance weight profiles.

mismatchScore.confirmed¶

Default: 0.5

Type: double

Mismatch between active stations and used stations. If the score is less than or equal to the evaluation status is set to CONFIRMED.

mismatchScore.rejected¶

Default: 0.7

Type: double

Mismatch between active stations and used stations. If the score is greater than or equal to the evaluation status is set to REJECTED.

mismatchScore.use¶

Default: true

Type: boolean

Calculate the mismatch score and set the origin status. Deactivating only calculates the score without setting the status. Deactivating is useful for testing and tuning. View the score in scolv.

Note

distanceProfile.* Distance-weight profiles for the station-distance evaluation.

Note

distanceProfile.$name.* $name is a placeholder for the name to be used and needs to be added to distancesProfiles to become active.

distancesProfiles = a,b
distanceProfile.a.value1 = ...
distanceProfile.b.value1 = ...
# c is not active because it has not been added
# to the list of distancesProfiles
distanceProfile.c.value1 = ...

distanceProfile.$name.max¶

Unit: deg

Type: double

Upper epicentral distance of stations for using this profile.

distanceProfile.$name.weights¶

Type: list:double

Weights to use. The number of weights determine the number of distance intervals.

Command-Line Options¶

Generic¶

-h, --help¶: Show help message.

-V, --version¶: Show version information.

--config-file arg¶: Use alternative configuration file. When this option is used the loading of all stages is disabled. Only the given configuration file is parsed and used. To use another name for the configuration create a symbolic link of the application or copy it. Example: scautopick -> scautopick2.

--plugins arg¶: Load given plugins.

-D, --daemon¶: Run as daemon. This means the application will fork itself and doesn’t need to be started with &.

Verbosity¶

--verbosity arg¶: Verbosity level [0..4]. 0:quiet, 1:error, 2:warning, 3:info, 4:debug.

-v, --v¶: Increase verbosity level (may be repeated, eg. -vv).

-q, --quiet¶: Quiet mode: no logging output.

--print-component arg¶: For each log entry print the component right after the log level. By default the component output is enabled for file output but disabled for console output.

--component arg¶: Limit the logging to a certain component. This option can be given more than once.

-s, --syslog¶: Use syslog logging backend. The output usually goes to /var/lib/messages.

-l, --lockfile arg¶: Path to lock file.

--console arg¶: Send log output to stdout.

--debug¶: Execute in debug mode. Equivalent to –verbosity=4 –console=1 .

--trace¶: Execute in trace mode. Equivalent to –verbosity=4 –console=1 –print-component=1 –print-context=1 .

--log-file arg¶: Use alternative log file.

Origin¶

--agencies list¶: Agency IDs for filtering origins. Separate by comma. Only evaluate origins with one of the given agency ID. If unset, no filtering is applied.

--authors list¶: Author names for filtering origins. Separate by comma. Only evaluate origins with one of the given author names. If unset, no filtering is applied.

-O, --origins string¶: origin ID(s). Only process origins which have one of the given IDs. Provide a comma-separated list for multiple IDs. Only in offline playbacks with –ep.

--manual¶: Enable evaluation of origins where the evaluation mode is MANUAL.

Mode¶

--ep XML file¶: Read event parameters from XML file in offline processing.

--sloppy¶

Enable if sceval is used in a real-time waveform playback to disable waiting for waveform QC messages. Waveform QC messages may be missing or take some time to be created. Arteficial gaps may result from repeated real-time waveform playbacks. Consider adjusting qc.parameters, e.g. disable the availability check.

Playbacks without waveforms: Set qc.parameter ranges to -inf,inf.

--noQC¶: Do not consider QC parameters.

--force¶: For evaluation of all origins. Use this optiom to evaluate origins which have already been evaluated or which are manual. Use the option for testing the configuration.

Tuning¶

-f, --filename profiles file¶: File to read tuning parameters from. e.g. profiles.

-p, --profile name¶: Name of the distance profile which should be tuned. If ommitted, the default profile is used.

-t, --time-window time range¶: Specify time window as one properly quoted string. Times are in UTC and separated by a tilde ~ e.g. “2016-01-01 00:00:00~2016-01-02 00:00:00”.

--use-defaults¶: Use default configuration of sceval in tuning mode. Default: use configuration.