-
Notifications
You must be signed in to change notification settings - Fork 91
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
Vehicle init pose: failed to get transform from map to base_link #76
Comments
@fadimee |
My environment is Japan Tokyo Nishishinjuku in the Quick Start Demo, that can be seen in the given link below: https://tier4.github.io/AWSIM/GettingStarted/QuickStartDemo/ |
What environment means is Ubuntu, ROS version and etc. |
I misunderstood |
AWSIM v1.0.1 is for Ubuntu 20, ROS2 Galactic version. |
@fadimee Could you share your log of Autoware from the start to error part? |
@shmpwk
|
@fadimee
Autoware will not perform initial position estimation unless the vehicle has been stopped for at least 3 seconds. |
@shmpwk
I am not sure you noticed beacuse I didnt mentioned about it in my previous posts, I want to remind the map on autoware is not aligned correctly. You can see in picture below. I think that is the reason of issue. But I am not sure why it is not aligned and how I can fix it. |
I couldn't figure out the cause of the problem from that log. As for the map, you first use AWSIM v1.0.1 but the map is different between that and v1.1.0 (or the latest version). |
I've checked the latest map and found something wrong with it. [edit] |
|
FYI this issue might be related to this. |
@isouf |
@shmpwk thank you for the prompt response. I can set the initial pose by changing the resolution of my screen. However, this was not always working as expected. Following some further investigation I found a more efficient solution. Essentially, when I launch the docker image I pass rocker --nvidia --x11 --user --privileged --volume $HOME/autoware --volume $HOME/autoware_map -- ghcr.io/autowarefoundation/autoware-universe:humble-latest-cuda This is is now working for the Planning Simulation tutorial, I can set the initial pose without having to change the resolution of my screen. Perhaps this is not so relevant for the AWSIM init pose problem but it might give some pointers on how to resolve this issue. |
@fadimee I could not found the cause of your problem yet.
|
@shmpwk I am also trying to run the AWSIM simulator and I have the same issue. Attaching here the launch.log file. Also, please see below answers to your questions:
Yes.
I am running Autoware and AWSIM from Docker as per #81. I run the Docker container using the following command: rocker --nvidia --x11 --user --privileged --net host --volume $HOME/autoware --volume $HOME/autoware_map --volume $HOME/AWSIM_v1.1.0 -- ghcr.io/autowarefoundation/autoware-universe:humble-latest-awsim-cuda I use the following to run Autoware inside the Docker container: ros2 launch autoware_launch e2e_simulator.launch.xml vehicle_model:=sample_vehicle sensor_model:=awsim_sensor_kit map_path:=$HOME/autoware_map/nishishinjuku_autoware_map
awsim_error-2023-02-15_17.16.44.mp4 |
@isouf |
You can also reffer to the other example of docker launching. |
Thank you @shmpwk. The Looking at the Unrecoverable error (code=500): cuda error: out of memory (code=2) @ /code/src/DeviceBuffer.hpp:127 The
How much memory would you expect to be consumed by AWSIM v1.1.0? |
@isouf
|
@shmpwk |
@yangjiameng |
@shmpwk if [ ! -e /tmp/cycloneDDS_configured ]; then |
What do you mean by breakdown? The simulation is crashed ? FYI, I created AWSIM + docker instruction here |
@shmpwk |
For Ubuntu 20.04, Galactic, you can refer to the v1.0.2 tutorial. This issue thread is for Vehicle init pose: failed to get transform from map to base_link. |
@shmpwk |
@Mufan187569 [edit] |
@shmpwk |
@shmpwk |
@shmpwk |
@yangjiameng @Mufan187569
The latter one is extracted one. source.
If you integrate real vehicle, you can ignore the radar. You can switch not to use radar in Autoware launch file. |
I got almost the same issue. could someone give me some help. log file attached here. |
@zhuyingxiang95 Seems to be solved #129 |
Signed-off-by: Lukasz Chojnacki <lukasz.chojnacki@robotec.ai>
Hello
I am trying to run "Quick Start Demo" on AWSIM. I am encountering a problem about vehicle pose.
Autoware can not find init pose of vehilce and when I try to do it manually by using "2D Pose Estimate" still it doesnt work. Vehicle's init pose on Autoware is very far from map origin.
I shared screenshots and logs below;
Logs;
[motion_velocity_smoother-58] [WARN] [1674567417.778344619] [planning.scenario_planning.motion_velocity_smoother]: failed to get transform from map to base_link: Could not find a connection between 'map' and 'base_link' because they are not part of the same tree.Tf has two or more unconnected trees. [motion_velocity_smoother-58] [INFO] [1674567417.778411542] [planning.scenario_planning.motion_velocity_smoother]: waiting for self pose... [component_container-64] [WARN] [1674567418.757881289] [control.trajectory_follower.lane_departure_checker_node]: failed to get transform from map to base_link: Could not find a connection between 'map' and 'base_link' because they are not part of the same tree.Tf has two or more unconnected trees. [component_container-64] [INFO] [1674567418.757951568] [control.trajectory_follower.lane_departure_checker_node]: waiting for self pose... [component_container-62] [INFO] [1674567421.019612140] [planning.scenario_planning.parking.costmap_generator]: waiting for initial pose... [component_container_mt-61] [WARN] [1674567422.255320688] [planning.scenario_planning.lane_driving.motion_planning.obstacle_avoidance_planner]: failed to get transform from map to base_link: Could not find a connection between 'map' and 'base_link' because they are not part of the same tree.Tf has two or more unconnected trees. [component_container_mt-61] [INFO] [1674567422.255387806] [planning.scenario_planning.lane_driving.motion_planning.obstacle_avoidance_planner]: waiting for self pose...
Screenshots;
How can I solve this problem?
The text was updated successfully, but these errors were encountered: