-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
TkDQM: Introduce monitoring package for pixel SoA products #35965
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35965/26388 |
A new Pull Request was created by @sroychow (Suvankar Roy Chowdhury) for master. It involves the following packages:
The following packages do not have a category, yet: DQM/SiPixelPhase1Heterogeneous @emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @pmandrik, @pbo0, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
enable gpu |
@cmsbuild please test |
continue; | ||
float chi2 = tsoa.chi2(it); | ||
float phi = tsoa.phi(it); | ||
float zip = tsoa.zip(it); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what about tip?
if (nHits == 0) | ||
break; // this is a guard | ||
float pt = tsoa.pt(it); | ||
if (!(pt > 0.)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe some "optional" filter on quality could be useful.
(eventually a plot of quality itself)
hz->Fill(z); | ||
if (vsoa.ndof[iv] != 0) | ||
hchi2->Fill(vsoa.chi2[iv] / vsoa.ndof[iv]); | ||
hptv2->Fill(vsoa.ptv2[iv]); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what about track multiplicity?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am trying to understand if vsoa.ndof[iv]
does the right thing.
Why
float chi2[MAXVTX]; // vertices chi2 |
but
int32_t ndof[MAXTRACKS]; // vertices number of dof (reused as workspace for the number of nearest neighbours FIXME) |
isn't ndof
a property of the vertex ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
because of
reused as workspace for the number of nearest neighbours FIXME
so ndof IS a property of the vertex and == to number-of-associated-tracks-1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so it is safe to use vsoa.ndof[iv]
. @sroychow can you put it back?
Also we can just use ndof+1
instead of counting the tracks:
cmssw/DQM/SiPixelPhase1Heterogeneous/plugins/SiPixelPhase1MonitorVertexSoA.cc
Lines 95 to 99 in 15b20da
for (auto k = 0U; k < pixtrks.size(); ++k) { | |
if (vsoa.idv[k] == int16_t(vsoa.sortInd[iv])) | |
ntk++; | |
} | |
hntrks->Fill(ntk); |
right?
ibooker.cd(); | ||
ibooker.setCurrentFolder(topFolderName_); | ||
hnVertex = ibooker.book1D("nVertex", ";# of Vertex;#entries", 101, -0.5, 100.5); | ||
hx = ibooker.book1D("vx", ";Vertez x;#entries", 30, -30., 30); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the scale is a bit exaggerated in the transverse plane
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @sroychow just some minor additional comments.
SiPixelPhase1MonitorTrackSoA::~SiPixelPhase1MonitorTrackSoA() { | ||
// do anything here that needs to be done at desctruction time | ||
// (e.g. close files, deallocate resources etc.) | ||
edm::LogInfo("SiPixelPhase1MonitorTrackSoA") << ">>> Destroy SiPixelPhase1MonitorTrackSoA "; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it really needed?
This has a cost in production as the message is constructed anyway but dropped.
desc.add<std::string>("TopFolderName", "SiPixelHeterogeneous/PixelTrackSoA"); | ||
descriptions.add("monitorpixelTrackSoA", desc); | ||
// or use the following to generate the label from the module's C++ type | ||
//descriptions.addWithDefaultLabel(desc); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any reason why not using the default?
SiPixelPhase1MonitorVertexSoA::~SiPixelPhase1MonitorVertexSoA() { | ||
// do anything here that needs to be done at desctruction time | ||
// (e.g. close files, deallocate resources etc.) | ||
edm::LogInfo("SiPixelPhase1MonitorVertexSoA") << ">>> Destroy SiPixelPhase1MonitorVertexSoA "; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same comment as above.
desc.add<std::string>("TopFolderName", "SiPixelHeterogeneous/PixelVertexSoA"); | ||
descriptions.add("monitorpixelVertexSoA", desc); | ||
// or use the following to generate the label from the module's C++ type | ||
//descriptions.addWithDefaultLabel(desc); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as above.
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-26f94d/20220/summary.html GPU Comparison SummarySummary:
Comparison SummarySummary:
|
0e208d3
to
40300f0
Compare
address review comments add plot for ntracks associated simplify ntracks
5079789
to
95b41ec
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35965/26764 |
Pull request #35965 was updated. @emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @pmandrik, @pbo0, @rvenditti can you please check and sign again. |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-26f94d/20634/summary.html GPU Comparison SummarySummary:
Comparison SummarySummary:
|
+1 |
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. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
@sroychow in the last IBs there are errors in two RelVal workflows (136.8855 and 136.8885, see https://cmssdt.cern.ch/SDT/html/cmssdt-ib/#/relVal/CMSSW_12_2/2021-11-22-1100?selectedArchs=slc7_amd64_gcc900&selectedFlavors=X&selectedStatus=failed) which were originated by this PR:
Could you please have a look and provide a fix? |
PR description:
This PR introduces a new DQM subpackage called
SiPixelPhase1Heterogeneous
which will contain all the DQM modules to monitor the pixel SoA products. This proposal was presented in the last Central DQM meeting(talk). In this PR, only the modules to monitor Tracks and Vertices are added. The sequence defined in this package is added to theDQMHarvestPixelTracking
sequence.We plan to follow this up with several other PRs to this package:-
A PR to cms-bot for new package will be done.
PR validation:
Validated with the Patatrack PixelOnly wfs.
136.885502,136.888502,10824.502,10824.506,10842.502,10842.506,11634.502,11634.506,11650.502,11650.506
if this PR is a backport please specify the original PR and why you need to backport that PR:
NA