Task family

Egocentric Event Venue Setup and Teardown Video Data

Arranging tables and chairs into a layout, setting up and tearing down staging and equipment, routing cables and sweeping the room afterwards, captured first-person in event venues against a spec you write, for event setup robot training data and fast, on-demand custom venue data collection.
Venue tasks
Eight catalog rows
Status
All Ready to deploy
Billing
Per validated hour
License
Buyer-owned

Requirements

What does event venue setup and teardown data need?

01

A named setup and teardown task list

Arranging tables and chairs, setting up and tearing down staging, setting up equipment and lighting, routing cables and sweeping are different sequences, so a spec names each one and the room it covers.

02

Both hands and the layout in frame

A head-mounted view keeps both hands, the item being moved and the floor it lands on in view for the whole step.

03

Hand pose through every carry and place

3D hand pose with per-joint visibility carries how the fingers lift, steer, position and release each item, item after item.

04

Step boundaries on the same clock

Frame-accurate action segments mark where carrying ends, where positioning starts and where each item is locked, aligned or stacked.

05

Rights you can ship on

A perpetual, buyer-owned commercial license backed by a documented consent chain.

Why it matters

What is egocentric event venue setup and teardown data, and why does it need its own page?

Egocentric event venue setup and teardown data is real-world, first-person video of the physical work that readies an event room and clears it afterwards. It is recorded from the worker viewpoint, with depth, 3D hand pose, contact events and frame-accurate action segments aligned on one hardware clock. The tasks are the ones the site states under its Event Venue catalog environment.

It is room work, not event footage. None of the eight rows describes a guest, an attendee or an audience, and this page does not describe capturing event guests or audiences. This page is about the room itself: laid out, equipped, taken down and swept.

Setting

Which setup and teardown tasks can be captured?

The site states event work in one catalog environment, Event Venue, under the Hospitality & Events sector. Its examples line reads "Conference halls, wedding venues, stages and banquet rooms." Eight task rows sit under it. Five are rated Easy and three are rated Medium, and every one lists a head-mounted phone or multiview rig as the capture mode.

All eight rows carry the status Ready to deploy. The site defines that status as contributors and site access set up, with capture starting once a spec is signed. Words such as tables, chairs, platforms and cables are catalog wording for item types, not models.

Tables and chairs

How are the table and chair rows described?

Two rows cover layout work. The first reads the layout plan, rolls tables in on carts and positions and aligns tables and chairs, and it is rated Easy. The second, Table & Chair Arrangement, moves and arranges tables and chairs into the event layout and aligns rows, and it is also rated Easy. The catalog lists them separately and does not say how they differ.

The site states no layout plan format, no room size, no table or chair counts and no row spacing, so those are Not stated and are set in the spec. A spec should say whether a plan is provided, how many items go in and what counts as aligned, because the catalog does not.

Staging and equipment

How are the staging and stage and equipment rows described?

Two Medium rows cover staging. One carries staging platforms in on hand trucks, locks them together, then dismantles and stacks them. The other, Stage & Equipment Setup / Teardown, assembles stage decks, sets up equipment and lighting, then tears down and packs after the event. Both describe a build followed by its reverse.

The site states no stage size, load rating, rigging method or equipment list, and this page makes no stage-engineering or safety claim. Deck counts and packing order are Not stated.

Cables

How are the cable rows described?

Two rows cover cables. AV & Cable Management is rated Medium and runs cables to gear, tapes them down, positions speakers and screens and connects equipment. The routing row is rated Easy and lays cables along walls and walkways, covers them with ramps and tapes them down.

The site states no cable types, lengths, connection standards or signal specifications, so none is claimed. Cable work has its own page, linked below.

Room reset

How are the venue sweep rows described?

Two Easy rows reset the room. One sweeps the venue floor, bags trash and recycling and carries the bags to the dumpsters. The other, Trash & Recycling Sweep, walks the venue collecting trash and recycling into bags and sweeping up debris. They are the cleanup end of teardown.

The site states no waste volumes, bag counts or disposal rules. The trash and recycling page, linked below, covers these two rows in more depth.

Environments

Where is it captured and how are workers protected?

The catalog places the work in the settings its examples line names, conference halls, wedding venues, stages and banquet rooms, and the environment page states that contributors are recruited to spec in Western program markets, so the footage reflects how this work is done in North American and European businesses. The site names no venue, operator or region. Access and schedule are agreed in the spec, and the number of sites is Not stated.

The privacy steps the site states are these. Every episode links to a signed contributor release through a documented consent chain, and the consent record is part of the delivery. Faces, plates and screens are detected and irreversibly blurred at ingest, a reviewer confirms the result before anything ships, and the anonymization record is delivered with the data. The site states no venue-specific bystander rule, so how people who are present are handled is settled in the spec. Attendance, capacity and PPE rules are Not stated.

