cms-sw
Unphysical IsoTrack pt
Mirroring an issue opened under xpog gitlab https://gitlab.cern.ch/cms-nanoAOD/xpog-coordination/-/issues/40 so that this can be followed up on here.
There are events with unphysical IsoTrack_pt, e.g. in WF 2500.312 (ttbar UL18):
In that WF, all the 11 tracks with pt>6500 are flagged as isPFcand and isFromLostTrack.
A new Issue was created by @vlimant.
@antoniovilela, @Dr15Jones, @smuzaffar, @makortel, @rappoccio, @sextonkennedy can you please review it and eventually sign/assign? Thanks.
cms-bot commands are listed here
Is anywhere supposed to be a clamp of pt? Surely not at track level, 1/p(t) can be zero for what the track fit is concerned.
ah, this is just about large values of track pt. I misread as if there were NaNs and infinities when in gitlab 40 I suggested to open an issue here.
Now that I read this more correctly, I agree with Vincenzo. This is a non-issue
You're going too fast for me ; are you saying that 40TeV track are physical ?
You're going too fast for me ; are you saying that 40TeV track are physical ?
yes.
well, at least within uncertainties.
What does the ptError() return for these tracks?
If it comes out below 20% or so, I'd be motivated to follow up.
New categories assigned: reconstruction
@jfernan2,@mandrenguyen you have been requested to review this Pull request/Issue and eventually sign? Thanks
What does the
ptError()return for these tracks? If it comes out below 20% or so, I'd be motivated to follow up.
actually, compare qoverpError() with charge()/p() to stay on a Gaussian side of interpretation of uncertainties. A track with abs(qoverpError()*p())<0.2 and pt of 40TeV would be worth debugging.
@cms-sw/xpog-l2 relevant L2 should close this and propagate to https://gitlab.cern.ch/cms-nanoAOD/xpog-coordination/-/issues/40
New categories assigned: xpog
@ftorrresd,@hqucms you have been requested to review this Pull request/Issue and eventually sign? Thanks