Now recruiting capture teams worldwide. Get paid to record first-person video of real work.

Apply to capture

Task rows

Stereo Office Printer and Shredder Data

Load a paper tray and clear a jam; feed sheets into a shredder. Two catalog rows name this desk work, and both sit in the Office Document Station. This page covers the stereo and container side of printer jam clearing robot training data: what a calibrated stereo pair adds to stereo paper tray loading video, what MCAP is according to its own documentation, and what the site does not state. We run custom office data collection fast and on demand against a spec you write, as a handheld gripper shredder feeding dataset when the spec names it, delivered as MCAP, as custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs.
Catalog rows
"Load tray + clear jam" (Easy); "Shred documents" (Easy)
Environment
Office Document Station; both rows Available on request
Container
MCAP (.mcap), open source
License
Perpetual, buyer-owned

Why stereo and MCAP here

What do a stereo pair and an MCAP file add to printer and shredder video?

01

Depth of a sheet, a tray and a slot

The site states that a stereo pair at human-eye spacing makes depth recoverable from every frame pair, so the sheet, the tray or shredder opening and the hands working it sit in one frame. It gives no depth accuracy figure for these rows.

02

A hand that disappears inside the device

The site states that reaching into a printer hides the hand from the head camera. 3D hand pose carries a per-joint visibility flag, so a finger hidden inside the device is marked as hidden rather than silently filled in.

03

Two jobs, kept apart

Loading a tray and clearing a jam, and feeding a shredder, are separate catalog rows, so a spec can name each as its own task and ask for more of one without re-collecting the other.

04

Several streams in one container

MCAP stores multiple channels of timestamped, pre-serialized data, so a stereo pair, hand pose and IMU can share one file on one log-time axis. Which streams go in the file is set in the skill spec.

Definition

What is stereo office printer and shredder data?

It is video of a person at an office document station loading a paper tray, clearing a jam and feeding sheets into a shredder, recorded with two calibrated cameras, with hand pose and sensor streams alongside. People reach it through several phrasings: printer jam clearing robot training data, stereo paper tray loading video, a handheld gripper shredder feeding dataset, or custom office data collection at scale. They describe one request from different angles. Stereo describes the capture, and MCAP describes the container. They are separate choices.

One thing needs care. The site does not state that stereo is already running on these rows. The catalog lists a multiview rig with handheld grippers as the capture setup, so a stereo pair is a capture choice agreed in the skill spec through the site’s general stereo offer 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.

Catalog rows

Which catalog rows does this page rely on, and what is their status?

Two. In the Office Document Station environment of the Office & IT sector the catalog lists "Load tray + clear jam": "Load a paper tray and clear a jam." It is rated Easy. It also lists "Shred documents": "Feed sheets into a shredder." It is rated Easy too. Both list the capture setup Multiview rig + handheld grippers, and both are Available on request. The first table below reproduces the rows exactly.

Available on request means the work is scoped and recruited to spec when a buyer asks. It is not a statement that footage of these tasks has been delivered, and the site states no delivered hours or stereo clips for them, so this page claims none. Neither row is listed as Active collection or Ready to deploy.

The setting

What is the Office Document Station environment?

The catalog describes it as a desk-and-document station with a printer and tray, binders, a stapler, a label maker and mailers as examples. It is a staged working set, not a recording of a described real workplace. The site states that Firsthand does not capture at a customer’s own facility, so the set is a capture setting arranged for the task.

The environment examples name a printer and tray but do not name a shredder, even though the Shred documents row sits in that environment. The site names no office, company or building, and does not state a number of sites, regions or a venue type. Environment, access and schedule are agreed in the written spec.

Capture setup

What capture setup do the rows list, and where does stereo come in?

The catalog lists "Multiview rig + handheld grippers" for both rows. The site does not state a stereo pair for them, and it does not describe these tasks as stereo capture. 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 states that every sensor in a multiview rig is hardware-triggered from a single PTP grandmaster clock. It does not state a camera count for these rows.

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. Whether either is used with the catalog’s multiview rig is not stated.

Handheld grippers

Why does a handheld gripper capture matter for tray and shredder work?

The catalog lists handheld grippers because the operator holds a gripper rather than a bare hand while performing the task, and the site says this lets demonstrations map onto a robot end effector. A handheld gripper shredder feeding dataset therefore keeps the demonstration closer to the hardware a robot would use than a bare-hand clip does.

The site does not state which gripper is used or how it attaches, and this page names none. It does not claim that a model trained on this capture succeeds at either task, or that human capture replaces robot data.

Differences

How is this different from the egocentric, mailroom, envelope and stapler pages?

This page is the stereo and MCAP treatment of the two printer and shredder rows. The egocentric office printer and shredder page covers the same two rows as a first-person page, so it is a sibling, not an equivalent: stereo and MCAP are not its subject, and the two share the row wording.

The stereo office mailroom and document handling page is broader. It covers four Office & Professional Services rows, "Mail handling", "Filing", "Scanning" and "Printing", all Easy and all Available on request, and it lists "Phone (head-mounted) / multiview rig" as their capture setup. The stereo envelope stuffing and mailer packing page covers "Stuff + seal envelopes" and "Pack + tape mailer", and the egocentric stapler refill and label making page covers the stapler and tape refill and label-maker rows. None of them has stereo printer and shredder work as its main topic. The comparison table below sets the pages side by side.

Why stereo

Why capture tray, jam and shredder work in stereo?

Both jobs are geometry at a desk: where the sheets sit relative to the tray, where the hand sits relative to the opening it reaches into, where the sheet sits relative to the shredder slot, and where the hands sit relative to all of it. A stereo pair recovers depth from the calibrated frame pair rather than from a standalone depth sensor, so that geometry is in the same capture that shows the hands working. The site gives no depth accuracy figure for these rows.

The site also describes paper as thin and flexible, so a sheet changes shape every time it is touched. A frame pair that records the shape in three dimensions gives a policy more than a single flat view does, though the site makes no claim about robot results.

Occlusion, masks and depth

What does reaching into a device do to visibility, masks and depth?

In these jobs the hand goes where the camera cannot follow. The site states that reaching into a printer hides the hand from the head camera and that fingers disappear behind objects. That is why each hand joint carries a visibility flag, why wrist camera views are paired with the problem, why contact events mark when a hand meets or releases a sheet, and why labels say what is visible rather than imply a clean view. The site pairs the tray and jam task with wrist camera views, 3D hand pose with per-joint visibility and depth from the calibrated stereo rig.

On masks, the site states that clothing, bedding and bags do not track well with masks propagated from frame to frame, which is why deformable captures ship per-frame instance masks, stored at 848×480 so they line up with the depth stream, where the spec calls for them. Paper is not named in that statement, so whether an order asks for them is a spec decision. The site also states that depth degrades on wet and reflective surfaces, with per-frame confidence maps masking low-confidence regions, and that metric depth on sub-centimetre parts is flagged rather than interpolated. Whether a sheet edge or a shredder slot counts as such a part is not stated, so the Spec Pilot checks the real footage.

Episodes

What does one stereo printer or shredder episode contain?

Each attempt is delivered as one episode. The row descriptions give the tasks, but not a start state, an end state or a count. The site lists a jam start state and a failure and recovery case for the tray and jam task, so a spec can ask for the fault and the fix as well as a clean run. Whether an episode is one tray, one jam or one stack of sheets, and whether several attempts share one recording, are spec decisions, because the site states no episode length or item count.

Inside the episode, the synchronized streams run from start to end and action segments divide it into labeled spans, each with start_ns, end_ns, verb and noun. Feeding a sheet is a short contact event with a fast release, and the site pairs it with contact events on grasp and release, an IMU on one clock and action segments. A spec for these rows names the verb and the noun rather than a broad activity, as the site’s skill-spec guide advises. This page supplies no step list and no instruction on how either task is done.

Privacy

How are people and document contents protected?

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 describes its documents class as phone and monitor content, forms, badges and mail that would leak names, addresses or account data, and states that those regions are irreversibly blurred and confirmed by a human reviewer. The site states nothing about what sheets in these rows contain, and this page does not suggest that real confidential documents are used. Whether any engagement can keep specific content is not stated, so raise any need for readable content before the spec is signed. This is not legal advice, and the executed agreement controls.

MCAP

What is MCAP, per its own documentation?

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.

Streams

Which streams can ship in an MCAP delivery of printer and shredder data?

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 stream map table below sets each stream beside what the site states about it.

Failure modes

What goes wrong when you record printer work in stereo, and what does QA reject?

Hand occlusion and weak depth on reflective surfaces are the first two risks. Calibration is measured at the start and end of every session under a 0.28 px RMS gate. 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 more than 35 percent of depth pixels in the manipulation region being invalid, 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 our cost. What counts as the manipulated object, the sheet, the tray, the shredder opening or a combination, is a decision the spec settles.

Scale and speed

How fast can custom stereo printer and shredder data be collected at scale?

