mt-io
Version: 0.0.5
This package is meant to be a repository for readers for various magnetotelluric data file types from various data loggers including:
| Data Logger | File Type | Reader | Maturity |
|---|---|---|---|
| LEMI 424 | txt | Y | medium |
| LEMI 423 | B423 | Y | medium |
| LEMI 417 | ? | In progress | weak |
| Metronix | atss | Y | medium |
| Metronix | ats | In progress | weak |
| MiniSEED | mseed | Y | strong |
| NIMS | bin | Y | strong |
| Phoenix MTU-5C | td_*, JSON, bin | Y | medium |
| Phoenix MTU-5A | tbl* | Y | medium |
| UoA PR6-24 | BX, BY, BZ, EX, EY | Y | medium |
| UoA Orange | binary | Y | medium |
| USGS ASCII | ascii | Y | medium |
| ZEN | z3d | Y | strong |
This package will read the data into either a mt_timeseries.ChannelTS or a mt_timeseries.RunTS object depending on the data included in the file.
Newer Readers
Recent additions include newer LEMI and University of Adelaide readers:
mt_io.lemi.read_lemi423for LEMI-423B423filesmt_io.lemi.read_lemi424for LEMI-424 ASCII text filesmt_io.uoa.read_uoafor PR6-24 Earth Data Logger channel filesmt_io.uoa.read_orangefor legacy Orange Box binary files
These readers return mt_timeseries.RunTS objects and are covered by the current test suite.
Installation
From Source
git clone https://github.com/kujaku11/mt-io.git
cd mt-io
pip install .
For development installation with editable mode:
pip install -e .
Note: This package is currently in development. PyPI and conda-forge releases will be available in future versions.
Issues
If you encounter any problems or have suggestions for improvements, please report issues on the GitHub Issues page.
When reporting an issue, please include:
- A clear description of the problem
- Steps to reproduce the issue
- Expected vs. actual behavior
- Your Python version and operating system
- Relevant code snippets or error messages
Contributing
Contributions are welcome! To contribute:
- Fork the repository on GitHub
- Create a new branch for your feature or bug fix (
git checkout -b feature/your-feature-name) - Make your changes and commit them with clear, descriptive messages
- Add tests for any new functionality
- Ensure all tests pass
- Push your branch to your fork (
git push origin feature/your-feature-name) - Submit a pull request to the main repository
Please ensure your code follows the project's coding standards and includes appropriate documentation.
For major changes, please open an issue first to discuss what you would like to change.
Test Data
If you have a small data set contribute to the repository here.
Metadata
Release files for mt-io 0.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mt_io-0.0.5.tar.gz | 14.7 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mt_io-0.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.0 MB
Release files / mt_io-0.0.5.tar.gz
| Download URL | mt_io-0.0.5.tar.gz |
|---|---|
| Size | 14.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ad8587a497bc76c8af5a847d42cbc2c7c4faac170ff49e3ba43858fdbb86737d
|
|
BLAKE2b-256 checksum How to use checksums |
4c7aff5d2fa1f784edc08f7411b09e9bf601a85be849f0ca398b4b75ab3286e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 11, 2026.
Transparency logRelease files / mt_io-0.0.5-py3-none-any.whl
| Download URL | mt_io-0.0.5-py3-none-any.whl |
|---|---|
| Size | 219.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
acea138500f06cd8abf366ab0dc477d09ceb3c0dd2f9ac678a0b4a488ae2be65
|
|
BLAKE2b-256 checksum How to use checksums |
b703dea4ebd4d98af4cff360384d3c5b6d53e623a4fe9daf9b20f0f9c1390c34
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 11, 2026.
Transparency log