Data MarketplaceData Market English

EGOCENTRIC DATA · VLM

Bring first-person capture
into your VLM pipeline.
Bring egocentric capture
into your VLM pipeline.

From real capture and time alignment to semantic annotation. First verify the E2 / E6 samples and fields, then evaluate training, evaluation, and delivery scope against the target task.From real capture and time alignment to semantic annotation. Inspect E2 / E6 samples and fields, then scope training, evaluation and delivery for your task.

Public samples are verifiable · Source tiers are traceable · Scope of applicability confirmed per projectInspectable Samples · Traceable Provenance · Project-Scoped Adaptation

E2 left eye with Vision 21 hand points
E2 · estimate Left-eye sample. Cyan = left hand, orange = right hand, gray = confidence below 0.5. The screen has been redacted; the wearer's hands are retained. Left-eye sample. Cyan = left hand, orange = right hand, gray = confidence below 0.5. The screen is mosaicked; the wearer's hands remain.

TOBI · VLM DATA ENGINEERING

What does your model need to understand?What does your model need to understand?

Below is the project requirements entry point. The existing samples demonstrate basic observation and partial annotation; the full task set, adaptation, and performance evaluation require separate confirmation.These are project-scoping paths. Current samples show observations and selected annotations; full task datasets, adaptation, and model evaluation require confirmation.

01

Scenarios and Wearer Q&AScene & wearer QA

Distinguish who is operating, what is seen, and which questions cannot be answered.Identify who acts, what is visible, and which questions cannot be answered.

Q&A + Evidence Time RangesQA + evidence spans

Evaluate this task →Scope this task →
02

Temporal Localization and Step UnderstandingTemporal Grounding

Locate the start and end of the action; verify preceding and following states and step order.Locate action boundaries, before/after states and step order.

Time interval + step labelTime spans + step labels

Evaluate this task →Scope this task →
03

Hand–object interaction and spatial relationshipsHand–object understanding

Verify hands, objects, occlusion, and coordinate definitions.Inspect hands, objects, occlusion and coordinate conventions.

Optional keypoints + valid maskOptional Keypoints + Validity

Evaluate this task →Scope this task →
04

Long-Video Event RetrievalVideo Event Retrieval

Find clips by event; cross-session memory requires a new capture design.Retrieve clips by event; cross-session memory requires additional capture design.

Event index + query evidenceEvent Index + Query Evidence

Evaluate this task →Scope this task →
05

Task Progress and Failure UnderstandingProgress & failure

Design reviewable supervision for success, failure, and error correction.Design-reviewable supervision for success, failure, and recovery.

State Changes + Failure CausesState transitions + failure labels

Evaluate this task →Scope this task →

TOBI · VLM DATA ENGINEERING

Every step has a clear output.A concrete output at every stage.

  1. 01

    Task definitionDefine the Task

    Capture protocol / task matrixCapture protocol / task matrix

    First define the problem, scenario coverage, train/test split, and acceptance criteria.Agree on the task, scene coverage, train/test split, and acceptance criteria.

  2. 02

    Real CaptureCapture

    Raw footage / sensors / calibrationSource / sensors / calibration

    Retain the original master, and record the device, session, calibration version, and the scope of available licensing rights.Preserve source media with device, session, calibration and permitted-use records.

  3. 03

    Spatiotemporal alignmentAlign

    Time index / valid intervalTime indexes / valid intervals

    Distinguish clock offset from drift; check for dropped frames, gaps, units, and coordinate systems.Separate clock offset from drift; check dropped frames, gaps, units and coordinate frames.

  4. 04

    Semantic supervisionAnnotate

    Narration / evidence / review recordNarration / evidence / review

    Evaluate Q&A, motion ranges, and step labels based on the task; indicate whether the source is manual or model-generated.Scope QA, action spans and step labels by task; record human or model provenance.

  5. 05

    Spatial AssistanceEnrich

    Optional hand-point / spatial relationshipsOptional hands / spatial relations

    Evaluated per project, with methodology and validity retained. Neither device algorithms nor offline estimates automatically equal ground truth.Evaluate per project, preserving method and validity. Device algorithms and offline estimates are not automatically ground truth.

  6. 06

    Model AdaptationAdapt

    Sample Structure / Loading RecipeSample schema / loading recipe

    Agree on model version, frame sampling, resolution, and budget; confirm compatibility after validation with actual loading.Agree on model version, sampling, resolution and budget; confirm compatibility only after a loading test.

  7. 07

    Independent evaluationEvaluate

    Frozen test set / failure analysisFrozen test set / failure analysis

    Isolate data by personnel, site, and session. Accept QC reports and model performance separately.Separate people, locations, and sessions across splits. Validate data quality separately from model performance.

  8. 08

    Version deliveryDeliver

    Checklist / QC / Change LogManifest / QC / changelog

    Deliver documents, source records, and quality reports according to the confirmed scope; new adaptations and evaluations require separate confirmation.Deliver agreed files, provenance and QC. Additional adaptation and evaluation require a scoped agreement.

