gdsfactory 5.2.9

python library to generate GDS layouts

gdsfactory 5.2.9

gdsfactory is an EDA (electronics design automation) tool to Layout Integrated Circuits. It is built on top of phidl, gdspy and klayout to work with GDSII components, PDKs and masks for different foundries. It combines the power of a code driven flow (python or YAML) together with visualization interfaces (Klayout for GDS, trimesh for 3D rendering, networkx for graphs ...)

You just need to adapt the functions to your foundry and build your own library of elements (see UBC PDK example).

gdsfactory provides you with functions that you can use to:

• define components, circuits and masks in python or YAML
• route between components
• test settings, ports and GDS geometry

It enables both layout and netlist driven flows and is all code driven.

As input, you write python or YAML code.

As output it creates a GDSII file which is the most common filetype used by CMOS foundries. It also can output components settings (that you can use for measurement and data analysis) or netlists (for circuit simulations). And you can easily adapt any outputs to your needs, thanks to being all natively written in python.

For Photonics IC layout I used IPKISS for 7 years.

IPKISS is quite slow when working with large layouts, so in 2019 I stopped using it.

Then I tried all the commercial (Luceda, Cadence, Synopsys) and open source EDA tools (phidl, gdspy, picwriter, klayout-zero-pdk, nazca) looking for a fast and easy to use workflow.

The metrics for the benchmark were:

1. Fast
2. Easy to use and interface with other tools
3. Maintained / Documented / Popular

PHIDL won in speed, readability and easy of use. PHIDL is written on top of gdspy (which came second), so you can still leverage all the work from the gdspy community.

Gdsfactory also leverages klayout and gdspy python APIs.

What nice things come from phidl?

• functional programming that follow UNIX philosophy
• nice API to create and modify Components
• Easy definition of paths, cross-sections and extrude them into Components
• Easy definition of ports, to connect components. Ports in phidl have name, position, width and orientation (in degrees)
  • gdsfactory expands phidl ports with layer, port_type (optical, electrical, vertical_te, vertical_tm ...) and cross_section
  • gdsfactory adds renaming ports functions (clockwise, counter_clockwise ...)

What nice things come from klayout?

• GDS viewer. gdsfactory can send GDS files directly to klayout, you just need to have klayout open
• layer colormaps for showing in klayout, matplotlib, trimesh (using the same colors)
• fast boolean xor to avoid geometric regressions on Components geometry. Klayout booleans are faster than gdspy ones
• basic DRC checks

What functionality does gdsfactory provide you on top phidl/gdspy/klayout?

• @cell decorator for decorating functions that create components
  • autonames Components with a unique name that depends on the input parameters
  • avoids duplicated names and faster runtime implementing a cache. If you try to call the same component function with the same parameters, you get the component directly from the cache.
  • automatically adds cell parameters into a component.info (full, default, changed) as well as any other info metadata (polarization, wavelength, test_protocol, simulation_settings ...)
  • writes component metadata in YAML including port information (name, position, width, orientation, type, layer)
• routing functions where the routes are composed of configurable bends and straight sections (for circuit simulations you want to maintain the route bends and straight settings)
  • get_route: for single routes between component ports
  • get_route_from_steps: for single routes between ports where we define the steps or bends
  • get_bundle: for bundles of routes (river routing)
  • get_bundle_path_length_match: for routes that need to keep the same path length
  • get_route(auto_widen=True): for routes that expand to wider waveguides to reduce loss and phase errors
  • get_route(impossible route): for impossible routes it warns you and returns a FlexPath on an error layer to clearly show you the impossible route
• testing framework to avoid unwanted regressions
  • checks geometric GDS changes by making a boolean difference between GDS cells
  • checks metadata changes, including port location and component settings
• large library of photonics and electrical components that you can easily customize to your technology
• read components from GDS, numpy, YAML
• export components to GDS, YAML or 3D (trimesh, STL ...)
• export netlist in YAML format
• plugins to compute Sparameters using for example Lumerical, meep or tidy3d

How can you learn more?

gdsfactory is written in python and requires some basic knowledge of python. If you are new to python you can find many free online resources to learn:

• books
• youTube videos
• courses
  • scientific computing
  • numerical python
  • python

Installation

First, you need to install klayout to visualize the GDS files that you create.

gdsfactory works for python versions 3.7, 3.8 and 3.9 in Windows, MacOs and Linux. Github runs all the tests at least once a day for different versions of python (3.7, 3.8, 3.9)

If you are on Windows, I recommend you install gdspy with Anaconda3, Miniconda3 or mamba (faster conda alternative) and pip for gdsfactory. I also recommend you install the gdsfactory link to klayout gf tool install

mamba install gdspy -y
pip install "gdsfactory[full]"
gf tool install

Mamba is a faster alternative to conda, if you don't want to install mamba, you can also replace mamba install gdspy with conda install -c conda-forge gdspy -y

For Linux and MacOs you can also install gdsfactory without Anaconda3:

pip install "gdsfactory[full]"
gf tool install

Or you can install the development version if you plan to contribute to gdsfactory:

git clone https://github.com/gdsfactory/gdsfactory.git --shallow-exclude=gh-pages
cd gdsfactory
make install

To summarize: There are 2 methods to install gdsfactory

1. For users, pip install gdsfactory will download it from PyPi (python package index)
2. For developers, git clone it from GitHub to your computer and link the library to your python with make install

For updating:

1. Users need to pip install gdsfactory --upgrade to install the latest release available.
2. Developers need to git pull from GitHub to get the latest changes.

After installing it you should be able to import gdsfactory as gf from a python script.

• gdsfactory
  • components: define a basic library of generic components that you can customize
  • gdsdiff: hash geometry and show differences by displaying boolean operations in klayout
  • klayout: klayout generic tech layers and klive macro
  • klive: stream GDS directly to klayout
  • ports: to connect components
  • routing: add waveguides to connect components
  • samples: python tutorial
  • tests:
• docs/notebooks: jupyter-notebooks based tutorial

Documentation

• Run notebooks on
• read online docs
• download the code
• run gdsfactory/samples on your IDE (Spyder, PyCharm, VSCode) and docs/notebooks in jupyter-lab
• play with UBCpdk docs and code

Plugins

We try to keep gdsfactory core with minimum dependencies. So when you run pip install gdsfactory you do not install any plugins by default. If you want to install gdsfactory together with all the plugins you can run

pip install gdsfactory[full]

Here are some of the plugins that you can use in gdsfactory:

Trimesh

For (3D rendering and STL export)

pip install trimesh

Lumerical FDTD

For simulating Sparameters using FDTD.

meep / mpb

Open source FDTD / mode simulations. You to install meep and MPB with conda:

conda install -c conda-forge pymeep=*=mpi_mpich_* -y

or mamba (faster conda)

mamba install pymeep=*=mpi_mpich_* -y

Works only on Mac, Linux or windows WSL

SAX

Circuit simulations with optimization capabilities. You can install sax with pip install sax

Works only on Mac, Linux or windows WSL

tidy3d

For fast FDTD GPU based simulations on the cloud. Requires you to create an account on their website

CHANGELOG

gdsfactory keeps a changelog.

You can also keep a changelog for each individual component. By default each component has an empty changelog and starts with version '0.0.1'

• major:
  • position of ports changes. Affects position of ports. High level circuits may not work.
• minor
  • affects a physical layer. Footprint is the same. it fits, but may not work the same.
• patch: (decoration or formalities)
  • smaller changes
  • name change

You will need to manually bump the version and document any changes

@gf.cell
def my_component():
    c = gf.Component()

    c.version = "0.0.2"
    c.changelog += " # 0.0.2 increase default length to 11um "

Acks

gdsfactory top contributors:

• Joaquin Matres (Google): maintainer
• Damien Bonneau (PsiQ): cell decorator, Component routing functions, Klayout placer
• Pete Shadbolt (PsiQ): Klayout auto-placer, Klayout GDS interface (klive)
• Troy Tamas (Rockley): get_route_from_steps, netlist driven flow (from_yaml)
• Floris Laporte (Rockley): netlist extraction and circuit simulation interface with SAX
• Alec Hammond (Georgia Tech): Meep and MPB interface
• Simon Bilodeau (Princeton): Meep FDTD write Sparameters
• Thomas Dorch (Freedom Photonics): for Meep's material database access, MPB sidewall angles, and add_pin_path

Open source heroes:

• Matthias Köfferlein (Germany): for Klayout
• Lucas Heitzmann (University of Campinas, Brazil): for gdspy
• Adam McCaughan (NIST): for phidl
• Alex Tait (Queens University): for lytest
• Thomas Ferreira de Lima (NEC): for pip install klayout

Links

• gdsfactory github repo and docs
• ubc PDK: sample open source PDK from edx course.
• miniforge install instructions
• SAX: separate package for circuit simulations
• awesome photonics list
• phidl (gdsfactory is based on phidl)
• gdspy (phidl is based on gdspy)
• docs follow MyST syntax
• versions follow semantic versioning