CLHEP VERSION Reference Documentation
   
CLHEP Home Page     CLHEP Documentation     CLHEP Bug Reports

Functions | Variables
merge-details.doc File Reference

Functions

ZOOM classes Symbol which is defined in the SpaceVector h backward compatibility header This has the consequence that ThreeVector h is considerably since the plethora of constructors is greatly reduced Spherical coordinate the user can still use the set () methods in spherical coordinates. Except that again the keywords DERGREES RADIANS ETA are not available. Instead
 
ZOOM classes Symbol which is defined in the SpaceVector h backward compatibility header This has the consequence that ThreeVector h is considerably since the plethora of constructors is greatly reduced Spherical coordinate the user can still use the we provide a few new for setRThetaPhi (double r, double theta, double phi)
 
there is no operator* (HepRotation). In reallity
 

Variables

ZOOM classes Symbol pollution
 
ZOOM classes Symbol which is defined in the SpaceVector h backward compatibility header This has the consequence that ThreeVector h is considerably simplified
 
ZOOM classes Symbol which is defined in the SpaceVector h backward compatibility header This has the consequence that ThreeVector h is considerably since the plethora of constructors is greatly reduced Spherical coordinate setting
 
ZOOM classes Symbol which is defined in the SpaceVector h backward compatibility header This has the consequence that ThreeVector h is considerably since the plethora of constructors is greatly reduced Spherical coordinate the user can still use the we provide a few new methods
 
ZOOM classes Symbol which is defined in the SpaceVector h backward compatibility header This has the consequence that ThreeVector h is considerably since the plethora of constructors is greatly reduced Spherical coordinate the user can still use the we provide a few new for example
 
In these
 
In alll angles are always treated as measured in RADIANS Spherical coordinate setting mof V in LorentzVector
 
In alll angles are always treated as measured in RADIANS Spherical coordinate setting mof V in however
 
there is no the time needed for times is not significantly less
 
there is no the time needed for times is not significantly certainly not enough to warrant the additional complication So we simple provide the transform method taking a rotation interface
 
there is no the time needed for times is not significantly certainly not enough to warrant the additional complication So we simple provide the transform method taking a rotation which will break no code But for pure rotations around coordinate axes and boosts along axes
 
there is no the time needed for times is not significantly certainly not enough to warrant the additional complication So we simple provide the transform method taking a rotation which will break no code But for pure rotations around coordinate axes and boosts along we do provide such methods as rotateZ and boostZ Here the efficiency difference is marked Besides
 
there is no the time needed for times is not significantly certainly not enough to warrant the additional complication So we simple provide the transform method taking a rotation which will break no code But for pure rotations around coordinate axes and boosts along we do provide such methods as rotateZ and boostZ Here the efficiency difference is marked CLHEP has these explicitly We also must keep the technically superfluous rotate(delta, axis) and boost(3 doubles or 3-vector) methods. Split of .cc files I decided it might not be worth it TODO
 
there is no the time needed for times is not significantly certainly not enough to warrant the additional complication So we simple provide the transform method taking a rotation which will break no code But for pure rotations around coordinate axes and boosts along we do provide such methods as rotateZ and boostZ Here the efficiency difference is marked CLHEP has these explicitly We also must keep the technically superfluous rotate(delta, axis) and boost(3 doubles or 3-vector) methods. Split of .cc files I decided it might not be worth it Y
 
