KineticsToolkit extracts angle value error from c3d data #146
-
After using vicon to collect kinematics data, I found that all kinds of angle data in the c3d data extracted with kineticsToolkit were incorrect. But the EMG and point data are correct.
I don't know what the problem is. Please tell me how to convert to the correct angle value. If you have time, please upgrade the kineticsToolkit to calculate the correct angle value. I'd be happy to help if I could. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
@gaozelle Thank you for noticing and testing with the other softwares. Would you mind sending me this c3d, either by email (chenier dot felix at uqam dot ca) or right here in this thread? It will greatly help me. Tx |
Beta Was this translation helpful? Give feedback.
-
Hi @gaozelle Thanks for the question and c3d file. This may indeed be described as a bug in Kinetics Toolkit and I will open an issue related to this. The workaround is simple though (see below). The problem is that While I figure out a clean way to address this issue, you can either multiply the angles by 1000, or load the file "as is" without any conversion using |
Beta Was this translation helpful? Give feedback.
Hi @gaozelle
Thanks for the question and c3d file. This may indeed be described as a bug in Kinetics Toolkit and I will open an issue related to this. The workaround is simple though (see below).
The problem is that
ktk.read_c3d
doesn't distinguish points between proper points (markers) and computed "points" such as angles and forces. Since the point unit in your c3d is millimeters and the default in KTK is to convert to meters, then it divides every point coordinate by 1000, including the computed angles, forces, moments, etc.While I figure out a clean way to address this issue, you can either multiply the angles by 1000, or load the file "as is" without any conversion using
ktk.read_c3…