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 behavior_path_planner can not plan the right path in some positions as the target #2310

Closed
3 tasks done
shulanbushangshu opened this issue Nov 17, 2022 · 5 comments
Closed
3 tasks done
Labels
component:planning Route planning, decision-making, and navigation. (auto-assigned) status:stale Inactive or outdated issues. (auto-assigned) type:bug Software flaws or errors.

Comments

@shulanbushangshu
Copy link
Contributor

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

When I set the different positions of target in the lane,the behavior_path_planner can not plan the right path in some positions.
case 1:

lane_follow_normal

case 2:

Screenshot from 2022-11-16 16-27-25

case 3:
Screenshot from 2022-11-17 14-35-22

case 4:

Screenshot from 2022-11-17 14-37-25

Expected behavior

The behavior_path_planner shall plan the right path in all positions of the lanes.

Actual behavior

The behavior_path_planner can not plan the right path when I set some different positions as the target in the lanes.

Steps to reproduce

1.Start autoware planning simulator;
2. Set initial position
3. Set target in the different positions in the lane(far from the initial position)

Versions

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

Possible causes

No response

Additional context

No response

@takayuki5168 takayuki5168 added the component:planning Route planning, decision-making, and navigation. (auto-assigned) label Nov 17, 2022
@ismetatabay
Copy link
Member

Hi, can you please share map (pcd and lanelet) files? The lanelets which highlighted as I have shown below picture show that the route has been successfully generated by the mission_planner, I didn't see any problem in this case. If you're worried about not seeing the green path in rviz, the path will move forward as the vehicle move. The parameter that is forward_path_length limits the path . You can also increase the generated path by changing this parameter.

Selection_013

@shulanbushangshu
Copy link
Contributor Author

shulanbushangshu commented Nov 18, 2022

@ismetatabay As you say, the route has been successfully generated by the mission_planner.Yes,I get what you mean.The distance from the target is more than 300m.But the problem is that final path of the behavior_path_planner is short(I print the size of the path and it shows that there are just 8 points in the path)

@shulanbushangshu
Copy link
Contributor Author

@ismetatabay I test the code and show the information about the path of behavior_path_planner as below:

case1:

Screenshot from 2022-11-18 12-55-42

case 2:

Screenshot from 2022-11-18 12-56-37

@ismetatabay
Copy link
Member

@shulanbushangshu This is weird thing that it shouldn't happen. At this case, if forward_path_length is 300m and backward_path_length is 5m, the number of path points created should be approximately 305/2 ≅152. To see if this situation is related to distance goal distance , I modified the sample .osm file of autoware as in the image below.

I've tried many different scenarios but haven't run into a problem. As expected, if the distance to the goal was greater than 300 meters, approximately 152 path points were generated on bpp.

Is it possible for you to share the lanelet2 .osm file?

Selection_015

@stale
Copy link

stale bot commented Jan 17, 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 Jan 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component:planning Route planning, decision-making, and navigation. (auto-assigned) status:stale Inactive or outdated issues. (auto-assigned) type:bug Software flaws or errors.
Projects
None yet
Development

No branches or pull requests

4 participants