DQ/detchar task should include Virgo's veto streams
PyCBC Live did not include Virgo's data in S190828j. I suspect this was due to Virgo's PyCBC veto stream (DQ_VETO_PYCBC) being active at the time of the event. It would be great if the DQ/detchar task could report the state of Virgo's veto streams in addition to V1:OBSERVATION_INTENT and V1:GOOD_DATA_QUALITY_CAT1, so situations like this are immediately clear.
Assigning to @geoffrey.mo based on history of
Pinging @florent-robinet as well as he can provide more info on veto streams.