-
Notifications
You must be signed in to change notification settings - Fork 325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] a general option in Moco solver to minimize the coordinates accelerations #3899
Comments
Hi @mrrezaie, if using implicit multibody dynamics, the options minimize_implicit_multibody_accelerations and implicit_multibody_accelerations_weight exist. A more general feature would need to be implemented in a new |
Hi @nickbianco, thanks for your response. Actually I had tested |
@mrrezaie, the default multibody dynamics mode in MocoTrack is "explicit". In "explicit" mode, those settings will not have any effect. |
Deeply sorry, my bad. |
No worries @mrrezaie! |
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: