MyoVerse - The AI toolkit for myocontrol research
What is MyoVerse?
MyoVerse is your cutting-edge research companion for unlocking the secrets hidden within biomechanical data! It's specifically designed for exploring the complex interplay between electromyography (EMG) signals, kinematics (movement), and kinetics (forces).
Leveraging the power of PyTorch and PyTorch Lightning, MyoVerse provides a comprehensive suite of tools, including:
- Data loaders and preprocessing filters tailored for biomechanical signals.
- Peer-reviewed AI models and components for analysis and prediction tasks.
- Essential utilities to streamline the research workflow.
Whether you're predicting movement from muscle activity, analyzing forces during motion, or developing novel AI approaches for biomechanical challenges, MyoVerse aims to accelerate your research journey.
Installation
MyoVerse automatically installs with the correct PyTorch version for your platform.
Basic installation:
# Install from PyPI
pip install myoverse
This will automatically:
- On Linux: Install PyTorch and TorchVision from PyPI (with CUDA support)
- On Windows: Install PyTorch and TorchVision with CUDA 12.4 support
Development
For development, install the dev dependencies:
- Clone the Repository:
git clone https://github.com/NsquaredLab/MyoVerse.git # Replace with your actual repo URL if different cd MyoVerse
- Install uv: If you don't have it yet, install
uv. Follow the instructions on the uv GitHub page. - Set up Virtual Environment & Install Dependencies: Simply run:
uv sync --group dev
What is what?
This project uses the following structure:
myoverse: This is the main package. It contains:datasets: Contains data loaders, dataset creators, and a wide array of filters to preprocess your biomechanical data (e.g., EMG, kinematics).models: Contains all AI models and their components, ready for training and evaluation.utils: Various utilities to support data handling, model training, and analysis.
docs: Contains the source files for the documentation.examples: Contains practical examples demonstrating how to use the package, including tutorials (01_tutorials) and specific use cases like applying filters (02_filters).tests: Contains tests to ensure package integrity and correctness.
Metadata
Release files for MyoVerse 2.0.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 | |
|---|---|---|---|
| myoverse-2.0.0.tar.gz | 71.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| myoverse-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 161.2 kB
Release files / myoverse-2.0.0.tar.gz
| Download URL | myoverse-2.0.0.tar.gz |
|---|---|
| Size | 71.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
84c07cedb42dc0ebf93932660a6551ca8112f5f29b5ce134ea363bb5f3f1ae23
|
|
BLAKE2b-256 checksum How to use checksums |
2b560ced315e9411c8d990bfe1719c4dd180492183c663a98324e0ad4a5620e3
|
| 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 Jan 22, 2026.
Transparency logRelease files / myoverse-2.0.0-py3-none-any.whl
| Download URL | myoverse-2.0.0-py3-none-any.whl |
|---|---|
| Size | 89.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
769849db136baac2217f9e75c4369df906b6ce44d406ab6df580495717bb1cff
|
|
BLAKE2b-256 checksum How to use checksums |
1b8b81fe5d1551689379ae74f99642f8451c408bf933b6de8b79ae7143a68b91
|
| 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 Jan 22, 2026.
Transparency log