The site’s off-the-shelf catalog lists about 324,800 hours across 18 datasets. This page does not offer any of it as coverage of these rows, the site lists no off-the-shelf printer, shredder or office document dataset, and it states no delivered hours or stereo clips for them.

Printer and shredder collection to a spec is therefore custom collection: 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 rows are Available on request, so the scoped-to-spec timeline applies and the quote states it up front. A pilot reaches its first delivery in two to three weeks and a standing program reaches full rate in four to six weeks, assuming capture coverage is already in place. Collections are billed per validated hour, and rejected episodes and recaptures are never billed.

Delivery and license

Which formats and license come with a stereo printer and shredder order?

Delivery is MCAP, alone or beside the formats your stack already reads: RLDS, LeRobot, WebDataset, HDF5 or zarr, or raw streams with metadata. Readable converter source ships alongside the data so the schema can be retargeted to your own loader.

The license is perpetual, irrevocable and worldwide, with the data buyer-owned and non-exclusive by default. Training, evaluating, fine-tuning and deploying models, including commercial ones, is permitted, and exclusivity is available as a separate term. The executed agreement controls. The site does not publish a price list, a minimum order or a batch size for these tasks, so those are set in your quote.

Ordering

How do you order a stereo office printer and shredder dataset?

Name the row or rows, "Load tray + clear jam", "Shred documents" or both, the start and end state of one attempt, what counts as the manipulated object and what counts as a reject. 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 a training format.

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.

At a glance

What you get.

Catalog row
"Load tray + clear jam" (Easy), Office Document Station, Office & IT; Available on request
Catalog description
"Load a paper tray and clear a jam."
Catalog row
"Shred documents" (Easy), Office Document Station, Office & IT; Available on request
Catalog description
"Feed sheets into a shredder."
Environment examples
"Desk-and-document station: printer/tray, binders, stapler, label maker, mailers"
Catalog capture setup
Multiview rig + handheld grippers on both rows. The site states no stereo pair for these rows, so a stereo pair is agreed in the skill spec through the general stereo offer
Stereo head rig (06)
Dual fisheye, 1080p per eye, 62 mm baseline, per-unit calibration, 9-axis IMU, hand-tracking output; shipped as MCAP
Hand pose
21 joints per hand with a per-joint visibility flag
Sync
Hardware-triggered onto one clock; 2.0 ms cross-stream ceiling
Language data
One task instruction per episode
Printer, shredder, paper and jam types, sizes, volumes, task times, success rates
Not stated; agreed in the skill spec
MCAP topics, schemas, rates
Not stated on the site; agreed in the skill spec
License
Perpetual, irrevocable, buyer-owned, non-exclusive by default

Every collection runs through the same seven-stage end-to-end custom collection pipeline. End-to-end custom data collection is a managed service that takes an AI data need from problem to owned dataset in a single accountable pipeline.

Catalog rows

Which catalog rows cover printer and shredder work, and what is their status?

The rows exactly as the task catalog states them. Items the catalog does not list are marked Not stated. Source file: lib/commercial-catalog-data.ts.
Task (as listed)Description (as listed)EnvironmentSkillCapture setupStatus
Load tray + clear jamLoad a paper tray and clear a jam.Office Document StationEasyMultiview rig + handheld grippersAvailable on request
Shred documentsFeed sheets into a shredder.Office Document StationEasyMultiview rig + handheld grippersAvailable on request
Printer, shredder, paper and jam types, sizes, volumes, outcome labelsNone beyond the row wordingNot stated as rowsNot statedNot statedNot stated

Compared pages

How does this page differ from the egocentric, mailroom, envelope and stapler pages?

Each page and what it covers. Statuses are as the site lists them; none of these pages is claimed to hold delivered hours here.
PageCaptureWhat it coversRelation to this page
This page: stereo office printer and shredder dataStereo, agreed in the specLoad tray + clear jam (Easy) and Shred documents (Easy); both Available on requestStereo pair and MCAP delivery for the two printer and shredder rows
Egocentric office printer and shredder dataMultiview rig + handheld grippers, not stereoThe same two rowsThe first-person sibling; stereo and MCAP are not its subject
Stereo office mailroom and document handling dataStereo, agreed in the specFour Office & Professional Services rows (Mail handling, Filing, Scanning, Printing), all Easy and Available on requestBroader mail, filing, scanning and printing page; different rows and environment
Stereo envelope stuffing and mailer packing dataStereo, agreed in the specStuff + seal envelopes and Pack + tape mailer, in the same Office Document StationSame environment, different rows
Egocentric stapler refill and label making dataMultiview rig + handheld grippers, not stereoThe stapler and tape refill and label-maker rowsSame environment, different rows; first-person page
Egocentric stereo data in MCAPStereo, hubThe stereo and MCAP hub across tasksGeneral stereo and MCAP treatment; not specific to printers or shredders

