diff options
| author | Your Name <[email protected]> | 2026-09-13 08:29:19 -0700 |
|---|---|---|
| committer | Your Name <[email protected]> | 2026-09-13 08:29:19 -0700 |
| commit | 3c88e05331af142826ac4cafe56c7536f4d0ae2f (patch) | |
| tree | 1f05487ec87d449c6917e282c2bf3d7a0bd2a56e /README.md | |
| parent | 02158c7613495f1a02a2a8f108cd1c397656ce2b (diff) | |
Better commentsmain
Also removed unneccesary section from readme
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 18 |
1 files changed, 0 insertions, 18 deletions
@@ -74,21 +74,3 @@ make run MODE=offline The benchmark prints the mean squared error for each device model and writes generated netlists, simulation data, and SVG plots under `output/`. - -## Embedded deployment - -The shared-ngspice backend targets a general-purpose computer. Typical -microcontrollers do not have the memory, numerical libraries, filesystem, or -operating-system services required to run ngspice. - -For an embedded deployment, a small SPIRES reservoir (for example, up to 16 -neurons) can run on a microcontroller and transmit each state vector to a host -computer. The host runs the persistent ngspice crossbar and returns the decoded -prediction. A fixed-size binary protocol should include a timestep number, the -state values, and integrity checking so missing or reordered messages can be -detected. - -The producer/consumer pipeline remains useful in that configuration, but the -concurrency spans the microcontroller and host. The two-thread local -implementation is primarily useful when both the software reservoir and ngspice -readout run on the same general-purpose computer. |
