ivana [Thu, 16 Apr 2009 08:50:17 +0000 (08:50 +0000)]
In AliMUONLocalTriggerBoard:
Adding methods to check separately if the bending or non-bending plane
triggered. The methods are useful when re-building the trigger response
for checks.
(Diego)
ivana [Wed, 15 Apr 2009 11:20:14 +0000 (11:20 +0000)]
In trigger classes:
- Fill the "global input" words read from the raw data into the reconstructed
object, via a patch to AliMUONDigitMaker::ReadTriggerDDL
- Type correction in AliMUONRawStreamTriggerHP.h
(Bogdan, Artur)
ivana [Fri, 10 Apr 2009 09:52:00 +0000 (09:52 +0000)]
In AliMUONVTrackReconstructor:
Change the range of theta angles for trigger tracks to match the convention
adopted for tracker tracks (the shift of pi does not affect the Tan(theta)
which is used elsewhere in the code).
(Diego)
Putting the correct vzero information in the tags - only total multiplicity and number of fired cells on the A and C side. Correct filling of these data in AliESDTagCreator class.
Summary of changes:
- Change sign of deflection length (previously inconsistent with TRAP model,
to be clarified which one is used in reality)
- decrease windows for track matching, possible due to better tracklet parameters
- Change handling of output tree (not owned by current directory after creation)
- check for a = 0 in pt-calculation
- added GetLabel to AliTRDtrackletGTU
- change CookLabel according to other changes (offset of 1 in label)
Update of the tag system. 1. Correct implementation of the event ID - period, orbit ID and bunch-crossing number. 2. Adding the information relevant to the reconstruction of the first LHC data which will be taken with a bunch-srossing trigger. The information is related to same basic quantities related to the activity in SPD and VZERO. This information should be enough in order to identify the events on which one would run the full aliroot reconstruction. 3. A bug fix in the trigger and trigger-cluster selection in AliEventTagCuts.cxx (Panos)
major TRD reconstruction update
- update clusterizer for flexible switch between methods to calculate
r-phi cluster position. Currently the following methods are supported:
- COG - center of gravity
- LUT - look up table [default]
- GAUS - gauss approximation [testing phase]
- move position calculation related code from clusterizer to the
cluster
itself
- steering options for cluster position calculation
implemented at Reconstructor level.
- user help via static method
AliTRDReconstructor::Options() function
- consistent pad row cross implementation in the
tracklet. Reference
radial position for pads crossing pad row is
recalculated based on z
cluster charge distribution.
- miscellaneous
major TRD reconstruction update
- update clusterizer for flexible switch between methods to calculate
r-phi cluster position. Currently the following methods are supported:
- COG - center of gravity
- LUT - look up table [default]
- GAUS - gauss approximation [testing phase - to production]
- move position calculation related code from clusterizer to the cluster
itself
- steering options for cluster position calculation implemented at Reconstructor level.
- user help via static method AliTRDReconstructor::Options() function
- consistent pad row cross implementation in the tracklet. Reference
radial position for pads crossing pad row is recalculated based on z
cluster charge distribution.
- miscellaneous
The variable fSeed is not really needed as the fitter is called in a way that the seeding is done only once. Apparently its presence caused a bug when the fitter is used to fit set of tracks and the fit fails at some point. Then fSeed was not properly reset and all the consequtive fits used the seed at the point of failure. Thanks for Dariusz for reporting the problem.
All:
- Speed up the computation/selection of primary track candidates (by up to a factor 100)
- Improve computation of initial covariance matrices for Kalman
- Use specific covariance matrices when there is no magnetic field
- fix potential bug by reordering cluster/track selection
- fix selection of track candidates when there is no magnetic field
- new protection against tracking divergences (see below)
AliMUONRecoParam:
- change Cosmic settings
- New parameter: maximum number of trigger tracks above which the tracking is cancelled
- New parameter: maximum number of track candidates above which the tracking abort