Using autoware mpc_follower

asked 2019-12-05 02:42:40 -0500

196 ●37 ●55 ●50

Autoware version : 1.13.0
ROS Version Melodic
Autoware installed from Docker
Docker version 19.03.5, build 633a0ea838

Hello everyone.

After several tests and days using the pure_pursuit follower I would like to see if mpc is suitable for my use. I have no problem using pure_pursuit with op_global_planner, it's working perfect.

But I can't get mpc_follower working at all. I tried to look for documentation here but I can't find anything helpful and google is not helping at all.

Here's the generated trajectory in Rviz : image description

And here's the error message I get :

[ERROR] [1575534953.909298763]: cannot find closest base_waypoints' waypoint to final_waypoints.waypoint[1] !!

And here's what is activated in my computing tab : image description

Do you know what I am doing wrong ?

Thanks a lot for your answers !

answered 2019-12-06 01:51:30 -0500

TakaHoribe
181 ●1 ●8 ●9

By default, the mpc_follower is configured on the assumption that astar_avoid and velocity_set nodes are used, not tested with OpenPlanners.

The error is comming from mpc_waypoint_converter, which generates the /mpc_waypoints (input for mpc) combining /base_waypoints and /final_waypoints.

To run mpc_follower, please try the followings.

comment out here , then the mpc_waypoint_converter is not going to be launched.
remap the topic name of the op_global_planner's output waypoints to /mpc_waypoints so that mpc_follower can read the waypoints directly.

Note: Since mpc applies a smoothing filter to the reference path, it may behave strangely if the path is cut at vehicle position as the attached picture. (A path behind vehicle position is required, and that is the role of mpc_waypoint_converter.) So, It might be better to set false to enable_path_smoothing (you can set from launch file, or runtime_manager GUI with app button).

edit flag offensive delete link

Comments

@TakaHoribe Thanks a lot for your answer ! Maybe I can try to make mpc_follower work while using a* first ?

I am still struggling and it doesn't work at all,

I have enabled this in the computing tab : image

In the first place I am trying to make it work with this tutorial : https://www.lgsvlsimulator.com/docs/a... But I really can't find any documentation on mpc_follower !

Mackou ( 2019-12-10 02:06:33 -0500 )edit

@TakaHoribe I got A* working as an open space planner, but is there any way to make it follow my vector map ?

And also I can't make the mpc_follower work mwith the A* generated waypoints, do you have an idea ? waypoints

Thanks a lot !

Mackou ( 2019-12-10 07:59:05 -0500 )edit

@TakaHoribe

I guess I got closer but mpc is still not driving.

Here's the log output : [ INFO] [1576075515.839709316]: [MPC] MPC is not solved. ref_traj_.size() = 0, my_position_ok_ = 1, my_velocity_ok_ = 0, my_steering_ok_ = 0

And the current status : https://imgur.com/a/sPkYZyI

Mackou ( 2019-12-11 08:55:12 -0500 )edit

@Mackou Following LG sim tutorial, the reference path would be appropriately passed to the mpc_follower.

I guess, the vehicle_status topic is not published to mpc.

ref_traj_.size() = 0, my_position_ok_ = 1, my_velocity_ok_ = 0, my_steering_ok_ = 0

This means, the refecrence path size is zero, and velocity & steering source is not received (thus, mpc doesn't work). About path size, please check the waypoints size which mpc_follower reads (maybe /mpc_trajectory). About the velocity & steering, please confirm /vehicle_status is published (usually, it is published from vehicle interface). If no, you have to generate the /vehicl_status topic with autoware_msgs/VehicleStatus type. The components needed for mpc is just speed (vehicle velocity [km/h]) & angle (steering angle [rad]).

TakaHoribe ( 2019-12-19 03:17:24 -0500 )edit

add a comment

Using autoware mpc_follower

2 Answers

Comments

Question Tools

Stats

Related questions

Using autoware mpc_follower edit

2 Answers

Comments

Question Tools

Stats

Related questions

Using autoware mpc_follower