You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
I guess the easiest thing is just for each user to have an individual
"installation" (where this of course just means an individual copy of the
code). Sorry that I didn't write it with that scenario in mind, you're
right that the home directory would have made more sense, but given the
easy workaround I'd prefer not to modify this behavior now.
On Thu, Jan 7, 2021 at 2:58 PM randybruno ***@***.***> wrote:
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?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#303>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABZ5IP3TRV5OWFDXVKF627TSYY4DBANCNFSM4VZUPEQQ>
.
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?
The text was updated successfully, but these errors were encountered: