All, thanks for the input so far, keep it coming!
A few comments.
1) I plan to create a github.com repo for this (hopefully under github.com/ros2 namepace, working on that), and will start capturing the wish list items and requirements, as well as documenting design decisions, etc. This thread is just the primer for that.
2) The many different types of maps requested, to me means we need a more abstract data type for maps, that can represent many different types of maps that might be inputs to the system. I'm not sure what that will be exactly yet, but to me, this illustrates that we need to decouple the map type as much as possible from the system.
3) I also agree on the use of ROS2 nodes for the low level plug-ins like global and local planning. That will improve decoupling and make it easier to replace those components with other algorithms, and will also ease the debug effort as pointed out before. We can do this using shared memory pointer passing so that the performance overhead is small.
Keep the feedback coming!
---
[Visit Topic](
https://discourse.ros.org/t/ros2-navigation-input-requested/4884/14) or reply to this email to respond.
If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <
http://lists.ros.org/mailman//options/ros-users>
(text/plain)