<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.xmsonormal, li.xmsonormal, div.xmsonormal
{mso-style-name:x_msonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1603369175;
mso-list-type:hybrid;
mso-list-template-ids:231905174 -1470579870 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hi Alexander, <o:p></o:p></p>
<p class="MsoNormal">Thanks for your feedback. Let me add some personal comment, but please keep in mind that a lot of the aspect of the DSC (not DSS
<span style="font-family:"Segoe UI Emoji",sans-serif">😊</span>) are still a bit of not fully clear for me and what I am saying are just my current understanding which is probably not better than yours.
<o:p></o:p></p>
<p class="MsoNormal">
<o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">You are right that MPGD trackers (hypothetical) in ePIC do not constitute a subsystem stricto sensu but this is the same for the Si layers… My understanding is that because of the
nature of the ePIC tracker mostly MAPS technology everywhere complemented by MPGDs when necessary, it is better to have two separate groups MAPS-DSC and MPGD-DSC to allow experts in each technology to be included in the discussion because you don’t want for
example a DSL for the barrel tracker who is a MAPS expect to be making decision regarding MPGD technology. Therefore this approach makes sense to me.
<o:p></o:p></li></ul>
<p class="MsoListParagraph">To which extent we can call it collaboration is not clear for me. It will still be, at least at the beginning an eRD108 like consortium but expanded to new groups and singularly focused on developing the technologies relevant to
ePIC detector needs. <o:p></o:p></p>
<p class="MsoListParagraph"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Regarding where MPGD layers are present in the current ePIC detector, I agree that for now, after the choice of imaging calorimeter as barrel EMCAL, the planar uRWELL behind DIRC are
no longer part of the picture. My personal opinion is that. Regardless the number of imaging calo layers (4 or 6), if tracking behind DIRC is necessary to provide angular resolution information after the particle pass through to help the DIRC bars, I would
argue that you need a second hit points in addition to the first tracking layer of the calo to provide a track.
<o:p></o:p></li></ul>
<p class="MsoListParagraph"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">But actually, the real question is whether the DIRC folks need that information at all. We asked explicitly this question a couple of weeks ago to the DIRC people and their answer
seems to imply that precision tracking before DIRC was what is needed <span style="font-family:Wingdings">
è</span> I will come back to this point later when addressing the barrel Micromegas layer. So planar uRWELL layer might not be needed not really because of the imaging calo tracking layer but because it is not crucial for DIRC. There is a similar lack of interest
from the collaboration for an MPGD layer behind dRICH in the forward region that I also don’t understand.<o:p></o:p></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Additional MPGD discs in the forward and backward regions to provide tracking points and precision timing are been discussed and we (former tracking WG) are going to present the optimization
of MPGD trackers options at the TIC meeting in the coming weeks. <o:p></o:p></li></ul>
<p class="MsoListParagraph"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Regarding the current cyl. Micromegas in the barrel tracker, I have some real issues with the current design. I don’t know of any good argument (other than the available space) for
having this layer at a radius 55 cm between the Si layers and the TOF layer which also is a precision tracking layer. It would make more sense in my view to me to move the layer(s) at a larger radius between TOF and DIRC. This will combine the benefit of
providing a better tracking capability (assumption) for the DIRC and less material (when we account for all services, support structure, cables and connectors) in the way of the Si tracker performance (momentum and DCA resolution) and still been mainly used
for pattern recognition and precision timing for the overall tracker performance
<span style="font-family:Wingdings">è</span> We are also going to present this alternative option of swapping the order of AC-LGAD and MM to the TIC at the meeting.
<o:p></o:p></li></ul>
<p class="MsoListParagraph"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Last point, my view is that we need to focus our future effort in developing MPGD technologies that provide good performance (spatial point resolution > 150 um or more is not a good
performance) and more importantly are robust and resilient technologies that can operate in a stable manner over the lifetime of ePIC
<span style="font-family:Wingdings">è</span> to do so, an eRD108 like consortium consolidated by new institutions with experience in these technologies should be the path toward forming the Detector Subsystem Collaboration (DSC). <o:p></o:p></li></ul>
<p class="MsoListParagraph"><o:p> </o:p></p>
<p class="MsoNormal">I provide long answers to your questions because the optimization of ePIC tracker with MPGD layers has just actually started recently and there are a lot of questions that are still not answered to in the current geometry, that we need
to quickly converge to <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Any comment and feedback is welcome as whatever I said here are my raw personal opinion
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards <o:p></o:p></p>
<p class="MsoNormal">Kondo<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Kiselev, Alexander <ayk@bnl.gov> <br>
<b>Sent:</b> Saturday, April 15, 2023 2:42 PM<br>
<b>To:</b> Kondo Gnanvo <kagnanvo@jlab.org>; erd108@jlab.org; eic-rd-tracking-l@lists.bnl.gov<br>
<b>Cc:</b> Seung Joon Lee <sjlee@jlab.org>; Huong Nguyen <htn3r.uva@gmail.com><br>
<b>Subject:</b> [EXTERNAL] Re: ePIC Gaseous Detector DSL and DSTC<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"> Dear Kondo,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"> remind me please what DSS are we talking about. I mean the MPGD technology does not sound like a DSS to me, and eRD108 (as a project-funded consortium) either, even that
the management plan tells us otherwise. As of yesterday a tracker behind the DIRC is seemingly gone, although it may not be true any longer with just four imaging EmCal layers. Endcap disks behind the silicon tracker look more than likely to me. Micromegas
barrel is still alive, while uRWell barrel layers are questionable, right? Is there anything left behind the dRICH in the ePIC baseline configuration?
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"> Anyway, are we talking about an umbrella DSS governing all these possible (MPGD) subsystems, as proposed by the management? With a unified DSSL and just a single DSTC
for e.g. a barrel micromegas and an endcap uRWell "real world Detector Subsystems"? How it is supposed to work in real life, if the former will probably be designed and built at Saclay, and the latter one say at FIT (and / or JLAB)?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"> Cheers,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"> Alexander.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="98%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> Eic-rd-tracking-l <<a href="mailto:eic-rd-tracking-l-bounces@lists.bnl.gov">eic-rd-tracking-l-bounces@lists.bnl.gov</a>> on behalf of Kondo Gnanvo <<a href="mailto:kagnanvo@jlab.org">kagnanvo@jlab.org</a>><br>
<b>Sent:</b> Friday, April 14, 2023 2:31 PM<br>
<b>To:</b> <a href="mailto:erd108@jlab.org">erd108@jlab.org</a> <<a href="mailto:erd108@jlab.org">erd108@jlab.org</a>>;
<a href="mailto:eic-rd-tracking-l@lists.bnl.gov">eic-rd-tracking-l@lists.bnl.gov</a> <<a href="mailto:eic-rd-tracking-l@lists.bnl.gov">eic-rd-tracking-l@lists.bnl.gov</a>><br>
<b>Cc:</b> Seung Joon Lee <<a href="mailto:sjlee@jlab.org">sjlee@jlab.org</a>>; Huong Nguyen <<a href="mailto:htn3r.uva@gmail.com">htn3r.uva@gmail.com</a>><br>
<b>Subject:</b> [Eic-rd-tracking-l] ePIC Gaseous Detector DSL and DSTC</span> <o:p>
</o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="xmsonormal">Dear all, <o:p></o:p></p>
<p class="xmsonormal">I am assuming that you have all been following the new structure put in place for the ePIC collaboration that requires the formation of Detector Subsystem Collaboration (DSC) with a designated leader (DSL) and technical contact (DSTC).
These two people are going to be representing the subsystem collaboration at the ePIC Technical and Integration Council (TIC) regular meeting
<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">We would need to identify two people within our consortium (eRD108 and affiliates) So I would suggest if there are candidates for either role, please put your name in the ring and at some point we will find a way by next week to select
the two people. I am certainly putting my name for the DSL role. <o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">We need to select the two people before the first TIC meeting on Friday 28 April.<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">Best regards <o:p></o:p></p>
<p class="xmsonormal">Kondo<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>