Sorry about that, here is the model that goes with it.

Hey NMSM Team, This seems to be the last big error we have come across with about 5 of our 30 subjects. I think it has to do with how the moment arms are being parsed from the muscle analysis data. It seems that in between the moment arm files there is a mismatch in the number of columns that are ge...

Hey Rob, That did the trick across the participants/trials that we were having this problem. In some cases, it happens in the middle of the trial as well...but your fix (or changing training trials) works for those as well. The root of the problem was finger speed during our tasks. Some participants...

Hey NMSM Team, We have successfully been using NMSM (v1.3) and have come across this error with about a third of our 30 participants (we get the same issue in earlier versions as well). Something is causing there to be two Inf values in the initial values set given to the optimizer. We don't think i...

Hi Joshua, I haven't come across this issue yet. I usually do single arm analysis and just mirror the motion capture data of left handed subjects, or run two sets of single arm tasks when do a dual arm task (probably the only benefit of the arms acting 'fully' independent of each other. The first th...

Hi Nico,

I had been using the direct output from my IK simulations which where in degrees. Changing them to radians did the trick. Thanks for all the help.

-Max

Hi Nicos, I got a chance to try your recommendation today...and I think my issue may be with either pulling the correct frame for the rigid body or something with how the frame is being adjusted when I realize the position. I get the same result (figure below) whether I apply findStationLocationInGr...

Hi Everyone, I am trying to write a python script in 4.4 that takes a point in a rigid body's reference frame and gives me that point in the ground reference frame throughout a motion to eventually apply a point force. I've done this with Point Kinematics under the Analyze Tool, but OpenSim seems to...

Hi Kristy, The easiest way to see if the muscle path changes are either a visualizer error or path error would be to plot the fiber length and moment arm curves for LAT1. This can be done with the plot tool, and I usually do a set of plots in the default posture and a set of plots with my posture se...

Hey Rob, All around good news that its just a saving issue (awesome that the core MTP processing can handle the difference in passive data formats). In the meantime I do have one questions about getting the rest of my MTP results to save since if appears saving the passive moments is the first step ...