Legacy physics classes.
The references below are for legacy use cases.
Please use the current physics classes as described in the Manual instead of these legacy classes:
Please consider using RooStats instead of TRolke. For non-trivial cases use RooStats instead of TFeldmanCousins. TRobustEstimator and TGenPhaseSpace have no current alternatives.
Classes | |
| class | TFeldmanCousins |
Legacy CodeTFeldmanCousins is a legacy interface: there will be no bug fixes nor new developments. Therefore it is not recommended to use it in new long-term production code. But, depending on the context, using TFeldmanCousins might still be a valid solution. Consider switching to RooStats for non-trivial cases. | |
| class | TGenPhaseSpace |
| Phase Space Generator, based on the GENBOD routine of CERNLIB. More... | |
| class | TLorentzRotation |
Legacy CodeTLorentzRotation is a legacy interface: there will be no bug fixes nor new developments. Therefore it is not recommended to use it in new long-term production code. But, depending on the context, using TLorentzRotation might still be a valid solution. Consider using instead ROOT::Math::LorentzRotation. | |
| class | TLorentzVector |
| class | TQuaternion |
Legacy CodeTQuaternion is a legacy interface: there will be no bug fixes nor new developments. Therefore it is not recommended to use it in new long-term production code. But, depending on the context, using TQuaternion might still be a valid solution. Consider using instead ROOT::Math::Quaternion. | |
| class | TRobustEstimator |
| class | TRolke |
Legacy CodeTRolke is a legacy interface: there will be no bug fixes nor new developments. Therefore it is not recommended to use it in new long-term production code. But, depending on the context, using TRolke might still be a valid solution. Consider switching to RooStats. | |
| class | TRotation |
Legacy CodeTRotation is a legacy interface: there will be no bug fixes nor new developments. Therefore it is not recommended to use it in new long-term production code. But, depending on the context, using TRotation might still be a valid solution. Consider using instead ROOT::Math::Rotation3D. | |
| class | TVector2 |
| class | TVector3 |