9cd5061732
The directory grew well beyond Wokwi-only contents: it now hosts
lcgamboa's QEMU fork (qemu-lcgamboa), Espressif's esp32-camera, the
ngspice WASM build, fritzing-parts, picowi, an alternative QEMU
(qemu-esp32), the 100_Days_100_IoT_Projects examples repo, and
Wokwi's own avr8js/rp2040js/wokwi-elements/wokwi-features/wokwi-boards.
"wokwi-libs" was misleading — half the contents have nothing to do
with Wokwi. "third-party/" is the standard convention for vendored
external dependencies.
Mechanical changes:
Path rename:
wokwi-libs/ → third-party/
update-wokwi-libs.bat → update-third-party.bat
docs/WOKWI_LIBS.md → docs/THIRD_PARTY.md
Submodule reconfiguration:
.gitmodules — 4 path= and section names updated
.git/modules/wokwi-libs/ → .git/modules/third-party/
each submodule's .git file rewired to ../../.git/modules/third-party/<name>
Reference updates (~80 files): vite.config.ts aliases, Dockerfile
COPY paths, GH Actions workflow steps, build_qemu_*.sh, all
docs/* and test/*/autosearch/* entries that mention the path,
package-lock.json file: dependencies, .gitignore patterns,
sitemap.xml + index.html SEO blurbs, scripts/generate-component-*,
.dockerignore, .idea/vcs.xml. Bulk replaced both `wokwi-libs/`
(path) and bare `wokwi-libs` (textual mentions in docs/comments).
Verified:
- npx tsc -b --noEmit produces no new errors related to these paths
- vite.config.ts aliases now point at ../third-party/avr8js etc.
- All 4 git submodules (avr8js, rp2040js, wokwi-elements,
wokwi-features) are linked under third-party/ with their
worktrees re-populated and config files referencing the new path
- `grep -r wokwi-libs` returns zero hits outside node_modules,
.vite, frontend/dist, third-party/ (upstream submodule contents),
*.pyc caches, and *.dll.pre-camera rollback binaries
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| README.md | ||
| phase_0_scope.md | ||
| phase_1_libraries.md | ||
| phase_2_solver.md | ||
| phase_3_passives.md | ||
| phase_4_actives.md | ||
| phase_5_avr_integration.md | ||
| phase_6_end_to_end.md | ||
| phase_7_ngspice.md | ||
| phase_8_velxio_implementation.md | ||
| phase_9_component_catalog_expansion.md | ||
| phase_10_electromech_and_ics.md | ||
| plan1.md | ||
README.md
test_circuit — plan
Carpeta de planificación para la campaña de pruebas de emulación de circuitos.
Estructura
plan1.md— plan maestro original (SPICE + ngspice WASM, propuesta grande)phase_0_scope.md— alcance inicialphase_1_libraries.md— librerías evaluadasphase_2_solver.md— solver hand-rolled (legacy, baseline de comparación)phase_3_passives.md— pasivos (R, C, L)phase_4_actives.md— activos (diodo, LED, BJT, MOSFET)phase_5_avr_integration.md— integración con avr8js (estilo Velxio)phase_6_end_to_end.md— E2E pot→PWM-LED y termistorphase_7_ngspice.md— ngspice-WASM víaeecircuit-engine+ co-simulación avr8jsphase_8_velxio_implementation.md— plan de implementación en Velxio (definitivo): componentes nuevos (genéricos + reales), instrumentos, fases 8.1–8.6phase_9_component_catalog_expansion.md— expansión del catálogo: XNOR, SPICE mappers para las gates existentes, PNP/P-MOSFET, op-amps reales, reguladores, fuentes (complementa fase 8 con los huecos detectados enautosearch/05_velxio_component_inventory.md)phase_10_electromech_and_ics.md— electromecánica (relé), aislamiento óptico (optoacopladores), packaging de lógica (74HC00/04/08/14/32), flip-flops (D/JK/T) y driver de motores L293D
Cómo correr
cd test/test_circuit
npm install
npm test
Resultados se documentan progresivamente en ../autosearch/.