-
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
Update event content structure in RecoEcal and RecoVertex #29299
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29299/14363
|
A new Pull Request was created by @jeongeun (JeongEun Lee) for master. It involves the following packages: RecoEcal/Configuration @perrotta, @slava77, @christopheralanwest, @tocheng, @cmsbuild, @tlampen, @pohsun can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+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.
These are all the comments I have for this PR
'keep recoSuperClusters_correctedHybridSuperClusters_*_*', | ||
# Endcap clusters | ||
'keep *_multi5x5SuperClusters_*_*', | ||
'keep recoSuperClusters_multi5x5SuperClusters_*_*', |
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 a subset of the line above... But ok, it doesn't hurt
# Particle Flow superclusters | ||
'keep *_particleFlowSuperClusterECAL_*_*', | ||
'keep *_particleFlowSuperClusterOOTECAL_*_*', | ||
# DROP statements # not used |
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.
How did you verify that these drop statements are not used?
@afiqaize @SohamBhattacharya
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.
By my event content comparison check, these drop statements don't really act on the RECO/FEVT event content. When I checked every event content without these drop statements like this modified file, there is no difference in event contents.
@afiqaize @SohamBhattacharya Please confirm if these 4 drop statements can be removed.
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.
For now, it would be good to have these drop statements in RecoEcalRECO PSets as the original. I'll not remove them. It will safe in the new commit.
# Barrel clusters | ||
'keep *_correctedHybridSuperClusters_*_*', | ||
# Endcap clusters | ||
'keep *_multi5x5*_*_*', |
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.
Can this get expanded without the wild card (and without blowing the list too much)?
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.
If this is in FEVT, I think that an exception can be made, considering that this datatier is more debug-like than something for sustained production
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've found 5 modules in RECO/FEVT event contents :
multi5x5BasicClustersCleaned
multi5x5SuperClusters
multi5x5SuperClustersCleaned
multi5x5SuperClustersWithPreshower
multi5x5PreshowerClusterShape
with different types and labels.
vector<reco::CaloCluster> multi5x5BasicClustersCleaned * *
vector<reco::SuperCluster> multi5x5BasicClustersCleaned * *
vector<reco::CaloCluster> multi5x5SuperClusters * *
vector<reco::SuperCluster> multi5x5SuperClusters * *
vector<reco::PreshowerCluster> multi5x5SuperClustersWithPreshower * *
vector<reco::SuperCluster> multi5x5SuperClustersWithPreshower * *
vector<reco::PreshowerClusterShape> multi5x5PreshowerClusterShape * *
'keep *_correctedHybridSuperClusters_*_*', | ||
# Endcap clusters | ||
'keep *_multi5x5*_*_*', | ||
'keep *_correctedMulti5x5*_*_*') |
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 there anything else beside correctedMulti5x5SuperClustersWithPreshower
already saved in the AOD event content?
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.
No, only vector<reco::SuperCluster> "correctedMulti5x5SuperClustersWithPreshower" "" "RECO"
exists in AOD event content (also in RECO/FEVT event contents). So this line is redundant so it can be deleted.
please test |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1
|
+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. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Update event content definitions to explicitly have RECO to be a superset of AOD and for FEVT to be a superset of RECO. Clean up 'drop' not really used in RecoEcalRECO.
(The previous tasks are PR#29025, PR#29158, and PR#29225.)
3 files changed :
+RecoEcal_EventContent_cff.py
+RecoVertex_EventContent_cff.py
+BeamSpot_EventContent_cff.py
PR validation:
Event Content comparison check was also done and there is no change with these updates.
Tested in CMSSW_11_1_X_2020_03-23-1100, the basic test all passed in the CMSSW PR instructions.