ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2022-12-19 11:18:57 -0500 | received badge | ● Great Answer (source) |
2022-08-17 16:13:05 -0500 | received badge | ● Nice Answer (source) |
2021-03-04 01:23:58 -0500 | received badge | ● Good Answer (source) |
2020-11-01 15:17:45 -0500 | received badge | ● Nice Answer (source) |
2020-07-27 04:56:39 -0500 | received badge | ● Necromancer (source) |
2018-05-29 10:53:16 -0500 | edited answer | How to execute a ros callback just once In rospy, the easiest way is to use (as gvdhoorn suggests): msg = rospy.wait_for_message('/example_topic', ExampleMsg). |
2018-05-29 10:53:10 -0500 | edited answer | How to execute a ros callback just once In rospy, the easiest way is to use (as gvdhoorn suggests): msg = rospy.wait_for_message('/example_topic', ExampleMsg). |
2018-05-29 10:51:03 -0500 | edited answer | How to execute a ros callback just once The easiest way is to use: msg = rospy.wait_for_message('/example_topic', ExampleMsg). |
2018-05-24 14:13:54 -0500 | edited answer | How to execute a ros callback just once To only run the callback once, you can do something similar to: class Example: def __init__(self): self.sub |
2018-05-24 14:13:39 -0500 | edited answer | How to execute a ros callback just once To only run the callback once, you can do something similar to: class Example: def __init__(self): self.sub |
2018-05-24 14:13:27 -0500 | answered a question | How to execute a ros callback just once To only run the callback once, you can do something similar to: class Example: def __init__(self): self.su |
2018-05-23 10:59:10 -0500 | answered a question | How do I convert an ROS image into a numpy array? This will do what you want, assuming you have an RGB image. If not, you can check the data.encoding and add some extra |
2018-01-07 16:58:53 -0500 | received badge | ● Necromancer (source) |
2018-01-07 16:58:53 -0500 | received badge | ● Teacher (source) |
2017-10-07 23:46:45 -0500 | commented answer | There is no move_base node in move_base package Confirmed. Had the same problem in kinetic and this fixed it! (replacing indigo with kinetic) |
2017-06-19 09:06:07 -0500 | commented answer | Opencv in ROS: fatal error: opencv3/opencv.hpp: No such file or directory compilation terminated. @patrchri, can you post the header code and CMakeLists.txt that you eventually got to work? |
2017-06-06 15:28:35 -0500 | edited answer | Packages 'libswscale and libavcodec' for building usb_cam What worked for me is searching for the package: apt-cache search libavcodec A few options appeared: libavcodec-dev a |
2017-06-06 15:26:19 -0500 | edited answer | gmapping with depthimage_to_laserscan The gmapping package requires you to publish the transform from your sensor link to your base_link, as well as provide o |
2017-06-06 15:24:54 -0500 | received badge | ● Editor (source) |
2017-06-06 15:24:54 -0500 | edited answer | gmapping with depthimage_to_laserscan The gmapping package requires you to publish the transform from your sensor link to your base_link, as well as provide o |
2017-06-06 15:24:27 -0500 | edited answer | gmapping with depthimage_to_laserscan The gmapping package requires you to publish the transform from your sensor_link to your base_link, as well as provide o |
2017-06-06 15:14:41 -0500 | answered a question | gmapping with depthimage_to_laserscan The gmapping package requires you to publish the transform from your camera_link to your base_link as well as odometry d |
2017-01-05 00:22:02 -0500 | received badge | ● Enthusiast |
2016-12-27 11:13:48 -0500 | answered a question | Packages 'libswscale and libavcodec' for building usb_cam What worked for me is searching for the package:
A few options appeared:
|
2016-10-12 15:18:12 -0500 | received badge | ● Supporter (source) |