key4hep / key4hep/CLDConfig

How to propagate a track to the IP and to the calorimeter surface

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

Description

Hi all,
I am working with genfit to fit CLD tracks and I managed to create edm4hep::Tracks with two TrackStates: at first and last hit. In ILCsoft, I know that the trackState IP is calculated by propagating the track on [an additional surface within the beam pipe](https://github.com/key4hep/k4geo/blob/016b4fc408c98c217318141d0ef83cafa556cf1f/detector/other/Beampipe_o1_v01_geo.cpp#L624-L629). I wonder if it is possible to do the same with an edm4hep::Track with only two trackStates defined.

Thank you!

Andrea

Contributor guide

Open the contributing guide

Research direction

Start with the linked k4geo Beampipe_o1_v01_geo.cpp surface definition and review how genfit and edm4hep::Track represent the two existing track states. The issue names no CLDConfig file or test, so first identify the relevant propagation entry point. Done means establishing whether propagation to the IP and calorimeter surface is supported and documenting the required procedure or limitation.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.