I hear you and I tend to agree with all of that by the way. My beef really isn't with the fact that there was a veto, or the fact that they chose to override that veto. My issue and my criticism relates to the fact that they erroneously and inaccurately claimed that there was no veto within an hour of the event in their published and peer reviewed paper, and they never bothered to explain what actually caused the veto, or why it achieve a "high confidence" figure. All of that information *should* have been included in the published and peer reviewed paper but it wasn't. Instead we got a pure whitewashed and fabricated version of events in the *published paper*. That's simply unethical IMO.Benburch:
High energy physics has a thing called a trigger processor. This is the thing that constantly looks at the detector suite and which decides when something interesting enough to log and analyze has happened. Often these are exquisitely sensitive and will provide a very high percentage of interesting events. But the people running the show are never happy with them. They fear that the trigger, whose function is to throw away data, is going to throw away the events they are trying to find, so they disable or hobble the trigger.
This means they need to waste a lot of computer resources sorting out the things the trigger would have found for them from all the noise.
But when they do find it, the fact of ignoring the trigger does not in any way degrade the observation!
I think they should have made a real effort to fully *explain* the purpose of adding that veto, the cause of the veto, the actual hardware it's based upon, an explanation of why it was vetoed with "high confidence", and a lot more information related to their determination of "safety", specifically some quantified estimate of some sort.
I didn't even get that from LIGO. All I got was a slightly more verbose (not that much more verbose) version of the LIGO magazine account of events which really only verifies my criticism that the published version was a snow job.
See my comments above. I don't take issue with the fact that they received a veto or that they chose to override that veto. I have a problem with their fabricated explanation of the veto events around GW150914 in the *published* paper.Selfsim:
Yes .. and that's almost exactly how the vetos are used in notifying the 'downstream' follow-up teams (eg: such as other observatories).
Why was this particular veto added in the first place, and what kind of auxiliary hardware was attached to that particular veto? Was it an EM reading that caused it to fail, or was it something else altogether? How and why did the software decide to reject that specific signal with "high confidence" the first time through? LIGO has been rather frugal with any specific details. Perhaps you would care to enlighten us? You might start by explaining why that particular veto was added in the first place, and what kind of hardware it was associated with?LIGO has said that the veto which was over-ridden, was untested and was subsequently determined to be 'unsafe'.
Exactly how "safe" was their manual override? Was it 80 percent safe to override that veto? Was it 95 percent safe? 5.1 sigma safe? All I've seen thus far is a little bit of internal jargon and a request to simply "trust us, that veto software was wrong" without any *specific* details about anything.
Like I said, I don't really have a problem with their actions. I simply have a problem with their whitewashed version of events in the published paper which left out all the relevant details about that veto.This would be as expected during what was still an Engineering Run phase (and not an Operational Run phase). There was still a chance that testing was being carried out when the veto went active however, investigations conducted at the time, (over ~2 hour period), determined that no manual testing was being conducted.
How *exactly* (be specific) did you get the idea that "the veto assumed that manual tests were being carried out when they were not" from anything that is written in LIGO magazine? I certainly didn't get that from either the LIGO magazine account, or from their response to my first email. I'm kinda waiting with baited breath to see if they'll be a little more forthcoming with the details about the veto and their decision to override it. I still have no idea what *exactly* caused the veto, what specific hardware was involved with that veto, how it decided to veto that particular signal with "high confidence" rather than say "low confidence", or any pertinent details.The chances are that the veto assumed that manual tests were being carried out when they were not, and so the veto was (justifiably) over-ridden. This all comes from a cursory read of the LIGO newsletter in question.
They just confirmed to me that they gave a less than accurate account of data quality events in their published paper. That's all they've done so far. That information just disturbs me, particularly without any real details about the veto. All they did was verify my criticism about their less than accurate account of events in the published paper.I notice that MM has received nothing more than confirmation of what was in that newsletter from LIGO, so nothing has changed, and he has no new information for consideration.
I do not need any additional information as it relates to the content and theme of my paper. There is no empirical evidence that the signal in question was celestial in origin. If they applied their same process of elimination method consistently, they should have put this signal in the "unknown cause" category, not the "gravitational waves surely did it" category. The confirmation bias problem still applies and it still remains the Achilles heal of the their entire paper, and in fact *both* papers. All LIGO has done so far is confirm my criticism about their less than accurate portrayal of data quality veto events in the published papers. That's not comforting.