- Oct 16, 2014
-
-
olivier stasse authored
-
- Mar 20, 2014
-
-
Francois Keith authored
-
Francois Keith authored
The trigger signal cannot be destroyed.
-
- Feb 28, 2014
-
-
Gennaro Raiola authored
This enables to directly launch a python file within any roslaunch file Adapted by F.Keith for the extraction of the messages.
-
- Feb 12, 2014
-
-
Pierre Gergondet authored
Fixes #22 Conflicts: include/dynamic_graph_bridge/ros_interpreter.hh src/ros_interpreter.cpp
-
Francois Keith authored
Deregister the signal formerly added. Add a mutex system to prevent removing a signal while triggering it, to avoid a crash (especially if the topic was listened to).
-
- Nov 07, 2013
-
-
Florent Lamiraux authored
Without this call the command fails.
-
- Nov 05, 2013
-
-
Benjamin Coudrin authored
-
- Nov 04, 2013
-
-
Nirmal Giftsun authored
-
- Sep 26, 2013
-
-
Francois Keith authored
The old names are kept for now, but will disappear in the future.
-
Francois Keith authored
The old names are kept for now, but will disappear in the future.
-
- Sep 12, 2013
-
-
Damien Petit authored
-
Damien Petit authored
-
- Jul 15, 2013
-
-
Florent Lamiraux authored
Launching an application in a roslaunch file may cause to send python command before the interpreter has read the prologue. This commit should fix this issue.
-
- Jul 11, 2013
-
-
olivier stasse authored
-
olivier stasse authored
-
- Jul 10, 2013
-
-
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]
-
- Jul 08, 2013
-
-
olivier stasse authored
-
- Apr 25, 2013
-
-
olivier stasse authored
Pb: The openrtm architecture loads a shared library to implement the services of an OpenRTM node. The scheduling properties are ensured by the operating system running openrtm. Then on the robot, when the shared library is loaded it is run inside the real-time loop. As sot-hrp-2 was creating the interpreter and the ros-node in the constructor this used to break HRP-2 real-time OS. This commit change the initialization of the ros-node to use a multi-threaded spinner. Then ros calls are handled in a seperate non-realtime thread.
-
- Sep 07, 2012
-
-
olivier stasse authored
-
- May 17, 2012
-
-
Florent Lamiraux authored
-
- May 15, 2012
-
-
Thomas Moulard authored
-
- May 11, 2012
-
-
Thomas Moulard authored
-
Thomas Moulard authored
-
- May 09, 2012
-
-
Thomas Moulard authored
-
- May 07, 2012
-
-
Thomas Moulard authored
-
- Apr 28, 2012
-
-
Florent Lamiraux authored
Define entity RosTime that exports Ros time in a signal, add this entity in class dynamic_graph.ros.ros.Ros. Transfer Ros time in signal of type ptime instead of vector.
-
- Mar 21, 2012
-
-
Thomas Moulard authored
It happens, especially at init that vector are null (of size 0). In this case, avoid abrupt failure by just copying the available data instead of aborting the whole software.
-
- Mar 14, 2012
-
-
Thomas Moulard authored
-
Thomas Moulard authored
Previous version of abstract-robot-dynamics did not contain the joint name. Therefore, we had no way to forward the joint names to ROS. This patch changes the ros_joint_state entity to add a retrieveJointNames command. This command uses the pool to retrieve an instance of the Dynamic entity (i.e. robot.dynamic) by using the entity name. It then iterates on the robot structure to fill the joint names in the message. This command is automatically called in the Ros class so this change is transparent for the end-user. However, no more assumptions are made on the robot structure so the sent message is exactly matching the robot structure loaded in the dynamic entity. In particular, the free floating DOFs are sent and the hard coded hand values have been removed. ROS, in fact, requires DOF names and not joint names. Therefore, the names are computed as follow: - 0 dof: ignored, - 1 dof: dof name is the joint name, - >1 dof: <joint name>_<dof id>
-
Florent Lamiraux authored
-
Florent Lamiraux authored
RosImport entity writes data from a signal to a ROS topic.
-
- Mar 13, 2012
-
-
Florent Lamiraux authored
-
- Mar 12, 2012
-
-
Thomas Moulard authored
-
- Mar 08, 2012
-
-
Florent Lamiraux authored
Rename targets - dynamic_graph/ros/ros_import/wrap -> ros/ros_import/wrap, - dynamic_graph/ros/ros_export/wrap -> ros/ros_export/wrap, - dynamic_graph/ros/ros_joint_state/wrap -> ros/ros_joint_state/wrap. Add missing linking flags to target interpreter. Do not redefine PYTHON_SITELIB, use cmake/python.cmake definition.
-
- Feb 28, 2012
-
-
Thomas Moulard authored
-
Thomas Moulard authored
-
- Feb 27, 2012
-
-
Thomas Moulard authored
-
- Feb 07, 2012
-
-
Thomas Moulard authored
-
- Dec 22, 2011
-
-
Thomas Moulard authored
-