-
Notifications
You must be signed in to change notification settings - Fork 155
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
Index "xyz" is out of bounds for axis "xyx" #2779
Comments
Could you copy the complete stack trace? We need to see where the error comes from. |
sure. here it is IndexError Traceback (most recent call last) File ~\spikeinterface\src\spikeinterface\widgets\amplitudes.py:59, in AmplitudesWidget.init(self, sorting_analyzer, unit_ids, unit_colors, segment_index, max_spikes_per_unit, hide_unit_selector, plot_histograms, bins, plot_legend, backend, **backend_kwargs) File ~\spikeinterface\src\spikeinterface\core\sortinganalyzer.py:1476, in AnalyzerExtension.get_data(self, *args, **kwargs) File ~\spikeinterface\src\spikeinterface\postprocessing\spike_amplitudes.py:143, in ComputeSpikeAmplitudes._get_data(self, outputs) IndexError: index 2054149 is out of bounds for axis 0 with size 2054146
|
Which sorter are you using? This has happened before but I can't quite remember if it was the excessive spike issues. Did you load in the |
i used ks2.5. I have not done sorting_wout_escessive_spikes yet, but I will do it and let you know. |
Kilosort (all flavors) is the one we typically see having excessive spikes (usually after the recording ends). so if using KS, the remove excess spikes can be beneficial. |
It worked with |
Does it make sense to put this as a suggestion in the assert message? |
I would vote Yes! |
I think the issue is we don't know that you have excessive spikes until the |
Thanks @zm711 to me that makes sense, I am not caught up yet with the |
Hi,
I am getting the index error saying that "index 2054149 is out of bounds for axis 0 with size 2054146" when I try to run
sw.plot_amplitudes(sa,backend='ipywidgets')
. I am aware what this error means, but knowing that this is not due to any incorrect indexing logic in the source code, I am assuming that this is a rare scenario and may be issues with sorting or something else. Not sure how to resolve this. This is the first time I have gotten this error in spikeinterface and I haven't made any changes to the order of how I process my data. Is it something with the data itself? Not sure, because my data is still 30ish minutes long recordig and that has been the same all my recordings.Also, is it something similar to 'more spikes than the length of the recording' occassionally spike sorting causes? By that I mean an error originating from sorting. The workaround for that kind of error I used is:
Is there a similar workaround or a similar solution for this error?
Thanks
The text was updated successfully, but these errors were encountered: