From: Flemming Videbaek (videbaek@sgs1.hirg.bnl.gov)
Date: Wed Mar 26 2003 - 09:48:57 EST
It may be weird but it is correct it was wrong .
The position was 0,0,0 but the direction vector ok!
On the other issue I think we have to think hard how to do correction's - this pos correction is used
as far I understand only for tof matching, but if one understood the TPC better and made corrections one should
really not have two different representations of the same track.
For software as such we have a bit much of this kind of stuff. (momentum scales, angle rotations,small detector offsets
hardcoded, etc....) It may well be that
we need to apply these but it should be done in a consistent way throughout the analysis.
cheers
Flemming
------------------------------------------------------
Flemming Videbaek
Physics Department
Brookhaven National Laboratory
tlf: 631-344-4106
fax 631-344-1334
e-mail: videbaek@bnl.gov
----- Original Message -----
From: "Djamel Ouerdane" <ouerdane@nbi.dk>
To: "devlist" <brahms-dev-l@bnl.gov>
Sent: Wednesday, March 26, 2003 9:10 AM
Subject: Re: brat 2.8.10
| Hi Flemming,
|
| Sounds weird to me since I made a test with the default setting (obvious
| thing to do) and could reproduce the old behaviour of the T2-H1 pointing.
| Now, about the T2 position correction, it should be done earlier than the
| tof-track matching, simply because the FFS track pointing is done in
| BrFfsTrackingModule and not after. Later in the reconstruction, the
| corrected position should still be known. That's why I implemented a non
| persistent member in BrDetectorTrack, unless you want to move the track
| pointing to the tof plane to the tof-track matching module.
|
| Djam
|
|
This archive was generated by hypermail 2.1.5 : Wed Mar 26 2003 - 09:47:17 EST