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
DataFormats/ParticleFlowReco - remove unused data formats #26670
DataFormats/ParticleFlowReco - remove unused data formats #26670
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-26670/9630
|
A new Pull Request was created by @guitargeek (Jonas Rembser) for master. It involves the following packages: DataFormats/ParticleFlowReco @perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
We can remove DF classes including dictionaries for transient DFs (something that was never saved in production jobs). For the DFs that were saved in the past, but are no longer expected to be consumed, we can make a dummy dictionary to allow reading the old files. For this: add a Only if the old data is still needed for analysis it is worth to keep the DF implementation. |
@cmsbuild please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Hi @slava77, sorry I don't happen to know anything about how the classes were used, as they are from the "Snapshot of CMSSW_6_2_0_pre8" commit so it's hard to find some information in an associated PR or something. Maybe @hatakeyamak, @jpata or @bendavid are familiar with it? The dummy dictionary sounds like a good option to me anyhow, as it probably does not add any compile time whatsoever, no? Then I would not see any drawback. |
On 5/16/19 3:17 PM, Jonas Rembser wrote:
The dummy dictionary sounds like a good option to me anyhow, as it
probably does not add any compile time whatsoever, no? Then I would not
see any drawback.
I think that it will be OK to add them only after we see problems in I/O.
IIUC, none of the regular production samples have these classes persisted.
|
Comparison is ready Comparison Summary:
|
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:
Follow up on #26184, where a lot of the
PFClusterTools
code was removed. Actually, the removed code relied on several DataFormats with are now obsolete and should be removed as well.By the way, are there any CMSSW policies on how we treat the DataFormats? Is their removal allowed, or should they stick in the release forever to ensure backwards compatibility of ROOT files?
PR validation:
Code compiles and local matrix tests pass.