Index of MATH/GENVECTOR
GenVector Library
GenVector Library
GenVector, is a new package intended to prepresent vectors and their operations and transformations,
such as rotations and Lorentz transformations, in 2, 3 and 4 dimensions. The 2D and 3D space are used to describe the geometry vectors and points, while the 4D spacetime is used for physics vectors representing relativistic particles.
These 2D,3D and 4D vectors are different from vectors of the Linear Algebra package which describe generic Ndimensional vectors. Similar functionality is currently provided by the CLHEP
Vector and
Geometry packages and the ROOT
Physics Vector classes (Tvector2, TVector3 and TLorentzVector). It is also reuses concepts and ideas from the CMS
Common Vector package.
In contrast to CLHEP or the ROOT physics libraries, GenVector provides class templates for modelling the vectors. There is a usercontrolled freedom on how the vector is internally represented. This is expressed by a choice of coordinate system which is supplied as a template prameter when the vector is constructed. Furthermore each coordinate system is itself a template, so that the user can specify the underlying scalar type.
In more detail, the main characteristics of GenVector are:
Optimal runtime performances
We try to minimize any overhead in the runtime performances. We have deliberatly avoided to have any virtual function and even virtual destructors in the classes and have inlined as much as possible all the functions. For this reason, we have chosen to use template classes to implement the GenVector concepts instead of abstract or base classes and virtual functions.
Points and Vector concept
Mathematically vectors and points are two distinct concepts. They have different transformations, like vectors only rotate while points rotate and translate. You can add two vectors but not two points and the difference between two points is a vector. We then distinguish for the 2 and 3 dimensional case, between points and vectors, modeling them with different classes:
 ROOT::Math::DisplacementVector3D and ROOT::Math::DisplacementVector2D template classes describing 3 and 2 component direction and magnitude vectors, not rooted at any particular point;
 ROOT::Math::PositionVector3D template and ROOT::Math::PositionVector3D class modeling the points in 3 and 2 dimensions
.
For the 4D spacetime vectors, we use the same class to model them, ROOT::Math::LorentzVector, since we have recognized a limited needs for modeling the functionality of a 4D point.
Generic Coordinate System
The vector classes are based on a generic type of coordinate system, expressed as a template parameter of the class. Various classes exist to describe the various coordinates systems:
 2D coordinate system classes:
 ROOT::Math::Cartesian2D, based on (x,y);
 ROOT::Math::Polar2D, based on (r, phi);
 3D coordinate system classes:
 ROOT::Math::Cartesian3D, based on (x,y,z);
 ROOT::Math::Polar3D, based on (r, theta, phi);
 ROOT::Math::Cylindrical3D, based on (rho, z, phi)
 ROOT::Math::CylindricalEta3D, based on (rho, eta, phi), where eta is the pseudorapidity;
 4D coordinate system classes:
 ROOT::Math::PxPyPzE4D, based on based on (px,py,pz,E);
 ROOT::Math::PxPyPzM4D, based on based on (px,py,pz,M);
 ROOT::Math::PtEtaPhiE4D, based on based on (pt,eta,phi,E);
 ROOT::Math::PtEtaPhiM4D, based on based on (pt,eta,phi,M);
