Python GUI for gds2palace
Install
pip install setupEM
Full documentation, installation guide, and usage walkthrough: https://github.com/VolkerMuehlhaus/setupEM
Recent changes
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
_dcTouchstone 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, inscripts/) has--helpand--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/...forP:/...) 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.
What's New - November 11, 2026 (setupEM 0.18.1)
Command line fixes (from issue #52, use without a display):
--help,--versionand a wrong argument ofsetupEM,setupThermal,stackupEditor,resultViewerandfieldViewerno longer need a display: the arguments are read before Qt starts. All five have--versionnow.setupEM -simcfg <file>opens a settings file of an Elmer model in Elmer mode. It opened in Palace mode unless--elmerwas given, also when started from the KLayout plug-in.- A
-simcfg,-gdsfileor-xmlfilethat does not exist, or a settings file of the other application, endssetupEM/setupThermalwith a message on stderr and exit code 2 instead of an empty window. In the GUI, a settings file that is gone is reported as "File not found", not as "Unknown data format". - Loading a settings file no longer shows a "Loaded" box: the log says "Config loaded from ...", with a GDS or stackup file that was not found at its saved path and was taken from the settings file's folder instead.
- Opening a
.simcfgcontinues with the model script only when the file is linked to it, and asks only when the two have other settings (the question lists them). Create Model links: besides<model>.simcfgit writes the script's name ("model_script") into the.simcfgthe model was opened from, e.g. the KLayout plug-in's export, which keeps it on the next export. A script that only reads the same GDSII file is no longer taken for the model; the log names it. New options--continue-with-scriptand--start-from-configanswer the question on the command line. fieldViewer --screenshotneeds no display and noQT_QPA_PLATFORM=offscreen.python -m setupEM.join_piecesandpython -m setupEM.thermal_resultshave--helpand--version, write their errors to stderr, and a missing file is a message, not a traceback.- The modules without a GUI (
join_pieces,thermal_results,script_model, ...) can be imported without loading Qt. - User guide: Model Fit starts snp2le with the result file loaded (the text said it has to be loaded by hand).
**Split regions, fix:**a side of the region made a port wall in setupEM after the export (e.g. with via ports of the layout on the region's edge) was a plain PEC wall in every piece and in the full check model: the wall shorted those ports, and the joined result and the full model were both wrong, in the same way. The pieces' port walls on the region's edge are now found from the ports on the edge of each piece's layout; the full model has all of the region's port walls. Where the region has a port wall but a piece none of its ports, that stretch stays PEC and now moves outward with the region's port wall extension (a length; written as settings['wall_extension'], needs gds2palace 0.10.1), so that all pieces and the full model have the same box.
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.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| setupem-0.18.3.tar.gz | 483.3 kB | Without provenance | Details for setupem-0.18.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| setupem-0.18.3-py3-none-any.whl | Python 3 | none | any | Details for setupem-0.18.3-py3-none-any.whl |
Total release size: 930.1 kB
Release files / setupem-0.18.3.tar.gz
| Download URL | setupem-0.18.3.tar.gz |
|---|---|
| Size | 483.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
556a66a302abf2ab5998ddd8bc7ebaf0ce304793b901b5af59333fd7d09b1393
|
|
BLAKE2b-256 checksum How to use checksums |
2d1d87c8702d28a10b2f64faec9b3386e69a66458a15558f890ef65cfa1835f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.14
|
Release files / setupem-0.18.3-py3-none-any.whl
| Download URL | setupem-0.18.3-py3-none-any.whl |
|---|---|
| Size | 446.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d9c5f01c976b74c5e855ba38f1992acca9f7a99dea1442fc7ef7233d177b5454
|
|
BLAKE2b-256 checksum How to use checksums |
beb3f2134be1b048cfb7d5df04458cc450c2461ed573a3ef168062d11ce464bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.14
|
Security for setupEM 0.18.3
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.