skill

molecule-publish

Public Made by Adom

by adom

Publish molecules AND generic boards to the Adom wiki - one publisher, two shapes: OCCT conversion (molecule mode with stats gates, or plain for boards), component packaging, adom-wiki publish, APM re

moleculepipelinewikihydrogenskill
Overview Files Skills Discover Packages Releases Dependencies Issues12 Breadcrumbs Pull Requests Activity
Open bug report

Boards that can never render: ~16 pages published with no EDA source (split from #130)

barrett-land · 1d ago

Split out of #130, which assumed these could be backfilled by re-running --render-board off the wiki source. They can't — the source was never published.

The problem

~16 board/molecule pages have no render/ folder and can't get one, because the only files on the page are outputs: gerbers, PNG previews, BOM/CPL CSVs, and sometimes a GLB. There is no .kicad_pcb / .kicad_sch / .kicad_pro for the render service to consume, so they permanently trip APM's red "missing render folder" bar.

This is not a molecule-publish bug. It's a gap in what those publishes shipped, and closing it needs the original designs off a design machine.

Group A — Fusion 360 exports, gerbers + PNGs only (14)

adom/7in-display-moleculte, adom/bmv080-i2c-mpin-molecule, adom/capacitor-molecule-panelized, adom/capacitormolecule2, adom/capacitormoleculepanelized2, adom/coral-breakout-stand-molecule, adom/ina219-breakout-board, adom/molecule-rp2350b-pican2b-v1-318000, adom/moleculentx15r, adom/naneye2d-control-molecule, adom/pico2-2w-molecule, adom/rp2040-devboard-molecule, adom/vl53l4cdv-molecule, adom/coldfire-xilinx-dev-board

Plus adom/rp2040-test-board, which has only a GLB.

Mostly Kyle's Fusion exports. Needs the original .f3d/.brd re-exported and re-published through molecule-publish board mode. Note EAGLE/Fusion sources currently skip rendering anyway (they report "nothing rendered"), so until Fusion rendering lands in APM these will show a static version label even once source is published — worth confirming that's acceptable before anyone spends time on the re-export.

Group B — COSMIIC, Altium project zips (2)

cosmiic/cosmiic-biopotential-amplifier-eval-board-465000, cosmiic/cosmiic-pulse-generator-eval-board-545000

Both ship a *-altium-project.zip. --render-board has no Altium path at all. Either convert to KiCad (adom-lbr can read .SchLib/.PcbLib) or wait for an Altium render path.

Group C — one that's probably cheap (1)

cosmiic/cosmiic-power-module-eval-board-357000 ships cosmiic-pm-kicad-project.zip — a real KiCad project, just zipped. Unpacking it and re-pushing the loose .kicad_pcb/.kicad_sch/.kicad_pro alongside the zip should make it renderable with no design machine at all. Best first candidate.

Also worth deciding

Should molecule-publish refuse to publish a board with no EDA source, or at least warn loudly? Every page in Group A got through the pipeline in a state that can never render in APM, and nothing flagged it at publish time. A gate there stops this list from growing.

Suggested acceptance

  • Group C unpacked + rendered (cheap, no design machine)
  • Decide whether Group A's re-export is worth it given Fusion rendering isn't live yet
  • Decide Altium path for Group B (convert vs wait)
  • molecule-publish warns or gates when a board publishes with no renderable source

0 Replies

Log in to reply.