<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Andy, <div class=""><br class=""></div><div class="">That makes perfect sense now!</div><div class=""><br class=""></div><div class="">Thanks, </div><div class="">Nick</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 8 Nov 2017, at 21:03, Dr. A.M. Sandorfi <<a href="mailto:sandorfi@jlab.org" class="">sandorfi@jlab.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<title class="">Re: [G14_run] Systematic uncertainties on asymmetries - (Tsuneo's question to K Sigma analysis note)</title>
<div class="">
<font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class="">Nick,<br class="">
<br class="">
Pardon my cavalier interchange of the words “error” and “uncertainty”. But that’s not the point. There is a systematic uncertainty in the beam polarization, for example, and its variation from the nominal value is approximated by a gaussian distribution with a 1 sigma of 3.4%. So, someone else using the data set in some calculation is allowed to consider different values of that polarization within this distribution. BUT, if an overall fit to some model, a PWA, ...whatever, prefers a value for the beam polarization that is different from our quoted nominal, he/she must shift ALL of our data points together by exactly the same factor, because that’s how the measurement responds to a change to that parameter. {For example, If the assumed beam polarization is lowered by X%, then the deduced asymmetry values in kinematic bins at W=1800 and cosA= -0.3, and at W=2100 and cosA= +0.6, go up by exactly the same X%.} That’s the point! For this reason one does not combine uncertainties in the overall scale of an entire data set in quadrature with point-to-point uncertainties.<br class="">
<br class="">
Andy<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
On 11/8/17, 5:20 PM, "Nicholas Zachariou" <<a href="x-msg://28/nicholas@jlab.org" class="">nicholas@jlab.org</a>> wrote:<br class="">
<br class="">
</span></font><blockquote class="" type="cite"><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class="">Hi Andy, <br class="">
<br class="">
Thank you for the explanation. I do agree that that would be the correct way to do so if we found a systematic error (and not uncertainty). In that case we would need to shift our points to account for the systematic offset. In most cases (and in the analysis we have done for the E observable on K+Sigma-) the systematic studies yield uncertainties (i.e. the systematic effect of specific sources can produce higher or lower in magnitude observables). The same goes for the photon polarization. The 3.4% is a systematic uncertainty and not an error. This means that the true value of the photon polarization can vary from the nominal value by 3.4% in either direction. This effects our observable E directly in magnitude, so I think its more proper to include that in the total uncertainty by adding it to the statistical in quadrature. Maybe I am missing something and would love to discuss more on this during the meeting. <br class="">
<br class="">
Best regards, <br class="">
Nick<br class="">
<br class="">
<br class="">
</span></font><blockquote class="" type="cite"><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class="">On 8 Nov 2017, at 17:35, Dr. A.M. Sandorfi <<a href="x-msg://28/sandorfi@jlab.org" class="">sandorfi@jlab.org</a>> wrote:<br class="">
<br class="">
Re: [G14_run] Systematic uncertainties on asymmetries - (Tsuneo's question to K Sigma analysis note) <br class="">
Nick,<br class="">
<br class="">
A systematic scale uncertainty represents a shift to the entire data set as a hole. For example, imagine you find out after publication that a polarization (beam or target) was to high by 5%. How do you correct that – you multiply every data point by 0.95. Essentially, that just changes the scale of the axes in a plot of the data. The point-to-point statistical fluctuations do not change. That is not the equivalent to increasing the size of the point-to-point fluctuations.<br class="">
<br class="">
Now there can be some components of the systematic uncertainty that change with kinematic bins, and these parts could be added in quadrature with statistical errors. But those do not usually dominate the total systematic error. For this reason, when it comes time to publish, point-to-point systematics and scale uncertainties should be clearly quoted separated – as we have done in our recent pi-p PRL.<br class="">
<br class="">
Andy<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
On 11/7/17, 11:02 PM, "Nicholas Zachariou" <<a href="x-msg://28/nicholas@jlab.org" class="">nicholas@jlab.org</a> <x-msg:<a href="x-msg://22/nicholas@jlab.org" class="">//22/nicholas@jlab.org</a>> > wrote:<br class="">
<br class="">
</span></font><blockquote class="" type="cite"><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class="">Hi Andy,<br class="">
<br class="">
Can you elaborate why its not correct to add the systematic in quadrature with the statistical? <br class="">
I am not sure I understand why this "uses data that dont represent the experiment". Maybe we can talk more during the g14 meeting.<br class="">
<br class="">
Nick<br class="">
On Nov 7, 2017, at 22:22, "Dr. A.M. Sandorfi" <<a href="x-msg://28/sandorfi@jlab.org" class="">sandorfi@jlab.org</a> <x-msg:<a href="x-msg://22/sandorfi@jlab.org" class="">//22/sandorfi@jlab.org</a>> > wrote:<br class="">
</span></font><blockquote class="" type="cite"><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class="">Hi Eugene,<br class="">
<br class="">
Yes, your point is well taken - for those data points where the asymmetry is<br class="">
very close to zero. One has two choices: we could either give an overall<br class="">
fractional (%) uncertainty, while quoting the absolute value as an exception<br class="">
when the asymmetry vanishes, or just quote only an absolute uncertainty for<br class="">
all points. <br class="">
<br class="">
The trouble comes at the subsequent stage when the data is used by the<br class="">
various PWA groups. All PWA groups have their fitting routines set up to<br class="">
float the scale of a data set while including a chi^2 penalty that is<br class="">
weighted by a fractional systematic error. If we give them a systematic<br class="">
uncertainty that is absolute, they will combine it in quadrature with the<br class="">
statistical error to create an inflated point by point uncertainty, and set<br class="">
the fitting scale to 1. I can guarantee that this will happen and it is a<br class="">
completely incorrect way to use the data that doesn't represent the<br class="">
experiment. So it is better to use the first approach - quote the systematic<br class="">
uncertainty as a fractional (%) error, while explicitly noting the absolute<br class="">
value of the systematic uncertainty for those asymmetry points with nearly<br class="">
zero value. The later qualifying statement will probably be ignored in PWA<br class="">
analyses, but at least most of the data will have been included properly.<br class="">
<br class="">
Andy<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
On 11/4/17, 11:37 PM, "Eugene Pasyuk" <<a href="x-msg://28/pasyuk@jlab.org" class="">pasyuk@jlab.org</a> <x-msg:<a href="x-msg://22/pasyuk@jlab.org" class="">//22/pasyuk@jlab.org</a>> > wrote:<br class="">
<br class="">
</span></font><blockquote class="" type="cite"><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""> <br class="">
Any asymmetry can be anything between -1 and +1, 0 included. For any<br class="">
observable which may be equal to 0 relative uncertainty does not make sense.<br class="">
Only absolute uncertainty must be used.<br class="">
The second term in Nick's equation is equal to 0 if ObservableValue is always<br class="">
equal to 0 regardless of sigma_sys_relative. This is incorrect but good<br class="">
illustration why one must not use relative uncertainty for asymmetries.<br class="">
<br class="">
-Eugene<br class="">
<br class="">
----- Original Message -----<br class="">
</span></font><blockquote class="" type="cite"><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""> From: "Tsuneo Kageya" <<a href="x-msg://28/kageya@jlab.org" class="">kageya@jlab.org</a> <x-msg:<a href="x-msg://22/kageya@jlab.org" class="">//22/kageya@jlab.org</a>> ><br class="">
To: "Nicholas Zachariou" <<a href="x-msg://28/nicholas@jlab.org" class="">nicholas@jlab.org</a> <x-msg:<a href="x-msg://22/nicholas@jlab.org" class="">//22/nicholas@jlab.org</a>> ><br class="">
Cc: "g14 run" <<a href="x-msg://28/g14_run@jlab.org" class="">g14_run@jlab.org</a> <x-msg:<a href="x-msg://22/g14_run@jlab.org" class="">//22/g14_run@jlab.org</a>> ><br class="">
Sent: Saturday, November 4, 2017 10:57:28 PM<br class="">
Subject: Re: [G14_run] G14_run Digest, Vol 74, Issue 3 (Tuneo's question to<br class="">
K Sigma analysis note)<br class="">
</span></font></blockquote><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""> <br class="">
</span></font><blockquote class="" type="cite"><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""> Nick,<br class="">
<br class="">
thank you for the response.<br class="">
I would like to know why the absolute is more appropriate.<br class="">
I will look forward the statements.<br class="">
<br class="">
Regards, Tsuneo Kageya.<br class="">
<br class="">
----- Original Message -----<br class="">
From: "Nicholas Zachariou" <<a href="x-msg://28/nicholas@jlab.org" class="">nicholas@jlab.org</a> <x-msg:<a href="x-msg://22/nicholas@jlab.org" class="">//22/nicholas@jlab.org</a>> ><br class="">
To: "Tsuneo Kageya" <<a href="x-msg://28/kageya@jlab.org" class="">kageya@jlab.org</a> <x-msg:<a href="x-msg://22/kageya@jlab.org" class="">//22/kageya@jlab.org</a>> ><br class="">
Cc: "g14 run" <<a href="x-msg://28/g14_run@jlab.org" class="">g14_run@jlab.org</a> <x-msg:<a href="x-msg://22/g14_run@jlab.org" class="">//22/g14_run@jlab.org</a>> ><br class="">
Sent: Saturday, November 4, 2017 3:23:46 PM<br class="">
Subject: Re: [G14_run] G14_run Digest, Vol 74, Issue 3 (Tuneo's question to<br class="">
K<br class="">
Sigma analysis note)<br class="">
<br class="">
Hi Tsuneo,<br class="">
<br class="">
The absolute error is propagated directly to the total uncertainty<br class="">
(sigma_tot=sqrt(sigma_sys_absolute^2+(ObservableValue*sigma_sys_relative)^2 +<br class="">
sigma_statistical^2).<br class="">
<br class="">
I can elaborate more if you like on why thats the case (why absolute are more<br class="">
appropriate in my case). I will include some statements in the note to<br class="">
reflect<br class="">
this.<br class="">
<br class="">
Let me know if you would like to discuss this more.<br class="">
<br class="">
Best regards,<br class="">
Nick<br class="">
<br class="">
On Nov 4, 2017, 19:12, at 19:12, Tsuneo Kageya <<a href="x-msg://28/kageya@jlab.org" class="">kageya@jlab.org</a> <x-msg:<a href="x-msg://22/kageya@jlab.org" class="">//22/kageya@jlab.org</a>> > wrote:<br class="">
</span></font><blockquote class="" type="cite"><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""> Hi Nick,<br class="">
<br class="">
Sorry to be late to make a question.<br class="">
I have a question about the systematic error calculations.<br class="">
<br class="">
At page 35, on the table 4, you calculated the total absolute<br class="">
systematic error<br class="">
to be 0.10. How this is reflected into the total relative systematic<br class="">
error ?<br class="">
On the pi-p analysis, I think we calculated the systematic errors from<br class="">
cuts in<br class="">
the similar way and they are combined to the other errors (target and<br class="">
beam polarizations).<br class="">
Is this number 0.10 means 10 % or 0.1 % ?<br class="">
<br class="">
I may misunderstand this issue. Please let me know.<br class="">
<br class="">
Regards, Tsuneo Kageya.<br class="">
<br class="">
----- Original Message -----<br class="">
From: "g14 run-request" <<a href="x-msg://28/g14_run-request@jlab.org" class="">g14_run-request@jlab.org</a> <x-msg:<a href="x-msg://22/g14_run-request@jlab.org" class="">//22/g14_run-request@jlab.org</a>> ><br class="">
To: "g14 run" <<a href="x-msg://28/g14_run@jlab.org" class="">g14_run@jlab.org</a> <x-msg:<a href="x-msg://22/g14_run@jlab.org" class="">//22/g14_run@jlab.org</a>> ><br class="">
Sent: Saturday, November 4, 2017 12:00:03 PM<br class="">
Subject: G14_run Digest, Vol 74, Issue 3<br class="">
<br class="">
Send G14_run mailing list submissions to<br class="">
<a href="x-msg://28/g14_run@jlab.org" class="">g14_run@jlab.org</a> <x-msg:<a href="x-msg://22/g14_run@jlab.org" class="">//22/g14_run@jlab.org</a>> <br class="">
<br class="">
To subscribe or unsubscribe via the World Wide Web, visit<br class="">
<a href="https://mailman.jlab.org/mailman/listinfo/g14_run" class="">https://mailman.jlab.org/mailman/listinfo/g14_run</a><br class="">
or, via email, send a message with subject or body 'help' to<br class="">
<a href="x-msg://28/g14_run-request@jlab.org" class="">g14_run-request@jlab.org</a> <x-msg:<a href="x-msg://22/g14_run-request@jlab.org" class="">//22/g14_run-request@jlab.org</a>> <br class="">
<br class="">
You can reach the person managing the list at<br class="">
<a href="x-msg://28/g14_run-owner@jlab.org" class="">g14_run-owner@jlab.org</a> <x-msg:<a href="x-msg://22/g14_run-owner@jlab.org" class="">//22/g14_run-owner@jlab.org</a>> <br class="">
<br class="">
When replying, please edit your Subject line so it is more specific<br class="">
than "Re: Contents of G14_run digest..."<br class="">
<br class="">
<br class="">
Today's Topics:<br class="">
<br class="">
1. Re: Updated Analysis Note (Reinhard Schumacher)<br class="">
2. Re: Updated Analysis Note (Nicholas Zachariou)<br class="">
<br class="">
<br class="">
<hr align="CENTER" size="3" width="100%" class=""><br class="">
<br class="">
Message: 1<br class="">
Date: Fri, 3 Nov 2017 22:19:24 -0400<br class="">
From: Reinhard Schumacher <<a href="x-msg://28/schumacher@cmu.edu" class="">schumacher@cmu.edu</a> <x-msg:<a href="x-msg://22/schumacher@cmu.edu" class="">//22/schumacher@cmu.edu</a>> ><br class="">
To: <a href="x-msg://28/g14_run@jlab.org" class="">g14_run@jlab.org</a> <x-msg:<a href="x-msg://22/g14_run@jlab.org" class="">//22/g14_run@jlab.org</a>> <br class="">
Subject: Re: [G14_run] Updated Analysis Note<br class="">
Message-ID: <<a href="x-msg://28/a5780718-56ac-1dc0-44e8-6b991dbf849b@cmu.edu" class="">a5780718-56ac-1dc0-44e8-6b991dbf849b@cmu.edu</a> <x-msg:<a href="x-msg://22/a5780718-56ac-1dc0-44e8-6b991dbf849b@cmu.edu" class="">//22/a5780718-56ac-1dc0-44e8-6b991dbf849b@cmu.edu</a>> ><br class="">
Content-Type: text/plain; charset="windows-1252"; Format="flowed"<br class="">
<br class="">
Hi Nick,<br class="">
<br class="">
Indeed, noticeably improved.?? I recommend that you put the horizontal<br class="">
error bars on Figs.? 29 - 32, too.? They are just as important there<br class="">
since the model curves can vary a lot across one bin.<br class="">
<br class="">
Reinhard<br class="">
<br class="">
<br class="">
On 11/3/2017 7:13 PM, Nicholas Zachariou wrote:<br class="">
</span></font></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""> Dear all,<br class="">
<br class="">
I am attaching the updated note that incorporates and addresses all<br class="">
</span></font><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""> comments made. I have noticed that I have previously forgotten to<br class="">
include the systematic uncertainty associated with the<br class="">
photon-selection, and is now estimated and included.<br class="">
</span></font></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""> I would like to thank again Shumacher for his time and valuable<br class="">
</span></font><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""> insight, and everybody for the comments and feedback. If there is no<br class="">
other comments, I will be submitting the note early next week.<br class="">
</span></font></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""> <br class="">
Best regards,<br class="">
Nick<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<hr align="CENTER" size="3" width="100%" class=""><br class="">
G14_run mailing list<br class="">
<a href="x-msg://28/G14_run@jlab.org" class="">G14_run@jlab.org</a> <x-msg:<a href="x-msg://22/G14_run@jlab.org" class="">//22/G14_run@jlab.org</a>> <br class="">
<a href="https://mailman.jlab.org/mailman/listinfo/g14_run" class="">https://mailman.jlab.org/mailman/listinfo/g14_run</a><br class="">
</span></font><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""> <br class="">
--<br class="">
<hr align="CENTER" size="3" width="100%" class=""><br class="">
Reinhard Schumacher Department of Physics, 5000 Forbes Ave.<br class="">
Carnegie Mellon University, Pittsburgh, PA 15213, U.S.A.<br class="">
phone: 412-268-5177 web: <a href="http://www-meg.phys.cmu.edu/~schumach" class="">www-meg.phys.cmu.edu/~schumach</a> <<a href="http://www-meg.phys.cmu.edu/~schumach" class="">http://www-meg.phys.cmu.edu/~schumach</a>> <<a href="http://www-meg.phys.cmu.edu/~schumach" class="">http://www-meg.phys.cmu.edu/~schumach</a>> <br class="">
<hr align="CENTER" size="3" width="100%" class=""><br class="">
<br class="">
-------------- next part --------------<br class="">
An HTML attachment was scrubbed...<br class="">
URL:<br class="">
<<a href="https://mailman.jlab.org/pipermail/g14_run/attachments/20171103/651ca313/at" class="">https://mailman.jlab.org/pipermail/g14_run/attachments/20171103/651ca313/at</a><br class="">
tachment-0001.html><br class="">
<br class="">
<hr align="CENTER" size="3" width="100%" class=""><br class="">
<br class="">
Message: 2<br class="">
Date: Sat, 04 Nov 2017 07:10:14 +0000<br class="">
From: Nicholas Zachariou <<a href="x-msg://28/nicholas@jlab.org" class="">nicholas@jlab.org</a> <x-msg:<a href="x-msg://22/nicholas@jlab.org" class="">//22/nicholas@jlab.org</a>> ><br class="">
To: Reinhard Schumacher <<a href="x-msg://28/schumacher@cmu.edu" class="">schumacher@cmu.edu</a> <x-msg:<a href="x-msg://22/schumacher@cmu.edu" class="">//22/schumacher@cmu.edu</a>> ><br class="">
Cc: G14 Run <<a href="x-msg://28/g14_run@jlab.org" class="">g14_run@jlab.org</a> <x-msg:<a href="x-msg://22/g14_run@jlab.org" class="">//22/g14_run@jlab.org</a>> ><br class="">
Subject: Re: [G14_run] Updated Analysis Note<br class="">
Message-ID: <<a href="x-msg://28/d21ed42f-6b13-482d-8c8b-4ea087ad31e1@jlab.org" class="">d21ed42f-6b13-482d-8c8b-4ea087ad31e1@jlab.org</a> <x-msg:<a href="x-msg://22/d21ed42f-6b13-482d-8c8b-4ea087ad31e1@jlab.org" class="">//22/d21ed42f-6b13-482d-8c8b-4ea087ad31e1@jlab.org</a>> ><br class="">
Content-Type: text/plain; charset="utf-8"<br class="">
<br class="">
Hi Reinhard,<br class="">
<br class="">
The figures looked a bit busy when I did that (too many lines) and<br class="">
thats why i left the x-uncertainties out in those, but its takes me 2<br class="">
minutes to incorborate them. I think that will be more relevant when we<br class="">
decide exactly how to present our results in the publication.<br class="">
<br class="">
In the meantime I was wondering if its OK with the group to share our<br class="">
preliminary results with the theorists and see if we can get any<br class="">
insights from them.<br class="">
<br class="">
Best regards,<br class="">
Nick<br class="">
<br class="">
<br class="">
On Nov 4, 2017, 02:19, at 02:19, Reinhard Schumacher<br class="">
<<a href="x-msg://28/schumacher@cmu.edu" class="">schumacher@cmu.edu</a> <x-msg:<a href="x-msg://22/schumacher@cmu.edu" class="">//22/schumacher@cmu.edu</a>> > wrote:<br class="">
</span></font></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""> Hi Nick,<br class="">
<br class="">
Indeed, noticeably improved.?? I recommend that you put the horizontal<br class="">
</span></font><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""> <br class="">
</span></font></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""> error bars on Figs.? 29 - 32, too.? They are just as important there<br class="">
since the model curves can vary a lot across one bin.<br class="">
<br class="">
Reinhard<br class="">
<br class="">
<br class="">
On 11/3/2017 7:13 PM, Nicholas Zachariou wrote:<br class="">
Dear all,<br class="">
<br class="">
I am attaching the updated note that incorporates and addresses all<br class="">
comments made. I have noticed that I have previously forgotten to<br class="">
include the systematic uncertainty associated with the<br class="">
photon-selection, and is now estimated and included.<br class="">
I would like to thank again Shumacher for his time and valuable<br class="">
insight, and everybody for the comments and feedback. If there is no<br class="">
other comments, I will be submitting the note early next week.<br class="">
<br class="">
Best regards,<br class="">
Nick<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<hr align="CENTER" size="3" width="100%" class=""><br class="">
G14_run mailing list<br class="">
<a href="x-msg://28/G14_run@jlab.org" class="">G14_run@jlab.org</a> <x-msg:<a href="x-msg://22/G14_run@jlab.org" class="">//22/G14_run@jlab.org</a>> <br class="">
<a href="https://mailman.jlab.org/mailman/listinfo/g14_run" class="">https://mailman.jlab.org/mailman/listinfo/g14_run</a><br class="">
<br class="">
--<br class="">
<hr align="CENTER" size="3" width="100%" class=""><br class="">
Reinhard Schumacher Department of Physics, 5000 Forbes Ave.<br class="">
Carnegie Mellon University, Pittsburgh, PA 15213, U.S.A.<br class="">
phone: 412-268-5177 web: <a href="http://www-meg.phys.cmu.edu/~schumach" class="">www-meg.phys.cmu.edu/~schumach</a> <<a href="http://www-meg.phys.cmu.edu/~schumach" class="">http://www-meg.phys.cmu.edu/~schumach</a>> <<a href="http://www-meg.phys.cmu.edu/~schumach" class="">http://www-meg.phys.cmu.edu/~schumach</a>> <br class="">
<hr align="CENTER" size="3" width="100%" class=""><br class="">
<br class="">
<br class="">
<br class="">
<hr align="CENTER" size="3" width="100%" class=""><br class="">
<br class="">
<hr align="CENTER" size="3" width="100%" class=""><br class="">
G14_run mailing list<br class="">
<a href="x-msg://28/G14_run@jlab.org" class="">G14_run@jlab.org</a> <x-msg:<a href="x-msg://22/G14_run@jlab.org" class="">//22/G14_run@jlab.org</a>> <br class="">
<a href="https://mailman.jlab.org/mailman/listinfo/g14_run" class="">https://mailman.jlab.org/mailman/listinfo/g14_run</a><br class="">
</span></font><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><blockquote class="" type="cite"><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""> -------------- next part --------------<br class="">
An HTML attachment was scrubbed...<br class="">
URL:<br class="">
<<a href="https://mailman.jlab.org/pipermail/g14_run/attachments/20171104/14965baf/at" class="">https://mailman.jlab.org/pipermail/g14_run/attachments/20171104/14965baf/at</a><br class="">
tachment-0001.html><br class="">
<br class="">
<hr align="CENTER" size="3" width="100%" class=""><br class="">
<br class="">
Subject: Digest Footer<br class="">
<br class="">
<hr align="CENTER" size="3" width="100%" class=""><br class="">
G14_run mailing list<br class="">
<a href="x-msg://28/G14_run@jlab.org" class="">G14_run@jlab.org</a> <x-msg:<a href="x-msg://22/G14_run@jlab.org" class="">//22/G14_run@jlab.org</a>> <br class="">
<a href="https://mailman.jlab.org/mailman/listinfo/g14_run" class="">https://mailman.jlab.org/mailman/listinfo/g14_run</a><br class="">
<br class="">
<br class="">
<hr align="CENTER" size="3" width="100%" class=""><br class="">
<br class="">
End of G14_run Digest, Vol 74, Issue 3<br class="">
**************************************<br class="">
<hr align="CENTER" size="3" width="100%" class=""><br class="">
G14_run mailing list<br class="">
<a href="x-msg://28/G14_run@jlab.org" class="">G14_run@jlab.org</a> <x-msg:<a href="x-msg://22/G14_run@jlab.org" class="">//22/G14_run@jlab.org</a>> <br class="">
<a href="https://mailman.jlab.org/mailman/listinfo/g14_run" class="">https://mailman.jlab.org/mailman/listinfo/g14_run</a><br class="">
</span></font></blockquote><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""><hr align="CENTER" size="3" width="100%" class=""><br class="">
G14_run mailing list<br class="">
<a href="x-msg://28/G14_run@jlab.org" class="">G14_run@jlab.org</a> <x-msg:<a href="x-msg://22/G14_run@jlab.org" class="">//22/G14_run@jlab.org</a>> <br class="">
<a href="https://mailman.jlab.org/mailman/listinfo/g14_run" class="">https://mailman.jlab.org/mailman/listinfo/g14_run</a><br class="">
</span></font></blockquote><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""><hr align="CENTER" size="3" width="100%" class=""><br class="">
G14_run mailing list<br class="">
<a href="x-msg://28/G14_run@jlab.org" class="">G14_run@jlab.org</a> <x-msg:<a href="x-msg://22/G14_run@jlab.org" class="">//22/G14_run@jlab.org</a>> <br class="">
<a href="https://mailman.jlab.org/mailman/listinfo/g14_run" class="">https://mailman.jlab.org/mailman/listinfo/g14_run</a><br class="">
</span></font></blockquote><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""><br class="">
<br class="">
<hr align="CENTER" size="3" width="100%" class=""><br class="">
G14_run mailing list<br class="">
<a href="x-msg://28/G14_run@jlab.org" class="">G14_run@jlab.org</a> <x-msg:<a href="x-msg://22/G14_run@jlab.org" class="">//22/G14_run@jlab.org</a>> <br class="">
<a href="https://mailman.jlab.org/mailman/listinfo/g14_run" class="">https://mailman.jlab.org/mailman/listinfo/g14_run</a><br class="">
</span></font></blockquote><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""><br class="">
</span></font></blockquote></blockquote><font face="Calibri, Verdana, Helvetica, Arial" class=""><span style="font-size:11pt" class=""><br class="">
<br class="">
</span></font></blockquote>
</div>
</div></blockquote></div><br class=""></div></body></html>