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

[Pixel 3D Digitizer] Fix wrong channel assignation #30446

Merged
merged 2 commits into from Jul 2, 2020

Conversation

duartej
Copy link
Contributor

@duartej duartej commented Jun 29, 2020

PR description:

Fix bug in channel assignation, by using PixelDigi::pixelToChannel function instead of PixelTopology::channel.

@emiglior and @skinnari as conveners of the upgrade simulation group are aware and agree.
cc: @suchandradutta

PR validation:

This PR is affecting the Phase 2 upgrade 3D geometry only, checked with workflows 26234.0 and 24834.0 succesfully.

if this PR is a backport please specify the original PR and why you need to backport that PR:

Not a backport

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30446/16568

Code check has found code style and quality issues which could be resolved by applying following patch(s)

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30446/16569

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @duartej (Jordi Duarte Campderros) for master.

It involves the following packages:

SimTracker/SiPhase2Digitizer

@cmsbuild, @civanch, @kpedro88, @mdhildreth can you please review it and eventually sign? Thanks.
@makortel, @mtosi, @GiacomoSguazzoni, @JanFSchulte, @rovere, @VinInn, @ebrondol, @threus, @dgulhan this is something you requested to watch as well.
@silviodonato, @dpiparo you are the release manager for this.

cms-bot commands are listed here

@mmusich
Copy link
Contributor

mmusich commented Jun 29, 2020

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Jun 29, 2020

The tests are being triggered in jenkins.

@mmusich
Copy link
Contributor

mmusich commented Jun 29, 2020

@duartej
I had a look to your attached presentation, the lines which you claim are giving inconsistent results for the phase1 digitizer are actually protected by a conditional inclusions

#ifdef TP_DEBUG
mp = MeasurementPoint(float(ix), float(iy));
LocalPoint lp = topol->localPosition(mp);
chan = topol->channel(lp);
LogDebug("Pixel Digitizer") << " pixel " << ix << " " << iy << " - "
<< " " << chan << " " << ChargeFraction << " " << mp.x() << " " << mp.y() << " "
<< lp.x() << " " << lp.y() << " " // givex edge position
<< chan; // edge belongs to previous ?
#endif

in any case in the phase1 case the class PixelTopology is used, while here you are using Phase2TrackerTopology

@duartej
Copy link
Contributor Author

duartej commented Jun 29, 2020

@duartej
I had a look to your attached presentation, the lines which you claim are giving inconsistent results for the phase1 digitizer are actually protected by a conditional inclusions

#ifdef TP_DEBUG
mp = MeasurementPoint(float(ix), float(iy));
LocalPoint lp = topol->localPosition(mp);
chan = topol->channel(lp);
LogDebug("Pixel Digitizer") << " pixel " << ix << " " << iy << " - "
<< " " << chan << " " << ChargeFraction << " " << mp.x() << " " << mp.y() << " "
<< lp.x() << " " << lp.y() << " " // givex edge position
<< chan; // edge belongs to previous ?
#endif

in any case in the phase1 case the class PixelTopology is used, while here you are using Phase2TrackerTopology

ahh, yes, you are right. I can see it is using the pixelToChannel function there as well.

However, regarding the Phase2TrackerTopology, it is actually PixelTopology (see https://github.com/cms-sw/cmssw/blob/master/SimTracker/SiPhase2Digitizer/plugins/Phase2TrackerDigitizerFwd.h#L12, which is included in https://github.com/cms-sw/cmssw/blob/master/SimTracker/SiPhase2Digitizer/plugins/Phase2TrackerDigitizerAlgorithm.h#L17).

@cmsbuild
Copy link
Contributor

+1
Tested at: 4df841c
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d13e10/7480/summary.html
CMSSW: CMSSW_11_2_X_2020-06-28-0000
SCRAM_ARCH: slc7_amd64_gcc820

@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-d13e10/7480/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 8 differences found in the comparisons
  • DQMHistoTests: Total files compared: 36
  • DQMHistoTests: Total histograms compared: 2778915
  • DQMHistoTests: Total failures: 7
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2778858
  • DQMHistoTests: Total skipped: 50
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 35 files compared)
  • Checked 152 log files, 16 edm output root files, 36 DQM output files

@civanch
Copy link
Contributor

civanch commented Jun 30, 2020

+1

@kpedro88
Copy link
Contributor

+upgrade

@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 (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

6 participants