Stereo Food Plant Sanitation Washdown Data

It is first-person video of a person washing down a food-production area: rinsing equipment with hoses, applying foam sanitizer, scrubbing and rinsing down the production area. It is recorded from their own point of view with two calibrated cameras, with hand pose and sensor streams alongside. The task is the one the site’s catalog lists in two rows. 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. It describes task video only and makes no chemical, food-safety, HACCP, allergen or certification claim. Firsthand is not affiliated with Foxglove or the MCAP maintainers.

Two, both in the Food & Beverage Manufacturing Plant environment of the Food & Beverage sector, both rated Medium and both listed as Ready to deploy. The first is named "Sanitation Washdown": "Rinse equipment with hoses, apply foam sanitizer, scrub and rinse down the production area." The second is named "Wash down and sanitize production equipment using hoses and foam sanitizer": "Disassemble guards, hose down equipment, foam, scrub and rinse to a sanitary finish." The words "sanitary finish" are quoted from the catalog; the site states no measured result behind them.

Both list a head-mounted phone or a multiview rig as the capture setup. The catalog lists examples for the environment such as a packaged food factory, a bottling plant, a meat processing facility and a ready-meal production line, and does not say which one a row was captured in. The site says nothing further about what Ready to deploy means in volume, hours or delivered stereo footage, so this page claims none. It names only the tools and items that appear in the rows: hoses, foam sanitizer, production equipment, guards and the production area. The first table below reproduces the rows as the catalog states them.

The egocentric food plant sanitation and washdown page covers the two plant rows together with two restaurant kitchen cleaning rows as first-person capture, and it has no stereo-pair or MCAP treatment. The stereo dishwashing and kitchen sanitation page gives stereo and MCAP treatment to four Restaurant & Commercial Kitchen rows, and leaves the food plant rows out.

This page is the stereo and MCAP treatment of the two food plant washdown rows alone, with their own stream map and failure modes. The comparison table below sets the pages side by side.

A washdown is about where the hands, the hose and the surface sit relative to one another: how far a hose is from a piece of equipment, where a scrub pad has been, which guard has come off. A stereo pair recovers depth from the calibrated frame pair rather than from a standalone depth sensor, so the equipment, the tool, the surface and the hands share a frame.

The site also states that depth degrades on wet and reflective surfaces and handles that with per-frame confidence maps shipped so a buyer can mask rather than guess. The site gives no depth accuracy figure for washdown, and no label for a clean surface, so whether foam, spray or wet steel is resolvable in depth is Not stated, and a spec should check it on a Spec Pilot. Capture at your own facility is listed as not offered.

The site describes two stereo setups and does not say which one a washdown 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 rig, resolution and streams a washdown order uses is Not stated on the site, and the third 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. The site does not state how capture hardware is protected from water or spray, and gives no waterproofing or IP rating for any rig, so any splash or handling requirement is settled in the spec. The catalog states that a multiview rig adds synchronized third-person angles when the spec asks for them, and wrist cameras give a closer view of the hands when one hand holds a hose and the other a pad.

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, 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 washdown work the site states hand pose, a stereo-derived depth stream with confidence maps, IMU, contact events, action segments and per-frame instance masks 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.

Wet and reflective surfaces are the first risk. The site states that depth degrades on them, with per-frame confidence maps to mask low-confidence regions. A washdown is wet work by definition, so ask for the confidence maps to be delivered with each episode. How a stereo pair behaves on foam, spray or a rinsed stainless surface is Not stated, and this page makes no claim about it.

Occlusion is the second. A hose, a scrub pad or a guard can hide the fingers that hold it. The visibility flag on each joint is the answer the site gives, contact events mark when a hand takes hold of an item, masks are recorded per frame, and a spec can ask for wrist views or a second angle so a grip the head camera loses is still recorded. The site does not say whether a hose, a guard or a pad counts as the object for contact events, so settle it in the spec.

Sequence is the third. The rows chain disassembling guards, hosing down, foaming, scrubbing and rinsing, so a spec naming each step gives a sequence that can be sliced by step, while a spec saying "wash down the line" gives one long action segment. The rows do not say what one episode covers, so the spec decides. Chemical names, concentrations, water temperatures and pressures, cleaning cycle times, equipment makes and models, plant or customer names, throughput and any food-safety, HACCP, allergen or certification claim are Not stated and are not claimed on this page.

Calibration is the fourth, because stereo depth is only as good as the rectification behind it: calibration is 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, when more than 35 percent of depth pixels in the manipulation region are invalid, or when an undocumented bystander appears, and a reject log ships with every batch.

For every delivered episode the site states that faces, plates and screens are blurred irreversibly, and that footage that cannot be de-identified is discarded. The anonymization record ships with the data, and an undocumented bystander is a stated reject criterion.

The site does not state a rule for plant access or hygiene zones, so this page makes no such claim. Raise it in the spec if it matters.

The October 2026 off-the-shelf catalog lists ~324,800 hours across 18 datasets, of which stereo is ~64,800 hours across 9 datasets. The site lists no off-the-shelf washdown or sanitation dataset, so stereo food plant washdown in MCAP is custom collection: custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs. The off-the-shelf stereo and hand-tracking video page shows what the rig delivers, and the custom order applies it to your task.

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. Both washdown rows are Ready to deploy, and the site does not say which speed applies to a stereo washdown order, so the timeline is quoted against your spec. Collections are billed per validated hour, and rejected episodes and recaptures are never billed.

Describe the steps and where each starts and ends: removing guards, hosing down, foaming, scrubbing and the final rinse. Name the tools you expect to see, whether an episode covers one piece of equipment or a whole production area, what counts as a reject 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. The fifth table below shows what each spec element decides.