Glossary
What Is VRB (Vision-Robotics Bridge)?
Last reviewed: November 2026
Short answer
VRB (Vision-Robotics Bridge) is the method from the paper “Affordances from Human Videos as a Versatile Representation for Robotics” (arXiv 2304.08488, CVPR 2023). It trains a model on human video to predict contact points and a post-contact trajectory in a scene image, which robots then use. Third-party research; Firsthand is not affiliated.
01
What is VRB, and what problem does it address?
VRB is named in Affordances from Human Videos as a Versatile Representation for Robotics (arXiv 2304.08488), submitted on 17 April 2023 by Shikhar Bahl, Russell Mendonca, Lili Chen, Unnat Jain and Deepak Pathak, from Carnegie Mellon University and Meta AI. The arXiv comments and project page name CVPR 2023. The project page expands the name as Vision-Robotics Bridge, because the authors aim to integrate computer vision techniques with robotic manipulation. They argue that a robot needs to know where and how to manipulate an object, not only what it is, and that videos of humans interacting offer more than a pretrained visual encoder. For the broader idea, see the site’s affordance entry.
02
Where does Firsthand fit next to VRB?
Firsthand is not affiliated with the VRB authors and makes no claim that any model, VRB included, was trained on Firsthand data. Firsthand captures real human egocentric video, custom collection, fast and on demand, to a written spec, with depth derived from a calibrated stereo rig, 3D hand pose at 21 joints per hand and 6-DoF IMUs at 200 Hz, delivered in RLDS, LeRobot format or WebDataset under a buyer-owned commercial license, with one task instruction per episode. Affordance labels, contact-point labels, post-contact trajectories, contact heatmaps, pretrained representations, embeddings, reward labels, robot trajectories, teleoperation data, paired human-robot video, synthetic data and language annotations beyond that instruction are not Firsthand deliverables.
03
What does VRB predict as a versatile affordance representation?
Per the paper, VRB adopts contact points and post-contact trajectories as a simple, actionable representation of visual affordance, both in pixel space. A contact point says where to interact, such as the handle of a lid, and the trajectory says how to move after contact, such as moving the lid upwards. The authors argue that copying human movement would be human-centric and would not generalize well because human morphology is starkly different from a robot’s, so this abstraction is agnostic to the morphology of the robot.
04
How does VRB get contact points and trajectories from egocentric video?
The authors train on EPIC-KITCHENS-100, using each sub-action clip, such as open door, as a sequence, and report around 54K image-trajectory-contact point tuples. A hand-object detector, with annotations released alongside the dataset, gives a hand box and a contact variable per frame. The first contact frame is found, the hand location afterwards becomes the post-contact trajectory, and skin-colour segmentation around the hand gives contact points, which a Gaussian mixture model turns into several likely targets. The project page describes the trajectory as the tracked wrist.
A homography between frames compensates for head movement, and because no human appears at robot test time, the authors map the affordances back to the first frame without the human. The labels are inferred by this pipeline, not recorded by a sensor. The project page also names Ego4D as a source of large-scale human video; the paper’s data section describes EPIC-KITCHENS-100.
05
How does the VRB model turn an image into an affordance?
Per the paper, a ResNet visual encoder produces a spatial latent, deconvolutional layers turn it into several heatmaps, and a spatial softmax gives contact-point estimates. Several heatmaps are used because the authors say the problem is multi-modal. A transformer with self-attention predicts the trajectory as relative shifts, and training uses local crops around contact points. The README says the output can be used directly at inference with sparse 3D information, such as depth, and robot kinematics. The paper projects the pixel output into 3D with a calibrated robot-camera system.
06
How do robots use VRB affordances?
The authors integrate the model with four robot learning paradigms: affordance-driven data collection for offline imitation learning, reward-free exploration, goal-conditioned learning, and affordance as an action space for reinforcement learning. The abstract reports 4 real-world environments, over 10 tasks and 2 robotic platforms. The paper names a Franka Emika Panda arm and a Hello Robot Stretch mobile manipulator, and also tests on a simulation benchmark modelled on the Franka Kitchen environment from D4RL.
07
What did the authors report, and what is left as future work?
In the offline imitation test, the authors report that VRB beat prior approaches on 7 of 8 tasks, with an average success rate of 57% against 25% for the runner-up, Hotspots. They also report that its visual encoder beat R3M on three simulated Franka tasks after fine-tuning. These are the authors’ figures on their setup; Firsthand has not verified them. The conclusion lists multi-stage tasks and force and tactile information as future directions.
08
How does VRB compare with General Flow, Track2Act and Im2Flow2Act?
The first table sets VRB beside four site entries, summarising what those entries state. The General Flow entry notes that its paper lists Bahl et al. (VRB) as the only open-source work with a similar setup.
09
What data does a VRB-style approach need, and what does Firsthand state?
Per the paper and README, it needs egocentric human video with hand-object contact, a hand-object detector, a way to estimate camera motion, and camera calibration plus depth to turn pixel outputs into robot actions. Firsthand states real human egocentric capture, depth from a calibrated stereo rig, 3D hand pose, and contact events (see the affordance entry), with one task instruction per episode. That is a note about format, not a compatibility claim: any contact points or trajectories would come from tools the buyer runs.
This site’s EPIC-KITCHENS entry names that dataset’s video and annotation licences as non-commercial. For real human demonstrations that public video does not cover, request on-demand custom collection and confirm it on a Spec Pilot, with a median of 48 hours to a first validated batch where coverage is deep and three to four weeks where it is thin.
10
VRB at a glance, as stated in the paper, project page and GitHub README
| Item | What the sources state |
|---|---|
| Paper | Affordances from Human Videos as a Versatile Representation for Robotics (arXiv 2304.08488) |
| Name | VRB, expanded as Vision-Robotics Bridge on the project page |
| Authors | Shikhar Bahl, Russell Mendonca, Lili Chen, Unnat Jain and Deepak Pathak |
| Affiliations | Carnegie Mellon University and Meta AI |
| Venue | CVPR 2023 (arXiv comments and project page) |
| Representation | Contact points and a post-contact trajectory, in pixel space |
| Training data | EPIC-KITCHENS-100 video; around 54K image-trajectory-contact point tuples (authors) |
| Label source | Hand-object detector, skin-colour segmentation, Gaussian mixture model and a homography for camera motion |
| Robot platforms | Franka Emika Panda arm and Hello Robot Stretch mobile manipulator |
| Code | shikharbahl/vrb on GitHub; MIT License per the repository |
| Firsthand relationship | None |
12
VRB beside the General Flow, Track2Act, Im2Flow2Act and Affordance entries
| Site entry | What the entry states | How VRB differs (sources read) |
|---|---|---|
| General Flow | A published affordance representation: future 3D trajectories of points on an object, predicted from a point cloud and a language instruction, trained on RGBD human video | VRB predicts 2D contact points and a post-contact trajectory from a single image, with labels inferred from EPIC-KITCHENS-100 video, and uses no language input in the model |
| Track2Act | A published method that predicts 2-D point tracks from an initial and a goal image, then refines the plan with a residual policy trained on a small set of robot demonstrations | The VRB model takes one human-agnostic image and no goal image, and the paper uses it across four learning paradigms |
| Im2Flow2Act | A published framework that generates 2D object flow from human video and a task description, then runs a flow-conditioned policy trained on simulated robot data | VRB centres on hand contact and wrist motion, takes no task description, and the paper states it enables robot learning without requiring any simulation |
| Affordance | What an object lets an agent do; the entry cites VRB for contact points plus a post-contact trajectory | VRB is one concrete method that defines an affordance that way and trains a model for it |
13
What VRB consumes beside what the Firsthand site states
| Aspect | VRB (sources read) | What the Firsthand site states |
|---|---|---|
| Human video | EPIC-KITCHENS-100 kitchen video | Real human egocentric video, custom collection |
| Labels | Inferred by the authors’ pipeline: contact points and hand trajectory | Not a Firsthand deliverable; contact events are stated separately |
| Depth | Needed at deployment to project pixel output into 3D | Depth derived from a calibrated stereo rig |
| Task specification | Goal images in the robot experiments | One task instruction per episode |
| Robot data | Collected by the authors’ robots during their experiments | Robot trajectories, teleoperation data and synthetic data are not Firsthand deliverables |
14
Frequently asked questions
- What is VRB (Vision-Robotics Bridge)?
- A published method (arXiv 2304.08488, CVPR 2023) that learns affordances from human videos as contact points and post-contact trajectories, for use across robot learning paradigms. It is third-party research.
- What does VRB predict from an egocentric video frame?
- Given a scene image, the model predicts where a person is likely to make contact, as heatmaps over contact points, and how the hand would move afterwards, as a trajectory, both in pixel space.
- What data trains VRB?
- Per the paper, EPIC-KITCHENS-100 video, with labels inferred by a hand-object detector and a segmentation and tracking pipeline. The authors report around 54K training tuples.
- Is the VRB code available?
- The official GitHub repository, shikharbahl/vrb, lists an MIT License. Check the licences of any dataset you train on.
- Was VRB trained on Firsthand data?
- No. Firsthand is not affiliated with the authors and claims no use, training or compatibility. Contact-point labels, trajectories and heatmaps are not Firsthand deliverables.
- How can I request a custom egocentric dataset for affordance learning?
- Request a custom dataset with your objects, interactions and signals. Collection is fast and on demand, with a first validated batch in a median of 48 hours where coverage is deep.
Related terms
- Affordance
- General Flow
- Track2Act
- Im2Flow2Act
- Hand-object interaction (HOI)
- EPIC-KITCHENS
- HRP (Human Affordances for Robotic Pre-Training)
- SWIM (Structured World Models from Human Videos)
- WHIRL (Human-to-Robot Imitation in the Wild)
- ZeroMimic (Distilling Robotic Manipulation Skills from Web Videos)
- Zero-Shot Robot Manipulation from Passive Human Videos
Sources
- Affordances from Human Videos as a Versatile Representation for Robotics (VRB, arXiv 2304.08488)
- VRB (official project page)
- shikharbahl/vrb (official GitHub repository)
- Rescaling Egocentric Vision: Collection Pipeline and Challenges for EPIC-KITCHENS-100 (arXiv 2006.13256)
- EPIC-KITCHENS dataset (official site)
- Ego4D: Around the World in 3,000 Hours of Egocentric Video (arXiv 2110.07058)
- R3M: A Universal Visual Representation for Robot Manipulation (arXiv 2203.12601)
- D4RL: Datasets for Deep Data-Driven Reinforcement Learning (arXiv 2004.07219)
- General Flow as Foundation Affordance for Scalable Robot Learning (arXiv 2401.11439)
- Track2Act (arXiv 2405.01527)
- Flow as the Cross-Domain Manipulation Interface (arXiv 2407.15208)