pyEpilepsy
This repository provides code for epilepsy seizure forecasting. The documentation of the pyEpilepsy module is available at: documentation.
Installation
To install the package, the simplest way is to use pip to get the latest release:
$ pip install pyepilepsy
Work to be done
This repo only covers metrics for seizure forecasting for now. I plan to add some other features such as:
- common databases data parsing to mne format
chb-mit
…
- data labellisation
for binary classification (preictal vs interictal)
for regression (time before seizure)
…
Contribution
Any contribution is welcomed. If you want to collaborate on this repo, feel free to reach me by private message.
Metadata
Release files for pyEpilepsy 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyEpilepsy-0.1.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for pyEpilepsy-0.1.1-py2.py3-none-any.whl |
Release files / pyEpilepsy-0.1.1-py2.py3-none-any.whl
| Download URL | pyEpilepsy-0.1.1-py2.py3-none-any.whl |
|---|---|
| Size | 7.3 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
71c91095ac82061e53c673091523a45f54ea2fe457239f58e4aa12c4d3cb32a5
|
|
BLAKE2b-256 checksum How to use checksums |
13095b0e46b0e46100da840b92780807cd59448a3e83c78a2ac895fe086cf847
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.0
|
Security for pyEpilepsy 0.1.1
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.