Hierarchical Object-Oriented POMDP Planning for Object Rearrangement

Rajesh Mangananvar             Alan Fern             Prasad Tadepalli            

Oregon State University Logo

Hierarchical planning framework for real-world robotic rearrangement: jointly optimizing exploration and manipulation to achieve 50-70% object success with only 60% detector realiability

Abstract

We present an online planning approach and a new benchmark dataset for solving multi-object rearrangement problems in partially observable, multi-room environments. Current object rearrangement solutions, primarily based on Reinforcement Learning or hand-coded planning methods, often lack adaptability to diverse challenges. To address this limitation, we propose a Hierarchical Object-Oriented Partially Observed Markov Decision Process (HOO-POMDP) planner that leverages object-factored belief representations for efficient multi-object rearrangement. This approach comprises of (a) an object-oriented POMDP planner generating sub-goals, (b) a set of low-level policies for sub-goal achievement, and (c) an abstraction system converting the continuous low-level world into a representation suitable for abstract planning. To enable rigorous evaluation, we introduce MultiRoomR, a comprehensive benchmark featuring diverse multi-room environments with varying degrees of partial observability (10-30% initial visibility), blocked paths, obstructed goals, and multiple objects (10-20) distributed across 2-4 rooms. Experiments demonstrate that our system effectively handles these complex scenarios while maintaining robust performance even with imperfect perception.

Interactive: Multi-Object Rearrangement Scenario

Hover over objects and paths to explore spatial dependencies. In this scene, the robot must determine the optimal order to move objects to their goals.

HOO-POMDP Multi-room Rearrangement Example
Path Colors
Object 1 & 2 Object 4 Object 6 Shared corridor Object 3 (blocked) Goal location
HOO-POMDP Computed Optimal Sequence
1. Move Obj 3 2. Move Obj 2 3. Move Obj 1 4. Others...
Object 3 blocks Object 1's goal. Object 2 blocks the corridor. Moving them first enables efficient completion.

Hover over numbered objects to see their dependencies and blocking relationships.

Why POMDPs for Rearrangement? [Expand All]


The Problem with Existing Approaches [Expand All]


HOO-POMDP's Key Insight [Expand All]


Method Overview [Expand All]

HOO-POMDP Framework Diagram

Results [Expand All]

Performance Comparison Graphs

Scene Success Rate (%) - RoomR Dataset
0 25 50 75 49% HOOP 10% FHC 0% VRR 8% MSS 48% Oracle
Higher is better. Oracle = Perfect Detector
Object Success Rate (%) - MultiRoomR Dataset
0 25 50 75 65% HOOP 18% FHC 6% VRR 9% MSS 75% Oracle
10-object scenes with blocked paths. Higher is better.
HOO-POMDP Scaling: Performance vs. Problem Complexity
0% 50% 100% Success Rate RoomR (5 obj) Proc (5 obj) MultiR (10 obj) MultiR (15-20) 49% 46% 32% 21% HOO-POMDP Oracle (PD)
Scene Success Rate as problem complexity increases. HOOP maintains strong performance close to Oracle even with more objects.
📊
Key Finding
HOO-POMDP achieves 50-70% object success even with only 60% detector reliability. Baselines (VRR, FHC, MSS) struggle significantly, often achieving 0-10% scene success on complex multi-room scenarios. The small gap between HOO-POMDP and the Oracle demonstrates effective handling of uncertainty.
Table 1 (from paper): Main comparison of HOO-POMDP (HOOP) against Baselines, Ablations, and Oracles across all datasets.
Dataset Objs #BP #Rm #V HOOP (Ours) Baselines Ablation Oracle Settings
HOOP FHC VRR MSS HOOP-HP PK PD
SS↑OS↑TA↓ SS↑OS↑TA↓ SS↑OS↑TA↓ SS↑OS↑TA↓ SS↑OS↑TA↓ SS↑OS↑TA↓ SS↑OS↑TA↓
RoomR5013-4 4971211 3858269 731256 2144267 1333302 6388176 6287189
Proc5022-3 4668352 3261411 219382 1429395 929410 6082203 6081269
Multi RoomR 10022-3 3265710 2044931 013NA 825920 5251029 4178457 4078529
122-3 2149789 1238993 09NA NCNCNC 2191092 3369489 2967587
1003-41-2 30621189 19341345 08NA 014NA 3161408 3975726 3774834
13-41-2 18441321 9261490 05NA NCNCNC 171549 3270789 3170985
1503-42-3 22591228 12311605 09NA 011NA 05NA 3278895 3074921
13-42-3 14411416 7231886 05NA NCNCNC 06NA 2971988 2569965
2003-42-4 17551621 018NA 06NA 09NA 05NA 27751168 27741197
13-42-4 10361786 011NA 04NA NCNCNC 04NA 22701307 20681336
Table 3 (from paper): MCTS search depth ablation. A greedy depth of 1 (HOOP-MCTS 1) fails.
Dataset Objs #BG #Sw #BP #Rm #V HOOP (Depth 12) HOOP-MCTS 1 (Depth 1)
SS↑OSR↑TA↓Time(m)↓ SS↑OSR↑TA↓
RoomR510013-4 49712111.61 826565
Proc51D0022-3 46683523.42 212875
Multi RoomR 1011022-3 32657107.89 07NA
21122-3 21497898.98 03NA

Key Findings from Ablations [Expand All]


Technical Details [Expand All]


Why This Matters [Expand All]

BibTeX


@article{mangannavar2024hierarchical,
  title={Hierarchical Object-Oriented POMDP Planning for Object Rearrangement},
  author={Mangannavar, Rajesh and Fern, Alan and Tadepalli, Prasad},
  journal={arXiv preprint arXiv:2412.01348},
  year={2024}
}