Skip to content

Fix PCA metric recomputation when "soft" merging - #4748

Open
RobertoDF wants to merge 2 commits into
SpikeInterface:mainfrom
RobertoDF:fix-soft-merge-pca-metrics
Open

Fix PCA metric recomputation when "soft" merging#4748
RobertoDF wants to merge 2 commits into
SpikeInterface:mainfrom
RobertoDF:fix-soft-merge-pca-metrics

Conversation

@RobertoDF

Copy link
Copy Markdown
Contributor

Soft merges and splits recompute quality metrics only for newly created units. Previously, this subset was also used as the complete PCA comparison population. Consequently, merged units could not see neighboring unchanged units, producing incorrect "No other units found" warnings and invalid or fallback PCA metrics.

Keep the recomputation targets limited to new units, but use all analyzer units
for PCA projections, neighbor selection, spike counts, and firing rates.

Done with help from copilot, seems reasonable, results seems fine

RobertoDF and others added 2 commits September 1, 2026 13:48
Use every analyzer unit as PCA comparison context when recomputing metrics only for newly merged or split units.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@chrishalcrow chrishalcrow added this to the 0.105.0 milestone Sep 3, 2026
@alejoe91 alejoe91 added the postprocessing Related to postprocessing module label Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

postprocessing Related to postprocessing module

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants