-
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
add triplets using TOB and TIB4 for redundancy in TobTec and PIxelLess seeding steps respectively. reduce chi2-cut in MuonInOut #11492
Conversation
A new Pull Request was created by @VinInn (Vincenzo Innocente) for CMSSW_7_6_X. add triplets using TOB4 for redundancy It involves the following packages: RecoTracker/IterativeTracking @cmsbuild, @cvuosalo, @slava77 can you please review it and eventually sign? Thanks. |
@boudoul FYI |
@cmsbuild please test |
The tests are being triggered in jenkins. |
Comparison is ready The workflows 140.53 have different files in step1_dasquery.log than the ones found in the baseline. You may want to check and retrigger the tests if necessary. You can check it in the "files" directory in the results of the comparisons |
Pull request #11492 was updated. @cvuosalo, @monttj, @cmsbuild, @deguio, @slava77, @ggovi, @vadler, @vanbesien, @danduggan can you please check and sign again. |
apparently there where some newer PR integrated after last IB... (rebase worked!) |
I've updated the plots in https://mkortela.web.cern.ch/mkortela/tracking/validation/CMSSW_7_6_0_pre5_pr11492/index.html to contain the results from bb306e1. |
Thanks Matti. |
In general I think we have a problem with MixelTriplets (and piccolos/tobtec) |
Can this all be done better with knowledge of bad components? Meaning, to
|
|
I suppose no more changes to this PR are coming in a follow up to #11492 (comment) |
@slava77devel |
@slava77 I agree that for PU25 most probably would be better to roll-back the cut on MaxHIts. |
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_6_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar |
I've seen tob-tec fakes introduce problems at analysis level in run1 data. |
+1 |
add triplets using TOB and TIB4 for redundancy in TobTec and PIxelLess seeding steps respectively. reduce chi2-cut in MuonInOut
trying to mitigate inactive feds in TOB L3.
for an extensive description please refer to
https://indico.cern.ch/event/442135/session/1/contribution/18/attachments/1160196/1670021/tob3.pdf
for "ideal" MC results by @makortel
Plots are here:
https://mkortela.web.cern.ch/mkortela/tracking/validation/CMSSW_7_6_0_pre5_tob3/index.html
In the global picture there is ~no effect in efficiency, while fake rate increases by ~0.5-1 % (up to 3 % in barrel)
https://mkortela.web.cern.ch/mkortela/tracking/validation/CMSSW_7_6_0_pre5_tob3/ttbar_25ns_ootb/effandfake1.pdf
For tobTecStep itself also an efficiency increase is visible
https://mkortela.web.cern.ch/mkortela/tracking/validation/CMSSW_7_6_0_pre5_tob3/ttbar_25ns_tobTecStep/effandfake1.pdf
but it is so small (~0.05 %-unit) that it is not visible in the global picture.
some timing numbers:
reco 11.27 11.32 ~0.4 %
tracking 5.80 5.87 1 %
tobTecStep 0.426 0.463 8 %
*SeedsTripl 0.080 0.096 20 %
*TrackCandidates 0.256 0.276 8 %
*Tracks 0.028 0.028 ~0
(for other parts of tobTecStep the times are ~the same)
All times are real time per event as given by
process.options.wantSummary=True for a single run of 200 events of
TTbar+25ns PU on the same machine. For both cases the reported event
loop real time and CPU time are within <0.5 %, so I think the numbers
are good enough.