Bugfix in AliPoints2Memory
[u/mrichter/AliRoot.git] / AliGeant4 / doc / history / TGeant4_geometry_History
... / ...
CommitLineData
1$Id$
2-----------------------------------------------------------------
3
4TGeant4/geometry:
5=================
6 20.11.01:
7 TG4GeometryManager
8 added support for MANY - using new methods implemented
9 in G3toG4.
10
11 21.8.01:
12 Added checking of materials - a new material is built only
13 if it is different from the existing ones.
14 Mapping of tracking medium properties had to be changed
15 from mapping per material to mapping per logical volume.
16 The input material names, tracking medium IDs and names
17 are preserved in TG4Limits names.
18
19 TG4GeometryManager
20 medium id vector (TG4intVector, material id -> medium id)
21 changed to medium map (TG4IntMap, logical volume name -> medium id);
22 TG4GeometryServices
23 added methods for finding, comparing materials,
24 for finding logical volumes, user limits,
25 methods for generating limits names, for printing;
26 TG4Limits (in global)
27 added name composed from the input material name,
28 tracking medium ID and name.
29
30 9.8.01:
31 TG4VSensitiveDetector:
32 moved to digits+hits;
33 TG4GeometryManager, TG4GeometryServices:
34 methods dependent on sensitive detectors separated
35 to TG4SDManager, TG4SDServices (digits+hits).
36
37 19.12.00:
38 TG4GeometryServices: a new class separated from
39 TG4GeometryManager; it provides service methods for accessing
40 to Geant4 geometry, namely using AliMC volumes and materials
41 identifiers.
42
43 9.10.00:
44 XML implementation:
45 - solids are stores in XML with names of logical volumes
46 (as solids names are not unique)
47 - the length parameters in XML are multiplied by 2.
48 - element poxXYZRot -> transform
49 TG4XMLGeometryGenerator:
50 added fVolumeNames - set for remembering logical
51 volumes already processed; this ensure that each lv
52 is processed only once.
53
54 28.7.00: new classes:
55 TG4XMLGeometryGenerator: class for generation of geometry data
56 files in XML; the XML format is independent from G4 geometry
57 object model. The interface TG4VXMLConvertor is used for
58 writing XML elements; more than one implementation of XML
59 convertor can be used -> more than one dtd geometry descriptions
60 can be supported.
61 TG4VXMLConvertor: interface for XML convertor that provides
62 methods interfaces for converting G4 basic geometry objects
63 to XML description
64 TG4XMLConvertor: concrete implementation of XML convertor
65 generating XML elements according to AGDD.dtd
66 (ATLAS Generic Detector Description)
67 Only subset of G4 solids are implemented;
68 Not yet implemented:
69 materials, rotation matrices, replicated volumes.
70
71 6.6.00:
72 TG4NameMap moved to g4mc/global;
73 as it is used also in TG4PhysicsManager
74 for mapping names of particles between
75 G4 and TDatabasePDG
76
77 13.4.00:
78 TG4NameMap: new class;
79 defines a map for associated names;
80 it is used in TG4Geometry manager for the map of
81 G3 volume names with the modules name;
82
83 28.3.00:
84 New subcategory:
85 Classes: TG4GeometryManager, TG4GeometryOutputManager,
86 TG4VSensitiveDetector, TG4ElementTable
87