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

Running a shared installation? #303

Closed
ifittakesallnight opened this issue Jan 7, 2021 · 1 comment · Fixed by #595
Closed

Running a shared installation? #303

ifittakesallnight opened this issue Jan 7, 2021 · 1 comment · Fixed by #595

Comments

@ifittakesallnight
Copy link

We installed Kilosort on a GPU-equipped many-core large-RAM-capacity linux server. The Kilosort GUI has to be able to write to the Kilosort/gui directory. We could of course make this directory write-able by all users as there's only one GPU installed and only one user would use it at a time. But given that the GUI seems to write the location of the previously opened file, cutoff values, number of channels, etc, this might still cause problems in a shared install scenario. Is there an option so that Kilosort saves these to the user's home directory rather than the Kilosort/gui directory? Or do you just recommend that each user install Kilosort for themselves?

@nsteinme
Copy link
Collaborator

nsteinme commented Jan 7, 2021 via email

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.

3 participants