ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2018-05-07 09:18:52 -0500 | received badge | ● Great Answer (source) |
2018-05-07 09:18:52 -0500 | received badge | ● Guru (source) |
2018-04-04 07:27:31 -0500 | received badge | ● Enlightened (source) |
2018-04-04 07:27:31 -0500 | received badge | ● Good Answer (source) |
2017-05-02 03:14:54 -0500 | received badge | ● Famous Question (source) |
2017-03-01 16:29:25 -0500 | received badge | ● Notable Question (source) |
2017-01-09 08:19:21 -0500 | received badge | ● Nice Answer (source) |
2017-01-05 23:54:13 -0500 | received badge | ● Self-Learner (source) |
2017-01-05 23:54:13 -0500 | received badge | ● Teacher (source) |
2017-01-04 09:04:29 -0500 | answered a question | AMCL Probabilistic Likelihood Field I have read through the AMCL source and this is what I understand from the code: AMCL implements a likelihood field that skips beams whose endpoints do not match the map for a significant number of particles. The skipped beams are not used in computing the probability of the observation given the map p(z|m), which is used as the weight of each particle. Therefore particles that are correct do not get downweighted because of unexpected obstacles. This claimed to help in dynamic environments. Algorithm Details:
|
2017-01-04 07:54:06 -0500 | received badge | ● Popular Question (source) |
2016-12-30 12:37:07 -0500 | asked a question | AMCL Probabilistic Likelihood Field I am interested in trying out the probabilistic Likelihood field observation model in amcl because if its beam_skip feature. However, there is no documentation in the AMCL ROS Wiki about the beam skip parameters. I know about them because I was digging through the amcl source code. The paramters are: It would be great if someone could shed some light on what those parameters mean. I also wanted to understand the difference between the standard likelihood field which I understand by reading Thrun's book and the probabilistic likelihood field that can be used in amcl. My motivation behind this is to try and improve amcl localization when the map changes significantly due to new obstacles. Ideally I would like amcl to remove all beams that don't match the static map prior to evaluating p(z|m) |