app
AI Flow
Public Made by Adomby adom
Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board.
main
John Lauer
0.1.39: adom-aiflow-etch (colour-preserving, long-axis MPN laser etch), marking on by default for ICs with a finish check, component heroes per eda-component-hero
8ddac71
6d ago
AI Flow 0.1.39
MPN laser etch on the parts, done properly, and component heroes that show the part on its footprint.
adom-aiflow-etch(installed with the package): laser-etches a part's MPN onto the top face of its STEP with adom/adom-chip-laser, but keeps the model's own colours and lays the text along the part's longest top-face direction. The service on its own repaints the whole part black and grey and writes across X (adom/adom-chip-laser#2), so the tool turns the part so its long axis lies along X (and stands Y-up vendor models upright with--up y), keeps only the service's inlay, adds it to the untouched original as a separatelaser_etchpart with its own colour (--mark light|dark|r,g,b), and turns it back into the original frame. On a SOT-23-6 the mark is 0.22 mm along the long axis against 0.14 mm across it. It uses OCP (OpenCascade's Python bindings) in its own venv, made on first use.- Marking is on by default for ICs.
componentsnow defaults toon, andfinishrefuses while an IC's (U*, IC*) bound STEP has nolaser_etchpart;components --etch offdeclines for a run. - Component pages. aiflow-sourcing and aiflow-molecule now require the eda-component-hero hero (etched part, teal dashed copper outlines, footprint silkscreen, pin labels) whenever a component page is created, including through molecule-publish's "create missing component pages" stage, which does not ask for it.
- The components step in the flow says the same: long axis, colours, Y-up models, and leave a part unmarked rather than ship a mark across a polarity stripe or off the face.
# AI Flow 0.1.39
MPN laser etch on the parts, done properly, and component heroes that show the part on its footprint.
- **`adom-aiflow-etch`** (installed with the package): laser-etches a part's MPN onto the top face of its STEP with adom/adom-chip-laser, but keeps the model's own colours and lays the text along the part's longest top-face direction. The service on its own repaints the whole part black and grey and writes across X (adom/adom-chip-laser#2), so the tool turns the part so its long axis lies along X (and stands Y-up vendor models upright with `--up y`), keeps only the service's inlay, adds it to the untouched original as a separate `laser_etch` part with its own colour (`--mark light|dark|r,g,b`), and turns it back into the original frame. On a SOT-23-6 the mark is 0.22 mm along the long axis against 0.14 mm across it. It uses OCP (OpenCascade's Python bindings) in its own venv, made on first use.
- **Marking is on by default for ICs.** `components` now defaults to `on`, and `finish` refuses while an IC's (U*, IC*) bound STEP has no `laser_etch` part; `components --etch off` declines for a run.
- **Component pages.** aiflow-sourcing and aiflow-molecule now require the eda-component-hero hero (etched part, teal dashed copper outlines, footprint silkscreen, pin labels) whenever a component page is created, including through molecule-publish's "create missing component pages" stage, which does not ask for it.
- The components step in the flow says the same: long axis, colours, Y-up models, and leave a part unmarked rather than ship a mark across a polarity stripe or off the face.