Closed mmesim closed 2 years ago
The issue is definitely related to scdetect-cc
and the current master branch.
I ran a few examples with an older version of scdetect-cc
and it worked fine. However I still get the same error when trying to fix minimumArrivals
in scconfig
.
When I switched to the latest master the minimumArivals
set in templates.json
is ignored.
In the zip you can find all the input files and the expected results. It is actually the input files from example-03.
Perfect, @mmesim. Thanks a lot.
A minor note.
When I switched to the latest master the
MinimumArivals
set intemplates.json
is ignored.
Please make sure the spelling of the configuration parameters is correct. E.g. instead of MinimumArrivals
it must be minimumArrivals
in the templates.json
. See also: https://scdetect.readthedocs.io/en/stable/base/Template-Configuration.html#detector-configuration-parameters.
In the templates.json
unknown configuration parameters are simply ignored.
Please make sure the spelling of the configuration parameters is correct. E.g. instead of
MinimumArrivals
it must beminimumArrivals
in thetemplates.json
. See also: https://scdetect.readthedocs.io/en/stable/base/Template-Configuration.html#detector-configuration-parameters.In the
templates.json
unknown configuration parameters are simply ignored.
I confirm that I misspelled minimumArrivals
here. The .json file is fine.
Actually, there were two issues:
scdetect-cc
stopped with the error message from above. Due to simplicity I fixed this one with #126, as well.
Well, I was testing feature/iss-118 when I noticed something weird. When I run
scdetect-cc
on multiple stations & multiple channels and setting theminimumArrivals
to 8 (for example) in thetemplate.json
, the code returns all possible detections and ignores completely this value. Same when I runscdetect-cc
on master.Then I tried to set the value in the module (
scconfig
) and I got thisI pulled today the most recent master from seiscomp github page, but I have no idea if this issue is related to that.