-
Notifications
You must be signed in to change notification settings - Fork 5
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
Accessing data from read-only cache directory #64
Comments
Hello, if you already have the data locally you can use ONE in local mode like this: |
Thanks! I'm able to initialize a I can load a trials object from the local directory, but |
If you set up ONE with a local directory instead of a database URL it will return an instance of the
I'll add this to the ONE documentation FAQ. [Edit] Added here: https://one.internationalbrainlab.org/FAQ.html#how-do-i-use-one-in-a-read-only-environment |
Thanks! This is working now, with a few minor caveats:
Once I figured these things out, everything went smoothly. |
ONE currently assumes write access to the cache directory. However, there are some cases where it would be helpful to mount a database as a read-only input to an analysis environment. And ideally, if the analysis is being carried out on AWS, one should be able to read data from the original bucket (e.g.
s3://ibl-brain-wide-map-public/data
).With a local install of the
ONE
package, I found two places where it tries to write to the cache directory:webclient.py
line 138api.py
line 1476After commenting out those actions, I was able to successfully access data from a read-only S3 bucket. However, it failed when I tried to load the spike sorting results due to a file that wasn't downloaded when I first created the cache directory (
electrodeSites.brainLocationIds_ccf_2017.npy
).Hopefully it's not too difficult to check whether ONE has write access to the cache directory and use that information to update its behavior.
The text was updated successfully, but these errors were encountered: