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
{{ message }}
This repository has been archived by the owner on Dec 9, 2024. It is now read-only.
However, the pT estimate in parseT5 is just the average of the T3 pT's (which is somewhat questionable per #214):
// Compute pt estimates from inner and outer tripletsconstfloat ptAv_in = abs(dr_in * k2Rinv1GeVf / sin((betaIn_in + betaOut_in) / 2.));
constfloat ptAv_out = abs(dr_out * k2Rinv1GeVf / sin((betaIn_out + betaOut_out) / 2.));
// T5 pt is average of the two pt estimatesconstfloat pt = (ptAv_in + ptAv_out) / 2.;
It's my understanding that the pT as computed for the T5s in the output NTuple are "more correct," and that both the pTs from the output NTuple and parseT5 are used and therefore giving inconsistent results. I am working on a PR (will include link here when available) that will add some additional branches for the GNN NTuple, so I can make the fix in that PR as well if desired.
The text was updated successfully, but these errors were encountered:
The pT for T5s in the output NTuple are computed as follows:
However, the pT estimate in
parseT5
is just the average of the T3 pT's (which is somewhat questionable per #214):It's my understanding that the pT as computed for the T5s in the output NTuple are "more correct," and that both the pTs from the output NTuple and
parseT5
are used and therefore giving inconsistent results. I am working on a PR (will include link here when available) that will add some additional branches for the GNN NTuple, so I can make the fix in that PR as well if desired.The text was updated successfully, but these errors were encountered: