Orientation Tracking Setup
Posted: Thu Aug 24, 2023 12:25 pm
Hi all,
I recently started working with some IMU data that I'm trying to use with Moco, the good news being that there's a ton of data available but it's a bit like drinking out of a fire hose. The Xsens system we're using gives a ton of information and I've been able to adapt some conversion code from the native MVNX files to kinematics .mot files. However, (and this seems silly to say) I can only pull joint angle data from the MVN model joints which leaves gaps in various OpenSim model DOFs that don't have data to track (i.e., pelvis_tilt/list/rotation); resulting in solutions that aren't super great.
I have a question regarding the MocoOrientationTrackingGoal. I've used a variant of this goal in the past to assign a states trajectory for reference for the torso orientation. The description of this goal says that it can also take a trajectory in quaternion format, representing the orientation reference data which is provided in an array for all of the MVN model segments in each captured frame. I'm wondering if it's as straightforward as building a TimeSeriesTable of the quaternion data and adding a Pelvis_Orientation tracking goal to my problem? Or am I missing something else?
Thanks!
Nick
I recently started working with some IMU data that I'm trying to use with Moco, the good news being that there's a ton of data available but it's a bit like drinking out of a fire hose. The Xsens system we're using gives a ton of information and I've been able to adapt some conversion code from the native MVNX files to kinematics .mot files. However, (and this seems silly to say) I can only pull joint angle data from the MVN model joints which leaves gaps in various OpenSim model DOFs that don't have data to track (i.e., pelvis_tilt/list/rotation); resulting in solutions that aren't super great.
I have a question regarding the MocoOrientationTrackingGoal. I've used a variant of this goal in the past to assign a states trajectory for reference for the torso orientation. The description of this goal says that it can also take a trajectory in quaternion format, representing the orientation reference data which is provided in an array for all of the MVN model segments in each captured frame. I'm wondering if it's as straightforward as building a TimeSeriesTable of the quaternion data and adding a Pelvis_Orientation tracking goal to my problem? Or am I missing something else?
Thanks!
Nick