-
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
Move dictionaries (and some classes) defined in SimTracker/TrackTriggerAssociation
and SimGeneral/TrackingAnalysis
to more proper packages
#45567
Conversation
Also remove map<int, int> from SimTracker/TrackTriggerAssociation as it exists already in StdDictionaries
These are already defined in the correct SimDataFormats/GeneratorProducts packages
…rAssociation These are already defined in SimDataFormats/TrackingAnalysis
These classes are persisted, and therefore must be defined in a data format package. These classes are associations, and therefore SimDataFormats/Associations seems like a reasonable place, especially given that it already depends on DataFormats/L1TrackTrigger.
The dependence on tt::Setup implies the tt::StubAssociation may not be persisted.
… SimDataFormats/Associations These seem to be related to the maps of those Ptr types alredy defined there.
…taFormats/Associations These are persisted, and therefore must be defined in a data format package. Since the pair and map are about associating TrackingParticle to PSimHits, the SimDataFormats/Associations seems like a reasonable place. An alternative place could have been SimDataFormats/TrackingAnalysis where TrackingParticle is defined.
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45567/41062
|
A new Pull Request was created by @makortel for master. It involves the following packages:
@Dr15Jones, @Martin-Grunewald, @aloeliger, @antoniovagnerini, @civanch, @cmsbuild, @epalencia, @makortel, @mdhildreth, @mmusich, @nothingface0, @rvenditti, @smuzaffar, @srimanob, @subirsarkar, @syuvivida, @tjavaid can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
type -changes-dataformats |
Comparison differences are related to #39803 |
+core |
+1 |
+1 |
+Upgrade |
@makortel , I see several duplication of the dictionaries. Do those need a fix ? |
@tjavaid Those are false positives caused by a deficiency of the checker script. Because the |
+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. @rappoccio, @mandrenguyen, @antoniovilela, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
#45423 (comment) pointed to potential issues in dictionaries defined in
SimTracker/TrackTriggerAssociation
andSimGeneral/TrackingAnalysis
. This PRmap<string, unsigned long long>
toDataFormats/StdDictionaries
map<int, int>
fromSimTracker/TrackTriggerAssociation
because it is already defined inDataFormats/StdDictionaries
map<int, HepMC...>
fromSimTracker/TrackTriggerAssociation
because they are already defined inSimDataFormats/GeneratorProducts
SimTracker/TrackTriggerAssociation
because they are already defined inSimDataFormats/TrackingAnalysis
TT{Cluster,Stub,Track}AssociationMap
classes and their dictionaries fromSimTracker/TrackTriggerAssociation
toSimDataFormats/Associations
.SimDataFormats/Associations
seemed like a reasonable placement.tt::StubAssociation
as transienttt::Setup
(defined inL1Trigger/TrackTrigger
) implies it (in its present form) can not be moved to a data format package, and therefore it must not be persistedstd::pair
s ofPtr<TTTrack>
andPtr<TrackingParticle>
fromSimGeneral/TrackingAnalysis
toSimDataFormats/Associations
std::map
s already defined there (by an earlier commit in this PR)std::pair<TrackingParticleRef, TrackPSimHitRef>
etc fromSimGeneral/TrackingAnalysis
toSimDataFormats/Associations
SimDataFormats/Associations
seemed like a reasonable placement.I am a little bit concerned though that the
SimDataFormats/Associations
package has become a kitchen sink, which means that some jobs may end up loading more shared libraries than necessary.Resolves cms-sw/framework-team#968
PR validation:
The modified packages compiled in 14_1_0_pre5 (I had to rebase afterwards but the conflict looked simple enough).