biosigIO
A Python package for biosignal import/export and manipulation across modalities (EEG, EMG, iEEG, MEG, and behavioral/marker streams). biosigIO provides a unified Recording interface for loading data from many acquisition systems and archives (EEGLAB, Delsys Trigno, OTB, EDF/BDF, WFDB, XDF, MEG/CTF/KIT/4D-BTi and BrainVision via MNE, MEF3 iEEG via MNE+pymef, and proprietary electrophysiology such as Intan/Blackrock via python-neo) and exporting it to standardized and serving formats (EDF/BDF, Parquet, Arrow, Zarr) with harmonized metadata.
The determination of the EDF/BDF format is based on the dynamic range of the data. If the data is within the range of 16-bit integers (~90dB), the EDF format is used. Otherwise, the BDF format is used. This is to ensure that the data is stored in the most efficient format possible. This determination is made automatically using SVD decomposition and/or FFT to determine the dynamic range of the data. (Alternatively, the user can override the format selection by explicitly indicating their desired format).
Documentation
The documentation including installation instructions, examples, and API reference is available at https://neuromechanist.github.io/biosigio/.
What changed in each release is in CHANGELOG.md.
Breaking in 1.2.10: biosigio 1.2.10 is a patch release that contains breaking changes:
Recording.select_channels raises ValueError for a name listed twice (and now accepts any iterable of names);
the Parquet/Arrow importer raises ValueError for a Feather/Arrow table that repeats a column name;
EDF/BDF export numbers labels that collide once truncated to 16 characters;
a Delsys Trigno file that repeats a Label: line keeps every column, each with its own line's rate and unit, and is refused if its header does not have one field per column;
XDF, neo and EEGLAB suffixes for repeated labels never take a label the file genuinely uses, so a label such as Ch1_1 can now point at a different signal;
a channels.tsv row matched to its channel case-insensitively now applies its type and unit, which can convert the signal;
and, for anyone upgrading from before 1.2.9, Recording.add_channel still raises for a label that already exists (below).
To adapt, de-duplicate select_channels arguments and re-check stores regenerated from files with repeated labels;
to defer, pin biosigio==1.2.9 (a ~=1.2.9 or <1.3 pin takes 1.2.10 automatically).
Details are in the changelog.
Breaking in 1.2.9: Recording.add_channel raises ValueError for a label that already exists instead of silently replacing that channel; use set_channel to change metadata or assign rec.signals[label] to replace samples.
Features
-
Import biosignal recordings from many systems and archives:
- EEGLAB set files (supported, classic and MATLAB v7.3; v7.3 needs the
hdf5extra) - Delsys Trigno (supported)
- OTB Systems (supported)
- EDF/BDF(+) (supported, including annotations)
- WFDB (supported, including annotations)
- XDF/Lab Streaming Layer (supported, multi-stream)
- MEG:
.fif, CTF.ds, KIT/Yokogawa.con/.sqd/.kdf, and 4D Neuroimaging/BTi (a directory, detected by content) via MNE (supported;megextra) - BrainVision
.vhdrvia MNE (supported;megextra) - MEF3 iEEG
.mefdvia MNE (supported;mef3extra -- mne>=1.12 plus pymef) - Proprietary electrophysiology via python-neo: Intan, Blackrock, Spike2, Plexon, Micromed, Neuralynx (supported;
neoextra) - Generic CSV (supported with auto-detection)
- Noraxon (planned)
- EEGLAB set files (supported, classic and MATLAB v7.3; v7.3 needs the
-
Smart import:
- Automatic file format detection based on extension
- Specialized format detection for CSV files
- Custom importers for system-specific formats
- Automatic annotation/event loading (WFDB, EDF+/BDF+, and EEGLAB .set) into the events table, embedded back on EDF+/BDF+ export and carried in the Parquet/Arrow/Zarr serialization formats
- LSL timestamp preservation for XDF files (for synchronization)
-
Export to standardized formats:
- EDF/BDF(+) with channels.tsv metadata (automatically selects format based on signal properties, preserves annotations)
-
Serialization & serving (see docs):
- Parquet and Arrow/Feather: lossless columnar round-trip (analytics, fast IPC); requires the
arrowextra - Zarr: cloud-native serving store (one store serves viewing, inference, and training), a derived downsampled copy; requires the
zarrextra
- Parquet and Arrow/Feather: lossless columnar round-trip (analytics, fast IPC); requires the
-
Data manipulation:
- Channel selection
- Metadata handling
- Event/Annotation handling (access, add)
- Basic signal visualization
- Raw data access and modification
Installation
biosigIO uses UV for Python environment and package management.
From PyPI (recommended)
uv pip install biosigio
(If your own project is uv-managed, use uv add biosigio to track it as a dependency.)
From source
git clone https://github.com/neuromechanist/biosigio.git
cd biosigio
uv pip install .
Usage
Basic Example
from biosigio import Recording
# Load data with automatic format detection
rec = Recording.from_file('data.csv') # Format detected from file extension
# Load data with explicit importer
rec = Recording.from_file('data.csv', importer='trigno')
# Plot specific channels
rec.plot_signals(['EMG1', 'EMG2'])
# Export to EDF or BDF (format automatically determined)
rec.to_edf('output.edf')
Generic CSV Import
# Import a generic CSV file
rec = Recording.from_file('data.csv', importer='csv',
sample_frequency=1000, # Required if no time column
has_header=True, # Whether file has header row
channel_names=['EMG_L', 'EMG_R', 'ACC_X'])
Channel Selection
# Select specific channels
subset_emg = rec.select_channels(['EMG1', 'EMG2', 'ACC1'])
# Select all channels of a specific type
emg_only = rec.select_channels(channel_type='EMG')
# Plot selected channels
subset_emg.plot_signals()
Metadata Handling
# Set metadata
rec.set_metadata('subject', 'S001')
rec.set_metadata('condition', 'resting')
# Get metadata
subject = rec.get_metadata('subject')
Development
Setup
- Clone the repository:
git clone https://github.com/neuromechanist/biosigio.git
cd biosigio
- Install for development (editable install with dev dependencies):
uv sync --extra dev
Running Tests
uv run pytest
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
This project is licensed under the BSD 3-Clause License - see the LICENSE file for details.
Acknowledgment
This project is partially supported by a Meta Reality Labs gift to @sccn and NIH 5R01NS047293.
Metadata
Release files for biosigio 1.2.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| biosigio-1.2.10.tar.gz | 344.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| biosigio-1.2.10-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 725.7 kB
Release files / biosigio-1.2.10.tar.gz
| Download URL | biosigio-1.2.10.tar.gz |
|---|---|
| Size | 344.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0105e674c953aa1d5bb64b6415a9b982303b274779e051598a627ceb19128b74
|
|
BLAKE2b-256 checksum How to use checksums |
0766b306b6195cc8de2440f70df89a59acc7b69fe551211f64df7f96d4079231
|
| 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 29, 2026.
Transparency logRelease files / biosigio-1.2.10-py3-none-any.whl
| Download URL | biosigio-1.2.10-py3-none-any.whl |
|---|---|
| Size | 381.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
14027f58921348552ecd6f7f0eddfc6c97c1578971f38f139a03c57779be53c6
|
|
BLAKE2b-256 checksum How to use checksums |
f1529ed867da9afae21df0fe7a21a988a5df7f4cb1b37cb1069858ec98fe731e
|
| 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 29, 2026.
Transparency log