-
Notifications
You must be signed in to change notification settings - Fork 488
Extend TOF Event Time maker for analysis #7652
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
Conversation
|
@noferini Here it is! |
|
For reference this is used in AliceO2Group/O2Physics#300 |
- Add authors - Add track multiplicity used for the TOF event time estimation Align AOD maker behaviour for trackTime - Update trackTime - Fix call to exp times Expand log axis in HistogramRegistry
| extraInfoHolder.trackTime = (tofCl.getTime() - tofInt.getTOF(trackPar.getPID())) * 1e-3; // tof time in \mus, FIXME: account for time of flight to R TOF | ||
| extraInfoHolder.trackTimeRes = 200e-3; // FIXME: calculate actual resolution (if possible?) | ||
| const float massZ = o2::track::PID::getMass2Z(trackPar.getPID()); | ||
| const float energy = sqrt((massZ * massZ) + (extraInfoHolder.tofExpMom * extraInfoHolder.tofExpMom)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why using m/Z and not M ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Ruben, it is to match the p/z measurement
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, makes sense, thanks.
|
Hi @shahor02, |
Align AOD maker behaviour for trackTime
Expand log axis in HistogramRegistry