Practical Picks PP-270: earlier hands-on check record, October 3, 2026 Historical note, added October 19, 2026: this is a record of a small local check run on October 3, 2026, before Practical Picks adopted its research-only method later that day. It is kept as a dated observation of one simple part, not as current testing. It did not decide the recommendations in the current article, which rest on public sources read on October 19, 2026. Wording below such as "test" and "tested" describes that October 3 check. The record body is unchanged. Observed October 3, 2026 UTC on Linux x86-64 with Python 3.12.3. Reader job: keep editable source, change one length, regenerate an STL for a small four-hole plate. This is a geometry/export test, not a printer, load, strength, safety or speed test. The protocol was frozen October 1 before installations: 40 x 24 x 5 mm plate, four through-holes of 4 mm diameter, hole centers 6 mm from their nearest X and Y edges. Change length to 52 mm while retaining all other dimensions. STL has no unit metadata; the source treats coordinates as millimeters. Expected initial bounds: X -20..20, Y -12..12, Z 0..5. Revised bounds: X -26..26, Y -12..12, Z 0..5. Analytic volumes: 4548.6725877 and 5988.6725877 mm3. The acceptance checks required watertight, consistently wound, positive-volume meshes; four holes at the specified centers and diameters on a Z=2.5 cross section; bounds within 0.05 mm; and meshed volume within 1% of analytic volume. Exact public source and verifier copies (the link labels are usable in Markdown viewers; the full URLs identify the same public assets in plain text): - [OpenSCAD source](https://practicalpicks.guide/assets/pp270/plate-openscad.scad) - [CadQuery source](https://practicalpicks.guide/assets/pp270/plate-cadquery.py) - [build123d source](https://practicalpicks.guide/assets/pp270/plate-build123d.py) - [Independent mesh verifier](https://practicalpicks.guide/assets/pp270/verify-mesh.py) Browser readers of this plain-text method can use the clickable [source index](https://practicalpicks.guide/assets/pp270/sources.html) after release. On an access-controlled candidate, use `/assets/pp270/sources.html` on the same host. These links describe proposed assets; they do not imply that the private candidate has been published at the public domain. The public copies byte-match the private research originals at the time of this record. Tested products and source commands: - OpenSCAD 2021.01 official Linux AppImage, SHA-256 f758528f2cd213f773c7a105fb63bf3b45bf754b0f586fbb7c9cd653ffcd0882. Run `openscad -D 'length=40' -o openscad-40.stl plate-openscad.scad`, then replace 40 with 52. The command-line override changes the generated model without rewriting the `.scad` file. - CadQuery 2.8.0 from PyPI in a task-local virtual environment. Run `python plate-cadquery.py 40 cadquery-40.stl`, then replace 40 with 52. The source takes length as its explicit model parameter; the file bytes were not rewritten. - build123d 0.13.0 from PyPI in a separate task-local virtual environment. Run `python plate-build123d.py 40 build123d-40.stl`, then replace 40 with 52. The source takes length as its explicit model parameter; the file bytes were not rewritten. An initial 0.10.0 attempt failed at import with `ModuleNotFoundError: No module named 'OCP.collections'` because pip selected incompatible ocp_gordon 0.3.1 for OCP 7.8. Upgrading once to 0.13.0 resolved the import and export. This CLI parameter override is functionally equivalent for the generated geometry but differs from the protocol's literal in-file edit. We did not test the usability of editing each source file in an editor. The source files remain available and editable. Independent verification used trimesh 4.8.3, NumPy 2.5.3, SciPy 1.18.1 and NetworkX 3.7. The first verifier attempt lacked SciPy and NetworkX; installing those verifier dependencies changed no product output. All six final STLs passed. At 40 mm: OpenSCAD mesh volume 4548.851217 mm3 (0.0039% analytic error); CadQuery and build123d each 4548.776727 mm3 (0.0023%). At 52 mm: OpenSCAD 5988.851217 mm3 (0.0030%); CadQuery and build123d each 5988.776748 mm3 (0.0017%). All reported expected bounds and four cross-section holes. Mesh differences come from tessellation. No measured speed ordering follows from these runs. Adverse output-path check: each tool was asked to export to a missing parent directory. OpenSCAD exited 1 and wrote no file. build123d raised FileNotFoundError and exited 1. The frozen CadQuery script exited 0 and printed an export message but wrote no file: its Shape.exportStl() returned False, which that script did not check. CadQuery users should check the return value and resulting file before handoff. This test did not compare every exporter API or path failure. No account or purchase was used. All downloads and virtual environments stayed under /tmp/pp270-20261003. Peak task-local pip cache was 799 MiB; the OpenSCAD AppImage was 39 MiB and an unused Ubuntu package download was 3.2 MiB. These recorded downloads stayed below the 2 GiB cap. No system package was installed. Six generated STLs are retained in private research, along with source SHA-256 hashes and the verifier. No vendor supplied access. No affiliate link was used. Limits: one simple part and one parameter change per product; Linux x86-64 only. We did not test GUI editing, STEP/3MF output, intricate geometry, large assemblies, plugin ecosystems, hostile files, privacy traffic, support response, slicing, real printing or mechanical strength. The documented export formats and project licenses cited in the article are separate from the direct test.