On Fri, Mar 19, 2010 at 12:54 PM, <<a href="mailto:posik@jlab.org">posik@jlab.org</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote">
Hi all,<br>
<br>
So after our meeting yesterday, I decided to look at the cuts that I was<br>
using. So what I did is used the first ~500k or so events from run 2060<br>
and applied one by one the cuts that I was using. What I found was that<br>
using BB.tr.n==1 killed about 95% of the events. I know that we are<br>
going to be a lot of BB.tr.n!=1 tracks, but 95% seems high. The rest of<br>
the cuts that I used didn't seem to drastically affect the statistics.<br>
<br>
Here is a summary of how the statistics changed with various cuts.<br>
<br>
<a href="http://www.jlab.org/%7Eposik/d2n/BB/cer/cer_cuts/cer_cut_summary.txt">http://www.jlab.org/~posik/d2n/BB/cer/cer_cuts/cer_cut_summary.txt</a><br></blockquote><div><br>run 0 already includes the 1-track cut (BB.tr.n==1) the n signifies the number of tracks (compare to L.tr.n => number of tracks). <br>
<br>In which case, I find it odd that 'run 1' gives ~2x the amount of events after run 0.<br><br>Maybe start with the momentum cut + z-vertex reconstruction cut as your 'standard' cut, then tack on the BB.tr.n cut and see what happens?<br>
<br> <br></div></div><br>-- <br>-----------------------------------------------------------<br>David Flay<br>Physics Department<br>Temple University<br>Philadelphia, PA 19122 <br><br>office: Barton Hall, BA319<br>phone: (215) 204-1331<br>
<br>e-mail: <a href="mailto:flay@jlab.org">flay@jlab.org</a> <br> <a href="mailto:flay@temple.edu">flay@temple.edu</a><br><br>website: <a href="http://www.jlab.org/~flay">http://www.jlab.org/~flay</a><br> <a href="http://quarks.temple.edu">http://quarks.temple.edu</a><br>
-----------------------------------------------------------<br><br><br>