Alessio Buccino

Hi @tinaxia2016 Sorry for the delay! Could you share the `phy` folder with me? I'll take a look!

Hi @max-c-lim Unfortunately, because of the filter, the binary input data will be slightly different using different chunk sizes. We use a margin for the chunks to ameliorate the margin...

Also, note that Kilosort always find a slightly different set of units and spikes. So I don't think the mismatch is due to the different chunking. You can also try...

I see. You could try to use `total_memory='100G'`, but then it would only use one job..so it's a tradeoff. Anyways, I would recommend to check the traces ;)

Unfortunately KS GPU errors are not very interpretable! Honestly I usually use smaller chunks, like `total_memory='1G'`! Give it a try!

@bendichter just to double check you get normal output for `nvidia-smi`?

Ahhhh that might explain it!

Any update on this?

Thanks Philipp! Can confirm that this is Windows-specific:  Can you try to run `sorting_well_1 = si.run_sorter('tridesclous2', recording, job_kwargs={'n_jobs' : 1, 'chunk_duration' : '1s', 'verbose' : False})`? Just to confirm...

ahhh! Interesting! We should handle the logic better then when -1 (n_jobs = n_cpus) is used