key4hep / key4hep/k4SimDelphes
Particle ID meta data should be populated
- Dominant language
- C++
- Stars
- 6
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
We fill a few ParticleID collections (after #131). However, we do not store any additional information on the contents of these collections (apart from the collection name). We should store the necessary information to make the usage of the `edm4hep::utils::PIDHandler` possible with all features.
This will most likely require changing the API of the converter slightly as we need to be able to get the collected metadata out and into the metadata Frame that we can create in `DelphesMain`. Framework integrated usage will require some more thinking as it's not entirely clear how we can easily put the necessary information into the whole machinery again.
Contributor guide
Research direction
Start by tracing the converter API and the metadata Frame created in DelphesMain, then review how edm4hep::utils::PIDHandler consumes ParticleID metadata. Determine how collected metadata can pass through both normal conversion and framework-integrated usage. Done means all ParticleID collections expose the information required by PIDHandler without leaving the API or framework path unresolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100