MRseq - MR pulse sequences using Pulseq
MRseq is a collection of several useful functions, kernels and scripts for creating vendor-agnostic MR pulse sequences using the open-source Pulseq format.
- Source code: https://github.com/PTB-MR/mrseq
- Bug reports: https://github.com/PTB-MR/mrseq/issues
- Documentation: https://ptb-mr.github.io/mrseq/intro.html
Contributing
We are looking forward to your contributions via Pull-Requests.
Installation for developers
Prerequisites for Windows
Before installing MRseq with development dependencies on Windows, you need:
-
Visual Studio Build Tools: The MRzeroCore dependency requires Rust compilation with Microsoft Visual C++ linker
- Download "Build Tools for Visual Studio 2022" from https://visualstudio.microsoft.com/downloads/
- During installation, select the "C++ build tools" workload
- Ensure "Windows 10/11 SDK" is included
- This is required for compiling native Rust extensions
-
Rust toolchain (automatically installed by MRzeroCore if not present)
Installation steps
- Clone the
MRseqrepository - Create/select a python environment
- Install
MRseqin editable mode including test dependencies:pip install -e ".[dev]" - Setup pre-commit hook:
pre-commit install
Licensing and Dependencies
The core source code of MRseq is licensed under the Apache-2.0 license.
For quality control and demonstration purposes, the notebooks in the examples/ directories utilize MRZero which is AGPL-licensed. The notebooks in the examples/ folder should be treated as AGPLv3.
Important for Commercial Users:
The AGPL dependency is listed only as an optional dev dependency. Installing this package via pip install mrseq does not install the AGPL library. Your usage of the core library remains subject to the permissive Apache-2.0 terms, unaffected by the licensing of the test suite or examples.
Contact
For questions or support, please contact us:
Christoph Kolbitsch
Physikalisch-Technische Bundesanstalt (PTB)
Abbestraße 2-12
10587 Berlin, Germany
christoph.kolbitsch@ptb.de
Patrick Schünke
NVision Quantum Technologies GmbH
Wolfgang-Paul-Straße 2
89081 Ulm, Germany
patrick.schuenke@nvision-quantum.com
Acknowledgments
We would like to thank NVision Quantum Technologies GmbH for their contributions to this project.
Metadata
Release files for mrseq 0.260810
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mrseq-0.260810.tar.gz | 56.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mrseq-0.260810-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 149.6 kB
Release files / mrseq-0.260810.tar.gz
| Download URL | mrseq-0.260810.tar.gz |
|---|---|
| Size | 56.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e91b0c09d04a70efcf8431585db25bd077d73b4684bab9f2b82ea598d92e879a
|
|
BLAKE2b-256 checksum How to use checksums |
17f759d87740835e01d4a72ed7b00bd134c57a9679d403fb821c0b8500b56215
|
| 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 Aug 10, 2026.
Transparency logRelease files / mrseq-0.260810-py3-none-any.whl
| Download URL | mrseq-0.260810-py3-none-any.whl |
|---|---|
| Size | 92.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
93729814519738bb53bc5f57f404fbec98a6085309343076fffc27d25f02f55b
|
|
BLAKE2b-256 checksum How to use checksums |
0529592bed91242d5ab131e21c161508c09baaa25fd791f2235f3c6133704636
|
| 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 Aug 10, 2026.
Transparency log