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
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:
Addition of the variable: nOpHitOverThreshold to the dataproduct in sbnobj;
Addition of the variable: nOpHitOverThreshold to the CAF Standard Record in sbnanaobj;
Need to discuss with Trigger experts which threshold conditions make sense for each Run;
In icaruscode we need to modify the current producer in order to fill the nOpHitOverThreshold variable;
Fill the SR object with the newly included nOpHitOverThreshold.
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: