YUBI—Real2Sim

ROBOT LEARNING · REAL-TO-SIMULATION

YUBI-Real2Sim

3DGS Scene Verification for Reliable Policy Evaluation

When can a reconstructed world be trusted to evaluate a robot?
Connecting real scenes, fisheye vision, and policy performance.

Hiroki Nishizawa1,2 Takehiko Ohkawa1 Nicola Scianca1
Tatsuya Matsushima1 Shigeo Morishima2 Kei Ota1

1 AIRoA 2 Waseda University

Real dual-arm Franka robot with YUBI grippers facing a cup and plate on a laboratory table REAL WORLD
Reconstructed laboratory scene and robot used for simulation RECONSTRUCTED WORLD
01 / REAL → SIMA physical workspace becomes a reusable environment for policy evaluation.

THE QUESTION

A realistic scene.
A reliable evaluation?

Evaluating vision–language–action policies on real robots is costly and difficult to reproduce. 3D Gaussian Splatting (3DGS) makes it possible to reconstruct real environments, but visual realism alone does not establish whether a simulator will select the better policy.

YUBI-Real2Sim studies that connection. We combine scene reconstruction, object modeling, and MuJoCo simulation with the dual fisheye wrist views used by YUBI. Controlled changes to the reconstruction let us investigate how holes, floaters, and warped surfaces affect policy evaluation.

THE FRAMEWORK

From capture to closed-loop evaluation.

Real-world appearance.
Physical interaction. The same wrist views.

01

Capture

Fisheye frame captured in the real workspace

Capture the environment with a wide-angle camera, then project selected frames into pinhole views.

FISHEYE VIDEO
02

Reconstruct

Estimated camera poses and reconstructed scene geometry

Estimate camera poses and geometry, then optimize a 3D Gaussian Splatting background.

COLMAP · OpenMVS · 3DGS
03

Simulate

Robot and task objects assembled in MuJoCo

Register the scene to the robot and combine object visual meshes with collision geometry.

OBJECT MESHES · MuJoCo
04

Evaluate

Fused background and mesh render used as a policy observation

Render both calibrated wrist-camera views and execute policy actions in a closed simulation loop.

DUAL WRIST VIEWS · VLA
Policy observations → action chunks → simulated robot → new observations

THE BENCHMARK

Three scenes. Three tasks.

Cup pick-and-place, tape placement,
and pen placement.

Reconstructed Duo scene for the dual Franka FR3 platform

Duo

Dual Franka FR3
Reconstructed Flat scene for the dual Franka FR3 platform

Flat

Dual Franka FR3
Reconstructed G2 scene for the G2-compatible bimanual platform

G2

G2-compatible platform

2 policies per task

20 real trials per policy

80 simulated trials per policy

INITIAL RESULTS

Does simulation recover
the real policy ranking?

88.9%

8 of 9 observed scene–task pairs

The two policies have the same observed ordering in eight comparisons. Flat / Cup is the single reversal. This measures pairwise ranking agreement, not agreement in absolute success rates.

Successes / trials · π₁ → π₂

Showing all nine comparisons.

Observed real and simulated success counts for two policies in each scene and task
SceneTaskReal π₁ / π₂Simulation π₁ / π₂Ranking
DuoCup18/20 → 19/2021/80 → 78/80Agrees
DuoTape14/20 → 6/2020/80 → 2/80Agrees
DuoPen17/20 → 6/2025/80 → 1/80Agrees
FlatCup8/20 → 7/2030/80 → 59/80Reversed
FlatTape19/20 → 1/2050/80 → 14/80Agrees
FlatPen4/20 → 0/2012/80 → 0/80Agrees
G2Cup8/20 → 16/2018/80 → 47/80Agrees
G2Tape20/20 → 16/2015/80 → 14/80Agrees
G2Pen19/20 → 7/2048/80 → 0/80Agrees

π₁: box80k. π₂: cup1trim for Cup; tateno80k for Tape and Pen. Counts: September 16, 2026 research snapshot. Download data ↗

How to interpret these preliminary results

These are exploratory point-estimate rankings on selected measurements, not a held-out validation estimate. Some differences are only one successful trial. Tray has tied zero real successes and is excluded; unreported tasks are not counted.

The source notes historical eligibility exclusions for Duo and G2 Tape and an execution caveat for Duo Pen. Excluding those three comparisons leaves 5/6 agreement (83.3%). The nine-pair summary does not override these caveats or establish statistically resolved policy ordering.

The downloadable September 16 count ledger is used consistently here, including Flat Cup simulation counts of 30/80 and 59/80; an earlier manuscript snapshot reports different counts.

BEYOND VISUAL REALISM

What happens when the scene breaks?

How the noisy scene breaks its policy ranking.

Example reconstructed scene with a ceiling hole
01 / MISSING GEOMETRY

Remove parts of the reconstruction that can enter a wide-angle wrist-camera view.

Example reconstructed scene with floating artifacts
02 / SPURIOUS GEOMETRY

Introduce floating artifacts that alter the appearance of the workspace.

Example reconstructed G2 workspace with a warped table surface
03 / DISTORTED GEOMETRY

Distort the reconstructed surface while retaining the underlying physical setup.

How often do the conclusions change?

Holes produce one ranking reversal per condition. Floaters produce one reversal or tie, depending on severity. Warping preserves the ordering despite significance changes in three comparisons. Random 30% capture removal produces two reversals.

