ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | Q&A answers.ros.org |
2022-12-08 08:52:12 -0500 | received badge | ● Enlightened (source) |
2022-12-08 08:52:11 -0500 | received badge | ● Good Answer (source) |
2022-12-08 08:43:42 -0500 | received badge | ● Nice Answer (source) |
2022-11-03 16:37:25 -0500 | received badge | ● Self-Learner (source) |
2022-11-03 16:37:23 -0500 | received badge | ● Student (source) |
2022-10-12 06:18:33 -0500 | received badge | ● Famous Question (source) |
2022-09-19 06:58:59 -0500 | received badge | ● Necromancer (source) |
2022-08-19 15:48:04 -0500 | received badge | ● Notable Question (source) |
2022-08-04 23:27:05 -0500 | received badge | ● Notable Question (source) |
2022-07-30 08:31:09 -0500 | received badge | ● Notable Question (source) |
2022-07-30 08:31:09 -0500 | received badge | ● Popular Question (source) |
2022-06-13 17:53:20 -0500 | commented answer | Topic remapping in launch.xml is not working for topic_tools/mux node The documentation for mux says to use mux:=asdf. I just created a launch file with <node name="asdf" pkg="topic_tools |
2022-06-13 17:53:09 -0500 | commented answer | Topic remapping in launch.xml is not working for topic_tools/mux node The documentation for mux says to use mux:=foo. I just created a launch file with <node name="asdf" pkg="topic_tools" |
2022-06-13 17:45:32 -0500 | received badge | ● Popular Question (source) |
2022-06-13 02:54:01 -0500 | received badge | ● Popular Question (source) |
2022-06-13 02:54:01 -0500 | received badge | ● Notable Question (source) |
2022-06-13 02:53:59 -0500 | received badge | ● Notable Question (source) |
2022-06-13 02:53:59 -0500 | received badge | ● Popular Question (source) |
2022-06-12 21:18:05 -0500 | edited question | Topic remapping in launch.xml is not working for topic_tools/mux node Topic remapping in launch.xml is not working for topic_tools/mux node The documentation for topic_tools/mux says: IM |
2022-06-12 17:25:44 -0500 | asked a question | Topic remapping in launch.xml is not working for topic_tools/mux node Topic remapping in launch.xml is not working for topic_tools/mux node The documentation for topic_tools/mux says: IM |
2022-04-22 07:31:58 -0500 | received badge | ● Self-Learner (source) |
2022-04-22 07:31:58 -0500 | received badge | ● Teacher (source) |
2022-04-22 04:12:00 -0500 | marked best answer | What controls the Python search path, and how? In my shell I first activate a Python virtual environment and then the Catkin workspace which results in this Yet when I run I would expect it to add the first two entries (so that the ROS package's own Python modules take priority), but keep the rest which include my |
2022-04-21 15:03:28 -0500 | answered a question | What controls the Python search path, and how? Basically, my nodes were being launched with a different python3 executable than I expected. This is because roslaunch |
2022-04-21 15:03:28 -0500 | received badge | ● Rapid Responder (source) |
2022-04-21 14:49:42 -0500 | commented question | What controls the Python search path, and how? When roslaunch calls execve() to run my node, it is executing (via some symlinks) /home/user/project/devel/.private/pkg/ |
2022-04-21 14:32:59 -0500 | received badge | ● Commentator |
2022-04-21 14:32:59 -0500 | commented question | What controls the Python search path, and how? It appears that it is due to the Python interpreter /usr/bin/python3 being executed instead of /home/user/project/.venv/ |
2022-04-21 14:17:43 -0500 | asked a question | What controls the Python search path, and how? What controls the Python search path, and how? In my shell I first activate a Python virtual environment and then the Ca |
2022-04-08 03:44:57 -0500 | received badge | ● Famous Question (source) |
2022-04-08 03:44:57 -0500 | received badge | ● Notable Question (source) |
2022-04-08 03:44:57 -0500 | received badge | ● Popular Question (source) |
2022-02-05 21:40:25 -0500 | received badge | ● Notable Question (source) |
2022-02-05 21:40:25 -0500 | received badge | ● Famous Question (source) |
2022-02-05 21:40:21 -0500 | marked best answer | Cannot install catkin-tools on Debian buster due to Python version requirement I installed ROS Noetic on a Debian Buster system, which is listed as a supported platform. However, I cannot install packages (like Though |
2022-02-03 14:09:53 -0500 | answered a question | Cannot install catkin-tools on Debian buster due to Python version requirement Until this bug is resolved it should be possible to do: wget http://packages.ros.org/ros/ubuntu/pool/main/p/python3-osr |
2022-02-03 14:09:53 -0500 | received badge | ● Rapid Responder (source) |
2022-02-03 13:40:26 -0500 | commented question | Cannot install catkin-tools on Debian buster due to Python version requirement I think this was a regression introduced in this pull request and hopefully it can be resolved by publishing the right p |
2022-02-03 13:29:05 -0500 | edited question | Cannot install catkin-tools on Debian buster due to Python version requirement Cannot install catkin-tools on Debian buster due to Python version requirement I installed ROS Noetic on a Debian Buster |
2022-02-03 13:28:01 -0500 | asked a question | Cannot install catkin-tools on Debian buster due to Python version requirement Cannot install catkin-tools on Debian buster due to Python version requirement I installed ROS Noetic on a Debian Buster |
2021-12-15 03:53:28 -0500 | received badge | ● Popular Question (source) |
2021-12-15 03:53:28 -0500 | received badge | ● Notable Question (source) |
2021-12-15 03:53:28 -0500 | received badge | ● Famous Question (source) |
2021-11-14 09:35:08 -0500 | marked best answer | Defining message types directly in Python I'm writing a Python script to synthesize a rosbag from data files generated outside of ROS. It would be easiest to be able to define the ROS message types within my Python code, rather than have to write standalone What would this entail? I'm fine with importing from |
2021-11-14 09:35:01 -0500 | received badge | ● Rapid Responder (source) |
2021-11-14 09:35:01 -0500 | answered a question | Defining message types directly in Python from genpy.dynamic import generate_dynamic msgs = generate_dynamic('pkg/Msg', 'string data\n') Here msgs is a dictiona |
2021-11-14 09:22:50 -0500 | edited question | Defining message types directly in Python Defining message types directly in Python I'm writing a Python script to synthesize a rosbag from data files generated o |
2021-11-14 09:11:26 -0500 | edited question | Defining message types directly in Python Defining message types directly in Python I'm writing a Python script to synthesize a rosbag from data files generated o |