MyoGestic
Real-time biosignal experiment GUI builder. A compact Python framework that turns a short script into a live experiment - signal viewers, recording, training, prediction - without classes, registries, or config files.
Built at the n-squared lab at Friedrich-Alexander-Universität Erlangen-Nürnberg (FAU) for the myocontrol research community. v2 is a ground-up rewrite of MyoGestic v1 focused on small, composable API surfaces and live extensibility.
Provides: live LSL ingest, on-disk recording (Zarr → .session.zip),
ML pipeline lifecycle (train/predict on their own threads), Dear ImGui
widgets, output filters, gRPC + LSL dual-plane integration with the
Virtual Hand Interface.
Does not provide: DSP, ML models, feature extraction. You bring scipy, MyoVerse, CatBoost, PyTorch - whatever fits.
Try it in your browser
A live MyoGestic app runs entirely in your browser via Pyodide at https://nsquaredlab.github.io/MyoGestic/playground/. Synthetic EMG, in-memory recording, sklearn LDA training, live prediction. No install.
Install
uv sync # core dependencies only
uv sync --extra examples # + catboost, myoverse, torch, scikit-learn (to run the demos)
uv sync --extra dev # + pytest, ruff, the examples extras above
Optional extras: [brainflow] [bdi] [serial] [grpc] [zarrs] [docs].
[grpc] pulls in grpcio + grpcio-tools + protobuf for the VHI control
plane.
Quick start
from myogestic import App, Stream
from myogestic.sources import LSLSource
from myogestic.widgets import recording_controls, signal_viewer
app = App("Hello EMG")
app.streams(Stream("emg", source=LSLSource("EMG"), window_ms=1000))
@app.ui
def ui(ctx):
signal_viewer(ctx, "emg")
recording_controls(ctx, ["Rest", "Fist"],
on_record=app.start_recording,
on_stop=app.stop_recording)
app.run()
That's the whole loop. Add a Pipeline, decorate extract / train /
predict, and you have a closed-loop experiment.
For a whole protocol rather than a loop to build on,
examples/start_here/
holds applications you can take to a session unmodified — they pick their
hardware from a dropdown, so the same file runs against any supported amplifier
or against the synthetic one when you have none:
force_ramps.py- isometric force ramps: track a trapezoid at a set %MVC, with the EMG, the force and the target all recorded togethermyocontrol.py- record cued Rest/Fist trials, train a classifier or a regressor, and drive the Virtual Hand from the predictionpong.py- chase a cursor with the paddle, train one signed[-1, +1]command, and play Pong with your wrist; the Virtual Hand only mirrors it
Six runnable end-to-end demos live in
examples/synthetic/:
emg_classification.py- the reference first read (CatBoost binary)emg_classification_grpc.py- adds the VHI gRPC control planeemg_regression.py- continuous 5-DoF regressionemg_regression_raulnet.py- same flow with a PyTorch Lightning CNNemg_32ch_multi_model.py- selectable classifier + Save/Loademg_popout_layout.py- the same flow in a dockable tear-off layout
Documentation
The full docs live as a ProperDocs site under
docs/ - tutorials, how-to guides, concept explanations, an
auto-generated API reference, and the in-browser playground.
Build and serve locally:
uv sync --extra docs --extra grpc --extra serial
uv run properdocs serve
Then open http://127.0.0.1:8000/MyoGestic/.
Quick links into the source:
- Getting Started - install + run the synthetic-EMG demo.
- Tutorials -
emg-classification,emg-regression-with-vhi. - How-to guides - recipes (custom source, custom widget, custom model, integrate the Virtual Hand, install VHI, the recipe feature set, ...).
- Concepts - architecture, streams, pipeline, threading, recording, the
Px/Frgrid, theEdgeTriggerpattern. - API reference - auto-generated from docstrings.
- API cheatsheet - the most-used public symbols on one page.
- Playground - the in-browser demo (no install).
The docs are deployed to GitHub Pages via .github/workflows/docs.yml on every push to main.
Development
uv sync --extra dev
uv run pytest -q
uv run ruff check .
Some integration tests need a live LSL outlet (port-bind sensitive in sandboxed CI). A handful of test files lag recent refactors and are scheduled for cleanup.
How to cite
If you use MyoGestic in your research, please cite our Science Advances paper:
@article{Simpetru2025,
author = {Raul C. S{\^i}mpetru and Dominik I. Braun and Arndt U. Simon
and Michael M{\"a}rz and Vlad Cnejevici
and Daniela Souza de Oliveira and Nico Weber and Jonas Walter
and J{\"o}rg Franke and Daniel H{\"o}glinger and Cosima Prahm
and Matthias Ponfick and Alessandro Del Vecchio},
title = {MyoGestic: EMG interfacing framework for decoding multiple
spared motor dimensions in individuals with neural lesions},
journal = {Science Advances},
volume = {11},
number = {15},
pages = {eads9150},
year = {2025},
doi = {10.1126/sciadv.ads9150},
url = {https://www.science.org/doi/abs/10.1126/sciadv.ads9150},
}
License
MyoGestic is licensed under the GNU General Public License v3.0 (GPL-3.0), matching the v1 release. Derivative work must remain open under the same license.
Metadata
Release files for myogestic 2.6.2
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 | |
|---|---|---|---|---|
| myogestic-2.6.2.tar.gz | 987.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| myogestic-2.6.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.7 MB
Release files / myogestic-2.6.2.tar.gz
| Download URL | myogestic-2.6.2.tar.gz |
|---|---|
| Size | 987.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
91b986611336faf4efdf43c694a7450310431717e1d3c2c49ae614a5c3ae2ed1
|
|
BLAKE2b-256 checksum How to use checksums |
30508024c5adf77266d28ae83145cf9b22bf6aa8b18c461421ef706b733e869b
|
| 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 / myogestic-2.6.2-py3-none-any.whl
| Download URL | myogestic-2.6.2-py3-none-any.whl |
|---|---|
| Size | 739.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
81ccef468e5259aae60989148b63a460b0c541c9bc8373678d4f3506eb7a8127
|
|
BLAKE2b-256 checksum How to use checksums |
f1e3e56b0421378a9e4098500d4681e29044fce257c2735dfe74c2ff68e8b775
|
| 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 logSecurity for myogestic 2.6.2
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 myogestic-2.6.2.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 Aug 10, 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.