Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Map merging without initial pose only publishing one of the maps #22

Closed
MerryMarry opened this issue Nov 8, 2018 · 3 comments
Closed
Labels

Comments

@MerryMarry
Copy link

Hello
We are having a group project in ROS using P3AT robots and Gmapping.
We wanted to use your package to merge the maps published by each of the robots but we have faced some problems.
I have read the previous issue on this project where you changed the estimation confidence to merge the maps properly but no matter how much I change it, the only thing that happens it that the merged map changes from robot0 to robot1's map and keeps switching between them, so that we can't manage to get the merged map of both at the same time.

I have attached the image and YAML files of our maps.

Could you please help me out with this?
files and pictures of project.zip

@hrnr
Copy link
Owner

hrnr commented Nov 9, 2018

What version are you using? Are you running from the latest master or from the ROS distribution? The maps you posted are very small (almost none), it will never work for those maps. You need big enough overlapping space for merging to be successful. You can read the attached paper, there are some examples if you want to get the idea what setup you need.

@hrnr hrnr added the question label Nov 9, 2018
@MerryMarry
Copy link
Author

Thank you

@MerryMarry
Copy link
Author

Hello
We developed our maps in order to make them overlap, also we reduced the estimation confidence to 0.3 and the code works fine now!
Thank you for your help, I'm closing this issue now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants