sphenix-tracking-l AT lists.bnl.gov
Subject: sPHENIX tracking discussion
List archive
Re: [Sphenix-tracking-l] Keeping track of bunch crossing
- From: "Liu, Ming Xiong" <mliu AT lanl.gov>
- To: Anthony Frawley <afrawley AT fsu.edu>, "sphenix-tracking-l AT lists.bnl.gov" <sphenix-tracking-l AT lists.bnl.gov>
- Cc: "Dean, Cameron" <cdean AT bnl.gov>, "Shi, Zhaozhong" <zhaozhongshi AT lanl.gov>, Yasser Corrales Morales <yasser.corrales.morales AT cern.ch>
- Subject: Re: [Sphenix-tracking-l] Keeping track of bunch crossing
- Date: Wed, 10 Nov 2021 05:05:58 +0000
Hi Tony and all,
For pp (and pA), are we going to have bunch crossing based event structure that contains all the vertices and tracks, or not? I think for spin related analyses, we also need to have beam-xing related spin information.
Cheers, Ming
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>
Hi All,
In pp running we will want to keep track of bunch crossing number for every track. At the least, we need to know if the track was in an event that is fully contained in the TPC.
We could either: a) add a signed int to the track object. b) add a signed int to the vertex object.
In case b), the bunch crossing would have to be kept in a map on the node tree for all tracks, so that the final vertexer could look it up and add it to the vertex object.
Case b) would use less disk space. But it would possibly be more of a pain for analyzers to have to look up which vertex a track belongs to, and get the bunch crossing from that.
On the other hand, perhaps all analyses will proceed vertex by vertex anyway, in which case, b) would be convenient enough.
For context, a pp event with 7 microseconds additional readout time will have ~ 15-20 vertices from events fully contained in the TPC. These will be distributed over ~ 70 bunch crossings.
Thoughts?
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] Keeping track of bunch crossing,
Anthony Frawley, 11/09/2021
- <Possible follow-up(s)>
-
Re: [Sphenix-tracking-l] Keeping track of bunch crossing,
Liu, Ming Xiong, 11/10/2021
-
Re: [Sphenix-tracking-l] Keeping track of bunch crossing,
Anthony Frawley, 11/10/2021
-
Re: [Sphenix-tracking-l] Keeping track of bunch crossing,
Osborn, Joe, 11/10/2021
-
Re: [Sphenix-tracking-l] Keeping track of bunch crossing,
Dean, Cameron, 11/10/2021
-
Re: [Sphenix-tracking-l] Keeping track of bunch crossing,
pinkenburg, 11/10/2021
-
Re: [Sphenix-tracking-l] Keeping track of bunch crossing,
Anthony Frawley, 11/10/2021
- Re: [Sphenix-tracking-l] Keeping track of bunch crossing, pinkenburg, 11/10/2021
- Re: [Sphenix-tracking-l] Keeping track of bunch crossing, Liu, Ming Xiong, 11/10/2021
- Re: [Sphenix-tracking-l] Keeping track of bunch crossing, Anthony Frawley, 11/10/2021
- Re: [Sphenix-tracking-l] Keeping track of bunch crossing, Osborn, Joe, 11/10/2021
-
Re: [Sphenix-tracking-l] Keeping track of bunch crossing,
Anthony Frawley, 11/10/2021
-
Re: [Sphenix-tracking-l] Keeping track of bunch crossing,
pinkenburg, 11/10/2021
-
Re: [Sphenix-tracking-l] Keeping track of bunch crossing,
Dean, Cameron, 11/10/2021
-
Re: [Sphenix-tracking-l] Keeping track of bunch crossing,
Osborn, Joe, 11/10/2021
-
Re: [Sphenix-tracking-l] Keeping track of bunch crossing,
Anthony Frawley, 11/10/2021
Archive powered by MHonArc 2.6.24.