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
TICL: Create PF candidates as output of TICL #28116
Conversation
…into from-CMSSW_11_0_0_pre9
…CL PF validation; and add a bit of documentation
…o be re-added later w/ modifier); avoid setting charge for neutrals
The code-checks are being triggered in jenkins. |
please test workflow 20493.52 |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28116/12139 |
The tests are being triggered in jenkins. |
Comparison is ready Comparison Summary:
|
+1 |
+upgrade |
@steggema , I am belatedly late in jumping in this PR. Looking at the thread I see this comment from @smuzaffar which suggests to move all headers into the I see that this PR does not fail the headers check any more, and therefore it should be considered as technically fixed. However, I would like to get confirmation from @smuzaffar that he is fine with the current arrangements. or if it would still be preferable to move to |
#include "RecoHGCal/TICL/interface/TracksterMomentumPluginBase.h" | ||
#include "FWCore/Framework/interface/MakerMacros.h" | ||
|
||
EDM_REGISTER_PLUGINFACTORY(TracksterMomentumPluginFactory, "TracksterMomentumPluginFactory"); |
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.
this is wrong, we shoud never register a plugin from a shared library
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.
@smuzaffar this is registering a factory, not a plugin. Doesn't this need to be in a shared library to be accessible?
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.
ah did not realize that @kpedro88 . Looking at cmssw , yes plugin factories are ok to be in shared libs.
#include "RecoHGCal/TICL/interface/TracksterTrackPluginBase.h" | ||
#include "FWCore/Framework/interface/MakerMacros.h" | ||
|
||
EDM_REGISTER_PLUGINFACTORY(TracksterTrackPluginFactory, "TracksterTrackPluginFactory"); |
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.
this is wrong, we shoud never register a plugin from a shared library
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.
ignore the above comment
@perrotta From the updated responses, I understand that there's no action required from my side. Please let me know if I misunderstood. |
From the last time I checked, pre11 is due today and it would be a pity if this Pr is not part of it. |
Yes, as far as I understand @smuzaffar does not ask any more to move everything into the plugin directory and remove the top level Buildfile. |
true, PR is its current state looks good. No need to move top level buildfile or interface, src files. headers file checks look good too. |
The footprint on CPU time and output size of this PR is quite limited, at least for the non PU workflow 20493.52
|
+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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR prepares the integration of TICL into CMS Particle Flow by creating PFCandidates that can subsequently be integrated in the central CMS PF collection. It does so with the help of an intermediate data format, the TICLCandidate, by converting the TICL output (a list of tracksters) into TICLCandidates, and subsequently the TICLCandidates into regular PFCandidates. It also adds DQM plots for the such-produced PFCandidates.
Presentations were given in a RECO/AT meeting, https://indico.cern.ch/event/841640/contributions/3539177/attachments/1896768/3129567/2019_08_23_reco.pdf, and in an HGCAL DPG meeting, https://indico.cern.ch/event/849004/contributions/3567562/attachments/1910534/3156782/2019_09_18_hgcal_dpg.pdf
PR validation:
The workflow has been validated by enabling TICL as defined in RecoHGCal/TICL/python/ticl_iterations.py and checking the DQM output.
if this PR is a backport please specify the original PR: -
@rovere @felicepantaleo @bendavid @hatakeyamak (HGCal RECO and PF)