Stated vs not stated

What the site states about stereo capture for printer and shredder work

Left to right: the item, what the site states, and what that means for a printer and shredder order. “Not stated” means the site does not say.
ItemWhat the site statesFor a printer and shredder order
Catalog capture setupMultiview rig + handheld grippers on both rowsNo stereo pair is stated for these rows; a stereo pair is a spec choice through the general stereo offer
Gripper capture modeA staged working set recorded by a multiview rig while the operator uses handheld grippers, so demonstrations map onto a robot end effectorStated for the mode; cameras for these rows Not stated
Stereo head rig (dataset 06)Dual fisheye, 1080p per eye, 62 mm baseline, per-unit calibration, 9-axis IMU, hand-tracking output; shipped as MCAPWhether an order uses it: Not stated
Hard-environments stack4K/60 head camera, 120° lens; two 1080p/60 wrist cameras; depth 848×480 at 30 fps; 200 Hz 6-DoF IMUWhether an order uses it: Not stated
Hands, contacts and masksPer-joint visibility flag on hand pose; contact events; per-frame instance masks stored at 848×480 where the spec calls for themStated; what counts as the object is set in the spec
OcclusionReaching into a printer hides the hand from the head camera; fingers disappear behind objectsStated; how often it occurs on these rows is Not stated
Jam start state and failure and recovery caseListed for the tray and jam taskStated; whether an order requires them is set in the spec
Depth on small and reflective partsMetric depth on sub-centimetre parts is flagged rather than interpolated; depth degrades on wet and reflective surfaces; confidence maps mask low-confidence regionsStated; whether a sheet edge or shredder slot counts as sub-centimetre is Not stated
Calibration and synchronizationMeasured every session, 0.28 px RMS reprojection gate; hardware-triggered onto one clock, 2.0 ms ceilingStated
QA rejectsObject out of frame over 15 percent, over 35 percent invalid depth pixels, undocumented bystanderStated; per-batch reject log
Row statusEasy and Easy, both Available on requestNo volume, hours or delivered stereo footage is claimed on this page
Printer, shredder, paper and jam types, sizes, volumesNot statedNot claimed; set in the spec
Task duration, success rateNot statedNot claimed on this page
MCAP topics, schemas, ratesNot statedAgreed in the skill spec

Stream map

Streams for printer and shredder work and what the site states about an MCAP file

Left to right: the stream or item, what the site states about it, and what the site states about it in MCAP. “Not stated” means the site does not say.
Stream or itemWhat the site statesIn an MCAP delivery, as the site states it
Stereo pairDual fisheye, 1080p per eye, 62 mm baseline (dataset 06)Dataset 06 is stated as shipped as MCAP; channel layout not stated
Depth with confidence mapsRecovered from the calibrated stereo pair; confidence map masks low-confidence regionsNot stated
Hand pose21 joints per hand with a per-joint visibility flagChannel layout and joint order not stated
IMU9-axis (dataset 06); 6-DoF at 200 Hz (hard-environments stack)Channel layout and rate not stated
Contact events, action segments, instance masksListed in the site episode schema; masks stored at 848×480Not stated
Task instructionOne per episodeNot stated
CalibrationMeasured every session and shipped with the episodePlacement in the file not stated
Topic names, schemas, encoding, ratesNot statedAgreed in the skill spec

Formats and licensing

Which formats and license terms come with a printer and shredder order?

Delivery formats stated on the site, set against what each format’s official documentation states, with the license terms the site states.
ItemWhat the official documentation or the site statesUsed for here
MCAPAn open source container file format for multimodal log data, supporting multiple channels of timestamped pre-serialized data (MCAP documentation)Stereo pair, hand pose and IMU in one file
RLDSAn ecosystem of tools to store, retrieve and manipulate episodic data; a dataset is retrieved as episodes, and each episode holds a dataset of steps (RLDS repository README)Episode-based training loaders
LeRobotLeRobotDataset v3.0 is a standardized format for robot learning data, including multi-camera video, with many episodes stored per Parquet or MP4 file (LeRobot documentation)LeRobot dataset format and tooling
WebDatasetTar files in which files that belong together share a basename, with shards numbered in sequence (WebDataset README)Sharded streaming for large training runs
HDF5 and zarrStated by Firsthand onlyArray storage for custom pipelines
LicensePerpetual, irrevocable, worldwide, buyer-owned, non-exclusive by default; exclusivity available as a separate term (site statement; the executed agreement controls)Training, evaluating, fine-tuning and deploying models, including commercial ones

