Toolchain

Monata can call external simulators and model compilers. These pages explain those tools in detail. Use them when the user guide tells you to choose, configure, or debug a backend or compiled model.

• External Tool Setup
  • Distribution Boundary
  • How Monata Finds Tools
  • Current Required Backend
  • Recommended: Build a Local Conda Channel
  • Create a Pixi Runtime Environment
  • Fallback: Build ngspice From Upstream Source
  • Optional and Deferred Tools
  • Model and PDK Files
• ngspice
  • Runtime Contract
  • Distribution and License Boundary
  • Supported Task Inputs
  • Explicit Limitations
• Xyce
• OpenVAF and OSDI
  • Registry and Cache
• ADMS

How These Pages Relate to Monata

Tool	Role in Monata
External tools	Public installation boundary, lizhangmai-skills local conda-channel workflow, and pixi environment setup
ngspice	Current local SPICE backend: subprocess by default, shared-library runner when libngspice is user-provided
Xyce	Deferred scalable SPICE backend
OpenVAF	Deferred Verilog-A compilation path; existing OSDI artifacts can be loaded by ngspice
ADMS	Deferred Verilog-A to Xyce plugin generation path

The main user guide stays focused on Monata objects and workflows. Toolchain pages cover backend-specific syntax, installation, limitations, and examples.