Task descriptions
A concise account of what the demonstrator is trying to complete, including the relevant object and starting condition.
Data annotation & review
Collection quality depends on a shared definition of a usable recording. We agree the checks and label rules during the pilot, then apply them to the larger collection. Annotation depth is scoped to the project.
ANNOTATION / CHOOSE THE USEFUL SIGNAL
The label vocabulary and granularity should follow the research question. Agree examples and ambiguous cases before a larger annotation effort.
A concise account of what the demonstrator is trying to complete, including the relevant object and starting condition.
Start and end times for agreed steps such as pick, align, fasten, inspect or place.
Agreed descriptions of how hands, tools and objects relate during a task. Granularity is established with examples.
The fields needed to understand the recording setup and connect each file to the task matrix.
CONSISTENCY / BEFORE VOLUME
Begin with a small set of representative clips and a written label guide. Define action boundaries, object names, uncertainty handling and examples of what should be excluded. Review disagreements before extending the work.
THE HANDOFF
Agree the schema and delivery format your team can use. The handoff can be scoped around task descriptions, temporal segments, project metadata and review outcomes.
Depth, IMU, multi-camera synchronisation, 2D/3D tracking and robot control trajectories are distinct requirements. They need their own collection, processing and acceptance discussions.
Explore an illustrative annotationTell us what you want recorded. We can discuss the skill, environment, camera setup, annotation and budget in a scoping meeting.