marius10p
commented
5 years ago The last change to spike deconvolution I remember was more than 5 months ago and it was a change in running baseline correction. If it's not that, have you checked that your timescale and sampling rate is the same? Btw, the new version looks better to me, the old seems to have been losing some smaller transients, which is exactly what you'd expect if the baselining was not good.
The Python version also has running baseline correction, but some of the parameters might be treated differently, for example sampling rate is per plane not cumulative. Other than that, I think the baselining might be slightly different, I could double check. Would be good to figure this out, we'd like the Python and Matlab versions to be as similar as possible.
horsto
Hello! I have a problem with the output from deconvolution (OASIS). I noticed in recent analysis output that my spike matrices were much denser in comparison to ones I analyzed about half a year ago. Since then I have updated both the OASIS matlab package and suite2p code. I am thresholding the deconvolution output with
mean + 2 * standard deviationfor every cell, which seems to give stable results (across sessions / animals), meaning, results that "by eye" look reasonable. Now the same threshold does not filter the output adequately. I am showing an example of 4 different sessions, analyzed with old and new code, below.I tried to revert the OASIS package to the code version I used ~5 months ago. With all suite2p parameters the same (no differences in "ops") there are still differences visible (OLD - old analysis result, NEW - same cell, with old OASIS package and up-to-date suite2p code).
There are also apparent differences in the neuropil corrected traces in the examples above. I also tried to run the suite2p python version which, with the thresholds I usually use, leads to good results! Since my pipeline depends still on the Matlab version for now I would appreciate any input on what might be going on.