Stereo Production Line Quality Inspection Data

It is real-world, first-person video of a person doing in-line quality inspection on a manufacturing production line, recorded with two calibrated cameras so that depth can be recovered, together with 3D hand pose and the other streams the site already lists. The person checks parts against a spec, measures them and sets aside or rejects units that fail. The buyer sets the task and the accept criteria; Firsthand handles contributors, capture, QA, consent and delivery.

The term covers a narrow slice of inspection. It is the in-line case: the check happens at the line, as part of the line work, rather than at a separate lab bench. The wider family of inspection captures, such as damaged-goods sorting or checking a hotel room, has its own page, and so do food, weld and surface checks. The comparison table further down shows exactly where this page sits among them.

Two live rows in the Plastic & Light-Assembly Manufacturer environment name this work. "In-Line Quality Inspection" is rated Easy and described as "Check parts on the line against the spec, measure and set aside defective units." "Quality inspection on a production line" is also rated Easy and described as "Inspect units on the line for defects, measure critical dimensions and reject failures." Both are listed as Ready to deploy, with a capture setup of Phone (head-mounted) / multiview rig. The first table below reproduces them exactly.

The environment sits in the Manufacturing & Workshops sector and holds fifteen rows in total, all Ready to deploy, covering assembly, trimming, molding-machine tending, inspection, packing, palletizing and labeling. This page does not claim delivered hours or delivered stereo footage for either row. Part or product types, line speeds, defect rates, acceptance criteria and inspection standards are Not stated on the site, so they are set in the written spec.

Not stated. The catalog lists a head-mounted phone or multiview rig for both rows and no stereo pair. Stereo applies here only through the general stereo offer: the site describes a stereo head rig and a hard-environments stack, and a stereo pair for an in-line inspection order is a choice made in the skill spec and confirmed on a Spec Pilot.

This is why the page is written as a stereo and container page for the two rows rather than as a description of existing stereo inspection footage. If you need stereo, say so in the brief; if you are happy with the catalog setup, the egocentric inspection and light assembly pages describe that non-stereo route.

This page is stereo capture of in-line quality inspection on a manufacturing production line. The stereo surface quality page is the wide view: it counts nine inspection-named rows across several environments, including these two, and is not tied to one line. The stereo food QA page covers two rows in a Food & Beverage Manufacturing Plant that centre on an inspection light, foreign objects and pulling suspect product from the belt. The stereo weld page covers one Medium row in a Metal Fabrication & Welding Workshop that adds grinding, cleaning seams and marking for rework.

Two further pages are egocentric rather than stereo. The egocentric visual inspection page is the task family across stations and lines, and the egocentric light assembly page covers the whole Plastic & Light-Assembly Manufacturer environment, of which these two inspection rows are a part. The second table below puts all of them side by side with their status as the site lists it.

The site describes two stereo configurations. The stereo head rig, dataset 06, is a dual fisheye pair at 1080p per eye on a 62 mm baseline, with per-unit calibration, a 9-axis IMU and hand-tracking output, shipped as MCAP. The hard-environments stack is a 4K/60 head camera with a 120° lens, two 1080p/60 wrist cameras, depth at 848×480 and 30 fps and a 200 Hz 6-DoF IMU. Which of these an in-line inspection order uses is Not stated and is agreed in the skill spec.

Whichever rig is chosen, calibration is measured every session and shipped with the episode, with a 0.28 px RMS reprojection gate. Hand pose is 21 joints per hand with a per-joint visibility flag, and the language data is one task instruction per episode. Camera count, resolution and frame rate for inspection specifically are Not stated.

Glossy or reflective parts are the clearest case. The site states that depth degrades on wet and reflective surfaces and that per-frame confidence maps mask low-confidence regions, so a consumer of the data can tell where depth should not be trusted. How a particular part or finish behaves is Not stated. Hands are the second case: the per-joint visibility flag on the 21-joint hand pose marks joints that are not visible, instead of guessing them, which matters when a hand covers part of a part during a check.

Line speed and lighting changes are Not stated on the site as standard values, so they are not promised here. They are fixed in the skill spec for the station in question, and a Spec Pilot proves the capture on real footage before you scale. Episodes that fail the QA bar are rejected and logged per batch, not delivered with a caveat.

Firsthand offers MCAP delivery. MCAP is an open-source container format with its own official site at mcap.dev, a specification at mcap.dev/spec and a repository at github.com/foxglove/mcap; read those for what the container is and how it stores records, timestamps and attachments. This page describes the container only from those sources and does not state anything more about it.

The streams the site already states for a stereo capture are the stereo pair, depth with confidence maps, 21-joint hand pose, IMU, contact events, action segments and calibration. Topic names, message schemas, encoding and rates are Not stated on the site and are agreed in the skill spec. Only dataset 06 is stated as shipped as MCAP; for any custom order, MCAP can be the only delivery or sit beside RLDS, LeRobot, WebDataset, HDF5 or zarr.

Defect labels, a defect taxonomy, a pass or fail outcome label for each inspected unit, measurement values such as dimensions, and part, serial or lot identity are not stated as standard labels. The catalog descriptions mention measuring and rejecting, but those describe what the operator does, not a label delivered with the episode.

This page gives no defect rate, detection accuracy, tolerance, line speed, task time or error rate, and it names no client, plant, brand or product type. It also names no inspection standard. If your policy needs any of these, it is written into the skill spec as annotation depth and covered in the quote before capture begins.

No off-the-shelf dataset for in-line inspection tasks exists on the site, so this is custom collection. The off-the-shelf stereo category lists stereo datasets and hand-tracking video, and only dataset 06 is stated as MCAP. It is a way to look at the format and rig, not coverage of these two 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.

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 catalog status on each row tells you which case you are in, and these rows are listed as Ready to deploy. Collections are billed per validated hour.

The site states that faces and screens are blurred at ingest, and describes consent and anonymization on its anonymization page. Anything beyond that, including how a plant handles other staff or marked parts in frame, is Not stated and is set in the spec. This page gives no equipment-safety guidance.

The buyer owns the dataset under a perpetual, irrevocable, non-exclusive-by-default licence, with exclusivity available. Consent is recorded per session.

Name the row you are following, the part and the station, the standard the part is checked against, what counts as one completed check and the decision at the end. 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.

Most programs begin with a Spec Pilot, a small first batch that proves the spec and accept criteria on real footage before you scale. The last table below shows what each spec element decides.