Sasha, privet!<br><br>I have a simple question: do we need to use trip detection at all?<br>Can you provide normalized to the flux yield (pp-+pi-, or any other combination)<br>for selected with trip detector events and just for all events. I mean take all events with<br>
flux from the trip, bad or good.<br>Based on these numbers we can judge, do we need it or not. What do you think?<br>g12 is not PRIMEX, we don't need very good absolute normalization.<br><br>Valery<br> <br><br><div class="gmail_quote">
On Wed, Apr 13, 2011 at 9:22 PM, Alexander Ostrovidov <<a href="mailto:ostrov@hadron.physics.fsu.edu">ostrov@hadron.physics.fsu.edu</a>> wrote:<br>
<blockquote class="gmail_quote"><div>On Wednesday, April 13, 2011, Eugene Pasyuk wrote:<br>
> In your first example it is clear that trip detection failed the second<br>
> interval should have status "0"<br>
><br>
<br>
</div>Eugene,<br>
<br>
I'm getting an impression that if trip detection by sync followed by<br>
tripFixer can so easily fail on such good looking interval then<br>
it's even more likely to fail in many other places as well.<br>
<br>
Live time peak for this run 57129 is 0.8019 with a sigma of 0.0209<br>
(Gaussian fit). The interval I gave has LT of 0.813. It's well within<br>
LT peak and should survive any LT cut. Same story for the number<br>
of events. Yet it was still marked as bad by sync/tripFixer.<br>
<br>
This is not an insignificant problem. Run 57129 which I looked carefully at<br>
contains 768 scaler intervals. Not a small run - about 2 hours of running.<br>
251 intervals are marked with status "1". By my eyeball estimate, about<br>
150 of them look perfectly normal in terms of the number of events and<br>
average live time. If "trip detection failed" in 1/5 of all scaler intervals then<br>
this should be of some concern, right?<br>
<br>
As I understood you, your suggested solution is to ignore interval's beam trip<br>
status after sync. Don't use tripFixer at all - what the point? Just determine<br>
LT threshold on per run basis, and use LT cut to correct interval status<br>
in the trip files for all intervals (not just the ones merged together from<br>
previously split files). Is this that simple?<br>
<div><br>
Sasha<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
G12 mailing list<br>
<a href="mailto:G12@jlab.org">G12@jlab.org</a><br>
</div><div><div></div><div><a href="https://mailman.jlab.org/mailman/listinfo/g12">https://mailman.jlab.org/mailman/listinfo/g12</a><br>
</div></div></blockquote></div><br>