Aron,
just to let you know that there is a wch ntuple: look into wch_ntuple.C of
course. This ntuple will store each physics event Nhits times, where
Nhits is the number of wch hits. So if in the ntuple you cut on physics ev
number you will have all the wch hits related to it.
This was done to address the issue of ntuple with varying number of
fields. Of course you could restrict to events with, say, 40+40 hits but
then you would need a tree structure (see scaler_ntuple.C) since the
ntuple fileds will be close to 100.
Now you may just want to take wch_ntuple, copy it over, add the tracks and
restrict output(filling) only to events with meaningful tracks. This
essentially corresponds to recrunching. If it is a lot of files, it could
be a cpu problem right now
-- ________________________________________________________________________________ Tancredi Botto, phone: +1-617-253-9204 mobile: +1-978-490-4124 research scientist MIT/Bates, 21 Manning Av Middleton MA, 01949 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^On Sat, 21 Jun 2003, zhangchi wrote:
> > hi, Aaron: > > in current v3, for each TBLTrack, a list of hits used in it can be > accessed in the following manner: > > TBLTrack& track = ...; > TBLWc1Hit hit[18]; > > for (int i=0; i<18; ++i) > hit[i] = track->fFit->fHITS[i].fwc1; > > This get a COPY of TBLWc1Hit's used by this track into hit[18]. you know > how to changed it to pointer semantics. > > Unfortunately, I am on my way to change this structure. namely, the > copy/reference to the TBLWc1Hit will be replaced by a long int which > include Key/tdc/side information of the used hit. So the above few lines > will have to be changed to something like: > > TBLTrack& track = ...; > TBLWc1Hit hit[18]; > > for (int i=0; i<18; ++i) > hit[i] = TBLWc1Hit(tdc(track->fFit->fHITS[i].key), > key(track->fFit->fHITS[i].key)); > > which creates a TBLWc1Hit from the info contained by: > T_Key TBLHit::key; > > all these apply only to v3. > > lrn.C could be easily changed to adapt to current v3 which we > affectionately call 2.96 :). Again unfortunately, the real v3 will change > some sematics so it is not compatible with 2.96. but the changes to your > scripts/programs shall be just a little. limited to probably no more than > 10 lines. > > Chi > > On Sat, 21 Jun 2003, Aaron Joseph Maschinot wrote: > > > > > i'm trying to do a WC efficiency study. to do so, i need to have access > > to the list of hits corresponding to each track that successfully gets > > reconstructed (i also need the list of corresponding keys for each of the > > hits). does anyone know how to access these values? i'm pretty sure it > > should be done through the TBLTrack class somehow. > > > > aaron > > > > >
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:29 EST