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

Apply to capture

Task row

Stereo Thermal Paste and Heatsink Application Data

Apply thermal paste and seat a heatsink. One catalog row names this bench work, and it sits in the Precision Assembly Bench (electronics). This page covers the stereo and container side of thermal paste robot training data: what a calibrated stereo pair adds to stereo heatsink seating video, what MCAP is according to its own documentation, and what the site does not state. We run custom precision assembly data collection fast and on demand against a spec you write, as a handheld gripper thermal compound 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 row
"Apply paste + heatsink" (Medium)
Environment
Precision Assembly Bench (electronics); 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 paste and heatsink video?

01

Depth between a part and a surface

The site states that a stereo pair at human-eye spacing makes depth recoverable from every frame pair, so the part being seated, the surface under it and the hands working it sit in one frame. It gives no depth accuracy figure for this row.

02

Hands over small items, flagged when hidden

Fingers cover the item they place, and the item covers the surface it goes onto. 3D hand pose carries a per-joint visibility flag, so a finger hidden behind a part is marked as hidden rather than silently filled in.

03

Two actions in one row

The row names applying paste and seating a heatsink. A spec can say whether an attempt covers paste only, seating only or both in sequence, and QA checks episodes against that choice.

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 thermal paste and heatsink application data?

It is video of a person at a bench applying thermal paste and seating a heatsink, recorded with two calibrated cameras, with hand pose and sensor streams alongside. People reach it through several phrasings: thermal paste robot training data, stereo heatsink seating video, a handheld gripper thermal compound dataset, or custom precision assembly 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 this row. 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 row

Which catalog row does this page rely on, and what is its status?

One. In the Precision Assembly Bench (electronics) environment of the Manufacturing & Workshops sector the catalog lists "Apply paste + heatsink": "Apply thermal paste and seat a heatsink." It is rated Medium, lists the capture setup Multiview rig + handheld grippers, and is Available on request. The first table below reproduces the row exactly, with a neighbouring bench row as context only.

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

The setting

What is the Precision Assembly Bench environment?

The catalog describes it with the example line "Assembly bench: PCB/electronics, fasteners, fixtures, solder/crimp tools, small parts". It lists 15 rows, all Available on request, each with a multiview rig and handheld grippers. The ratings are two Easy, ten Medium and three Hard, and the paste row is one of the ten Medium rows. It is a staged working set, not a recording of a described real workplace, and the site states that Firsthand does not capture at a customer’s own facility.

The site names no workshop, 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. If your project needs several bench tasks, the egocentric precision assembly bench page treats all 15 rows; this page takes the paste row on its own.

Capture setup

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

The catalog lists "Multiview rig + handheld grippers" for the row. The site does not state a stereo pair for it, and it does not describe this task 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 this row.

The site describes two stereo setups and does not say which one an order for this row 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 paste and heatsink 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 thermal compound 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 the task, or that human capture replaces robot data. The GR00T N1 paper says its human video datasets do not include explicit action labels, and that hand-held robot grippers speed up collection but leave a mismatch with the downstream robot, which is why retargeting remains your step.

Differences

How is this different from the egocentric, repair, soldering and data center pages?

This page is the stereo and MCAP treatment of the single paste row. The egocentric thermal paste and heatsink page covers the same row 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 electronics and device repair page covers one different row, "Device Repair", rated Hard and listed as Active collection. The stereo soldering and circuit board assembly page covers two Electronics Manufacturing & E-Waste rows, "Circuit board assembly" and "Component soldering". The stereo data center rack and server hardware page covers twelve Data Center & IT Hardware Bench rows. None has stereo thermal paste and heatsink application as its main topic. The comparison table below sets the pages side by side.

Why stereo

Why capture paste and heatsink work in stereo?

The job is geometry on a small scale: where the part sits relative to the surface it is going onto, how the two meet, and where the hands sit relative to both. 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 this row.

The row also joins two actions, applying and seating, so the order in which items come together matters. A frame pair that records the shape of the scene 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 do covered parts, small items and shiny surfaces do to visibility, masks and depth?

Fingers disappear behind objects, and in bench work the hand often covers the very item it is placing. That is why each hand joint carries a visibility flag, why contact events mark when a hand meets an item, and why labels say what is visible rather than imply a clean view.

On depth, the site states that small fasteners can fall below a depth sensor’s reliable floor, that hand pose stays valid at that range, and that metric depth on sub-centimetre parts is flagged rather than interpolated. It also states that depth degrades on wet and reflective surfaces, with per-frame confidence maps masking low-confidence regions. Per-frame instance masks are stored at 848×480 so they line up with the depth stream, where the spec calls for them. No depth floor is stated for this row, so the Spec Pilot checks the real footage.

Episodes

What does one stereo paste and heatsink episode contain?

Each attempt is delivered as one episode. The row description gives the task, but not a start state, an end state or a count. Whether an episode is paste only, seating only or both in sequence, and whether several attempts share one recording, are spec decisions, because the site states no episode length.

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, from a taxonomy of 97 verbs and 512 nouns, annotated to the frame and human-reviewed. A spec that says only "apply paste and seat the heatsink" gives one long segment; one that names the steps gives a sequence you can slice. This page supplies no step list and no instruction on how the task is done.

What the row leaves out

What does the paste and heatsink row leave unstated?

The row says what is done, not what it is done with. It names no paste, heatsink, board, tool or part count, and gives no amount, spread pattern, seating order, tolerance or temperature. Whether fastening is part of an attempt is not stated, and the site lists no label for the outcome: no paste-coverage, seated-state, defect or completion label. Force, tactile and temperature readings are not among the standard streams.

A buyer who needs a pattern, a fastening step, paste only or seating only writes it into the skill spec as an accept criterion, and a Spec Pilot proves it before you scale. If your pipeline needs an outcome label, it is scoped in the spec rather than assumed.

Privacy

How are people and board markings 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.

Printed text or markings on a board or part are not a listed blur category, so this page does not claim they are blurred. Which bench, venue or region a program uses, and any safety practice, is not stated and is agreed in the spec. 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 paste and heatsink data?

Firsthand offers MCAP delivery, and dataset 06 is stated as shipping as MCAP. For this row 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 small-part bench work in stereo, and what does QA reject?

Hand occlusion, weak depth on reflective surfaces and parts below the depth floor are the first 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 part being seated, the surface it goes onto or the combination, is a decision the spec settles.

Scale and speed

How fast can custom stereo paste and heatsink data be collected at scale?

This page claims no off-the-shelf coverage of this row and no delivered hours or stereo clips for it. Paste and heatsink collection to a spec is therefore custom collection.

Custom collection at scale runs 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 row is 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 paste and heatsink 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 this task, so those are set in your quote.

Ordering

How do you order a stereo thermal paste and heatsink dataset?

Name the row, "Apply paste + heatsink", the start and end state of one attempt, whether an episode covers paste only, seating only or both, 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
"Apply paste + heatsink" (Medium), Precision Assembly Bench (electronics), Manufacturing & Workshops; Available on request
Catalog description
"Apply thermal paste and seat a heatsink."
Environment examples
"Assembly bench: PCB/electronics, fasteners, fixtures, solder/crimp tools, small parts"
Catalog capture setup
Multiview rig + handheld grippers. The site states no stereo pair for this row, 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
Paste, heatsink, board and tool types, amounts, patterns, tolerances, 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 row

Which catalog row covers thermal paste and heatsink application, and what is its status?

The row exactly as the task catalog states it, with a neighbouring bench row as context only. Items the catalog does not list are marked Not stated. Source file: lib/commercial-catalog-data.ts.
Task (as listed)Description (as listed)EnvironmentSkillCapture setupStatusRole on this page
Apply paste + heatsinkApply thermal paste and seat a heatsink.Precision Assembly Bench (electronics)MediumMultiview rig + handheld grippersAvailable on requestThe row this page covers
Apply adhesive beadDispense an adhesive bead on a path.Precision Assembly Bench (electronics)MediumMultiview rig + handheld grippersAvailable on requestNearby context only
Paste, heatsink, board and tool types, amounts, patterns, outcome labelsNone beyond the row wordingNot stated as rowsNot statedNot statedNot statedNot claimed

