UMI

The hardware guide describes two packages

The capture guide lists printed gripper parts, linear rails, springs, soft fingers, visual tags and a GoPro Hero9 with a Max Lens Mod. It links separate Onshape documents for the gripper and fingers. It also states that left and right grippers use different tags, so bimanual hardware cannot be treated as two unconfigured copies. The public text export was preserved; image-based assembly details and external CAD payloads were not independently inspected. [S005]

The deployment section instead lists a UR5-family arm, Weiss WSG-50, camera accessories, an HDMI capture card and workstation connections. Its per-component historical prices do not establish a current complete delivered budget, and the robot is listed by quote. A low capture-device cost therefore should not be presented as the cost of a complete autonomous robot system. [S005]

SLAM quality limits the training input

The README provides an example SLAM workflow and explicitly identifies its ORB_SLAM3 fork as a fragile stage. Its example success fraction belongs to that supplied session, not to every new recording. The fork, container and data-collection instructions are separate dependencies. No videos were processed and no SLAM result was reproduced here. [S001]

The selected installation instructions report testing only on Ubuntu 22.04 and name an RTX3090 with 24 GB for a tested single-GPU training setup. These are reported environment details, not a catalog-tested minimum specification. The workflow links processed datasets and pretrained checkpoints externally; their complete payloads and applicable licenses were not preserved in this review. [S001] [S009]

Deployment still requires rig-specific configuration

The example configuration contains robot and gripper addresses, observation and action latencies, a TCP offset, collision-geometry parameters and an inter-arm transform. Those are concrete reasons to match a deployment to the physical rig rather than treating broad calibration-free project language as eliminating all setup. They are examples, not measurements of a reader's hardware. [S006] [S007]

The UR route uses WSG50 configuration and a camera capture chain. The Franka instructions describe a separate Polymetis server on a real-time-kernel computer and different load settings. Neither route was installed or connected to hardware by this catalog. [S001] [S005] [S008]

The cup-policy download command names cup_wild_vit_l_1img.ckpt, while the shown evaluation command uses cup_wild_vit_l.ckpt. Resolve that filename/configuration mismatch before assuming the example runs unchanged. The README also reports poor performance in direct sunlight for that policy; the project page's broader lighting-robustness claims should not erase this specific limitation. [S001] [S006]

The repository is MIT-licensed. That license is not automatically assigned to external CAD, hardware-guide media, datasets, checkpoints or the SLAM fork. This profile establishes source-researched workflow coverage, with no fabrication, training, flashing or physical performance test claimed. [S001] [S003] [S005] [S009]