Hi Azarang, Apologies if I'm missing some details here, I wasn't sure if I fully followed what your workflow is: If you are tracking kinematic data using MocoTrack or MocoStateTrackingGoal, the GRF produced by contact elements on the feet will not typically resemble experimentally measured GRF very ...

Configuring the latest OpenSim release with Matlab should also include Moco.

Hi Mughees,

Moco is part of recent releases of the OpenSim software. You don't need to download and install Moco separately from OpenSim itself. I would guess that having the 0.x release of Moco installed along with OpenSim might be causing problems.

Ross

I don't think there is an element of randomness to the perturbation IPOPT applies to initial guesses. There is some discussion on this issue elsewhere if you search for things like "IPOPT repeatability", for example: https://groups.google.com/g/opti-toolbox-forum/c/vJPxa_c_CLg I believe this largely...

IPOPT perturbs the initial guess from the initial guess that's provided by the user by a small amount. Ah, that explains a lot. Thanks a lot, Ross! Do you know if there is a way to modify that? Also, do you have some idea what happens in a case where my guess is, for example, 4s, and I try to predi...

IPOPT perturbs the initial guess from the initial guess that's provided by the user by a small amount.

Hi Ana, If my math is correct here, it looks like you might be simulating an almost-impossibly-fast condition and that might be where the convergence trouble is coming from. Model is rotating the crank at ~175 rad/s, which is a "cadence" of about 28 pedal revolutions per second or almost 1700 rotati...

I haven't done the old IK-->RRA-->CMC for a while, but I think the reserve actuators in that workflow are conceptually similar to what would be done in a MocoTrack or "predictive simulation" problem (non-muscle actuators given a large weight to discourage the optimizer from using them unless really ...

Nice, glad you found it!

Hi Yimeng, In the solution file, are you 100% sure there is no value indicated for the stiffness? In my solution files with parameters optimized, these values are easy to miss, they will have the single parameter value in the first entry (first "timestep"), then the value at all other timesteps will...