gautam2410's profile - activity

Thank you for outlining the possibilities. I'll start with your suggestion to view the images separately and then cross-check each possibility. I'll update you once I'm done with that. Do you have any suggestion/possible explanation for the drop in Velodyne frames? Thanks!

it's very unlikely that the error is in the camera drivers as I'm using widely used pointgrey camera drivers without any modification. Yes, I see the issue in the Rviz window while the bagfile is recording. However, I'm yet to see this issue when the bagfile is not being recorded.

Hello,

I'm trying to store selected topics being published from various sensors sources (velodyne, monocular camera, IMUs) in a large bag file. I'm able to record the bagfile without seeing any errors. However, when I play back the file, I'm seeing the following errors:

1. Some of the frames of the Velodyne data are being dropped. I've tried recording multiple bagfiles but I see this behavior in all of them

2. From the monocular camera, I'm just recording the camera/image_raw topic . However, after about a minute into the bagfile, the camera input image splits into 2 unequal part and one of the parts get displaced (as seen in the pictures below). I'm seeing this behavior in most of the bagfiles and the time of split is random.

Original Image:

Corrupted Image

A few details about my setup:

1. I have tried recording files at 2 buffer sizes 1024 and 0 (infinity) and I see these problems in both cases
2. I have tried recording bagfiles on and Odroid XU4 and a high-performance laptop but that did not help
3. I'm running ROS indigo on Ubuntu 14.04

Rosbag info:

I will be happy to provide any relevant info that may be required. Thanks in advance!

Hello,

I am trying to perform autonomous navigation using hector slam and the navigation stack, something similar to this ( www.youtube.com/watch?v=5V-0Y43i0h8 ) or ( www.youtube.com/watch?v=RPaa8ZsO0rk ) .

I have already seen this post ( answers.ros.org/question/59153/how-to-extract-information-from-hector-slam-for-autonomous-navigation/ ) but instead of working with a pre stored map I want the map to be generated using hector_mapping and simultaneously I am able to perform navigation, that to without using the robot's odometry.

I got hector slam working with hokuyo laser and was able to do mapping using just the laser.

So my doubts are:

1. Is it possible to do this without using the robot's odometry and just using the odometry information from the tf that is being published by hector_mapping ( answers.ros.org/question/62081/using-odometry-from-hector_mapping-for-move_base-nav-stack/ ) ?

2. Does AMCL works only with static maps i.e. can AMCL perform localization on the maps being generated in real time ?

3. Moreover do I need AMCL to perform localization in a dynamic map being generated using hector slam ? If, not then how exactly should I make this work without amcl.

I will be happy to provide any relevant info that may be required and I'm sorry for not publishing actual links as my karma is not enough.

Thank you for your time..

On the wiki page, I see the sentence "To run an unbounded exploration task, simply leave the boundary blank". I'm not sure how exactly should I do this? The same question is asked here

Does the frontier_exploration package provide complete map coverage? I have implemented it and once the region within the set boundaries is explored, the robot stops. Is there any way of using this package to make the robot move to every cell in the set boundary?

The same question has been asked here so I am not posting a new question. Can you please explain how to give the goal with an empty polygon? By unbounded search do you mean the total map coverage?

Hi Sobot, I am trying to achieve something similar but with hector slam and ROS navigation stack. Were you successful in running it? Thanks!

Hey, I am working on a similar problem, were you able to get it running?

Hey Lucas, I am working on a similar application. However, still could not get it running. Did you make any progress?

So was anyone able to figure out how to cover the complete map and not just part of the map as done in exploration?

And if you are not registered on the Aldebaran community, you can still download it from here: http://robocup.bowdoin.edu/public/sof...

I am also getting a similar output. I am using kinect sensor, groovy, 64 bit. Did you find any solution?

Thank you for your reply and for addressing the problem of roboearth with groovy. I will try to follow your solution and then discuss further.