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

There is some problem in LPAstar #18

Open
HandsomeDragon3 opened this issue Mar 25, 2021 · 3 comments
Open

There is some problem in LPAstar #18

HandsomeDragon3 opened this issue Mar 25, 2021 · 3 comments

Comments

@HandsomeDragon3
Copy link

In some case, there would be no path extrated right!

@HandsomeDragon3
Copy link
Author

especially after adding a lot of obstacles

@zhm-real
Copy link
Owner

zhm-real commented Jun 9, 2021

Thanks for your feedback! We will check it later.

@MeetYyj
Copy link

MeetYyj commented Oct 3, 2021

I also find this problem. For example, when program started, after adding obstacke (35, 17) and (36, 16), no path extrated right.
image

I think the key problem is precision of float in function CalculateKey and TopKey.
I changed line 136 like this
s = min(self.U, key=lambda k: tuple(map(lambda x: round(x, 2), self.U[k])))
and line 142&143 like this
return [round(x, 2) for x in [min(self.g[s], self.rhs[s]) + self.h(s), min(self.g[s], self.rhs[s])]]
the path showed.
image

Besides

  1. Line 68, we should also UpdateVertex(Obs) when add obstacles ?
  2. We should not use manhattan heuristic in a 8-neighborhood map ?

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