What Makes a Good Symbol for Hybrid Discrete-Continuous Planning?
Organizations: Robotics Institute, Carnegie Mellon University · University of Pennsylvania
Abstract
The physical world has continuous state and action spaces, yet robot planning often benefits from hybrid discrete-continuous formulations that explicitly expose combinatorial structure, such as contact modes or discrete primitive actions. Existing methods typically rely on human-defined symbol sets or symbols derived from language supervision, without asking what makes a symbol computationally useful. In this paper, we take an inference-algorithm--centric view to define usefulness: a good symbol should expose the discrete commitments that simplify solving the original planning problem. We first introduce the concept of solver-sufficient symbolization by studying finite-horizon piecewise-affine systems, for which solver sufficiency can be precisely characterized, and develop a counterexample-guided algorithm for symbol invention. We then extend this principle to invent symbols for optimization objectives parameterized by general neural networks as energy functions, showing that solver-sufficient symbols can nevertheless be induced from their continuous optimization landscapes. Experiments on simulated and real-robot tasks show that the resulting symbols reduce solving cost while preserving solution quality, while also improving interpretability and steerability. Furthermore, our theoretical and algorithmic insights help explain why certain human-defined symbols are computationally useful.
Figures & tables
| Method | 2D Manipulation | In-Hand Reorientation | ||||||||||
| MPushT | Hook | Shelf | Block | Cuboid | Pen | |||||||
| SR | IS | SR | IS | SR | IS | SR | IS | SR | IS | SR | IS | |
| - Solver-Oriented Methods | ||||||||||||
| CoCo | ||||||||||||
| GBD-MPC | ||||||||||||
| - Symbol-Oriented Methods | ||||||||||||
| Method | Avoiding | Pushing | Aligning | Sorting | Matching | |||||
| SR | DC | SR | DC | SR | DC | SR | DC | SR | DC | |
| DDPM | ||||||||||
| ACT | ||||||||||
| BESO | ||||||||||
| IBC | ||||||||||
| BeT | ||||||||||
| Task | Ours | PGS | pix2pred |
| MPushT | is clockwise push is push above | T orientation threshold near the goal | stem_pointing_down_right rotation_error_small |
| Block | index finger contacts object thumb contacts palm | index finger near thumb control variable threshold | orientation_over_bound orientation_southeast |
Appendix figures & tables8 assets
Supplementary material from the paper’s appendix.
Appendix
| Task | Factors | Semantics |
| MPushT | , push along ; cumulative runs | |
| , push along at | ||
| , push along from to | ||
| , push along at and along | ||
| , push along at | ||
| , push along from to |
| Task | Factors | Semantics |
| Block | active finger: ff, mf, rf, lf, or th | |
| admissible finger–face assignment | ||
| contacted face: palm-facing, dorsal, thumb-side, little-side, distal, or proximal | ||
| idle unit, allowing only two active finger contacts | ||
| Cuboid | same finger, finger–face, face, and idle-factor semantics as Block ; contact feasibility follows the cuboid geometry | |
| Pen | active finger group: opposition, medial, or ulnar |
| Form. | Factors | Semantics |
|---|---|---|
| : push at , extend leftward to , or move to | ||
| single pushes on at | ||
| : push at or move to | ||
| : push at or extend to | ||
| one occupancy bit per face , pushing at its innermost contact point | ||
| push from the top, bottom, right, or left side |
Symbolic Planning
Symbolic planning represents goals, states, and actions explicitly, then searches for action sequences that satisfy constraints.
See all 89 papers