Introduce the Variables Handler #50
Conversation
Co-authored-by: Silvio Traversaro <silvio.traversaro@iit.it>
GiulioRomualdi
force-pushed
the
feature/add_variable_handler
branch
from
a5954b0
to
85a7125
Compare
| class VariablesHandler | ||
| { | ||
|
|
||
| std::unordered_map<std::string, iDynTree::IndexRange> m_variables; /**< Map containing the name |
There was a problem hiding this comment.
Since you are using an IndexRange, I guess that the assumption is to store all the values in a vector. Does it make sense to add a container to store the values in this class? In this way, once you fill the whole buffer (maybe from the solution of the optimization variable), you can get the values directly using getVariable, maybe using a GenericVector as a output. In fact, you can use span to get a reference to a sub-vector, then you can use it to build a GenericVector.
There was a problem hiding this comment.
After a short Fm2mF (Face-mask to mask-face) discussion we decided to avoid implementing this in the current PR. Since we are thinking to introduce CasADi in our pipeline, we may need different implementations of the handler.
This PR implement the first version of the variables handler. It is really useful for giving a meaning of variables stacked in a vector