--- license: apache-2.0 pretty_name: OOJU Galaxea R1 Pro Pick Cube task_categories: - robotics size_categories: - 10K ## What is in each episode Each recording has a task name and timestamp identifier, for example `side-grasp_20260815_210713` or `top-grasp_20260813_213502`: - `_.json` — Time-series XR frames, including hand and eye poses and validation signals. - `__metadata.json` — Episode and environment metadata, including task environment, device, timing, success, and quality checks. - `__robot.json` — Robot observations and actions, including joint positions, velocities, drive targets, root pose, and engine state. - `camera_real/frames.tar` — Uncompressed archive of the original JPEG passthrough frames (`real_frame_*.jpg`). - `camera_real/` also contains camera poses, calibration, and video sidecar metadata. ### Episode layout ```text side-grasp/ ├── side-grasp_20260815_210713/ │ ├── side-grasp_20260815_210713.json │ ├── side-grasp_20260815_210713_metadata.json │ ├── side-grasp_20260815_210713_robot.json │ └── camera_real/ │ ├── side-grasp_20260815_210713_camera_poses.json │ ├── side-grasp_20260815_210713_video.json │ ├── calib.json │ └── frames.tar └── ... ``` ### Robot joint ordering The 22-element `q`, `qd`, and `action_q` arrays use this order: 1. Four torso joints 2. Seven left-arm joints 3. Seven right-arm joints 4. Two left-gripper finger joints 5. Two right-gripper finger joints Exact joint names are recorded in each `*_robot.json` file. ### Hand-joint ordering Each hand stores 26 poses in this order: palm and wrist; thumb metacarpal, proximal, distal, tip; then metacarpal, proximal, intermediate, distal and tip for index, middle, ring and little fingers. The names are repeated in each frame under `left_hand.joint_names` and `right_hand.joint_names`. Every hand pose is translation followed by rotation, `[x, y, z, qx, qy, qz, qw]`. ### Units and coordinate conventions - Joint angles in radians, translations in metres, time in seconds. - Quaternions are XYZW, scalar last. - Robot root poses use the Unity left-handed, Y-up world frame. - Camera poses are camera-to-world transforms in the Unity world frame. - Camera intrinsics follow the OpenCV pinhole convention, top-left origin, downward-positive image Y axis. ## Synchronization The robot and XR/camera streams run at different rates. Robot samples are nominally 50 Hz; each JPEG maps one-to-one to an XR frame and a camera-pose entry at roughly 24 FPS. Align with `timestamp_seconds` in the trajectory file and `trajectory_timestamp_seconds` in the camera-pose sidecar. Do not substitute `center_eye_pose`, `left_eye_pose` or `right_eye_pose` for the physical passthrough-camera pose. The eye fields are display-view poses; the camera-pose sidecar describes the image sensor at capture time. ## Data quality and limitations - The first JPEG of every episode is blank. It is written before the passthrough stream is live, so start from the second frame. - Camera sidecars flag 678 frames as `IMG_STATIC`. - The camera distortion model is unmeasured; distortion coefficients are zero. - Video sidecars contain recorder-generated MP4 path fields, but this snapshot ships the original JPEG frames inside `frames.tar`, not MP4 files. - The snapshot covers two grasp tasks, one robot embodiment, one XR device, one camera viewpoint and a limited physical setting. - It contains no failed demonstrations, no audio, no depth and no force/torque. - Capture device identifiers in the JSON have been replaced with a neutral label. All episodes come from a single headset. ## What is visible in the frames The passthrough frames are first person and were recorded indoors on a high floor. They show the demonstrator's bare hands and forearms, the desk surface and props used for the task, and a window with a view of the surrounding area. If you plan to redistribute derived imagery, note that the window view is identifiable. ## FAQ **Can I collect demonstration data without building a teleoperation rig?** Yes. Every episode here was recorded by a person wearing a Meta Quest 3 and moving their hands; the robot joint commands were produced afterwards by retargeting. There is no leader arm, no exoskeleton and no motion-capture stage. **Can data recorded from human hands be used on a robot?** It has to be retargeted first. This repository ships the result of that step for the Galaxea R1 Pro: 80,014 robot samples with 22-DoF joint positions, velocities and drive targets, alongside the original hand poses. The retargeting is what turns a hand trajectory into something a robot controller can execute. **How many demonstrations do I need?** This dataset does not answer that on its own. Our [cup dataset](https://huggingface.co/datasets/OOJU/pick-place-cup-20260404) ships trained checkpoints and evaluation results for one task at 47 demonstrations, and reports both the learned-policy and the retrieval-and-replay numbers so the gap is visible. **What is the difference between this and a teleoperation dataset?** Most teleoperation datasets record the leader device or the robot's own commanded state. This records the human hand at 26 joints per hand plus the first-person view, and derives the robot action from it. The hand pose is kept, not discarded, so grasp shape survives into the released data. ## Collect and validate your own data If your task, objects or environment are not covered here, the same pipeline is available: Quest 3 capture, automated validation against a target embodiment, and export. **[Request access](https://ooju-app.world/request?utm_source=huggingface&utm_medium=dataset_card&utm_campaign=galaxea-pick-cube&utm_content=footer)** ## License Released under the Apache 2.0 License. ## Citation ```bibtex @misc{ooju_galaxea_pick_cube, title={OOJU Galaxea R1 Pro Pick Cube}, author={OOJU}, year={2026}, publisher={Hugging Face}, howpublished={\url{https://huggingface.co/datasets/OOJU/ooju-galaxea-pick-cube}} } ```