Skip to main content

"The test of a first-rate intelligence is the ability to hold two opposed ideas in the mind at the same time, and still retain the ability to function." ~ F. Scott Fitzgerald

Polarism

Polarism is a Python package for 2-D driven-dissipative Gross-Pitaevskii simulations of exciton-polariton systems. It provides configurable pumps, reservoirs, solvers, and result output for CPU and optional CUDA runs.

PyPI version Python versions Tests Documentation License: MIT Open in Colab DOI

Condensate density and phase under a ring-shaped pump, with vortices forming and moving inside the ring

A ring-shaped pump (the example plugin below) traps a rotating condensate with quantized vortices. Left: density |ψ|², right: phase. 256² grid; 180 frames spanning 300–1200 ps, rendered by examples/readme_media.py.

Highlights

  • Finite-difference RK4, split-step FFT, ETD-RK2, and interaction-picture solver families.
  • NumPy execution and optional CuPy GPU execution, including CUDA graph chunks for eligible CUDA solver runs.
  • Single, double, and quadratic-double reservoirs; continuous and pulsed pumps.
  • HDF5, NPY, and JSON output written on a background thread, so saving frames barely slows GPU runs; ps.load_results reads runs back lazily.
  • Checkpoint and restart, including a clean stop on SLURM time-limit signals.
  • Parameter sweeps with batched device execution, saved member results, and resume.
  • Live visualization and online GPU-rendered animation.
  • Registries for custom solvers, model components, output formats, and observables, documented in the plugin guide; a tyro-generated polarism CLI.
  • polarism-bench for measuring per-step and chunked GPU execution on your hardware.

Installation

pip install polarism

For CUDA runs, install the extra matching your CUDA environment:

Extra CUDA environment
pip install "polarism[cuda12]" CUDA 12.x; use this for V100/Volta
pip install "polarism[cuda13]" CUDA 13.x

The installed CuPy build must be compatible with the NVIDIA driver and CUDA toolkit. See the installation guide and GPU guide.

For a development checkout:

pip install -e ".[dev]"

Quickstart

This example matches examples/basic_run.py:

import polarism as ps
from polarism.compute_engine import compute_engine

cfg = ps.Config()

cfg.grid.nx = 128
cfg.grid.ny = 128
cfg.grid.lx = 100.0
cfg.grid.ly = 100.0
cfg.grid.grid_type = "periodic"

cfg.reservoir.reservoir_type = "single"
cfg.potential.potential_type = "zero"

cfg.laser.mode = "single"
cfg.laser.laser_type = "continuous-gaussian"
cfg.laser.P0 = 0.02
cfg.laser.sigma_space = 12.0

cfg.solver.method = "rk4-fdm"
cfg.solver.dt = 1e-3
cfg.solver.total_time = 2.0

cfg.result.save_results = True
cfg.result.save_hdf5 = True
cfg.result.output_directory = "quickstart_results"

cfg.compute_engine.use_gpu = False
compute_engine.configure(cfg.compute_engine)

ps.SimulationController(cfg).run()

Open a saved run with ps.load_results(run_dir). Its fields["density"], scalars["norm"], and static["pump"] use stable ASCII names; x and y contain the grid coordinates. HDF5 datasets are read lazily, so fields["density"][::10] loads every tenth frame only. Use the returned object as a context manager for HDF5 output.

You can save this configuration to YAML with cfg.to_yaml("run.yaml"), load it with ps.Config.from_yaml("run.yaml"), or run it from the CLI:

polarism --config run.yaml --grid.nx 256

CLI flags override values in the file. See the configuration guide.

For long cluster jobs, cfg.checkpoint.every_steps writes restartable checkpoints and cfg.checkpoint.resume_from continues from one; see Checkpoint and restart.

For GPU execution, set cfg.compute_engine.use_gpu = True, choose cfg.solver.method = "rk4-cuda", "split-step-fft-cuda", or "ifrk-fft-cuda", and consider cfg.solver.precision = "single" on consumer GPUs. FFT solvers require a periodic grid. Inspect CLI options with polarism --help.

To try Polarism on a GPU without installing CUDA, open the Colab notebook.

Adding your own pump

Pumps, reservoirs, potentials, solvers, grids, and absorption strategies are selected by name from registries. Subclass the base class, register it, and select the name in the config. This ring-shaped pump traps vortices inside the ring:

import polarism as ps
from polarism.laser import register_laser
from polarism.laser.abstract_laser import AbstractLaser


