(c) 2026 Santiago Hofwimmer BSc
Institute for Integrated Circuits and Quantum Computing, Johannes Kepler University (JKU), Linz, Austria
[!WARNING] This repository is a Work in Progress.
[!IMPORTANT] It is recomended to use the IIC-OSIC-TOOLS container. Otherwise, you have to install Ngspice, Xschem and IHP-Open-PDK manually as prerequisites.
[!IMPORTANT] Currently, only the IHP-Open-PDK is fully supported, but more will follow soon

Chipify is a high-performance EDA (Electronic Design Automation) tool for mismatch simulations, parameter sweeping, and yield analysis. It wraps Xschem (schematic capture) and Ngspice (circuit simulation) to automate Monte-Carlo and corner sweeps, run them in parallel, and turn the raw results into plots, yield matrices, and reports.
It ships with both a PySide6 (Qt) desktop GUI and a headless CLI, plus a plugin system for custom plots, reports, and expressions.

range, linspace, and logspace parameter sweeps (safely parsed, no eval).
Chipify is a wrapper around external EDA tools, so these must be installed and
available on your PATH:
libegl1 / libgl1 (libEGL.so.1 / libGL.so.1) are dlopened when Qt
is imported — required even for the headless test suite. Without them you get
ImportError: libEGL.so.1: cannot open shared object file.libxcb-cursor0 (Qt ≥ 6.5) is needed by the xcb/XWayland platform for
the on-screen GUI; without it a Wayland session falls back to native Wayland,
where dropdown menus don’t close on selection.install.sh installs all of these automatically on Debian/Ubuntu; elsewhere
install them with your package manager (e.g. apt install libegl1 libgl1
libxcb-cursor0). System libraries can’t be declared in
setup.py/pyproject.toml, so they’re handled by install.sh.
It is highly recommended to install and run Chipify inside the IIC-OSIC-TOOLS docker container. This way, all the required tools plus a bunch of open source PDKs are already installed.
git clone https://github.com/santihofi/chipify.git
cd chipify
python -m venv venv
# Linux/macOS:
source venv/bin/activate
# Windows (PowerShell):
venv\Scripts\Activate.ps1
pip install .
Optional extras:
pip install ".[fast]" # numexpr — vectorized transient-equation evaluation
pip install ".[vacask]" # PyOPUS — VACASK simulation backend
For development, install in editable mode: pip install -e .
(On Linux/macOS, install.sh is a one-line convenience wrapper for the venv + install steps above.)
chipify
This opens the desktop application where you can edit datasheets, launch sweeps, and explore results interactively.
See examples/datasheet.yaml for a documented
datasheet template (and examples/README.md for how to run
it). Place your datasheet YAML in the input folder (datasheets/ by default), then:
chipify-cli -c my_design.yaml # run a single datasheet
chipify-cli --batch ./datasheets # run every *.yaml in a directory
chipify-cli -c my_design.yaml --json # also print a JSON summary (handy for CI)
chipify-cli -c my_design.yaml --markdown report.md
Results are written to the output folder (out/ by default), including
simulation_results.csv and any generated reports. Run chipify-cli --help
for the full list of options.
User preferences are stored in settings.json in the directory you launch
Chipify from (CPU cores, simulator engine, theme, live plotting, custom
equations, …). The file is created/updated by the GUI’s settings dialog.
By default Chipify uses this layout under the working directory:
| Folder | settings.json key |
Default |
|---|---|---|
| Input datasheets | in_dir |
datasheets/ |
| Simulation output | out_dir |
out/ |
| Scratch / temp | work_dir |
tmp/ |
| Testbench files | tb_dir |
tb/ |
To relocate any of them, set the corresponding key in settings.json to an
absolute or relative path, e.g.:
{
"out_dir": "results",
"in_dir": "/data/chipify/datasheets"
}
Any key that is missing or blank falls back to its default. Paths are resolved when Chipify starts, so changes take effect on the next launch.
A source follower example is included. to run the example, navigate to /chipify/examples/source_follower and run chipify in this directory. You can select between two datasheets describing a corner case and a mismatch simulation.
chipify/ # engine (no GUI-toolkit deps)
cli.py # CLI entry point + GUI launcher
simulator.py # multiprocessing simulation engine
schema.py # datasheet validation + range DSL
expression.py # sandboxed expression evaluation
settings.py # project folder paths (configurable via settings.json)
app_config.py # persistent preferences + logging
data_loader.py # results loading / pass-fail / history (shared, headless)
uikit/ # toolkit-agnostic GUI-support layer (state, services, plugin facade)
gui_qt/ # PySide6 (Qt) desktop GUI (tabs / controllers / workers / widgets)
tests/ # pytest suite for the core engine + GUI smoke tests
See context.md for the full architecture overview and PLUGINS.md for the plugin API.
pip install -e .
pytest # run the test suite
python -m mypy chipify/settings.py # strict type-checking (see pyproject.toml)
Licensed under the Apache License 2.0.