The angle theta is defined between [0,PI] and phi between [PI,PI]. The angles are expressed in radians.
Users can define the Vectors according to the coordinate type which is most efficient for their use. Transformations between the various coordinate systems are available through copy constructors or the assignment (=) operator.
For maximum flexibility and minimize in some use case memory allocation, the coordinate system classes are templated on the scalar type. To avoid exposing templated parameter to the users, typedefs are defined for all types of vectors based an double's.
See the
2D Vector and Point,
3D Vector,
3D Point,
LorentzVector classes
classes for all the possible types of vector classes which can be constructed by the user with the available coordinate system types.
Coordinate System Tag
The 2D and 3D points and vector classes can be associated to a tag defining the coordinate system. This can be used to distinguish between vectors of different coordinate systems like global or local vectors. The coordinate system tag is a template parameter of the ROOT::Math::DisplacementVector3D (and ROOT::Math::DisplacementVector2D) and ROOT::Math::PositionVector3D (and ROOT::Math::PositionVector2D) classes. A default tag, ROOT::Math::DefaultCoordinateSystemTag, exists for users who don't need this functionality.
Transformations
The transformations are modeled using simple (nontemplate) classes, using double as the scalar type to avoid too large numerical errors. The transformations are grouped in Rotations (in 3 dimensions), Lorentz transformations and Poincarre transformations, which are Translation/Rotation combinations. Each group has several members which may model physically equivalent trasformations but with different internal representations.
Transformation classes can operate on all type of vectors using the operator() or the operator * and the transformations can also be combined via the operator *. In more detail the transformations available are:
3D Rotations classes
 Rotation described by a 3x3 matrix (ROOT::Math::Rotation3D)
 Rotation described by Euler angles, Goldstein representation, (ROOT::Math::EulerAngles)
 Rotation described by 321 Euler angles (ROOT::Math::RotationZYX)
 Rotation described by a direction axis and an angle (ROOT::Math::AxisAngle)
 Rotation described by a quaternion (ROOT::Math::Quaternion)
 Optimized rotation around the x (ROOT::Math::RotationX), y (ROOT::Math::RotationY) and z (ROOT::Math::RotationZ) axis and described by just one angle.
3D Transformation
We describe the transformations defined as a composition between a rotation and a translation using the class ROOT::Math::Transform3D.
It is important to note that transformations act differently on Vectors and Points. The Vectors only rotate, therefore when applying a transfomation (rotation + translation) on a Vector, only the rotation operates while the translation has no effect. The interface for Transformations is similar to the one used in the CLHEP Geometry package
(class Transform3D).
A class, ROOT::Math::Translation3D. describe transformations consisting of only a translation. Translation can be applied only on Points, applying them on Vector objects has no effect. The Translation3D class can be combined with both ROOT::Math::Rotation3D and ROOT::Math::Transform3D using the operator * to obtain a new transformation as an instance of a Transform3D class.
Lorentz Rotation
 Generic Lorentz Rotation described by a 4x4 matrix containing a 3D rotation part and a boost part (class ROOT::Math::LorentzRotation)
 A pure boost in an arbitrary direction and described by a 4x4 symmetric matrix or 10 numbers (class ROOT::Math::Boost)
 Boost along the x (ROOT::Math::BoostX), y (ROOT::Math::BoostY) and z (ROOT::Math::BoostZ) axis.
Other main characteristics of the GenVector classes are:
Minimal Vector classes interface
We have tried to keep the interface to a minimal level:
 We try to avoid methods providing the same functionality but with different names ( like getX() and x() ).
 we minimize the number of setter methods, avoiding methods which can be ambigous and set the Vector classes in an inconsistent state.
We provide only methods which set all the coordinates at the same time or set only the coordinates on which the vector is based, for example SetX() for a cartesian vector. We then enforce the use of transformations as rotations or translations (additions) for modifying the vector contents.
 The majority of the functionality, which is present in the CLHEP package, involving operations on two vectors, is moved in separated helper functions (see ROOT::Math::VectorUtil). This has the advantage that the basic interface will remain more stable with time while additional functions can be added easily.
Naming Convention
As part of ROOT, the GenVector package adheres to the prescribed ROOT naming convention, with some (approved) exceptions, as described here:
 Every class and function is in the ROOT::Math namespace
 Member function names starts with uppercase letter, apart some exceptions (see later CLHEP compatibility)
Compatibility with CLHEP Vector classes

For backward compatibility with CLHEP the Vector classes can be constructed easly from a CLHEP HepVector or HepLorentzVector, by using a template constructor, which requires only that the classes implement the accessors x(), y() and z() (and t() for the 4D).
 we have decided to provide Vector member function with the same naming convention as CLHEP for the most used functions like x(), y() and z().
Connection to Linear Algebra package
In some use cases, like in track reconstruction, it is needed to use the content of the vector and rotation classes in conjunction with linear algebra operations. We prefer to avoid any direct dependency to any Linear algebra package. However, we provide some hooks to convert to and from Linear Algebra classes.

