ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange

Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Revision history [back]

Not out of the box, but if you read the AMCL code, I think you'll find it pretty simple to change those criteria.

Why _not_ do it? Imagine your robot is just hanging out for a few hours, scan matcher and the lasers aren't perfect, you'll end up drifiting in place while staying still I imagine. Also, if you're running a robot at let's say conservatively 0.5m/s, you're probably going to trigger your AMCL config once a second typically (more or less, I'm just looking at defaults). Do you really want to run this more than once a second?

ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.

Powered by Askbot version 0.10.2