Flow Motion Policy: Manipulator Motion Planning with Flow Matching Models

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2604.07084v2 Announce Type: replace-cross Abstract: Open-loop end-to-end neural motion planners have recently been proposed to improve motion planning for robotic manipulators. These methods enable planning directly from sensor observations without relying on a privileged collision checker during motion planning. However, existing planners produce a single path for a given planning problem and cannot exploit their open-loop nature to propose multiple motion plans. To address this limitation, we introduce Flow Motion Policy, an open-loop neural motion planner that uses flow matching to generate a batch of motion plan proposals by learning a distribution over motion plans conditioned on the planning observation. At inference time, it samples multiple candidate motion plans to enable efficient best-of-$N$ inference while avoiding iterative collision checking during planning. We benchmark the Flow Motion Policy against representative sampling-based, optimization-based and neural motion planning methods. Evaluation results demonstrate that Flow Motion Policy improves planning success and efficiency, highlighting the effectiveness of stochastic generative policies for end-to-end motion planning and best-of-$N$ sampling. Project website: \href{https://davoodsz.github.io/FlowMotionPolicy.github.io/}{https://davoodsz.github.io/FlowMotionPolicy.github.io/}

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2604.07084
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.