You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I was trying to implement what this article suggested about minimizing the derivatives of states. Since both coordinates value and speed are provided as state in OpenSim, I ended up with the accelerations. So, I added a MocoOutputGoal with a very small weight for every coordinate's acceleration output. For instance:
I had to do this for every coordinate. The problem converged successfully; although it increased the convergence time, the solution states (coordinate values and speeds) were well-smoothed. I'm not expert, perhaps minimizing the derivatives of coordinate speeds instead of using MocoOutputGoal for coordinate accelerations could make it more efficient computationally. But the smoothness I see in the coordinate values and speeds in my markers+GRF tracking simulation is definitely worth it.
It would be great if you could make this option available for MocoCasADiSolver. For instance, a bool option (set_minimize_coordinates_accelerations) and its weight (set_coordinates_accelerations_weight).
Thank you in advance.
The text was updated successfully, but these errors were encountered:
Hi @nickbianco, thanks for your response. Actually I had tested set_minimize_implicit_multibody_accelerations, but the IPOPT output (e.g., objective, constraint violation, number of iterations, and overall NLP error) was exactly identical compared to before. My simulation was muscle driven marker + GRF tracking (I think the default multibody_dynamics_mode in MocoTrack is set to implicit). It also didn't appear in the solution headers. Could you please explain this option a little bit? What does it do exactly? Thank you.
Hi, I was trying to implement what this article suggested about minimizing the derivatives of states. Since both coordinates value and speed are provided as state in OpenSim, I ended up with the accelerations. So, I added a
MocoOutputGoal
with a very small weight for every coordinate's acceleration output. For instance:I had to do this for every coordinate. The problem converged successfully; although it increased the convergence time, the solution states (coordinate values and speeds) were well-smoothed. I'm not expert, perhaps minimizing the derivatives of coordinate speeds instead of using
MocoOutputGoal
for coordinate accelerations could make it more efficient computationally. But the smoothness I see in the coordinate values and speeds in my markers+GRF tracking simulation is definitely worth it.It would be great if you could make this option available for
MocoCasADiSolver
. For instance, a bool option (set_minimize_coordinates_accelerations
) and its weight (set_coordinates_accelerations_weight
).Thank you in advance.
The text was updated successfully, but these errors were encountered: