Skip to content

amplitude cutoff should require amplitude scalings extension#4513

Open
Julie-Fabre wants to merge 1 commit into
SpikeInterface:mainfrom
Julie-Fabre:amplitude-scalings
Open

amplitude cutoff should require amplitude scalings extension#4513
Julie-Fabre wants to merge 1 commit into
SpikeInterface:mainfrom
Julie-Fabre:amplitude-scalings

Conversation

@Julie-Fabre

Copy link
Copy Markdown
Contributor

This is a proposal (please close if you don't agree) to require amplitude scalings for the amplitude cutoff metric.
I also modified in conftest.py make_small_analyzer & sorting_analyzer_simple to have amplitude scalings - let me know if that's right, I am not sure.

@samuelgarcia

Copy link
Copy Markdown
Member

I think I am OK with this a metrics should refer to only on thing.

@alejoe91 alejoe91 added postprocessing Related to postprocessing module metrics Related to metrics module labels Apr 17, 2026
@zm711

zm711 commented Jul 10, 2026

Copy link
Copy Markdown
Member

For reproducibility it makes sense to rely on only one thing. But I am a bit worried about past users that may have determined their amplitudes previously without scalings. If they want to recalculate this then we error. We allow templates to be fast templates or based on waveforms so we aren't completely strict on this.

I suppose I could go either way in the end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

metrics Related to metrics module postprocessing Related to postprocessing module

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants