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

Fixing the seed check in CA iterations of FastSim #25758

Merged
merged 1 commit into from
Jan 29, 2019

Conversation

angirar
Copy link
Contributor

@angirar angirar commented Jan 24, 2019

CAHitNTupletGenerator::hitNtuplets() takes in empty std::vector of type 'OrderedHitSeeds' from the SeedFinderSelector and modifies its value depending upon whether hit combination has qualified for a seed or not. The size of the std::vector is fixed to be equal to the number of tracking regions in IntermediateHitDoublets. Therefore, the size of the elements inside this container should be checked rather than the size of the vector itself to see if seed candidate has passed.
Attaching below a plot of tracking efficiency vs pT for the 'Out of the box' tracks which demonstrates the effect of this change. In the plot, red curve is current FastSim (without this fix), blue is FastSim after this fix in place and black is FullSim. As can be seen, agreement of FastSim with FullSim will become much better after this change which indicates the proper implementation of the seed check.
trackingeffvspt

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@ssekmen
Copy link
Contributor

ssekmen commented Jan 24, 2019

@pmaksim1 , please watch.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-25758/8163

  • This PR adds an extra 12KB to repository

@cmsbuild
Copy link
Contributor

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

It involves the following packages:

FastSimulation/Tracking

@cmsbuild, @lveldere, @civanch, @ssekmen, @mdhildreth can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @matt-komm 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

@ssekmen
Copy link
Contributor

ssekmen commented Jan 24, 2019

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Jan 24, 2019

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/32821/console Started: 2019/01/24 12:59

@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-25758/32821/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 32
  • DQMHistoTests: Total histograms compared: 3097440
  • DQMHistoTests: Total failures: 1
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3097242
  • 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

@ssekmen
Copy link
Contributor

ssekmen commented Jan 29, 2019

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

@fabiocos
Copy link
Contributor

@ssekmen @angirar the plot included indeed show a change, but this is not visible from the limited size DQM test for this PR. Is it just a problem of statistics, or do you have an explanation wihy the test does not show any change?

@ssekmen
Copy link
Contributor

ssekmen commented Jan 29, 2019

@fabiocos , for our better understanding, which exact DQM plot are you referring to? Thanks.

@ssekmen
Copy link
Contributor

ssekmen commented Jan 29, 2019

please test workflow 2017.1

@cmsbuild
Copy link
Contributor

cmsbuild commented Jan 29, 2019

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/32876/console Started: 2019/01/29 11:55

@fabiocos
Copy link
Contributor

@ssekmen in the short list there are 2 FS workflows run in the PR test, and according to #25758 (comment) no difference is observed in DQM output. I now see that you are checking workflow 2017.1

@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-25758/32876/summary.html

@slava77 comparisons for the following workflows were not done due to missing matrix map:

  • /build/cmsbld/jenkins/workspace/compare-root-files-short-matrix/results/JR-comparison/PR-25758/2017.1_TTbar_13_UP17+TTbarFS_13_UP17+HARVESTUP17FS+MINIAODMCUP17FS

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 4 differences found in the comparisons
  • DQMHistoTests: Total files compared: 32
  • DQMHistoTests: Total histograms compared: 3097440
  • DQMHistoTests: Total failures: 1
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3097242
  • 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

@ssekmen
Copy link
Contributor

ssekmen commented Jan 29, 2019

The 2017.1 workflow test is done, but I realize that a direct comparison with the baseline cannot be automatically done. Is there a command to do this here? Otherwise we'll have to rely on @angirar 's comparison plot.

@fabiocos
Copy link
Contributor

@ssekmen a baseline plot should be manually produced for that based to my knowledge

@fabiocos
Copy link
Contributor

+1

a test was done by the author on workflows sensitive to this update, results presented in the documentation of this PR

@cmsbuild cmsbuild merged commit 902620c into cms-sw:master Jan 29, 2019
@angirar
Copy link
Contributor Author

angirar commented Jan 30, 2019

Thank you @ssekmen @fabiocos !
Just for the sake of future references, I am sharing the tracking validation results that I produced from 2017.1 workflow to test the changes. The plots contain FastSim with/without this fix alongwith results from FullSim Relval. You can find them here -
https://www.dropbox.com/sh/o6gs0a0f62ibree/AACfYAuKtN51IwM-P0Gq21XBa?dl=0

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

4 participants