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
A problem encountered in #133, which was supposed to solve #79, was how to properly define a computation graph for optimal control problems: how do operations (matrices, vectors, "operators") flow between costs, dynamics, constraints and the functions and objects they call into from other libraries (e.g. Pinocchio).
Discussing with others, we have come at the conclusion a computation graph would look like some of DAG with some extra structure/constraints (due to some nodes necessarily being arranged as a timeline, others necessarily being cost functions and dynamics).
A problem encountered in #133, which was supposed to solve #79, was how to properly define a computation graph for optimal control problems: how do operations (matrices, vectors, "operators") flow between costs, dynamics, constraints and the functions and objects they call into from other libraries (e.g. Pinocchio).
Having such a graph would enable:
Discussing with others, we have come at the conclusion a computation graph would look like some of DAG with some extra structure/constraints (due to some nodes necessarily being arranged as a timeline, others necessarily being cost functions and dynamics).
This would address the following issues:
The text was updated successfully, but these errors were encountered: