Differences

This shows you the differences between two versions of the page.

--- visual3d:documentation:pipeline:model_based_data_commands:helical_angle [2024/06/19 12:51] – sgranger
+++ visual3d:documentation:pipeline:model_based_data_commands:helical_angle [2024/07/17 15:46] (current) – created sgranger
@@ Line 1: / Line 1: @@
-{{a [[visual3d:documentation:pipeline:model_based_data_commands:joint_angle|joint angle]] is the transformation between two coordinate system that is described by a rotation matrix.
+====== Helical Angle ======
-this rotation matrix is rarely used to report the joint angle. from the rotation matrix several different representations are possible, such as cardan/euler angle, helical angle, quaternion. all representations of the transformation are equivalent but the interpretation of the joint angle relative to the anatomy varies with the description.
+A [[Visual3D:Documentation:Pipeline:Model_Based_Data_Commands:Joint_Angle|Joint Angle]] is the transformation between two coordinate system that is described by a rotation matrix.
-helicalangledlg.jpg
+This rotation matrix is rarely used to report the joint angle. From the rotation matrix several different representations are possible, such as Cardan/Euler angle, Helical angle, Quaternion. All representations of the transformation are equivalent but the interpretation of the joint angle relative to the anatomy varies with the description.
-the helical angle calculation is output as vector rather than a unit vector and an angle of rotation.
+{{:HelicalAngleDlg.jpg}}
-visual3d is simply multiplying the angle of the rotation by the three components of the unit vector.
+The helical angle calculation is output as vector rather than a unit vector and an angle of rotation.
-helical angles are especially appropriate when the rotation is very small. in addition, they eliminate the problem of gimbal lock. however, the representation of joint motion provided by helical angles does not always correspond with an anatomical representation that is clinically meaningful. in addition, helical angles are very sensitive to noisy coordinate data. therefore, the coordinate data must be substantially smoothed before the helical angles are calculated.
+Visual3d is simply multiplying the angle of the rotation by the three components of the unit vector.
+Helical angles are especially appropriate when the rotation is very small. In addition, they eliminate the problem of gimbal lock. However, the representation of joint motion provided by helical angles does not always correspond with an anatomical representation that is clinically meaningful. In addition, helical angles are very sensitive to noisy coordinate data. Therefore, the coordinate data must be substantially smoothed before the helical angles are calculated.
 \\
-====== joint angle lecture ======
+===== Joint Angle Lecture =====
-joint angle lecture prepared by tom kepple when he was teaching at the university of delaware. [[[https://www.has-motion.com/download/examples/jointangleslecture.pdf|joint angle lecture]]]
+Joint angle lecture prepared by Tom Kepple when he was teaching at the University of Delaware. [[[https://www.has-motion.com/download/examples/JointAnglesLecture.pdf|Joint Angle Lecture]]]
-====== helical axis ======
+===== Helical Axis =====
-is possible to calculate a helical axis (vector and angle) in visual 3d?
+Is possible to calculate a helical axis (vector and angle) in Visual 3D?
-the answer yes by going the opposite way. to do this you would have to first compute the magnitude of the output of the “compute model based helical_angle” and then divide each of the components of this vector by the magnitude.
+The answer yes by going the opposite way. To do this you would have to first compute the magnitude of the output of the “Compute Model Based Helical_Angle” and then divide each of the components of this vector by the magnitude.
-to actually do this inside visual3d you would:
+To actually do this inside Visual3d you would:
 \\
-step 1) use “compute model based helical_angle” to get the helical angle as a vector.
+Step 1) Use “Compute Model Based Helical_Angle” to get the helical angle as a vector.
-step 2) use the pipleline command “signal magnitude” (which is under signal math in the pipeline) to get the magnitude of the “compute model based helical_angle”. this would give you the angle you are looking for.
+Step 2) Use the Pipleline command “Signal Magnitude” (which is under Signal Math in the Pipeline) to get the magnitude of the “Compute Model Based Helical_Angle”. This would give you the angle you are looking for.
-step 3) use the pipeline command evaluate_expression to divide the result of “compute model based helical_angle” by the result of the signal magnitude. this will give you the unit vector you are looking for.
+Step 3) Use the pipeline command Evaluate_Expression to divide the result of “Compute Model Based Helical_Angle” by the result of the Signal Magnitude. This will give you the unit vector you are looking for.
-for example:\\
+For example:\\
-evaluate_expression\\
+Evaluate_Expression\\
-/expression=link_model_based::original::ball_helical/derived::processed::ball_helical_magni\\
+/EXPRESSION=LINK_MODEL_BASED::ORIGINAL::BALL_HELICAL/DERIVED::PROCESSED::BALL_HELICAL_MAGNI\\
-! /signal_types=\\
+! /SIGNAL_TYPES=\\
-! /signal_folder=original\\
+! /SIGNAL_FOLDER=ORIGINAL\\
-! /signal_names=\\
+! /SIGNAL_NAMES=\\
-! /result_types=derived\\
+! /RESULT_TYPES=DERIVED\\
-! /result_folders=processed\\
+! /RESULT_FOLDERS=PROCESSED\\
-/result_name=ball_helical_vector\\
+/RESULT_NAME=BALL_HELICAL_VECTOR\\
-! /apply_as_suffix_to_signal_name=false\\
+! /APPLY_AS_SUFFIX_TO_SIGNAL_NAME=FALSE\\
@@ Line 48: / Line 50: @@
-}}