pylabianca
Python tools for spike analysis.
pylabianca:
- allows to read, analyse spike rate and statistically compare conditions in just a few steps
- follows the convenient API of mne-python
- provides two straightforward objects for storing spiking data:
SpikesandSpikeEpochs - allow storing trial-level metadata in these object (just like mne-python) and selecting trials based on these metadata
- returns xarrays (arrays with labeled dimensions and coordinates) as output from operations like cross-correlation, spiking rate calculation or decoding analysis
- these xarrays inherit all the trial-level metadata and can be visualised splitting by conditions using
pylabianca.viz.plot_shadedor native xarray plotting - the xarrays can be statistically tested with cluster based permutation test comparing condition metadata
installation
pylabianca can be installed using pip:
pip install pylabianca
To get most up-to-date version you can also install directly from github:
pip install git+https://github.com/labianca/pylabianca
what's new?
See whats_new.md for documentation of recent changes in pylabianca.
docs
Online docs are currently under construction.
Below you can find jupyter notebook examples showcasing pylabianca features.
- introductory notebook - a general overview using human intracranial spike data (sorted with Osort).
- FiedTrip data example notebook - another broad overview using fieldtrip sample spike data from non-human primates.
- decoding example - overview of decoding with pylabianca
- spike-triggered LFP analysis - use pylabianca and
MNE-Pythonto perform spike-triggered analysis of LFP - working with spiketools - example of how
spiketoolsand pylabianca can be used together
To better understand the data formats read natively by pylabianca (and how to read other formats) see data formats page.
sample data
You can get example human data that are used in the examples here.
The preprocessed FieldTrip data used in the examples are available here.
Metadata
Release files for pylabianca 0.3.0
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 |
|---|---|---|---|---|
| pylabianca-0.3.0.tar.gz | 108.2 kB | Without provenance | Details for pylabianca-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pylabianca-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for pylabianca-0.3.0-py3-none-any.whl |
Total release size: 232.4 kB
Release files / pylabianca-0.3.0.tar.gz
| Download URL | pylabianca-0.3.0.tar.gz |
|---|---|
| Size | 108.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
71b3e1fcc480392e5e4659f44fe1b1c457a8c25e2d5fe49dcd019d04aeedb1c5
|
|
BLAKE2b-256 checksum How to use checksums |
4d3dfba36c174ee12c8f29af8c96e7b4847da64469bbef44e28dccdf7ffbd6ed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.4
|
Release files / pylabianca-0.3.0-py3-none-any.whl
| Download URL | pylabianca-0.3.0-py3-none-any.whl |
|---|---|
| Size | 124.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
94b653e899bba4214d647ce287cdacbf300306c5128a0f89fd063e11e0d2aa6c
|
|
BLAKE2b-256 checksum How to use checksums |
a23af50e40aa22a877ae3bce4e6a91c2ddf9f985565540fbf759d80b88fa7938
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.4
|
Security for pylabianca 0.3.0
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.