Detector_Split_Branch project

Advantages of the new geometry

• Sensors stored in a typed, specialized TPhSensorSet container,

- this makes it easy to write processing functions taking a TPhSensorSet parameter to define a geometric scope of processing operations.

• TPhSensorSet class has a list of other sensor set type objects, pointers to sensors can be stored in multiple sensor sets

- this makes it possible to define multiple, user defined logical sets of sensors that are most convenient for the user from the point of view of particular application that he is implementing
- an extended tree of logical structures consisting of subdetectors, layers, planes and modules has been designed and is implemented by creating them from predefined sets

• Both sensors and sensor sets are TNode type classes that derive from a common TPhSensorNode class

- geometrical parameters of all sensors are stored in the the appropriate TShape objects
- since TPhSensorNode derives from TNode , the new geometry is constructed exclusively of objects that derive from TNode, thus geometry visualization functions of ROOT can be automatically used,
- TPhSensorNode class provides basic geometrical and sorting operations that are not present in ROOT
- It is now possible to do geometrical transformations not only on a sensor by sensor level, but also on their sets by applying transfomations to sensor sets. The chnages in a position of a sensor set are automatically propagated to all sensors (and their subsets) in the current sensor set.

• A backward compatibility is fully supported, however ROOT files with geometry information will have to be regenerated.
• Sensors stored in a typed, specialized TPhSensorSet container,

TPhDetector

• Pointer to TPhGeometry created in TPhDetector
• Geometry functions and pointers to subdetectors and sensors moved to TPhGeometry
• Access to geometry functions provided through deprecated functions in TPhDetector
• TPhDetector
• AddHit
• DeleteHits
• ClearHits
• BuildSensorList
• GetSubDetectorList
• GetSubDetector
• GetSubDetectorOfSensor
• GetSubDetectorOfSensor
• GetNumSensors
• GetSensor
• GetClosestSensor
• Processing functions moved to temporary data processing classes
• TPhDataOnDetector
• FillWithEventHitArrays
• FillWithEventHits
• MakeCalRawHitFECs0
• MakeHitArrays
• MakeHitArrays
• MakeHitArraysOutOfHits
• MakeHitLists
• MakeHits
• MakeHitsOutOfHitArrays
• MakeRawHitFECn0
• MakeRawHitFECs0
• TPhFECRawProperties
• CMNProcess
• NoiseProcess
• PedPreProcess
• PedProcess
• ZeroSuppress

TPhGeometry

• Adam Trzupek TPhGeometry class has been merged with TPhGeoDetector
• TPhGeometry inherits from TGeometry
• It contains a pointer to a mother sensor set and 2 lists, one with all sensors and the other with all sensor sets
• In the first step, geometry is constructed by creating (adding) sensors to a set of predefined subdetectors
• In the second step, a structure of specialized geometry classes (TPhSensorLayer, TPhSensorPlane, TPhSensorModule inheriting from TPhSensorSet) is built. Definitions of sets of sensors belonging to these objects, can be found in header files of the corresponding classes.
• Label numbers of layers, planes and modules start from zero in each subdetector separately.
• At the beginning all specialized sensor sets of the initial TNode linked structure will be located at 0 in mother (Phobos) reference frame.
• When created, sensors are connected to subdetector nodes. During the second step of construction, layers, planes or modules overtake parenthood.
• Currently, the TPhSensorSet::Overtake.. () functions work only for nodes with an "Identity" rotation matrix,
• 
  later there may be a function provided to recalculate sensor positions after moving a node to a different position, or after moving sensors to a different node (sensor set).

TPhSensorNode

• This is an extension of TNode class, providing geometrical transformation functionalities not present in ROOT TNode class or specific to Phobos requirement - e.g. lazy evaluation of the parameters of transformation to Mother reference frame.
• It may also provide common sort  properties for TPhSensor and TPhSensorSet classes, that derive from TPhSensorNode.
• There will be several sorting types defined (by name, by label, by x,y,z), other sorting types may be available in subclasses.

TPhSensorSet

• TPhSensorSet class inherits from TPhSensorNode
• It contains a pointer to TPhGeometry object
• During construction it adds itself to the parent and TPhGeometry lists of sensor sets
• Different sensor set types will be recognized by:
• sensor set name,
• class name (classes inheriting from TPhSensorSet) and by
• user type (coded in string)
• TPhSensorSet has a list of sub sensor sets and a list of all sensors in these subsets.
• TPhSensors will be geometrically manipulated by the TPhSensorSet object.
• When moving TPhSensorSet, it will automatically make sure that it is on the path of transformation to Mother reference frame for all sensors/sensor sets it containes in its lists.
• Getting a list of sensors/sensor sets will involve:
• creating/updating sensor set (if it doesn't exist yet)
• adding individual sensors (found by name or by location)
• adding sensor sets (by name, by user type or by class type)
• sorting  - NOT DONE, (waiting for better sorting facilities in ROOT)
• reqesting a pointer to a list of sensors, or sensor sets, the container class will provide iterator.

Classes inheriting from TPhSensorSet

• TPhSubDetector
• Inheriting from TPhSubDetector - current list
• TPhMulRingsDet
• TPhOctagonDet
• TPhVertexDet
• TPhSpecDet
• TPhTOFDet
• TPhTrigger
• TPhZDCDet
• TPhSensorLayer (changed name from TPhLayer)
• TPhSensorPlane
• TPhSensorModule

TPhSensor

• Inherit from TPhSensorNode
• Introduce constructors with parameters to build a real tree of TPhSensor nodes in T(Ph)Geometry
• During construction it finds closest parent sensor set and TPhGeometry object and adds itselft to their lists of sensors
• Only layer number left in the base TPhSensor class. The Plane and Module numbers are placed in TPhSpectSensor class.