<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;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@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:617949642;
mso-list-template-ids:-572342884;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:1780443939;
mso-list-type:hybrid;
mso-list-template-ids:181406220 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
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="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks for the detailed explanations. Here are my thoughts:
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo2"><span style="font-size:11.0pt">While I can see the underlying logic of the 1D U and V strip chambers, and I’m sure they would help on some level, I’m less convinced of their necessity
and/or usefulness, given the already high redundancy of the GEP tracking layout.
<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo2"><span style="font-size:11.0pt">On the other hand, the 1 cm^2 pixels, if we put them at the front and the back of the front tracker, would indeed form an extremely powerful combination.
They could even, in principle, almost <i>replace</i> the strategy that we plan to use for the front tracker analysis using the ep kinematic constraints from the electron arm; the combination of the two (ep kinematic constraint from electron arm information
and search region constraint from pixel detectors) will help not only with the tracking ambiguities but also with the SPEED of track-finding; the lack of vertexing information from ECAL+CDET limits how well we can define the search region in the horizontal
direction, we would have to use the correlation between the assumed vertex location and the electron polar scattering angle to narrow the search region in the horizontal dimension.
<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo2"><span style="font-size:11.0pt">The pixel chambers would dramatically reduce the potential combinations we would need to consider and I would LOVE to have pixel chambers, the smaller
the better. <o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo2"><span style="font-size:11.0pt">What is the active area of the pixel chambers? Obviously, making a 60x200 cm^2 requires more channels than making a 40x150 cm^2 pixel chamber. So perhaps
instead of putting them at the front and back of the back tracker, we put one at the front and one between the 6<sup>th</sup> and 7<sup>th</sup> layer in the front tracker; i.e., since the last two layers of the front tracker are XY, this scheme would not
reduce the acceptance.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo2"><b><span style="font-size:11.0pt">What if, instead of building these 1D strip chambers (assuming you have the electronics to support them), you instead use those electronics channels
to shrink the size of the pixels (other limitations than just electronics might come into play of course…) Just for argument’s sake, suppose each 1D strip chamber has about 4,000 channels. Suppose your pixel chamber is 40x150 cm^2 so 6,000 channels. If I suddenly
have 8,000 more channels available, then the pixels could be 5 mm x 5 mm for a 40x150 cm^2 layer, shrinking the occupancy by a factor of 4 (from ~10% to ~2-3%) and imposing an even tighter constraint on the track-finding in the 2D strip chambers?
<o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo2"><span style="font-size:11.0pt">Finally, we need to consider space constraints. If we increase the total size of the front tracker along z, then in principle the CH2 analyzer and the
back tracker have to be pushed back, reducing the useful acceptance for polarimetry. So unless we want to REPLACE one of the 2D strip chambers (say, an X/Y layer) in the front tracker, we do need to be mindful of the space constraints.
<b><o:p></o:p></b></span></li></ol>
<p class="MsoNormal"><b><span style="font-size:11.0pt"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Maybe we should have a phone call to discuss this? I guess I already missed the GEM meeting today.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Cheers,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Andrew<b> </b><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:"Calibri",sans-serif;color:black">From:
</span></b><span style="font-family:"Calibri",sans-serif;color:black">Sbs_gems <sbs_gems-bounces@jlab.org> on behalf of "Liyanage, Nilanga K (nl8n) via Sbs_gems" <Sbs_gems@jlab.org><br>
<b>Reply-To: </b>"Liyanage, Nilanga K (nl8n)" <nl8n@virginia.edu><br>
<b>Date: </b>Wednesday, May 15, 2024 at 1:08 PM<br>
<b>To: </b>Bogdan Wojtsekhowski <bogdanw@jlab.org>, "Sbs_gems@jlab.org" <Sbs_gems@jlab.org>, Mark Kevin Jones <jones@jlab.org>, "Liyanage, Nilanga K (nl8n)" <nl8n@virginia.edu><br>
<b>Subject: </b>[Sbs_gems] [EXTERNAL] Re: Test for GEp<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">The logic behind this new idea is as follows:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<ul type="disc">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
The brand new research by Gianni Benchvinni's group at Frascatti has shown that the improved uRwell could operate at hit rates upto 1 MHz/cm^2 (Gianni is physicist who invented uRwell concept; Huong has visited his lab and formed collaborative connections
with his group; Gianni has graciously agreed to collaborate with us on this new develpment aimed at SBS and SoLID.)<o:p></o:p></li></ul>
</div>
<div>
<ul type="disc">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
At these very high rates, to facilitate stable operation, uRwells need to operate at low gains, about 2000 as opposed to about 8000 for GEMs. These low gains are sufficient to support one readout direction, but not enought for charge to be divided between two
directions. As such one 1 detectors, for example U or V are the most optimum in these conditions.<o:p></o:p></li></ul>
</div>
<div>
<ul type="disc">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Actually this is much better for us in SBS conditions: most of our random background, low energy photons, only give a random hit on a single layer, but not correlated hits on successive independent detectors. <o:p></o:p></li></ul>
</div>
<div>
<ul type="disc">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
In our UV or XW case, the total number of channels we have per chamber allows us to build a pixel detector with pixel sizes of 1 cm x 1 cm to have the same active area and the same total channels as a UV or a XW. <o:p></o:p></li></ul>
</div>
<div>
<ul type="disc">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Having two pixel chambers seperated by some distance and requiring .AND. between hits on both can clean up most of the random hits and select mostly the high energy tracks. <o:p></o:p></li></ul>
</div>
<div>
<ul type="disc">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Given the catchment area for these pixels, the occupancy level would be about 1/6<sup>th</sup> of that of any existing UV or XW chamber; so in the worst case the occupancy would be around 10%; and the .AND. condition would lower this by some factor (beween
1 and 10, and I think closer to 10)<o:p></o:p></li></ul>
</div>
<div>
<ul type="disc">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Also we can place one pixel chamber at the front of the stack and one at the end of the stack; they will be built as independent detectors and can be seperated by any distance. <o:p></o:p></li></ul>
</div>
<div>
<ul type="disc">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
All this would ensure that we have a pretty narrow (about a factor of 100 smaller in area than right now) search area for hits on the strip chambers. <o:p></o:p></li></ul>
</div>
<div>
<ul type="disc">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
As for 1D strip chambers: in the current 2D strip chambers, since the same charge cloud gives both U and V hits, the random hits and hign energy track hits are indistinguishable: they would both give correlated and correct U/V combinations (as opposed to ghost
UV combinations which are filtered out in tracking), in the order of (occupancy); for example, at ~ 40% for GEp<o:p></o:p></li></ul>
</div>
<div>
<ul type="disc">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
On the other hand, when we have a 1D U chamber and a 1D V chamber (in this case not too far apart), we will only get correlated U/V hits, WITHIN THE NARROW SEARCH AREA POINTED TO BY THE PIXELS., only for the high energy tracks, and only trandom combinations,
in the oder of (occupancy^2) for the random hits; for example, ~ 16 % for GEp.<o:p></o:p></li></ul>
</div>
<div>
<ul type="disc">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
So, this is what makes the combination of two back to back pixel detectors, combined with a back to back 1D U and 1D V detectors so powerful in our situation.<o:p></o:p></li></ul>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> Sbs_gems <sbs_gems-bounces@jlab.org> on behalf of Liyanage, Nilanga
K (nl8n) via Sbs_gems <sbs_gems@jlab.org><br>
<b>Sent:</b> Wednesday, May 15, 2024 12:33 PM<br>
<b>To:</b> Bogdan Wojtsekhowski <bogdanw@jlab.org>; Sbs_gems@jlab.org <Sbs_gems@jlab.org>; Mark Jones <jones@jlab.org><br>
<b>Subject:</b> [Sbs_gems] [EXTERNAL] Re: Test for GEp</span> <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Also, I am realizing that this information makes what I have been considering (outlined below) so much more important and urgent. :<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">I just got the quotes from Rui at CERN about the pixel uRwell chamber I have been talking about for GEp to make the tracking much easier than robust. The cost of material for a double chamber is about $ 30 k, and
Huong and I would be happy to contribute person power from our group to build two double chambers by late fall, hopefully in time for GEp installation; of course this will depend on when we can get the parts from CERN; Huong is traveling there in June and
will try to convince Rui to get these foils to us on time.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">The ideal and the most powerful combination would be a double pixel chamber ( two back to back chambers with 1 cm x 1 cm pixels) and a double UV chamber (back to back strip chambers, same pitch as UV, one chamber
with U readout and the second with V readout); and we need to find $ 60 k for this set. Given the extremely high importance of this for GEp, and the urgency of the situation, I am happy to go ahead with the orders for the double pixel chamber using my grant
funds at UVa. I plan to initiate these orders today. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">I will send in a request to Mark and Bogdan soon for the funds for the UV set, if you can find funds from either Jlab or from collaborators, we can place those orders very soon as well and build both double layer
detectors at the same time.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Best<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Nilanga<o:p></o:p></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" align="center">
</div>
<div id="x_divRplyFwdMsg">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> Liyanage, Nilanga K (nl8n) <nl8n@virginia.edu><br>
<b>Sent:</b> Wednesday, May 15, 2024 12:20 PM<br>
<b>To:</b> Bogdan Wojtsekhowski <bogdanw@jlab.org>; Sbs_gems@jlab.org <Sbs_gems@jlab.org>; Mark Jones <jones@jlab.org><br>
<b>Subject:</b> Re: Test for GEp</span> <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Hi Bogdan<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Yes, you are absolutely correct, it is a 30 cm target. I am sorry I missed that. So yes, it would be a factor of 6-7.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Yes, in that case it is good to push higher in the beam current for the test and also test the HV corrections on Sunday.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">While I think that from the hardware perspective the GEMs would still be OK at that high luminosity, I think Andrew might have a really challenging problem with tracking with that factor of 6-7 increase: currently
we are having raw occupancies of ~ 12.5 % , so given the same gain etc. we will have about 80-90% level occupancies for GEp; I do not think we ever expected or prepared for those level of occupancies (Andrew, please correct me if I am mistaken here); in my
opinion, it would be next to impossible to run with anything higher than ~ 50-60% occupancy and get useful tracking information.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">In that case we will seriously have to think about the hadron filter you have been proposing; and this Sunday could be an idea opportunity to test something like that.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Best<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Nilanga<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" align="center">
</div>
<div id="x_x_divRplyFwdMsg">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> Bogdan Wojtsekhowski <bogdanw@jlab.org><br>
<b>Sent:</b> Wednesday, May 15, 2024 12:07 PM<br>
<b>To:</b> Liyanage, Nilanga K (nl8n) <nl8n@virginia.edu>; Sbs_gems@jlab.org <Sbs_gems@jlab.org>; Mark Jones <jones@jlab.org><br>
<b>Subject:</b> Re: Test for GEp</span> <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Hi Nilanga,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">We can use BB tracker to monitor the beam stability and conformation from 50k analysis will good.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">The difference between GEn-Rp and GEP operation is a bit larger: <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">GEP plans to use 50 uA on 30 cm long LH2 but GEn-RP used 15 uA on 15 cm LH2 => a factor of 6-7. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">In addition, GEP will use SBS at 16 degree angle but now we have 23 degree.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">So, it will be useful to see how GEM capable to operate with 30 uA on 15 cm long LH2.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Bogdan<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" align="center">
</div>
<div id="x_x_x_divRplyFwdMsg">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> Liyanage, Nilanga K (nl8n) <nl8n@virginia.edu><br>
<b>Sent:</b> Wednesday, May 15, 2024 11:29 AM<br>
<b>To:</b> Sbs_gems@jlab.org <Sbs_gems@jlab.org>; Bogdan Wojtsekhowski <bogdanw@jlab.org>; Mark Kevin Jones <jones@jlab.org><br>
<b>Subject:</b> [EXTERNAL] Re: Test for GEp</span> <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Dear All<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Looks like thanks to all the hard work put in by Holly, Vimukthi and the team, all GEM trackers are operating pretty well now, with efficiencies mostly around 75-80% per layer. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">The current production running at 15 uA on LD2 is equivalent to about 25 uA on LH2; so about 50% of the GEp goal; this is consistent with the ~ 10-12% occupancies we are seeing in the SBS front tracker, I think
Andrew was expecting about 25-30% for GEp.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Given this, the high efficiencies, good tracking etc. we are seeing now are great signs for GEp.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">As I mentioned earlier, what we are doing now is much harder than the case for GEp: we are now requiring 3 hits out of 4 layers, while GEp will be asking for 4 hits out of 8 layers. This means that the layer efficiencies
we are already getting are more than enough for GEp. Given the combinatorials of C(8,4) we should be able to get a very high tracking efficiency with what we already have. In fact, we might be able to lower the gains a bit to achieve more stable performance
under higher luminosity, and still be able to get very good tracking efficiency in GEp.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">We should be able to demonstrate this with the analyzer removed runs this Sunday<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">With the individual power supplies, is seems that the gains are pretty linear with beam current. So I think even at twice the current lumonosity we should be able to operate the power supplies like we are doing
now, without any additional corrections to account for protective resistor voltage drops. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">As for the program on Sunday, I do not think we need to push too high on the beam current, if we can get something like 25 uA on LH2 and LD2, that would be sufficient; with LD2 that would be close to 42 uA on LH2. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">One thing we MUST remember for the beam test on Sunday is that the GEM gains are going to go up for both FRONT AND BACK TRACKERS on SBS with beam current. This means that we may not be able to go to the same high
voltage settings we are using for these chambers, especially for the back tracker ones, for production right now. So, for the beam test, we should back down all the GEMs voltages to 3500 V and then carefully go up in voltage in 25 V steps while carefully
monitoring the gains.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Also: if the beam is not stable and/or crappy, I think we should not turn on the GEMs on Sunday: given everything we have learned so far, there is nothing much left we must do to prepare for GEp. So if the beam
quality is not good, I would rather not risk the GEMs to take some data which is not a must. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">I plan to be there on Sunday<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Best<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Nilanga<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" align="center">
</div>
<div id="x_x_x_x_divRplyFwdMsg">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> Sbs_gems <sbs_gems-bounces@jlab.org> on behalf of Mark Kevin Jones
via Sbs_gems <sbs_gems@jlab.org><br>
<b>Sent:</b> Thursday, May 9, 2024 5:15 PM<br>
<b>To:</b> Sbs_gems@jlab.org <Sbs_gems@jlab.org>; Bogdan Wojtsekhowski <bogdanw@jlab.org><br>
<b>Subject:</b> [Sbs_gems] Test for GEp</span> <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Hi all,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> Everyone has been working hard to get the GEMs working at this setting. Thanks to everyone.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">For the next experiment GEp, we need to verify that the GEMs can be run at that <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">the luminosity of 50uA on 30cm LH2 target. Nilanga seemed fairly confident <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">that we can run at the GEp luminosity after the current scan that was early in the experiment.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> Do we need to do additional tests to show the expected performance for the GEp?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">I am sure that we will get from Thia and Patrizia questions about the expected performance for GEp.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Cheers,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> Mark<o:p></o:p></span></p>
</div>
</div>
</body>
</html>