The vector and the transformation classes have methods which allow to get and set their data members (like SetCoordinates and GetCoordinates ) passing either a generic iterator or a pointer to a contigous set of data, like a C array.
This allows a easy connection with linear algebra package which allows creation of matrices using C arrays (like the ROOT TMatrix classes) or iterators ( SMatrix classes )
 Multiplication between Linear Algebra matrix and GenVector Vectors is possible by using the template free
functions ROOT::Math::VectorUtil::Mult. This works for any Linear Algebra matrix which implement the operator(i,j) and with first matrix element at i=j=0.
Example of Usage
Additional Documentation
A more detailed description of all the GenVector classes is available in this
document.
References
 CLHEP Vector package (User guide and reference doc)
 CLHEP Geometry package
 ROOT Physics Vector classes
 CMS Vector package
N.B.: For consulting the reference GenVector documentation it is strongly recommended
to look at these online doc. The class documentation shown from the class links below is not complete, it is missing some template methods.
Last modified: Tue Jun 24 10:39:56 CEST 2008
Further Reading
List of Classes
Class Index
 ROOT::Math::AxisAngle
 ROOT::Math::Boost
 ROOT::Math::BoostX
 ROOT::Math::BoostY
 ROOT::Math::BoostZ
 ROOT::Math::Cartesian2D<Double32_t>
 ROOT::Math::Cartesian2D<double>
 ROOT::Math::Cartesian3D<Double32_t>
 ROOT::Math::Cartesian3D<double>
 ROOT::Math::Cylindrical3D<Double32_t>
 ROOT::Math::Cylindrical3D<double>
 ROOT::Math::CylindricalEta3D<Double32_t>
 ROOT::Math::CylindricalEta3D<double>
 ROOT::Math::DefaultCoordinateSystemTag
 ROOT::Math::DisplacementVector2D<ROOT::Math::Cartesian2D<Double32_t>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::DisplacementVector2D<ROOT::Math::Cartesian2D<double>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::DisplacementVector2D<ROOT::Math::Polar2D<Double32_t>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::DisplacementVector2D<ROOT::Math::Polar2D<double>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::DisplacementVector3D<ROOT::Math::Cartesian3D<Double32_t>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::DisplacementVector3D<ROOT::Math::Cartesian3D<Double32_t>,ROOT::Math::GlobalCoordinateSystemTag>
 ROOT::Math::DisplacementVector3D<ROOT::Math::Cartesian3D<Double32_t>,ROOT::Math::LocalCoordinateSystemTag>
 ROOT::Math::DisplacementVector3D<ROOT::Math::Cartesian3D<double>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::DisplacementVector3D<ROOT::Math::Cylindrical3D<Double32_t>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::DisplacementVector3D<ROOT::Math::Cylindrical3D<double>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::DisplacementVector3D<ROOT::Math::CylindricalEta3D<Double32_t>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::DisplacementVector3D<ROOT::Math::CylindricalEta3D<Double32_t>,ROOT::Math::GlobalCoordinateSystemTag>
 ROOT::Math::DisplacementVector3D<ROOT::Math::CylindricalEta3D<Double32_t>,ROOT::Math::LocalCoordinateSystemTag>
 ROOT::Math::DisplacementVector3D<ROOT::Math::CylindricalEta3D<double>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::DisplacementVector3D<ROOT::Math::Polar3D<Double32_t>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::DisplacementVector3D<ROOT::Math::Polar3D<double>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::EulerAngles
 ROOT::Math::GlobalCoordinateSystemTag
 ROOT::Math::LocalCoordinateSystemTag
 ROOT::Math::LorentzRotation
 ROOT::Math::LorentzVector<ROOT::Math::PtEtaPhiE4D<Double32_t> >
 ROOT::Math::LorentzVector<ROOT::Math::PtEtaPhiE4D<double> >
 ROOT::Math::LorentzVector<ROOT::Math::PtEtaPhiM4D<Double32_t> >
 ROOT::Math::LorentzVector<ROOT::Math::PtEtaPhiM4D<double> >
 ROOT::Math::LorentzVector<ROOT::Math::PxPyPzE4D<Double32_t> >
 ROOT::Math::LorentzVector<ROOT::Math::PxPyPzE4D<double> >
 ROOT::Math::LorentzVector<ROOT::Math::PxPyPzM4D<Double32_t> >
 ROOT::Math::LorentzVector<ROOT::Math::PxPyPzM4D<double> >
 ROOT::Math::Plane3D
 ROOT::Math::Polar2D<Double32_t>
 ROOT::Math::Polar2D<double>
 ROOT::Math::Polar2DPoint
 ROOT::Math::Polar2DPointD
 ROOT::Math::Polar2DVector
 ROOT::Math::Polar2DVectorD
 ROOT::Math::Polar3D<Double32_t>
 ROOT::Math::Polar3D<double>
 ROOT::Math::Polar3DPoint
 ROOT::Math::Polar3DPointD
 ROOT::Math::Polar3DVector
 ROOT::Math::Polar3DVectorD
 ROOT::Math::PositionVector2D<ROOT::Math::Cartesian2D<double>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::PositionVector2D<ROOT::Math::Polar2D<double>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::PositionVector3D<ROOT::Math::Cartesian3D<Double32_t>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::PositionVector3D<ROOT::Math::Cartesian3D<Double32_t>,ROOT::Math::GlobalCoordinateSystemTag>
 ROOT::Math::PositionVector3D<ROOT::Math::Cartesian3D<Double32_t>,ROOT::Math::LocalCoordinateSystemTag>
 ROOT::Math::PositionVector3D<ROOT::Math::Cartesian3D<double>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::PositionVector3D<ROOT::Math::Cylindrical3D<Double32_t>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::PositionVector3D<ROOT::Math::Cylindrical3D<double>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::PositionVector3D<ROOT::Math::CylindricalEta3D<Double32_t>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::PositionVector3D<ROOT::Math::CylindricalEta3D<Double32_t>,ROOT::Math::GlobalCoordinateSystemTag>
 ROOT::Math::PositionVector3D<ROOT::Math::CylindricalEta3D<Double32_t>,ROOT::Math::LocalCoordinateSystemTag>
 ROOT::Math::PositionVector3D<ROOT::Math::CylindricalEta3D<double>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::PositionVector3D<ROOT::Math::Polar3D<Double32_t>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::PositionVector3D<ROOT::Math::Polar3D<double>,ROOT::Math::DefaultCoordinateSystemTag>
 ROOT::Math::PtEtaPhiE4D<Double32_t>
 ROOT::Math::PtEtaPhiE4D<double>
 ROOT::Math::PtEtaPhiEVector
 ROOT::Math::PtEtaPhiM4D<Double32_t>
 ROOT::Math::PtEtaPhiM4D<double>
 ROOT::Math::PtEtaPhiMVector
 ROOT::Math::PxPyPzE4D<Double32_t>
 ROOT::Math::PxPyPzE4D<double>
 ROOT::Math::PxPyPzEVector
 ROOT::Math::PxPyPzM4D<Double32_t>
 ROOT::Math::PxPyPzM4D<double>
 ROOT::Math::PxPyPzMVector
 ROOT::Math::Quaternion
 ROOT::Math::RhoEtaPhiPoint
 ROOT::Math::RhoEtaPhiPointD
 ROOT::Math::RhoEtaPhiVector
 ROOT::Math::RhoEtaPhiVectorD
 ROOT::Math::RhoZPhiPoint
 ROOT::Math::RhoZPhiPointD
 ROOT::Math::RhoZPhiVector
 ROOT::Math::RhoZPhiVectorD
 ROOT::Math::Rotation3D
 ROOT::Math::RotationX
 ROOT::Math::RotationY
 ROOT::Math::RotationZ
 ROOT::Math::RotationZYX
 ROOT::Math::Transform3D
 ROOT::Math::Translation3D
 ROOT::Math::VectorUtil
 ROOT::Math::XYPoint
 ROOT::Math::XYPointD
 ROOT::Math::XYVector
 ROOT::Math::XYVectorD
 ROOT::Math::XYZPoint
 ROOT::Math::XYZPointD
 ROOT::Math::XYZTVector
 ROOT::Math::XYZVector
 ROOT::Math::XYZVectorD