Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compute quality metrics after pipeline nodes #2773

Merged

Conversation

alejoe91
Copy link
Member

Fixes #2772

@zm711 this is a temporary solution that works for the time being. We can look for a more flexible and long-term solution later

Comment on lines +1029 to +1032
# PATCH: the quality metric is computed after the pipeline, since some of the metrics optionally require
# the output of the pipeline extensions (e.g., spike_amplitudes, spike_locations).
# An alternative could be to extend the "depend_on" attribute to use optional and to check if an extension
# depends on the output of the pipeline nodes (e.g. depend_on=["spike_amplitudes[optional]"])
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

perfect

@alejoe91 alejoe91 added the core Changes to core module label Apr 29, 2024
Copy link
Collaborator

@zm711 zm711 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. I'll run one quick test when I get to lab :)

src/spikeinterface/core/sortinganalyzer.py Outdated Show resolved Hide resolved
Co-authored-by: Zach McKenzie <92116279+zm711@users.noreply.github.com>
@zm711
Copy link
Collaborator

zm711 commented Apr 29, 2024

Tested and this worked for me locally.

@samuelgarcia samuelgarcia merged commit 0af935e into SpikeInterface:main May 13, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Changes to core module
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SortingAnalyzer doesn't respect order of compute in case of nodepipeline + non-nodepipeline code
3 participants