Try ".add()" instead.

(Appending to a std::vector in Matlab and Python works differently and I can never remember which one to use.)

Ah yes, apologies. Here is the correct snippet: finalHandVelocity = MocoFinalOutputGoal('final_hand_velocity); finalHandVelocity.setOutputPath('/bodyset/hand|linear_velocity'); finalHandVelocity.setMode('endpoint_constraint'); bounds = StdVectorMocoBounds(); bounds.append(MocoBounds(10)); finalHandV...

Hi Cedric, You can use MocoFinalOutputGoal in endpoint constraint mode to achieve what you're looking for: finalHandVelocity = MocoFinalOutputGoal('final_hand_velocity); finalHandVelocity.setOutputPath('/bodyset/hand|linear_velocity'); finalHandVelocity.setMode('endpoint_constraint'); finalHandVeloc...

Hi Rick,

You need to use `set_default_activation()` here. `setActivation()` sets the activation for the current state, not the default activation.

Best,
Nick

Hi Rick, The default activation check is a check we perform internally for the model. In most OpenSim simulations (not necessarily Moco), you don't want muscle controls to get too small to avoid singularities in the muscle dynamics. To avoid the error, simply set the default activation for DELT1 in ...

Hi Mohammadreza, If you have large residuals in ID, then it is unlikely that you will be able to achieve fully smooth controls by tracking the markers and GRFs tightly. Since you are enforcing the residuals to be small, the dynamic inconsistencies have to be made up somewhere. If you want smoother c...

Hi Mohammadreza, The actuator controls don't seem particularly "noisy", but there are certainly spikes at a some time points. Since you are running the problem with weak residuals and tightly tracking markers and GRFs, the model will need to adjust the controls (compared to ID) in order to maintain ...

I'm happy to help get over those hurdles whenever you encounter them!

It would be nice to update the Dockerfile on opensim-core, so it would be useful to know that the whole process is working for you.

Hi Siva, I would recommend starting with larger reserve actuator strengths and then plotting the results of each simulation to try to better understand why the problem did not converge or achieve the expected motion. I would also try running the simulation with and without the constant applied force...

Docker/Singularity is actually the best way to go! You'll first need to create a Docker image and host it on Docker Hub. To do that, you'll first need to write a Dockerfile to create a Docker image that will contain your OpenSim build. Here is an example Dockerfile for building OpenSim . It is a bit...