Delivery begins with a review of tasks and fields. The real samples below can be used to verify current outputs; added supervision, model adaptation, and independent evaluation are not included in the default deliverables.Delivery starts with task and field review. Samples below document current outputs; new supervision, model adapters and independent evaluation are not included by default.

Source attribution: raw sensor data, on-device algorithms, offline estimates, and human annotation are recorded separately. OpenXR / SLAM are algorithm outputs and do not become ground truth merely because they are written by the device. All frequency, offset, and validity-rate figures describe only the corresponding public sample.Provenance distinguishes raw sensors, device algorithms, offline estimates and human annotation. Device-written OpenXR / SLAM is not ground truth. Rates, offsets and validity figures describe the specific public samples only.

E2 · estimate · 40.0–48.0 s · 4 Hz Left: raw left-eye frame. Right: SGBM + left-right consistency + confidence gating. Black blocks = low confidence / matching failure. Not a depth camera. Left: original Camera0. Right: SGBM + LR check + confidence gate. Black = low confidence. Not a depth camera.
The preview is for verification only. Training reads the Camera0 / Camera1 original footage at 1600×1200 @ 30 Hz. Effective pixel ratio is approximately 40%, with a median distance of approximately 1.34 m. Preview for checking only. Train on Camera0 / Camera1 at 1600×1200 @ 30 Hz. ~40% valid pixels, median distance ~1.34 m.

Interaction ExamplesInteractive sample

Annotation Workbench

Annotation workbench

Click a step or use the left/right arrow keys: both streams jump and play in sync, with audio from the original clip only. Player 0 seconds = recording 22 seconds. Boxes, masks, 6DoF, contact force, and joint confidence are empty.

Click a step or use the arrows: both players jump and play together; only raw stays audible. Player 0 s = record 22 s. Boxes, masks, 6DoF, contact force and joint confidence stay empty.

Page 1 / 6 stepsStep 1 / 6 SourceSource 22.00 s PreviewPreview 0.00 s
E6 RAW
E6 ANNOTATED

E2 · 20260917_133640

Post-Processing on Binocular Data

Estimates on stereo

11 minutes 22 seconds. The device only has left and right eyes, an IMU, a magnetometer, and 16 kHz stereo audio. The skeleton, mosaic, and top-right parallax are not device output. When played together, only the track you pressed sounds.

11 min 22 s. Device files are the two eyes, IMU, mag and 16 kHz stereo. Skeleton, mosaic and corner disparity are estimates. Only the player you press stays audible.

E2 RAW
E2 ANNOTATED

Open E2 sample documentationE2 sample notes

Tiered DataGraded data

Full pipeline: real worn recording → depth-processed into trainable assets

One pipeline: worn capture → graded assets for training

Using TOBI's established naming: device → indexes → human → estimate. For procurement, tiers can be selected by depth; no undelivered capabilities are claimed. Samples are for field verification; actual delivery is subject to the project manifest.

Named with what TOBI already ships: device → indexes → human → estimate. Buyers pick depth; we do not claim undelivered layers. Use samples to inspect fields; the agreed manifest defines delivery.

E6 worn capture
D1 · DEVICE

Raw capture data

Source Data

Video and IMU / pose. Native frame rate original footage, calibration tied to serial number.

