Stereo Handyman and Home Repair Data

It is first-person video of a person doing the repair calls the catalog lists, recorded from their own point of view with two calibrated cameras and with hand pose and sensor streams alongside. 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: 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 home repair page covers the same four rows with no stereo or MCAP content. The three stereo trade pages each cover one trade across several environments. Each lists only its own repair call row, and none lists the handyman row.

This page is the one that treats the four On-Site Home Repair rows together: one environment, four calls, with the stereo and MCAP layer on top. It states no brand, part spec, duration, standard or certification, because the site states none.

Four, all in the On-Site Home Repair environment under the Construction & Trades sector, described as a professional plumber, electrician, HVAC technician or handyman working in a client’s home. "Handyman repair call" reads "Fix doors, shelves, fixtures and minor damage in a client’s home with hand tools" and is rated Medium. "Electrical repair call", "HVAC service call" and "Plumbing repair call" are rated Hard. All four are Available on request and list a head-mounted phone or a multiview rig.

The steps on this page are the ones the rows name: diagnose or locate a fault, replace or fix, then test. The only tool named is hand tools, on the handyman row.

The environment is described as professional trades working in a client’s home. The site names no city, region, client or address, and does not state the number of residences, sites or episodes. Whose home is used, and under what access agreement, is set per program in the spec.

The rows do not say which capture mode applies to which row; a multiview rig adds synchronized angles when the spec asks for them.

A repair call is about a fixture and its surroundings: where the fault is and how the hand and tool approach it. A stereo pair recovers depth from the calibrated frame pair rather than from a standalone depth sensor, so the form of the fixture and the surface is in the same frame as the hands and the tool.

No depth accuracy figure, repair-quality label or test result field is stated.

The site describes two stereo setups and does not say which one a repair 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.

Which of these a repair call uses, and how a head-mounted phone, a multiview rig and a stereo pair combine, is Not stated and agreed in the spec.

The first risk is occlusion by the work itself: hand and tool cover the fault while it is fixed. The site answers with a per-joint visibility flag, contact events, and wrist views where the spec asks for them.

Depth is the second. The site says depth degrades on wet and reflective surfaces, masks low-confidence regions with per-frame confidence maps, and rejects an episode above 35 percent invalid depth pixels in the manipulation region. How depth behaves when the plumbing row tests the water flow is Not stated. Calibration is the third, measured at the start and end of every session under a 0.28 px RMS gate. An episode is also rejected when the manipulated object is out of frame for more than 15 percent of it or an undocumented bystander appears, and a reject log ships with every batch. The site states no handling for glare, low light, dust or motion blur on these rows, so this page promises none.

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.

Reader and writer libraries exist for C++, Go, Python, Rust, Swift and TypeScript. The foxglove/mcap repository is MIT-licensed; that is the MCAP project’s licence, not the licence of a Firsthand delivery.

Firsthand offers MCAP delivery, and dataset 06 is stated as shipping as MCAP. For repair calls the site states hand pose, a stereo-derived depth stream, IMU, contact events, action segments, per-frame instance masks and one task instruction per episode 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 here; confirm them in the skill spec on a Spec Pilot batch.

Off-the-shelf covers what is already in stock. The industrial and skilled-trade category lists datasets 02, 03 and 04, covering work such as machinery, auto repair, carpentry, construction, factory floors and inspection, and the stereo category lists the stereo head rig. Neither listing names a home repair call, so this page claims no off-the-shelf coverage of these rows.

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. The site states no provider count, cadence, hours or volume beyond that wording, so they are quoted against your spec.

Where coverage is deep, the median time from signed spec to first validated batch is a median of 48 hours. Construction and skilled trades is described as a thinner-coverage setting, where a first batch typically takes three to four weeks. All four rows are Available on request, and the site does not say which timing applies, so ask when you request the quote.

For every delivered episode the site states that faces, heads, licence plates and legible screens are detected and irreversibly blurred at ingest, a human reviewer confirms the result, and footage that cannot be de-identified is held or discarded. Every episode links to a signed contributor release through a documented consent chain, and the release covers bystanders. Resident access terms are set per program.

The buyer owns the dataset under a perpetual, irrevocable, non-exclusive-by-default licence, with exclusivity available. This page makes no safety, electrical, gas, refrigerant or code-compliance claim for any repair row.

Name the repair calls, the diagnose, fix and test steps in order, what the camera must see, and the streams, topic naming and encoding your reader expects. Say whether MCAP is the only delivery or sits beside RLDS, LeRobot or WebDataset. Most programs begin with a Spec Pilot, which confirms the spec on real footage.