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 CAFs use the beam spill time as the time reference (as opposed to the trigger time). Currently the times saved in the CAF CRT Hit object SRCRTHit.t0,SRCRTHit.t1,SRCRTHit.time correctly use the beam time reference for both data and MC, as implemented in sbncode PR#323 and sbncode PR#358, however the CRT Hit time saved in the CAF CRT-PMT Match object SRCRTPMTMatch.matchedCRTHits.time still uses the trigger timestamp as a time reference. We should definitely have the two different collections of CRT Hit times on the same time scale so they can easily be compared.
To do:
Add srtrigger.trigger_within_gate to SRCRTPMTMatch.matchedCRTHits.time to shift the CRT-PMT Match CRT Hit time reference from trigger time to beam time reference.
Currently as is in the CAFs, the analyzer can easily fix the matched CRT Hit time by adding on this value manually, but it will be better to have all of the times using the same reference. I will make a PR to address this.
The text was updated successfully, but these errors were encountered:
The CAFs use the beam spill time as the time reference (as opposed to the trigger time). Currently the times saved in the CAF CRT Hit object
SRCRTHit.t0
,SRCRTHit.t1
,SRCRTHit.time
correctly use the beam time reference for both data and MC, as implemented in sbncode PR#323 and sbncode PR#358, however the CRT Hit time saved in the CAF CRT-PMT Match objectSRCRTPMTMatch.matchedCRTHits.time
still uses the trigger timestamp as a time reference. We should definitely have the two different collections of CRT Hit times on the same time scale so they can easily be compared.To do:
srtrigger.trigger_within_gate
toSRCRTPMTMatch.matchedCRTHits.time
to shift the CRT-PMT Match CRT Hit time reference from trigger time to beam time reference.Currently as is in the CAFs, the analyzer can easily fix the matched CRT Hit time by adding on this value manually, but it will be better to have all of the times using the same reference. I will make a PR to address this.
The text was updated successfully, but these errors were encountered: