Python module for creation and manipulation of GDSII files.
Gdstk (GDSII Tool Kit) is a C++ library for creation and manipulation of GDSII and OASIS files. It is also available as a Python module meant to be a successor to Gdspy.
Key features for the creation of complex CAD layouts are included:
Typical applications of Gdstk are in the fields of electronic chip design, planar lightwave circuit design, and mechanical engineering.
The complete documentation is available here.
The source files can be found in the docs directory.
The C++ library is meant to be used by including it in your own source code.
If you prefer to install a static library, the included CMakeLists.txt should be a good starting option (use -DCMAKE_INSTALL_PREFIX=path
to control the installation path):
cmake -S . -B build
cmake --build build --target install
The library depends on zlib.
The Python module can be installed via pip, Conda or compiled directly from source. It depends on:
Simply run the following to install the package for the current user:
pip install --user gdstk
Or download and install the available wheels manually.
Windows users are suggested to install via Conda using the available conda-forge recipe. The recipe works on MacOS and Linux as well.
To install in a new Conda environment:
# Create a new conda environment named gdstk
conda create -n gdstk -c conda-forge --strict-channel-priority
# Activate the new environment
conda activate gdstk
# Install gdstk
conda install gdstk
To use an existing environment, make sure it is configured to prioritize the conda-forge channel:
# Configure the conda-forge channel
conda config --env --add channels conda-forge
conda config --env --set channel_priority strict
# Install gdstk
conda install gdstk
The module must be linked against zlib. The included CMakeLists.txt file can be used as a guide.
Installation from source should follow the usual method (there is no need to compile the static library beforehand):
python setup.py install
Help support Gdstk development by donating via PayPal or sponsoring me on GitHub.
The benchmarks directory contains a few tests to compare the performance gain of the Python interface versus Gdspy. They are only for reference; the real improvement is heavily dependent on the type of layout and features used. If maximal performance is important, the library should be used directly from C++, without the Python interface.
Timing results were obtained with Python 3.11 on an Intel Core i7-9750H @ 2.60 GHz They represent the best average time to run each function out of 16 sets of 8 runs each.
Benchmark | Gdspy 1.6.13 | Gdstk 0.9.41 | Gain |
---|---|---|---|
10k_rectangles | 80.2 ms | 4.87 ms | 16.5 |
1k_circles | 312 ms | 239 ms | 1.3 |
boolean-offset | 187 μs | 44.7 μs | 4.19 |
bounding_box | 36.7 ms | 170 μs | 216 |
curves | 1.52 ms | 30.9 μs | 49.3 |
flatten | 465 μs | 8.17 μs | 56.9 |
flexpath | 2.88 ms | 16.1 μs | 178 |
flexpath-param | 2.8 ms | 585 μs | 4.78 |
fracture | 929 μs | 616 μs | 1.51 |
inside | 161 μs | 33 μs | 4.88 |
read_gds | 2.68 ms | 94 μs | 28.5 |
read_rawcells | 363 μs | 52.4 μs | 6.94 |
robustpath | 171 μs | 8.68 μs | 19.7 |
Memory usage per object for 100000 objects:
Object | Gdspy 1.6.13 | Gdstk 0.9.41 | Reduction |
---|---|---|---|
Rectangle | 601 B | 232 B | 61% |
Circle (r = 10) | 1.68 kB | 1.27 kB | 24% |
FlexPath segment | 1.48 kB | 439 B | 71% |
FlexPath arc | 2.26 kB | 1.49 kB | 34% |
RobustPath segment | 2.89 kB | 920 B | 69% |
RobustPath arc | 2.66 kB | 920 B | 66% |
Label | 407 B | 215 B | 47% |
Reference | 160 B | 179 B | -12% |
Reference (array) | 189 B | 181 B | 4% |
Cell | 430 B | 229 B | 47% |