Egocentric Electrical Work Video Data

Egocentric electrical work video data is first-person video of a person doing electrical wiring tasks, recorded from the contributor’s own point of view with synchronized sensor streams alongside. The camera sits on the head, close to what a robot’s onboard camera would see at a wall, a fixture or a bench, so the frames show what the hands are doing to the wire, the device and the terminal rather than a distant view of someone standing near a job. On this site it is a custom collection: you name the task and the setting, and capture is run to a written skill spec.

The catalog describes the tasks in its own words, for example "Run cable, mount boxes and wire outlets, switches and fixtures on a construction site" and "Strip wires, connect outlets and fixtures and test with a voltage tester with power off." This page repeats those descriptions as written and adds nothing to them. The data is human capture: a paid, consented contributor wears the rig and performs the task. It is not robot or teleoperation data, and it is not a fixed corpus you download.

People reach this topic through several phrasings: electrician robot training data, an electrical installation video dataset, egocentric wiring and outlet work data, or custom trade task data collection. They describe one request from different angles. Under each of them the work is the same: write down the task, collect it on demand, and receive validated episodes with the labels a training pipeline expects.

This page is narrower than the cable routing and wiring page, which covers routing, clipping, patching and crimping across benches, racks and venues, and narrower than the construction trades page, which covers the whole sector. The subject here is the electrical rows only. The catalog also lists thermostat and control wiring in the same trade service calls environment, but that is a heating and cooling control task and is left out.

Five rows of the site’s commercial task catalog describe an electrical wiring or repair step. The first table below reproduces them exactly as the catalog states them, with the environment, skill level, capture setup and status. All five are listed as Hard, and all five sit in the Construction & Trades sector, spread over four environments.

On an active construction site the catalog lists one row, electrical installation, with the status Active collection and a head-mounted phone or multiview rig as the capture setup. In on-site home repair it lists an electrical repair call: "Diagnose a fault in a client's home, replace the failed switch, socket or breaker and test." That row is Available on request. In trade service calls it lists two rows, outlet and fixture wiring, and stripping and wiring electrical outlets with wire strippers and a voltage tester. Both are Ready to deploy. At the trades workshop bench it lists wiring an outlet, "Strip wires and land on terminals," which is Available on request and is captured with a multiview rig and handheld grippers.

The statuses are the catalog’s own: Active collection, Ready to deploy and Available on request. The catalog is a list of what is captured or available, not a ceiling on what can be briefed. A circuit type, fitting, wiring step or setting outside these rows is a skill-spec question to settle in a Spec Pilot rather than an assumption. The site does not describe a voltage, a circuit type, a wire gauge, a fitting list or a task duration for any of these rows, so none is stated here.

Each attempt is delivered as one episode. For the instrumented tier the site describes a head-mounted stereo rig that records first-person RGB, with a metric depth stream recovered from the calibrated stereo rig rather than from a standalone depth sensor, and 6-DoF IMU data at 200 Hz from head- and wrist-mounted sensors. The wider stack is ten streams: a 4K head camera, two wrist cameras, depth, IMU, 3D hand and body pose, instance segmentation and action labels, hardware-aligned under 2 ms. The catalog lists the capture setup per row: a head-mounted phone or multiview rig for four of the five, and a multiview rig with handheld grippers for the workshop bench row. Which tier a program uses is set in the skill spec.

Hand pose is delivered for both hands as 21 joints per hand in three dimensions, with a per-joint visibility flag for occluded fingers. Wiring is close work: a hand closing around a wire or an outlet terminal hides fingers, and the flag marks the joints that were not visible instead of presenting a guess as a measurement. Contact events mark when a hand meets the item.

Every stream is hardware-triggered onto one PTP clock domain, so depth, motion and hand pose line up with the same video frame rather than being approximated afterwards. The rig is calibrated twice per session, and an episode is accepted only if RMS reprojection stays under 0.28 px.

The only language field the site ties to Firsthand capture is one task instruction per episode. The site does not list a voltage, current or electrical-test stream for these rows. This is human first-person capture, not robot or teleoperation data.

Inside each episode, action segments divide the timeline into spans, each carrying start_ns, end_ns, verb and noun. For this task family a segment can be one step as written in the skill spec, such as stripping the wires, landing them on terminals and testing, so one outlet job becomes a sequence of labeled steps rather than one long clip. The other standard fields are hand_joints and hand_visible for 3D hand pose, contact_events, objects, and per-frame instance masks where the spec calls for them, stored at the depth resolution of 848×480 so they line up with the depth stream.

Delivery is in the format your stack already reads: RLDS, LeRobot, WebDataset, HDF5, zarr or Rerun .rrd, or raw streams with metadata. The official sources describe three of these in their own terms. The RLDS repository describes an ecosystem of tools to store, retrieve and manipulate episodic data, including for learning from demonstrations and imitation learning. The LeRobot repository describes its dataset format as synchronized MP4 videos or images for vision plus Parquet files for state and action data. The WebDataset repository describes tar files in which files that belong together share the same basename and make up a training sample. In the HDF5 layout the site documents, hand pose sits at annotations/hand_joints and action segments at annotations/action_segments.

