melizalab-tools
A collection of python code and scripts used by the Meliza Lab.
To install: pipx install melizalab-tools
modules
dlab.pprox: functions for working with pprox objects, a data format for storing multi-trial point process data (e.g. spike times evoked by stimulus presentation).
dlab.neurobank: some convenient wrappers for interacting with a neurobank repository and archives.
dlab.signal: signal processing functions
console scripts
group-kilo-spikes: sort spike times output from kilosort and phy2 into pprox files (stimtrial format), optionally recording pulses on auxiliary channels such as optogenetic stimulation (--aux). For recordings without a sync track, --audio-sync CHANNEL finds the stimulus onsets on a copy of the audio by cross-correlation (python -m dlab.audio_sync does this on its own, for checking a recording). If only part of the recording was sorted, --sort-start and --sort-stop give the part. Where kilosort’s output for it starts is found by checking it against the recording’s neural channels, to the sample, and the output is timed from the recording’s start. Stimuli presented under other names than they were deposited under are mapped with --alt-stim-names. The outputs record the sort, the sorter’s version (read from kilosort 4’s log, or given with --sorter), and how many of each unit’s spikes were dropped and why.
audit-kilo-spikes: check the group-kilo-spikes output for one recording against its waveform files, the stimulus messages in the ARF file, and each other, and write a JSON report. Changes nothing.
find-kilo-units: find the units of recordings in the registry and write a control file for running audit-kilo-spikes in batches.
collect-kilo-audit: summarize the audit-kilo-spikes reports.
regenerate-pprox: rebuild missing pprox files from their waveform files.
get-songs: extract segments from arf files, rescale, resample, save into wave files, and optionally deposit back into neurobank. Usually the first step in generating a stimulus set, keeps a nice provenance trail.
See docs/audit.md for how to run the audit and what its findings mean.
other stuff
1 maintainer
Metadata
1 maintainer
Release files for melizalab-tools 2026.10.14
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| melizalab_tools-2026.10.14.tar.gz | 3.2 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| melizalab_tools-2026.10.14-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.2 MB
Release files / melizalab_tools-2026.10.14.tar.gz
| Download URL | melizalab_tools-2026.10.14.tar.gz |
|---|---|
| Size | 3.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
00e407f7455332b0bde81866d2da671b714b63e7e84775e998237e74c963d65a
|
|
BLAKE2b-256 checksum How to use checksums |
ceaff11fc9b6183e50099f09e5ccbbeb236ed18684d539fe5aa66f7a4d3bd61f
|
| 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 15, 2026.
Transparency logRelease files / melizalab_tools-2026.10.14-py3-none-any.whl
| Download URL | melizalab_tools-2026.10.14-py3-none-any.whl |
|---|---|
| Size | 85.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
415b69d8b1a7e9599ccf986a6adbc879521fd1fa8f8483dfe63deff8ae505396
|
|
BLAKE2b-256 checksum How to use checksums |
e76cf354dc3e17abaab5d5c146c8c331b6e3eb87e470e13d7e566d2d51ae5ecc
|
| 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 15, 2026.
Transparency log
