<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
Thanks Sean,<br>
<br>
It would be great if you can help to<br>
implement CCAL to the rest format.<br>
<br>
We'll work on skims needed for data<br>
analysis.<br>
<br>
<br>
Cheers,<br>
Sasha
<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> Sean Dobbs <sdobbs@fsu.edu><br>
<b>Sent:</b> Friday, July 19, 2019 4:42:55 PM<br>
<b>To:</b> primexd@jlab.org <primexd@jlab.org>; Alexander Somov <somov@jlab.org><br>
<b>Subject:</b> Data production</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hi all,<br>
<br>
Sorry for not bringing this up at the Primex meeting - I got pulled<br>
away in the middle and didn't get back until it was over.<br>
<br>
There was one thing that I wanted to bring up: in the Wednesday GlueX<br>
Analysis meeting, the question was asked when the Primex data would be<br>
ready for a first production pass to generate data in the standard<br>
reconstruction format. My take on this was that<br>
1. The calibrations have to converge to a (not necessarily final)<br>
state which everyone is happy with<br>
2. Whatever skims would be helpful to generate for calibration and<br>
data analysis should be defined and implemented<br>
<br>
It would be good to have some clarity on where we stand with these two<br>
items and what needs to be accomplished to complete them. If anyone<br>
else has some feedback on this subject, I'd be happy to hear it.<br>
<br>
Once Drew's new version of the CCAL reconstruction is merged in, there<br>
will be some minor changes to our REST format needed, which I can help<br>
with. I'll think if any other changes need to go in.<br>
<br>
Cheers,<br>
Sean<br>
</div>
</span></font></div>
</body>
</html>