Carve out a separate subnet from a larger network

Cookbook
1

If one wanted to create a smaller subnet of (~80) stations from a larger network, but still preserve the stations’ role in the larger network, is it recommended to create a separate set of modules: scamp2, scautopick2, scautoloc2, scevent2, scolv2, and scrttv2; and also create a separate set of groups: AMPLITUDE2, PICK2, LOCATION2, EVENT2?

Is there a more efficient way of doing it? Are the modules and groups listed above the only ones that need to have a separate pipeline or are there any that are missing (or I’ve listed them, but they are not necessary)? Is there a cookbook for this?

2

Is the old SeisComP3 way of having a split pipeline still way to do this, or is there a more efficient way in seiscomp 6?

3

Pipelines are defined by the message groups. Some modules such as scanloc and sceval (gempa modules, not provided with SeisComP) allow the filtering by author making additional message groups unnecessary for specific use cases.