Capture setup

How is venue work captured from a first-person view?

A head-mounted phone records the first-person view of real work on site, and a multiview rig adds synchronized third-person angles when the spec asks for them. All eight venue rows list this single setup. On the rig tier, every stream is hardware-triggered onto one PTP clock domain, and the rig is calibrated twice per session, before capture starts and after it ends. An episode is accepted only if RMS reprojection stays under 0.28 px.

Camera count, resolution and frame rate for venue work are Not stated, so session length and volume are quoted against your spec.

Streams and labels

What does each venue episode contain?

Each episode follows the Firsthand episode schema: ten streams synced under 2 ms, with head and wrist RGB, depth, 3D hand pose with per-joint visibility, contact and grasp events, and frame-accurate action segments. In a venue, hand pose tracks how the fingers lift and place each item, contact events mark touches on a table edge, chair back, platform edge, cable or bag, and action segments mark each step.

Object labels use the terms your spec sets. Force or tactile data, and success or quality labels, are Not stated for these rows. If your policy needs them, they are defined in the spec. Tactile gloves are a separate capture tier with their own page.

Delivery

How is the data labeled and delivered?

Delivery formats are RLDS, LeRobot and WebDataset, plus HDF5, zarr and Rerun .rrd. The format table below sets each against what its official documentation states. Action segments are the step labels, and any further object labels follow the spec.

Every batch is validated against signed accept criteria before it ships, with a reject log, and delivery is rolling, per validated batch. Billing is per validated hour, and rejected items are recaptured at our cost.

Why it is hard

Why are stacking, unfolding and room resets hard for robot learning?

The site states no robot results for venue work, so this section describes what the work asks of a dataset, not what any policy achieves. The catalog describes work that comes in pairs. Staging is carried in, locked together, then dismantled and stacked, and the stage row is assembled, equipped, then torn down and packed. A single task therefore contains a build and its reverse, with the same items handled in a different order.

Layout rows add alignment, because items are positioned into rows rather than just moved, and cable rows add long, thin items laid along walls and walkways. Moving from carrying to locking to packing without a break in the recording is hard to cover with a few recordings, so a spec names the tasks, item groups and number of sequences. Cycle times, repetition counts and error rates are Not stated.

Fast · on demand

How fast can a custom venue dataset be collected?

Where coverage is already deep, the first validated batch lands in a median of 48 hours from signed spec. Thin environments typically take three to four weeks, because vetting operators there is the bottleneck, and we quote that up front. The site does not state which of the two applies to venue work.

All eight venue rows are Ready to deploy, so contributors and site access are set up and capture starts once a spec is signed. The timeline is still quoted against your spec.

The spec

How do you start a pilot?

You describe the venue tasks, item groups and sequence your policy needs. We turn that into a written spec covering tasks, environments, capture tier, annotation depth and accept criteria, then quote reach, timeline and price before any capture begins.

A Spec Pilot, a small and fast first batch, can prove the spec and accept criteria before you scale. Billing is per validated hour, a reject log ships with every batch, rejected items are recaptured at our cost, and every collection ships under a perpetual, buyer-owned commercial license.

At a glance

What you get.

Every collection runs through the same seven-stage end-to-end custom collection pipeline. End-to-end custom data collection is a managed service that takes an AI data need from problem to owned dataset in a single accountable pipeline.

Catalog rows

Which catalog rows cover event venue setup and teardown?

The eight Event Venue rows with the catalog description, skill rating and status as listed. Every row lists a head-mounted phone or multiview rig as capture mode.
Task familyCatalog task and descriptionSkillStatus
Tables and chairsArrange and align tables and chairs using layout plans and dollies: read the layout plan, roll tables in on dollies and position and align tables and chairsEasyReady to deploy
Tables and chairsTable & Chair Arrangement: move and arrange tables and chairs into the event layout and align rowsEasyReady to deploy
StagingSet up and tear down staging using folding platforms and hand trucks: carry staging platforms in on hand trucks, lock them together, then dismantle and stack themMediumReady to deploy
Stage and equipmentStage & Equipment Setup / Teardown: assemble stage decks, set up equipment and lighting, then tear down and pack after the eventMediumReady to deploy
CablesAV & Cable Management: run cables to AV gear, tape them down, position speakers and screens and connect equipmentMediumReady to deploy
CablesRoute and tape AV cables using gaffer tape and cable ramps: lay cables along walls and walkways, cover them with ramps and tape them down with gaffer tapeEasyReady to deploy
Room resetSweep and bag venue trash using brooms and liner bags: sweep the venue floor, bag trash and recycling and carry the bags to the dumpstersEasyReady to deploy
Room resetTrash & Recycling Sweep: walk the venue collecting trash and recycling into bags and sweep up debrisEasyReady to deploy

