This release is a pre-release and may not be stable for production use.
Introduction
EMerge is a python based FEM EM library for the time harmonic helmholtz formulation. It is thus best suited for Electromagnetic wave phenomenon. You can use it to simulate:
- RF Filters
- Signal propagation through PCBs
- Antennas
- Optycal systems
- Arrays and periodic structures
- Much more!
It is designed to be as easy to use and compatible as possible. It runs on all operating systems and on all hardware.
EMerge is designed to have your entire simulation start and finish in the same Python script (or more if you want). You require no awkward configuration files, JSON's, external software to do modelling etc. It allows you to do everything in Python:
- Geometry Creation/description |
- Material assignment |
- Meshing + mesh settings and adaptive mesh refinement |
- Boundary condition setup |
- Solving |
- Post processing and visualization |
If you have questions, suggestions, bug reports or just want to hang out, feel free to join the discord!
How to install
You can now install the basic version of emerge from PyPi!
pip install emerge
Direct solvers
EMerge solves all systems with direct solvers only. Some are faster than others. Depending on the operating system and hardware you have, some might work better and/or are easier to install than others.
MacOS (ARM)
EMerge uses the Apple Accelerate sparse solver for all cases. From 3.0.0b5 onwards it is installed automatically
with EMerge on macOS (the precompiled emerge-aasds package on PyPI), so no extra installation is needed.
By default the Accelrate solver will be limited to a single thread for frequency distributed sweeps. To allow for more threads either set the environment variable manually:
VECLIB_MAXIMUM_THREADS = 4
Or in Python before loading EMerge:
import os
os.environ['VECLIB_MAXIMUM_THREADS'] = '4'
Of from 2.5.3 onwards also through the config sister module
from emerge_config import config
config.set_acc_threads(4)
MacOS (ARM, GPU)
To utilize the GPU on Apple silicon you can install the open source GPU based sparse direct solver SPARTA.
pip install git+https://github.com/FennisRobert/SPARTA
To activate the GPU, set:
model.set_solver(em.EMSolver.SPARTA)
Windows (x86)
Windows has easy access to the lightning fast PARDISO solver out of the box, no installation needed. If you want to install the UMFPACK solver for distributed sweeps this distribution should work through conda forge:
conda install conda-forge::scikit-umfpack
Otherwise try the solution in the user manual.
GPU based CuDSS solver
If you have a new NVidia card you can try the first test implementation of the cuDSS solver. The dependencies can be installed through:
pip install emerge[cudss]
GPU based SPARTA solver
You can utilize the GPU on AMD devices through Vulkan using the open source SPARTA solver.
pip install git+https://github.com/FennisRobert/SPARTA
To activate the GPU, set:
model.set_solver(em.EMSolver.SPARTA)
Install GMSH Version 5.0.0 MacOS
pip install https://gmsh.info/python-packages-dev/gmsh/gmsh-5.0.0.dev1-py2.py3-none-macosx_12_0_arm64.whl --force-reinstall
Dependencies
EMerge ships compiled Rust kernels (the
emrmodule, source inemr/). PyPI wheels include them; installing from source (pip install /path/to/EMergeorpip install git+https://github.com/FennisRobert/EMerge.git) compiles them automatically and requires a Rust toolchain (https://rustup.rs).
| To run this FEM library you need the following libraries | Optional: |
|---|---|
|
|
PCB and CAD readers
You can read Gerber and ODB++ files using the optional emcad dependency which I also maintain. To get all the dependencies its easiest to do:
pip intall emerge[cad]
Resources / Manual
You can find the latest versions of the manual on: https://www.emerge-software.com/resources/
1 maintainer
Metadata
1 maintainer
Release files for emerge 3.0.0b5
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 | |
|---|---|---|---|---|
| emerge-3.0.0b5.tar.gz | 858.5 kB | With provenance | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| emerge-3.0.0b5-cp310-abi3-win_amd64.whl | CPython 3.10 | abi3 | Windows x86-64 | Details |
| emerge-3.0.0b5-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.10 | abi3 | Linux glibc 2.17+ x86-64 | Details |
| emerge-3.0.0b5-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | CPython 3.10 | abi3 | Linux glibc 2.17+ ARM64 | Details |
| emerge-3.0.0b5-cp310-abi3-macosx_11_0_arm64.whl | CPython 3.10 | abi3 | macOS 11.0+ ARM64 | Details |
| emerge-3.0.0b5-cp310-abi3-macosx_10_12_x86_64.whl | CPython 3.10 | abi3 | macOS 10.12+ x86-64 | Details |
Total release size: 9.7 MB
Release files / emerge-3.0.0b5.tar.gz
| Download URL | emerge-3.0.0b5.tar.gz |
|---|---|
| Size | 858.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
02996e7e15d54e83c2ba9577fe952999190c663696449ebfd0f255502c8cb6f8
|
|
BLAKE2b-256 checksum How to use checksums |
62b7c9d652478e843f81492de0eb92fe3cfb937f713194fe86cd4040a8238a8a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logRelease files / emerge-3.0.0b5-cp310-abi3-win_amd64.whl
| Download URL | emerge-3.0.0b5-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
48a2a738aabce23a57ce8440ea81653f2e1c4acce991ef9df53677a5796156a4
|
|
BLAKE2b-256 checksum How to use checksums |
d289d057c030d0dbc014189b91d89032191b7ae0f1ad08008c71c2fcc80f51ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logRelease files / emerge-3.0.0b5-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | emerge-3.0.0b5-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
017a2bca384ab19f509a59be43120c96542beb4648659d9bdcfd752bbaf33095
|
|
BLAKE2b-256 checksum How to use checksums |
438306857cce19171c7d16b04cda52d45dd59f5cef4022cb0cf685897dd4cc40
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logRelease files / emerge-3.0.0b5-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | emerge-3.0.0b5-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
0c302b8019d9c8728b8f07ec428abba0a5ffaf82ebf2c5137a0b5552037114d8
|
|
BLAKE2b-256 checksum How to use checksums |
011f5eb3b7f5e5cce627f50b28cc5cad19633b1c709103d45e24e51fceb38f85
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logRelease files / emerge-3.0.0b5-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | emerge-3.0.0b5-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
f32a6d1be766b94453494033b16f73c3b3b94df1f8b2d0d96b69eedfaa31d3df
|
|
BLAKE2b-256 checksum How to use checksums |
ea68c509c02fe7deb34d2227618f5f825a4124b66d36f07ef1f4c163c38ad76a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logRelease files / emerge-3.0.0b5-cp310-abi3-macosx_10_12_x86_64.whl
| Download URL | emerge-3.0.0b5-cp310-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.10 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
8a96c4aecd0c49af54193ca4af09c404620856cc612d2a4d2a281ed451355db3
|
|
BLAKE2b-256 checksum How to use checksums |
75cfe559a957c5c3435fed71643d6c51bae0dbea342f65cc362163eeeb9dbf95
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logSecurity for emerge 3.0.0b5
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.
Full provenance
All 6 files in this release have been uploaded with provenance metadata.
Attestation for emerge-3.0.0b5.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logA 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.