Video plus IMU / pose. Native-Hz source; calibration by serial.

  • E2 Binocular / E6 Multi-Stream RGB
  • IMU · Audio Offset
  • Camera intrinsic and extrinsic parameters
  • E2 stereo / E6 multi RGB
  • IMU · audio offset
  • Intrinsics / extrinsics
E6 synced frames
D2 · INDEXES

Basic alignment

Aligned base

Standardized structure, multimodal temporal alignment, and validity quality checks.

Standard structure, multimodal time sync, validity QA.

  • time_sync.json
  • rgb / stereo indexes
  • Missing columns left blank
  • time_sync.json
  • rgb / stereo indexes
  • Empty columns stay empty
Workbench narration
D3 · HUMAN

Semantic data

Semantic data

Let the model read the wearer's sentences and keyframes: scenes, objects, and action time spans.

Wearer sentences and keyframes: scene, objects, action spans.

  • narration.jsonl
  • Six-step keyframes / object time segment
  • Human-verified, not detector-rewritten
  • narration.jsonl
  • Six keyframes / object spans
  • Human check, not detector rewrite
Hand estimate points
D4 · ESTIMATE

Behavior estimation (optional)

Behavior estimate (optional)

Hand points, trajectory assistance, privacy blurring. Carries a method label; not treated as device-source data, not used as robot actions.

Hand points, track aids, privacy mosaic. Method-tagged; not device truth; not robot actions.

  • Vision 21 · estimate
  • Mosaic · weak OCR
  • SGBM distance samples (not depth ground truth)
  • Vision 21 · estimate
  • Mosaic · weak OCR
  • SGBM distance sample (not depth truth)
D1
Original footageSource Binocular / Multi-Stream Video · IMU · Calibration Stereo / multi video · IMU · calibration
Cleaning and Alignment
Quality inspection
clean · sync
QA
D2
AlignmentAligned Standardized structure · Multimodal synchronization · Scene indexing Standard structure · multimodal sync · scene index
Narration linking
Manual Review
attach narration
human review
D3
SemanticSemantic Task semantics · Object / Action · Structured sentence Task semantics · object / action · structured sentences
Estimate Extraction
Write method
estimate extract
write method
D4
EstimateEstimate Hand Keypoints · Trajectory Assistance · Behavior Understanding Assistance Hand keypoints · track aids · behavior helpers

07 · Delivery Examples07 · Delivery samples

Raw footage, alignment, semantics, and hand estimation, processed and delivered on demand

Source, alignment, semantics and hand estimates — delivered by depth

The primary VLM package falls under device / human / indexes; estimate is optional. MCAP and LeRobot directories have been reserved but are not yet exported. The following four categories are the actual delivery list, not slogans.

Primary VLM packs land as device / human / indexes; estimate optional. MCAP and LeRobot folders are reserved, not exported yet. The four cards below are the real delivery checklist.

TOBI DATA PACK TOBI delivery package · confirm delivery fields against the project checklist TOBI pack · delivery fields defined by the project manifest

Choose depth based on the project. Default is D2; add D3 for VLM-focused work; add D4 for hand assistance.

Pick depth per project. Default D2; add D3 for VLM; add D4 for hand aids.

View real delivery samplesOpen real delivery samples

D2 D2 · INDEXES Base data · Standardized capture alignment Base · standardized aligned capture time_sync, index, validity. Suitable for pipeline integration first. time_sync, indexes, validity. First pipeline hook.
D3 D3 · HUMAN Semantic Data · Scene / Narrative / Keyframes Semantic · scene / narration / keyframes VLM recommended tier: human sentences can be verified. Primary VLM tier: checkable human sentences.
D4 D4 · ESTIMATE Behavior Estimation · For Policy Assistance Behavior Estimate · Policy Helpers Fingertip tapping and barcode scanning are optional; not described as robotic actions or ground-truth depth. Optional hands / mosaic; not robot actions or depth ground truth.

01

Data files

Data files

  • Video / binocular or multi-channel raw footage
  • IMU / sensor streams
  • Time synchronization and audio offset
  • Video / stereo or multi-cam source
  • IMU / Sensor Streams
  • Time sync and audio offset
MP4CSVJSON

02

Structured results

