BrightEyes-MCS-Reader
Reader-only utilities for BrightEyes MCS HDF5 files.
This package contains the current schema reader in
brighteyes_mcs_reader.readerfor the h5 scheme > 0.0.6- the legacy compatibility helpers in
brighteyes_mcs_reader.reader_legacyfor the pure raw output of BrightEyes-MCS (h5 scheme == 0.0.2).
Install
pip install brighteyes-mcs-reader
Usage
from brighteyes_mcs_reader import list_datasets, read_signal
for info in list_datasets("measurement.h5"):
print(info.path, info.kind, info.shape)
signal = read_signal("measurement.h5", time=0, depth=0, channel="sum")
print(signal.data.shape, signal.dims)
Legacy files can be loaded with:
from brighteyes_mcs_reader import reader_legacy
data, metadata = reader_legacy.load("legacy_measurement.h5")
Calibration, output building, conversion, alignment, and plotting helpers have
moved to BrightEyes-MCS-DataPrep.
1 maintainer
Metadata
1 maintainer
Release files for brighteyes-mcs-reader 0.1.0
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 | Actions |
|---|---|---|---|---|
| brighteyes_mcs_reader-0.1.0.tar.gz | 17.1 kB | With provenance | Details for brighteyes_mcs_reader-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| brighteyes_mcs_reader-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for brighteyes_mcs_reader-0.1.0-py3-none-any.whl |
Total release size: 32.1 kB
Release files / brighteyes_mcs_reader-0.1.0.tar.gz
| Download URL | brighteyes_mcs_reader-0.1.0.tar.gz |
|---|---|
| Size | 17.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
67e8615e68917b162a1aab31a747f91d908577ccf89c52d572480b2e809999ca
|
|
BLAKE2b-256 checksum How to use checksums |
6a37d909e8fba5045d290f377be9182afa42e0add6cb0462a2d2056af5112f4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 9, 2026.
Transparency logRelease files / brighteyes_mcs_reader-0.1.0-py3-none-any.whl
| Download URL | brighteyes_mcs_reader-0.1.0-py3-none-any.whl |
|---|---|
| Size | 15.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6d5b2a6035a82f5f128b3072e80a1ba5863a9865d814d0d96f0b813124eb3f92
|
|
BLAKE2b-256 checksum How to use checksums |
5cacbd33433116c074cb55cd78330d56caa55370e70def464d896bbac05cc6d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 9, 2026.
Transparency logSecurity for brighteyes-mcs-reader 0.1.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.
Attestation for brighteyes_mcs_reader-0.1.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 Jul 9, 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.