Click a condition name to explore its scene rendering and YUBI observations. Each row: 9 policy comparisons across three scenes and three tasks, including Pen; 80 trials per policy. Changes are relative to the selected Clean reference.

Provisional artifact results: significance changes, strict ranking reversals. Counts out of nine per row.
Artifact / conditionSignificance changedRanking reversed
2 (1 lost / 1 gained)1
4 (4 lost / 0 gained)1
1 (1 lost / 0 gained)0
2 (1 lost / 1 gained)1
1 (1 lost / 0 gained)1
3 (2 lost / 1 gained)0
5 (5 lost / 0 gained)0
3 (3 lost / 0 gained)1
3 (3 lost / 0 gained)2

Significance: two-sided Fisher’s exact test, unadjusted p < 0.05. “Changed” counts crossings of this threshold; it does not test whether the policy-performance gap itself changed significantly. Reversals are strict changes of ordering; ties are excluded.

Provisional September 17 snapshot. Intended condition labels include unresolved execution/provenance flags; historical Clean references are not matched controls. Download counts and definitions ↗

Source and interpretation

This is the manuscript’s intended-label aggregate, not the restricted execution-audited subset. Source flags remain on 2/9 comparisons for Hole 54°, 5/9 for Hole 90°, each floater condition and Warping, and 9/9 for each capture-coverage condition. They include wrong-scene executions, pending re-audits, and unverified reference matching; the downloadable data retains these counts.

Each severity is a separate condition, so rows reuse scene–task pairs and should not be summed as independent cases. Rank reversals compare point estimates and do not imply statistically resolved ordering.

3DGS SCENE VERIFICATION · IMAGE-QUALITY RESULTS

Can image quality tell us which simulations to trust?

Held-out Test camera rendering of Flat with a 54-degree ceiling hole, showing a tilted capture viewpoint
Test · held-out capture view3DGS-only rendering from a held-out camera pose. Shown rotated 180° for readability.
Right wrist-camera OBS illustration of Flat with a plate and cup at the initial rollout state
OBS · full right wrist viewFull 719×539 wrist-renderer output before policy resizing and contrast adjustment.
Left wrist-camera OBS illustration of Flat at the same initial rollout state
OBS · full left wrist viewThe paired full left view, with the camera housing excluded and the original aspect ratio preserved.

Example views from Flat / Hole 54°: Test image 60 and OBS frame 0. Test samples capture viewpoints; OBS samples recorded policy-observation poses. These are different viewpoints, not aligned image pairs.

NVS-SQA alone did not reliably identify policy-ranking failures in this study. Under reduced capture coverage, held-out Test scores changed by at most 0.060, compared with a 0.224 range across the three Clean scenes. G2’s contiguous and random 30% frame-removal variants reversed policy rankings while changing the score by only −0.018 and −0.039, respectively.

We fit quality thresholds on two scenes and evaluate on the held-out third, keeping all variants of each scene together. Across 15 matched scene–variant conditions and three tasks (Cup, Tape, Pen), SSIM on Test views and NVS-SQA on OBS views with camera-housing occlusion removed both achieve 32/45 correct task-level decisions (71.1%). Neither exceeds the constant “always reliable” baseline.

Correct ranking-reliability classifications for Cup, Tape, and Pen, with each scene held out in turn
Metric / viewsCupTapePenTotalAll-three
PSNR / Test8/158/1515/1531/45 (68.9%)9/15
SSIM / Test8/159/1515/1532/45 (71.1%)7/15
LPIPS / Test8/155/1515/1528/45 (62.2%)10/15
NVS-SQA / Test7/158/1515/1530/45 (66.7%)13/15
NVS-SQA / OBS13/154/1515/1532/45 (71.1%)4/15
Always reliable8/1512/1515/1535/45 (77.8%)6/15

OBS scores use 518×518, 90° pinhole re-renders at recorded wrist-camera poses, they are not the exact policy-input images. The original inputs include camera-housing occlusion. Entries count correct classifications, not successful robot trials. “All-three” is a separately fitted binary target: whether all three task rankings agree with real evaluation. It is not a combination of the task-level predictions. Pen’s 15/15 reflects constant predictions on all-reliable labels, not demonstrated failure detection.

Housing-removal evaluation, October 22, 2026: all 15 conditions were rescored with the same NVS-SQA model, 518×518 resolution, 90° field of view, camera poses, and recorded frames (19 paired frames per Flat condition; 38 per Duo/G2 condition, 950 images total). Paired renders identify pixels affected by camera-housing removal; all other pixels are retained exactly from the original evaluation images. Thresholds are refitted using the same scene-held-out protocol. Test scores are unchanged. Download comparison data ↗

For context, always predicting “reliable” achieves 35/45 (77.8%) task-level accuracy without a quality score. NVS-SQA misses all three Tape ranking failures. Test-view NVS-SQA performs better on the separate All-three target (13/15, versus 6/15 for always reliable and 9/15 for always unreliable), but these three-scene results do not establish a general scene-acceptance rule.

FOLLOW THE PROJECT

Building toward reproducible
real-to-sim evaluation.

The public repository is in early development. A runnable pipeline,
evaluation code, and release documentation are planned.

View on GitHub

SCENE & YUBI OBSERVATIONS

Scene rendering · 360° orbit
YUBI OBS · right wrist
YUBI OBS · left wrist

The orbit shows the reconstruction from a moving camera. OBS shows the initial recorded state, with the camera housing excluded and the full native image preserved, before policy resizing and contrast adjustment. Orbit and OBS use different viewpoints and may show different task setups. Click an OBS image for full resolution.