You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The open box page involves the following executables:
pycbc_pygrb_page_tables
pycbc_pygrb_plot_snr_timeseries
pycbc_pygrb_efficiency
(and pycbc_pygrb_exclusion_dist_table)
(and the minifollow-ups subworkflow)
pycbc_pygrb_efficiency does not perform any data quality veto (nor do the other scripts, but I would have to double check to make this statement firm) and this kind of vetoing needs to be placed somewhere
To make the most out of the onsource trial, we would want to veto an onsource trigger only if it is in the, e.g., CAT2 vetoed time. This "preserves: as much data as possible and catches a trigger at, e.g., t_GRB - 1s if there is a veto at t_GRB - 4s. HOWEVER, the p-value calculation would be skewed because the onsource trial would be different from the offsource trials, which are all clean 6s stretches of data.
The other possibility (solution adopted in the past) is to exclude from the workflow IFOs that have CAT2 vetoes (or other requested vetoes beyond CAT1) in their onsource. However, this would miss the trigger in the example above.
The text was updated successfully, but these errors were encountered:
The open box page involves the following executables:
pycbc_pygrb_page_tables
pycbc_pygrb_plot_snr_timeseries
pycbc_pygrb_efficiency
pycbc_pygrb_exclusion_dist_table
)pycbc_pygrb_efficiency
does not perform any data quality veto (nor do the other scripts, but I would have to double check to make this statement firm) and this kind of vetoing needs to be placed somewhereThe text was updated successfully, but these errors were encountered: