Skip to content
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

Use also the fourth hit of pixel track in SeedGeneratorFromProtoTracksEDProducer #26322

Closed

Conversation

makortel
Copy link
Contributor

@makortel makortel commented Apr 2, 2019

PR description:

I noticed that SeedGeneratorFromProtoTracksEDProducer does not include the possible fourth hit of a pixel tracks when creating TrajectorySeeds from pixel tracks (when useProtoTrackKinematics == False). This PR adds also the fourth hit.

In addition of affecting HLT with phase1 pixel, also phase0 HI tracking is affected, as TrackCleaner is used there for pixel tracks and the cleaner merges tracks.

PR validation:

I have here MTV plots (done in 10_4_0_patch1 with ttbar+PU 50 events on 2018 realistic conditions) comparing the effect with both the "offline MTV cuts" and "online MTV cuts"
https://mkortela.web.cern.ch/mkortela/tracking/validation/CMSSW_10_4_0_patch1_hlt/
The main effects seem to be

@mtosi @JanFSchulte

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 2, 2019

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 2, 2019

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-26322/9025

  • This PR adds an extra 16KB to repository

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 2, 2019

A new Pull Request was created by @makortel (Matti Kortelainen) for master.

It involves the following packages:

RecoTracker/TkSeedGenerator

@cmsbuild, @perrotta, @slava77 can you please review it and eventually sign? Thanks.
@felicepantaleo, @GiacomoSguazzoni, @rovere, @VinInn, @mschrode, @gpetruc, @ebrondol, @dgulhan this is something you requested to watch as well.
@davidlange6, @slava77, @fabiocos you are the release manager for this.

cms-bot commands are listed here

@makortel
Copy link
Contributor Author

makortel commented Apr 2, 2019

@cmsbuild, please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 2, 2019

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/33904/console Started: 2019/04/02 14:35

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 2, 2019

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 2, 2019

Comparison job queued.

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 2, 2019

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-26322/33904/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 236 differences found in the comparisons
  • DQMHistoTests: Total files compared: 32
  • DQMHistoTests: Total histograms compared: 3139747
  • DQMHistoTests: Total failures: 7477
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3132073
  • DQMHistoTests: Total skipped: 197
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 31 files compared)
  • Checked 133 log files, 14 edm output root files, 32 DQM output files

@slava77
Copy link
Contributor

slava77 commented Apr 4, 2019

I see differences in the run-1 reco for heavy ions, wf 140.53.
@makortel are these expected?
I thought that we did things correctly for phase-0 with this code.

@makortel
Copy link
Contributor Author

makortel commented Apr 4, 2019

Probably everything is a consequence of this
image
What I don't understand is how there can be 4 hits in the pixel track.

@VinInn
Copy link
Contributor

VinInn commented Apr 4, 2019

overlaps.
It requires seed-region rebuild though

@makortel
Copy link
Contributor Author

makortel commented Apr 4, 2019

@VinInn These are pixel tracks (used as seeds). IIRC we don't have any mechanism in (legacy) seeding to go beyond 3 hits.

I added some printouts and the pattern seems to be (e.g.) BPix1+BPix2+BPix3+FPix1.

@makortel
Copy link
Contributor Author

makortel commented Apr 4, 2019

I saw also one BPix1+BPix2+BPix3+BPix3

@makortel
Copy link
Contributor Author

makortel commented Apr 4, 2019

Seems that TrackCleaner (used for producing hiPixelTracks) actually merges tracks
https://github.com/cms-sw/cmssw/blob/master/RecoPixelVertexing/PixelLowPtUtilities/src/TrackCleaner.cc#L161
so that explains the existence of 4-hit pixel tracks with phase0 pixel. So the changes are expected (I'll update the description).

@cmsbuild cmsbuild removed the hold label May 15, 2019
@slava77
Copy link
Contributor

slava77 commented May 15, 2019

Now master moved to 11_0_X, maybe we could proceed with this PR?

in the meantime, was the impact of the changes discussed in the TSG already?
@mmasciov @mtosi @JanFSchulte

@slava77
Copy link
Contributor

slava77 commented May 15, 2019

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented May 15, 2019

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/236/console Started: 2019/05/15 22:55

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-15aafa/236/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 241 differences found in the comparisons
  • DQMHistoTests: Total files compared: 33
  • DQMHistoTests: Total histograms compared: 3212004
  • DQMHistoTests: Total failures: 11091
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3200579
  • DQMHistoTests: Total skipped: 334
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 32 files compared)
  • Checked 137 log files, 14 edm output root files, 33 DQM output files

@slava77
Copy link
Contributor

slava77 commented May 16, 2019

assign hlt

mostly because the most affected parts are in the code used by HLT.

@cmsbuild
Copy link
Contributor

New categories assigned: hlt

@Martin-Grunewald,@fwyzard you have been requested to review this Pull request/Issue and eventually sign? Thanks

@slava77
Copy link
Contributor

slava77 commented May 17, 2019

Here are some notes based on the jenkins tests.

For hltMerged:
The duplicate rate goes up by around a factor of 4
wfMattiPU50_plots_hltOnline_hltMerged_dupNfake

The number of layers with measurements in PXL is up (mostly around eta 1.5), but the number of hits goes down (most visible for eta > 2)
wfMattiPU50_plots_hltOnline_hltMerged_hits

more details from wf 250202.18 show that all the reduction in the number of hits is in PXF
wf250202 181_hltMerged_pxf_hits

It looks like the changes proposed with this PR are exposing some "features" of tracking that may need some mitigation

  • to get all relevant hits on the tracks
  • to reduce the duplicate rate

I think that this PR is incomplete.
Perhaps some tests that can show that the HLT rates remain roughly unchanged can be reassuring that there are no adverse consequences in a big picture.

@slava77
Copy link
Contributor

slava77 commented May 23, 2019

@makortel @JanFSchulte @mtosi @mmasciov
please let me know if there were any actions from the tracking side on this PR and my comments to it.
Thank you.

@slava77
Copy link
Contributor

slava77 commented May 30, 2019

@makortel @JanFSchulte @mtosi @mmasciov
please let me know if there were any actions from the tracking side on this PR and my comments to it.
Thank you.

ping

@JanFSchulte
Copy link
Contributor

@slava77 Sorry for the late reply. We discussed this and think that we would want to understand the effects of this PR better before merging it. However, as we are going to revamp the HLT tracking anyway for Run 3 we will look into this in that context later on. So this PR can be closed for the moment.

@makortel
Copy link
Contributor Author

It occurred to me that the effect of the bug is actually close to the "seed extension" approach that we studied in 2016, i.e. you take the pixel triplet seed and let the pattern recognition to figure out the right hit(s) on the fourth layer (except in this case the seeds are already guaranteed to have a compatible hit (with some definition) on the fourth layer, and the pattern recognition is not strictly required to include a hit from the fourth layer). I suppose that leads to the increase in duplicates.

Here are some old slides on the subject
https://indico.cern.ch/event/508493/contribution/3/attachments/1242946/1828945/slides.pdf
https://indico.cern.ch/event/527844/contributions/2161117/attachments/1269921/1881271/slides_phase1_20160509.pdf

The (pixel) seed extension was enabled in initialStep in #14621 (for the triplet propagation seeding), and was disabled (for the default sequence) in #16911 when the seeding approach was changed to CA. I don't think we ever tested the seed extension approach with CA.

@slava77
Copy link
Contributor

slava77 commented May 31, 2019

@makortel
if you agree with #26322 (comment)
please close this PR.

@makortel
Copy link
Contributor Author

Fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants