sPHENIX tracking discussion

[Hugo Pereira Da Costa <hugo.pereira-da-costa AT cea.fr>]

Hi Christof, all,

as discussed during today's meeting: the branch in which I maintain my own evaluators is there: https://github.com/hupereir/coresoftware/tree/Micromegas

The relevant code is coresoftware/simulation/g4simulation/g4eval/TrackingEvaluator_hp.*

There is a lot of stuff in there so really some cleanup is needed to get this in the official repo.

The relevant thing for the plots I produced today are:

TrackingEvaluator_hp::Container, which is the object I store on the node tree, that contains all the information (per event) out of which I make histograms.

In there: TrackStruct::List _tracks contains track base information (of type: TrackingEvaluator_hp::TrackStruct, which in turns contains a list of clusters

ClusterStruct::List

The cluster struct contains:

- cluster information (x, y, z, r, phi)

- the corresponding track information, retrieved from track fit statevector at the same "r" as the cluster

- the corresponding truth information

This is what I use to build my residuals.

The code to fill these variables from the Trkr (and Svtx) objects is all self contained in TrackingEvaluator_hp.cc.

Based on this, we can discuss what you would be interested to have in the official repo for the output format tests, what possible modifications to the association algorithm would be needed (there are some differences wrt official evaluators, in particular in the G4Hit  <-> cluster association) and I would take the corresponding code out.

Hugo