Re: track attributes in Bdst

From: Bjorn H Samset (bjornhs@rcf2.rhic.bnl.gov)
Date: Wed Jun 18 2003 - 06:24:12 EDT

  • Next message: Hironori Ito: "[Fwd: Re: OS upgrade xv,xfig]"
    On Wed, 18 Jun 2003, Peter H. L. Christiansen wrote:
    
    > Hi Kris
    >
    > I think that you suggestion to include a fP member which is the
    > mommentum
    > from your global fit and replace the T1 projection (I guess) of phi and
    > theta with your global fit values sound very good. We should just make
    > sure that we get meaningful values even without your refit module, so
    > phi
    > and theta should be said from the Ffs track in the Fs track and the
    > momemntum should be initialised to something (0=no global fit?).
    
    This sounds good to me too, now that we seem to have consistency between
    the different momenta. I would propose to add
    * fP, containing the global momentum
    * fPMethod, integer member having:
    0 = No momentum (fP = 0)
    1 = Mom. from global fit
    2 = Mom. from FFS only (in case we don't have BFS, what's done now)
    3 = Mom. from BFS only (there are some of these events...)
    i.e. we fill fP as often as possible, and just mark how we do in. In
    addition to keeping the individual momenta like now, of course. This way
    we should be able to select the momentum sample we want pretty easily.
    Theta and phi should then be calc. from whatever fP is set to.
    
    Ping :-)
    
    -Bjorn
    
    > On Tue, 17 Jun 2003 hagel@comp.tamu.edu wrote:
    >
    > > Hello,
    > > Interested parties probably read my message regarding the global track
    fitting
    > > that I have implemented.  More details on that will emerge.  I have
    run into a
    > > problem, however.  I made Bdst files thinking I was using that
    information and
    > > then things did not make sense when I began to use them, so I started
    digging in
    > > the code (again).  Here is what I find for the Bdst tracks unless I
    > > misunderstand something.
    > >
    > > 1. theta, phi and vertices for BdstTrack are actually the theta, phi
    and vertex
    > > of the BrFfsTrack extracted from the BrFsTrack and the information
    from the
    > > BrFsTrack (as well as the information from the BrBfsTrack) is
    ignored/thrown
    > > away.  That seems strange to me as I had read the code generating the
    BrFsTracks
    > > to be an attempt to have the "global picture" which is made up of the
    compendium
    > > of information from the BrFfsTracks and the BrBfsTracks.  That is
    where I set
    > > the theta and phi that come out of that procedure.
    > >
    > > 2. There is no momentum information in the BdstTrack.  The only
    momentum saved
    > > is in the momentum information from the BdstFsTrack::fD2, fD3 and fD4.
    And
    > > there is no possibility to save information from a global track ie the
    momentum
    > > that you think is the best for the track.  I had niavely set the
    momentum of the
    > > BrFsTrack to be the momentum that comes out of the fitting procedure
    only to see
    > > it thrown away by the BdstModule::FillTrack.
    > >
    > > I would like some comments on this.  I do realize that almost all (if
    not all)
    > > of the information necessary to fit the tracks is saved in the
    BdstFsTrack.  But
    > > if one waits until after the Bdst step to generate the fit tracks, the
    > > possibility of using a perhaps better momentum to calculate pid or
    anything else
    > > that one would use momentum for is precluded.  So at least for my
    personal copy,
    > > I am going to add a BdstTrack:: momentum and I will fill the theta and
    phi with
    > > the values I get out of the fit.  After I have comments I will weigh
    what to do
    > > "officially"
    > >
    > > Regards
    > >
    > > Kris
    
    --
    Bjorn H. Samset                           Phone: 22856465/92051998
    PhD student, heavy ion physics            Adr:   Schouterrassen 6
    Inst. of Physics, University of Oslo             0573 Oslo
                                  \|/
    ----------------------------> -*- <-----------------------------
                                  /|\
    


    This archive was generated by hypermail 2.1.5 : Wed Jun 18 2003 - 06:25:03 EDT