# ManiSkill panda StackPyramid-v1 motion planner: robotics skill example

Arrange three cubes into a pyramid using the official Panda planner. The recorded CPU/state seed-0 attempt ran 176 steps but failed the task objective; installation and imports succeeded.

## Task and environment

maniskill | 3.0.0b22 | panda | pd_joint_pos | linux | 3.10

## Example input

```json
{
  "task": "StackPyramid-v1",
  "seed": 0,
  "robot": "panda",
  "controller": "pd_joint_pos",
  "obs_mode": "state",
  "sim_backend": "cpu",
  "render_backend": "none",
  "reward_mode": "sparse",
  "max_episode_steps": 1000
}
```

## Retrieve and prepare

Read https://hub.superfastrobotics.com/skills/maniskill-panda-stack-pyramid/skill.json or https://api.superfastrobotics.com/v1/skills/maniskill-panda-stack-pyramid?hub_commit=ede75c00118e9808e5099da43c26f4619cc3bc37&record_version=1.1.0&include=experience without installing a client. Inspect the license, exact environment and evidence before preparation. Preparation and execution remain separate.

Source: https://github.com/haosulab/ManiSkill at 33967b9e3ead1f841eec57cc9f31d0d8b8cf0907. Record version: 1.1.0.

## Success condition

StackPyramid-v1 env info.success is true after the upstream solver finishes, truncated is false, and 0 < elapsed_steps < max_episode_steps=1000; only then status is task_complete and exit is 0. The 1000-step motion-planning horizon is a Hub recipe condition, not the upstream default benchmark horizon.

## Recorded evidence

import_verified: The exact 1.1.0 wrapper was installed, imported and executed once at seed 0 in run 39100095436 at Hub commit 0442ed7b99d78a970e92780a16df793e65039370. It returned success=false, task_objective_not_reached, 176 steps, terminated=false, truncated=false and exit 1 after 5.678 seconds, without hitting the 180-second timeout. import_verified records the passed setup/import stage; last_task_attempt records the failed task outcome. The failed objective was not a step-budget or process-timeout failure. No subcondition measurements were captured, so its precise cause and the causal role of the initial-pose warning remain unknown. This is one maintainer-selected CPU/state attempt under the Hub 1000-step horizon, not the upstream default-250-step benchmark, independent adoption, RGB or hardware validation.

This page is a data-only example and performs no execution.