SLiCAP — more than symbolic SPICE
Analog design is complex.
Systems engineering tells us how engineers solve complex problems.
SLiCAP makes it doable.
A simulator tells you what your circuit does — after you have chosen the components. SLiCAP tells you what the components must be: it turns a circuit into symbolic design equations, so values follow from your requirements instead of from guessing and re-simulating.
Since version 5.2 it comes with the Structured Electronic Design Environment, which integrates SLiCAP and NGspice into one workspace. It keeps every design decision traceable — from the specification, through the budgets, to the final design report — so you can design first-time-right.
pip install slicap # then start the environment with: slicap
From specification to design report, in one chain
- Specification. Functions, performance and cost requirements are written down as project data — the reference every later decision is checked against, not a note in the margin.
- Budgeting. SLiCAP expresses performance and cost as explicit functions of your device properties — you allocate each contribution its share of the requirement, and solving the expression gives the value that property must have. Noise, DC variance, tolerance, matching and temperature drift all budget the same way.
- Design and verification, one environment. Create and solve design equations with simple, solvable models, and verify your design with NGspice's full device models.
- Report generation. Create graphs, LaTeX and RST snippets from expressions, tables and NGspice simulations. Put them in your LaTeX design documents and Sphinx websites, and keep them up to date with one run.
Nothing is locked in: the environment writes a plain Python script you can read, edit, run from the command line, or import from your own design code — and SLiCAP works perfectly well without the GUI.
SLiCAP is the tool set behind the open-access book Structured Electronic Design and the analog electronics courses at Delft University of Technology.
What it looks like
What it can do
Symbolic and numeric analysis of linear, continuous-time circuits: transfer functions and their polynomial coefficients, poles and zeros, root-locus plots and Routh arrays, noise and noise integration, DC variance for tolerance, matching and temperature budgets, inverse Laplace and network solutions.
Feedback circuits are analysed with the asymptotic-gain model — loop gain, asymptotic gain, servo function and direct transfer, each available on its own. Balanced circuits are converted into their common-mode and differential-mode equivalent circuits, so each mode is designed for what it must do.
Out of all of it come the design equations for bandwidth, frequency response, noise, dc variance and temperature stability. Hierarchical netlists, parameter stepping, and NGspice for numeric verification.
→ Full documentation, tutorials and examples: slicap.org
About
SLiCAP is an open-source Python program by Anton J.M. Montagne, created for and used in structured analog design practice, teaching and research.
Two companions to install. NGspice is the
verification half of the environment — install it and your design is simulated with full
device models from inside the same project. A TeX distribution (pdflatex + dvisvgm)
typesets the expressions on your schematics and builds your LaTeX design reports;
without it SLiCAP falls back to plain text — readable, but not what you want in a
document. Sphinx comes with SLiCAP, so design documentation as a website needs nothing
extra.
See slicap.org for installation details and for building from source.
Contributing
Ideas and contributions are welcome — email us. Found a bug? Please report it on the Issues page.
1 maintainer
Metadata
1 maintainer
Release files for SLiCAP 6.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| slicap-6.4.0.tar.gz | 13.9 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| slicap-6.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.1 MB
Release files / slicap-6.4.0.tar.gz
| Download URL | slicap-6.4.0.tar.gz |
|---|---|
| Size | 13.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ec501bb345758d50aa498092ea8181250664c36a01d09631565bd665fd29cf7
|
|
BLAKE2b-256 checksum How to use checksums |
214df102ae08619c7c0cf412c957d177e5f2c569c636248990c89d97123d080b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / slicap-6.4.0-py3-none-any.whl
| Download URL | slicap-6.4.0-py3-none-any.whl |
|---|---|
| Size | 14.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
035a7a5a659a02bed447707416501cb6799593e1c3273c3604c55e2e49ed3be1
|
|
BLAKE2b-256 checksum How to use checksums |
52ce0900228ef3bc4dcdfb9f14102b9fb15fdae43e667d3894445d27b5ec44e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for SLiCAP 6.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for slicap-6.4.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
