muse is a library for reading, writing, and analyzing data from the Multi-slit Solar Explorer (MUSE) mission.
To learn more about MUSE, please visit the MUSE website.
Our documentation is hosted by ReadTheDocs (RTD).
Acknowledging or Citing muse
When writing a paper about MUSE, please include the following statement in the acknowledgements:
MUSE is led by the Lockheed Martin Solar and Astrophysics Laboratory of Palo Alto, California.
MUSE is managed by the Explorer's Program Office of NASA's Goddard Space Flight Center in Greenbelt, Maryland, for the Heliophysics Division of NASA's Science Mission Directorate.
Lockheed Martin Advanced Technology Center, along with partner institutions, builds the MUSE instrument and spacecraft and University of California, Berkeley provides the mission operations center.
MUSE benefits from international contributions supported by the Norwegian Space Agency (NOSA), the Italian Space Agency (ASI), the German Space Agency at DLR, and from the Max Planck Institute for Solar System Research (MPS).When writing a paper which uses the muse library, for now, please cite 
Usage of Generative AI
We expect authentic engagement in our community. Do not post the output from Large Language Models or similar generative AI as code, issues or comments on GitHub or any other platform. If you use generative AI tools as an aid in developing code or documentation changes, ensure that you fully understand the proposed changes and can explain why they are the correct approach and an improvement to the current state. For more information see our documentation on fair and appropriate AI usage.
Contributing
We love contributions! muse is open source, built on open source, and we’d love to have you hang out in our community.
If you would like to get involved, check out the Developers Guide section of the SunPy docs. The instructions are for SunPy but you just need to replace sunpy with muse. Help is always welcome so let us know what you like to work on, or check out the issues page for the list of known outstanding items.
1 maintainer
Metadata
1 maintainer
Release files for muse 0.2.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 | |
|---|---|---|---|
| muse-0.2.3.tar.gz | 213.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| muse-0.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 331.1 kB
Release files / muse-0.2.3.tar.gz
| Download URL | muse-0.2.3.tar.gz |
|---|---|
| Size | 213.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd3cc9012589b0dfcda4b5efc4d2c66edaed9f85ad1c964286f72a2a18a86848
|
|
BLAKE2b-256 checksum How to use checksums |
f6d1160505fccb4f8ce4e613bd96e16fb7495541a9e8671c5c45cc445ce3b101
|
| 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 Sep 9, 2026.
Transparency logRelease files / muse-0.2.3-py3-none-any.whl
| Download URL | muse-0.2.3-py3-none-any.whl |
|---|---|
| Size | 117.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
00f07224017470c2b482a763547f130c5ff85cd035a5c506a257977f18c823d5
|
|
BLAKE2b-256 checksum How to use checksums |
272fd0d91d6bdc9a3ea668e033bcabf0a2aaef5c0cc2eb30854e06f96b53708a
|
| 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 Sep 9, 2026.
Transparency log
