Setup and configuration

Catalyst is configured in three places:

  • the module configuration catalyst.cfg, for settings that belong to the installation (database, messaging, plugins, file paths, limits),

  • processing profiles, for the processing settings of the GUI, typically one per network or region,

  • the GUI itself, where every processing setting can be changed at runtime.

The module configuration is read from @DEFAULTCONFIGDIR@/catalyst.cfg, @SYSTEMCONFIGDIR@/catalyst.cfg and @CONFIGDIR@/catalyst.cfg, in this order, as for every SeisComP module. Use scconfig or edit the files directly. All parameters are listed in the module reference.

Starting Catalyst

catalyst is a SeisComP GUI application and accepts the usual command-line options. Typical calls:

  • Work on files only, without database or messaging:

    catalyst

    Open an XML file with File → Open….

  • Load from the database:

    catalyst -d mysql://sysop:sysop@localhost/seiscomp

  • Load from the database and send results to the messaging system:

    catalyst -H localhost -d mysql://sysop:sysop@localhost/seiscomp

Without a messaging connection, File → Send Selection to Messaging and Review in scolv are not available.

Plugins

The origin score uses the OriginMultiFeature score processor of scevent, which is provided by the scoremf plugin. Load it and configure its parameters in catalyst.cfg:

plugins = ${plugins}, scoremf

# Which score processor to use and whose score.* configuration to read.
score.processor = OriginMultiFeature
score.configModule = scevent

score.processor and score.configModule are optional and default to the values shown. With score.configModule = scevent the score uses the same score.mf.* parameters as scevent, so Catalyst and the real-time system rank origins the same way.

OriginMultiFeature gives a manual origin its default score (usually 0) unless score.mf.scoreManualOrigins is set: in scevent the evaluation mode outranks the score. In catalyst an origin becomes manual when it is relocated or confirmed, so by default its score drops to 0. score.scoreManualOrigins decides this for catalyst alone, without changing scevent:

# true: score manual origins like automatic ones
# false: manual origins keep the default score
# unset: the setting of score.configModule applies
score.scoreManualOrigins = true

If the plugin cannot be loaded, the score shows N/A. Calculate score retries and reports the reason.

Processing limits

# Upper limit on the number of origins nucleation may create, as a guard
# against runaway output. 0 = no limit.
nucleator.maxOrigins = 5000

nucleator.maxOrigins is not shown in the GUI on purpose. The minimum number of phases of a Smart-locate result is a processing setting: the profile key locator.smartLocate.minPhases (see Processing profiles).

Keys of earlier versions (maxOrigins, minPhases, cities, citiesFile, demPath, faultPointBudget) are no longer read; Catalyst logs a warning with the new name when it finds one.

Over-detecting stations

Picks from stations that produce many more picks than the others are weak evidence. They are used by the Clean Q metric and the isolated-pick filter. Stations are treated as over-detecting either because they are listed explicitly, or, without a list, because they have more than factor times the median number of picks per station in the loaded data.

# Explicit list: NET.STA or a plain station code.
qc.overdetection.stations = IS.HRAUN, KRA

# Automatic detection when no list is given. 0 or less switches it off.
qc.overdetection.factor = 3.0

3D view

# Reference cities shown in the 3D view. The key of the same name in the
# processing profile overrides this list.
gui.cities = Reykjavik, Akureyri

# SeisComP cities XML used to look up their coordinates.
# Default: @DATADIR@/cities.xml
gui.citiesFile = @DATADIR@/cities.xml

# Folder with the GEBCO elevation tiles used for topography.
gui.demPath = /home/data/elevation

# Total number of points used to draw fault surfaces (default 500000).
gui.faultPointBudget = 500000

Travel-time models

The TTT model list offers the tables configured for the chosen travel-time interface:

ttt.LOCSAT.tables = iasp91, sil
ttt.libtau.tables = iasp91, ak135

For LOCSAT, the profiles of the LOCSAT locator are used if ttt.LOCSAT.tables is not set.

catalyst ships two Is tables for infrasound and lists them in its default configuration, for the TTT model list and the LOCSAT profiles of the locator:

ttt.LOCSAT.tables = iasp91, iasp91_scanloc_istrat, iasp91_scanloc_icel026
LOCSAT.profiles = iasp91, iasp91_scanloc_istrat, iasp91_scanloc_icel026

Table

Is celerity

iasp91_scanloc_istrat

0.34 km/s in the near field, 0.30 km/s (stratospheric) from 300 km.

iasp91_scanloc_icel026

0.34 km/s up to 100 km, tapering to 0.26 km/s from 300 km. Used by the infra profile; fits regional sources at 300–800 km in eastern Europe.

The tables are installed in share/locsat/tables. A ttt.LOCSAT.tables or LOCSAT.profiles in etc/global.cfg or etc/catalyst.cfg replaces these lists; add the Is tables there to keep them. The generator apps/catalyst/docs/make_is_table.py in the source tree writes further tables with other celerities.

Processing profiles

Profiles are declared in catalyst.cfg as well. See processing profiles.

profiles = iceland, ukraine
defaultProfile = iceland
profile.iceland.configFile = @SYSTEMCONFIGDIR@/iceland.profile
profile.ukraine.configFile = @SYSTEMCONFIGDIR@/ukraine.profile

Window layout

The panel layout is saved when catalyst closes and restored at the next start. View → Home (reset layout) returns to the default layout, and View → Panels shows or hides individual panels.