Skip to content
Snippets Groups Projects
  1. Feb 12, 2014
  2. Jan 08, 2014
  3. Dec 19, 2013
  4. Dec 04, 2013
  5. Dec 02, 2013
  6. Nov 09, 2013
  7. Nov 07, 2013
  8. Nov 05, 2013
  9. Nov 04, 2013
  10. Sep 26, 2013
  11. Sep 13, 2013
  12. Sep 12, 2013
  13. Sep 11, 2013
  14. Jul 16, 2013
  15. Jul 15, 2013
  16. Jul 11, 2013
  17. Jul 10, 2013
    • olivier stasse's avatar
      Publish joint-states using the SoT · 2be0ffb4
      olivier stasse authored
      Setting up ROS:
      rosparam load `rospack find hrp2_14_description`/sot/hrp2_14_reduced.yaml
      rosrun robot_state_publisher state_publisher
      
      Display the robot using the info given in
      https://trac.laas.fr/gepetto/hrp2/hrp2_14_description/html/reference/
      
      To repeat at each simulation:
      rosrun dynamic_graph_bridge geometric_simu --input-file ~/devel/ros-unstable-2/install/lib/libsot-hrp2-14-controller.so
      rosrun dynamic_graph_bridge run_command
      >>> from dynamic_graph.sot.application.velocity.precomputed_tasks import *
      >>> solver=initialize(robot)
      rosservice call /start_dynamic_graph
      >>> Put_whatever_you_want_in_python
      
      The rationale is to use a state vector map provided by the robot stack.
      For instance for hrp-2 we have a yaml file providing the ros parameter:
      /sot/state_vector_map
      which specifies the state vector:
      [RLEG_JOINT0, RLEG_JOINT1, RLEG_JOINT2, RLEG_JOINT3, RLEG_JOINT4, RLEG_JOINT5, LLEG_JOINT0,
        LLEG_JOINT1, LLEG_JOINT2, LLEG_JOINT3, LLEG_JOINT4, LLEG_JOINT5, CHEST_JOINT0, CHEST_JOINT1,
        HEAD_JOINT0, HEAD_JOINT1, RARM_JOINT0, RARM_JOINT1, RARM_JOINT2, RARM_JOINT3, RARM_JOINT4,
        RARM_JOINT5, RARM_JOINT6, LARM_JOINT0, LARM_JOINT1, LARM_JOINT2, LARM_JOINT3, LARM_JOINT4,
        LARM_JOINT5, LARM_JOINT6]
      2be0ffb4
  18. Jul 08, 2013
Loading