iDQ check should only use times when it is reporting OK

Use the IDQ_OK channel to filter on the FAP timeseries. It is set to 1 when iDQ is OK.

changed milestone to %O4 bug fixes

mentioned in issue #559 (closed)

assigned to @geoffrey.mo

changed milestone to %O4

changed iteration to LL grp iterations May 15, 2023 - May 21, 2023

A potentially simpler implementation would involve skipping the iDQ check entirely if IDQ_OK = 0 for any time within the window of time requested.

changed iteration to LL grp iterations May 22, 2023 - May 28, 2023

removed iteration LL grp iterations May 15, 2023 - May 21, 2023

@geoffrey.mo any update on this? We need this in asap, it should have been in the O4 release

Please let me know if you can't do this today, because we'll ask Rachael to do it if you don't have the bandwidth.

I de-prioritized this last week since it isn't essential for O4 alerts (iDQ values are just annotated) and especially given that AFAIK iDQ isn't fully reviewed yet. I can get to it this afternoon/evening if it must go in today.

It doesn't need to get merged today (because it shouldn't go in this release with the circular fix), but it should go into the next release, so if you've got the bandwidth to do this today or tomorrow that'd be fantastic.

mentioned in merge request !1229 (merged)

changed iteration to LL grp iterations May 29, 2023 - Jun 4, 2023

removed iteration LL grp iterations May 22, 2023 - May 28, 2023

closed with merge request !1229 (merged)