-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
update PackedCandidate::dzError to return what it should in track parameterization #45612
base: master
Are you sure you want to change the base?
update PackedCandidate::dzError to return what it should in track parameterization #45612
Conversation
…o::TrackBase; add dszError method and compatibility rules
…ng PackedCandidate::dzError
looks like bot is asleep/broken |
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45612/41112
|
A new Pull Request was created by @slava77 for master. It involves the following packages:
@antoniovagnerini, @cmsbuild, @ftorrresd, @hqucms, @jfernan2, @mandrenguyen, @nothingface0, @rvenditti, @syuvivida, @tjavaid, @vlimant can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
+1 Size: This PR adds an extra 92KB to repository Comparison SummarySummary:
|
type bug-fix |
Does it make sense to add to PackedCandidate a method returning correctly dzError (as present in TrackBase)? |
isn't this what this is doing? |
Given that we only plan to do the next re-Mini with CMSSW_15_X, probably there is no need to backport this? I am slightly worried that a backport would create more confusion than the benefits of correctness... |
enable nano |
please test |
I'm not sure I follow why a The main part of the PR is fixing the method that operates on already persisted data. If the change in |
Indeed that's the main concern. To me it is probably OK for a major release (15_X) which we will use for the next re-MINI campaign (where people would expect changes), but I am not sure if people would expect any changes like this between minor versions of existing releases. I guess a safer way is to remove |
The only practical way to be exposed is to throw an exception; simply removing will lead to the base class method It sounds like your argument is that at some point a wrong implementation becomes a more acceptable truth and we are in this case. |
-1 Failed Tests: AddOn AddOn Tests
Comparison SummarySummary:
NANO Comparison SummarySummary:
Nano size comparison Summary:
|
@hqucms @cms-sw/xpog-l2 |
@slava77 How about we throw an exception in the original |
should this new method be added to the
|
I think it only needs to be added to For me |
Uhm, I suspect that the design plans were to keep the code that works for objects deriving from The proposal now discussed is instead to break this, right? |
Unfortunately yes... But given that the calls of |
@slava77 @cms-sw/xpog-l2 @cms-sw/orp-l2 |
Milestone for this pull request has been moved to CMSSW_14_2_X. Please open a backport if it should also go in to CMSSW_14_1_X. |
ping (to make bot change milestone) |
(a belated note on the status) |
in response to #45598
prior to this PR
PackedCandidate
saved had a mis-named covariance elementdz
instead ofdsz
Details of all track parameters from TrackBase.h:
cmssw/DataFormats/TrackReco/interface/TrackBase.h
Lines 19 to 25 in fd00eb2
This PR updates the naming and corrects the returned value in
PackedCandidate::dzError
.For convenience,
dszError
is also kept available.I checked dependencies using the short matrix tests and initially throwing in the
PackedCandidate::dzError
. This revealed dependencies inPATIsolatedTrackProducer
,PackedCandidateTrackValidator
, and ML b and tau taggers.The tracking-related parts affected by the change:
PATIsolatedTrackProducer::produce
andIsolatedTrack
will now have a value saved indzError
matching the meaning.IsolatedTrack::dzError
I did not detect anything using this method in the matrix tests.diffDszError
which comparesTrack::dszError
should still match the candidate by now using directlydszError
anddiffDzError
should match as wellThis PR keeps ML b and tau taggers behavior unchanged, to keep values consistent with the training.
@cms-sw/btv-pog-l2 @cms-sw/tau-pog-l2