Skip to Content.
Sympa Menu

sphenix-maps-l - Re: [Sphenix-maps-l] Next Tracker Task Force Meeting

sphenix-maps-l AT lists.bnl.gov

Subject: sPHENIX MAPS tracker discussion

List archive

Chronological Thread  
  • From: sookhyun lee <dr.sookhyun.lee AT gmail.com>
  • To: mxliu <ming AT bnl.gov>
  • Cc: chiu AT rcf.rhic.bnl.gov, sphenix-intt-l AT lists.bnl.gov, mitay AT mit.edu, sphenix-maps <sphenix-maps-l AT lists.bnl.gov>, todoroki AT rcf.rhic.bnl.gov
  • Subject: Re: [Sphenix-maps-l] Next Tracker Task Force Meeting
  • Date: Sat, 1 Dec 2018 22:28:46 -0600

Hi Ming,
To weigh in on your comment, N_MVTX_Clust >=2 alone cannot remove most of the out-of-time tracks as there are ~10 reconstructible out of time events (with a number of tracks associated with each vertex) that do not leave hits on INTT per in-time crossing. We had some discussions during last ITTF meeting and I think it still would be nice to see a linear plot to better understand what is going on. 

Best regards,
Sookhyun

On Sat, Dec 1, 2018 at 10:13 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 3rd layer 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:

 

 

The bluejeans connection can be found here:

 

 

See you tomorrow

 

   Christof  

 




Archive powered by MHonArc 2.6.24.

Top of Page