Re: [BLAST_ANAWARE] dst/crunch update V: crunching going on spuds

From: zhangchi (zhangchi@general.lns.mit.edu)
Date: Sun Jan 04 2004 - 19:04:38 EST


Hi,

I guess I know what is your problem. Not like the default settings in
blast account which Chris setup for reversed field, the default blastrc
environment is for NORMAL field! try invoke what ever program you are
using to crunch or display with option "-bm -1".

and a few clean up cuts is by default turned off in nsed. try nsed with
the following additional options: +Recon.ScreenTrack +Recon.PickZ. This
will give you very clean one track per sector for both those events.

Hope this would solve your problem, let me know if it don't work.

Chi

On Sun, 4 Jan 2004, Adrian T Sindile wrote:

> Hi, Chi!
> I checked out (from scratch) from CVS as specified in the previous email.
> I should now have everything like the blast account, right?
> How did you get e-p events?
> If I run nsed (not my own cruncher) again and look for the results you
> mentioned:
>
> > I ran nsed on 3691 and I have the following ep events by the program:
> > 145, 229, 348, 610, 676, 1037, 1091, 1337, 1553, 1599. 10 of them, not
> > very shabby compare to 7 with old version. In fact the new version is
> > constantly getting a 40-50% more tracks than 2_96. I believe with the
> > proposed new calibration, we will get even more tracks.
> > these events are all recongnized by the program as havine on electron in
> > one sector and a proton in the other sector. some electrons are
> > misidentified as pi-.
>
>
> ... this is what I get for first two events (145 and 229):
>
> Event Number: 145
> nw 0 pion- : Sec 1 SC10 CC-1 NC-1 q-1 : M=0.96324 X2M=34.82648
> p=0.51019
> L=379.72 T=27.06 V=14.04 SC_Y=89.70 X2SC=62.94
> nw 1 pion+ : Sec 0 SC 6 CC 1 NC-1 q 1 : M=0.13957 X2M=0.00000
> p=0.55892 trig
> L=428.17 T=14.71 V=29.11 SC_Y=-23.90 X2SC=43.72
> nw 2 pion+ : Sec 0 SC 6 CC 1 NC-1 q 1 : M=0.00033 X2M=0.99525
> p=0.55512 trig
> L=458.81 T=14.71 V=30.00 SC_Y=-23.90 X2SC=44.48
> nw 3 pion+ : Sec 0 SC 6 CC 1 NC-1 q 1 : M=0.00033 X2M=0.99525
> p=0.55543 trig
> L=487.06 T=14.71 V=30.00 SC_Y=-23.90 X2SC=45.36
> nw 4 positive : Sec 0 SC-1 CC 1 NC-1 q 1 : M=0.00000 X2M=nan p=0.54389
> L=0.00 T=-25.89 V=nan SC_Y=0.00 X2SC=-1.00
> nw 5 electron : Sec 0 SC 6 CC 1 NC-1 q-1 : M=0.10311 X2M=40314.84870
> p=0.32292 trig
> L=420.11 T=14.71 V=28.58 SC_Y=-23.90 X2SC=40.74
> nw 6 negative : Sec 0 SC-1 CC 1 NC-1 q-1 : M=0.00000 X2M=nan p=0.15937
> L=0.00 T=-25.89 V=nan SC_Y=0.00 X2SC=-1.00
> nw 7 negative : Sec 0 SC-1 CC 1 NC-1 q-1 : M=0.00000 X2M=nan p=0.16260
> L=0.00 T=-25.89 V=nan SC_Y=0.00 X2SC=-1.00
>
>
>
> Event Number: 229
> nw 0 pion- : Sec 0 SC13 CC-1 NC-1 q-1 : M=0.85115 X2M=25.99257
> p=0.23130
> L=292.39 T=37.19 V=7.87 SC_Y=14.20 X2SC=8.98
> nw 1 pion+ : Sec 1 SC 2 CC 0 NC-1 q 1 : M=0.13957 X2M=0.00000
> p=0.74307 trig
> L=451.59 T=15.32 V=29.48 SC_Y=22.50 X2SC=1.48
>
>
> They do not look like e-p events here... I agree they look nice on the
> nsed display, but how can I know they are e-p if nsed misidentifies them?
> How can I reproduce your nsed's results (or how do you know they were
> e-p)?
> Thanks for looking into this!
>
> Adrian
>



This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:30 EST