Requirements & feasibility
Define the learning or evaluation objective, workflow, objects, target environments, market, participants and intended use. Identify specialist access and whether the required signals can be captured.
Buyer-directed recording programs for human activity data. Specify what your model needs to observe; agree feasibility, access, protocol and acceptance before collection.
Define the learning or evaluation objective, workflow, objects, target environments, market, participants and intended use. Identify specialist access and whether the required signals can be captured.
Agree accepted-hours definitions, equipment, perspectives, resolution, frame rate, annotation, privacy boundaries, licensing, review criteria and re-recording policy.
Record a representative permitted sample under the proposed setup. Review visibility, task completion, file compatibility and label quality. Resolve gaps before expanding scope.
Capture the agreed variations. Track files and decisions against the protocol. Separate accepted footage from rejected footage and any approved re-recordings.
Package accepted footage, agreed annotations, metadata and review records. Include the agreed rights and permission documentation; verify the manifest and delivery method.
Agree the schema and evidence needed to evaluate a batch. The deliverable is defined in the proposal, including what is not captured or measured.
Accepted recordings can be paired with task IDs, recording conditions, camera information and review outcomes. Optional annotation layers are scoped against your requirements.
Human RGB video does not automatically include 3D pose, depth, force or executable robot trajectories. Sensor streams and derived labels require a suitable rig and separate validation.
collection-example/ # illustrative
footage/ # accepted video files
metadata/ # clip and capture records
annotations/ # if commissioned
review/ # QA decisions and reasons
documentation/ # datasheet and agreed rights
manifest.json # agreed file indexThe brief should define what must be visible and what must be measured. More cameras are useful only when they solve a real visibility or synchronization need.
| Setup | Useful for | Check in the pilot |
|---|---|---|
| Egocentric / first-person | Operator perspective and tool selection | Head movement, occlusion, field of view and task continuity |
| Fixed / overhead | Stable visibility of hands, parts and work surface | Reach boundaries, shadows, tiny objects and obstruction |
| Multi-view | Complementary coverage of complex interactions | Camera calibration, synchronization and shared identifiers |
| Additional sensors | Specific depth, motion or tactile requirements | Rig feasibility, measured performance and annotation validity; separately scoped |
Commercial terms depend on specialist recruitment, site access, rig complexity, accepted hours, annotation depth and review effort. Pilot scope and timing are agreed before collection starts.
Prepare a project briefThe buyer defines the task, intended use and test for success. Taktfield assesses the proposed site, permissions, safety, equipment and cost. The parties then agree a written scope or revise the brief.
The pilot agreement defines the unit of delivery, review sample or coverage, feedback window and limits on corrections. Any larger collection is a separate decision after pilot review.