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
[HGCAL] TICL in reconstruction #29081
Conversation
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29081/13966
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
tests can not be started without passing code-checks. |
Thanks, @slava77 I was not aware that code-checking was a requirement to run the tests. |
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29081/13975
|
A new Pull Request was created by @rovere (Marco Rovere) for master. It involves the following packages: Configuration/EventContent The following packages do not have a category, yet: RecoHGCal/Configuration @perrotta, @andrius-k, @kmaeshima, @schneiml, @kpedro88, @cmsbuild, @silviodonato, @franzoni, @jfernan2, @fioriNTU, @slava77, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
5f826c7
to
0db2fbc
Compare
The code-checks are being triggered in jenkins. |
Thank you @felicepantaleo Sizes blow up at 200 PU wrt the no-PU case in #29081 (comment) ... Do you have the total event size numbers for the two samples (before and after this PR: I don't see them in your logs), so that we can get an idea of the relative size increase in output? It was 8.6% increase overall for the no-PU case. |
unhold |
The overall
|
+1
|
+dqm |
+upgrade |
+operations |
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) |
+1 |
desc.add<edm::InputTag>("ticlCandidateSrc", edm::InputTag("ticlCandidateFromTrackstersProducer")); | ||
descriptions.add("pfTICLProducer", desc); | ||
desc.add<edm::InputTag>("ticlCandidateSrc", edm::InputTag("ticlCandidateFromTracksters")); | ||
descriptions.add("pfTICL", 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.
I think the automatic replacement of *Producer in the product names inlcuded this one by mistake, see #29446
Add TICL to Phase2 Reconstruction
This is a PR for the inclusion of TICL into the standard Phase2 reconstruction.
It will run TICL by default and save its output products into the output file for several data-tiers.
The objects reconstructed by TICL are not injected into ParticleFlow by default. A customization function has been provided (
injectTICLintoPF
) in order to swap the sim-Assisted reconstruction in HGCAL with the one coming from TICL.Non-optimal performances on complex events have to be expected out of the box (i.e. quite some development will have to be implemented on top of what is provided in this PR).
Results based on the development contained in this PR have been shown at a recent
HGCAL DPG
Meeting: linkA special thanks to @gouskos for helping during the development and testing phase.
PR validation:
The limited Matrix run w/o issues.