autowarefoundation / autoware.universe

https://autowarefoundation.github.io/autoware.universe/
Apache License 2.0
958 stars 624 forks source link

The lane_following can not operate normally in some conditions #2633

Open shulanbushangshu opened 1 year ago

shulanbushangshu commented 1 year ago

Checklist

Description

When I use the map to do simulation about lane_following, there are three cases.

case1: Screenshot from 2023-01-10 13-14-00

case2: Screenshot from 2023-01-10 13-16-53

case3: Screenshot from 2023-01-10 14-50-24

In the case1 and case3,the mode can work normally.But in the case2,the mode is unable to operate normally.

Expected behavior

In the conditions of case2,the lane_following is unable to operate normally.

Actual behavior

In the conditions of case2,the lane_following is unable to operate normally.

Steps to reproduce

1.Use the map of demo and start autoware planning simulator;

  1. Set initial position in the lane of 34976
  2. Set target in the lane of 35016

Versions

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

Possible causes

In the path based on sampling distance by parameters,there is the lane which connects to the start lane.

Additional context

No response

zulfaqar-azmi-t4 commented 1 year ago

@shulanbushangshu This PR https://github.com/autowarefoundation/autoware.universe/pull/2648 might interest you.

shulanbushangshu commented 1 year ago

@zulfaqar-azmi-t4 @purewater0901 . I use the newest code to do the simulation.The result is shown as below:

In the start position:

Screenshot from 2023-01-16 17-45-56

When the car travels a certain distance:

Screenshot from 2023-01-16 17-46-40

Could you help me to confirm it?

mitsudome-r commented 1 year ago

@shulanbushangshu Could you explain what you mean by "not operating normally"? Is it not engaging?

shulanbushangshu commented 1 year ago

@mitsudome-r .I test the new code after the pr https://github.com/autowarefoundation/autoware.universe/pull/2648 and the result is that the path can not get the target lane as below shown: Screenshot from 2023-01-16 17-46-40

purewater0901 commented 1 year ago

@shulanbushangshu Thank you for your reporting. I also encountered the same issue, but this problem is not related to this PR. I think the root cause of the problem comes from either Lanelet library or the route handler. The route handler(or Lanelet library) gives incorrect Lanelet sequences.

purewater0901 commented 1 year ago

It seems this funciton chooses wrong lanelet in this case

shulanbushangshu commented 1 year ago

@purewater0901 @mitsudome-r Yes,this problem is not related to https://github.com/autowarefoundation/autoware.universe/pull/2648. The function of getNextLaneletWithinRoute() has no judgement when chose the next lane. Screenshot from 2023-01-18 12-46-21

purewater0901 commented 1 year ago

@shulanbushangshu Yes, when you make a "half-looped" route, it won't work correctly. In order to fix this problem, we have to re-design the route handler.

stale[bot] commented 1 year ago

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

stale[bot] commented 10 months ago

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