ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2023-07-03 04:08:25 -0500 | received badge | ● Notable Question (source) |
2023-07-03 04:08:25 -0500 | received badge | ● Famous Question (source) |
2023-05-22 14:33:50 -0500 | received badge | ● Famous Question (source) |
2023-05-22 08:48:26 -0500 | received badge | ● Popular Question (source) |
2023-05-22 08:47:48 -0500 | marked best answer | Build ros2 from source in Docker I imagine folks do this all the time, but somehow I can't find a standard Dockerfile or osrf image like osrf/ros2:source. I see the tag mentioned here, but it doesn't exist: https://hub.docker.com/r/osrf/ros2/ Obviously I can just build my own, but I just wanted to ask in case I'm missing something obvious. |
2023-05-22 08:47:18 -0500 | received badge | ● Notable Question (source) |
2023-05-22 08:47:18 -0500 | received badge | ● Famous Question (source) |
2023-05-22 08:46:17 -0500 | marked best answer | ResizeNode subscribes and publishes camera info on the same topic Seems like a dumb question, but I can't find the answer. I see that image_proc::ResizeNode subscribes to /camera_info, and then generates a new CameraInfo message with the scaled intrinsics. But it publishes this scaled camera info on the the same topic. The messages are identical except for fx, fy, cx and cy. How can a downstream node tell them apart? How does this work with image_transport? Thanks. |
2023-05-22 08:46:07 -0500 | answered a question | ResizeNode subscribes and publishes camera info on the same topic Bug reported here: https://github.com/ros-perception/image_pipeline/issues/703 |
2023-05-15 15:11:24 -0500 | received badge | ● Famous Question (source) |
2023-04-24 16:29:46 -0500 | received badge | ● Good Answer (source) |
2023-04-02 13:43:47 -0500 | answered a question | Topic for SCALED_PRESSURE2 This is an old message, but I recently stumbled upon it looking for the same information. The upshot is that mavros doe |
2023-03-17 03:45:30 -0500 | received badge | ● Nice Answer (source) |
2023-02-24 12:14:23 -0500 | received badge | ● Nice Answer (source) |
2023-02-22 07:48:57 -0500 | received badge | ● Necromancer (source) |
2023-01-14 02:16:13 -0500 | received badge | ● Popular Question (source) |
2023-01-14 02:16:13 -0500 | received badge | ● Notable Question (source) |
2023-01-10 02:02:26 -0500 | received badge | ● Good Answer (source) |
2023-01-06 06:36:34 -0500 | received badge | ● Nice Answer (source) |
2022-12-24 07:49:59 -0500 | received badge | ● Good Answer (source) |
2022-12-23 10:17:15 -0500 | received badge | ● Nice Answer (source) |
2022-12-23 08:45:09 -0500 | answered a question | Actions and nested goal states You can nest message types inside message types, service types and action types in both ROS1 and ROS2. See section 2.1. |
2022-12-23 08:45:09 -0500 | received badge | ● Rapid Responder (source) |
2022-12-20 08:57:07 -0500 | edited question | Why isn't Gazebo publishing on the /odom topic on ROS2? Wh Gasebo isn't pubishing on the /odom topin on ROS2? Hey all! I'm having some problems with Gazebo. I'm using ROS2 foxy |
2022-12-19 08:10:15 -0500 | commented answer | ROS2 workspace clean Nice! Thanks for posting. |
2022-12-02 11:50:37 -0500 | asked a question | sensor_msgs_LIBRARIES has ~2000 entries sensor_msgs_LIBRARIES has ~2000 entries Distro: Humble on 22.04 I'm seeing weird behavior, and I don't quite know what |
2022-12-01 12:51:44 -0500 | commented answer | ROS2 Foxy fail to link kdl_parser In Foxy, kdl_parser declared a PUBLIC dependency on urdf, but did not export that dependency. It looks like this was fix |
2022-12-01 12:37:49 -0500 | commented question | [ROS2] CMake Error When Building the Package I don't see a call to ament_package() in your CMakeLists.txt file. See: https://docs.ros.org/en/humble/How-To-Guides/Ame |
2022-11-23 13:53:02 -0500 | commented answer | How to get an array of parameters with rclcpp foo is std::vector<int64_t>. Yes, that is the default. |
2022-11-23 12:54:43 -0500 | commented answer | How to get an array of parameters with rclcpp declare_parameter also gets the parameter. But if you need to use get_parameter, it looks like that isn't possible right |
2022-11-19 08:47:54 -0500 | commented answer | ROS2 action goal canceling problem I was looking for an example that had time.sleep() in it to simulate a long-running calculation. I actually found some g |
2022-11-19 08:44:35 -0500 | marked best answer | Handling long actions in rclpy (with cancellation) The Fibonacci action demo is nice, but it doesn't support cancellation. I added a custom What is a preferred pattern for handling long-running actions in rclpy with cancellation? Any examples / demos / tutorials? Thanks. |
2022-11-19 08:44:25 -0500 | answered a question | Handling long actions in rclpy (with cancellation) Whoops, I looked at the rclpy demos, but forgot about the rclpy examples. There are several server examples showing how |
2022-11-19 08:44:25 -0500 | received badge | ● Rapid Responder (source) |
2022-11-17 19:27:19 -0500 | answered a question | Is there an equivalent of rospy.wait_for_message in ros2? I have not tried it, but I see that this features was added to rclpy Rolling just 2 days ago: https://github.com/ros2/r |
2022-11-17 17:27:11 -0500 | asked a question | Handling long actions in rclpy (with cancellation) Handling long actions in rclpy (with cancellation) The Fibonacci action demo is nice, but it doesn't support cancellatio |
2022-11-17 17:17:32 -0500 | commented answer | ROS2 action goal canceling problem Thanks for this example. Is there a way to support long-running actions? E.g., in https://github.com/ros2/demos/blob/hum |
2022-11-03 16:18:05 -0500 | marked best answer | usb_cam outbuf size mismatch; possibly different format? I'm using usb_cam with a camera that supports mjpeg, but I'm getting errors. The camera supports these formats: Here's my launch file: At 640x480 I get an image, but I also get lots of messages like this: At 800x600 (and above) I do not get an image, but I do get lots of these messages: Interestingly ... (more) |
2022-11-03 16:17:57 -0500 | answered a question | usb_cam outbuf size mismatch; possibly different format? I was able to work around this by modifying usb_cam. I opened a bug: https://github.com/ros-drivers/usb_cam/issues/79 |
2022-10-23 16:00:09 -0500 | received badge | ● Nice Answer (source) |
2022-10-03 01:33:56 -0500 | received badge | ● Famous Question (source) |
2022-09-15 04:19:12 -0500 | received badge | ● Nice Answer (source) |
2022-08-10 00:42:04 -0500 | received badge | ● Notable Question (source) |
2022-07-05 04:56:28 -0500 | received badge | ● Notable Question (source) |
2022-07-01 07:37:09 -0500 | commented answer | UserWarning: ERROR: No flags found I suggest you start a new question for Windows. |
2022-06-22 11:04:58 -0500 | commented question | gstreamer appsink buffer to ROS CompressedImage The fact that the failure is in cvtColor suggests that there's a problem with your gstreamer pipeline. Have you gotten t |
2022-06-16 10:54:44 -0500 | received badge | ● Nice Answer (source) |
2022-06-15 20:05:46 -0500 | received badge | ● Popular Question (source) |
2022-06-03 02:10:52 -0500 | marked best answer | using ros-tooling/action-ros-ci in a private repo Hi, I'm trying to use ros-tooling/action-ros-ci with a private repo. Here are the contents of .github/workflows/build_test.yml: IIUC, this should "just work" with a private repo. But I'm consistently getting github action errors like this: In comparison, I have zero problems with creating a private repo using https://github.com/ros-tooling/action... which uses tooling/action-ros2-lint rather than ros-tooling/action-ros-ci. Any clues? Thanks. |