Closed Kim-mins closed 5 months ago
Hi @Kim-mins Sorry for late reply.
I saw attached video and thought the lanelet structure was weird. I tried to open your map but I couldn't. If possible, could you attach your lanelet2_map.osm?
No problem! thank you for the response @satoshi-ota!
Here's the map I'm using now: [lanelet2_map] Actually, I think it is not different with the map above, since I downloaded it from there..
I guess you have a problem on loading lanelet2 map on Vector Map Builder with the message below:
I'm also suffering the issue on loading the lanelet2 map, and as far as I know, JOSM is the only way to open the map.
Thank you!
Hi @Kim-mins I could reproduce your report things.
But unfortunatelly, threre is obiously a issue on your map. The right and left bound of lanelet (ID:7419) collides each other.
If you want to create merging lane, it's better to create lanelet like this.
Thank you for the response and the investigation @satoshi-ota!
I should have noticed there have to be the right bound.. sorry for bothering you.
After reading your response, I got two questions regarding the issue.
1. Question on Autoware At first I thought this was a bug because I thought that, if routing was successful, Autoware could reach to the destination successfully (if there's no effect from surroundings), but it wasn't. Could you please share your opinion on this? I agree that using bad lanelet2 map is more problematic, but I wonder if Autoware could emit routing failure beforehand.
2. Question on lanelet2 map generation Do you know any proper tool for generating lanelet2(.osm) from opendrive file(.xodr)? I've heard about the tools assuremappingtools and commonroad-scenario-designer, but I failed to run the former, and the latter does not generate the complete map(the generated map looks nice, but some errors here. Autoware does not work well with the map.). So, if you have any experience on generating lanelet2 file from opendrive file for Autoware, could you please share the tool for me? Or if you successfully converted the map by using the two tools above, I want to ask you if you can share your experience.
Thanks a lot!
At first I thought this was a bug because I thought that, if routing was successful, Autoware could reach to the destination successfully (if there's no effect from surroundings), but it wasn't. Could you please share your opinion on this? I agree that using bad lanelet2 map is more problematic, but I wonder if Autoware could emit routing failure beforehand.
Thanks for your comment. I guess we can validate the map and prevent output such a wierd output. In my opinion, we should validate the map when we create it instead of adding some feature in autoware. What do you think? Actually, we TIER IV develop several validator for VMB and I think you can propose these kind of feature for map team if you want. (In that case, please open another discussion or issues.)
Do you know any proper tool for generating lanelet2(.osm) from opendrive file(.xodr)? I've heard about the tools assuremappingtools and commonroad-scenario-designer, but I failed to run the former, and the latter does not generate the complete map(the generated map looks nice, but some errors here. Autoware does not work well with the map.). So, if you have any experience on generating lanelet2 file from opendrive file for Autoware, could you please share the tool for me? Or if you successfully converted the map by using the two tools above, I want to ask you if you can share your experience.
Sorry. I don't know...
Thank you for the response @satoshi-ota!
I agree to your point. Just validating the map in offline seems better since there would be no problem if the map is validated once. So, as you mentioned, the validation during the running seems not a good idea.
I'll close this issue soon.
Thank you!
Checklist
Description
Hi team,
I'm currently running Autoware with prebuilt docker(version 20240115), and I found that a weird drivable area is generated for the merging lane, and it makes the ego vehicle stop forever.
Here's the [rviz video] and [launch.log] files.
From the start of the rviz video, we can check that the shape of a drivable area is weird, and it gets worse as the vehicle tries to merge.
Expected behavior
I think Autoware should drive to the destination if the routing was successful.
Actual behavior
But Autoware fails to reach to the destination, even though the routing was successful.
Steps to reproduce
Versions
Possible causes
Sorry, I have no idea on this, but I assure that this issue is a special case, since I've seen Autoware worked well on the other maps with merging lanes(e.g., Town04).
Additional context
No response