Changes between Version 10 and Version 11 of RaveKinematics

Timestamp:

Jan 29, 2008, 12:32:09 PM (17 years ago)

Author:

fmos

Comment:

--

RaveKinematics

@@ -111 +111 @@
 == Converting the input ==
 
-The kinematic fit makes heavy use of the !KinematicParticle class. It is used as an input as well as an output data class. Strictly spoken, the input data accepted by the kinematic fitting algorithms must be converted to !TransientTrackKinematicParticle classes. This class can be created from !Track objects by providing an additional mass hypothesis or from !Vector7D and !Covariance7D objects by providing additional charge and fit information. The two basic constructors are 
+The kinematic fit makes heavy use of the !KinematicParticle class. It is used as an input as well as an output data class. Strictly spoken, the input data accepted by the kinematic fitting algorithms must be converted to !TransientTrackKinematicParticle classes. This class can be created from Track objects by providing an additional mass hypothesis or from Vector7D and Covariance7D objects by providing additional charge and fit information. The two basic constructors are 
 
 {{{
@@ -157 +157 @@
  * Momentum
  * Pointing
- * Simple pointing
- * Smart pointing
- * Two-track Mass
+ * Simple-Pointing
+ * Smart-Pointing
+ * Two-Track-Mass
  * Vertex
  * (Multiple)
@@ -165 +165 @@
 Constraints are represented by instances of the !KinematicConstraint class. They cannot be created freely, but only by using the !KinematicConstraintBuilder. This builder offers a creation method for each type of constraint. The signatures of those methods can be found in the Doxygen documentation shipping with Rave.
 
-As is visible from these signatures, the !MultipleKinematicConstraint has a special role copared to the other constraints.
+As is visible from these signatures, the !MultipleKinematicConstraint has a special role compared to the other constraints. It allows to apply multiple constraints at the same time. This is done by creating a !MultipleKinematicConstraint and binding other constraints to it by calling its addConstraint method with the newly created constraint as an argument.
+
+== Fitting ==
+
+The kinematic fitting with Rave is done by the !KinematicTreeFactory class. It provides two types of fitting methods which take different types of parameters.
+
+ * useVertexFitter
+ * useParticleFitter
+
+The vertex fitter takes the input particles to be fitted to a vertex together with an optional constraint and returns a !KinematicTree (which will be described in the next chapter). On the other hand the particle fitter takes a !KinematicTree together with an additional constraint. The only way to get the input !KinematicTree for use with the particle fitter is by invocation of the vertex fitter.
+
+Apart from that obvious difference, also the set of constraints accepted by each fitter differs. The vertex fitter only accepts either the  Two-Track-Mass- or the Vertex constraint. The particle fitter accepts one of the remaining constraints (Back-to-Back, Four-Momentum, Mass, Momentum, Pointing, Simple-Pointing, Smart-Pointing or Multiple).
+
+== Interpreting the results ==
+
+The fitter always returns a !KinematicTree, which will be invalid if the fit wasn't successfull. The validity can be tested by calling the isValid method.