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

OSerror when trying save preprocessed copy in kilosort4 #805

Open
kingsEffy opened this issue Oct 24, 2024 · 3 comments
Open

OSerror when trying save preprocessed copy in kilosort4 #805

kingsEffy opened this issue Oct 24, 2024 · 3 comments

Comments

@kingsEffy
Copy link

Describe the issue:

Hi,
Have anyone experienced this error in kilosrt4 GUI when trying to save preprocessed dat copy? We are using standard parameter settings. And there i8s no such error before when we did not select save copy.

Screenshot 2024-10-24 155635

Reproduce the bug:

No response

Error message:

No response

Version information:

Kilosort 4: Kilosort version 4.0.15

@jacobpennington
Copy link
Collaborator

Can you please attach a screenshot of what the Kilosort4 GUI looks like after loading the data?
You should also try updating to the latest version of Kilosort, v4.0.19.

@KunmingS
Copy link

Seems like results_dir / 'temp_wh.dat' did not act correctly so np.memmap has an invalid argument. Do you assigned results_dir on GUI? And could you please check if the results_dir exist? According to https://github.com/MouseLand/Kilosort/blob/v4.0.15/kilosort/gui/sorter.py#L46, if self.results_directory has a meaningful value, then the result_dir should exist on disk. result_dir had been assigned on https://github.com/MouseLand/Kilosort/blob/v4.0.15/kilosort/gui/main.py#L500. And I don't think this issue is related to version cause all related code remains unchanged from 4.0.15 to 4.0.19.

@jacobpennington
Copy link
Collaborator

jacobpennington commented Oct 29, 2024

@KunmingS Can you please attach a screenshot of what the Kilosort4 GUI looks like after loading the data, if you're having this issue as well?

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

No branches or pull requests

3 participants