Skill spec

What the skill spec fixes for a stereo office printer and shredder order

Spec element and where a buyer can see it in the delivery. “Set per program” means the site states no fixed value.
Spec elementWhat it decidesWhere it shows up
Row or rowsLoad tray + clear jam, Shred documents or both, worded as the catalog words themSet per program; Available on request as listed
Start and end stateWhat one attempt is, and what counts as finished for each job; whether the jam start state and the failure and recovery case are requiredEpisode boundaries; the site does not state an episode length
Object definitionWhat counts as the manipulated object: the sheet, the tray, the shredder opening or a combinationContact events, masks and the out-of-frame reject rule; set per program
Rig and streamsStereo pair, multiview angles, wrist views, hand pose, IMU and any othersThe channels you can read; confirm on the Spec Pilot
VariationHow much variation in items and setting your policy should seeSet per program
Action segmentsVerbs and nouns for each stepSegment labels on each episode
MCAP topics and encodingWhat your reader expectsSet per program
Delivery formatHow the data is packagedMCAP alone, or beside RLDS, LeRobot, WebDataset, HDF5 or zarr
Accept criteriaWhat passes QA, including what counts as a rejectReject log per batch
PrivacyHow people, screens and document content in frame are handledFaces and screens blurred at ingest; document content blurred and reviewed; other items agreed in the spec
LicenseWho owns the datasetPerpetual, irrevocable, buyer-owned, non-exclusive by default

Example footage

What does stereo capture look like on this site?

One real clip already published on this site, shown as a rig example. It is a head-mounted stereo capture with hands in frame. It does not show a printer, a paper jam, a shredder or an office document station, and it is not an example of the multiview rig with handheld grippers these rows list.

egocentric_stereo_sample.mp4 · head-mounted stereo · hands in frame · 1920 × 1080 web preview · rig example, not a printer or shredder clip

No stereo printer or shredder clip is published on the site, so this is labelled as a rig example. Request a sample to see delivered files. See sample data outputs, stereo sample page, request an egocentric data sample.

FAQ

Printer jam clearing robot training data, answered.

What is stereo office printer and shredder data?
Video of a person loading a paper tray, clearing a jam and feeding sheets into a shredder, recorded with a calibrated stereo pair so depth is recoverable, with hand pose alongside where the spec calls for it.
Which catalog rows cover it, and what is their status?
"Load tray + clear jam" ("Load a paper tray and clear a jam.", Easy) and "Shred documents" ("Feed sheets into a shredder.", Easy), in Office Document Station, both listed with Multiview rig + handheld grippers and Available on request. This page claims no delivered hours.
Is stereo already captured on these rows?
Not stated. The catalog lists a multiview rig with handheld grippers. A stereo pair is agreed in the skill spec through the general stereo offer and confirmed on a Spec Pilot.
How is this different from the egocentric printer page and the mailroom page?
The egocentric page covers the same two rows as first-person video. This page covers them with a stereo pair and MCAP delivery. The stereo mailroom page covers four different Office & Professional Services rows for mail, filing, scanning and printing.
Is there an off-the-shelf printer or shredder dataset?
The site lists none, and this page claims none. Printer and shredder work is custom collection, at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs.
Are names and addresses on sheets readable in the footage?
No. The site states that document regions that would leak names, addresses or account data are irreversibly blurred at ingest and confirmed by a human reviewer. Whether any engagement can keep specific content is not stated.
How fast can a custom stereo printer and shredder dataset be collected?
Where coverage is deep, the median time from signed spec to first validated batch is a median of 48 hours; thin coverage runs three to four weeks. The rows are Available on request, so the timeline is quoted against your spec.
Can it be delivered as MCAP, and what is in the file?
Yes. Firsthand offers MCAP delivery. Topic names, message schemas and rates are not stated on the site and are agreed in the skill spec.

Sources

Where is MCAP documented?

Request a custom stereo office printer and shredder dataset delivered as MCAP.

Tell us the row or rows, the start and end state of one attempt, what counts as the manipulated object, how much variation in items and setting your policy should see, the streams you want in the file, the privacy rule for document content and whether MCAP sits alongside a training format. We will quote reach, timeline and price against a written spec, with a first validated batch in a median of a median of 48 hours where coverage is deep.