SimTK Exception thrown at InteriorPointOptimizer.cpp:264: when running CMC tool
Posted: Thu Sep 02, 2021 4:01 am
So, I've been trying to run CMC tool for my gait analysis.
However, this error message appears at the same time of the CMC analysis if I set the analysis time from 0 to 1.03333 s (legible recorded motion). "Unable to find a feasible solution at time = 0.7."
However, the analysis would've completed if I were to set the time 0.6 to 1.03333 s (quite odd, considering that it passed the same period at which the OPTIMIZATION FAILED error occurs)
I thought it was because I didn't put in the ground torque/moment values, but with or without the error still appeared. Any idea what triggers this?
SimTK Exception thrown at InteriorPointOptimizer.cpp:264:
Optimizer failed: Ipopt: Restoration failed (status -2)
OPTIMIZATION FAILED...
CMC::computeControls: Optimizer could not find a solution.
Unable to find a feasible solution at time = 0.7.
Model cannot generate the forces necessary to achieve the target acceleration.
Possible issues: 1. not all model degrees-of-freedom are actuated,
2. there are tracking tasks for locked coordinates, and/or
3. there are unnecessary control constraints on reserve/residual actuators.
However, this error message appears at the same time of the CMC analysis if I set the analysis time from 0 to 1.03333 s (legible recorded motion). "Unable to find a feasible solution at time = 0.7."
However, the analysis would've completed if I were to set the time 0.6 to 1.03333 s (quite odd, considering that it passed the same period at which the OPTIMIZATION FAILED error occurs)
I thought it was because I didn't put in the ground torque/moment values, but with or without the error still appeared. Any idea what triggers this?
SimTK Exception thrown at InteriorPointOptimizer.cpp:264:
Optimizer failed: Ipopt: Restoration failed (status -2)
OPTIMIZATION FAILED...
CMC::computeControls: Optimizer could not find a solution.
Unable to find a feasible solution at time = 0.7.
Model cannot generate the forces necessary to achieve the target acceleration.
Possible issues: 1. not all model degrees-of-freedom are actuated,
2. there are tracking tasks for locked coordinates, and/or
3. there are unnecessary control constraints on reserve/residual actuators.