Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- modellingcomponents:elements:kinematics [2021/04/30 17:31] – [Generated trajectories] oliver
+++ modellingcomponents:elements:kinematics [2022/07/18 23:18] (aktuell) – [Created parameters] oliver
@@ Zeile 130: / Zeile 130: @@
 ======GlobalCoordinateSystem======
 This element is used to define a cartesian coordinate system based on a given coordinate system in local coordinates of a given reference coordinate system.
-Not yet implemented!
 ==== Attributes ====
@@ Zeile 144: / Zeile 142: @@
 ^ <name> | Matrix3d | Representation of the three orthogonal orientation axes of the determined local coordinate system (columns of the matrix) |
 ^ <name>Position | Vector3d | Origin of the coordinate system |
-======ForwardKinematicDH======
-This element defines a cartesian coordinate system based on a parent coordinate system and Denavit-Hartenberg parameters.
-==== Attributes ====
-^ Attribute ^ Description ^ Required ^
-^ name | Name of the element | Yes |
-^ referenceCoordinateSystem | Defines the the reference coordinate system by its name. | Yes |
-^ Alpha| Denavit-Hartenberg parameter | Yes |
-^ Theta| Denavit-Hartenberg parameter | Yes |
-^ D | Denavit-Hartenberg parameter | Yes |
-^ R | Denavit-Hartenberg parameter | Yes |
-====Generated trajectories ====
-^ Name ^ Type ^ Description ^
-^ <name> | Matrix3d | Representation of the three orthogonal orientation axes of the determined local coordinate system (columns of the matrix) |
-^ <name>Position | Vector3d | Origin of the coordinate system |
-**Example**
-<code xml>
-<ForwardKinematicDH name="BaseUR"
-                    referenceCoordinateSystem="GLOBE"
-                    Alpha="0.5"
-                    Theta="Angle0"
-                    D="0.145"
-                    R="0.234"/>
-</code>
-An alternative to use this element is to use the corresponding function:
-<code xml>
-<CoordinateSystem name="BaseUR"
-                  Pose="dhm(Angle0, DH_alpha0, DH_d0, DH_r0)"/>
-</code>
-======ForwardKinematicEulerCardan======
-==== Attributes ====
-^ Attribute ^ Description ^ Required ^
-^ name | Name of the element | Yes |
-^ referenceCoordinateSystem | Defines the the reference coordinate system by its name. | Yes |
-^ EulerCardanAngles| Formula that defines a 3-tuple e.g. vec(1.0,1.0,1.0) with a sequence of three angles | Yes |
-^ rotationOrder | rotation order | No |
-^ Position | Origin of result coordinate system | Yes |
@@ Zeile 283: / Zeile 241: @@
 ^ coordinateSystem | | Name of the coordinate system element which is used in two cases: 1. If the point is defined in local coordinates with the attribut "localPoint" it defines the corresponding coordinate system. 2. If calibration is used, than for static trial which is defined by switches given with the attributes calibrateIncludes/calibrateExcludes the point is transformed in local coordinates of the coordinate system which is given with this element. For all other trials the local coordinates are back transformed to the global coordinates using the current value of the coordinate system defined by this attribute. | No ^
-**Note:** The Parameter <name>Local is created, if calibration is used. It caontains the mean vector of the calibration trial in the coordinates of the given coordinate system.
+**Note:** The Parameter <name>Local is created, if calibration is used. It contains the mean vector of the calibration trial in the coordinates of the given coordinate system.
 **Examples**
@@ Zeile 289: / Zeile 247: @@
 <code xml>
     <Vector name="A"
-     coordinateSystem="Thorax"
+            coordinateSystem="Thorax"
-     calibrateIncludes="static">B+C</Vector>
+            calibrateIncludes="static">B+C</Vector>
 </code>
@@ Zeile 414: / Zeile 372: @@
 </code>
-In the case the two timeseries (TCPUR5e and TCPP) are not perfectly sychronized, especially a delay is between them the following expamples implements the usage of phases seperately defined for each timeeries. The phases are used only if in a trial the cound of phases for each of the two timeseries contains the same count.
+In the case the two timeseries (TCPUR5e and TCPP) are not perfectly sychronized, especially a delay is between them the following expamples implements the usage of phases seperately defined for each timeeries. The phases are used only, if in a trial the count of phases for each of the two timeseries is equal.
 <code xml>
@@ Zeile 442: / Zeile 400: @@
 ^ <name>Orientation | Matrix3d | Orientation of the coordinatesystem the points of pointset 2 are given in. The orientation is given in coordinates the points of the first pointset are given in. ^
 ^ <name>Origin | Vector3d | Origin of the coordinatesystem, the points of pointset 2 are given in. The origin is given in coordinates the points of the first pointset are given in. ^
+These parameters are created for non calibration files to make them availble in furher formula, e.g.:
+<code xml>
+<CoordinateSystem name="Mediapipe2ViconFit"
+                  Position="Mediapipe2ViconOrigin*1.0"
+                  Rotation="Mediapipe2ViconOrientation*1.0"
+                  excludes="static_calibrate,locator,dynamic_calibrate,calibrate_mediapipe"/>
+</code>