Backend
Local AI Agents in Power Electronics Simulation: Deployment, Measurements and Costs
arXiv eess.SY0 views
arXiv:2611.24880v1 Announce Type: cross Abstract: Agentic artificial intelligence (AI) is emerging in power electronics, where it drives the simulation loop that engineers used to close largely by hand. In this loop, a converter design, or a study of the network it connects to, is built, run, measured and revised until it satisfies its specification. Such an agent can be served from a cloud API or from an inference device on the premises. For organizations whose designs, customer data or export-controlled material cannot leave the site, and whose simulators are licensed there, local deployment is the natural choice. In such a deployment, the agent becomes an electrical load on the organization's own equipment, i.e., every run consumes power and energy on a local device, generates tokens and takes time. However, existing work focuses mainly on what the agent can achieve with cloud-hosted models. What a local deployment costs in power, energy, tokens and time on real simulation tasks, and what its choices trade against one another, has received little quantitative investigation under comparable conditions. To address this gap, a systematic evaluation framework is presented in this paper. It applies locally served models to agentic power electronics tasks, from the converter level to the system level, and measures their power, energy, token and time costs. Based on these measurements, the capability boundary of a local agent on such tasks and the cost per solved task are characterized. The results are expected to provide practical insight for the use of agentic AI in power electronics and the power systems it serves.
Source:https://arxiv.org/abs/2611.24880PreviousCommunications-free Collective Intelligence Via Allocentric BeliefNextGeneral formulation of an analytic, Lipschitz continuous control allocation for thrust-vectored controlled rigid bodies
Related posts

Signal is blocking Gemini and Siri AI from reading your screen
0The Verge
12 Paid Calls, 0 Answers: A Contract That Says Every Field Is Optional
0dev.to
Auditing a WooCommerce checkout from the shell before Black Friday
0dev.to

Fix Kubernetes CrashLoopBackOff in k3s: A Debug Guide
0dev.to
Four columns that stop a size-ambiguous furniture inquiry from being priced wrong
0dev.to
Wi-Fi Calling where there is no cellular signal: what the phone, ePDG and IMS do on the call path
0dev.to