- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
FITR is a pipeline that takes articulated-object images, generates assets with an existing image-to-URDF method (URDF-Anything+), and then augments them with metric scale, contact points, and joint drive parameters. Scale comes from a VLM prompted with same-category reference dimensions. Contacts are derived geometrically from joint axes, and drive parameters are category-level baselines calibrated against force-gauge measurements. The resulting 2,772 assets (FITR-Assets) and a 240-object benchmark (FITR-Bench) support about 60k motion-planned demonstrations in Isaac Sim. Three VLAs (π0.5, X-VLA, PRTS) are fine-tuned on these demonstrations, and PRTS is further improved with residual RL and distillation (PLD). The authors report zero-shot real-robot transfer on six tasks, with mean NJC around 57% for π0.5 and 82.5% for post-trained PRTS.
Critical strengths
-
The paper is an end-to-end pipeline from image to asset to demonstrations to RL post-training to real-robot deployment, and the real-world results show nonzero zero-shot progress on all six tasks. This makes the work practically useful and goes beyond asset-quality metrics.
-
The attribute completion is cheap and effective, with reference-guided scaling cutting sMAPE from 27.75% to 7.93% and geometric contacts cutting error from 21.45 cm to 1.48 cm. The released assets, demonstrations, and code add value for the community.
Critical weaknesses
-
The central claim that physical augmentation (especially joint drive calibration) enables sim-to-real transfer is never directly tested as far as I can tell. There is no ablation with and without calibrated drive parameters or absolute scale in terms of policy performance, and the only policy ablation (Table 2) confounds randomization, dataset size (10k vs 300 demos), and training steps (30k vs 5k).
-
The evaluation is limited and the novelty is modest. Real-world results cover only six single-object tasks with 20 trials each and no variance or confidence intervals, and the PRTS RL gains are measured against a baseline from the same sim distribution. The contact derivation is a simple analytic rule, and the drive parameters are category-level constants from small measurement sets, so the contribution is mostly integration of existing components (URDF-Anything+, ArticuBot-style planning, PLD).
Questions for authors
- Can you ablate policy performance with uncalibrated or default drive parameters and with wrong scale, holding the dataset size and training budget fixed? This is the key evidence that the physical attributes matter for transfer.
- Can you provide variance or confidence intervals over seeds and trials, and compare against baseline assets such as PartNet-Mobility with default physics? Also, how often does the VLM-completed instance-level drive adjustment actually differ from the category baseline?
- (Clarification) Table 1 is not clear. Why is handle accuracy only computed for 5 categories? Also, how are contact points validated beyond successful planning in simulation?
Follow-up on Our Response
Dear Reviewer Tp8D,
As the discussion period draws to a close, we would welcome your feedback on our responses. We have added six-task physical attribute ablations, training-step comparisons, and standard deviations and confidence intervals for selected simulation results. We also clarified the training settings and evaluation protocol and provided a two-stage manipulation demo.
Please let us know whether any concerns remain after considering this additional evidence. We would be happy to discuss them further. Thank you again for your time and consideration.