VUB-RECOIL Archives

Vub measurement using recoil of fully reconstructed Bs

VUB-RECOIL@LISTSERV.SLAC.STANFORD.EDU

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Heiko Lacker <[log in to unmask]>
Date:
31 May 2006 09:49:58 +0200 (CEST)Wed, 31 May 2006 09:49:58 +0200 (CEST)
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (143 lines)
Hi Chukwudi,

On Tue, 30 May 2006, Chukwudi Kweku Clarke wrote:

> Hello Heiko and all.
> Here is a more detailed note on nomenclature:
> The "a" (without a following number) stands for the use of chains located
> at;
> /afs/slac.stanford.edu/u/br/sacco/newsel-23/workdir/
> , i.e., 1DR14mm2a-010.
> .
> The "a" (when followed by a number) stands for the use of chains located
> at;
> /nfs/farm/babar/AWGsemilep01/menges/summer06/store.2/Vubrec-def/chains/
> .
> The "b" stands for the use of chains located at;
> /nfs/farm/babar/AWGsemilep01/menges/summer06/store.2/Vubrec-1111/chains/
> .
> The "c" stands for the use of chains located at;
> /nfs/farm/babar/AWGsemilep01/menges/summer06/store.2/Vubrec-1111hybrid/chains/
> .
> The "d" stands for the use of chains located at;
> /nfs/farm/babar/AWGsemilep01/menges/summer06/store.2/Vubrec-wosf/chains/
> .
> 
> The numbers refer to the use of flags:
> 1 = NO -tmodel flag
> 
> 2 = using -tmodel flag
> 
> 3 = using -tmodel -notunbinmes=3 flags.
I was refering to the kind of selection. My understanding is:
a2: default selection
b2: Michael Mazur's selection
c2: our hybrid selection starting from Michael Mazur's
d2: the selection from the 'Without shape function' analysis

> 
> > Hi Chukwudi,
> >
> > could you please give a short list saying what a2, b2, c2 and d2 means as
> > a selection? It would ease the discussion.
> >
> > 1. There are a few things which I do not understand:
> >
> >    a. Comparing the results between the different selections it looks like
> >       that PBRBR or BRBR do not agree which is worrysome. Any idea why?
> I'm not sure why this is the case. I look a several plots (like *050mES_data3)
> and some of the bins had peaking background components and some didn't.
It might vanish with the most recent tag but this is not guaranteed.

> >    b. Compared to Roberto's plots the errors are significantly larger.
> >       Did you apply the same cuts?
> I assume I used the same cuts as Roberto as I never altered anything that
> was hard coded in VVF and I fact the only things I did alter were mnscan
> (for obvious reasons) and the inclusion of the above flags.
Hm, this is strange. Maybe Roberto has an idea. Could you please try to 
contact him in person if he does not respond?

> >    c. A minor point: In diff1DR14mm2a2.eps and diff1DR14mm2d2.eps the
> >       point at mm2=0.4 has a smaller error than the one at 0.45 which
> >       can't be correct.
> I saw this myself and looking in the corresponding directories in my scra
> area (Ibu1DR14mm2a2-040 and Ibu1DR14mm2a2-045) one sees that in the
> results.dat files the stat error is less for 0.45 than for 0.4 and the
> converse is true of the Monte Carlo errors. I'm not certain how Roberto
> treated the errors but adding them or adding them in quadrature results in
> the mm2 point at 0.4 having an error less than that of the point at 0.45.
OK. Do you know how the error on the difference is then calculated
in the script? Naively, I would expect: 
sigma_diff = sqrt(sigma(0.4)^2-sigma(0.5)^2)

> > 2. We should also do the the scans for charged and neutral B's.
> I'll will do them also. How ever, It will take some time because I have
> jobs in the queues and I'm sure my priorities are getting low again.
>
> > 3. It would be good to do the scans also for Run4 separately from the
> >    other runs, e.g. Run1+2.
> It would be but the rate at which the jobs are taking to be completed is a
> concern to me and weren't we suppose to have the BAD ready by last Friday?
We will add these in the next version.

Cheers,
Heiko

> Cheers, C.C.
> 
> > Cheers,
> > Heiko
> >
> > P.S.: I can not call in right at the beginning at today's meeting.
> >       I expect to call in abo 8:45. Please start without me.
> >
> >
> >
> > On Mon, 29 May 2006, Chukwudi Kweku Clarke wrote:
> >
> > > Hi all, you can find the mm2 scans for 1D and 2D analyses using unbinned
> > > mES fits at
> > > http://www.slac.stanford.edu/~clarke1/protected/clarke1/
> > > with names like diff1DR14mm2a2.eps and brbr1DR14mm2a2.eps
> > >
> > > A note on Nomenclature:
> > >
> > > 1DR14mm2a2 : The new chains along with the -tmodel flag
> > > chains are in
> > > /nfs/farm/babar/AWGsemilep01/menges/summer06/store.2/Vubrec-def/chains/
> > >
> > > 1DR14mm2b2 : The new chains along with the -tmodel flag
> > > chains are in
> > > /nfs/farm/babar/AWGsemilep01/menges/summer06/store.2/Vubrec-1111/chains/
> > >
> > > 1DR14mm2c2 : The new chains along with the -tmodel flag
> > > chains are in
> > > /nfs/farm/babar/AWGsemilep01/menges/summer06/store.2/Vubrec-1111hybrid/chains/
> > >
> > > 1DR14mm2d2 : The new chains along with the -tmodel flag
> > > chains are in
> > > /nfs/farm/babar/AWGsemilep01/menges/summer06/store.2/Vubrec-wosf/chains/
> > > ---------------------------------------------------------------
> > > 2DR14mm2a2 : The new default chains along with the -tmodel flag
> > > chains are in
> > > /nfs/farm/babar/AWGsemilep01/menges/summer06/store.2/Vubrec-def/chains/
> > >
> > > 2DR14mm2b2 : The new chains along with the -tmodel flag
> > > chains are in
> > > /nfs/farm/babar/AWGsemilep01/menges/summer06/store.2/Vubrec-1111/chains/
> > >
> > > 2DR14mm2c2 : The new chains along with the -tmodel flag
> > > chains are in
> > > /nfs/farm/babar/AWGsemilep01/menges/summer06/store.2/Vubrec-1111hybrid/chains/
> > >
> > > 2DR14mm2d2 : The new chains along with the -tmodel flag
> > > chains are in
> > > /nfs/farm/babar/AWGsemilep01/menges/summer06/store.2/Vubrec-wosf/chains/
> > >
> > > Cheers, C.C.
> > >
> >
> 



ATOM RSS1 RSS2