From 3c88e05331af142826ac4cafe56c7536f4d0ae2f Mon Sep 17 00:00:00 2001 From: Your Name Date: Sun, 13 Sep 2026 08:29:19 -0700 Subject: Better comments Also removed unneccesary section from readme --- README.md | 18 ------------------ 1 file changed, 18 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index b5787fd..35959cc 100644 --- a/README.md +++ b/README.md @@ -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. -- cgit v1.2.3