-
Notifications
You must be signed in to change notification settings - Fork 20
Conversation
Sorry, was off this while handling something, I'm going to test but I wanted to know if the return_rescaled is also merged into master. I was working from return_rescaled. |
Yes into master and released :) |
Ok, not sure if this was a problem with the local work I was doing to sort the loading (based on
I'll dig into this more now, but if you see something obvious, let me know. |
Yep the openephys extractor doesn't have a style arg anymore as this is handled internally by the return_scaled |
Ok, I removed it and ran through. Seemed good, until I realised I'd been still running a version of pyopenephys forked from an old release for reasons that had been necessary but I can't reconstruct. So, mixed results after further testing. First, when running with my pyopenephys 1.0.7 forked branch for hacking the 'int16' problem, I got:
Realising that I was getting a deprecation warning, I switched to a clean 1.1.3 pyopenephys and encountered:
So walking backwards, pyopenephys 1.1.2 produced:
and with pyopenephys 1.1.0:
Finally, reverting to a clean pyopenephys 1.0.7, it worked again. |
@eejd ok it seems to have a problem in dumping the OpenEphys extractor. If |
So I think the three problems were each different (i.e. that occurred at a different part of the processing pipeline). With 1.1.3, the problem is at the call to the sorter (KiloSort2 in this case). Note the final cause of the exception:
For the errors <= 1.1.3, the problems are occurring before the call to the sorter. With 1.1.2 it is in the call to the CacheRecordingExtractor with a save location. If I
1.1.0 fails at SI versions:
|
Thanks @eejd ! I think we should focus on solving the first problem. Could I ask you if you are willing to share this dataset with me? It would greatly help debugging it! |
Quick test: what does |
I think so, let me check with the collaborators. Also, if you want to do a quick audio/video call that's no problem. Also, I'll be working on this more continuously again, so I will try to look through the recent merges to understand the change. |
|
@alejoe91 How should I prepare and send the data set? |
You can send me an email and share the data on gdrive with a script/notebook to reproduce the error :) |
Fixes https://github.com/SpikeInterface/spikesorters/issues/206
@eejd can you try that out? Note that you need the master version of spikeextractors and spiketoolkit