[d2n-analysis-talk] current d2 DB

Diana Parno dseymour at andrew.cmu.edu
Thu Oct 29 18:03:21 EDT 2009


Hi Matt,

Thanks so much for looking at this and for posting your results so 
clearly. It's very helpful. But, being a neophyte with the analyzer, I'm 
still a little bit confused by what's going on. OK, a lot confused.

> To start I replayed(not full replay, too many events) the run with no
> cuts and got 685,485 events. I then applied the trigger cuts...

By replaying the run with no cuts, do you mean with the almost empty cdef 
file that you showed me last week? This is the one with just the lines as 
shown below:


 	Block: RawDecode

 	#RawDecode_master  true


 	Block: Decode

 	#Decode_master  true

When you applied the trigger cuts you speak of, was that part of a 
subsequent replay (in the replay itself), or were you applying these cuts 
to an already-replayed root file and seeing what happened?

I'm also wondering where you got your analyzer software from. I'm 
currently using the analyzer lib from the d2n branch of the CVS 
repository (checked out in September), the BB lib from the transversity 
branch of the CVS repository (checked out this week), and the DB that you 
so kindly sent me. I'm wondering if the libraries are likely to be 
different for the two of us; you mentioned that you have a 
replay_phys.cdef file, which I have never had in my setup.

Thanks again,
Diana

On Wed, 28 Oct 2009, posik at jlab.org wrote:

> Hi Diana,
>
>  I finished looking at run 1250 where the missing tracks were, you can
> find some plots I made and the description of them here as well as the
> cuts I used:
>
> http://jlab.org/~posik/1250/
>
> To start I replayed(not full replay, too many events) the run with no
> cuts and got 685,485 events. I then applied the trigger cuts but instead
> of using evtype, I used (DL.evtypebits&(1<<X))==(1<<X) where X is the
> trigger you want to cut on. The sh/ps cuts that I used are
>
> BB.ts.ps.e>800&&0.5*BB.ts.ps.e+BB.ts.sh.e>700
>
> Using just the trigger cuts seemed to only get rid of a few events
> (~1000), so I then implemented the sh/ps + trigger cuts and then I see
> there are only 412602 events left of these 190299 have one or more
> tracks.
>
> I was recently able to get a result from a onepass shower and preshower
> calibration. So I then used this calibration to see if there is any
> significant change. Again I used the same cuts as in the uncalibrated case
> and what I found was that in 685485 events after the ps/sh + trigger cuts
> was that there were 173839 events of which 94855 were one track events.
> The reason for the less one track events here I think is that the
> calibration on the ps/sh tightened up the shower+preshower energy and the
> ps energy so that the original cuts are cutting out a good amount of good
> electrons.
>
> -Matt
>
> Hi Matt,
>
> Good idea! It's run 1250; it was taken in unified-DAQ mode, so it also
> includes some LHRS data.
>
> I'm actually getting the track numbers from a macro I got from Xin (which
> is a preliminary stage in doing the optics analysis). The basic gist is
> that it's a for loop running over all the entries in the T tree in the
> root file. I inserted a line wherein I add up the value of the branch
> BB.tr.n for each entry.
>
> Initially I only added up the value of that branch for events satisfying
> the cuts
>
> ((evtype==1||evtype==2||evtype==5||evtype==6)&&pse>800.&&(pse/2.+she)>700.)
>
> which is where the ntracks=28430 number comes from. When I remove that cut
> entirely, I get 38503 tracks.
>
> Diana
>
> On Tue, 27 Oct 2009, MATTHEW R POSIK wrote:
>
>    Hi Diana,
>
>     I was wondering what run it was that you were replaying, I can try it
> on
>    my comp and see if we get the same results. Also to get the tracks are
> you
>    just plotting the BB.tr.n and making the cut BB.tr.n>=1?
>
>    -Matt
>
>    On Tue, Oct 27, 2009 at 10:44 AM, Diana Parno
> <dseymour at andrew.cmu.edu>wrote:
>
>        Thanks Matt,
>
>        I'll try it directly. It took a little time to get the BB library
> straightened out, but the new library doesn't seem to have made
> any
>        significant difference to the number of tracks.
>
>        Diana
>
>
>        On Mon, 26 Oct 2009, MATTHEW R POSIK wrote:
>
>         Hi Diana,
>
>
>             Here is a tar ball of my current d2n DB that I am working
> with. Also let
>            me know if updating the bigbite lib helps at all.
>
>            Thanks
>            Matt
>
>
>
>
> _______________________________________________
> d2n-analysis-talk mailing list
> d2n-analysis-talk at jlab.org
> https://mailman.jlab.org/mailman/listinfo/d2n-analysis-talk
>
>


More information about the d2n-analysis-talk mailing list