Structured results

  • Narration / Keyframes / Object Time Segments
  • Hand trajectory (device or Vision estimate)
  • Action time segment (manually verified)
  • Narration / keyframes / object spans
  • Hand tracks (device or Vision estimate)
  • Action spans (human-checked)
JSONLJSON

03

Data index

Data index

  • Episode / Task timestamp
  • Scenario and file association
  • RGB / hand / sync index
  • Episode / task timestamps
  • Scene and file links
  • RGB / hand / sync indexes
JSONJSONL

04

Quality Report

Quality report

  • Data Volume and Validity Rate
  • Anomalies and access control
  • QA / validity acceptance
  • Volume and yield
  • Anomalies and gates
  • QA / validity acceptance
JSONHTML
device/Raw streams and calibration
Read here for training
Raw streams & calibration
Train here
estimate/Offline Algorithm
With method
Offline algorithms
with method
human/Narrative and keyframesNarration & keyframes
indexes/Time synchronization
validity
Time Sync
validity
preview/Low-frame-rate mp4
For human viewing only
Low-Hz mp4
humans only
For model trainingModel training · VLM / Scene Description Used for data validity checksEvaluation · validity · workbench verification For data researchResearch · Field and timeline audit

VLM minimum set: device/ raw footage, calibration and applicable audio offsets · human/narration.jsonl (and E6 keyframes) · indexes/time_sync.json · validity. Preview mp4 and ungated estimated distances do not enter the training columns, and public model scores are not written in.

Minimum VLM set: device/ source, calibration, and audio offsets where applicable · human/narration.jsonl (plus E6 keyframes) · indexes/time_sync.json · validity. Do not put preview mp4, ungated estimated distance, or public model scores into a training column.

episode_bundle.v1.json embodied_layers.v1.json Delivery tier descriptionDelivery tier note

TOBI · VLM DATA ENGINEERING

Agree on acceptance criteria first, then scale up capture.Agree on acceptance before scaling.

File and Synchronization QualityFiles & synchronization

Verify schema, temporal monotonicity, file checksums, dropped frames, missing intervals, and synchronization residuals. Thresholds, sample sizes, and acceptance denominators are agreed upon in the project.Check schema, monotonic timestamps, checksums, frame drops, gaps and sync residuals. Agree on thresholds, sample size and denominators.

Independent task evaluationIndependent task evaluation

For Q&A, evaluate correctness and evidence; for temporal localization, evaluate interval overlap; for spatial localization, evaluate coordinate error; for failure detection, evaluate missed detections. Fix the model, prompts, frame extraction, and data split before reporting results.Assess answer evidence, temporal overlap, spatial error and missed failures. Freeze model, prompts, sampling and data splits before reporting results.

Public validity reports are provided for data inspection and do not represent model performance. No model performance commitments are currently offered for the data on this page.Public validity reports describe data checks, not model performance. No model-performance claim is made for these samples.

TOBI · VLM DATA ENGINEERING

Before integration, clarify the boundaries first.Clarify the scope before integration.

Can this data be used directly to train VLMs?Can I train a VLM directly?

Can serve as a foundation for building samples. Supervised annotation, data splitting, frame extraction, input format, and loading validation must be completed for the target task; a small number of display examples do not constitute a complete training set.They are a foundation for samples. Task labels, splits, sampling, input formatting and loading require validation; a small demo is not a complete training set.

Do all VLMs require audio?Does every VLM need audio?

No. Pure vision-language tasks use images/video and text; audio is handled through a separate input or transcription branch depending on the target model's capabilities, with offsets and provenance preserved.No. Visual-language tasks use images/video and text. Audio requires a supported model input or a transcription branch with offset and provenance.

Has it already been adapted to LeRobot or a specified model?Are LeRobot or model adapters verified?

The MCAP / LeRobot directories on the current public page are reserved and are not a verified export. Adaptation must confirm version, fields, actual loading, and task scope before agreement.The public MCAP/LeRobot directories are reserved, not validated exports. Confirm version, fields, actual loading, and task scope before committing.

Can It Be Used as a Robot Motion Training Pack?Is this a robot action training pack?

