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

"Quality is a required field" when uploading Kilosort4 #869

Open
oliriley opened this issue Jun 21, 2024 · 3 comments
Open

"Quality is a required field" when uploading Kilosort4 #869

oliriley opened this issue Jun 21, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@oliriley
Copy link

Describe the issue

When attempting to convert a paired Open Ephys recording with its associated spike sorting, I encountered an error stating "quality" was required in the table describing the units:
Screenshot 2024-06-21 120318

No quality.npy or similar is present in the kilosort results folder. The data were processed with kilosort 4 and the same issue arrises whether uploading a Kilosort session alone or a Phy session after curation.

Steps to Reproduce

  1. Begin new conversion
  2. Select Kilosort or Phy interface
  3. Provide path to sorting results folder containing params.py
  4. Hit next to extract metadata
  5. Error under "Ecephys" -> "Summarized Units"

Operating System

Windows 11 Home

GUIDE Version

1.0.1 (I think)

Code of Conduct

Yes

Did you confirm this issue was not already reported?

Yes

@CodyCBakerPhD
Copy link
Collaborator

CodyCBakerPhD commented Jun 21, 2024

Hi @oliriley

Unfortunately, I'm having trouble reproducing this on our current example data (for Kilosort/Phy, that is) - would you be able to share your data over Google Drive or Dropbox so I can try to get to the bottom of this? (spike sorting data may also be small enough to zip and send over GitHub)

Two other things to try might be

i) Use the Phy interface instead (KS3 as I recall is essential equivalent to Phy minus certain unit classifications) I see you tried that and the problem persists
ii) Go ahead and write in a value for that field on the table; 'unknown' is also acceptable as a placeholder Nevermind, I don't think we have enabled interactive editing of those columns on the summary table

@CodyCBakerPhD
Copy link
Collaborator

Another option that I believe should work is

iii) delete the row with the name 'quality' on the UnitsProperties tab and that column of the Summarized units should disappear

@CodyCBakerPhD CodyCBakerPhD self-assigned this Jun 24, 2024
@CodyCBakerPhD
Copy link
Collaborator

But I see that (iii) is also blocked by #873

@CodyCBakerPhD CodyCBakerPhD removed their assignment Jul 29, 2024
@CodyCBakerPhD CodyCBakerPhD added the bug Something isn't working label Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants