Reducing the Barrier to Entry of Complex Robotic Software: a MoveIt! Case Study

TL;DR

This paper presents best practices and a case study on reducing entry barriers in the MoveIt! robotic software framework, making it easier for users to configure, customize, and deploy robotic motion planning functionalities.

Contribution

It introduces a graphical configuration interface, standardized robot models, and plugin architecture to lower entry barriers in MoveIt! and provides design principles applicable to other robotic software.

Findings

Increased user adoption and ease of setup demonstrated by usage statistics.

Positive user survey feedback on configurability and usability.

Effective automation of configuration and optimization processes.

Abstract

Developing robot agnostic software frameworks involves synthesizing the disparate fields of robotic theory and software engineering while simultaneously accounting for a large variability in hardware designs and control paradigms. As the capabilities of robotic software frameworks increase, the setup difficulty and learning curve for new users also increase. If the entry barriers for configuring and using the software on robots is too high, even the most powerful of frameworks are useless. A growing need exists in robotic software engineering to aid users in getting started with, and customizing, the software framework as necessary for particular robotic applications. In this paper a case study is presented for the best practices found for lowering the barrier of entry in the MoveIt! framework, an open-source tool for mobile manipulation in ROS, that allows users to 1) quickly get basic motion planning functionality with minimal initial setup, 2) automate its configuration and optimization, and 3) easily customize its components. A graphical interface that assists the user in configuring MoveIt! is the cornerstone of our approach, coupled with the use of an existing standardized robot model for input, automatically generated robot-specific configuration files, and a plugin-based architecture for extensibility. These best practices are summarized into a set of barrier to entry design principles applicable to other robotic software. The approaches for lowering the entry barrier are evaluated by usage statistics, a user survey, and compared against our design objectives for their effectiveness to users.