Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data vetoes in the onsource #4981

Open
pannarale opened this issue Dec 9, 2024 · 0 comments
Open

Data vetoes in the onsource #4981

pannarale opened this issue Dec 9, 2024 · 0 comments

Comments

@pannarale
Copy link
Contributor

The open box page involves the following executables:

  1. pycbc_pygrb_page_tables
  2. pycbc_pygrb_plot_snr_timeseries
  3. pycbc_pygrb_efficiency
  4. (and pycbc_pygrb_exclusion_dist_table)
  5. (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.
@pannarale pannarale converted this from a draft issue Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

1 participant