<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Andrew,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
For the BBShower/preshower, we have been analyzing use the SBSoffline. Of course that was fastbus</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
data that was simpler to decode. Now that we are using FADC, we have just starting to try and use Juan Carlos' new detector classes. Of course there is a separation between what can be done with cosmics ( which only</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
need the low level Decode/CoarseProcess) and what is needed for the experiment. </div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
For that it involves using the MC.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
So Eric can talk about that side of things. Presently I am working on getting the SBSoffline working so we</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
can analyzed the cosmic data.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
To me this brings up another issue about how the standard Podd analysis flow in the code is to be modified</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
to deal with how we want to do the analysis flow. For example using the shower/preshower cluster position for the GEm cluster selection. Ole had some ideas. But I have not recently heard what the overall plan is.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Maybe this could be discussed.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;"> A separate idea is about having the trigger information in the separate Trigger Detector class. We did this </span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;">in Hall C. So the HCAL/ECAL trigger signals that are going TDC/FADC would be analyzed in a separate class rather </span><span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;">than
shoehorn them into the HCAL or BBCAL. </span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;"> Another idea is about putting the ROL configuration information to be read in at beginning of run</span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;">as an event 125, so that this info is saved and in principal could be used. For example the FADC would know what mode the data was taken in.</span><span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;"> </span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;"><br>
</span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;">Cheers,</span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;"> Mark </span></div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Sbs_software <sbs_software-bounces@jlab.org> on behalf of Andrew Puckett <puckett@jlab.org><br>
<b>Sent:</b> Thursday, April 22, 2021 10:15 PM<br>
<b>To:</b> sbs_software@jlab.org <sbs_software@jlab.org><br>
<b>Subject:</b> [Sbs_software] Reminder for SBS simulation and software meeting tomorrow, 1 PM</font>
<div> </div>
</div>
<style>
<!--
@font-face
{font-family:Wingdings}
@font-face
{font-family:Century}
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.x_MsoHyperlink
{color:#0563C1;
text-decoration:underline}
p.x_MsoListParagraph, li.x_MsoListParagraph, div.x_MsoListParagraph
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
span.x_EmailStyle17
{font-family:"Calibri",sans-serif;
color:windowtext}
.x_MsoChpDefault
{font-family:"Calibri",sans-serif}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.x_WordSection1
{}
ol
{margin-bottom:0in}
ul
{margin-bottom:0in}
-->
</style>
<div lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="x_WordSection1">
<p class="x_MsoNormal">Hello all, </p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">We will hold our regular SBS simulation and software meeting tomorrow at the regular time of 1 PM.
</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Agenda: </p>
<ul type="disc" style="margin-top:0in">
<li class="x_MsoListParagraph" style="margin-left:0in">Andrew: Timeline and planning discussion—reviewing status of SBS-offline, decoders, databases, replay scripts, etc.</li><li class="x_MsoListParagraph" style="margin-left:0in">Eric: digitization and sim decoder status</li><li class="x_MsoListParagraph" style="margin-left:0in">Juan Carlos: “generic detector” status and timeline of merging HCAL/developmental code into master</li><li class="x_MsoListParagraph" style="margin-left:0in">Mark/Arun/Provakar/Eric or preshower/shower expert: status of Preshower/Shower in SBS-offline. What is currently in use in TEDF/how are TEDF data being analyzed? SBS-offline or other?</li><li class="x_MsoListParagraph" style="margin-left:0in">All: Brief roundtable updates</li></ul>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"><span style="color:black">If you have anything else you would like to add to the agenda, please send it to me (<a href="mailto:puckett@jlab.org"><span style="color:#0563C1">puckett@jlab.org</span></a>)</span></p>
<p class="x_MsoNormal" style="font-variant-caps:normal; orphans:auto; text-align:start; widows:auto; word-spacing:0px">
<span style="color:black"> </span></p>
<p class="x_MsoNormal" style="font-variant-caps:normal; orphans:auto; text-align:start; widows:auto; word-spacing:0px">
<span style="color:black">We will meet on BlueJeans: </span></p>
<p class="x_MsoNormal" style="font-variant-caps:normal; orphans:auto; text-align:start; widows:auto; word-spacing:0px">
<span style="color:black"> </span></p>
<p class="x_MsoNormal" style="font-variant-caps:normal; orphans:auto; text-align:start; widows:auto; word-spacing:0px">
<span style="color:black">BlueJeans meeting info can be found below: </span></p>
<p class="x_MsoNormal" style="font-variant-caps:normal; orphans:auto; text-align:start; widows:auto; word-spacing:0px">
<span style="color:black"> </span></p>
<p class="x_MsoNormal" style="font-variant-caps:normal; orphans:auto; text-align:start; widows:auto; word-spacing:0px">
<span style="color:black">Meeting URL<br>
<a href="https://bluejeans.com/7634370740?src=join_info"><span style="color:#0563C1">https://bluejeans.com/7634370740?src=join_info</span></a><br>
<br>
Meeting ID<br>
763 437 0740<br>
<br>
Want to dial in from a phone?<br>
<br>
Dial one of the following numbers:<br>
+1.888.240.2560 (US Toll Free)<br>
(see all numbers - <a href="https://www.bluejeans.com/premium-numbers"><span style="color:#0563C1">https://www.bluejeans.com/premium-numbers</span></a>)<br>
<br>
Enter the meeting ID and passcode followed by #<br>
<br>
Connecting from a room system?<br>
Dial: bjn.vc or 199.48.152.152 and enter your meeting ID & passcode</span></p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">See you tomorrow at 1! </p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Best regards,</p>
<p class="x_MsoNormal">Andrew</p>
<p class="x_MsoNormal"> </p>
<div>
<p class="x_MsoListParagraph" style="margin-bottom:12.0pt"><span style="font-family:"Century",serif; color:black">Andrew Puckett<br>
Associate Professor, Physics Department<br>
University of Connecticut<br>
196 Auditorium Road, Unit 3046<br>
Storrs, CT 06269-3046<br>
Office phone: (860) 486-7137<br>
<a href="https://puckett.physics.uconn.edu/" title="https://puckett.physics.uconn.edu/"><span style="color:#00006A">https://puckett.physics.uconn.edu</span></a><br>
<a href="mailto:puckett@jlab.org" title="mailto:puckett@jlab.org"><span style="color:#000064">puckett@jlab.org</span></a></span></p>
</div>
</div>
</div>
</body>
</html>