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
#9 implements everything but residual/violation and importance.
For both solvers residual/violation can be calculated easily.
Importance can only be calculated in the HQP solver (?). While iteration over the hierarchy, tasks occurring in later levels as null-space constraints will be assigned multiple importance values. How do we treat these?
Importance can only be calculated in the HQP solver (?).
Yes.
While iterating over the hierarchy, tasks occurring in later levels as null-space constraints will be assigned multiple importance values. How do we treat these?
I suggest keeping the first solution's values only.
Simplify Task class hierarchy. Currently, you distinguish between Task and TaskDesc. I suggest merging them, having finally the following members:
T_c
) + goal (role ofT_t
) ?)These are updated during
compute()
:These are updated during
solve()
and will allow for convergence check:The text was updated successfully, but these errors were encountered: