simtk.org

Hi interested users. This is a new contribution to the Opensim platform. I hope it helps you in some way. Please let me know via this forum if you have any problems with the instructions or want to implement something special. The solutions here are certainly not 1 size fits all, so it may take a little bit of work to get things up and running. Good luck!

Hi Glen,

First, allow me to say how helpful you guys have been and useful these forums are in solving the vast majority of issues I face with the MATLAB-OpenSim interface.

There has been one bug that has been popping up very recently for me. Whenever I started to use the Forward Tool, Force Reporter Class, and Prescribed Forces together in MATLAB, MATLAB would often crash. At first I thought it was a problem with MATLAB. I have been in correspondence with MATLAB tech and they believe it is an issue with the OpenSim plugins for MATLAB. Whenever I am only using the Forward Tool, I do not have any issues. But when I start using the Force Reporter and Prescribed Forces - MATLAB crashes.

Currently it isn't a real issue for me, because as long as I ignore the MATLAB warning that it needs to close my code continues to run. I just send the information to MATLAB and let it close once my script is finished running.

-Sam Masters

Dear Glen,
First of all, many thanks to you and to all the other contributors for this great package Matlab_Opensim_Tools_v2. It is really a lifesaver in order to import C3D data into Matlab and then into OpenSim.

I spotted a little bug into the function "coord2mot.m" which is used to export a struct containing coordinates into a .mot file.

The bug causes all the coordinates to be wrongly interpreted by OpenSim 3.2, even if the values inside the exported .mot file are perfectly correct. Basically, you can see the skeleton collapsing on itself and the limbs moving in a nonsense fashion.

It took me a while to understand that the reason behind this problem is at line 64:
fprintf(fid,'indegrees=%s\n',indegrees);

which should actually be:
fprintf(fid,'inDegrees=%s\n',indegrees);

I think that this little difference in case causes the values to be interpreted as radians by OpenSim, instead of degrees.

Hope it helps!

Hi !
I have a question, I thought that Opensim was written in c++, so how I can analyze the code in matlab ?

Thanks for your time