<html 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)">
<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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hello all, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">After realizing in today’s discussion that we need to support three different APV
<span style="font-family:Wingdings"></span> <span style="font-family:Wingdings">
</span> strip mappings in the analysis, I made some major updates to the GEM code to accommodate this. I also updated the BigBite GEM pedestals in the database, because the ordering of these pedestals in the database depends on this mapping.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">See: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_JeffersonLab_SBS-2Doffline_commit_81988437aec3dea6fd15d508ce03fa7d536a48b7&d=DwMGaQ&c=CJqEzB1piLOyyvZjb8YUQw&r=QlYVvSkd1eI3G8amPtrE_if6U-4zjeas0cAWa4BvYGo&m=ARji6V74jphKYznCmVym_hGIwl3PjQ-kSOR4gk8SZgY&s=wZKwJt9kGawpiDbXcxWWA2ck0ha1d3fLd42bBSQ6IKo&e=">
https://github.com/JeffersonLab/SBS-offline/commit/81988437aec3dea6fd15d508ce03fa7d536a48b7</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">And: <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_JeffersonLab_SBS-2Dreplay&d=DwMGaQ&c=CJqEzB1piLOyyvZjb8YUQw&r=QlYVvSkd1eI3G8amPtrE_if6U-4zjeas0cAWa4BvYGo&m=ARji6V74jphKYznCmVym_hGIwl3PjQ-kSOR4gk8SZgY&s=B7U_tNPZrineu1-gwr07R8AGgzPw-EBUiDegE1cY0Ek&e=">https://github.com/JeffersonLab/SBS-replay</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If you are doing GEM analysis, you will want to pull down these changes. This probably explains the issue of having too many single-strip clusters, since the mapping of strips to positions was not correct for most of the modules. Interesting
then that the code still found so many “tracks”. Anyway, hope to test the effect of the changes shortly<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">Andrew<o:p></o:p></p>
</div>
</body>
</html>