Try it: the model proposes, you decide
A miniature of the stance the system is built on: the robots do not move until a person approves the plan.
Expressive behaviors were hand engineered for one scenario and could not travel to another.
Counterbalanced within subjects study comparing two ways of authoring, with think aloud, workload and usability measures, and interviews.
Full paper under review. Described in general terms here while review runs.
System
Novices author the motions themselves, either by sketching the path they want or by demonstrating the motion physically. A language model composes those motions into a plan for a scenario described in plain English, and the person reviews and edits that plan before any robot moves.
My role
I built this end to end: the robots and their electronics, the localization and the control server that drives them, both authoring interfaces, and the planning and validation layer behind them. The interface work was as much of the problem as the hardware: it has to be usable by someone who has never programmed a robot, in one sitting, under observation. I designed, ran and analyzed the user study.