USE CASE GUIDE / Semiconductor

AI for analog circuit optimization: make every simulation count

Explore how a specialist model can propose circuit changes, learn from simulator feedback and hand difficult cases to a stronger model.

Read the guide
In this guide

Analog circuit design involves repeated trade-offs. A change that helps one measurement may make another worse. Engineers propose parameters, run simulations, inspect the results and decide where to go next. The value lies in the quality of those decisions across many iterations.

This is a promising setting for specialist AI because proposals can be checked against a simulator. The model does not get to declare a design successful through a convincing explanation. Its changes have to produce measurements that can be compared with the agreed targets.

THE WORKFLOW, AT A GLANCE

Keep the feedback loop grounded in measurements

  1. 01

    Propose a bounded change

    Work within the chosen circuit topology, parameter limits and design targets.

  2. 02

    Simulate and compare

    Measure the result and examine which targets improved, regressed or could not be measured.

  3. 03

    Revise or escalate

    Use the evidence to choose the next step, with a stronger model available when progress stalls.

  4. 04

    Review the best result

    Return the measured candidate and its history for engineering assessment.

The opportunity is in the iteration

Running a simulation is only one part of the work. Someone must choose a sensible change, understand why a result moved, and remember which previous configuration was better. A long sequence becomes difficult to assess if only the final parameter set survives.

Neurologic’s circuit research preserves complete optimization traces: the proposal, the measured result and the next correction. These records make the work inspectable and provide examples from which a specialist model can learn. The useful unit is an evidence-backed sequence, rather than an isolated suggestion.

Train against outcomes that can be checked

The published methodology first teaches a model from collected traces, then uses simulator feedback to refine its behavior. This connects learning to an engineering objective: meeting the specified measurements for the circuit under consideration.

The research also illustrates why the scoring rules matter. A failed measurement must not be treated as a better outcome than a measured result that misses its target. Otherwise, the system can learn to exploit the evaluation instead of improving the design. Engineers need to examine the evidence behind a score, including missing measurements and unsuccessful runs.

A specialist does not have to work alone

The evaluated system combines a trained specialist with a larger model. The specialist works first; evidence of stalled progress can trigger escalation. The larger model continues from the best state already found, so the earlier search remains useful.

In the paper’s controlled internal benchmark, this hybrid approach matched or exceeded the single-model baselines on most tested circuits under the same iteration budget. That result supports further engineering evaluation. It does not establish performance on every topology, process technology or specification, and it is not evidence of a manufactured chip outcome.

Let the engineering team define success

A useful pilot begins with a bounded family of circuits, a fixed simulator setup and explicit parameter limits. Keep the design targets visible, and separate the circuits used for learning from those reserved for evaluation. If a target is relaxed, record that change rather than presenting the new result as success against the original requirement.

Compare approaches under equivalent conditions. Examine specifications met, simulation failures, iteration use and the cost of model calls. Review the best candidates and the histories that produced them. A result that is easy to inspect is more useful than a headline score whose trade-offs are unclear.

  • Which design targets must hold together, rather than individually?
  • Are failed or missing measurements counted honestly?
  • When does escalation help, and what extra cost does it introduce?
  • Can an engineer reproduce the candidate and understand its remaining gaps?

Support engineering judgment with a better record

The business opportunity is to make a demanding optimization loop more systematic and reviewable. The model can explore candidates and preserve a record of measured progress. Engineers still need to decide whether the evaluation represents the design problem they care about and whether a candidate is ready for the next stage of validation.

READ THE ORIGINAL WORK

The research behind this guide.

Based on Neurologic’s public circuit-trace and specialist-training papers. The reported results concern a controlled internal simulator benchmark of a hybrid specialist-plus-larger-model system; they are not a guarantee of silicon performance or general superiority.

Explore the related work
START WITH YOUR WORKFLOW

Bring a circuit family and a clear target.

Explore a simulator-grounded evaluation with your engineering team and agree how useful progress will be measured.

Discuss an evaluation