SPICE Simulation Skills

START HERE for any circuit simulation in the Adom ecosystem. Picks the right SPICE engine (ngspice, LTspice, PSpice for TI, QSPICE, Xyce) for the job and the machine, runs it headless from an AI thread, and knows the licensing limits of each. ngspice in the Ubuntu container is the default; LTspice and PSpice for TI run on a Windows host through Adom Bridge for vendor models. Use when any circuit needs simulating in the Adom ecosystem. Trigger words - spice, simulate, simulation, ngspice, ltspice, pspice, pspice for ti, qspice, xyce, spice model, encrypted model, vendor model, transient, ac analysis, loop gain, monte carlo, which simulator, simulator comparison, spice licensing, run a spice sim, simulate this circuit, check the buck in spice.

The Adom SPICE dashboard - run one circuit study in ngspice (in the container), LTspice and PSpice for TI (on a Windows host through Adom Bridge), overlay the waveforms on one set of axes, measure every engine with the same code, flag where the engines disagree, and keep a ledger of simulation time and AI tokens per run. Use when simulating a circuit in more than one SPICE engine, checking that simulators agree, debugging a model or netlist translation, or showing SPICE results in a dashboard. Trigger words - adom-spice, spice dashboard, compare simulators, run in ngspice ltspice and pspice, do the simulators agree, three engine simulation, overlay waveforms, simulation ledger, spice tokens cost, pspice for ti run, ltspice run from ai.

Decide which SPICE simulator to use for a job in the Adom ecosystem and where to run it (Ubuntu container, WSL2, Lima on Mac, a Windows host through Adom Bridge). Covers ngspice, Xyce, LTspice, QSPICE, PSpice and PSpice for TI with measured pros and cons, install weight and emulation layers. Use when someone asks which simulator to use, where to run it, or what an install costs. Trigger words - which simulator, which spice, ngspice or ltspice, pspice vs ltspice, best spice simulator, spice on mac, spice in wsl, spice in container, wine ltspice, simulator tradeoffs.

Licence terms that decide where each SPICE simulator may run in the Adom ecosystem - containers, VMs, parallel agent runs, hosted web dashboards for other users, commercial use - for ngspice, Xyce, LTspice, QSPICE, PSpice and PSpice for TI. Use when deciding whether a simulator may run in a container, back a dashboard, or have its results published. Trigger words - spice licence, pspice license, pspice price, ltspice eula, can we host ltspice, spice dashboard licensing, commercial use spice, pspice for ti terms.

Install and drive LTspice on a Windows host from an AI thread through Adom Bridge - silent per-user install with no admin, the hidden first-run usage-data dialog that hangs batch mode, running LTspice -b and reading .meas results from the .log. Use when a job needs LTspice or an ADI/LT model on a Windows host. Trigger words - ltspice, run ltspice, ltspice batch, ltspice -b, install ltspice, ltspice on windows host, ltspice hangs, adi model, lt model.

Run ngspice headless in the Adom Ubuntu container - batch runs, measurements in a .control block, parallel Monte Carlo across cores, building ngspice 47 with the shared library, and the parse traps that silently produce no data. Use when running, measuring or debugging a simulation in the Adom container. Trigger words - ngspice, run ngspice, ngspice batch, ngspice meas, ngspice monte carlo, libngspice, build ngspice, ngspice 47, spicelib, pyspice, simulate in the container.

Write one SPICE netlist that runs in ngspice, LTspice and PSpice, and translate between dialects - B sources vs E VALUE, SW vs VSWITCH, .meas vs .PROBE, print syntax, switch thresholds - plus how to cross-check results between simulators. Use when moving a netlist between ngspice, LTspice and PSpice or cross-checking their results. Trigger words - portable netlist, pspice syntax, ltspice syntax, ngspice syntax, convert netlist, b source pspice, vswitch, meas in pspice, cross-check simulators, same circuit different simulator.

Get, install and drive PSpice for TI on a Windows host through Adom Bridge to run TI's encrypted PSpice models - the myTI access key, the admin-only install that a person must finish, the missing batch runner, clicking Run, the V(node) print bug, the 1 to 4 trace limit with third-party models, and reading CSDF output. Use when a TI model only ships PSpice-encrypted, or when PSpice for TI errors out. Trigger words - pspice, pspice for ti, ti pspice model, encrypted pspice model, run ti model, TPS model, webench model, psp_cmd, ORPSIM-16583, ORPSIM-15090, csdf.

Handle vendor SPICE models in the Adom flow - detect encrypted PSpice or LTspice models, know which simulator can run each, validate a fast hand-built behavioral model against the slow vendor model, and what never to do (decrypting). Use when a vendor model will not load, is encrypted, or a behavioral model needs validating. Trigger words - vendor model, encrypted model, $CDNENCSTART, ENCRYPTED_LIB, ti model, pspice model in ngspice, model won't load, behavioral model, validate model, spicecrypt, decrypt model.