Egocentric Drain Snaking and Clearing Data

It is first-person video of a person snaking a drain, recorded from a head-mounted camera, with two wrist cameras for a closer view of the hands. The contributor is a paid, consented person following a written skill spec, not an actor and not a robot.

The point of the data is what the hands do across the whole job: feeding the auger into the line, working through the blockage, and then flushing the drain or checking the line with a light. It is labeled so each step can be sliced out and trained on separately or as one longer episode. Where the site states nothing, a table says "Not stated" and the answer lives in the spec or the quote.

The task catalog lists two rows for it, both in the Trade Service Calls (Plumbing / HVAC / Electrical) environment, whose examples are a plumber, electrician or HVAC crew on service calls at client sites. One is "Drain Snaking & Clearing": "Feed a drain auger into the line, work through the blockage and flush the drain." The other is "Snake and clear drain lines using a drain auger and inspection light": "Feed the drain auger into the pipe, clear the blockage and check the line with a light."

Both are Medium, both list a head-mounted phone or multiview rig, and both are Ready to deploy. That is everything the catalog states, so the first table sets the two rows side by side and the rest of this page says "Not stated" wherever a buyer might expect a detail such as a pipe size, a drain type or an auger model.

The wording is close but not the same. The first row names a drain auger in its description and ends by flushing the drain. The second row names two tools in its title, a drain auger and an inspection light, and ends by checking the line with a light, with no flush step.

A buyer can ask for either, or for both in one spec. The site does not say how the two overlap in practice, whether a flush follows the light check, or what the light is pointed at, so the spec states which stages are wanted and where each begins and ends.

The two rows give a natural cut: feed the auger into the line; work through the blockage; flush the drain; check the line with a light. A spec that says "clear the drain" gives you one long action segment. A spec that names those stages gives you a sequence you can slice by step.

The step table sets each stage beside the episode field that carries it. The stages are the catalog’s own wording. How finely a spec splits them, and where each one starts and ends, is a spec decision and not a stated default. The catalog does not say how many attempts, or how long a blockage, make up one episode.

The catalog ties both rows to the Trade Service Calls environment and lists a head-mounted phone or multiview rig. The wider site describes a head camera plus two wrist cameras, a depth sensor and an IMU, shown in the capture table below.

The site does not state which sites host a given row, whether the work is at a sink, a floor drain or a cleanout, how access to a client site is arranged, or how many contributors are available for it. The spec settles location and access, and the quote settles reach.

The catalog marks both rows Medium. It does not say why a row sits at a level, so this page does not explain it beyond what the rows list: feeding an auger in, clearing a blockage, and a flush or a check with a light.

Ready to deploy is the catalog’s status for both rows. The catalog does not define it further, so ask what it means for your region and your timeline when you request the quote.

An episode is one contributor performing one task from the skill spec, recorded with ten hardware-synchronized streams that line up within 2 ms. The site documents a canonical episode schema, and every delivery format is a view of it.

Hand pose is stored as 21 joints per hand in metres in the head frame, with a visibility flag for each joint. Contact events record when a hand meets an object. The site does not say whether the auger, the pipe, the light or a fitting counts as the object, so settle it in the spec.

Action segments carry a start, an end, a verb and a noun from a taxonomy the site states as 97 verbs and 512 nouns, human-reviewed. Every episode links to its contributor’s signed release by a consent artefact ID, and each batch ships with a data card.

The unit of labeling is the action segment: one start, one end, one verb, one noun. Feeding the auger in, working through the blockage, a flush and a light check can each be one segment if the spec asks for it. Instance masks track object IDs per frame at 848×480, which helps keep the auger, the light and the pipe apart.

Every episode is machine-checked, then reviewed by a human against its skill spec, and rejected episodes are recaptured at our cost. The site states no label for blockage type, whether a line is clear, how far the auger went or task success, and no force, torque or tactile reading, so ask for any such label at the start.

The site describes a small set of failure modes and what it does about each. Hands hidden from the camera are flagged by a per-joint visibility bit, not guessed, contact events mark when a hand meets an object, and per-frame instance masks keep objects apart. Which parts of the auger or the line are hidden in this work is Not stated.

Depth ships with a per-pixel confidence map, so a buyer can see where it should not be trusted. The rig is re-solved against a checkerboard at the start and end of every session and accepted only under the 0.28 px RMS reprojection gate. Weak episodes are rejected and recaptured at our cost. The site states no further failure modes for this task, such as lighting, glare, reflections, water, dirt or motion blur, so those are raised in the spec.

Only what the site already states applies. Every contributor signs a written release, and each episode links to it. Faces and screens are detected and blurred irreversibly, a human reviewer confirms that no un-consented person is identifiable, and footage with bystanders who cannot be de-identified is discarded rather than shipped.

The site does not state how a resident or a client at the site is handled beyond that general rule, so settle it in the spec before capture. This is not legal advice, and the executed agreement controls.

The egocentric plumbing and pipe fitting page covers ten plumbing and pipe rows, of which the two drain rows are two. The egocentric water heater replacement page covers one row, in which draining the old heater is a step of the swap and not a drain-clearing task. The stereo plumbing and pipe fitting page covers the stereo layer and points to the egocentric plumbing page for the task rows.

The egocentric commercial janitorial page lists a differently worded row in a cleaning environment, "Drain Clearing & Cleanup", with a plunger or an auger. This page takes just the two Trade Service Calls rows and goes deeper on their steps, tools, labels and capture. A buyer who wants a mix can combine rows from several pages in one spec.

The site states one published timeline: from a signed spec to a first validated batch, a median of 48 hours where coverage is already deep, and typically three to four weeks where it is thin because operators have to be staffed. The site does not say which applies to either row and promises nothing faster, so ask when you request the quote.

Collection is on demand, so a focused brief is a normal starting point. One drain cleared from the first feed of the auger to the final step is a reasonable first unit, and a Spec Pilot is a fast way to prove the fill rate and reject rate before you scale.

Data is delivered in RLDS, LeRobot, WebDataset, HDF5, zarr or Rerun .rrd, or as raw streams with metadata, with the episode schema as the canonical layout. QA runs once, against the canonical episode, before any format is cut. The formats table sets the site’s delivery next to each maintainer’s own documentation, linked under Sources.

The license is perpetual, irrevocable and worldwide, buyer-owned and non-exclusive by default, with exclusivity available as a separate term and the executed order form governing.

Firsthand captures humans, not robots. Episodes carry human hand pose and human action labels, so using them for a specific robot means your own retargeting step. The site does not state robot actions, teleoperation data or any claim about a particular model or embodiment for this task.

What the data gives a lab is the human side of the job: the order of steps, how the hands hold a tool, and where a step begins and ends. A lab can use that for imitation, for segmenting a task into steps or for evaluation. Each of those is the buyer’s own use of the data.

Start with the free sample pack to check the loader and label quality, then move to a Spec Pilot: a small, fast first batch against the written spec that proves the fill rate and reject rate on your conditions before you scale.

A good drain brief names the setting, the tools, the stages of the job, how each stage starts and ends, what counts as a reject and the privacy rule for the site. The site’s skill-spec guide walks through that structure. Then request a custom dataset.