Backend
Contact-based optimization for collision-free motion planning for a million robots
arXiv cs.RO0 views
arXiv:2610.41548v1 Announce Type: new Abstract: Multi-agent robotic systems have attracted growing interest in recent years, with applications ranging from coordinated drone shows to autonomous operations on land, in the air, and on water. At the planning level, robot motion is often modeled using double-integrator dynamics (with low-level controllers handling the physical dynamics during execution) with a minimum-energy objective subject to collision-avoidance constraints and limits on position, velocity, and acceleration. The complexity of the problem resides in the constraints, which couple the trajectories and make the optimization problem nonconvex. Existing numerical approaches typically discretize and optimize entire trajectories, which becomes expensive for large fleets. We exploit the structure of optimal trajectories by organizing optimization around contacts, at which robots reach the minimum allowed separation. We formulate a coupled algebraic system in contact variables and reconstruct trajectories analytically between contacts. Our algorithm, sequential contact insertion (SCI), starts from unconstrained trajectories, inserts contacts at separation violations, and jointly adjusts their times and states. Numerical experiments demonstrate planning for one million robots in minutes and thousands of robots in fractions of a second. On problems feasible for a fixed-grid sequential convex programming baseline, SCI achieves median speedups of several orders of magnitude at matching solution accuracy.
Source:https://arxiv.org/abs/2610.41548PreviousAC-SMPC: Differentiable Actor--Critic MPC with State Constraints for Safe and Fast Robot NavigationNextA complete analytical characterization of optimal collision-free motion for two robots
Related posts
I Made an AI Birthday Song for My Dad's 70th — Here's What Happened
0dev.to

Following the GitLab Dead Drop: Configuration Changes and C2 History
0dev.to

From Commit Metadata to a Developer Target List
0dev.to

Three Answers to "How Many Coins Should I Test?"
0dev.to

Giving CI your own login? Pull secrets into GitHub Actions with one service token
0dev.to
The Restitution Layer — Or, "We Made Them Whole" Is Not the Same as "They Agree They Are Whole"
0dev.to