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

Addition of number of optical hits above a specific threshold to the CRTPMT Data product #788

Open
francescopoppi opened this issue Dec 10, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@francescopoppi
Copy link
Contributor

As the title suggest, we have applying spcific threhsold requirements to the selection of the Optical Hits above threshold that were outdate (coming from Run1). We need to make this variable a member of the data product os that analyzers can choose their cuts.
Few things need to be done in this order:

  1. Addition of the variable: nOpHitOverThreshold to the dataproduct in sbnobj;
  2. Addition of the variable: nOpHitOverThreshold to the CAF Standard Record in sbnanaobj;
  3. Need to discuss with Trigger experts which threshold conditions make sense for each Run;
  4. In icaruscode we need to modify the current producer in order to fill the nOpHitOverThreshold variable;
  5. Fill the SR object with the newly included nOpHitOverThreshold.
@francescopoppi francescopoppi added the enhancement New feature or request label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants