User Tools

Site Tools


visual3d:documentation:pipeline:model_based_data_commands:joint_velocity_and_joint_angular_velocity

This is an old revision of the document!


joint coordinate system of grood and suntay]]. the joint angle is interpreted as: rotation about the x-axis of the thigh segment coordinate system rotation about the z-axis of the shank segment coordinate system rotation about an axis perpendicular to the other two axes. to compare the joint angular velocity and joint angle you need to create two joint angular velocity signals. one resolved into the the reference segment coordinate system one resolved in the segment coordinate system. the x-component of the joint angle has an x-axis consistent with the angular velocity resolved into the reference coordinate system the z-component of the joint angle has a z-axis consistent with the angular velocity resolved in the segment coordinate system and only for small values of the y-component can there be a comparison of either angular velocity. ===== joint angles and joint angular velocities ===== it is certainly confusing conceptually to compare the components of joint angles and joint angular velocities, because it isn't intuitively obvious that you are trying to compare "apples and oranges". if you consider the joint angle to be described as segment1 (e.g. segment) relative to segment2 (e.g. reference segment) using an xyz cardan sequence (e.g. the joint coordinate system of grood & suntay). it is only possible to find a comparison between the x-component and the z-component of the angle with an angular velocity, and oddly enough it is actually two different angular velocities. the x-component can be compared with the x-component of a joint angular velocity resolved into segment2, and the z-component of a joint angular velocity resolved into segment1 the second component of the joint angle cannot be compared with anything ==== ik constraints ==== this is even more confusing when you are using inverse kinematic (global optimization) because a joint that is constrained to have degrees of freedom in only the x and z components will have a y-component of the joint angle that is essentially zero (e.g. just noise), but the y-component of the angular velocity is non-zero. you should not expect the second component to have meaning in the context of the ik constraints, you should resist the temptation to interpret the y-component of the angular velocity in the context of the y- component of the joint angle. ===== relationship between the joint angular velocity and the derivative of the cardan joint angles ===== the joint angular velocity can be a bit troublesome to interpret unless you recognize that the signal is not the same as the derivative of the joint angle. it is possible that the some terms of the joint angular velocity are not consistent with the derivative of the joint angle. euler angles are not vectors, so it isn't possible to compute joint angular velocity by taking the first derivative of the joint angles (e.g. euler/cardan angles). with respect to the default visual3d convention of an xyz sequence for the cardan angle, the joint angular velocity can be expressed in euler angles using the following \\ angularvelocityusingeulerangles.gif\\ }}

visual3d/documentation/pipeline/model_based_data_commands/joint_velocity_and_joint_angular_velocity.1718801505.txt.gz · Last modified: 2024/06/19 12:51 by sgranger