key4hep / key4hep/CLDConfig

Split-up lcio collection patching and move it to where it is needed

Open
#79 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
0
Forks
21
PR merge metrics
No merged PRs in 30d

Description

As we are increasingly adding more Gaudi-native algorithms to the steering, there can also be conversions basically anywhere in the future. Therefore, instead of fixing up the lcio event just before the final conversion to edm4hep like now, we should patch the lcio event directly after the offending processors, such that the lcio event is always in a consistent state.

Contributor guide

Open the contributing guide

Research direction

Locate the current lcio event patching immediately before the final conversion to edm4hep, then identify the processors whose output requires patching. Move the patching to follow each offending processor and verify that the lcio event remains consistent wherever a conversion may occur.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.