[Brahms-dev-l] sigma range != sigma cut

Hello again,

A long time ago, I introduced an elliptical cut in the matching parameter 
space (dY, dAly, dAng). The thing is that there are two kinds of sigma 
"cuts", one using fSigmaRange and the other one using fSigmaCut.

By default fSigmaRange = 4 and fSigmaCut = 3.

The elliptical cut is using fSigmaRange while the _track status_ is 
determined with fSigmaCut. The latter is not based on an elliptical cut 
but just independent cuts of the three parameters. I just discovered that. 
How does it show up in real life ? Here it goes : 
When in my config script, I write:

BrModuleMatchTrack::SetSigmaCut(20.)

the matching histograms will however show a much stringent cut. It's 
because fSigmaRange was not set in the script and uses the default value 
of 4 sigmas.

I guess this one can be explained by Flemming :) I think I see the point
of having two kinds of sigma range (a loose one for cleaning up bad
combinations, and a more strict one to set a flag for analysis but that
does not imply track removal at the reconstruction stage). Buuut! calling
the latter fSigmaCut is then really confusing...The proof is that what I 
thought was a loose cut (TrackOffset.C) was in fact pretty strict! :)

Maybe it's not clear to most of you but experts will certainly 
understand :)

Djam


-- 
Djamel Ouerdane ------------------------------------------o
|  Niels Bohr Institute      |  Home:                     |
|  Blegdamsvej 17, DK-2100 Ø |  Jagtvej 141 2D,           |
|  Fax: +45 35 32 50 16      |  DK-2200 Copenhagen N      |
|  Tel: +45 35 32 52 69      |  +45 35 86 19 74           |
|                  http://www.nbi.dk/~ouerdane            |
|                  ouerdane@nbi.dk                        |
o---------------------------------------------------------o


_______________________________________________
Brahms-dev-l mailing list
Brahms-dev-l@lists.bnl.gov
http://lists.bnl.gov/mailman/listinfo/brahms-dev-l