sPHENIX MAPS tracker discussion

[Sanghoon Lim <shlim AT rcf.rhic.bnl.gov>]

Hi Ming and all,

Sorry for continuous emails, but I have additional plot to share the probability of MVTX/INTT cluster association for reconstructed tracks from out-of-time events. Here I specifically check the time of track generation to select tracks from out-of-time events. Interesting thing is the probability to have 2 MVTX clusters (9.1e-5) is quite lower than the probability to have 2 INTT clusters (1.1e-3). Based on the plot, the additional rejection from N_MVTX_Clus>=2 to N_MVTX_Clus>=2 && N_INTT_Clus>=1 is 9.1e-5 of reconstructed tracks from out-of-time events. Keep in mind that this is *full tracking with true seed vertex*. Here I used +/- 5 us timing window for MVTX.

Best,

Sanghoon

Attachment: sPHENIX_sim_pileup_only_pp_nclus_maps_intt_4INTT_pp.pdf
Description: Adobe PDF document

---------------------------------------------
> Sanghoon LIM
> University of Colorado Boulder

> Physics Department

>
> sanghoon.lim AT colorado.edu

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

On Dec 2, 2018, at 6:36 AM, Sanghoon Lim <shlim AT rcf.rhic.bnl.gov> wrote:

Hi Ming and Sookhyun,

Thanks for the discussion.

When you look at bottom plots in page 6-7 of my slides, you can check the pileup rejection with requirements of N_INTT_Cluster>=2 or N_MVTX_Cluster>=2. You can see the performance of out-of-time rejection is better with the requirement of N_MVTX_Cluster>=2. I need to check the N_INTT_Cluster distribution for tracks of N_MVTX_Cluster>=2, but I guess most of tracks already have associated INTT cluster. I'll add the distribution of N_INTT_Cluster for those tracks then this will answer the Sookhyun's question. However, when requiring N_INTT_Cluster>=2, there's still a small change to mis-associate between out-of-time TPC track and intime INTT clusters. The situation in full tracking based on true seed vertex is a bit different from the seed vertexing. Although there are pileup events in MVTX, but associating with MVTX around a good seed vertex show a quite good rejection.

Best,

Sanghoon

---------------------------------------------
> Sanghoon LIM
> University of Colorado Boulder

> Physics Department

>
> sanghoon.lim AT colorado.edu

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

On Dec 1, 2018, at 9:12 PM, Ming Liu <ming AT bnl.gov> wrote:

Sanghoon,

Nice work, very encouraging results. 

On your slide #8, you showed the tracking efficiency is fairly insensitive to INTT deadmap (4% vs 8%). Is this due to the fact you only require N_INTT_Cluster >=1 or the N_MVTX_Clust >=2 effectively removes most of the out-of-time tracks? Probably a combination of these two, I guess.  

 

I am wondering whether 4INTT_PP can already provide sufficient redundancy or we still like to have the 3^rdlayer INTT? 

 

Cheers,

Ming  

 

-- 

Ming Xiong Liu

P-25, MS H846                     TEL: 505-667-7125 

Physics Division                            631-344-7821(BNL)

LANL                                               630-840-5708(FNAL)

Los Alamos, NM 87545      FAX:  505-665-7020

 

 

From: Sanghoon Lim <shlim AT rcf.rhic.bnl.gov>
Date: Saturday, December 1, 2018 at 8:40 PM
To: Christof Roland <christof.roland AT cern.ch>
Cc: Sanghoon Lim <shlim AT rcf.rhic.bnl.gov>, Mickey Chiu <chiu AT bnl.gov>, Jin Huang <jhuang AT bnl.gov>, Ross Corliss <rcorliss AT mit.edu>, "Todoroki, Takahito" <todoroki AT rcf.rhic.bnl.gov>, Carlos Perez <carlos.perezlara AT stonybrook.edu>, "Frawley, Anthony" <afrawley AT fsu.edu>, "Chiu, Mickey" <chiu AT rcf.rhic.bnl.gov>, Molly Taylor <mitay AT mit.edu>, Sookhyun Lee <dr.sookhyun.lee AT gmail.com>, "Ming Liu (BNL)" <ming AT bnl.gov>, sphenix-mvtx-l <sphenix-maps-l AT lists.bnl.gov>, <sphenix-intt-l AT lists.bnl.gov>
Subject: Re: Next Tracker Task Force Meeting

 

Hi all,

 

I've checked a couple of things based on the last meeting and uploaded slides with the update and a few performance plots.

 

https://indico.bnl.gov/event/5370/contributions/25249/attachments/20902/28338/sPHENIX_IDTF_shlim_20181201.pdf

 

The pileup event generator also put events in the same beam crossing of the signal event to take into account multiple collisions in one beam crossing. The remaining tracks from pileup events even the requirement of 2 MVTX clusters and 1 INTT clusters are actually due to the case of multiple collisions close in z within the same beam crossing. Hope plots in the slide are clear enough.

 

Best,

Sanghoon

---------------------------------------------
> Sanghoon LIM
> University of Colorado Boulder

> Physics Department

>
> sanghoon.lim AT colorado.edu

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

On Nov 27, 2018, at 6:01 PM, Christof Roland <christof.roland AT cern.ch> wrote:

 

Hi Everybody, 

 

sorry for the late announcement. Tomorrow we will have the last 

task force meeting before the collaboration meeting where we will have to give 

the final report on the findings of our studies. 

 

The indico agenda can be found here:

 

https://indico.bnl.gov/event/5370/

 

The bluejeans connection can be found here:

 

https://bluejeans.com/553808487/

 

See you tomorrow

 

   Christof