batchplan 0.5: tool paths, blended motions and a ROS 2 demo
Overview
batchplan version 0.5 is released, adding support for tool paths, pick-and-place operations, blended motions, and live replanning to the core library. The batchplan-ros package now supports Cartesian paths and blended motion sequences on Lyrical and Jazzy ROS distributions. A demonstration example shows the system attempting multiple grasps in a single request, selecting the shortest path, and approaching the object in a straight line. The demo runs on simulated hardware with an optional MoveIt plugin and can be accessed via a browser interface after cloning the repository and running the provided commands.
Generated from attributed reports · Updated 1 hours ago
Event evidence and corrections
0 attributed source owners. Ownership does not establish independent confirmation. Quantities are reported separately and are never added together.
Environment: simulation
“https://github.com/natsuku-lab/batchplan-ros cd batchplan-ros pixi run demo Open http://localhost:8080 . It runs on simulated hardware, with an optional MoveIt plugin. The GIF shows the core library planning pen paths for 20 simulated UR5e arms in one batch. ROS example · Library”
Exact source · revision 2Source owner not reported
Report timeline
Follow attributed reports and material updates.
- ROS Discourse — Community updatesSignalbatchplan 0.5: tool paths, blended motions and a ROS 2 demo
batchplan version 0.5 is released, adding support for tool paths, pick-and-place operations, blended motions, and live replanning to the core library. The batchplan-ros package now supports Cartesian paths and blended motion sequences on Lyrical and Jazzy ROS distributions. A demonstration example shows the system attempting multiple grasps in a single request, selecting the shortest path, and approaching the object in a straight line. The demo runs on simulated hardware with an optional MoveIt plugin and can be accessed via a browser interface after cloning the repository and running the provided commands.
Event coverage history
There is not enough continuous observation data to show a trend.
Timezone · UTC
Article dates follow your selected timezone. Briefing editions use Hong Kong time (UTC+8).