The current public package does not provide verified action supervision for target robots. Human observations can be used for representation or research, but cannot be directly treated as robot control actions; whether contact force is needed depends on the task.The public pack does not provide verified action supervision for a target robot. Human observations may support representation research but are not robot control actions; force requirements depend on the task.

TOBI · VLM DATA ENGINEERING

Turn your task into deliverable data requirements.Turn your task into a scoped data project.

Start a technical review with a sample clip.Start with one sample and a technical review.

Tell us the target task, existing model, or missing fields. We will first confirm samples and delivery scope, then discuss a small-scale PoC and batch collection.Share your task, model or missing fields. Confirm sample and delivery scope before discussing a small PoC and volume capture.

  1. Field and source verificationReview fields and provenance
  2. Scope confirmation for adaptation and acceptanceAgree on adaptation and acceptance
  3. Trial capture, quality inspection, and version deliveryPilot capture, QC and versioned delivery
lk@langhuiai.com
Company and phone (optional)

TOBI · VLM DATA ENGINEERING

Traceable technical basisTraceable technical references

Method reference, not a performance demonstration on TOBI data.Method references, not performance evidence on TOBI data.

Methods, sources, and sample limitationsMethods, Provenance, and Sample Limitations

Technical SolutionMethod

Hand recognition: start with the verifiable 21 points

Hands: write 21 points you can check

Current public samples do not include MANO reconstruction results. E2 uses Apple Vision to write 21 points on the raw footage, each with a confidence value. E6 hands still use the device's OpenXR; do not replace this with that image.

The current public sample does not include MANO reconstruction. On E2, Apple Vision writes 21 points on the source frame, each with a confidence. E6 hands stay device OpenXR. This picture does not replace them.

E2 left-eye Vision 21 points
E2 left eye. Cyan = left hand, orange = right hand, gray = confidence below 0.5. Screens and distant people have been redacted; the wearer's hands are retained. E2 left eye. Cyan = left hand, orange = right hand, gray = confidence below 0.5. Screens and distant people are mosaicked. The wearer's hands stay visible.
  1. 01

    Now

    Now

    The 21 points from the raw frame enter the estimate, with the method specified. Points below 0.5 are marked invalid, not removed.

    The 21 points go into estimate with a method field. Points below 0.5 are marked invalid, not deleted.

  2. 02

    Items for Later Evaluation

    Potential follow-up evaluation

    WiLoR / HaWoR may serve as candidate methods for future use; inputs, scale, and error must be validated. These results are not currently delivered.

    WiLoR / HaWoR are potential methods requiring input, scale and error validation; their results are not currently delivered.

  3. 03

    Don't do

    Not done

    Do not express two-view disparity in meters. Do not substitute E6 device joints with a visual mesh. Do not present the paper's post-aligned millimeter figures as this segment's accuracy.

    Do not turn two-eye disparity into meters. Do not replace E6 device joints with a vision mesh. Do not treat a paper's aligned millimeter score as this take's accuracy.

18/21Left Hand Valid PointsLeft Joints Kept
15/21Right-hand valid pointsRight joints kept
0.5Confidence thresholdConfidence Gate
estimateNot a device outputNot a device output

This frame comes from the publicly released E2 sample left eye, file sequence number 0120; the exposure timestamp was not re-read. Another original clip (uid 532f0cf9a78d, not 20260917) was processed the same way for 613 seconds on each eye: the left eye had a hand present for 593 seconds, and the right eye for 588 seconds. That 1 Hz coordinate does not replace the 30 Hz original clip.

This frame is the published E2 left eye, filename index 0120. The exposure time was not re-read. A different take (uid 532f0cf9a78d, not 20260917) was run the same way for 613 seconds on each eye: a hand is present on 593 left seconds and 588 right seconds. That 1 Hz file does not replace the 30 Hz source.

Information architectureArchitecture

device · estimate · human

The same capture session is split into three layers. Missing columns are left blank. Training reads the raw footage at native frame rate, not the 4 Hz / 10 Hz previews.

One capture splits into three namespaces. Missing columns stay empty. Train at native source Hz, not the 4 Hz / 10 Hz preview.

device

Written by the device

From the device

Only accept streams whose capture device or factory calibration is written into the file.

