[signal, include, tools] Use robot_utils' sot-core files instead of the ones of sot-torque-control #59
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull-request linked to the creation of
robot_utils
tool in sot-core based oncommon
from sot-torque-control.robot_utils
,signal_helper
andmatrix_geometry
from sot-core instead ofcommon
,signal_helper
andvector_conversion
from sot-torque-control.logger
includes and use directlysendMsg
method ofrobot_utils
instead ofgetLogger.sendMsg
.common
torobot_utils
by moving the python wrapper, changing the CMakeLists accordingly. (see PR #79)Use the namespace dynamic_graph::sot with a short cut (dg::sot) for Vector[1|6]d instead of Eigen. (fix the issue Change namespace Vector6d to dynamic_graph::sot #57)
WARNING: This pull-request should follow the ones about the macros:
Fix the sot-core convention to follow the one of dynamic_graph #78 and #35.