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 Lorentz Angle from data base for pixel template CPE's in case of error #33495

Merged
merged 4 commits into from Apr 28, 2021

Conversation

OzAmram
Copy link
Contributor

@OzAmram OzAmram commented Apr 21, 2021

This PR updates the template reco CPE's (PixelCPETemplate and PixelCPEClusterRepair) to use the Lorentz Angle value from the database in the case of a template reconstruction error rather than using outdated hardcoded values. This has been a known issue for quite a while but has come up again during tests of the Phase 2 3D pixel integration (link).

In general these template reconstruction errors are quite rare, so the overall effect of these changes is expected to be quite small.

PR Testing

Testing has been done on phase 1 workflows with TTbar + Pu with 2024 conditions. The difference in hit residuals and tracking performance is very minor.
Slides here
Full tracking validation plots here
Link to Pixel Offline (virtual) meeting slides

Because of the update to the HLT configuration, the addOnTests have been run as well.

@OzAmram
Copy link
Contributor Author

OzAmram commented Apr 21, 2021

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33495/22227

  • This PR adds an extra 40KB to repository

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @OzAmram (Oz Amram) for master.

It involves the following packages:

HLTrigger/Configuration
RecoLocalTracker/SiPixelRecHits

@perrotta, @cmsbuild, @slava77, @Martin-Grunewald, @fwyzard, @jpata can you please review it and eventually sign? Thanks.
@mtosi, @OzAmram, @makortel, @felicepantaleo, @GiacomoSguazzoni, @JanFSchulte, @rovere, @VinInn, @Martin-Grunewald, @ferencek, @dkotlins, @gpetruc, @ebrondol, @threus, @tvami this is something you requested to watch as well.
@silviodonato, @dpiparo, @qliphy you are the release manager for this.

cms-bot commands are listed here

@mmusich
Copy link
Contributor

mmusich commented Apr 21, 2021

type bug-fix

@@ -129,11 +129,26 @@ def customiseFor2018Input(process):

return process

def customiseForPixelCPE(process):
Copy link
Contributor

@mmusich mmusich Apr 21, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@OzAmram I think it's customary to call these customisations with the PR number, e.g. customiseFor33495.
@Martin-Grunewald can comment if this is acceptable.

Copy link
Contributor

@perrotta perrotta Apr 22, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@OzAmram I think it's customary to call these customisations with the PR number, e.g. customiseFor33495.
@Martin-Grunewald can comment if this is acceptable.

@OzAmram please add the PR number as suggested by @mmusich : if you do so, once the PR will get merged, it will be easier for @Martin-Grunewald to identify the customization that can be removed

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok I just updated the name

@mmusich
Copy link
Contributor

mmusich commented Apr 21, 2021

@duartej can you please post in this thread the validation plots about the effect of this fix on the pixel template CPE reco for geometry T23?
Thanks.

@duartej
Copy link
Contributor

duartej commented Apr 22, 2021

@duartej can you please post in this thread the validation plots about the effect of this fix on the pixel template CPE reco for geometry T23?
Thanks.

Here they are. The plots below shows how the problematic population (marked within the circles in the left small plots) disappear after the fix is applied (right plots).

Screenshot from 2021-04-21 19-09-27
Screenshot from 2021-04-21 19-06-24

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33495/22242

  • This PR adds an extra 12KB to repository

@cmsbuild
Copy link
Contributor

Pull request #33495 was updated. @perrotta, @cmsbuild, @slava77, @Martin-Grunewald, @fwyzard, @jpata can you please check and sign again.

@mmusich
Copy link
Contributor

mmusich commented Apr 22, 2021

@cmsbuild, please test

@OzAmram
Copy link
Contributor Author

OzAmram commented Apr 26, 2021

Ok I just pushed a new commit with the updates based on the comments

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33495/22295

  • This PR adds an extra 32KB to repository

@cmsbuild
Copy link
Contributor

Pull request #33495 was updated. @perrotta, @cmsbuild, @slava77, @Martin-Grunewald, @fwyzard, @jpata can you please check and sign again.

@slava77
Copy link
Contributor

slava77 commented Apr 26, 2021

@cmsbuild please test

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2c9d6c/14589/summary.html
COMMIT: 1745048
CMSSW: CMSSW_12_0_X_2021-04-26-1100/slc7_amd64_gcc900
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/33495/14589/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

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

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 5494 differences found in the comparisons
  • DQMHistoTests: Total files compared: 38
  • DQMHistoTests: Total histograms compared: 2877605
  • DQMHistoTests: Total failures: 24715
  • DQMHistoTests: Total nulls: 21
  • DQMHistoTests: Total successes: 2852847
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 45.699 KiB( 37 files compared)
  • DQMHistoSizes: changed ( 140.53 ): 44.531 KiB Hcal/DigiRunHarvesting
  • DQMHistoSizes: changed ( 140.53 ): 1.172 KiB RPC/DCSInfo
  • DQMHistoSizes: changed ( 312.0 ): -0.004 KiB MessageLogger/Warnings
  • Checked 160 log files, 37 edm output root files, 38 DQM output files
  • TriggerResults: no differences found

@slava77
Copy link
Contributor

slava77 commented Apr 27, 2021

+reconstruction

for #33495 1745048

  • code changes are in line with the PR description and the follow up review
  • jenkins tests pass and comparisons with the baseline show small differences starting from tracking and propagating downstream; these confirm the tests provided in the PR description

@Martin-Grunewald
Copy link
Contributor

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2)

@silviodonato
Copy link
Contributor

+1

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.

None yet

8 participants