<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<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);">
We should definitely be able to match straight tracks with the start counter. How efficient this is I do not know.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Looking at the PDF Keigo curculated, the black distribution looks like it needs to be shifted to the right by about 10 ns.<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Simon<br>
</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> Sean Dobbs <sdobbs@fsu.edu><br>
<b>Sent:</b> Friday, February 7, 2020 2:09 PM<br>
<b>To:</b> Keigo Mizutani <keigo@jlab.org><br>
<b>Cc:</b> Lubomir Pentchev <pentchev@jlab.org>; halld-tracking-hw <halld-tracking-hw@jlab.org>; Simon Taylor <staylor@jlab.org><br>
<b>Subject:</b> Re: [EXTERNAL] Re: [Halld-tracking-hw] slot for DC alignment talk</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hi Keigo,<br>
<br>
Unfortunately this is not an easy question - generally I haven't been<br>
calibrating these runs since it's not a straight-forward task with our<br>
current codes, and the person who calibrated the 2016 data is long<br>
gone, so I'm not 100% sure what he did. Also, it had been my<br>
understanding that, at least to this point, a detailed timing<br>
alignment wasn't required. But we can work on this.<br>
<br>
A quick look at both runs doesn't show any obvious problems, except<br>
for maybe the start counter, but maybe some of the assumptions that<br>
are being made are not correct for the field-off data.<br>
<br>
One question for Simon: is there a reason we should not expect tracks<br>
to be matched to the start counter in the field-off data?<br>
<br>
One more serious problem I noticed is that if you are running off of<br>
the standard CCDB, it seems like 11048 is configured to have the<br>
magnetic field on in the reconstruction. Presumably this would not<br>
give correct answers. Can you confirm that you see this too (you<br>
should be able to see if a magnetic field map is loaded by looking at<br>
the output of hd_root), and if so, can you tell me which 2016<br>
field-off runs you might be looking at?<br>
<br>
Cheers,<br>
Sean<br>
<br>
<br>
On Fri, Feb 7, 2020 at 1:26 PM Keigo Mizutani <keigo@jlab.org> wrote:<br>
><br>
> Hi Sean,<br>
><br>
> I've checked two straight track runs: run040847 in 2018 and run011048 in 2016, using the same tracking code (halld_recon).<br>
> Only run040847 shows high left-right mis-selection rate in the FDC tracking, and I'm suspecting that this might be related to the timing calibration.<br>
><br>
> I'm sending one picture as an attachment.<br>
> This figure shows drift time distributions for the two straight track runs (& one field-on run).<br>
> The distribution for the run040847 is shifted compared to the run011048, and I'd like to know the t0 calibration status of this run040847. Is this run calibrated in the way for the run011048?<br>
><br>
> Best regards,<br>
> Keigo<br>
><br>
> ________________________________<br>
> From: Sean Dobbs <sdobbs@fsu.edu><br>
> Sent: Friday, February 7, 2020 11:22 AM<br>
> To: Lubomir Pentchev <pentchev@jlab.org><br>
> Cc: halld-tracking-hw <halld-tracking-hw@jlab.org>; Keigo Mizutani <keigo@jlab.org><br>
> Subject: [EXTERNAL] Re: [Halld-tracking-hw] slot for DC alignment talk<br>
><br>
> It looks like there should be room, so I added in 15 minutes for Keigo<br>
> to talk. Perhaps it just reduces the size of the coffee break.<br>
><br>
> I don't mind answering questions regarding the timing, but the DC<br>
> meeting overlaps with my class time this semester. So perhaps Keigo<br>
> can send me (or whoever else is related) an email, or we can set up a<br>
> separate BlueJeans meeting.<br>
><br>
> Cheers,<br>
> Sean<br>
><br>
><br>
> On Fri, Feb 7, 2020 at 11:11 AM Lubomir Pentchev <pentchev@jlab.org> wrote:<br>
> ><br>
> > Hi all,<br>
> ><br>
> > At the tracking meeting yesterday<br>
> ><br>
> > <a href="https://halldweb.jlab.org/wiki/index.php/Meeting-2-6-2020">https://halldweb.jlab.org/wiki/index.php/Meeting-2-6-2020</a><br>
> ><br>
> > Keigo presented interesting results showing his progress with the DC alignment and at the same time he had some questions related to the timing calibration of the relevant detectors. We decided that it would be helpful to present his progress at the collaboration
meeting. He needs 10-15 min, however at this moment there are no open slots for his talk.<br>
> ><br>
> > Can we reshuffle the talks at the detector session (there's no organizer there in the agenda) and around so that we can give him 15min?<br>
> ><br>
> > Thanks,<br>
> > Lubomir<br>
> ><br>
> > _______________________________________________<br>
> > Halld-tracking-hw mailing list<br>
> > Halld-tracking-hw@jlab.org<br>
> > <a href="https://mailman.jlab.org/mailman/listinfo/halld-tracking-hw">https://mailman.jlab.org/mailman/listinfo/halld-tracking-hw</a><br>
</div>
</span></font></div>
</body>
</html>