@register_laser("ring")
class RingLaser(AbstractLaser):
    """Continuous Gaussian ring of radius `ring_radius` and width `sigma_space`."""

    def __init__(self, laser_config, X, Y, precision="double"):
        super().__init__(laser_config, X, Y, precision)
        self.radius = laser_config.extra.get("ring_radius", 20.0)
        self.width = laser_config.sigma_space
        self._finalize_spatial_envelope(X, Y)

    def _amplitude(self, t):
        return self.P0

    def _P_space(self, X, Y):
        r = self.xp.sqrt((X - self.x0) ** 2 + (Y - self.y0) ** 2)
        return self.xp.exp(-0.5 * ((r - self.radius) / self.width) ** 2)

    def _P_time(self, t):
        return 1.0


cfg = ps.Config()
cfg.laser.laser_type = "ring"
cfg.laser.extra = {"ring_radius": 20.0}
cfg.laser.sigma_space = 4.0

The class works on both NumPy and CuPy through self.xp. Put it in polarism_plugins/ to have it discovered automatically, including by the polarism CLI. The plugin guide covers the contract for each component type.

Parameter sweeps

Sweep related configs together and read any saved member by index:

import polarism as ps

cfg = ps.Config()
cfg.result.save_results = True
cfg.result.save_hdf5 = True
with ps.Sweep(cfg, {"laser.P0": [0.02, 0.03], "physics.g_C": [0.001, 0.002]}).run() as results:
    density = results.member(0).fields["density"][:]

See the parameter sweeps guide for batching, output, and restart.

Choosing a solver

Method Grid Device Use
rk4-fdm, rk4-fdm-fused periodic or closed-interval CPU or CuPy FDM reference or lower-overhead FDM
rk4-cuda periodic or closed-interval CUDA Fused FDM runs
split-step-fft, etd-rk2, ip-rk4 periodic CPU or CuPy Spectral integration
split-step-fft-cuda periodic CUDA Second-order spectral runs
ifrk-fft-cuda periodic CPU or CUDA Spectral RK4/DP5/DOP853/Verner 7/9 with stage-coupled reservoirs
ifrk4-fft-cuda periodic CPU or CUDA Historical alias for spectral RK4

Check timestep and grid convergence for your model. See the solver reference for compatibility details.

Documentation

For pulsed pumps, power_definition: pulse_energy makes power or P the integrated dose of one pulse over space and time. The legacy peak_amplitude mode remains available for reproducing older runs. See Potentials and Pumps.

Contributing

See the contributing guide. Run the default regression suite with .venv/bin/pytest -q from a development checkout.

Citation

Cite Polarism with its Zenodo DOI, 10.5281/zenodo.23531116, which always resolves to the latest release; each release also has its own version DOI on Zenodo. The same metadata is in CITATION.cff and GitHub's “Cite this repository” menu.

License

Polarism is licensed under the MIT License.

Acknowledgements

This project is developed with the Exciton-Polariton research group at the Faculty of Physics, University of Warsaw, with support from NCN OPUS grant work and ICM computing infrastructure.

Metadata

Release files for polarism 0.6.0

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

Source distribution (sdist)

Source distribution for polarism 0.6.0
File Size Uploaded Provenance
polarism-0.6.0.tar.gz 136.5 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for polarism 0.6.0
File Interpreter ABI Platform
polarism-0.6.0-py3-none-any.whl Python 3 none any Details

Total release size: 310.6 kB

Release files / polarism-0.6.0.tar.gz

Download URL polarism-0.6.0.tar.gz
Size 136.5 kB
Tags Source
SHA-256 checksum
How to use checksums
98a3c7b3a92763eaf768bca6f1be14bb8b8dfe6fca764e01e0c656c11fdddab2
BLAKE2b-256 checksum
How to use checksums
e5eb621d19d21de4f195887f94b5cc3062f23eec63e06f60ca16604dc26ad6f4
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 22, 2026.

Transparency log

Release files / polarism-0.6.0-py3-none-any.whl

Download URL polarism-0.6.0-py3-none-any.whl
Size 174.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
56503c69c3b3cd9c7fca92ebfa79037181ac6fe0d910350b03e01e41c1863c88
BLAKE2b-256 checksum
How to use checksums
33723a8ae00d8e2ecfc30065ff30982c441bcebd7166d338c952877d061e3bf2
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 22, 2026.

Transparency log

Security for polarism 0.6.0

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 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for polarism-0.6.0.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 22, 2026.

Transparency log

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.

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