there is no the time needed for times is not significantly certainly not enough to warrant the additional complication So we simple provide the transform method taking a rotation which will break no code But for pure rotations around coordinate axes and boosts along we do provide such methods as rotateZ and boostZ Here the efficiency difference is marked CLHEP has these explicitly We also must keep the technically superfluous rotate(delta, axis) and boost(3 doubles or 3-vector) methods. Split of .cc files I decided it might not be worth it Z
 
 boostX
 
Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation Classes
 
Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation RotationY
 
Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation RotationZ
 
Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation LorentzBoost
 
Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation LorentzBoostX
 
Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation LorentzBoostY
 
Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation LorentzBoostZ These are useful and will become part of CLHEP THe boost classes may be in their own header file Inheritance structure
 
Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation LorentzBoostZ These are useful and will become part of CLHEP THe boost classes may be in their own header file Inheritance which provide those methods available for GETTING INFORMATION ABOUT generic Rotations and LorentzTransformations We should keep these The proper inheritance is that RI derives from LTI
 
Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation LorentzBoostZ These are useful and will become part of CLHEP THe boost classes may be in their own header file Inheritance which provide those methods available for GETTING INFORMATION ABOUT generic Rotations and LorentzTransformations We should keep these The proper inheritance is that RI derives from because anything you wish to ask about a LT you could equally well ask about a R From one derives LT
 
Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation LorentzBoostZ These are useful and will become part of CLHEP THe boost classes may be in their own header file Inheritance which provide those methods available for GETTING INFORMATION ABOUT generic Rotations and LorentzTransformations We should keep these The proper inheritance is that RI derives from because anything you wish to ask about a LT you could equally well ask about a R From one derives and each of the boosts From RI
 
Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation LorentzBoostZ These are useful and will become part of CLHEP THe boost classes may be in their own header file Inheritance which provide those methods available for GETTING INFORMATION ABOUT generic Rotations and LorentzTransformations We should keep these The proper inheritance is that RI derives from because anything you wish to ask about a LT you could equally well ask about a R From one derives and each of the boosts From one derives Rotation and its special cases We then can derive RotationX from Rotation
 

Function Documentation

◆ operator*()

there is no operator* ( HepRotation  )

◆ set()

ZOOM classes Symbol which is defined in the SpaceVector h backward compatibility header This has the consequence that ThreeVector h is considerably since the plethora of constructors is greatly reduced Spherical coordinate the user can still use the set ( )

◆ setRThetaPhi()

ZOOM classes Symbol which is defined in the SpaceVector h backward compatibility header This has the consequence that ThreeVector h is considerably since the plethora of constructors is greatly reduced Spherical coordinate the user can still use the we provide a few new for setRThetaPhi ( double  r,
double  theta,
double  phi 
)

Variable Documentation

◆ axes

there is no the time needed for times is not significantly certainly not enough to warrant the additional complication So we simple provide the transform method taking a rotation which will break no code But for pure rotations around coordinate axes and boosts along axes

Definition at line 56 of file merge-details.doc.

◆ Besides

there is no the time needed for times is not significantly certainly not enough to warrant the additional complication So we simple provide the transform method taking a rotation which will break no code But for pure rotations around coordinate axes and boosts along we do provide such methods as rotateZ and boostZ Here the efficiency difference is marked Besides

Definition at line 58 of file merge-details.doc.

◆ boostX

boostX

Definition at line 99 of file merge-details.doc.

◆ Classes

Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation Classes

Definition at line 110 of file merge-details.doc.

◆ example

ZOOM classes Symbol which is defined in the SpaceVector h backward compatibility header This has the consequence that ThreeVector h is considerably since the plethora of constructors is greatly reduced Spherical coordinate the user can still use the we provide a few new for example

Definition at line 16 of file merge-details.doc.

◆ however

In alll angles are always treated as measured in RADIANS Spherical coordinate setting mof V in however

Definition at line 22 of file merge-details.doc.

◆ interface

there is no the time needed for times is not significantly certainly not enough to warrant the additional complication So we simple provide the transform method taking a rotation interface

Definition at line 55 of file merge-details.doc.

◆ less

there is no the time needed for times is not significantly less

Definition at line 53 of file merge-details.doc.

◆ LorentzBoost

Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation LorentzBoost

Definition at line 110 of file merge-details.doc.

◆ LorentzBoostX

Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation LorentzBoostX

Definition at line 111 of file merge-details.doc.

◆ LorentzBoostY

Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation LorentzBoostY

Definition at line 111 of file merge-details.doc.

◆ LorentzVector

In alll angles are always treated as measured in RADIANS Spherical coordinate setting mof V in LorentzVector

Definition at line 22 of file merge-details.doc.

◆ LT

Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation LorentzBoostZ These are useful and will become part of CLHEP THe boost classes may be in their own header file Inheritance which provide those methods available for GETTING INFORMATION ABOUT generic Rotations and LorentzTransformations We should keep these The proper inheritance is that RI derives from because anything you wish to ask about a LT you could equally well ask about a R From one derives LT

