BluePyEfe: Blue Brain Python E-feature extraction
Latest Release |
|
Documentation |
|
License |
|
Build Status |
|
Coverage |
|
Citation |
|
Gitter |
Introduction
BluePyEfe aims at easing the process of reading experimental recordings and extracting batches of electrical features from these recordings. To do so, it combines trace reading functions and features extraction functions from the eFel library.
BluePyEfe outputs protocols and features files in the format used by BluePyOpt for neuron electrical model building.
How to cite
If you use this repository in your work, please refer to the “Cite this repository” button at the top of the repository page to get various citation formats, including APA and BibTeX.
For detailed citation information, please refer to the CITATION.cff file.
Requirements
eFEL eFeature Extraction Library (automatically installed by pip)
Numpy (automatically installed by pip)
Scipy (automatically installed by pip)
Neo (automatically installed by pip)
The instruction below are written assuming you have access to a command shell on Linux / UNIX / MacOSX / Cygwin
Installation
To install BluePyEfe, run:
pip install bluepyefeQuick Start and Operating Principle
For a hands-on introduction to BluePyEfe, have a look at the notebook examples/example_of_extraction.ipynb. For an NWB-focused example, see examples/nwb_extraction.ipynb.
The goal of the present package is to extract meaningful electrophysiological features (e-features) from voltage time series. The e-features considered in the present package are the one implemented in the eFEL python library. See this pdf for a list of available e-features.
The present package makes one major assumption: E-features are more meaningful if they are coming from a set of traces rather than a single trace. And they are even more meaningful if these traces come from different cells of the same cellular type. This assumption dictates the organisation of the package and has several consequences:
The efeatures extracted through the package will always be averaged over the trace considered. For example, the AP_amplitude will be an average over all the action potentials present in a trace. If you wish to work on an AP by AP basis, please consider using the eFEL library directly.
A large part of the present software is therefore dedicated to averaging the features across set of “equivalent” recordings. To be able to average e-features across different cells in a meaningful way, an equivalence must be established between the traces coming from these different cells. It would not make sense to average the mean firing frequency obtain cell A on a 1s long step protocol with the one obtain for cell B on a ramp protocol that lasts for 500ms. We chose to define recordings as equivalent based on two criteria: (1) They have the same name and (2) they are of the same amplitude when the amplitude is expressed as a percentage of the rheobase of the cell.
A pseudo-code for the main function of the package (bluepyefe.extract.extract_efeatures) could look as follows:
Load the data to memory by reading all the files containing the traces
Extract the required e-features for all the traces
Compute the rheobases of the cells based on one or several protocols
Use these rheobases to associate to each protocol an amplitude expressed in % of the rheobase
Compute the mean and standard deviations for the e-features across traces having the same amplitude
Save the results and plot the traces and e-features
Each of these steps are parametrized by a number of settings, therefore we recommend that you read carefully the docstring of the function.
Coming from the legacy version
The legacy version (v0.4*) is moved to the legacy branch. Changes introduced in v2.0.0 are listed in the CHANGELOG.rst. That is the only file you need to look at for the changes as the future changes will also be noted there.
Funding
This work has been partially funded by the European Union Seventh Framework Program (FP7/20072013) under grant agreement no. 604102 (HBP), and by the European Union’s Horizon 2020 Framework Programme for Research and Innovation under the Specific Grant Agreements No. 720270 (Human Brain Project SGA1) and No. 785907 (Human Brain Project SGA2) and by the EBRAINS research infrastructure, funded from the European Union’s Horizon 2020 Framework Programme for Research and Innovation under the Specific Grant Agreement No. 945539 (Human Brain Project SGA3).
Copyright (c) 2016-2024 Blue Brain Project/EPFL
Copyright (c) 2025-2026 Open Brain Institute
4 maintainers
Metadata
4 maintainers
Release files for bluepyefe 2.3.63
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 | |
|---|---|---|---|---|
| bluepyefe-2.3.63.tar.gz | 1.1 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bluepyefe-2.3.63-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.1 MB
Release files / bluepyefe-2.3.63.tar.gz
| Download URL | bluepyefe-2.3.63.tar.gz |
|---|---|
| Size | 1.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ff475ade62eb3513b00a69076ae3b446d69c1ffbfb7bc8928b039111c96e62a3
|
|
BLAKE2b-256 checksum How to use checksums |
564e470aa2674010e3b44c6ac2bb66baac5134bcf90b3a87f299b3b395d4fda3
|
| 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 24, 2026.
Transparency logRelease files / bluepyefe-2.3.63-py3-none-any.whl
| Download URL | bluepyefe-2.3.63-py3-none-any.whl |
|---|---|
| Size | 74.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9c2add48971f9daadfffd19236d7c83c013b1e0b94b49cd71e3a4a58d58919e2
|
|
BLAKE2b-256 checksum How to use checksums |
fba4adc0a1d755f2ece23f0d815525ef4cd0642ffd1849176790c3225a8ac38c
|
| 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 24, 2026.
Transparency logSecurity for bluepyefe 2.3.63
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 bluepyefe-2.3.63.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 24, 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.
