<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=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<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:12.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:12.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:23747420;
mso-list-type:hybrid;
mso-list-template-ids:1492694084 1451676924 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:%1-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:391463759;
mso-list-template-ids:-706175838;}
@list l1:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:1996453201;
mso-list-template-ids:21520954;}
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"><span style="font-size:11.0pt">Hi Andrew, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">No I am not saying that it affects all strips in an APV. In the Hall D data, it affects only a few channels but these strips are the one carrying the signal
</span><span style="font-size:11.0pt;font-family:Wingdings">è</span><span style="font-size:11.0pt"> I lost these data because it last for the full time window of the triggered event. It is not a long lasting flip, the next triggered event, that will no longer
be the case for the same channels<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">But the situation might be different for SBS GMn case because my hypothesis is that these flips are caused by background events long before the triggered event, so we lose only hits that happens at the given
strip but even then, it is still a pretty bad situation <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">Yes, in principle, you can set APV25 baseline pedestal in the middle of the ADC range, I can do that with APV25-SRS, but I don’t know how well it works with signal of both polarity. I would not expect to be
great or balance though <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">Best regards <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Kondo<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Andrew Puckett <puckett@jlab.org>
<br>
<b>Sent:</b> Wednesday, February 23, 2022 3:25 PM<br>
<b>To:</b> Gnanvo, Kondo (kg6cq) <kg6cq@virginia.edu>; Holly Szumila-Vance <hszumila@jlab.org>; Sbs_gems@jlab.org<br>
<b>Subject:</b> Re: On APV25 polarity flip<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">PS—If the analysis Sean is working on shows a high probability of “negative hits” in the area where positive hits are missing from good tracks, then that would be pretty close to a smoking gun, and would have
significant implications for the analysis of the GMN data set. <br>
<br>
In light of this possible failure mode, I am glad we didn’t run GMN at the proposed luminosity or we might have inadvertently killed even the reduced physics output of the experiment that we got.<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" style="margin-bottom:12.0pt"><b><span style="color:black">From:
</span></b><span style="color:black">Sbs_gems <</span><a href="mailto:sbs_gems-bounces@jlab.org">sbs_gems-bounces@jlab.org</a><span style="color:black">> on behalf of Andrew Puckett <</span><a href="mailto:puckett@jlab.org">puckett@jlab.org</a><span style="color:black">><br>
<b>Date: </b>Wednesday, February 23, 2022 at 3:20 PM<br>
<b>To: </b>Gnanvo, Kondo (kg6cq) <</span><a href="mailto:kg6cq@virginia.edu">kg6cq@virginia.edu</a><span style="color:black">>, Holly Szumila-Vance <</span><a href="mailto:hszumila@jlab.org">hszumila@jlab.org</a><span style="color:black">>,
</span><a href="mailto:Sbs_gems@jlab.org">Sbs_gems@jlab.org</a><span style="color:black"> <</span><a href="mailto:Sbs_gems@jlab.org">Sbs_gems@jlab.org</a><span style="color:black">><br>
<b>Subject: </b>Re: [Sbs_gems] On APV25 polarity flip<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt">Hi Kondo, looks pretty convincing for these few examples. If it’s what we are seeing in Hall A, this could be a more serious and fundamental limitation than simple bias of the common-mode calculation or gain
drop, if the “negative occupancy” is high enough and the “polarity flip” probability is high enough, and if there is no way to eliminate/fix this problem.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">A question that I have is, you seem to be implying that if this happens, it affects ALL strips on any given APV affected by this issue. Is that correct? If so, then the frightening implication is that the
good signal would be not even in principle recoverable for any strips on that APV, when this condition exists.
<br>
<br>
If the “negative occupancy” as calculated by Sean is proportional to the “positive occupancy” and comparable in magnitude, and if this quantity is a reasonable proxy for the “polarity flip” probability, then you might imagine that any given APV in any given
event, including the one containing the good signal in that event, would suffer an efficiency loss of similar magnitude as the “negative occupancy”.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt">A good study might be to see if the observed reduction in elastic yield with beam current is consistent with this hypothesis.
<br>
<br>
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I can imagine a possible “hack” where we set the baseline at the midpoint of the ADC dynamic range (I don’t know what is possible in the electronics configuration), and then somehow lower the gain to fit the
signal within the reduced dynamic range of the ADC, and then detect the polarity of any given time sample in any given event, and do analysis using the absolute value of the ADC. But that’s just spitballing.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Andrew</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="color:black">From:
</span></b><span style="color:black">Sbs_gems <</span><a href="mailto:sbs_gems-bounces@jlab.org">sbs_gems-bounces@jlab.org</a><span style="color:black">> on behalf of Gnanvo, Kondo (kg6cq) <</span><a href="mailto:kg6cq@virginia.edu">kg6cq@virginia.edu</a><span style="color:black">><br>
<b>Date: </b>Wednesday, February 23, 2022 at 2:53 PM<br>
<b>To: </b>Holly Szumila-Vance <</span><a href="mailto:hszumila@jlab.org">hszumila@jlab.org</a><span style="color:black">>,
</span><a href="mailto:Sbs_gems@jlab.org">Sbs_gems@jlab.org</a><span style="color:black"> <</span><a href="mailto:Sbs_gems@jlab.org">Sbs_gems@jlab.org</a><span style="color:black">><br>
<b>Subject: </b>[Sbs_gems] [EXTERNAL] On APV25 polarity flip</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt">Dear all, </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I thought I would share again the slides I showed last October when we noticed the “negative pulses” issues for the first time early during the GMn run.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The slides are about some tests I was performing in 2017 in Hall D with a GEM prototype used as transition radiation detector and this is important because in that case the prototype has 21 mm drift so total
primary ionization is 7 times higher than our standard GEM tracker and was causing the polarity flip.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Here I am referring to polarity flip because the data is clean enough that we could actually confirm that APV25 flip polarization without too much speculation and I am going to try to explain the reason why.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3"><span style="font-size:11.0pt">First, these were data taken with APV25-SRS electronics (not MPD) and for that, as a convention, the raw APV25 signal points downside (just a software
decoding convention) as you can see on slide 1. Also, because it is GEM-TRD which operates in TPC mode, we needed to operate in the full APV25 data width mode (27 time samples) to be able to catch (in time and space) different ionization clusters and TRD photon
signal from the same electron hit traversing the detector </span><o:p></o:p></li></ol>
<p class="MsoListParagraph"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3"><span style="font-size:11.0pt">Slide 2 shows one event with clearly polarity flip in y-strips.
</span><o:p></o:p></li><ol style="margin-top:0in" start="1" type="a">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo3"><span style="font-size:11.0pt">The two top frames are x-strips raw data frames and on the right, you see actually signal from at least 2 ionization clusters (waveforms clearly separated
in time) </span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo3"><span style="font-size:11.0pt">The bottom 2 frames are the corresponding signal in y-plane where the signal flipped early after 3 time sample and remained in the flip mode for almost
all the 24 remaining time sample</span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo3"><span style="font-size:11.0pt">The system here triggered on the Hall D Pair spectrometer electron, so it is a clean trigger with on hit per event virtually no background. This can
be confirmed by standard detector so no debate here. So we see hits in x-strips , we expect hit in y
</span><span style="font-size:11.0pt;font-family:Wingdings">è</span><span style="font-size:11.0pt"> what we are seeing is an actual polarity flip</span><o:p></o:p></li></ol>
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3"><span style="font-size:11.0pt">Slide 3 shows 3 different event with polarity flip in y and more than half of the actual data at the time where showing the same behavior and 95% of
the time on y strips</span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3"><span style="font-size:11.0pt">The explanation on why it is always on y-strips is pretty simple, it it cause by pile-up because of if you look at the 2D profile of Hall D PS electron
beam, it is a narrow strips, with the electron normal to the detector in the vertical direction but coming at a large angle ~10 degree in the horizontal direction
</span><span style="font-size:11.0pt;font-family:Wingdings">è</span><span style="font-size:11.0pt"> for a GEM-TRD which produce an ionization 7 times higher than a standard GEM, the signal collected in x-strips will show several waveform separated in time and
also in spaces (several different strips collect the signal form the single electron). But the same signal will be hitting a small set of strips in y causing pile-up and I believe that what cause the polarity to flip.
</span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3"><span style="font-size:11.0pt">When the flip happens, it stays on for several time samples > 20 APV25 time sample
</span><span style="font-size:11.0pt;font-family:Wingdings">è</span><span style="font-size:11.0pt"> It is very likely that the negative pulses we are seeing also are due to similar background hits pile-up that happens way before our real triggered signal but
remained in flip state for the time window of the triggered signal and in that case, you will not see when the flip happens, only that it is there.
</span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3"><span style="font-size:11.0pt">You can also clearly see the saturation effect because of the ADC dynamic range for the flip signal, depending on where the baseline is set, the flipped
signal amplitude will always be small and the waveform shape will be flat </span>
<span style="font-size:11.0pt;font-family:Wingdings">è</span><span style="font-size:11.0pt"> It does not mean that it is not real signal.
</span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo3"><span style="font-size:11.0pt">In some case, you see a glimpse of flipping back to the correct polarity (circled in magenta) but the signal is never fully recover and with 6 time sample,
it is not clear if e will even have this luck</span><o:p></o:p></li></ol>
<p class="MsoListParagraph"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">This is the more serious problem we have other than the effect on corrupting the calculation of CM. It is a long email but I hope these few slides shed a little bit of light on the issue we are trying to understand
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Best regards </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Kondo</span><o:p></o:p></p>
</div>
</body>
</html>