Seve - @shibo I think I know what we need to do...
@shibo I think I know what we need to do on the spice side. It took me a while to figure out but we need to run the spice simulation inside of core with a "plugin" SPICE engine so that we don't need to bundle any WASM. Just going to jot some thoughts:
- We need to introduce
- Each
- Each
-
- We need a basic SPICE engine for testing that is in JS, this may be easy or hard no idea, but it just needs to be basic so that core has a default
-
- SPICE code generation happens in core
- Experiments are run while rendering (async)
- In the docs, inside CircuitPreview, but also in the RunFrame analog tab, we show the simulation with the probes also shown, with color. This makes it clear what part you're looking at
- Circuit-to-svg should also be able to output SPICE graphs
- We need to introduce
simulation_*- Each
simulation_*simulation_experiment_idsimulation_voltage_graphsimulation_current_graph- Each
<simulation>-
platformConfig.spiceEngine- We need a basic SPICE engine for testing that is in JS, this may be easy or hard no idea, but it just needs to be basic so that core has a default
-
<voltageprobe /><ammeter />- SPICE code generation happens in core
- Experiments are run while rendering (async)
- In the docs, inside CircuitPreview, but also in the RunFrame analog tab, we show the simulation with the probes also shown, with color. This makes it clear what part you're looking at
- Circuit-to-svg should also be able to output SPICE graphs
