Spike Encoders
| Branch | Codecov | CI |
|---|---|---|
| Master | Soon.. |  |
Spike encoders for Spiking Neural Network.
This package consists of two types of spike encoders for spatio-temporal data:
- Threshold Based Representation (TBR) encoder
- Bens Spiker Algorithm (BSA) encoder
Data
The data given to the encoders are spatio-temporal. Each sample is one csv file. In each file, every column is a feature and the rows are time points.
For example each file given in the Data folder had 128 rows and 14 columns, 14 columns are the features and 128 columns are the data points.
Instillation
pip install pyspikes
Example
from spikes import encoder
from spikes.utility import ReadCSV
data = ReadCSV("Data").get_samples()["samples"]
bsa = encoder.BSA(data)
print(bsa.get_spikes())
tbr = encoder.TBR(data)
print(tbr.get_spikes())
Contribution
All contributions are welcome.
Issues
Issues can be opened through Github's Issues tab.
1 maintainer
Metadata
1 maintainer
Release files for pyspikes 0.2.11
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 |
|---|---|---|---|---|
| pyspikes-0.2.11.tar.gz | 8.7 kB | With provenance | Details for pyspikes-0.2.11.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyspikes-0.2.11-py3-none-any.whl | Python 3 | none | any | Details for pyspikes-0.2.11-py3-none-any.whl |
Total release size: 21.0 kB
Release files / pyspikes-0.2.11.tar.gz
| Download URL | pyspikes-0.2.11.tar.gz |
|---|---|
| Size | 8.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9f91f88a388dbe282837ea44e3ad1d3e81c92647d4de0a550f50e060cf11e3a1
|
|
BLAKE2b-256 checksum How to use checksums |
daf5f2fc2ff7af11dc145189140ccf2c918ef6f7ca426267db0a4a4513411390
|
| 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 Oct 19, 2026.
Transparency logRelease files / pyspikes-0.2.11-py3-none-any.whl
| Download URL | pyspikes-0.2.11-py3-none-any.whl |
|---|---|
| Size | 12.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
780775fc2a5e2461297e983e725cd9f820a90dba83e649cf9cae122c98315468
|
|
BLAKE2b-256 checksum How to use checksums |
4875aaa83a9fae78c534368833459687a5a8d5eb1536559b7b74d6a6829c6380
|
| 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 Oct 19, 2026.
Transparency logSecurity for pyspikes 0.2.11
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 pyspikes-0.2.11.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 Oct 19, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
