You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I place the ego car on lane=1718 on the Hsinchu city (Taiwan) map and set the destination point to somewhere on lane=1720 , the ego car will not move during the simulation. And the simulation task failed.
Please see the TW map below, intuitively, according to the map visualization, the lane=1720 and lane=1721 should be reachable from lane=1718 (lane=1720 and lane=1721 are successors of lane=1718).
I also tested this scenario on Tier4 Scenario Editor. It failed too.
To Reproduce
Steps to reproduce the behavior:
Launch Autoware through docker
Run the scenario 1720.yml (at the end of this report), which uses Hsinchu city (Taiwan) map. I downloaded it from here
[openscenario_interpreter_node-3] [INFO] [1714688055.375044352] [simulation.openscenario_interpreter]: InternalError: Requested the service "/api/routing/set_route_points" 1 times, but was unsuccessful.
[scenario_test_runner.py-1] [INFO] [1714688055.379492981] [simulation.scenario_test_runner]: finish execution
See the simulation result log:
<?xml version="1.0"?>
<testsuites name="/tmp/scenario_test_runner" failures="0" errors="1" tests="1">
<testsuite name="1720" failures="0" errors="1" tests="1">
<testcase name="1720_0">
<error type="InternalError" message="Requested the service "/api/routing/set_route_points" 1 times, but was not successful." />
</testcase>
</testsuite>
</testsuites>
Expected behavior
Expect routing to find valid route from lane=1718 to lane=1720
Root Cause
I think the reason behind this bug is:
The end point of lane=1718's left bound != the start point of lane=1720's left bound
The end point of lane=1718's right bound != the start point of lane=1720's right bound
I use your lanelet2 extension python library to get this:
lane=1718 left bound: [id: 1685, inverted point ids: 1688, 1687, 1686, 1684, 1683, 1708, 1699]
lane=1718 right bound: [id: 1679 point ids: 1677, 1678, 1680, 1681, 1717, 1694]
lane=1720 left bound: [id: 1704, inverted point ids: 1708, 1707, 1706, 1705, 1703, 1702, 1656]
lane=1720 right bound: [id: 1711, inverted point ids: 1717, 1716, 1715, 1714, 1713, 1712, 1710, 1709, 1658]
I tried to add point=1699 to lane=1720's left bound, and point=1694 to lane=1720's right bound. The modified version is like this:
And I did the simulation again, it worked. The ego car can depart from lane=1718 and arrive at lane=1720:
Desktop (please complete the following information):
Describe the bug
When I place the ego car on lane=1718 on the Hsinchu city (Taiwan) map and set the destination point to somewhere on lane=1720 , the ego car will not move during the simulation. And the simulation task failed.
Please see the TW map below, intuitively, according to the map visualization, the lane=1720 and lane=1721 should be reachable from lane=1718 (lane=1720 and lane=1721 are successors of lane=1718).
I also tested this scenario on Tier4 Scenario Editor. It failed too.
To Reproduce
Steps to reproduce the behavior:
1720.yml
(at the end of this report), which usesHsinchu city (Taiwan)
map. I downloaded it from here[openscenario_interpreter_node-3] [INFO] [1714688055.375044352] [simulation.openscenario_interpreter]: InternalError: Requested the service "/api/routing/set_route_points" 1 times, but was unsuccessful. [scenario_test_runner.py-1] [INFO] [1714688055.379492981] [simulation.scenario_test_runner]: finish execution
Expected behavior
Expect routing to find valid route from lane=1718 to lane=1720
Root Cause
I think the reason behind this bug is:
I use your lanelet2 extension python library to get this:
I tried to add point=1699 to lane=1720's left bound, and point=1694 to lane=1720's right bound. The modified version is like this:
And I did the simulation again, it worked. The ego car can depart from lane=1718 and arrive at lane=1720:
Desktop (please complete the following information):
Scenario file
The text was updated successfully, but these errors were encountered: