EEG IO
For an easy-to-use API interfacing with EEG data in EDF, or FIF format in the BIDS-EEG layout. This module stores the code for IO of EEG data for human patients, and pipelining code to convert clinical center data (i.e. time series eeg, clinical metadata) into a developer-friendly dataset that is also invertible and debug-friendly.
TODO
- Add support for adding structural context via neuroimaging processed data (e.g. FreeSurfer)
Installation Guide
EEGio is intended to be a lightweight wrapper for easily analyzing large batches of patients with EEG data. eegio relies on the following libraries to work:
numpy
scipy
scikit-learn
pandas
mne
mne-bids
pybids
seaborn
matplotlib
pyedflib (deprecated)
xlrd (deprecated)
Intended Users / Usage
Epilepsy researchers dealing with EEG data compliant with BIDS and MNE formats. Anyone with human patient EEG data.
See example and docs for info on how to format this.
- https://github.com/bids-standard/bids-specification/blob/master/src/04-modality-specific-files/04-intracranial-electroencephalography.md
- https://github.com/bids-standard/bids-starter-kit/wiki/The-BIDS-folder-hierarchy
Setting Up the BIDS Directory and Reading EEG Data From EDF/FiF
These are just lightweight wrappers of MNE/pyedflib reading to load in EDF/FiF data easily, so that raw EEG ts are readily accessible in Python friendly format. We provide an example that was built off of the examples in MNE-BIDS. See example.
For more info, see tutorials and documentation.
Contributing
We welcome contributions from anyone. Please view our contribution guidelines. Our issues page is a great place for suggestions! If you have an idea for an improvement not listed there, please make an issue first so you can discuss with the developers. For information on setting up testing, see testing guide.
License
This project is covered under the GNU GPL License.
Metadata
Release files for eegio 0.1.3
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 | Actions |
|---|---|---|---|---|
| eegio-0.1.3.tar.gz | 63.4 kB | Without provenance | Details for eegio-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| eegio-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for eegio-0.1.3-py3-none-any.whl |
Total release size: 132.1 kB
Release files / eegio-0.1.3.tar.gz
| Download URL | eegio-0.1.3.tar.gz |
|---|---|
| Size | 63.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1f392d11fd7f3a1276cce0bc4762d47aa16f731cae41962f543566fa3b008dff
|
|
BLAKE2b-256 checksum How to use checksums |
078515b798e7390793bea7144b76bd8ef545b7cfead95b4d9b65e1a56d2c2d06
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/42.0.2.post20191201 requests-toolbelt/0.9.1 tqdm/4.41.1 CPython/3.6.7
|
Release files / eegio-0.1.3-py3-none-any.whl
| Download URL | eegio-0.1.3-py3-none-any.whl |
|---|---|
| Size | 68.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a56eeb5a21d8fafc1d01e89ac2fd955bfb6486b11ce320e93418edaa86e824a6
|
|
BLAKE2b-256 checksum How to use checksums |
76575a1c0780744222b2287ae1731b45e120cc39bab84b02cad37829876cd9e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/42.0.2.post20191201 requests-toolbelt/0.9.1 tqdm/4.41.1 CPython/3.6.7
|
Security for eegio 0.1.3
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.