This page describes how to duplicate the scautopick-scautoloc-screloc pipeline for different purposes e.g. monitoring a special region with a selected subset of stations, or monitoring different kind of seismic activities as large teleseismic events.

N.B. SeisComP3 limitations:

• SeisComP3 can handle only one instance of each module-name
• Messaging usernames cannot be longer than 10 characters so when creating an alias with more than 10 characters, set the connection.username to a unique identifier with not more than 10 characters

For these reasons, each module used in a duplicated pipeline should be duplicated.

FIRST STEP

Duplicate the module, the safest way is by using a soft link.

   ln -s $HOME/seiscomp3/trunk/bin/scautopick $HOME/seiscomp3/trunk/bin/scautopic2 

In all releases after Zurich you can also create the alias with

   seiscomp alias create scautopic2 scautopick

(N.B. name scautopick2 exceeds the 10 char messaging username limitation)

This should be done for three modules (scautopic2, scautoloc2, screloc2).

SECOND STEP

Add new groups to the messaging system in scmaster.cfg

   msgGroups = ${msgGroups}, PICK2, LOCATION2

THIRD STEP

change the subscription and the primary group in the .cfg files in order to distinguish pick and origin from the two pipeline and to avoid that one of the modules reads messages of the other. N.B. connection.primarygroup defines to which group the module will write, connection.subscriptions from which group to read.

scautopick.cfg

   connection.primarygroup = PICK

scautopic2.cfg

   connection.primarygroup = PICK2

scautoloc.cfg

   connection.primarygroup = LOCATION
   connection.subscriptions = PICK, AMPLITUDE

scautoloc2.cfg

   connection.primarygroup = LOCATION2
   connection.subscriptions = PICK2, AMPLITUDE

screloc.cfg

   connection.subscriptions = PICK,LOCATION

screloc2.cfg

   connection.subscriptions = PICK2,LOCATION2

scevent.cfg

   connection.subscriptions = LOCATION, LOCATION2, MAGNITUDE, EVENT

scamp.cfg

  connection.subscriptions = PICK, PICK2, AMPLITUDE, LOCATION, LOCATION2

scmag.cfg

  connection.subscriptions = PICK, PICK2, AMPLITUDE, LOCATION, LOCATION2

FOURTH STEP

add to each module the specific configurations

FIFTH STEP

Add the new modules in $HOME/seiscomp3/trunk/key/global

   SC3_CLIENTS='scautopick scqc scevent scautoloc scmag scamp screloc scvoice scautopic2 scautoloc2 screloc2'

SIXTH STEP

If the specific configuration requires to distinguish and/or prioritise locations produced by the different pipelines: set a different agencyID in one of the scautoloc config file

agencyID = SEDtele 

then add in scevent.cfg

eventAssociation.agencies = SED, SEDtele

According to the definition in scevent, events are merged if they share a certain number of picks OR if they are close in space AND time according to how this three variable are set in scevent.log

eventAssociation.minimumMatchingArrivals = 3
eventAssociation.maximumDistance = 5
eventAssociation.maximumTimeGap = 60

Setting properly the first two can help in distinguishing simultaneous events occurring in different places or a sequence of two events with similar location.

add AGENCY in the priority list according to the specific needs, e.g.:

eventAssociation.methods = "NonLinLoc(EDT)", "NonLinLoc(L2)", "LOCSAT"
eventAssociation.priorities =  STATUS, METHOD, AGENCY
eventAssociation.agencies = "SED", "SEDtele"

Now run seiscomp restart.