clerq
clerq solves the propagation of classical electromagnetic fields through media of open quantum systems, using Maxwell's equations coupled to the Lindblad master equation. It is used for near-resonant light in thermal atomic vapours, with two-, three- and many-level atoms, spontaneous decay, dephasing and Doppler broadening.
Renamed from
maxwellbloch. This package was previously published asmaxwellbloch. Installclerqand changeimport maxwellblochtoimport clerq. The old name keeps working through a transitional release that re-exportsclerqwith aDeprecationWarning. Version 0.13.0 also fixes a factor-of-2 error in the propagation equation, so results from earlier versions change. See the announcement.
Above is an example solution for the propagation of a 4π pulse through a dense atomic vapour. The pulse immediately breaks up on entering the medium and the resultant pulses form two optical solitons each with a pulse area of 2π.
Documentation
Docs for the project are at clerq.org.
Install
The recommended way to install is via uv:
uv pip install clerq
Or using pip:
pip install clerq
If you prefer Conda, you can create and activate an environment with the required dependencies with
conda create --name mb -c conda-forge python=3.11 qutip
conda activate mb
pip install clerq
More detailed installation instructions can be found in the docs along with many example problems.
Attribution
If you use clerq for research, please cite the original package, which was published as MaxwellBloch:
@misc{ogden2020maxwellbloch,
author = {Ogden, Thomas P.},
title = {{MaxwellBloch}: a Python package for solving the coupled
Maxwell-Bloch equations describing the nonlinear propagation of
near-resonant light through thermal quantised systems such as atomic
vapors.},
year = {2020},
publisher = {GitHub},
journal = {GitHub repository},
howpublished = {\url{https://github.com/tpogden/clerq}}
}
A CITATION.cff for clerq is included (GitHub's "Cite this repository" button
reads it). A citation with its own DOI will be added once the first archived
release under the new name is available.
Changelog
See CHANGELOG.md.
License
MIT License. See LICENSE.txt.
Metadata
Release files for clerq 0.13.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| clerq-0.13.1.tar.gz | 65.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| clerq-0.13.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 118.4 kB
Release files / clerq-0.13.1.tar.gz
| Download URL | clerq-0.13.1.tar.gz |
|---|---|
| Size | 65.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7e67ccd0a3e3342cc7b96aa9604e4dd04ea616138667b58d055b3b303ba29661
|
|
BLAKE2b-256 checksum How to use checksums |
8521ef22ec74f219b4593eb4716a288ebab77d1dd3ce36c7283ada2ba2842423
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 9, 2026.
Transparency logRelease files / clerq-0.13.1-py3-none-any.whl
| Download URL | clerq-0.13.1-py3-none-any.whl |
|---|---|
| Size | 52.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3befea4c01a58f26cbe1a331dc5960e89772a0a952f24b316ff82f04f8860373
|
|
BLAKE2b-256 checksum How to use checksums |
8cb2b86d843f535c1c15c606f47f5089f71d7bd74c885f03a4e0ddf84329acb7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 9, 2026.
Transparency log