Definition at line 121 of file merge-details.doc.

◆ LTI

Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation LorentzBoostZ These are useful and will become part of CLHEP THe boost classes may be in their own header file Inheritance which provide those methods available for GETTING INFORMATION ABOUT generic Rotations and LorentzTransformations We should keep these The proper inheritance is that RI derives from because anything you wish to ask about a LT you could equally well ask about a R From LTI

Definition at line 119 of file merge-details.doc.

◆ methods

Signatures of Hep3Vector::rotate For equivalent ZOOM axis There is no harm in leaving this axis CLHEP has implemented a first forming an identity then rotating that by axis and I leave the CLHEP code alone people are of course free to use the ZOOM originated method with signature which I believe will be faster Return types for rotateZ CLHEP and PhysicsVectors each have these three and they are identical except that the ZOOM version returns a reference to while in CLHEP they return void Having methods that alter an object return a reference to that object is convenient for certain chained and costs nothing I don t wish to potentially break ZOOM user code for no good so I have made these CLHEP method conform to this convention There are a couple of other CLHEP methods

Definition at line 16 of file merge-details.doc.

◆ pollution

ZOOM classes Symbol pollution

Definition at line 7 of file merge-details.doc.

◆ RI

Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation LorentzBoostZ These are useful and will become part of CLHEP THe boost classes may be in their own header file Inheritance which provide those methods available for GETTING INFORMATION ABOUT generic Rotations and LorentzTransformations We should keep these The proper inheritance is that RI derives from because anything you wish to ask about a LT you could equally well ask about a R From one derives and each of the boosts From RI

Definition at line 121 of file merge-details.doc.

◆ Rotation

Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation LorentzBoostZ These are useful and will become part of CLHEP THe boost classes may be in their own header file Inheritance which provide those methods available for GETTING INFORMATION ABOUT generic Rotations and LorentzTransformations We should keep these The proper inheritance is that RI derives from because anything you wish to ask about a LT you could equally well ask about a R From one derives and each of the boosts From one derives Rotation and its special cases We then can derive RotationX from Rotation

Definition at line 122 of file merge-details.doc.

◆ RotationY

Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation RotationY

Definition at line 110 of file merge-details.doc.

◆ RotationZ

Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation RotationZ

Definition at line 110 of file merge-details.doc.

◆ setting

ZOOM classes Symbol which is defined in the SpaceVector h backward compatibility header This has the consequence that ThreeVector h is considerably since the plethora of constructors is greatly reduced Spherical coordinate setting

Definition at line 14 of file merge-details.doc.

◆ simplified

ZOOM classes Symbol which is defined in the SpaceVector h backward compatibility header This has the consequence that ThreeVector h is considerably simplified

Definition at line 9 of file merge-details.doc.

◆ structure

Z these are I think new Just check against the equivalent form by instantiating a general Lor Rot based on a ROtationX and so forth Rotation LorentzBoostZ These are useful and will become part of CLHEP THe boost classes may be in their own header file Inheritance structure

Definition at line 116 of file merge-details.doc.

◆ these

In these

Definition at line 18 of file merge-details.doc.

◆ TODO

there is no the time needed for times is not significantly certainly not enough to warrant the additional complication So we simple provide the transform method taking a rotation which will break no code But for pure rotations around coordinate axes and boosts along we do provide such methods as rotateZ and boostZ Here the efficiency difference is marked CLHEP has these explicitly We also must keep the technically superfluous rotate (delta,axis) and boost(3 doubles or 3-vector) methods. Split of .cc files I decided it might not be worth it TODO

Definition at line 59 of file merge-details.doc.

◆ Y

Y

◆ Z

there is no the time needed for times is not significantly certainly not enough to warrant the additional complication So we simple provide the transform method taking a rotation which will break no code But for pure rotations around coordinate axes and boosts along we do provide such methods as rotateZ and boostZ Here the efficiency difference is marked CLHEP has these explicitly We also must keep the technically superfluous rotate (delta,axis) and boost(3 doubles or 3-vector) methods. Split of .cc files I decided it might not be worth it Z

Definition at line 99 of file merge-details.doc.