Inter-process communication for KLayout (lyipc)
KLayout is a layout editor and viewer. It is arguably the highest-performing and most advanced layout viewer in the 100€/$ – 104€/$ range. KLayout is free software. Among its editing functions is a generic scripting interface (GSI) that supports Python and Ruby, and there are other python scripting projects that specialize in various other ways (e.g. phidl, gdspy, nazca, MatlabGDSPhotonics, KiCad, etc.).
Approaches for integrated circuit layout fall into two main categories: GUI-driven, interactive design aided by software macros; and script-driven, non-interactive programming. The latter is more repeatable, modifiable, and reusable once the script (and its library modules) has been written. The problem lies in developing the code – the layout object state and its evolution through time is realtively opaque to the programmer.
The main application of lyipc is a graphical debugging workflow that uses the excellent KLayout viewer but is not necessarily dependent on the klayout scripting language or IDE. The idea is to create a communication link between two processes:
- A server that is launched from within the klayout.app GUI
- A client that can control various aspects of that klayout.app GUI
By separating the processes, the server GUI can be fully featured, initializing a large virtual program memory, while the client can be pretty lightweight.
Detail: a debug process flow looks like this
- [process #1] Launch klayout.app
- From menu item, start a simple server on port 11078
- [process #2: programmer] Run a python program in either klayout or python
- Stop this program in a debugger like PDB or Spyder (examine/change program variables)
- Write to a file "x.gds"
- [process #2: lyipc] The lyipc.client module will
- Initiate a socket connection on port 11078
- Send a command that means load
- [process #1] Upon receiving a connection request
- Received command is parsed
- An action is taken. In this case, load that file into the current view
- [process #2: lyipc] closes the socket and continues execution
- Animation: timed sequence of layouts
- Tracing: refresh display at every step of the program
- (future) Behavioral unit tests: Test whether code changes break previous layout behavior by keeping a reference.gds and creating a test.gds, then send them to klayout's visual diff tool.
From PyPI (Recommended)
As of version 0.1.5, installing the python package triggers a script to also install in klayout's system. All you need to do is
pip install lyipc
From github (Recommended for developers)
First, clone the project in a directory of your choice
git clone firstname.lastname@example.org:atait/klayout-ipc.git
Install the package with regular pip
pip install klayout-ipc/klayout_dot_config/python
For development mode, use pip's
As of version 0.1.5, this will also install it into klayout, so you're done.
From klayout salt package manager
In klayout.app, go to "Tools>Manage Packages". Go to "Install New Packages" and find "klayout_ipc". Double-click it, and press "Apply".
You still have to install the client module in your external-to-klayout system python The lyipc package is visible within klayout's interpreter namespace, but it is not on the system PYTHONPATH. In order for any python-based client to use it, lyipc must be installed with
pip install ~/.klayout/salt/klayout_ipc/python
or, on Windows
pip install %HOMEDRIVE%%HOMEPATH%/KLayout/salt/klayout_ipc/python
When an open file changes on disk, by default, KLayout asks whether to reload it. These prompts persist when reload is triggered by a communicating process instead of a human. Disable checks by going to klayout.app's preferences > Application > General, and uncheck the box for "Check for file updates."
-- press Ctrl+
or go to "Tools>Inter-process communication server"
Warning: clients have the ability to close and reload layout views that are unsaved, including ones in other tabs. It is highly recommended that you start a second instance of klayout.app dedicated to serving. This has to be done from command line. Tip for UNIX folks, put a shortcut to the klayout executable on your PATH
ln -s /Applications/klayout.app/Contents/MacOS/klayout /usr/local/bin/klayout
Note: as of now, the port is hard-coded (11078), so there can only be one server at a time. Communication is initiated by the client as a command or query. That means using multiple clients concurrently is possible, but they would clash unless synchronized somehow.
To load a layout file in the remote window, put these lines
import lyipc.client as ipc ipc.load('mylayout.gds')
in a file called
Run it with either a standard python interpreter
or the klayout general scripting interface (GSI) in non-GUI mode
klayout -b -r test-lyipc.py
The former is faster because a new klayout instance is not created, but of course, the latter must be used for
pya to work.
Usage examples for klayout and non-klayout layout clients are included in this repo in the "examples" folder.