Revision history [back]

I'm not aware of such a document, or at least not a single one.

It's likely the fact these two frameworks have been developed mostly independently is a factor in this, and there hasn't been anyone (or at least, I don't know of anyone) who's taken the time to first analyse and then write down the results of such an analysis for those two specific pieces of software.

The overlap has been recognised previously though, especially with the addition of the concept of local and global planners to MoveIt (a current project) and the desire to use MoveIt together with the navigation stack for whole-body control.

navigation.ros.org hosts the main documentation on Nav2, but it doesn't appear to include design documentation or analyses. moveit.ros.org also doesn't have something like that (although it has the Concepts page). There are pieces of what you could consider (the start of) design documentation, but it's not made explicit.

In the end, Nav 2 is the second version of the ROS 1 nav stack (with many, many changes), while MoveIt is a continuation/rewrite of arm_navigation.

I wasn't involved at all in any of those, but looking at it now, the use cases for those two precursors were just not so close/related as they appear now. That could be one explanation for why the apparent overlap is not exploited more.

In earlier discussions, IIRC, developers and maintainers of both software stacks have expressed a desire to see whether that overlap could be used better, but I don't believe it's currently a high-priority item on the TODO.

I'm not aware of such a document, or at least not a single one.

It's likely the fact these two frameworks have been developed mostly independently is a factor in this, and there hasn't been anyone (or at least, I don't know of anyone) who's taken the time to first analyse and then write down the results of such an analysis for those two specific pieces of software.

The overlap has been recognised previously though, especially with the addition of the concept of local and global planners to MoveIt (a current project) and the desire to use MoveIt together with the navigation stack for whole-body control.

navigation.ros.org hosts the main documentation on Nav2, but it doesn't appear to include design documentation or analyses. moveit.ros.org also doesn't have something like that (although it has the Concepts page). There are pieces of what you could consider (the start of) design documentation, but it's not made explicit.

In the end, Nav 2 is the second version of the ROS 1 nav stack (with many, many changes), while MoveIt is a continuation/rewrite of arm_navigation.

I wasn't involved at all in any of those, but looking at it now, the use cases for those two precursors were just not so close/related as they appear now. That could be one explanation for why the apparent overlap is not exploited more.

In earlier discussions, IIRC, developers and maintainers of both software stacks have expressed a desire to see whether that overlap could be used better, but I don't believe it's currently a high-priority item on the TODO.