Only streams written by the capture device or factory calibration.

  • RGB / grayscale / IMU / magnetometer / audio
  • Head Pose · OpenXR Hands
  • Camera intrinsics and extrinsics · Time synchronization
  • RGB / grayscale / IMU / magnetometer / audio
  • Head pose · OpenXR hands
  • Camera intrinsics & extrinsics · time sync

estimate

Offline Algorithm

Offline algorithms

Must include method and state not_device_output.

Must carry method and not_device_output.

  • Vision 21-Point Hands · SGBM Distance
  • Mosaic · OCR
  • MediaPipe / RTMPose / HaMeR / FoundationStereo slots retained; not re-run on the original footage
  • Vision 21-point hands · SGBM distance
  • Mosaic · OCR
  • MediaPipe / RTMPose / HaMeR / FoundationStereo slots reserved, not re-run on source

human

Manual verification

Human review

Do not rewrite the sentence as detector output.

Sentences are never rewritten as detector output.

  • Narrative · Six-step keyframe sentence
  • Object time segment
  • Accept markers
  • Narration · six keyframe sentences
  • Object time spans
  • Accept flags

embodied_layers.v1.json E2 validity E6 validity vision_pipeline_v1.json

Layer descriptionLayer Notes

IMU · Distance · Detection

IMU · Distance · Detection

Device-sourced dataDeviceNot inferred from the imageNot from the picture

IMU Data

IMU data

The device's gyroscope and accelerometer provide angular velocity and linear acceleration. E2 gyroscope and accelerometer are approximately 799 Hz, magnetometer 200 Hz, and the sampled mean of acceleration magnitude is 9.83 m/s². E6 gyroscope and accelerometer are approximately 1015 Hz. E2 acceleration starts 124 milliseconds before the left-eye exposure start. The bottom curve of the distance chart comes from gyro.csv.

E2: these 682 seconds are split into 5-second windows by angular-velocity RMS. The median is 0.352 rad/s. Segments above 1.8× that persist for at least 10 seconds are drawn in orange. This is head-worn angular velocity — not hand motion, and not pose. The longest routine segment is 150–505 seconds; the highest segment in this clip is 595–605 seconds, with an RMS of 2.188 rad/s. Integrated heading drifts; this is not SLAM, and E2 has no head-pose file.

Device gyro and accelerometer record angular velocity and linear acceleration. E2 gyro/accel ≈ 799 Hz, magnetometer 200 Hz, accel magnitude subsample averages 9.83 m/s². E6 ≈ 1015 Hz. E2 accel starts 124 ms before left-eye exposure. The curve under the distance clip is gyro.csv.

The 682 s are split by 5-second gyro RMS (median 0.352 rad/s). Spans above 1.8× that median and ≥10 s are orange. That is head-worn rate, not a hand verb or pose. Longest usual stretch 150–505 s; peak 595–605 s at RMS 2.188. Integrated heading drifts — not SLAM; E2 has no head-pose file.

Orange: angular velocity increases. Gray: everything else. The 40–48 second sample falls in the second orange segment (30–100 seconds, RMS 1.818). motion_spans.jsonl

Orange: elevated rate. Gray: the rest. The 40–48 s sample sits in the second orange span (30–100 s, RMS 1.818). motion_spans.jsonl

Training access controlTraining gate

Cleanup: these do not enter the training columns

Drop what should not train

Do not delete the source files. The following are not written into the training columns, and do not fill them in with other values.

Source files stay. These do not enter a training column, and nothing is invented to fill them.

  1. Use 4 Hz / 10 Hz previews instead of the E2 30 Hz and E6 ~60 Hz original footage.
  2. Writing post-processing estimates as device-sourced data.
  3. Text confidence < 0.40, or fewer than two letters/digits.
  4. A human body bounding box covering both hands of the wearer.
  5. Fill in dummy values when depth, object 6DoF, or joint confidence are missing.
  6. In E6, joints with active ≠ 1 are treated as visible.
  7. Applying fixture time alignment without head pose (neither of these two segments applies it).
  8. Turn manual sentences into detector output.
  9. Interpolating to fill holes in failed stereo matching pixels.
  10. Run triangulation with at least three views using two cameras, or write out the 3D hand when no left-right corresponding joint is available.
  11. Fill the temporal gaps in the hand index with smoothing, then treat the result as recognized trajectories.
  1. Train on the 4 Hz / 10 Hz preview instead of the native source Hz.
  2. Write a later estimate as a device measurement.
  3. Drop text below confidence 0.40, or with fewer than two letters or digits.
  4. Person boxes that cover the wearer's hands.
  5. Invent depth, object 6DoF, or joint confidence when absent.
  6. Treat E6 joints with active ≠ 1 as visible.
  7. Apply factory time alignment without head pose to check.
  8. Treat a human sentence as detector output.
  9. Fill stereo match failures with interpolation.
  10. Run a three-or-more-camera triangulation on two eyes, or write a 3D hand without left-right joint correspondence.
  11. Smooth across a gap in the hand index and call the result a recognition track.

