The Joint Velocity model-based item is a vector that describes the relative angular velocity of one segment relative to another segment.

Relationship between the Joint Angular Velocity and the derivative of the Cardan Joint Angles

The Joint 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 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 relationship.

Joint Angles are typically represented in a Cardan sequence and Joint Velocities are typically represented as vectors. The consequence is that you cannot compare directly all 3 components of the Joint Angle with, what appear to be homologous, components of the Joint Velocity. For example, given the following definition of the Right Knee Angle:

and the following definition of the Right Knee Angular Velocity:

only the X-components of the two signals are related (i.e., these components relate to the segment's rotation about the same axis).

If a second Joint Velocity item is created as follows:

then the Z-components of this second definition and the original joint angle definition can be compared.

If the Y-component (the 2nd component) of the knee angle is small it is often referred to as ab/adduction, but it is important to note that this rotation is technically isn't about either the y-axis of the thigh or shank segments. If this Joint Angle Y-component isn't small then it is not really possible to compare the Y-components between the Joint Angle and Joint Velocity items.