meco-group / omg-tools

Optimal Motion Generation-tools: motion planning made easy
GNU Lesser General Public License v3.0
565 stars 98 forks source link

Obstacle avoidance error in tutorial_example.py #77

Closed heguohao0728 closed 4 years ago

heguohao0728 commented 4 years ago

Hi! Thanks for providing omg-tools! I'm new in vehicle path planning and obstacle avoidance. I have read all of your codes, it's really great! But when I try to run tutorial_example.py, some errors happened. When I run this file with its original setting, it works fine. But when I changed some parameters, it worked like the screenshot below: screenshot1 Could you tell me why this happened and how to solve it? Really appreciated!

heguohao0728 commented 4 years ago

Hello, professor! If this wrong is too simple but too hard or complicated to explan it, please tell me which part of the code I must pay attention. Thank you so much!

timmercy commented 4 years ago

Hello!

Is the horizontal rectangle a moving obstacle? Could you post your adapted code?

heguohao0728 commented 4 years ago

Thanks! The rectangle is not a moving obstacle!

This problem always happened when I ran the code on my computer. For example: In tutorial_example.py, when I change the initial conditions of the vehicle like below: original code vehicle.set_initial_conditions([-1.5, -1.5]) updated code vehicle.set_initial_conditions([1., -1.5]) and the error will show like below: sc

This is one situation, and the problem I raised in Dec. 2019 is another situation. In that case, I only change the position of a static obstacle.

rubenvanparys commented 4 years ago

Hi, does the terminal output say 'Infeasible problem detected'?

Op vr 3 jan. 2020 07:22 schreef heguohao0728 notifications@github.com:

Thanks! The rectangle is not a moving obstacle!

This problem always happened when I ran the code on my computer. For example: In tutorial_example.py, when I change the initial conditions of the vehicle like below: original code vehicle.set_initial_conditions([-1.5, -1.5]) updated code vehicle.set_initial_conditions([1., -1.5]) and the error will show like below: [image: sc] https://user-images.githubusercontent.com/54935494/71709724-d893dc00-2e33-11ea-973d-c47e15d3d003.png

This is one situation, and the problem I raised in Dec. 2019 is another situation. In that case, I only change the position of a static obstacle.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/meco-group/omg-tools/issues/77?email_source=notifications&email_token=ADQ755NBPXXV2VQ74NOIT33Q33KR7A5CNFSM4J7I6DVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIAMQGY#issuecomment-570476571, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADQ755LLZ72GBDTHIO7PEPDQ33KR7ANCNFSM4J7I6DVA .

heguohao0728 commented 4 years ago

oh, Yes! It shows at the beginning. But why? I mean...this is a very simple room...

rubenvanparys commented 4 years ago

Yes, but note it is a highly non-convex problem... Sometimes it occurs no solution is found... You could try to use a scheduler problem that tries to overcome the non-convexity difficulty by using a simple global planner, and optimizing locally. See e.g. https://github.com/meco-group/omg-tools/blob/master/examples/schedulerproblem_example1.py

rubenvanparys commented 4 years ago

paper: https://lirias2repo.kuleuven.be/rest/bitstreams/484961/retrieve

heguohao0728 commented 4 years ago

Thanks for your advice! I'll learn this paper and atfer that I will try it myself!