Implementing a Complete Coverage Path Planner

1,754 views
Skip to first unread message

Spyros Maniatopoulos

unread,
Feb 18, 2016, 7:15:09 PM2/18/16
to ros-sig-navigation
Hello Navigation SIG,

this is my first post. Here goes.

I'm in the (very) early stages of implementing a global planner for complete coverage of a (known) map. Quite a few people have shown interest in this capability [1-3] but I don't think anything was ever implemented (I could only find [4] from ~2012). Btw, when I say coverage I mean by the robot's footprint, not a laser/sonar sensor; think a Roomba vacuuming the floor.

In terms of the algorithm, I'm thinking Complete Coverage D* [5] or Wavefront-based Coverage [6]. Regardless of the specific algorithm though, I'm writing to ask for your advice on how to best implement it such that it fits the plugin-based philosophy of the nav stack and David Lu's layered costmaps (if appropriate). I've thought of three approaches:

  1. Implement the algorithm as a global planner plugin that would plan over the (inflated) static map. Then follow the path using, e.g., DWA and replan (globally) if necessary. Keep track of (actual) coverage in a separate grid-like data structure. This is most intuitive for me, but doesn't feel very ROS-like.
  2. Implement a Costmap 2D layer that corresponds to coverage. Then implement a global planner plugin such that it plans over a master costmap that includes this new coverage layer. The coverage layer gets updated not based on sensor data but instead based on the robot's pose/footprint. The local planner may also take the coverage layer into account in order to avoid unnecessary overlap.
  3. Implement a Costmap 2D layer that corresponds to coverage in such a way that an existing global planner, e.g., A*, can be configured [7] such that the resulting robot behavior is that of complete coverage. The rest would be more or less like approach (2) above. If this sounds handwavy it's because it is. I'm not familiar enough with the technical details of the nav stack to say whether it makes sense or not. Hence my posting here.
Did any of that make sense? I'm looking forward to your thoughts.

Thanks a lot for your time :-)

Best,
Spyros


Disclosure: I'm developing this coverage path planner as part of an internship at a robotics startup. I would personally love to open-source it, but I'm not sure my employer will agree.

David Lu!!

unread,
Mar 2, 2016, 10:40:43 PM3/2/16
to ros-sig-n...@googlegroups.com
I think the first solution is fine. Ultimately it comes down to what
you're optimizing (besides coverage). If its more important that you
never revisit particular locations, then it might make sense to put
the coverage in the costmap. However, if you're optimizing over
time/distance, then I'd imaging that your planning algorithm would
already take into account where the robot has already been, and
wouldn't need to track that in the costmap.
> --
> You received this message because you are subscribed to the Google Groups
> "ros-sig-navigation" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ros-sig-navigat...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Damien

unread,
Sep 29, 2017, 5:46:11 AM9/29/17
to ros-sig-navigation
Hi all, 
This thread is more than a year old... But I have the same necesity: a complete coverage algorithm based on an existing map generated by SLAM...
Spyros, did you achieve a good implementation of your algorithm? Any video of the real robot ?
Is it available open source? 
Thanks !
Damien

Spyros Maniatopoulos

unread,
Sep 30, 2017, 1:30:13 PM9/30/17
to ros-sig-navigation
Damien, unfortunately I can't say much about my implementation because it was done while working for a company (under NDA, etc.)

But search through ROS Answers; there are some good starting points like: https://answers.ros.org/question/212614/complete-coverage-path-planning-ros
Reply all
Reply to author
Forward
0 new messages