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

saving to destination #272

Closed
stagkourakis opened this issue Nov 9, 2020 · 5 comments · Fixed by #595
Closed

saving to destination #272

stagkourakis opened this issue Nov 9, 2020 · 5 comments · Fixed by #595

Comments

@stagkourakis
Copy link

Hi Marius,

A minor bug; on a specific desktop, when I use KS2.0 everything runs smoothly, but KS2.5 gives an error at the very end of the spike sorting process: "Error writing to destination. Use the 'f' option to override." Any thoughts?

Best wishes,
Stefanos

@marius10p
Copy link
Contributor

Hi Stephanos, exactly when does this happen? Send more of the error please.

@stagkourakis
Copy link
Author

stagkourakis commented Nov 9, 2020

Of course! Does the following picture help?
errorSavingKS2-5

I only get this error: "Error saving data for phy! Cannot write to destination: ... Use the 'f' option to override"
with KS2.5 and not with KS2.0

@stagkourakis
Copy link
Author

Hi again Marius. Here is an update to this issue:

KS2.5 generates and saves all output files to the output directory apart from the params.py file. By manually adjusting the contents of the params.py file, I can see that the spike sorting with KS2.5 was successful, and do the manual curation in phy without problems.

Overall it works, apart from this minor nuisance. Feel welcome to close this issue.

@marius10p
Copy link
Contributor

Could you run in debug mode so we can see exactly what line it fails on? It is curious that it works differently between 2.0 and 2.5.

@stagkourakis
Copy link
Author

stagkourakis commented Dec 15, 2020

Hi Marius!
The issue I reported here, did not occur again, and I don't think it was an issue due to a Kilosort bug. My understanding is that it occurred due to Administrator rights and because the KS output folder was READ ONLY. Sorry for the false alarm.

I will now close this issue, and thanks for your attention to this.
Stefanos

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.

2 participants