Guide
Action Segmentation for Robot Learning
Short answer
Action segmentation marks the start and end timestamp of each sub-action in an episode with a verb and noun, such as "grasp mug", turning a continuous clip into supervised, temporally-localized units. Firsthand ships action_segments as {start_ns, end_ns, verb, noun} with nanosecond timestamps aligned to every other stream, so a policy can learn from the exact moment that matters.
Last reviewed:
What is action segmentation?
An action segment is a labeled time interval marking one sub-action within an episode: a start and end timestamp with a verb and a noun, such as "grasp mug" or "open drawer". It turns a continuous clip into supervised, temporally-localized units a policy can learn from, rather than one long undifferentiated recording.
This is distinct from action recognition, which classifies an entire clip with a single label. Segmentation instead marks where each sub-action begins and ends within a longer episode, so a manipulation task like "make coffee" decomposes into a sequence of separately-timed segments: reach, grasp, pour, release.
Why does robot learning need frame-accurate boundaries?
Frame-accurate action boundaries let you train and evaluate on the moments that matter and skip the transit between them. Clip-level tags or narration text are not enough for manipulation, where the exact contact moment, not the surrounding reach or retreat, is the signal a policy needs to learn.
Segment boundaries that drift even tens of milliseconds from the true contact moment corrupt supervision exactly where it is most informative. That is why segments need to be timestamped in the same clock domain as every other stream, not annotated loosely after the fact.
How is action segmentation delivered?
Firsthand ships action_segments as {start_ns, end_ns, verb, noun} with nanosecond timestamps aligned to the same PTP clock domain as video, depth, and hand pose. Because every stream shares one clock, a segment boundary lines up with the exact frame and hand-pose sample where the sub-action actually starts or ends.
- Clip-level tag
- One label for a whole clip — no internal structure, cannot localize contact
- Narration text
- Free-text description — not machine-parseable, no timestamps
- Action segment (verb-noun)
- Start/end timestamp plus verb and noun, aligned to every other stream
Action-labeling approaches
How do you spec action segmentation for a dataset?
A skill spec defines the verb-noun vocabulary and the sub-actions that matter for the target task before capture starts, so segmentation is planned rather than reconstructed afterward. That same spec drives which coverage cells count as validated hours.
FAQ
Action Segmentation for Robot Learning, answered.
01What is the difference between action segmentation and action recognition?
Action recognition classifies an entire clip with one label. Action segmentation marks the start and end timestamp of each sub-action within a longer episode, so a single clip can contain multiple separately-timed segments.
02What format are action segments delivered in?
Firsthand delivers action_segments as {start_ns, end_ns, verb, noun}, with nanosecond timestamps in the same PTP clock domain as every other stream in the episode.
03Why do segment boundaries need to be synchronized to video and depth?
If a segment boundary drifts from the true contact moment, the supervision is wrong exactly where it matters most. Aligning segments to the same clock as video, depth, and hand pose keeps the labeled moment and the sensor data in agreement.
04Can action segments be scoped to a custom verb-noun vocabulary?
Yes. The verb-noun vocabulary and sub-actions to label are defined in the skill spec before capture, so segmentation matches the target task rather than a generic label set.
05How fast can a dataset with action segmentation ship?
Turnaround depends on scope and coverage depth: shallow, well-covered cells can ship in a median of 48 hours, while long-tail failure-case coverage takes longer. See how validated hours are counted for the full breakdown.
Sources
Where is this documented?
- RLDS (Reinforcement Learning Datasets) — GitHub (opens in a new tab)Episode/step schema that action segments and other per-episode annotations are delivered within. github.com
Check it against the sample pack.
40 episodes across 4 environments, delivered in the exact schema these guides describe.