[Autoware] Lidar fake perception
Hi all,
Setup: - Ubuntu 16.04 - Ros Kinetic - Autoware - Docker
I am trying to use the lidarfakeperception node in Autoware, so basically reproduce the two following videos: https://gitlab.com/autowarefoundation/autoware.ai/core_perception/tree/master/lidar_fake_perception
The goal here is to create a 'fake' point cloud in front of the vehicle and the expected behavior would be to see a change in the topic /twist_cmd and eventually see the vehicle stop.
However, I can barely find any information about this node. The above link is the README.md from Gitlab but I find it difficult understanding how to use the node with this information only. More precisely:
1 - Does the parameter input points (topic /points_raw) need to be published by another node or can I just skip it ? What if the only point cloud I want to visualize is the fake object ? I don't care about other objects. I would like to have only one object in the middle of the path.
2 - Same question for the parameter input objects (topic /detected_objects)
3 - How do I create initial pose (topic /movebasesimple/goal) and input twist (topic /fake_twist) ? So far I just publish them from a terminal.
4 - What other nodes need to be launched ? So far what I am launching is the following: - point cloup map loader - tf loader - waypointloader - lanerule - laneselect - wfsimulator - velposeconnect - latticevelocityset - pathselect - purepursuit - twistfilter - Manually publish /movebasesimple/goal - Manually publish /faketwist
However, the only think I see is: - The vehicle following the path and publish /twistcmd as expect when using wfsimulator - The topic /fake points is published but /fakepoints.data = [] - In RVIZ when I add the topic /fakepoint [Type = PointCloud2] I get the error: Status: Error Transform [sender=unknown_publisher]
Anyone who already used this node ?
Thanks a lot :-)
Asked by Doug on 2019-08-27 14:56:15 UTC
Answers
1, It is not a must.
2, It is not a must
3, Not the scope of Autoware. Please check this document for /move_base_simple/goal http://wiki.ros.org/navigation/Tutorials/Using%20rviz%20with%20the%20Navigation%20Stackj
4, You need to set output_frame
to sim_lidar
in app for lidar_fake_perception.
Asked by kosuke_murakami on 2019-08-28 19:25:33 UTC
Comments
I see, thanks for the prompt answer. It helps a lot. I am getting this error now though: [ INFO] [1567104827.129211216]: no candidate. search closest waypoint from all waypoints...
I saw the question has already been asked a a month ago but no answer ... (https://answers.ros.org/question/328933/autoware-1120-astar_avoid-cant-correct-closest-waypoint-in-some-cases/)
Any idea where this comes from ?
Probably from velocity_set. Indeed, the topic /obstacle_waypoint is always set to -1, indicating no obstacle is detected. This is weird though because the lidar_fake_detection seems to be working as well as the /imm_ukf_pda_track, /naive_motion_predict and /costmap_generator
Asked by Doug on 2019-08-29 13:57:56 UTC
I also met this question. How can I manually publish /fake_twist?Please explain it in detail. Thank you.
Asked by slipper on 2021-02-23 21:49:57 UTC
@slipper in RViz:
Panels -> Add New Panel -> rviz_plugin_tutorials -> Teleop
In a new panel write /fake_twist
as an Output Topic.
Asked by anonymous62924 on 2021-02-26 09:00:07 UTC
Thank you for your reply. I check the rviz panel again. I don't find the panel named "rviz_plugin_tutorials" by running autoware in docker. But I can see the "rviz_plugin_tutorials" by running command(roscore and rviz). How to locate this problem?
Asked by slipper on 2021-03-08 02:38:26 UTC
Comments