Transition to using PODIO link collections
- Dominant language
- C++
- Stars
- 4
- Forks
- 7
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 3
Description
We've introduced our first link in https://github.com/eic/EDM4eic/pull/108.
The upstream changes for reference are:
* https://github.com/key4hep/EDM4hep/commit/ac7ceab53cb59d8e47dc0dc74530bf86a2f8b1ba
* https://github.com/key4hep/EDM4hep/commit/d651cd6792eb29808c18f742280508735f040269
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing PR #108 and the two referenced EDM4hep commits to understand the initial link-collection change and the expected upstream model. Then identify which remaining EDM4eic model definitions need the same transition; done means the data model consistently uses PODIO link collections and its existing validation or build checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100