sphenix-tracking-l AT lists.bnl.gov
Subject: sPHENIX tracking discussion
List archive
[Sphenix-tracking-l] Minutes of November 11, 2016 sPHENIX tracking meeting
- From: "Frawley, Anthony" <afrawley AT fsu.edu>
- To: "sphenix-tracking-l AT lists.bnl.gov" <sphenix-tracking-l AT lists.bnl.gov>
- Subject: [Sphenix-tracking-l] Minutes of November 11, 2016 sPHENIX tracking meeting
- Date: Sat, 12 Nov 2016 03:21:13 +0000
Hi All,
Here are the minutes of this morning's short tracking meeting.
Cheers
Tony
-----------------------------------------
We had a discussion about intermediate tracker configuration, following up on the discussion at the October 21 meeting.
We discussed at the previous meeting how to avoid conflicts between the INTT (and its readout) and the MAPS readout cone. One way is to reconfigure the MAPS readout so that the large fan out is reduced in size, leaving room for the INTT. A possibility that was also discussed was to read out the INTT at one end only, possibly with a channel count reduction by doubling the pitch of the strips.
Itaru said that the single side readout option for the INTT would be challenging and risky. The length of the HDI readout path would be doubled, and that may exceed technical limits. Technically it would be a big deal, and may require searching for a new manufacturer for the HDI. Re-configuring the MAPS readout fan is the strongly preferred option.
Itaru is going to BNL at the end of next week specifically to discuss the support structure/integration for the INTT. He will be there for a week. The plan is to Identify an engineer and bring him up to date. After Itaru leaves, his colleagues at BNL will work with the engineer.
Itaru said they will need a MAPS engineer to tell them how much space is available
We discussed briefly the reasoning behind having four layers in the INTT. The 4th layer does not quite cover the TPC acceptance (eta = 1.0 instead of 1.1 for events at 10 cm). Itaru said that the 4th layer is really for redundancy in case of problems with ladders in the inner layers.
We discussed at the previous meeting how to avoid conflicts between the INTT (and its readout) and the MAPS readout cone. One way is to reconfigure the MAPS readout so that the large fan out is reduced in size, leaving room for the INTT. A possibility that was also discussed was to read out the INTT at one end only, possibly with a channel count reduction by doubling the pitch of the strips.
Itaru said that the single side readout option for the INTT would be challenging and risky. The length of the HDI readout path would be doubled, and that may exceed technical limits. Technically it would be a big deal, and may require searching for a new manufacturer for the HDI. Re-configuring the MAPS readout fan is the strongly preferred option.
Itaru is going to BNL at the end of next week specifically to discuss the support structure/integration for the INTT. He will be there for a week. The plan is to Identify an engineer and bring him up to date. After Itaru leaves, his colleagues at BNL will work with the engineer.
Itaru said they will need a MAPS engineer to tell them how much space is available
We discussed briefly the reasoning behind having four layers in the INTT. The 4th layer does not quite cover the TPC acceptance (eta = 1.0 instead of 1.1 for events at 10 cm). Itaru said that the 4th layer is really for redundancy in case of problems with ladders in the inner layers.
Itaru will report back after his visit to BNL.
- [Sphenix-tracking-l] Minutes of November 11, 2016 sPHENIX tracking meeting, Frawley, Anthony, 11/11/2016
Archive powered by MHonArc 2.6.24.