damb
commented
2 years ago @mmesim, thanks for reporting.
That probably means that there are not 10 picks available, which seems weird.
Without having checked the reproducer's configuration yet, I guess that this might be an issue when trying to avoid to associate a single phase to be associated multiple times with a sensor location. This is required in certain configuration scenarios, e.g. given the following detector configuration:
{
"detectorId": "detector-01",
"createArrivals": true,
"originId": "originId",
"templatePhase": "Sg",
"templateWaveformStart": -0.25,
"templateWaveformEnd": 2,
"streams": [
{
"templateId": "template-01",
"waveformId": "CH.GRIMS..HHN"
},
{
"templateId": "template-02",
"waveformId": "CH.GRIMS..HHE"
}
]
}I.e. in the example above, in order to avoid to associate an Arrival with phase Sg twice (regarding the sensor location CH.GRIMS..) scdetect-cc drops one of the arrivals including the respective pick. This is not ideal, however, AFAIU, in the SeisComP datamodel the relationship Pick <-> Origin can be established only by means of an Arrival.
Do you have a better idea how to circumvent this issue?
mmesim
@damb Well, I shared with you the files. Here I'll report the problem. I run the shared example and set
minimumArrivals: 10. However, when I runsceventwith the results.scml I received the following message multiple timesor
That probably means that there are not 10 picks available, which seems weird.
I still do not if it
scdetect-ccorsceventproblem.I didn't include the results.scml to check whether you can fully reproduce the error.