Again, I noticed some inconsistencies while playing around with the the third offline playback example. That is, when running the example for the detector configuration identified by "detectorId": "detector-01" some of the detections are missing when enabling trigger facilities.
While the results are consistent for the detector identified by "detectorId": "detector-02", I obtained the following detection origin times for "detector-01" when executing scdetect-cc with
--record-starttime=2019-11-05T04:09:00 and the template configuration containing both the configuration of both detector-01 and detector-02:
i.e. overall 5 detections. Note the difference to the configuration above. Besides, the result contains subsequent detections with origin times smaller than the configured "triggerDuration" (see #129).
--record-starttime=2019-11-05T04:09:00 and the template configuration containing the configuration of detector-01, only:
As already mentioned results are perfectly consistent with trigger facilites disabled.
At first sight, I assumed that there detector-01 and detector-02 are somehow interfering. However, after some debugging it turned out that it's the trigger facility implementation which has a serious flaw.
Again, I noticed some inconsistencies while playing around with the the third offline playback example. That is, when running the example for the detector configuration identified by
"detectorId": "detector-01"some of the detections are missing when enabling trigger facilities.While the results are consistent for the detector identified by
"detectorId": "detector-02", I obtained the following detection origin times for"detector-01"when executingscdetect-ccwith--record-starttime=2019-11-05T04:09:00and the template configuration containing both the configuration of bothdetector-01anddetector-02:i.e. overall 3 detections.
--record-starttime=2019-11-05T04:11:00and the template configuration containing both the configuration of bothdetector-01anddetector-02:i.e. overall 5 detections. Note the difference to the configuration above. Besides, the result contains subsequent detections with origin times smaller than the configured
"triggerDuration"(see #129).--record-starttime=2019-11-05T04:09:00and the template configuration containing the configuration ofdetector-01, only:i.e. 7 detections overall.
--record-starttime=2019-11-05T04:11:00and the template configuration containing the configuration ofdetector-01, only:with 6 detections overall.
As already mentioned results are perfectly consistent with trigger facilites disabled.
At first sight, I assumed that there
detector-01anddetector-02are somehow interfering. However, after some debugging it turned out that it's the trigger facility implementation which has a serious flaw.