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

The node of behavior_path_planner dies in some conditions #2607

Closed
3 tasks done
shulanbushangshu opened this issue Jan 3, 2023 · 10 comments
Closed
3 tasks done

The node of behavior_path_planner dies in some conditions #2607

shulanbushangshu opened this issue Jan 3, 2023 · 10 comments
Assignees
Labels
type:bug Software flaws or errors.

Comments

@shulanbushangshu
Copy link
Contributor

shulanbushangshu commented Jan 3, 2023

Checklist

  • I've read the contribution guidelines.
  • I've searched other issues and no duplicate issues were found.
  • I'm convinced that this is not my fault but a bug.

Description

The node of behavior_path_planner dies when I set target in change lane.The simulation is shown as below:
Screenshot from 2023-01-03 15-28-51

Screenshot from 2023-01-03 15-30-06

Screenshot from 2022-12-29 14-46-47

note:

lane_change

Lane change is not allowed in the area within the red border.
I print out information of path and the size of points of path is zero in lane_following.

Expected behavior

The node of behavior_path_planner shall not die in any conditions of lanes and target.

Actual behavior

The node of behavior_path_planner dies in some conditions of lanes and target.

Steps to reproduce

1.Start autoware planning simulator;
2. Set initial position
3. Set target in the change lane(there are more than two lanes and the distance of lane change shall is not enough)

Versions

1.OS: Ubuntun 20.04
2.ROS2: Galactic
3.Autoware: Autoware.universe:main

Possible causes

No response

Additional context

No response

@shulanbushangshu shulanbushangshu changed the title The node of behavior_path_planner dies in some conditions. The node of behavior_path_planner dies in some conditions Jan 3, 2023
@zulfaqar-azmi-t4 zulfaqar-azmi-t4 self-assigned this Jan 4, 2023
@zulfaqar-azmi-t4 zulfaqar-azmi-t4 added the type:bug Software flaws or errors. label Jan 4, 2023
@zulfaqar-azmi-t4
Copy link
Contributor

Hi @shulanbushangshu
Thank you very much for the report.
The bug probably is related to the #2473

There is a bit delay due to some circumstances, but I'll try fix it as soon as possible.

@zulfaqar-azmi-t4
Copy link
Contributor

@shulanbushangshu
Can you help to confirm whether #2615 solve this issue ?
thank you very much in advance.

@shulanbushangshu
Copy link
Contributor Author

@zulfaqar-azmi-t4
I change the codes with #2615 and finish the simulation.

case1:
Screenshot from 2023-01-10 14-22-43

case2:
I set the target in the third lane and the distance of lane change shall is not enough.
Screenshot from 2023-01-10 14-22-59

The node of behavior_path_planner still died.

@zulfaqar-azmi-t4
Copy link
Contributor

@shulanbushangshu
Now I understand. Thank you very much.

@zulfaqar-azmi-t4
Copy link
Contributor

zulfaqar-azmi-t4 commented Jan 11, 2023

@shulanbushangshu
Is this the latest commit in the upstream?
I couldn't reproduce the error, therefore, could you share to me the lanelet map file?

@stale
Copy link

stale bot commented Mar 12, 2023

This pull request has been automatically marked as stale because it has not had recent activity.

@stale stale bot added the status:stale Inactive or outdated issues. (auto-assigned) label Mar 12, 2023
@zulfaqar-azmi-t4
Copy link
Contributor

@shulanbushangsh
is there any update regarding this issue?
If not, I might close the thread.

@stale stale bot removed the status:stale Inactive or outdated issues. (auto-assigned) label Mar 14, 2023
@shulanbushangshu
Copy link
Contributor Author

@zulfaqar-azmi-t4
The lanelet2_map:
lanelet2_map.zip

The position of testing lane:
Screenshot from 2023-03-24 16-25-17

@shulanbushangshu
Copy link
Contributor Author

I test the issue in the autoware of humble.There is still problem and the test is as follows:
Screenshot from 2023-04-07 13-32-17
Screenshot from 2023-04-07 13-32-03
I have updated the pr

@shulanbushangshu
Copy link
Contributor Author

It is fixed in the newest code. I close the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Software flaws or errors.
Projects
None yet
Development

No branches or pull requests

2 participants