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

Test multiple sensor input support #1227

Closed
crdelsey opened this issue Oct 11, 2019 · 2 comments
Closed

Test multiple sensor input support #1227

crdelsey opened this issue Oct 11, 2019 · 2 comments

Comments

@crdelsey
Copy link
Contributor

Support for multiple obstacle sensor sources exists in the obstacle/voxel layer. We need to test and verify it works.

@SteveMacenski There is no support for multiple sensor sources in AMCL. Do you think we need it there as well?

@crdelsey crdelsey mentioned this issue Oct 11, 2019
16 tasks
@SteveMacenski
Copy link
Member

SteveMacenski commented Oct 11, 2019

AMCL never before supported it, but if you see opportunity to support I wouldn't oppose! I haven't read the library with the eyes of trying to do multiple, I suspect it will be harder than it looks if theres even slight deviation in the relative positions of the lasers

@ninamwa
Copy link

ninamwa commented Feb 27, 2020

Is it a requirement that a subscribed topic for the obstacle layer is /scan? I tried testing with two different scan topics, named scan_1 and scan_2. When setting the initial pose in Rviz, nothing happens and the transform from map to odom is never created. When changing the topics to /scan and /scan_2, the initialization is fine again. But then it does look like only the /scan topic is included in the local costmap..

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

No branches or pull requests

3 participants