Parametric CAD
Reconstruction in build123d
01Overview
We rebuild parts as parametric CAD programs. From a reference model (STEP, STL, drawings or cross-sections), we write a standalone build123d script that reproduces the part to within an agreed tolerance. build123d is a Python CAD library built on the Open CASCADE kernel, so the output is plain code that runs anywhere Python does.
The scripts are written the way an engineer would model the part. Key dimensions are named parameters, features are built from standard operations (sketches, extrusions, revolves, holes, pockets, fillets), and repeated or symmetric geometry comes from loops and patterns. Design intent stays in the code, and a change is made once, in one place.
Each script is run in a clean environment, and its output is measured against the reference on volume, surface area, bounding dimensions, centre of mass and shape deviation. A part is accepted only when it meets the agreed limits on every check. A reviewer then reads the code for structure, naming and editability.
Each part is delivered as one record: the reference, the Python script, STEP and STL files generated by that script, an evaluation report, and a manifest linking them together. Records are available as ready-made datasets or built to order from your own reference parts.
02Modelling approach
Each reconstruction begins with the reference and ends with a script that regenerates it. The script follows ordinary feature-based practice, so a reader can follow the build sequence from the first sketch to the last fillet.
| FEATURE GROUP | TREATMENT IN THE SCRIPT |
|---|---|
| Profiles and solids | Sketches, extrusions and revolved features form the base body. Profile dimensions are named parameters. |
| Holes and pockets | Bores, cut-outs and other local features are applied as separate operations, positioned from stated datums. |
| Patterns and symmetry | Repeated or mirrored features come from loops, patterns and shared logic. Geometry is not duplicated. |
| Edges and transitions | Fillets and chamfers use named radii, so each can be changed on its own. |
Design datums and feature parameters are kept distinct from traced geometry. Where a complex feature cannot be described by standard operations, fitted geometry may be used. Each such decision is documented in the part's record.
Explore the Kaya Robot.
Inspect the supplied assembly and individual reconstructed parts alongside their Python scripts and reported validation results.
Kaya Robot Assembly
Loading supplied Python…
03Validation
Validation answers three questions: does the script run, does the result match the reference, and is the code sound. The checks and acceptance limits are agreed for each project, and the results are linked to the relevant model record.
3.1 Execution
The script is run in the agreed environment, and the generated outputs are inspected.
3.2 Geometry comparison
A single measurement is not enough. Matching volume can hide a misplaced hole, and matching overall dimensions can hide a missing pocket. Each part is therefore compared on several measurements, against limits set for the selected models.
| MEASUREMENT | WHAT IT CHECKS | WHAT IT DOES NOT ESTABLISH ALONE |
|---|---|---|
| Volume | Total occupied volume compared with the reference. | Correct placement of individual features. |
| Surface area | Agreement of the exposed surfaces in aggregate. | Exact shape or feature position. |
| Bounding dimensions | Overall dimensions in a consistent coordinate frame. | Internal geometry or modelling intent. |
| Centre of mass | Distribution of geometry under a consistent density assumption. | Agreement of every local feature. |
| Shape deviation | Spatial differences or overlap between reference and output. | Readable code, or behaviour under parameter edits. |
3.3 Code review
A reviewer checks that the script expresses features through named parameters, reusable operations, loops, patterns and symmetry. Numeric tables need context, so that design datums and feature parameters can be told apart from traced geometry. Comments should explain the purpose of each function and the reasoning behind modelling decisions.
Where editability is part of the agreed scope, parameter changes are also tested. A readable script does not by itself show that every dimension can be changed safely.
3.4 Reported results
Measured against the reference, for the evaluated collection:
Passed all five validation checks
Symmetric difference of 0.1% or less
Median symmetric difference
Source: SoftAge, build123d CAD Reconstruction Project Summary, evaluated collection. The pass rate reflects all five checks against the stated acceptance limits. Shape-difference figures are symmetric difference against the reference geometry.
Evaluation reports identify the tested model, the comparison method, the environment and the acceptance criteria. A result is meaningful only alongside the conditions that produced it.
04Deliverables
A stable identifier links the reference, the program, the generated geometry and the evaluation evidence. The delivery package is agreed for the selected collection or custom project.
| COMPONENT | PURPOSE | TYPICAL FORM |
|---|---|---|
| Reference | Identifies the source geometry used in the reconstruction. | Source file or recorded path |
| Program | Contains the build123d modelling logic. | model.py |
| Solid output | Provides generated exchange geometry. | model.step |
| Mesh output | Provides a generated surface mesh. | model.stl |
| Evaluation | Records measured differences and review outcomes. | Agreed report format |
| Manifest | Links record identity, files, units and status. | Agreed manifest format |
05Dataset organisation
Records are organised at three levels.
| LEVEL | ORGANISATION | LINKED INFORMATION |
|---|---|---|
| Project | Groups related models and associated deliverables. | Project identity and delivered records. |
| Part | Connects a model to its program and exports. | Reference, Python, geometry and review status. |
| Assembly | Organises related parts where assembly work is included. | Part relationships and agreed placement checks. |
06Scope and considerations
- Geometry comparison does not establish manufacturing suitability, structural performance or certification.
- Assembly placement, joints, constraints and motion require explicit scope and separate checks. Part validation does not establish assembly correctness.
- Complex features may require fitted geometry. Modelling decisions and any exceptions are documented per record.
- Model coverage, deliverable availability and acceptance criteria are confirmed for the selected collection or project.
07Project Collection
- 01Macro keyboard
- 02Parametric case
- 03RFM-69 container
- 04Keyberon Grid
- 053D Macro Keyboard
- 06BMS-C1
- 07Openscad-Screen-Case
- 08fbomb
- 09Mini Monitor
- 10Swap-Pi-Raspberry-Pi-5-case
- 113w6-split-keyboard
- 123D Electronics Enclosure
- 13Pteron Keyboard
- 14JP01
- 15Forager Case
- 16Pi-Camera
- 17Brkout-Keyboard
- 18Thermal-Camera-Casing
- 19ICPMS
- 20Arduino Macro Keyboard
- 21Entropy
- 22Tiny Touch
- 23Theia
- 24ESP32-cam-OV5640
- 25Void 40
- 26ESP32-S3_TFT_Combiner
- 27clawd-mochi
- 28krtkus
- 29Fulcrum
- 30ESP32_Web_Radio_I2S
- 31gridfinity-objects
- 32devCases
- 33snap_fit_box
- 34DIY MacroKeyboard
- 35southerly-split-keeb
- 36deskhop
- 37n64cartreader
- 38framework
- 39openscad-portfolio
- 40open-smartwatch-light
- 41Lumen PNP
- 42Chu-Pico
- 43uno-q-enclosure
- 44Forest Guard
- 45XIao
- 46scad-keyboard-cases
- 47popn-pico
- 48open-joystick
- 49cheap_boi
- 50GJ-Tho-Modular-V2
- 51vacuum-pump-controller
- 523D spacemouse
- 53dormouse
- 54Nucdeck
- 55Ketron-EVM-MIDI-Controller
- 56Nerdminder_v2
- 57FFB-Joystick-Base-Plywood
- 58raspberry-pi-3-model-a-plus
- 59case-for-little-backup-box
- 60bananasplit
- 61musec_pico
- 62m2-enclosures
- 63pouetpouet-board
- 64silakka54
- 65Hall-Effect-Sensor-CAD-Mouse-Spacemouse
- 66kaya-robot
- 67ccadquery-models
- 68Anemometer-3D-files
- 69Air-mouse
- 70Klacker_BS
- 71hyperpixel-raspi4b-case
- 72stack-chan
- 73Thor
- 74MicroManipulatorStepper
- 75esp32-cases-stl
- 76dactyl-keyboard
- 77Oak-Compact-Joystick
- 78YAPP_Box
- 79SBC_Case_Builder
- 80Forest-Joystick-Mouse-Hub
- 81Enclosures
- 82launch
- 83gridfinity_openscad
- 84bishi_pico
- 85Huxley
- 86Cases
- 87nes-ra-adapter
- 88BabyCube
- 89Nextis-AIRA-3D
- 90ZeroPanels
No projects match. Try another name or complexity.
Get in touch.
For build123d datasets, reconstruction projects, or sample enquiries, tell us about your requirements.
