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

Extract timing for tracker-only muons #20705

Merged
merged 7 commits into from Oct 6, 2017
Merged

Conversation

drkovalskyi
Copy link
Contributor

Modified CSC/DT timing extraction code to handle cases of tracker-only muons. Timing distributions will change since muons that didn't have timing computed before will not have non-zero values. Many fake TrackerMuons have wrong timing, so having significant deviations from zero timing is expected. It's a critical development for high-pileup fake suppression. Needed for 94X.

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 1, 2017

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 1, 2017

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/PR-20705/1070

Code check has found code style and quality issues which could be resolved by applying a patch in https://cmssdt.cern.ch/SDT/code-checks/PR-20705/1070/git-diff.patch
e.g. curl https://cmssdt.cern.ch/SDT/code-checks/PR-20705/1070/git-diff.patch | patch -p1

You can run scram build code-checks to apply code checks directly

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 1, 2017

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 1, 2017

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/PR-20705/1071

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 1, 2017

A new Pull Request was created by @drkovalskyi for master.

It involves the following packages:

RecoMuon/MuonIdentification

@perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks.
@bellan, @abbiendi, @jhgoh, @echapon, @calderona, @HuguesBrun, @battibass, @trocino, @bachtis, @rociovilar this is something you requested to watch as well.
@davidlange6, @slava77 you are the release manager for this.

cms-bot commands are listed here

@perrotta
Copy link
Contributor

perrotta commented Oct 1, 2017

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 1, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/23343/console Started: 2017/10/01 11:41

@drkovalskyi
Copy link
Contributor Author

I see some segfaults that seem to be related to the changes. Will investigate.

@drkovalskyi
Copy link
Contributor Author

drkovalskyi commented Oct 1, 2017

I see some segfaults that seem to be related to the changes. Will investigate.

Seems to be false positive. Rerunning the matrix to confirm. It's all good.

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 1, 2017

-1

Tested at: 0a24544

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
829d9e6
You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20705/23343/git-log-recent-commits
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20705/23343/git-merge-result

You can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20705/23343/summary.html

I found follow errors while testing this PR

Failed tests: UnitTests

  • Unit Tests:

I found errors in the following unit tests:

---> test testTauEmbeddingProducers had ERRORS

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
829d9e6
You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20705/23343/git-log-recent-commits
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-20705/23343/git-merge-result

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 1, 2017

Comparison job queued.

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 4, 2017

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 4, 2017

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/PR-20705/1135

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 4, 2017

Pull request #20705 was updated. @perrotta, @cmsbuild, @slava77 can you please check and sign again.

@perrotta
Copy link
Contributor

perrotta commented Oct 4, 2017

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 4, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/23445/console Started: 2017/10/04 19:45

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 4, 2017

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 4, 2017

Comparison job queued.

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 4, 2017

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

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 86 differences found in the comparisons
  • DQMHistoTests: Total files compared: 26
  • DQMHistoTests: Total histograms compared: 2761357
  • DQMHistoTests: Total failures: 419
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2760751
  • DQMHistoTests: Total skipped: 187
  • DQMHistoTests: Total Missing objects: 0
  • Checked 107 log files, 10 edm output root files, 26 DQM output files

@perrotta
Copy link
Contributor

perrotta commented Oct 5, 2017

Adding arbitration allows a few extra muons getting correct timing info: below the same figures that were obtained before the last commit are taken with that latest addition for comparison

image

image

image

image

image

@perrotta
Copy link
Contributor

perrotta commented Oct 5, 2017

+1

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 5, 2017

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. @davidlange6, @slava77, @smuzaffar (and backports should be raised in the release meeting by the corresponding L2)

@slava77
Copy link
Contributor

slava77 commented Oct 5, 2017

below the same figures that were obtained before the last commit are taken with that latest addition for comparison

I could not understand which of the 5 plots below can be compared with what is "before the last commit".
Most of the plots have a different number of entries (which means muons or their reconstruction is different other than in the time direction)

@perrotta
Copy link
Contributor

perrotta commented Oct 5, 2017

Good catch Slava: indeed I did not remember that I used slimmed photons for the previous 2012B and 2017B figures instead of reco ones. Adjusted now in my last entry: you can see that the 2012B figures have now the same number of events in both figures.
On the other hand. the 2017B ones have far more entries in the last figure than in the previous one. This is unlikely due to the current PR, and I am trying to figure out what happened between CMSSW_9_4_X_2017-10-03-1100 and CMSSW_9_4_X_2017-10-04-1100

@perrotta
Copy link
Contributor

perrotta commented Oct 5, 2017

Ok, I got it, Different events were used for the two IBs, due to #20699 merged in the meanwhile
The comments I made on the comparison still hold also for this workflow, anyhow.

@davidlange6
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit c4961f5 into cms-sw:master Oct 6, 2017
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

5 participants