-
Notifications
You must be signed in to change notification settings - Fork 87
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
Why are mean_waveforms worise by using the temp_wh.dat as row data than .bin file? #80
Comments
Hi – you can't use |
Thanks,I get it!
|
Hi!
I saw that the continous data can be .bin file or .dat file in these modules. As the temp_wh.dat file created by kilosort3 is whitened and high pass filtered, I think the outputs like mean waveforms, SNR and other quality control parameters should be better than using the .bin file. But I found that by using the temp_wh.dat as continous file to run the modules, the meanwaveforms are worise, the SNR is much lower. Why?
for example, the following pictures are the ploted mean waveforms of the same cluster:
by using the bin file:
SNR is 1.008
by using the temp_wh.dat file:
SNR is just 0.065
Is there anything wrong when I use the modules?
More information:
the bin file is created by SpikeGLX.
I just run the kilosort postprocessing, noise_templates,mean_waveforms,quality_metrics modules because the kilosort3 has been run manully.
The text was updated successfully, but these errors were encountered: