Backend
Infrastructure-Native Computing with Electric Power Grids
arXiv eess.SY0 views
arXiv:2610.08390v1 Announce Type: cross Abstract: Computing is conventionally implemented by hardware engineered for information processing. Here we investigate infrastructure-native computing: the use of a physical system built for another primary function as a fixed computational operator. In time-domain simulations of an IEEE 14-bus electrical network, Kirchhoff's current law and Ohm's law relate voltage-reference perturbations applied at distributed controllable nodes interfaced by power electronics converters to current responses through a topology-dependent transformation. A trained digital encoder and decoder exploit this transformation for image classification, reaching 91.5% accuracy on MNIST and 82.25% on Fashion-MNIST. The modeled operator is represented by 933 surrogate parameters, compared with 12,340 task-trained parameters for an accuracy-matched fully connected core transformation. Current superposition further supports concurrent spatial sharing of the operator and sequential temporal reuse, with per-stream accuracies above 85% and 93%, respectively, in surrogate-model evaluations. Evaluations on CIFAR-10 and repeated 10-class tasks sampled from a Butterflies-and-Moths dataset show that the incremental utility of the physical operator depends on the representation supplied by upstream digital feature extraction. These results provide a simulation-based proof of concept for infrastructure-native computing with electrical networks and identify topology, accessible control channels, and input representation as determinants of its computational utility.
Source:https://arxiv.org/abs/2610.08390PreviousSC3BF: Shifted Collision Cone Control Barrier Function for Dynamic Obstacle AvoidanceNextStable Rational Approximation of PDE Transfer Functions with $H_\infty$ Error Bounds
Related posts
I read all 308 open jobs at xAI: 54% are in its data center team, and most of them are in Memphis
0dev.to AI
Claude Code marketing analytics with an app-scoped key
0dev.to AI
I red-teamed my own support bot with 30 scenarios. It failed 7 — here's the harness.
0dev.to AI
The Log That Told Everyone the Password: Redacting Secrets in n8n Execution Logs
0dev.to WebDev
Your AI Portal Isn't Ready Until a Stranger Can Recover from Failure
0dev.to WebDev
API traffic monitoring: what to track, and how to set it up for a Node API
0dev.to Security