Closed bjhardcastle closed 7 months ago
Hi Ben, I'll take a look at the key error!
I think that the pipeline shouldn't fail fast in case of a spike sorting error, especially when there are many streams available. If only one spike sorting fails, then the entire pipeline will go fine for the others, plus the visualization will plot the traces that might be importanti for trouble shooting.
The KeyError is unrelated and that is triggering the failure. It is due to a mismatch in the aind-data-schema
that I'm investigating now.
For the spike sorting failure, I think it's the GPU RAM that's running out of memory, since it's happening during the Optimizing templates
step. Not sure how we can select larger GPUs on CodeOcean.
Fixed :)
Run 9595167
Seem to be two errors: running out of memory during spike-sorting, then a KeyError.
This also seems like a repeat of https://github.com/AllenNeuralDynamics/aind-ephys-spikesort-kilosort25-full/issues/22