Project

General

Profile

Feature #1840

Changes to PrimaryChain Datastructure object

Added by Greis, Jan about 5 years ago.

Status:
Open
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
15 April 2016
Due date:
% Done:

0%

Estimated time:
Workflow:
New Issue

Description

I've redesigned the PrimaryChain object (which in its previous form was not of much use) to function as a way of structuring everything that goes into a final track and making retrieval of these components easy.

The idea is that it stores all the spacepoints (TOFs, Ckovs, KL) and Tracks (Trackers, EMR) that went into global reconstruction and then separately all the tracks that are created while the data moves through global reconstruction (e.g. hypothesis tracks from track matching, PID'd tracks, later fitted tracks, as both separate upstream and downstream, as well as through tracks) which are retrievable by mapper name.

I've attached both the DS and Processor files for it and would like to ask whether people think this is good like this or if you have any comments, suggestions?
Also, I have tried to follow the instructions on http://micewww.pp.rl.ac.uk/maus/MAUS_latest_version/maus_user_guide/node14.html but if you spot any issues please let me know.


Files

PrimaryChain.cc (3.65 KB) PrimaryChain.cc Greis, Jan, 15 April 2016 11:55
PrimaryChain.hh (3.21 KB) PrimaryChain.hh Greis, Jan, 15 April 2016 11:55
PrimaryChainProcessor.cc (1.77 KB) PrimaryChainProcessor.cc Greis, Jan, 15 April 2016 11:55
PrimaryChainProcessor.hh (1.8 KB) PrimaryChainProcessor.hh Greis, Jan, 15 April 2016 11:55

No data to display

Also available in: Atom PDF