Kilosort icon indicating copy to clipboard operation
Kilosort copied to clipboard

features view cannot load it phy.

Open WeissShahaf opened this issue 4 years ago • 7 comments

features view cannot load it Phy. it did for KS 2.5

WeissShahaf avatar Feb 02 '21 10:02 WeissShahaf

Yes, I had the same issue. Is it a "save for phy" issue where pc_features.npy file is not saved?

aarac avatar Feb 02 '21 14:02 aarac

In the final_clustering routine in the main_kilosort script, I noticed that

rez1.cProj = [];
rez1.iNeigh = [];
rez1.cProjPC = [];
rez1.iNeighPC = [];

rez1 then gets returned as rez.

rezToPhy2 (used to store output to Phy format) skips storing feature related npy cause it is empty.

rajatsaxena avatar Feb 02 '21 17:02 rajatsaxena

I know, it's because the clustering is done very differently now. The feature view is going to come back in an upgrade, soon ish.

marius10p avatar Feb 02 '21 17:02 marius10p

Without this view, how do you verify that the spike sorting algorithm worked well? One of the main criteria we use is to look at a histogram of cProj or a scatter plot vs time. If these views look cut off it means there are some low-amplitude spikes that got missed, so it's not a single unit. Also useful for seeing if two clusters are too similar.

Thanks for all your work on this by the way, an awesome tool!

lshaheen avatar Apr 08 '21 21:04 lshaheen

Hi Marius, great work overall. However, is there any timeline when the feature view is coming back for kilosort 3 anytime soon? I am very much relying on this during curation in phy. For now I still have to use KS 2, because KS 2.5 always gives me an assertion error. My NPIX recordings contain lots of internal high frequency noise, so I preprocess the data prior to loading it into KS (band pass filtering, setting those channels that don't show spiking activity to NaN). Thanks

metmic avatar Jun 15 '21 17:06 metmic

any news on when we can expect to see PC features for phy again?

i'm getting 4-5 good units, and 100 mua's that i cannot split because i have no PCA space to do it in.

thanks, shahaf

WeissShahaf avatar Nov 09 '21 11:11 WeissShahaf

Any updates on this feature? Very much needed. Thanks!

pabloslash avatar Dec 01 '21 19:12 pabloslash

Bump! Any updates on this?

nataliekoh avatar Oct 21 '22 19:10 nataliekoh

Kilosort no longer uses the features. But u could compute them yourself from the raw data, given the timestamps of the spikes. Then format it so phy can read it.

I'd be happy to know if anyone already has a script for that.

Shahaf Weiss, PhD

Max Planck Institute for Brain Research

NSK - Laurent department Max-von-Laue-Str. 4 60438 Frankfurt am Main, Germany www.brain.mpg.de

@.***

@.***

Tel:+49 17657814689

On Fri, Oct 21, 2022, 21:33 Natalie Koh @.***> wrote:

Bump! Any updates on this?

— Reply to this email directly, view it on GitHub https://github.com/MouseLand/Kilosort/issues/317#issuecomment-1287360743, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK4J42GMWJ6EQV3JWRZQWY3WELVZNANCNFSM4W6MEN5A . You are receiving this because you authored the thread.Message ID: @.***>

WeissShahaf avatar Oct 21 '22 19:10 WeissShahaf

Before you run phy template-gui params.py to open the gui, run phy extract-waveforms params.py. Then phy can open feature view. (It worked on my Kilosort3)

tianw6 avatar Jan 05 '23 17:01 tianw6

@tianw6 - that was a nice suggestion!

moscraciunxxx avatar Mar 19 '23 11:03 moscraciunxxx