Stereo Electrical Installation Data

It is first-person video of a person doing electrical installation or wiring work, recorded from their own point of view with two calibrated cameras and with hand pose and sensor streams alongside. The tasks are the ones the site’s catalog lists for electrical installation, repair and outlet wiring. Stereo describes the capture, and MCAP describes the container. They are separate choices.

The site does not state that stereo is already running on these rows. The catalog lists a head-mounted phone or a multiview rig as the capture setup, and a stereo pair is a capture choice agreed in the skill spec and confirmed on a Spec Pilot. The data is human capture by paid, consented contributors, not robot or teleoperation data. Firsthand is not affiliated with Foxglove or the MCAP maintainers.

The egocentric electrical work page covers the tasks: the same five catalog rows, the episode contents, the labels, privacy and delivery. This page does not repeat it. It covers the two choices layered on those rows: a calibrated stereo pair for depth, and MCAP as the delivery container.

The cable routing and wiring page covers routing, clipping, patching and crimping across benches, racks and venues, which is a different set of rows. The stereo construction crews page covers the Active Construction Site environment as a whole, where electrical installation is one trade among fifteen task rows. Here the electrical rows from four environments sit together, because a trade-service lab wants installation, repair and outlet wiring in one specification. No voltage, wire gauge, circuit rating or code figure appears on this page, because the site states none.

Five rows count, in four environments. Active Construction Site lists Electrical installation. On-Site Home Repair lists Electrical repair call. Trade Service Calls lists two outlet rows, Outlet & Fixture Wiring and Strip and wire electrical outlets using wire strippers and a voltage tester. The Trades Workshop Bench lists Wire an outlet. The first table below reproduces each as the catalog states it.

Statuses are Active collection for the site row, Ready to deploy for the two service-call rows, and Available on request for the home repair and workshop bench rows. All five are rated Hard. The thermostat and control wiring row in trade service calls is a heating and cooling control task and is left out. The site names no building, brand, electrician, circuit or tool model for any row.

Electrical work is about the state of a connection: whether a conductor has been stripped, whether it sits on a terminal, whether a device is seated in its box. A stereo pair recovers depth from the calibrated frame pair rather than from a standalone depth sensor, so the shape of the part sits in the same frame as the hands. The site gives no depth accuracy figure for these rows and no connection-quality label, so what a buyer does with that depth is their pipeline’s question.

The site’s stereo material also says that in a glare-heavy or low-texture scene a single-frame depth guess gets worse, and that a calibrated pair measures disparity between two views at a fixed, known baseline instead. It adds that stereo keeps working outdoors where active depth sensors struggle. Whether an electrical job is indoors or on an open site is not stated beyond the environment names.

The rows describe mounting boxes and wiring outlets, switches and fixtures. They do not name wall cavities, ceilings, ladders or clearances, so this page does not either. What the site does state is the framing risk that comes with close work: an episode is rejected when the manipulated object is out of frame for more than 15 percent of it.

Where a job is mostly inside or behind something, the head camera keeps the hands in frame, a wrist view adds a closer angle on request, and the calibrated pair records how far the device and the surface sit from the lens. The site states no accuracy figure for depth at close range and no space dimensions, so none is promised here. If the work is mostly hidden, say so in the spec so the wrist view and the framing rule are planned together.

The site states 3D hand pose of 21 joints per hand with a per-joint visibility flag, and contact and grasp events that mark when fingers meet a tool or a part. In electrical work that is the grip on wire strippers, the pinch of a stripped wire, the hold on a device while it is seated and the fingers steadying a part while the other hand works.

These are the moments a head camera loses most often, because the device or the tool sits between the lens and the fingers. A spec can ask for a wrist view so a grip the head camera loses is still recorded, and the visibility flag marks the joints that were hidden. The site states no torque, grip-force, terminal-tightness or tool-pose stream, and does not say whether a wire or a device counts as the object in a contact event, so settle that in the spec.

Two rows name a voltage tester. Outlet & Fixture Wiring says to “test with a voltage tester with power off”, and the strip-and-wire row says to “verify with a voltage tester”. Those are descriptions of the task the contributor performs. The remaining rows say “test” or name no test, and the site states no power state for them.

The site lists no voltage, current or test-result stream, and no label for whether a test passed. A tester in frame is therefore visual evidence that a step happened, not a delivered measurement. If a program needs a test outcome as a label, that is a scoping conversation settled in the spec. This page makes no safety, procedure, lockout or compliance claim, because the site makes none.

The site describes two stereo setups and does not say which one an electrical order uses. The hard-environments stack is a global-shutter 4K/60 head camera with a 120° lens, two 1080p/60 wrist cameras, a depth sensor at 848×480 and 30 fps, and 200 Hz 6-DoF IMUs. The off-the-shelf stereo head rig, dataset 06, is dual fisheye cameras at 1080p per eye, a 62 mm baseline, per-unit calibration, a 9-axis IMU and hand-tracking output.

The catalog lists a head-mounted phone or multiview rig for four of the five rows and a multiview rig with handheld grippers for the workshop bench row. Which rig, resolution and streams an electrical order uses is Not stated, and the second table below sets what is stated beside what is not. Intrinsics and extrinsics are re-solved at the start and end of every session, and streams are hardware-triggered onto one clock with a 2.0 ms cross-stream ceiling.

Glare and low texture are the first risk. The site notes that glare-heavy and low-texture scenes make single-frame depth worse, and that depth degrades on wet and reflective surfaces while confidence maps mask the low-confidence regions. An episode is rejected when more than 35 percent of depth pixels in the manipulation region are invalid. The site does not say how depth behaves on a bare conductor end or a metal tool face, so this page promises no figure. It states a low-light share only for its automotive dataset, so lighting handling for electrical rows is Not stated.

Occlusion and motion blur are the second. The head camera is global-shutter, which avoids rolling-shutter skew, and the site notes that reach and grasp frames are where blur and occlusion show up. Hand pose carries a visibility flag for joints a device or a tool hides. Calibration is the third, because stereo depth is only as good as the rectification behind it: it is measured at the start and end of every session under a 0.28 px RMS gate.

Framing and bystanders are the fourth. An episode is rejected when the manipulated object is out of frame for more than 15 percent of it, or an undocumented bystander appears. The third table below sets each risk beside the site’s handling. No connection-quality, termination or test-result label is listed on the site.

Every batch is validated against signed accept criteria before it ships, a reject log ships with it, and rejected items are recaptured at our cost. Delivery is rolling, per validated batch, and billing is per validated hour. Each 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, and a reviewer confirms the result before anything ships. Footage with bystanders who cannot be de-identified is discarded. The rows set electrical work in a client’s home and at client sites, and the site does not state a separate rule for a household, a client’s documents or labels on equipment, so settle the privacy rule for the space in the spec before capture. The site makes no safety, protective equipment, licensing or compliance claim for any electrical environment, and neither does this page.

MCAP is an open source container file format for multimodal log data, supporting multiple channels of timestamped pre-serialized data. It is serialization-agnostic, so messages can be Protobuf, DDS (CDR), ROS, JSON and more. Its design is row-oriented and append-only, it stores schemas alongside the data, and it offers an optional index plus optional LZ4 or Zstandard chunk compression, with optional chunking and CRC checksums.

Native reader and writer libraries exist for C++, Go, Python, Rust, Swift and TypeScript, and the mcap CLI can inspect, merge and split files. The foxglove/mcap repository is MIT-licensed; that is the MCAP project’s licence, not the licence of a Firsthand delivery. The MCAP hub page and the glossary entry cover the format in full.

Firsthand offers MCAP delivery, and dataset 06 is stated as shipping as MCAP. For electrical work the site states a stereo pair, a stereo-derived depth stream with confidence maps, hand pose, IMU, contact events, action segments and calibration elsewhere. What it does not state is which of those are channels in an MCAP file, how they are named, what encoding they use or at what rate.

No topic name, message schema or rate is stated on this page, and none should be assumed. Name the streams that matter in the skill spec and confirm them on a Spec Pilot batch. The fourth table below sets each stream beside what the site states about it.

The site states delivery in RLDS, LeRobot and WebDataset, plus HDF5, zarr and Rerun .rrd, and MCAP can ship alone or beside any of them. Electrical episodes follow the same episode schema as every other Firsthand collection, so a loader that reads another Firsthand dataset reads this one without changes. In the HDF5 layout the site documents, hand pose sits at annotations/hand_joints and action segments at annotations/action_segments.

Which container suits a lab depends on its reader and its training loop, and the site does not rank them. The compare page on MCAP and HDF5 sets the two side by side, and the delivery formats guide covers the rest. Say in the spec whether MCAP is the only delivery or sits beside a training format.

Off-the-shelf covers what is already in stock: the stereo category lists the stereo datasets and hand-tracking video, and only dataset 06 is stated as MCAP. This page does not claim off-the-shelf coverage of the electrical rows. A lab can use the stock stereo footage to check the rig and the format first, then commission the electrical tasks it needs. Custom collection covers the rest: custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs.

Where coverage is deep, the median time from signed spec to first validated batch is a median of 48 hours; where it is thin, turnaround runs three to four weeks. The site does not say which coverage level applies to a given row or setting, so ask when you request the quote. Collections are billed per validated hour, and capture at your own facility is listed as not offered. The supply page covers how a recurring flow is set up.

Describe the sequence your policy needs: for an outlet, strip the wires, connect them to the terminals, verify with a voltage tester; for an installation, mount the box and wire the device. State what counts as a completed step, the setting, and the variation your pipeline is missing. Then name the streams you want in the file, the topic naming and message encoding your reader expects, whether calibration ships inside the file or beside it, and whether MCAP is the only delivery or sits beside RLDS, LeRobot or WebDataset.

Most programs begin with a Spec Pilot, a small first batch that proves the spec and accept criteria on real footage before you scale. Voltages, wire gauges, circuit ratings and tool models are agreed in the spec because the site does not state them. The fifth table below shows what each spec element decides.