External Forces Setup and .mot file not being read properly

Provide easy-to-use, extensible software for modeling, simulating, controlling, and analyzing the neuromusculoskeletal system.
POST REPLY
User avatar
Alexandra Dunning
Posts: 6
Joined: Wed Aug 31, 2022 7:29 pm

External Forces Setup and .mot file not being read properly

Post by Alexandra Dunning » Tue Dec 13, 2022 4:42 pm

I am using OpenSim 4.4 and am having issues with my external forces. I have written a .mot file in MATLAB for a person cycling (looking at only grf for feet at the moment) based off torque data and moment arms etc. This has given me a ground_force_vy and a l_ground_force_vy. All other forces an torques have been written as 0 for the entire time duration. I have set force to be applied to the body (I want the ground reaction force to follow each foot at a perpendicular orientation throughout the cycling motion). When I upload this into my external force setup for inverse dynamics, applying the force to the calcn_r and calcn_l, I get an associated motion from my .mot file which is floating beneath the person cycling, in the middle of the two legs. It seems to move up and down slightly (in the y-axis) and there seems to only be the one force (or they overlap completely despite having very different forces). Does anybody know how to resolve this or where the major issues may lie. The magnitude seems to be reasonable.
I have attached the .mot file and external forces setup file.
Attachments
external_loads_setup.xml
(2.49 KiB) Downloaded 13 times
10scaled_markers_pilot_scaled_trial_1_grf.mot
(146.41 KiB) Downloaded 14 times

Tags:

User avatar
Zakia Hussain
Posts: 38
Joined: Sun Dec 26, 2021 10:44 pm

Re: External Forces Setup and .mot file not being read properly

Post by Zakia Hussain » Fri Dec 23, 2022 4:50 am

I think what u mean is your grf is not consistent with your IK.mot results that is the grf is not applied at the correct points of application. So i guess u need to check your COP calculations. I had similar issues and the COP calculation was wrong.

POST REPLY