Skip to main content

Python GUI for gds2palace

Intro

Install

pip install setupEM

Full documentation, installation guide, and usage walkthrough: https://github.com/VolkerMuehlhaus/setupEM

Recent changes

What's New - November 16, 2026 (setupEM 0.18.4)

File > Save (Ctrl+S) saves the settings file you opened. Opened from a .simcfg (e.g. the KLayout plug-in's export, with Open in setupEM), Ctrl+S did nothing: the action existed only for a script edited in place, and changes such as a port wall extension were lost without a question when setupEM was closed. Now:

  • Ctrl+S saves into the .simcfg / .tsimcfg the model was opened from (the menu names it). Its other entries, e.g. the plug-in's link to the model script, are kept. A script edited in place and a piece of a split region are saved as before; a new model asks for a file name.
  • Closing setupEM, opening another file or File > New asks "Save the changes to ...?" when the settings changed since the file was opened or saved.

What's New - November 15, 2026 (setupEM 0.18.3)

Needs gds2palace 0.10.7 or newer (pip install updates it).

combine_extend_snp.py 1.5 (combine_snp, in scripts/), the same file as in gds2palace 0.10.7:

  • The _dc Touchstone file keeps all simulated frequency points and adds only the 0 Hz point in front. Before, a result with the two low frequency points of a sweep from 0 Hz was resampled to a uniform frequency grid, so the simulated points, among them the two low ones, were replaced by interpolated values. The 0 Hz value itself is unchanged.
  • Port walls (from gds2palace 0.10.6): the line resistance of the standards is taken from the model's lowest frequency, so R and Q of models with port walls are right also below fstop/20.

Sweep from 0 Hz, the frequencies that replace DC (a gds2palace 0.10.7 change, nothing to set in setupEM): with start frequency 0, gds2palace simulates two low frequency points instead of 0 Hz. These were always 10 MHz and 20 MHz. With a mesh finer than 0.5 µm (refined cellsize or a per-layer override), gds2palace 0.10.7 moves them up, to 5 MHz·µm divided by the smallest cell size and twice that (e.g. 25 and 50 MHz at 0.2 µm), because on such a fine mesh Palace could stop with "SuperLUSolver: Found a singular matrix" at 10 MHz. Models with cell sizes of 0.5 µm and more keep 10 and 20 MHz. The user's guide section on DC handling says this now.

Citation: CITATION.cff and a "How to cite" section in the README; GitHub's Cite this repository button gives APA and BibTeX entries.

Internal: the model script writer of setupEM and setupThermal is now a module without Qt (script_writer.py, issue #52). The written scripts are unchanged; tests/test_script_writer.py checks 8 recorded scripts against both the GUI and the writer.

What's New - November 13, 2026 (setupEM 0.18.2)

Ports and thermal objects: Return in a text field of the form (source layer, Z0, voltage; in setupThermal layer, power, temperature) applies the settings to the selected row, like the Apply button. With no row selected, the status bar says so.

Command line fixes (from issue #52):

  • A script from File > Export runs without a display: gds2palace 0.10.4 and newer builds the model without the gmsh window on Linux with no display (ssh, container, batch job). Before, the script stopped with "Can't open display". The exported script also has the switch as a comment, # settings['no_gui'] = True, for unattended runs where a display exists.
  • combine_extend_snp.py (combine_snp, in scripts/) has --help and --version, and takes the folder to search as an optional argument. Before, any option was ignored and the conversion ran. Same file as in gds2palace 0.10.4.

Scripts used on two machines (e.g. Windows and Linux):

  • A model script edited in place whose GDS file was taken from its folder on opening (the script had the other machine's path, e.g. /mnt/pub/... for P:/...) now gets that path when it is saved or the model is created; the Code tab shows it. Before, the GUI showed the new path and the script kept the old one, and the model was made from the old one.
  • On Linux, a path with a drive letter from Windows (D:/...) in a script or settings file is no longer taken as relative to the script's folder (/mnt/.../D:/..., "Load a GDSII file and XML stackup first"). A stackup that is not found, also not next to the script, is taken from the stackups that ship with gds2palace if one has that name; the log says so.

Full history: CHANGES.md


Note: the setupEM PyPI package itself requires:

  • gds2palace>=0.10.7
  • gds_prepare_for_EM>=1.6.0
  • PySide6
  • shiboken6
  • scipy
  • requests
  • scikit-rf
  • matplotlib
  • numpy
  • gdspy
  • meshio
  • pyvista
  • pyvistaqt

(Other Python modules mentioned above are only needed to run standalone helper scripts in this repository, not to use the installed package.)

Metadata

Release files for setupEM 0.18.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for setupEM 0.18.4
File Size Uploaded Provenance Actions
setupem-0.18.4.tar.gz 484.0 kB Without provenance Details for setupem-0.18.4.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for setupEM 0.18.4
File Interpreter ABI Platform Actions
setupem-0.18.4-py3-none-any.whl Python 3 none any Details for setupem-0.18.4-py3-none-any.whl

Total release size: 931.3 kB

Release files / setupem-0.18.4.tar.gz

Download URL setupem-0.18.4.tar.gz
Size 484.0 kB
Tags Source
SHA-256 checksum
How to use checksums
bfc007676ec273acf06c7e2ac6ddeb2e478f1dd09f83223360a556f4cf2f2670
BLAKE2b-256 checksum
How to use checksums
24b6d94a416e49f6b7bacb16168baf76ac144321ed6a03e4e2fd61b8f5e542fe
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Release files / setupem-0.18.4-py3-none-any.whl

Download URL setupem-0.18.4-py3-none-any.whl
Size 447.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
324434415227442aa27de4eb4a4c937eeb14ef4582f6e74a98caeaad067a4cd3
BLAKE2b-256 checksum
How to use checksums
8d57670e1db58596191b71f80285d9291345171290c7e8920a9f811dea3151a0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Security for setupEM 0.18.4

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.18.4 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page