Skip to content
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 to new link types to keep compatibility with EDM4hep in the future #217

Merged
merged 2 commits into from
Jul 30, 2024

Conversation

tmadlener
Copy link
Contributor

BEGINRELEASENOTES

ENDRELEASENOTES

@tmadlener
Copy link
Contributor Author

@jmcarcell I would merge this after confirming it doesn't break anything in CI and then trigger the downstream build in key4hep/EDM4hep#341 again

@jmcarcell
Copy link
Member

Hmm I'm not sure if we should bother with an intermediate step, we are already incompatible with the last release so just switching to the new names shouldn't cause more issues, I guess you just want to see how it affects other repos? But then with the workflow is going to take a while 😃

@tmadlener
Copy link
Contributor Author

I can also just move to the new types directly, and check locally. That would then tie this PR strictly to the EDM4hep one.

@jmcarcell
Copy link
Member

Yeah, I think in general since we are not compatible anyway with an older version we can move directly for this and other repos. More work upfront but it will be done.

&CollectionMerger::mergeCollections<edm4hep::MCRecoTrackParticleAssociationCollection>;
m_map["edm4hep::RecoParticleVertexAssociationCollection"] =
&CollectionMerger::mergeCollections<edm4hep::RecoParticleVertexAssociationCollection>;
m_map["edm4hep::RecoMCParticleLinkCollection"] =
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here one could think that duplicating the lines to also have the old names in the map (mapped to merging the new ones) could be useful but files with the old names can have been produced with the latest release and are incompatible or with an older nightly which will also be incompatible.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In principle the new typenames should be enough because they come from the collection in any case. So even if an older version / name was on disk, by the time it reaches this place, we will only ever have to deal with the actual / new typename.

@tmadlener
Copy link
Contributor Author

Things are building locally with this and key4hep/EDM4hep#341 for me. So from my side we can go ahead and merge them both.

@tmadlener tmadlener changed the title Add legacy includes to keep things compiling Move to new link types to keep compatibility with EDM4hep in the future Jul 30, 2024
@tmadlener tmadlener merged commit a03713c into key4hep:main Jul 30, 2024
1 of 7 checks passed
@tmadlener tmadlener deleted the transparent-associations branch July 30, 2024 11:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants