cholm [Tue, 6 Dec 2005 20:56:06 +0000 (20:56 +0000)]
Added new library libFMDutil. This library contains utility classes that
are mainly used for FMD specific tasks, such as reading in FMD data, and so
forth. Therefor, it's put in a separate library to not crowd the normal
libraries and binaries with extra code. See the file AliFMDInput.cxx
for more info. Updated some of the scripts to use this interface.
Added some docs to some scripts.
Added script to get X-sections, energy loss, and ranges for a given
medium for a given particle type from TGeant3TGeo.
Added a script that compiles and loads other scripts :-)
cholm [Mon, 5 Dec 2005 22:58:41 +0000 (22:58 +0000)]
Fixed a compilation warning.
Please note, that the previous commit might entail that
AliFMDGeometryBuilder and derived is moved from libFMDsim to libFMDbase,
as AliFMDGeometry depends on it.
cholm [Mon, 5 Dec 2005 22:52:09 +0000 (22:52 +0000)]
Added the class AliFMDGeometryBuilder (and derived
AliFMDGeometryBuilderSimple) that defines the geometry. AliFMDGeometry
uses that class. AliFMDGeometry can also get crucial information from
a predefined class (but more needs to be extracted from the TGeoManager).
The code has been changed to reflect this. In particular, the class
AliFMDSimulator is largely obsolete. I've kept it for a while, as I'd
like to test what penalty one endure from such a class. I believe
it is negligible, but Federico thinks it's not.
The AliFMDG3Simulator and derived can essentially disappear.
Fixed some compilation warnings in AliFMDReconstructor.
timms [Fri, 2 Dec 2005 11:17:04 +0000 (11:17 +0000)]
AliHLTTPCSpacePointData:
new variable Bool_t fUsed // only needed in AliHLTGUI
AliHLTTPCClusterFinder:
set variable fUsed = KFALSE // only needed in AliHLTGUI
AliHLTTPCDisplay:
Rename and Merge of functions
Complete new arrangement in order to use the AliHLTGUI
- 3D Geometry
- display padrows, cluster, tracks
- select single Tracks
- select used / unused cluster
- Histogram
- display padrows
- display pads in padrows
martinez [Mon, 28 Nov 2005 16:27:10 +0000 (16:27 +0000)]
Making AZ cluster finder and Kalman tracking the default methods (see README how to go back to old defaults (VS clustering and Original tracking)) (Sacha)
hristov [Mon, 28 Nov 2005 15:51:35 +0000 (15:51 +0000)]
Alignment framework (C.Cheshkov). More information is available in http://agenda.cern.ch/askArchive.php?base=agenda&categ=a057717&id=a057717s1t6/transparencies
cholm [Sun, 27 Nov 2005 16:17:57 +0000 (16:17 +0000)]
Commiting before moving code from `AliFMDSimulator' to `AliFMD' (and
sub-classes), as `requested' by Federico. The definition of materials,
and the like will move to `AliFMD' directly - cluttering up the class
even more than it is already (sigh!). The step-management will go
in `AliFMDv1' (and relevant sub-classes). The geometry definition will
go in the new class `AliFMDGeometryBuilder' (and sub-classes), to at least
keep that out of the `AliFMD' and to make it easier to make changes to
the geometry (via inheritance).
Federico also complains about the size of the digits. I'm not sure that
I understand his complaint, but we'll see.
The `AliFMDG3Simulator' (and sub-classes) will disappear completely. That
means, that the VMC _must_ support a geometry based on the ROOT `TGeo'
classes - rather than via calls to the GEANT 3.21-like member function
calls. This commit will be tagged.
I've temporarily added the class `AliFMDAlla' which is Alla's old
implementation of the FMD geometry. This class will disappear.
ivana [Tue, 22 Nov 2005 14:16:13 +0000 (14:16 +0000)]
Refactoring of geometry classes:
- AliMUONGeometryModules are accessed via a new AliMUONGeometry class
- Transformations data are separated in AliMUONGeometryTransformer,
AliMUONGeometryModuleTransformer classses
- AliMUONGeometryDetElement objects contain always transformation in
a new ALIC refernce frame
- Read/Write functions moved from AliMUONVGeometryBuilder
in AliMUONGeometry (svmaps) and AliMUONGeometryTransformer
(transformations)
ivana [Tue, 22 Nov 2005 14:07:22 +0000 (14:07 +0000)]
Updated with refactoring of geometry & segmentation classes;
- segmentations are not built explicitely but either via AliMUON
or via AliMUONSegFactory classes
- added option in MUONTest for selecting the way of building
segmentation
ivana [Tue, 22 Nov 2005 14:03:57 +0000 (14:03 +0000)]
Refactoring of geometry classes:
- AliMUONGeometryModules are accessed via a new AliMUONGeometry class
- Transformations data are separated in AliMUONGeometryTransformer,
AliMUONGeometryModuleTransformer classses
- AliMUONGeometryDetElement objects contain always transformation in
a new ALIC refernce frame
- Read/Write functions moved from AliMUONVGeometryBuilder
in AliMUONGeometry (svmaps) and AliMUONGeometryTransformer
(transformations)
ivana [Tue, 22 Nov 2005 14:01:05 +0000 (14:01 +0000)]
Removed all geometry & segmentation info:
- Rmin, Rmax, Z have to be taken from AliMUONConstants
- AliMUONGeometryModules - from AliMUONGeometry
- AliMUONGeometrySegmentations - from AliMUONSegmentation