Skip to content
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

Scaling factor for int16 #531

Closed
mvincenziit opened this issue Feb 10, 2023 · 0 comments · Fixed by #595
Closed

Scaling factor for int16 #531

mvincenziit opened this issue Feb 10, 2023 · 0 comments · Fixed by #595

Comments

@mvincenziit
Copy link

Hi Marius,

first of all, very nice to meet you and thanks a lot for your contributions.

I have a doubt on the scaling factor applied to imported data. By reading your last publication "Solving the spike sorting problem with Kilosort" I understood that data in uV should be multiplied by 200 before exporting to int16. I found a confirmation of that in the code (a factor obj.P.vScale=0.005 multiplies input data in ksGUI for bringing data back to uV scale). That means that input data as an allowed range in the interval ±163.835 uV.

Can you please confirm that? Was it documented somewhere? I didn't find any reference/tip on the wiki.

I have been using Kilosort without applying that factor, still units were correctly identified. Is there an internal check that tries to automatically compensate the signal's scale.

Thanks in advance,
Matteo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant