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

Distance to frontier evaluation #7

Open
DmytroKushnirSoftserveinc opened this issue Feb 28, 2019 · 0 comments
Open

Distance to frontier evaluation #7

DmytroKushnirSoftserveinc opened this issue Feb 28, 2019 · 0 comments
Assignees
Labels
Heuristics improves cost evaluation or planning order

Comments

@DmytroKushnirSoftserveinc
Copy link
Contributor

DmytroKushnirSoftserveinc commented Feb 28, 2019

Default heuristics for ranking the frontiers uses plane Euclidean metric for evaluating the distance.
As we have a highly structured environment (indoor strongly resembles task of navigation inside the labyrinth) it would be better to use geodesical path distance: 'real distance we have to traverse to reach the point'. For this, we can reuse produced path from the ros_nav nodes (move_base group of packages)

  • TODO: add parametrisation for weight of this heuristic.
@DmytroKushnirSoftserveinc DmytroKushnirSoftserveinc changed the title F#4: Improve distance evaluation heuristics F#4_2: Improve distance evaluation heuristics Feb 28, 2019
@DmytroKushnirSoftserveinc DmytroKushnirSoftserveinc changed the title F#4_2: Improve distance evaluation heuristics Improve distance evaluation heuristics Mar 21, 2019
@DmytroKushnirSoftserveinc DmytroKushnirSoftserveinc added the Heuristics improves cost evaluation or planning order label Mar 27, 2019
@DmytroKushnirSoftserveinc DmytroKushnirSoftserveinc changed the title Improve distance evaluation heuristics Distance to frontier evaluation Mar 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Heuristics improves cost evaluation or planning order
Projects
None yet
Development

No branches or pull requests

1 participant