Streams and tasks

How do the stated streams map to venue tasks?

The streams the site states for Firsthand custom collections, set against what each carries in an event venue episode.
Stream or labelStatus on this siteWhat it carries in a venue episode
Head and wrist RGB, depthStated; ten streams synced under 2 msKeeps the item, the floor and both hands on one timeline
3D hand pose, per-joint visibilityStatedCarries how the fingers lift, steer, position and release each item
Contact and grasp eventsStatedMarks when fingers meet a table edge, a chair back, a platform edge, a cable or a bag
Action segmentsStated; frame-accurateSeparates carrying, locking, positioning, taping, packing, stacking and sweeping
Object labelsSet by your specNames the items and steps in the terms your policy uses

What is not stated

Which event venue details does the site not state?

Event venue fields the site does not state, and where each one is settled.
ItemStatus on this siteWhere it is settled
Furniture, equipment or tool models and listsNot stated; task rows name item types onlyThe written spec
Layout plan format, row spacing, item countsNot statedThe written spec
Room sizes, venue types, guest counts, attendance, capacity, regions, number of sitesNot stated beyond the examples line and Western program marketsThe written spec
Rigging, AV, stage-engineering or load detailsNot statedNot claimed on this page
Cycle times, throughput, repetition countsNot statedQuoted against your spec
Number of episodes or workers, safety certificationsNot statedThe written spec; certifications not claimed
Venue-specific bystander handlingNot statedThe written spec
Success or quality labelsNot statedThe written spec, if needed
Force or tactile dataNot stated for these rowsThe written spec, if needed
Robot or policy resultsNot statedNot claimed on this page

Formats

Which formats carry event venue data?

Delivery formats stated on the site, set against what each format official documentation states where the documentation was read.
FormatWhat the official documentation statesUsed for here
RLDSA dataset is retrieved as episodes, and each episode holds a dataset of steps (RLDS repository README)Episode-based training loaders
LeRobotLeRobotDataset v3.0 is a standardized format for robot learning data, including multi-camera video, with many episodes stored per Parquet or MP4 file (LeRobot documentation)LeRobot dataset format and tooling
WebDatasetTar files in which files that belong together share a basename, split into numbered shards (WebDataset README)Sharded streaming for large training runs
HDF5 and zarrStated by Firsthand onlyArray storage for custom pipelines
Rerun .rrdStated by Firsthand onlyMulti-stream synchronized playback for review

FAQ

Event setup robot training data, answered.

What is egocentric event venue setup and teardown video data?
Real-world, first-person video of the work that readies an event room and clears it afterwards, such as arranging tables and chairs, setting up and tearing down staging and equipment, routing cables and sweeping, captured against a written spec with 3D hand pose, depth and action segments.
Which venue tasks does the site state?
The task catalog lists eight rows under Event Venue: two table and chair rows, a staging row, a stage and equipment setup and teardown row, two cable rows and two sweep rows. Five are rated Easy, three Medium, and all are Ready to deploy.
Does the data show event guests or audiences?
No. The eight rows describe room work, and this page does not describe capturing event guests or audiences. How people who are present are handled is settled in the spec.
Does the site state room sizes, guest counts or stage details?
No. Room sizes, guest counts, capacity, rigging, AV and stage-engineering details, cycle times and safety certifications are Not stated.
Are force data or quality labels included?
Not stated for these rows. They are defined in the written spec if your policy needs them. The site states hand pose, depth, contact events and action segments.
How is privacy handled?
Faces, plates and screens are detected and irreversibly blurred at ingest, and a reviewer confirms the result. Each episode links to a signed contributor release, and the anonymization record ships with the data. Venue-specific bystander rules and PPE rules are Not stated.
How fast can a custom venue dataset be collected?
Where coverage is deep, the first validated batch lands in a median of 48 hours from signed spec. Thin environments typically take three to four weeks. All eight venue rows are Ready to deploy, and the timeline is quoted against your spec.
How do you start a pilot?
Describe the venue tasks, item groups and sequence you need. We write a spec, quote against it, and a Spec Pilot proves the accept criteria before you scale.

Sources

Where are the delivery formats documented?

Request a custom dataset.

Tell us the venue tasks, item groups and sequence your policy needs to handle. We will quote reach, timeline, and price against a written spec, with a first validated batch in a median of 48 hours where coverage is deep.