Compared pages

How does this page differ from the egocentric, repair, soldering and data center 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 thermal paste and heatsink application dataStereo, agreed in the specApply paste + heatsink (Medium); Available on requestStereo pair and MCAP delivery for the one paste row
Egocentric thermal paste and heatsink application dataMultiview rig + handheld grippers, not stereoThe same rowThe first-person sibling; stereo and MCAP are not its subject
Stereo electronics and device repair dataStereo, agreed in the specOne row, Device Repair (Hard), Active collectionRepair counter work; a different row and environment
Stereo soldering and circuit board assembly dataStereo, agreed in the specTwo rows, Circuit board assembly (Medium) and Component soldering (Hard), both Available on requestBoard assembly and soldering; different rows and environment
Stereo data center rack and server hardware dataStereo, agreed in the specTwelve Data Center & IT Hardware Bench rows, all Available on requestRack and server bench work; different rows and environment
Egocentric stereo data in MCAPStereo, hubThe stereo and MCAP hub across tasksGeneral stereo and MCAP treatment; not specific to paste or heatsinks

Stated vs not stated

What the site states about stereo capture for thermal paste and heatsink application

Left to right: the item, what the site states, and what that means for a paste and heatsink order. “Not stated” means the site does not say.
ItemWhat the site statesFor a paste and heatsink order
Catalog capture setupMultiview rig + handheld grippers on the rowNo stereo pair is stated for this row; 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 this row 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
OcclusionFingers disappear behind objectsStated; how often it occurs on this row is Not stated
Depth on small and reflective partsSmall fasteners can fall below the depth floor while hand pose stays valid; metric depth on sub-centimetre parts is flagged rather than interpolated; depth degrades on wet and reflective surfaces; confidence maps mask low-confidence regionsStated; the depth floor for this row 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 statusMedium, Available on requestNo volume, hours or delivered stereo footage is claimed on this page
Paste, heatsink, board and tool types, amounts, patterns, tolerancesNot 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 paste and heatsink 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 paste and heatsink 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 thermal paste and heatsink 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
RowApply paste + heatsink, worded as the catalog words itSet per program; Available on request as listed
Scope of an attemptPaste only, seating only, or both in one attempt; start and end stateEpisode boundaries; the site does not state an episode length
Object definitionWhat counts as the manipulated object: the part being seated, the surface it goes onto or bothContact 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 board markings in frame are handledFaces and screens blurred at ingest; 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 thermal paste, a heatsink or a precision assembly bench, and it is not an example of the multiview rig with handheld grippers this row lists.

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

No stereo paste or heatsink 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

Thermal paste robot training data, answered.

What is stereo thermal paste and heatsink application data?
Video of a person applying thermal paste and seating a heatsink, recorded with a calibrated stereo pair so depth is recoverable, with hand pose alongside where the spec calls for it.
Which catalog row covers it, and what is its status?
"Apply paste + heatsink" ("Apply thermal paste and seat a heatsink.", Medium), in Precision Assembly Bench (electronics), listed with Multiview rig + handheld grippers and Available on request. This page claims no delivered hours.
Is stereo already captured on this row?
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 page and the repair and soldering pages?
The egocentric page covers the same row as first-person video. This page covers it with a stereo pair and MCAP delivery. The stereo repair page covers one Device Repair row, and the stereo soldering page covers two board assembly and soldering rows.
Does the site name paste or heatsink types, amounts or quality labels?
No. The site states no paste, heatsink, board or tool type, no amount or pattern, no tolerance, and no coverage, seated-state or defect label for this row. Those details are agreed in the skill spec.
Are board markings readable in the footage?
Not stated. Faces and screens are blurred irreversibly, but printed text or markings on a board or part are not a listed blur category, so raise any need before the spec is signed.
How fast can a custom stereo paste and heatsink 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 row is 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 are MCAP and the delivery formats documented?

Request a custom stereo thermal paste and heatsink application dataset delivered as MCAP.

Tell us the row, the start and end state of one attempt, whether an episode covers paste only, seating only or both, 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 the bench 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.