DMS & OMS · SYNTHETIC TRAINING DATA

Driver monitoring
video datasets

Custom synthetic in-cabin video for DMS and OMS models: driver fatigue, distraction, phone use and occupant behavior.

Fatigue & distractionDrivers & occupantsCustom annotations

Published driver-behavior video examples

These clips show examples already published on our homepage. A project sample establishes whether the requested scenario, visual quality, and labels meet your requirements.

DISCUSS YOUR DATA

Which scenarios does your model need?

Start with target behaviors and sample requirements. Agree the production scope, annotation format and acceptance criteria before scaling.

  • Scenarios: fatigue, distraction or occupant interactions
  • Requirements: viewpoint, duration, quantity and labels
  • Delivery: sample validation before a batch production plan

Requirements → Sample review → Production & delivery

chan@vwu.ai

Choose a starting point, or describe your requirements.

* Required. Used to assess and reply to your inquiry. Please do not include sensitive personal information. Information notice

INTERACTIVE CONCEPT

In-cabin gaze interaction

An original synthetic concept scene for interaction, not a model recognition result.

Original synthetic concept of an adult driver and front passenger in a dark blue cabin
In-cabin interaction concept
Original synthetic concept · Not a measurement
Move your pointer across the page

In-cabin scenarios to train and evaluate

Define the behavior taxonomy, positive and negative examples, and acceptance criteria before production. Scenario feasibility and quality are checked during sample validation.

01

Driver fatigue and drowsiness

Specify visible fatigue cues and their duration. Agree what counts as a positive example, a subtle sign, or a normal behavior for the dataset.

02

Driver distraction

Describe the attention-related actions your model should recognize, such as looking away, looking back, or searching for an object. Define the required context and labels.

03

Mobile phone use

Request clearly specified phone-use actions, camera views, and scene variations. Keep the action definition consistent across generated clips and annotations.

04

Passenger and occupant behavior

Define passenger-driver interactions and rare safety scenarios. People, positions, actions, and timing are reviewed at the sample stage before batch production.

Control the variables your model needs

Specify the scene, video, and annotation requirements together. Select the variables that matter to your deployment, then validate representative combinations.

01

People and cabin

  • Occupant count and seating position
  • Driver and passenger roles
  • Vehicle type
  • Left- or right-hand-drive configuration
02

Capture conditions

  • Daytime, night, or dusk
  • Camera position and viewpoint
  • Lighting requirements
  • Action duration and timing
03

Video specification

  • Video duration
  • Resolution
  • Aspect ratio
  • Requested quantity
04

Annotations and metadata

  • Behavior and action labels
  • Temporal labels or video descriptions
  • Bounding boxes or keypoints as agreed
  • Project-specific label taxonomy and format

From requirements to an agreed dataset

Agree the deliverables and quality checks before scaling. Quantities, schedules, and annotation scope are confirmed for each project.

01

Define requirements

Share the target behaviors, cabin setup, camera view, clip duration, quantity, and annotation needs. Include how the dataset will be evaluated.

02

Validate a sample

Review a representative sample before batch production. Agree on scenario accuracy, visual quality, labels, and the delivery structure.

03

Generate, review, and annotate

Produce the agreed scenarios, review their content and video quality, check duplicates, and complete the annotation scope defined for the project.

04

Deliver and expand

Receive the agreed video files, annotations, and metadata. For validated scenarios, discuss additional people, environments, or action variations.

Before production, use the DMS and OMS training data procurement and acceptance checklist to define behavior labels, metadata and evaluation splits.

Video Specifications and Annotation

Define observable behaviors and delivery rules before quantity. These fields support requirements discussions; sample review establishes the project scope.

01

Video and camera specification

Define resolution, clip duration, frame rate, aspect ratio, viewpoint and lighting. Confirm quantity and schedule against the scope established after sample review.

02

Behavior and timing boundaries

Define onset, offset and overlap rules for fatigue cues, gaze changes, phone actions and occupant interactions. Label normal actions and unjudgeable intervals separately.

03

Example annotation fields

Illustrative fields: clip_id, actor_role, behavior, start_ms, end_ms, visibility, review_status. This is a requirements example, not an extract from a customer delivery.

04

Delivery and evaluation splits

Agree video files, labels, metadata and version notes. Group evaluation splits by person, scenario or generation setup so near-duplicate clips do not cross training and test partitions.

Sample Validation and Quality Assurance

Document acceptance checks, rejection reasons and re-review rules before scaling production.

01

Representative samples

Review ordinary, boundary and confusable scenarios together, including normal blinking versus sustained eye closure, and a mirror glance versus sustained attention away from the road.

02

Visibility and annotation review

Check occlusion, whether the action is visible, timing boundaries and label consistency. Mark unjudgeable intervals rather than forcing a positive or negative label.

03

Delivery file checks

Verify playback, duration, frame rate, duplicate clips, annotation-to-file references and the manifest. Record rejection reasons, corrections and re-review decisions.

04

Scope of evidence

Synthetic video can extend scenario coverage. It does not replace validation in the real deployment environment, establish a driver’s physiological state, or guarantee model-accuracy gains.

Questions before starting a project

Send your scenario list and delivery requirements through our existing data request form.

Is this a fixed dataset for download?

This service produces custom datasets from your training requirements. Use the published clips to discuss a sample; the final scope and deliverables are agreed for your project.

Can you cover rare passenger interactions?

Describe the people, actions, seating positions, and camera view you need. We assess the request and validate a sample before committing to batch production.

What annotation and video formats are available?

The homepage lists behavior labels, temporal labels, descriptions, bounding boxes, and keypoints. Specify the exact fields, resolution, duration, and output structure you need so the annotation scope and format can be confirmed.

How do you check whether the data is useful?

Agree acceptance criteria at the sample stage, including scenario accuracy, video quality, and annotation checks. Evaluate samples with your own model or review process before scaling; no model-accuracy improvement is promised.

How do I request a quote or sample?

Submit the scenario list, quantity, video specification, annotation needs, and target schedule through the data request form. Sample arrangements, price, timing, and usage terms are confirmed for the project.

Tell us what your DMS or OMS model needs

Share the behaviors missing from your current dataset. We will discuss a production plan and sample validation before scaling.

Video annotation and QA · Synthetic data production · Procurement guides