soldermaskdocs

The pipeline

The pipeline turns one sentence into a folder of fab files. Each stage reports what it could not do.

The command line prints the stages in order as they run. The app runs the same code, workspace.realise(), and shows each stage in the build log.

The stages, in order

StageWhat it doesModules
1DesignA model turns the prompt into parts, nets and a board sizedesign.py, schema.py, priors.py
2Parts and packagesFinds a real LCSC part and a footprint for each componentresolve.py, parts.py, packages.py, easyeda.py
3Symbols and pinsTurns pin function names into pad numberssymbols.py
4SimulationSwitches the rails on in ngspice and reads what settlesspice.py
5Electrical rule checkChecks the netlist against electrical rules. It changes nothing.erc.py, electrical.py
6Placement and routingPlaces the parts, routes the copper and pours groundplacer.py, mounting.py, keepout.py, escape.py, pour.py, planes.py, pairs.py, widen.py, fillet.py, dsn.py, ses.py
7RoutersLightcycle routes and ranks every placement; the A* router routes when namedrouter.py, tandem.py, astar.py
8Fab filesWrites the Gerbers, drill, BOM and CPL, then reads them backgerber.py, assembly.py
9Stock and pricingChecks stock and price at 1, 10, 25 and 100 boardsinventory.py
10KiCad and 3D modelsWrites the KiCad files, fetches 3D models, and runs KiCad's DRCkicad.py, models3d.py, kicadcli.py
11Reviews and verdictGrades the layout, checks JLCPCB's limits, writes the schematic and stamps the verdictrubric.py, physics.py, layout_rules.py, fabrules.py, kicad_sch.py, repair.py

If the copper alone fails, the build runs again with the power nets poured. It keeps whichever build has fewer copper failures. See Power pours.

A board imported from a KiCad file skips stages 1 to 5. Its parts, nets and outline come from the file, and no simulation or ERC runs.

Everything the build made is then saved as one version that never changes.

Around the stages

  • Routability: the model that rates a placement's chance of routing. In a default build it ranks nothing, because Lightcycle ranks the placements by routing them. It lives with the research.
  • Repair loop and evaluation: the pass rule every board is judged by, and the benchmark suite.
  • What is not guaranteed: every limit of the pipeline, in one place.

The instruments that ask whether routing can be predicted rather than run are not stages. They are under Research.

On this page