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
Fix lostmidfrac in track MVA selection #17057
Conversation
@cmsbuild, please test |
The tests are being triggered in jenkins. |
A new Pull Request was created by @makortel (Matti Kortelainen) for CMSSW_9_0_X. It involves the following packages: RecoTracker/FinalTrackSelectors @cmsbuild, @cvuosalo, @slava77, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here #13028 |
Comparison job queued. |
type bugfix |
+1
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_9_0_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @smuzaffar |
+1 |
This PR fixes a small bug in the track MVA selection: in the MVA training, the so-called
lostmidfrac
(=nlost/(nvalid+nlost)) is correctly calculated in floating point, but in the MVA application side the fraction is calculated in integers (effectively leading the fraction to be always 0).Below are MTV plots for 1000 events of ttbar+35PU in 810pre16 for
The main effect is a small (~2 % in phase0, ~1 % in phase1) decrease in the fake rates.
Tested in 8_1_0_pre16, expecting changes described above in phase0 and phase1 workflows, no change expected in phase2 (as MVA selection is not used there yet).
@rovere @VinInn