-
Notifications
You must be signed in to change notification settings - Fork 51
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
Porting autoware_motion_velocity_obstacle_stop_module from autoware.universe to autoware.core #226
Comments
I will work on these dependencies if no one else is assigned. cc @mitsudome-r @xmfcx @youtalk @liuXinGangChina
If autoware_planning_factor_interface needs to be ported to autoware.core, maybe type substitution should be done in autoware.universe as there are quite a lot of packages that depend on autoware_planning_factor_interface as shown below.
|
Hello Mits san @mitsudome-r I look into the dependency graph,find that if we follow the porting rule in this file , we should move autoware_planning_factor_interface first, but i didn‘t find it in the porting task list。 Can you check with the planning team whether this package “autoware_planning_factor_interface” is in the porting plan If it is, we will port autoware_planning_factor_interface first At the mean time, we are working on porting the msg first Best regards 心刚 |
Already got confirmation from mits san, go go go! @NorahXiong |
Already done. autowarefoundation/autoware_internal_msgs#52 |
autowarefoundation/autoware.universe#10204 autoware_planning_factor_interface waiting for review |
Checklist
Description
As part of Autoware Core implementation activity discussed in this thread, I will be porting autoware_test_utils from Autoware Universe to Autoware Core.
Purpose
Port autoware_motion_velocity_obstacle_stop_module from Autoware Universe to Autoware Core.
Possible approaches
Fix bugs if detected. Deal dependence problems related to autoware_motion_velocity_obstacle_stop_module if detected.
Definition of done
The text was updated successfully, but these errors were encountered: