Stereo Pet Grooming Data

It is first-person video of a person doing commercial pet grooming, recorded with two calibrated cameras, with hand pose and sensor streams alongside. People reach it through several phrasings: pet grooming robot training data, stereo dog bathing and clipping video, an egocentric grooming salon dataset or custom pet care data collection at scale. They describe one request from different angles. 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, so 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, so using it for a specific robot still needs your own retargeting step. Firsthand is not affiliated with Foxglove or the MCAP maintainers.

Two, listed in lib/commercial-catalog-data.ts, in the Pet Grooming Salon environment of the Pet & Animal Care sector. One reads "Bathe, dry, trim, and brush pets’ coats and nails using pet shampoo, a grooming dryer, clippers, and brushes." and is described as "Pet grooming salon with washing tubs, grooming tables, and drying stations." The other is named "Pet Grooming" and is described as "Washing, clipping, drying and grooming animals in a commercial grooming setting." Both are rated Medium, and both are listed as Active collection.

The site defines Active collection as "Recording in this environment is running now, so a spec can join an existing capture stream." That is a statement about the catalog row, not a promise of a delivery date. The site states no delivered hours and no delivered stereo footage for either row, so this page claims none. The first table below reproduces the two rows as the catalog states them.

This page is the stereo and MCAP treatment of the two grooming-salon rows: bathing, drying, trimming or clipping, and brushing coats and nails. The egocentric pet grooming salon page covers the same two rows as first-person video, and it is not stereo as its subject. Where that page lists capture it gives the same head-mounted phone or multiview rig; this page is the one that starts from a calibrated stereo pair and an MCAP file.

The veterinary clinic page covers five clinic rows, such as animal handling, examination room prep, kennel cleaning, post-procedure care and surgical instrument setup, all listed as Available on request. The kennel and animal pen cleaning page covers cleaning work, and the pet care page is the broader overview. None of them is a stereo grooming page. The second table below sets the pages side by side with each status as the site lists it.

The catalog lists "Phone (head-mounted) / multiview rig" for both rows. The site does not state a stereo pair for them. Stereo applies through the site’s general stereo offer: a stereo pair is a capture choice agreed in the skill spec and confirmed on a Spec Pilot. The site also states that Firsthand does not capture at a customer’s own facility, so the setting is agreed in the spec.

The site describes two stereo setups and does not say which one an order for these rows 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. A multiview rig adds synchronized third-person angles when the spec asks for them. Whether a stereo pair is worn, mounted or combined with the phone capture the catalog lists is Not stated.

Grooming is about where a tool meets a coat and how the hands move around a subject: how a brush sits against a surface, how a clipper is held against a limb, how a dryer is angled at a coat. A stereo pair recovers depth from the calibrated frame pair rather than from a standalone depth sensor, so the geometry sits in the same capture that shows the hands working. The site gives no depth accuracy figure for these rows, so what a buyer does with that depth is their pipeline’s question.

A stereo pair adds depth, not a verdict. The site states no success or quality label for a wash, a dry, a trim or a brush, and none is claimed. The egocentric grooming page already supplies the first-person framing; stereo is the addition for a buyer who wants the depth and the MCAP file.

The rows give a natural cut: wash with pet shampoo, dry with a grooming dryer, trim or clip with clippers, and brush coats and nails with brushes. The order inside the first row is the catalog’s own. A spec that says "groom the pet" gives one long action segment. A spec that names the steps gives a sequence you can slice by step, and the site does not set an episode length or say how many animals make up an episode.

Whether washing and drying are one segment or two, and whether brushing a coat and brushing nails are one segment or two, is a spec decision, not a default. Contact events can mark when a hand meets a tool or an item, where the spec asks for them, and the spec decides what counts as the object. The site does not describe contact events as force or pressure.

A coat, a thumb and a dryer can all sit between the lens and the work. The site states that fingers disappear behind objects, which is why each hand joint carries a visibility flag, and that reach and grasp frames are where blur and occlusion show up. The head camera in the hard-environments stack is global-shutter, which avoids rolling-shutter skew.

The site gives no figure for how often a hand or a tool hides the work on these jobs, so a spec can ask for wrist views or a second angle and check it on a Spec Pilot. Tools are named only as the rows list them: pet shampoo, a grooming dryer, clippers and brushes. Washing tubs, grooming tables and drying stations are the stated stations. The site states no tool-pose, force or tactile stream for these rows; a separate glove tier has its own page, and whether it applies to grooming is Not stated.

Washing puts water on the animal, the tub and the lens, and the site states that depth degrades on wet and reflective surfaces while confidence maps mask low-confidence regions. It also states that glare-heavy and low-texture scenes make single-frame depth worse. Depth on wet coats and tub surfaces is therefore where a buyer should look first on a Spec Pilot.

The subject moves. The existing grooming page states that the effect of coat, water and animal movement on any stream is Not stated, and no accuracy figure is listed, and this page keeps that position. An episode is rejected when more than 35 percent of depth pixels in the manipulation region are invalid, and for this job the spec decides what the manipulation region is. Lens protection, splash handling, lighting and salon layout are Not stated.

Whether the animals are live, models or props, the animal types and breeds, the number of animals, and whether the salon is real or staged are Not stated. The site makes no animal-welfare, handling, health or safety claim, and no certification claim, and this page makes none. Owner and client handling is settled in the skill spec.

For every delivered episode the site states that faces and screens are blurred irreversibly, that a reviewer confirms no un-consented person is identifiable, and that footage that cannot be de-identified is discarded. The anonymization record ships with the data, an undocumented bystander is a stated reject criterion, and every episode links to a signed contributor release. The site does not state how animals or owners are handled beyond that. This is not legal advice, and the executed agreement controls.

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 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 these rows the site states hand pose, a stereo-derived depth stream with confidence maps, 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 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.

Hand and tool occlusion is the first risk, under the visibility flag above. Weak depth on wet or glare-heavy surfaces is the second. Calibration is measured at the start and end of every session under a 0.28 px RMS gate, and an episode is rejected for a sync breach beyond the ceiling for more than three consecutive frames, for the manipulated object out of frame for more than 15 percent of the episode, for an undocumented bystander or for a mismatch against the named skill spec.

A reject log ships with every batch, and rejected items are recaptured at the provider’s cost. The fifth table below lists the failure modes beside what the site states.

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 names no pet grooming dataset among them, so this work is custom collection, not an off-the-shelf purchase. The off-the-shelf stereo and hand-tracking video can still show the format before you write a spec.

It is 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. Both rows are listed as Active collection, but the site does not say which speed applies, 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: washing, drying, trimming or clipping, brushing coats and nails. Say whether an episode covers one animal, one step or one pass, what counts as the object and what counts as a finished step, the privacy rule for the space, and name 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 sixth table below shows what each spec element decides.