PFERD Machinist Hand File, Swiss Pattern, Double Cut, Rectangular, #0 Coarseness, 8" Length, 25/32" Width, 7/32" Thickness

The Pferd machinist pillar hand file has a rectangular shape with double-cut Swiss pattern teeth on both sides for precision smoothing and shaping of straight surfaces on stainless steel and exotic alloys. The file's width is narrower than standard hand files for more precise work. It has double-cut Swiss pattern teeth on each side for finishing, sharpening, and deburring, and no teeth on either edge to protect adjacent surfaces. The tang can be used with an optional handle for secure gripping (sold separately). Hand files are used to remove material and smooth and shape workpieces. They have forward-facing cutting teeth and cut when pushed over either a stationary or rotating workpiece. Single-cut teeth are single rows cut diagonally across the width of the file. Double-cut teeth have two sets of rows cut in opposite directions. American pattern files have three coarseness grades. Coarse, also known as bastard cut, is suitable for efficient, heavy material removal where finish is not a concern. Medium, also known as second cut, offers average material removal and finish quality. Fine, also known as smooth cut, provides the smoothest finish. Swiss pattern files have eight coarseness grades, from 00 (coarse), 0 (medium), and 1 to 6 (fine to finest), offering a smoother finish than equivalent American pattern files. For Swiss pattern files the length of the tool is the length of the blade, not counting the tang, which is the pointed end fitted for a handle; for American pattern files the length of the tool is its entire length, including the tang. Pferd manufactures abrasives and cutting tools for grinding, finishing, and cutting. The company, founded in 1799 in Germany, has its U.S. headquarters in Leominster, MA. It meets International Organization for Standardization (ISO) standard 9001.

ASIN

B006P2YFY4

Embedding

CLIP ViT-L/14 · 768d

Distance metric

cosine

Doc fetch

1ms·cache hitGET /v2/namespaces/amazon-products/documents/B006P2YFY4

How it works

Similar query

22msnearest_to_id → /query

Doc fetch goes through Layer's Aerospike pull-through cache; cache hit served the row without touching turbopuffer. The similar query asks Layer for nearest neighbors of the stored product vector — queries don't go through the doc cache, so no cache header is set.