Introduce a new type to keep track of individual event components

Open
  • Is something wrong?
#22 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
data

Research direction

Start by examining how edm4hep EventHeader is currently used to associate MCParticles with the same original hit. Define the information the replacement data type must preserve for downstream use, then update affected consumers and verify that EventHeader is no longer being used for this purpose.

Written by the indexing model from the issue text.

Description

Currently the edm4hep EventHeader is being abused as a way to store which MCParticles are associated with the same original hit. A different data type should made to hold the information which might be needed downstream.

Dominant language
C++
Stars
0
Forks
0
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eic/TimeframeBuilder

All issues in eic/TimeframeBuilder

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.