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

Analyze file which require write access #57

Open
marcelo-moglie opened this issue Aug 13, 2021 · 4 comments
Open

Analyze file which require write access #57

marcelo-moglie opened this issue Aug 13, 2021 · 4 comments

Comments

@marcelo-moglie
Copy link

Try symbolic link for Kilosort

@znamensk
Copy link
Member

Do you mean that you need to overwrite the Dataset the you are analyzing? I would call Dataset.from_flexilims, run the analysis - as long as you have permission on CAMP - then update the attributes and created property and call the update_flexilims method.

@ablot
Copy link
Member

ablot commented Aug 15, 2021

I think that kilosort does not require write access to the data file itself but must write its output in the same directory as the data. I want to try to create a folder in the processed data directory with a symbolic link to the dataset and see if kilosort is happy to use that.
We just tried to make sure that the linking works with Marcelo, but we did not have any ephys dataset to do the actual test.

@znamensk
Copy link
Member

That's annoying. Which files must it save there? From my quick dig around the kilosort repo, it looks like both the temporary binary and the phy2 output can be at a custom path.

Maybe forking kilosort and making a pull request to set custom paths would be a more elegant solution, if it's not too complicated?

@ablot
Copy link
Member

ablot commented Aug 15, 2021

Maybe it's not an issue anymore. If we change the temporary "fast ssd" path and replace the output line https://github.com/MouseLand/Kilosort/blob/main/main_kilosort3.m#L50

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