Open RikkelBob opened 1 month ago
Maybe related #3392? I'll have to read a bit more later. Are you using a probe group or probe?
@zm711 I don't use probe groups, just a probe - recording.set_probe(probe_64, in_place=True)
Internally we are representing probes as a probegroup (see here https://github.com/SpikeInterface/spikeinterface/blob/73f4d58d2d542e607155d49d30716cc28215e12f/src/spikeinterface/core/sortinganalyzer.py#L1101-L1106) so if there is some sort of bug happening when we get the probegroup (to get your probe) it could affect this as well. Do you want to try exporting from that PR and see if it fixes things or if it is still broken.
I've tried it now, but the issue persists
Okay thanks. We will read this more closely soon and see if we can find the place soon.
Would love to hear it if anything has been found related to this :)
@alejoe91 could you check this?
After manual curation, I'm recalculating cluster waveforms and some quality metrics using the script below. However, when I export to phy, the channel numbers are wrong. When I pause/debug the script before
export_to_phy
, channel numbers are correct, but inspecting cluster_info.tsv after exporting, they're different. I would fix this post-hoc, but because the channel numbers are wrong, the calculated waveforms and subsequent waveform based quality metrics are also incorrect. I'd very much appreciate any help!