Brat 2.6.5

• Previous message: Stephen J. Sanders: "minor brat changes to allow Macintosh OS 10.2 compilation"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Hi All,
I upgraded BrFsTrackingModule and added a new class
track/combine/BrDcEnhancementModule.{h,cxx}
It required some additional modification of  files in
modules/track/combine, namely:
Include.h, Makefile.am, LinkDef.h.

The changes have been committed and the brat revision number incremented
by 1, so now we have BRAT-2-6-5.

Let me write a few words about how the BrDcEnhancementModule is combined
with the rest
of the track/combine stuff.

BrDcEnhancementModule does a local tracking in T3 and/or T5 but it
utilizes global tracks produced
in BrBfsTrackingModule. The new T3/T5 tracks are build from hits stored
in RdoDC T{3,5} tables
which are produced during the first data reduction level.
In the present release BrDcEnhancementModule (like BrFfsTrackingModul
and BrBfsTrackingModule) is
used inside BrFsTrackingModule. It searches for BfsTracks with one
extended BrMatchedTrack component,
and does local tracking using the extended component as a "seed". If it
succeeds
the new local track is written to the BrDetectorTrack table and a
particular BfsTrack is updated with
a new BrMatchedTrack with a status set to kVirtual and kOk (which means
that is you call match->GetStatus() the
returned number is 17.) In general all the updates of BfsTables with a
new information is done inside BrDcEnhancementModule. The net effect is,
that some (or all) of the initial Bfs Tracks with a virtual component
are replaced by Bfs Tracks with ok+virtual component with a associated
new local tracks (in T3/T5). The momentum is
also recalculated by using BrModuleMatchTrack.

The status ok+virtual allows to distinct this tracks from the rest of
"ok" tracks, in the later stage of analysis.

In order to take an advantage of this new module you should setup the
global fs tracking like in the example below:

// fs tracking:
BrFsTrackingModule* fsmod = new BrFsTrackingModule("FS", "FS Tracking");

  fsmod->SetEnhanceMode("T3 T5"); // you can use only "T3" or only "T5"

// bfs tracking:
BrBfsTrackingModule* bfs = fsmod->GetBfsModule();
  bfs->SetKeepMatched(kTRUE);
  bfs->SetExtendD3Match(kTRUE);
  bfs->SetExtendD4Match(kTRUE);
  bfs->SetCleanUp(BrBfsTrackingModule::kCUT2, kTRUE);
  bfs->SetCleanUp(BrBfsTrackingModule::kCUT3, kFALSE);

Please, refer to script ps_app/fs/globtrac/effStudy.C for a more
comprehensive example.

My new efficiency calculation (which I hope will be complited soon) will
assume the usage of
BrDcEnhancementModule. This means that we need (Djamel) to update the
common global tracking script.

Regards Pawel.

--
 ----------------------------------------------------------------------
| Pawel Staszel                                                        |
| Niels Bohr Institute Tb 8    email:      staszel@nbi.dk              |
| Blegdamsvej 17               phone:      (+45) 35 32 53 51           |
| København Ø                    FAX:      (+45) 35 32 50 16           |
| Danmark                                                              |
 ----------------------------------------------------------------------

• Next message: Kris Hagel: "new monitor in operator account"
• Previous message: Stephen J. Sanders: "minor brat changes to allow Macintosh OS 10.2 compilation"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.5 : Tue Dec 17 2002 - 10:04:36 EST