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 ...

Ahhh, I was curious how/why you all were able to get perfect single joint movements. So we are having to collect the passive movement data using motion capture (and subsequently OpenSim Inverse Kinematics) to get our joint angles. For cameras to successfully pick up markers the arm is held straight ...

We seem to have run into an issue tied to saving the results of the Length Initialization step when running it with the Muscle-Tendon Personalization pipeline. It looks like it is tied to how the data is Passive Moment Data is getting reshaped for the eventual sto file. I'm guessing it is tied to ei...

Posting an error associated with muscle naming conventions due to MatLab variable name rules. This error occurs during MTP when the optimized parameters are being saved. From my limited understanding of MatLab it appears that the names of a field within a structure are not allowed to start with a nu...

Hey Spencer, This was a huge help. Changing the '_force' roots to '_moment' worked for running MTP with and without Length Initialization. The wrist_hand_r1 coordinates was an error with our preprocessing code and how it was parsing and reconstructing names, so the file existed but with the wrong na...