Hot answers tagged

2

Since you're using gazebo already and it should then be generating simulated time you can ask gazebo to run slower than realtime. In the physics section of your world you can ajdust the maximum realtime factor to tell gazebo to run slower than realtime using the real_time_factor parameter. There's a tutorial on the physics parameters here which you may find ...


2

I took at look at your example and you're correctly noticing that it is not executing. The problem is that python expects the constructor will invoke __init__ while you are defining _init_ Note the different number of underscores. Thus non of your setup code is being executed. I fixed that and saw more of the outputs that you expected since the system was ...


1

I think that you're correct in your assessment that "there is some disconnect between the axes of the 2D map and the response from aruco_detect." Reading the documentation for the topic /fiducial_transforms you'll see that those transforms are relative to the camera, "The transforms showing the pose of the fiducials relative to the camera.&...


1

roslaunch expects you to be launching ROS nodes. And it's passing standard ROS nodes arguments such as the full name and log path. You're seeing the errors in it rejecting arguments __name: __log: If you want to make this work you should use a script which is robust to receiving these extra arguments. Or wrap it in a script which will discard the extra ...


1

I agree with r-bryan that you're likely missinterpreting some of the metadata. It could be the frame width or alternatively the stride width or something else in the depth image. There's a good reference implementation that you can compare yours to the one in depth_image_proc The main part of the implementation is in this header where you can see that there'...


1

At first I thought there was some sort of systematic raw format or resolution error, sort of like ROS + kinect depth data duplication . Then I noticed that each corridor appears in a different perspective, as if the sensor turned to point a different way between two captured frames. You didn't say what sensor you're using, but I assume it's not two cams that ...


Only top voted, non community-wiki answers of a minimum length are eligible