Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Revision history [back]

It looks like trajectoy_planner.cpp implements the basic planning functionality, while trajectory_planner_ros.cpp provides the ROS API/communication part (publishers, subscribers etc.). This way of splitting functionality has the advantage that the planning part can be re-used more easily.

ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.