Skip to content

Remove peak_sign in favour of main_channel_index#4624

Draft
chrishalcrow wants to merge 18 commits into
SpikeInterface:mainfrom
chrishalcrow:less_peak_sign_more_main_channel
Draft

Remove peak_sign in favour of main_channel_index#4624
chrishalcrow wants to merge 18 commits into
SpikeInterface:mainfrom
chrishalcrow:less_peak_sign_more_main_channel

Conversation

@chrishalcrow

@chrishalcrow chrishalcrow commented Jun 23, 2026

Copy link
Copy Markdown
Member

Sequel to #4374

I didn't have permission to push to Sam's branch, so I made my own...

Idea is that when you make your analyzer, it must have a peak_sign, peak_mode and hence a main_channel_index. We then use these throughout the codebase instead of propagating the other stuff.

@samuelgarcia did the tedious work, but now I'm refining and getting the tests to pass...

WIP!

@chrishalcrow chrishalcrow added core Changes to core module postprocessing Related to postprocessing module labels Jun 23, 2026
@chrishalcrow chrishalcrow changed the title Remove peak_sign in favour of main_channel Remove peak_sign in favour of main_channel_index Jun 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core Changes to core module postprocessing Related to postprocessing module

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants