sPHENIX tracking discussion

[pinkenburg <pinkenburg AT bnl.gov>]

    Hi Tony,
    
    we need to revisit this - this will double the i/o.  I had some back
    and forth in 1008 about this - there doesn't seem to be a reason why
    this has to go through intermittent files.
    
    Chris

On 5/17/2023 11:27 PM, Ming Liu via sPHENIX-tracking-l wrote:

Thank you Tony for the summary, they look very reasonable, sorry I had to skip the discussions today for another mandatory LANL meeting.

 

Ming

 

-----

 

Dr. Ming Xiong Liu

P-3, MS H846

Physics Division

 

Office: 505.667.7125

Mobile: 505.412.7396

Los Alamos National Laboratory

 

 

From: sPHENIX-tracking-l <sphenix-tracking-l-bounces AT lists.bnl.gov> on behalf of Anthony Frawley via sPHENIX-tracking-l <sphenix-tracking-l AT lists.bnl.gov>
Reply-To: Anthony Frawley <afrawley AT fsu.edu>
Date: Wednesday, May 17, 2023 at 7:50 PM
To: "sphenix-tracking-l AT lists.bnl.gov" <sphenix-tracking-l AT lists.bnl.gov>
Subject: [Sphenix-tracking-l] Subsystem readout to reconstruction discussion

 

Hi All,

 

We had a discussion in the tracking software meeting this morning about what should be put in the data stream by each of the tracking detectors to forward the needed information to the track reconstruction code. Here is a brief summary of the results:

 

We picture three stages:

An intermediate file is written by each subsystem. An "event builder" picks up the intermediate files and creates an event-based file. The event-based file is read into Fun4All and tracks are reconstructed.

The primary goal today was to define what must be in the intermediate files, stage 1 above. For a discussion of step 2 we need other experts present. The general expectation is that there will be an event header for each assembled event that contains (at least) the GL1 trigger word and the full BCO times for each subsystem. Then the relative time offsets can be put in the hitset key for each subsystem.

 

For triggered data:

-------------------------

MVTX (Yasser):

GL1 trigger time

Full BCO start time for each strobe

Hitsets for each strobe

(The event header created later will contain the full GL1 and BCO times)

 

INTT (Joseph B):

GL1 trigger time

Full BCO time

Hitsets for each BCO

7 bit offset from GL1 time and address of hit in the hitset key

(The event header created later will contain the full GL1 and BCO times)

 

TPC (Jin and Takao):

GL1 trigger word

BCO start of time frame

Hitsets

 

TPOT (Hugo):

(Just like TPC in triggered mode)

GL1 trigger word

BCO start of time frame

Hitsets (Hugo: one hit will be selected from the time stream and kept).

 

There may be a need for changes to the hitset key structure by each subsystem. This should be made as a proposal and discussed beforehand, since there is potential for disruption when changing these.

 

The question was asked "who implements the event header?". We will look at what is available in the Fun4All framework as a starting point.

 

If I got anything wrong, please comment to the list.

 

Cheers

Tony

 

 

 

 

_______________________________________________ sPHENIX-tracking-l mailing list sPHENIX-tracking-l AT lists.bnl.gov https://lists.bnl.gov/mailman/listinfo/sphenix-tracking-l

_______________________________________________
sPHENIX-tracking-l mailing list
sPHENIX-tracking-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/sphenix-tracking-l
    
    
-- 
*************************************************************

Christopher H. Pinkenburg	;    pinkenburg AT bnl.gov
				;    http://www.phenix.bnl.gov/~pinkenbu

Brookhaven National Laboratory	;    phone: (631) 344-5692
Physics Department Bldg 510 C	;    fax:   (631) 344-3253
Upton, NY 11973-5000

*************************************************************