| Thanks >"GW170104 was first identified by inspection of low-latency triggers from Livingston data [15–17]. An automated notification was not generated as the Hanford detector’s calibration state was temporarily set incorrectly in the low-latency system. After it was manually determined that the calibration of both detectors was in a nominal state, an alert with an initial source localization [18,19] was distributed to collaborating astronomers [20] for the purpose of searching for a transient counterpart. About 30 groups of observers covered the parts of the sky localization using ground- and space-based instruments, spanning from γ ray to radio frequencies as well as high energy neutrinos [21]."
https://dcc.ligo.org/LIGO-P170104/public Regarding the earlier detection: >"At 11:23:20 UTC, an analyst follow-up determined which auxiliary channels were associated with iDQ’s decision. It became clear that these were un-calibrated versions of h(t) which had not been flagged as “unsafe” and were only added to the set of available low latency channels after the start of ER8. Based on the safety of the channels, the Data Quality Veto label was removed within 2.5 hours and analyses proceeded after re- starting by hand."
http://ligo.elte.hu/magazine/LIGO-magazine-issue-8.pdf So both times humans had to take special action for the detection to "count". I really wonder about whether the null model they are using is appropriate/relevant here. Also, the other thing I have been concerned about is the lack of any corroborating evidence that these signals are truly generated by inspiraling black holes(gamma ray bursts, etc). Apparently, in this case the above-mentioned miscalibration has impeded that effort: >"The event candidate was not reported by the low-latency analysis pipelines because re-tuning the calibration of the LIGO Hanford detector is not yet complete after the holiday shutdown. This resulted in a delay of over 4 hours before the candidate could be fully examined. We are confident that this is a highly significant event candidate, but the calibration issue may be affecting the initial sky maps. We will provide an update in approximately 48 hours which may include an improved sky map."
https://gcn.gsfc.nasa.gov/other/G268556.gcn3 I can't tell from that text file whether they got corroborating evidence or not. IANAP though. |
By design, detection statements and significance estimates come solely from the offline analysis which is conducted separately (i.e. not triggered by) the online analysis. No human intervention is required here, as the issue with the online status information was known about at the time and was not an issue with the data itself. Even if there were no candidate events at the time, it would be been included in the offline analysis of the period containing the event.
In regards to GW150914 and iDQ, you should know that iDQ has never been approved as a veto for CBC (compact binaries such as neutron stars and black holes) searches. Again, no intervention was required to "remove" the veto as it was never used in the offline analysis nor would be in the first place. It's only use that I am aware of is as a veto against Burst triggers in online analysis. These searches look for generic signals, but may also detect some of the louder CBC sources, such as GW150914. In case you were wondering, there weren't dedicated online CBC searches at the time of GW150914, but there were offline analysis, and those produced the results reported in the original detection paper.