The site does not list labels for the quality of electrical work. There is no stated label for whether a connection is correct, whether a termination is tight or whether a test passed. Two catalog task descriptions mention a voltage tester, but that describes the task the contributor performs, not a delivered measurement. The verb and noun on each action segment is the vocabulary the skill spec defines with you, and anything beyond it is a scoping conversation, not a delivered field.

The GR00T N1 paper structures its training corpora as a data pyramid. In its words: "large quantities of web data and human videos lay the base of the pyramid; synthetic data generated with physics simulations and/or augmented by off-the-shelf neural models form the middle layer, and real-world data collected on the physical robot hardware complete the top." In that framing, first-person human video of electrical tasks would belong to the human-video base. Human capture does not replace robot data, and this page does not claim that it does.

The same paper says of the human video datasets it used: "These do not include explicit action labels but contain extensive sequences of human-object interactions." That is a statement about those datasets, not about this one. A Firsthand episode carries labeled action segments, 3D hand pose and contact events, so the structure of the step is explicit in the data. No model named on this page was trained on Firsthand data, and this page does not suggest otherwise.

Electrical wiring is a useful family to specify because it is made of small, ordered, close-contact steps: strip, connect, verify. The catalog files all five rows under Construction & Trades and rates all five as Hard. This page does not claim that any robot performs electrical work, that any model improves from this data, or any result.

Public corpora are captured for someone else’s task distribution. A custom collection lets you aim at the outlet, switch or fixture step your model is missing instead of hoping a public release contains it. This page does not claim that any particular public corpus lacks electrical work. It makes the narrower point that a custom spec lets you name what you need and have it captured, labeled and checked to terms you agreed.

The catalog names the settings for these rows in its own words: an active construction site, "a client's home" in on-site home repair, "client sites" for trade service calls, and a workshop bench with hand and power tools. The site does not state whose premises any row is recorded on, how a site is arranged, or whether a given row is recorded on a live job or on a staged set, so this page does not either. It also does not state site types beyond those names, site counts, or regions or cities for these rows.

Every contributor signs a written release before capture, and each delivered episode links to that record through consent artefact IDs in the batch data card. At ingest, automated detection finds faces, plates and screens and blurs them irreversibly, and speech is scrubbed of names, addresses and card numbers. A human reviewer confirms that no un-consented person is identifiable in any frame, and footage that cannot be de-identified is discarded. An undocumented bystander is also a machine-checked reject criterion. The anonymization record is delivered with the data.

If your program needs terms about premises, access or who may be in frame, raise them when you scope it. On safety, the site states nothing about electrical safety, code, licensing, qualification or certification for these rows, and this page makes no such claim. One row says "with power off"; the other rows do not state the power state, and this page says no more than the rows do. None of this is legal advice, and the executed agreement controls.

From signed spec to first validated batch, the site states a median of 48 hours where coverage is deep and three to four weeks where it is thin and contributors need to be recruited first. The site does not state which of those applies to the electrical rows, so that is settled in your quote. Speed comes from a warm pipeline, not from cutting consent, review or anonymization. After the first batch, on-demand top-ups run against the same accept criteria, and the site does not state a turnaround for those later batches.

Validation runs against signed accept criteria written into the spec before capture. An episode is rejected for a sync breach beyond the ceiling for more than three consecutive frames, calibration drift beyond tolerance, the manipulated object out of frame for more than 15 percent of the episode, more than 35 percent invalid depth pixels in the manipulation region, an undocumented bystander, or a mismatch against the named skill spec. A human reviewer then checks each episode against the task spec. A reject log ships with each batch, only footage that clears the criteria is billed as a validated hour, and rejected items are recaptured at the provider’s cost.

The license is perpetual, irrevocable and worldwide, with the data buyer-owned and non-exclusive by default. Training, evaluating, fine-tuning and deploying models, including commercial ones, is permitted, and exclusivity is available as a separate term. The executed agreement controls. The site does not publish a price list, a minimum order or a batch size for this task family, so those are set in your quote.

Describe the electrical steps, the setting and the failure or variation cases your pipeline is missing. That becomes a written skill spec, quoted for reach, timeline and price before any capture begins, and most programs run a Spec Pilot first: a small, fast first batch that proves the spec and the accept criteria on real footage before volume scales. A published sample recording is on the sample data outputs page if you want to see the streams before you write a spec.

Three choices matter most for this family. Name the step and the item rather than a broad activity, using catalog wording such as "Strip wires and land on terminals," because that is what lets each step become one action segment. Name the setting and the capture tier, since the catalog lists a head-mounted phone or multiview rig for four rows and a multiview rig with handheld grippers for the bench row. And write the reject rule and the acceptance test first, so the batch is judged against terms you agreed.

Where this site does not state something, this page says "Not stated" rather than filling the gap. The final table separates what is delivered from what is not stated. There is no stated label for connection correctness, termination, or test outcome, no electrical-test stream, no safety, code, licensing or certification position, and no voltage, circuit type or wire gauge. Counts of episodes, hours, sites and contributors are not fixed numbers on this site. They are set in your skill spec.

The tradeoff to plan for is the embodiment gap between a human hand and a robot end-effector, which retargeting or pairing with robot data has to close. What you get is human first-person demonstrations in which the hands, the work and the step structure are explicit.