sovabids
sovabids is a python package for automating EEG to BIDS conversion (experimental MEG support).
New to sovabids? Start with the Quickstart guide.
- sovabids can be used through (click to see the examples):
Supported Formats
sovabids reads EEG files via MNE-Python’s read_raw, which supports a wide range of formats including BrainVision, EDF/BDF, EEGLAB, FIF, CNT, KIT/SQD, CTF, and more. See the full list in the MNE documentation.
Output is always written as a valid BIDS dataset. The table below lists formats that can also be exported natively (i.e., the BIDS data files stay in that format rather than being converted to BrainVision):
Format |
Extension |
Extra needed |
Notes |
|---|---|---|---|
BrainVision |
.vhdr |
(core) |
Default output format; pybv included in base install |
EDF |
.edf |
sovabids[formats] |
Requires edfio; date must be in 1985–2084 |
EEGLAB |
.set |
sovabids[formats] |
Requires eeglabio; montage with fiducials needed |
FIF |
.fif |
(core) |
MNE native format; use for MEG data (experimental — see warning above) |
Install export support for EDF and EEGLAB:
pip install "sovabids[formats]"
For all other readable formats, sovabids converts the data to BrainVision on output (the default mne-bids behaviour).
Architecture
- The main elements of sovabids are:
A source path with the original dataset.
A bids path that will be the output path of the conversion.
A rules file that configures how the conversion is done from the general perspective.
A mapping file that encodes how the conversion is performed to each individual file of the dataset.
Internally sovabids uses MNE-Python and MNE-BIDS to perform the conversion. In a sense is a wrapper that allows to do conversions from the command line.
Basic Usage
Terminal User Interface (sovatui)
sovabids ships an experimental terminal user interface (TUI) called sovatui. It lets you run a conversion without writing any command line code, guiding you through the full workflow in four tabs: Setup, Rules, Mappings, and Convert. It is optional (install it with the [tui] extra shown below); the CLI and Python API are the primary, fully supported interfaces.
Installation for TUI usage
This will install sovabids with the terminal user interface dependencies.
pip install "sovabids[tui]"
Running the TUI
sovatui
See the TUI tutorial video for a walkthrough and its example.
Command Line Interface (CLI) entry-points
Use sovabids through its CLI entry-points as follows:
Installation
pip install sovabids
sovapply
Use the sovapply entry-point to produce a mapping file from a source path, an output bids root path and a rules filepath.
sovapply source_path bids_path rules_path
By default the mapping file made will have the following filepath:
bids_path/code/sovabids/mappings.yml
sovaconvert
Use the sovaconvert entry-point to convert the dataset given its mapping file.
sovaconvert mapping_file
Using the experimental web GUI
Installation for WEB GUI usage
This will install sovabids for usage with an experimental web gui.
pip install "sovabids[gui]"
See the WEB GUI tutorial video for a walkthrough and its example.
Using the experimental bidscoin plugin
For the experimental bidscoin plugin, install the sovabids fork of bidscoin manually:
pip install "git+https://github.com/yjmantilla/bidscoin.git@sovabids"
Follow the example at https://sovabids.readthedocs.io/en/latest/auto_examples/bidscoin_example.html to see how to use the plugin.
Installation for developers
Fork this repo and run:
git clone https://github.com/<gh-username>/sovabids.git
cd sovabids
pip install -e ".[dev]"
Contributing
Contributions are welcome. See the Contributing guide for how to set up a development environment, run the tests, and open a pull request. The guide also lives at .github/CONTRIBUTING.md.
To report a bug, open an issue on the issue tracker. For usage questions and general help, use GitHub Discussions. The project follows a Code of Conduct.
Funding
Acknowledgments
sovabids is developed with the help of the following entities:
Academic Works
What does sova means?
sova is a contraction of ‘eso va’ which mean ‘that goes’ in spanish.
Nevertheless the real usage by the original developers is just to convey the idea of :
we will make it happen, we dont know how, but we will
Metadata
Release files for sovabids 0.4.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| sovabids-0.4.7.tar.gz | 3.2 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sovabids-0.4.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.3 MB
Release files / sovabids-0.4.7.tar.gz
| Download URL | sovabids-0.4.7.tar.gz |
|---|---|
| Size | 3.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0555a93b6b7d3f6040ff2fd282e2300b2cf54e154bf20066121fb9cd61071d5a
|
|
BLAKE2b-256 checksum How to use checksums |
5fd6a22b6c5672f91ffb8abc3f6b882dd859bd2c0e1b5d7acd425fc90fbe27a0
|
| 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 9, 2026.
Transparency logRelease files / sovabids-0.4.7-py3-none-any.whl
| Download URL | sovabids-0.4.7-py3-none-any.whl |
|---|---|
| Size | 55.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ee0022f1fd850c6fdbc01960589c190da865c67bd197dc12ff72ba1b75807c7b
|
|
BLAKE2b-256 checksum How to use checksums |
05d1e457dac90c6f05b500309b39cabd2e6ff793509d2d2d359622388ca329d5
|
| 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 9, 2026.
Transparency log