ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2023-05-09 08:04:50 -0500 | received badge | ● Necromancer (source) |
2022-10-21 03:38:33 -0500 | received badge | ● Famous Question (source) |
2022-09-23 02:00:30 -0500 | received badge | ● Notable Question (source) |
2022-07-21 00:04:49 -0500 | edited answer | Dynamically updating 3D plot in python using saved Odometry timestamp, quaternion, and translation data I assume your data is from a ROS odometry "pose": is that where you got it from ? or where from ? Normally a robot's po |
2022-07-20 03:13:41 -0500 | answered a question | How to launch roslaunch from python script I prefer to spawn a separate bash file, e.g. which then does whatever... sproc = subprocess.Popen("action.sh") # |
2022-07-20 02:57:39 -0500 | answered a question | Trying to save HDF5 file in ROS Odometry node; .h5 file not being saved maybe add some explicit file location to save to ? Key question is what are you saving it for ? I like to write numpy t |
2022-07-20 02:41:23 -0500 | edited answer | Dynamically updating 3D plot in python using saved Odometry timestamp, quaternion, and translation data I assume your data is from a ROS odometry "pose": is that where you got it from ? or where from ? Normally a robot's po |
2022-07-20 02:33:02 -0500 | answered a question | Dynamically updating 3D plot in python using saved Odometry timestamp, quaternion, and translation data Your data looks like a ROS tf2 transform... or a "pose": is that where you got it from ? Anyway, "tf"s are well visuali |
2022-07-20 02:33:02 -0500 | received badge | ● Rapid Responder (source) |
2022-07-17 23:43:26 -0500 | edited answer | Failed to load library /opt/ros/noetic/lib//libspatio_temporal_voxel_layer.so I now see there is a long history to this ... @ https://github.com/SteveMacenski/spatio_temporal_voxel_layer/issues/167 |
2022-07-17 02:25:39 -0500 | received badge | ● Popular Question (source) |
2022-07-14 22:35:58 -0500 | received badge | ● Student (source) |
2022-07-14 22:29:28 -0500 | answered a question | Failed to load library /opt/ros/noetic/lib//libspatio_temporal_voxel_layer.so I now see there is a long history to this ... @ https://github.com/SteveMacenski/spatio_temporal_voxel_layer/issues/167 |
2022-07-12 22:18:06 -0500 | asked a question | Failed to load library /opt/ros/noetic/lib//libspatio_temporal_voxel_layer.so Failed to load library /opt/ros/noetic/lib//libspatio_temporal_voxel_layer.so ERROR = " what(): Failed to load library / |
2022-05-20 17:01:25 -0500 | received badge | ● Necromancer (source) |
2021-03-11 19:35:06 -0500 | received badge | ● Famous Question (source) |
2021-03-11 19:35:06 -0500 | received badge | ● Notable Question (source) |
2021-02-24 10:30:14 -0500 | answered a question | SLAM Toolbox : "Warning: TF_REPEATED_DATA" when running rosbag in ROS Noetic. How do I get rid of this warning ? I now get the same with Cartographer ... There is comment @ https://answers.ros.org/question/359968/tf_repeated_data-e |
2021-01-18 08:19:26 -0500 | received badge | ● Enthusiast |
2020-11-10 04:19:53 -0500 | received badge | ● Popular Question (source) |
2020-11-08 17:32:38 -0500 | received badge | ● Teacher (source) |
2020-11-08 12:55:59 -0500 | answered a question | what is the standard way to get the quality of the obtained pose from slam_toolbox? I use the un-corrected (no tf) robot odometry as a baseline: if your robot is reasonably accurate, its basic odom readin |
2020-11-08 12:55:59 -0500 | received badge | ● Rapid Responder (source) |
2020-11-01 11:50:49 -0500 | edited answer | How to get robot position in map? I guess you already have the map subscribed as an OccupancyGrid: from nav_msgs.msg import OccupancyGrid If so, for me, |
2020-11-01 11:46:17 -0500 | edited answer | How to get robot position in map? I guess you already have the map subscribed as an OccupancyGrid: from nav_msgs.msg import OccupancyGrid If so, f |
2020-10-30 10:00:22 -0500 | answered a question | How to get robot position in map? I guess you already have the map subscribed as an OccupancyGrid (from nav_msgs.msg import OccupancyGrid). If so, for me |
2020-10-30 09:33:02 -0500 | edited answer | Cartographer ROS Scan-lag issue in PointCloud with clockwise Lidar I found a work-around to solve this: Cartographer ROS lets you change the .lua file in ~slam/config to: num_laser_sca |
2020-10-30 09:29:57 -0500 | answered a question | Cartographer ROS Scan-lag issue in PointCloud with clockwise Lidar I found a work-around to solve this: Cartographer ROS lets you change the .lua file in ~slam/config to: num_laser_sca |
2020-10-30 09:18:04 -0500 | edited question | Cartographer ROS Scan-lag issue in PointCloud with clockwise Lidar Cartographer ROS Scan-lag issue in PointCloud with clockwise Lidar On my TurtleBot3 the Lidar takes ~ 0.2 seconds to spi |
2020-10-30 09:18:04 -0500 | received badge | ● Editor (source) |
2020-10-30 09:13:58 -0500 | answered a question | Definitions of map and tf using turtlebot3 A map is type nav_msgs OccupancyGrid @ link text While for tf (assuming "tf2") see tutorials @ link text |
2020-10-27 05:05:37 -0500 | edited question | Cartographer ROS Scan-lag issue in PointCloud with clockwise Lidar Cartographer ROS Scan-lag issue in PointCloud with clockwise Lidar On my TurtleBot3 the Lidar takes ~ 0.2 seconds to spi |
2020-10-21 12:24:51 -0500 | asked a question | Cartographer ROS Scan-lag issue in PointCloud with clockwise Lidar Cartographer ROS Scan-lag issue in PointCloud with clockwise Lidar On my TurtleBot3 the Lidar takes ~ 0.2 seconds to spi |
2020-10-21 09:47:42 -0500 | received badge | ● Autobiographer |