ivana [Fri, 6 May 2011 15:44:38 +0000 (15:44 +0000)]
In AliMUONTracker:
Add a special case to use the vertex from ESD, even if the number of contributors is < 1, when it is taken from the simulation (using AliITSVertexerFast)
(Livio, Philippe P.)
hristov [Fri, 6 May 2011 15:41:48 +0000 (15:41 +0000)]
Fix from rev. 40001, avoids partons boosted by PYROBO endlessly:
Brute force initialisation of V(,) array at the beginning of each event
solves floating point exception (big number in V(4)).
Probably a MSTU(33) = 1 at the right position would do the same job.
jotwinow [Fri, 6 May 2011 15:12:46 +0000 (15:12 +0000)]
- new clesses added
A PWG0/dNdPt/AliPtResolAnalysis.cxx
A PWG0/dNdPt/AliPtResolAnalysisPbPb.cxx
A PWG0/dNdPt/AliPtResolAnalysis.h
A PWG0/dNdPt/AliPtResolAnalysisPbPb.h
M PWG0/CMakelibPWG0dep.pkg
M PWG0/PWG0depLinkDef.h
-- modifications by M.Knichel
M PWG0/dNdPt/AlidNdPt.h
M PWG0/dNdPt/AlidNdPtHelper.h
M PWG0/dNdPt/AlidNdPtAnalysis.h
M PWG0/dNdPt/AlidNdPtAnalysisPbPb.h
M PWG0/dNdPt/AlidNdPtHelper.cxx
M PWG0/dNdPt/AlidNdPt.cxx
M PWG0/dNdPt/AlidNdPtAnalysis.cxx
M PWG0/dNdPt/AlidNdPtAnalysisPbPb.cxx
kkanaki [Thu, 5 May 2011 14:53:04 +0000 (14:53 +0000)]
- introduction of array of data structures for holding the sets of cuts
- predefined cuts included
- cuts are printed every time the drawing method is called
- reduction of passed arguments in most methods
kleinb [Thu, 5 May 2011 09:30:49 +0000 (09:30 +0000)]
Fixes to track selection for embedding in cluster task (Bastian), Do no select events in the cluster task (switch added default no selection), adding delta pT histograms to the background subtraction
cblume [Thu, 5 May 2011 07:38:05 +0000 (07:38 +0000)]
- add support for SM header version 0xc
- read tracking and trigger headers
- read GTU trailer
- decode GTU tracks
- preparations for tracks to ESDs
- improve debug features
- some cleaning
gvolpe [Wed, 4 May 2011 17:29:52 +0000 (17:29 +0000)]
Tracking procedure updated, it is based now on AliTrackerBase method. The parameters of the constrained track to the MIP point in HMPID are used for Cherenkov angle reconstruction. Debug stream level defined in AliHMPIDReconstructor
cholm [Wed, 4 May 2011 13:53:05 +0000 (13:53 +0000)]
Added some extra scripts.
Updated SimpledNdeta
Updated ELoss vs Poisson
Updated OtherData to be more robust flexible
Updated Run.sh so one can explicitly specify
what to compare to using the -O option. The
option -J is gone. Options -A and -a allow
one to specify alternate script path and
excutable (e.g., root instead of aliroot).
Small fixes in AliBasedNdetaTask
Updated DrawdNdeta.C to allow for systematic
errors and final small corrections - e.g.,
cluster/tracklet ratio, remove outers, ...
Now also uses a bit mask of options.
hristov [Tue, 3 May 2011 10:14:01 +0000 (10:14 +0000)]
Update of the TRD PID Response:
- New reference distributions covering a momentum range from 1 to 10 GeV/c with an additional step at 1.5GeV/c. The reference in the OCDB up to now are going up to 6 GeV/c in integer momentum steps. With the change we increase the pt reach for the TRD up to 10GeV/c.
- The container type has changed: Before the references were stored in a TObjArray and associated to momentum steps and species via the name. Momentum steps were hardcoded in the PID Response, adapted to the old TRD PID code. With the new references having a different momentum binning we have seen that this is difficult to handle. A new class AliTRDPIDReference stores the reference objects together with the reference object container. The new container can handle references for all TRD PID methods.
- To keep backward compatibility the OCDB object contains the TObjArray containing the old reference objects and the reference container with the new references. In the code currently implemented the Load function checks the name of the TObject, and if it is not valid it will be neglected. In the new code we explicitly expect the new container, and all objects of a different type will be ignored. So backward compatibility is not an issue. One file in the TRD code is affected by the change, which has to be updated the same time commit is done.
- The TRD tender was also adapted to the change and the configuration was updated.
Concerning the OCDB entry since the TRD PID Response is now used in the reconstruction to calculate the TRD PID Probabilities we were concerned that we would cause problems there if we provide only the corresponding object for the new code while the reconstruction is still running with the old code. For this since the current OCDB entry stores the reference object in a simple TObjArray, we considered to be compatible with both versions of the code we add the new object to the old references. Since in the old code references which are not compatible with the name convention for the old objects are rejected, and in the new code we require the reference object to be of the new type, both versions should work with the new code.