ComparisonCompare

Split by Output Format

By output format

The preview mp4 is for verification. Training reads the raw video and index.

The preview mp4 is for checking only. Training reads the source video and indexes it.

FormatE6E2
Raw videorgb / tracking / ctrl, on the order of 60 HzCamera0, Camera1, 1600×1200, 30 Hz
Preview10 Hz, starting at 22 seconds, with joint projection and audio4 Hz annotated clip with audio; an unannotated side-by-side clip is also available
Time indextime_sync.json · rgb_index.jsonltime_sync.json · stereo_index.jsonl
Handhands_flags.jsonl + hand_openxr_device.jsonhand_2d_vision21.json + e2-findings.jsonl
Sentencenarration.jsonl · e6_keyframe_step.v1.jsonnarration.jsonl
Objectobject_spans.jsonlNo category box
Validitye6 validitye2 validity
FormatE6E2
Source Videorgb / tracking / ctrl, about 60 HzCamera0 and Camera1, 1600×1200, 30 Hz
Preview10 Hz from record 22 s, with joint projection and audio4 Hz annotated preview with audio, plus an unannotated side-by-side
Time indextime_sync.json · rgb_index.jsonltime_sync.json · stereo_index.jsonl
Handshands_flags.jsonl + hand_openxr_device.jsonhand_2d_vision21.json + e2-findings.jsonl
Sentencesnarration.jsonl · e6_keyframe_step.v1.jsonnarration.jsonl
Objectsobject_spans.jsonlNo class boxes
Validitye6 validitye2 validity

Break down by algorithm requirements

By algorithm need

Deliver whichever file the customer requests; do not write estimates as device-sourced data.

Take the file that matches the need. Do not write an estimate as a device measurement.

Inputs to be trainedUse E6Use E2
How the hands moveDevice OpenXR 26 joints, approx. 19 HzVision 21 points, estimated
Where is the headhead_pose.csv, 60 HzNo head pose; gyroscope integration will drift
One-line scenarioFour manually narrated sentencesOne Human Narrative
Text and PrivacyThis page preview has no detection-level watermarkingFaces, distant human bodies, text ≥0.40, bright screens, blue labels
DistanceParallax-free preview; SLAM 5 mm nominalSGBM + LR + confidence; FoundationStereo not run
Audio44.1 kHz mono, +288 ms16 kHz stereo, +97 ms
Input to trainUse E6Use E2
How the hands moveDevice OpenXR 26 joints, about 19 HzVision 21-point estimate
Where the head ishead_pose.csv, 60 HzNo head pose; integrated gyro drifts
One scene sentenceFour human sentencesOne human sentence
Text and privacyThis preview is not detector-maskedFaces, distant people, text at 0.40+, bright screens, blue wall marks
Near and farNo disparity on the preview; the 5 mm SLAM figure is nominalSGBM + left-right check + confidence gate; FoundationStereo not run
Audio44.1 kHz mono, +288 ms16 kHz stereo, +97 ms

Neither segment contains contact force, object 6DoF, or robot end-effector action. E6's grayscale tracking and downward-facing ctrl are present in the observations; ctrl is not controller pose (the controller file is a single line of zeros). E2 does not have these grayscale cameras.

Neither episode has contact force, object 6DoF, or robot eef action. E6 grayscale tracking and downward ctrl are observations; ctrl is not controller pose. E2 has no grayscale cameras.