Open julia-napoli opened 9 months ago
@julia-napoli, have you tried running this code locally on a jupyter notebook on your machine? Have you also verified that the parent directory '/content/drive/MyDrive/Personal_notebooks/Julia_Notebook/Imaging/hunger_state/DATA/240126f2/jn240126f2-live/suite2p/plane0/
of the data.bin
is found in your Google drive? Google Colab might be finicky with pathnames.
What also happens when you remove the line ops['save_path0'] = path
? For this case, you don't need to explicitly set this since suite2p will just output things to the data_path
you provided.
Hi @chriski777 - thanks for following up!
In answer to your questions,
(1) yes, the parent directory of the data.bin is in my Google drive and I have given appropriate authorization to allow this cell to write into the corresponding Google drive folder
(2) in removing the ops['save_path0'] = path
line, I am unfortunately still getting the same error popping up
Hi @julia-napoli, sorry for the late response. This may be a more Google Colab specific issue than a suite2p issue. Have you tried running a similar notebook locally on your computer?
Hey @chriski777, no worries. I have not tried running it in a local jupyter notebook, however, this is quite unideal for us since we save large amounts of data, data organization spreadsheets, and analysis-related code all saved in our Google Drive, and want to be able to batch analyze our data while accessing and saving through Colab. Is it possible to help troubleshoot what might be going wrong with the Colab-related error we are seeing? If it's helpful for troubleshooting purposes on your end, I can try running it on a local notebook, though for us this is equally as much of a go-around as is running it through the GUI.
Hmm, I see. Could you try running with keep_movie_raw
set to False? Also, have you been able to get the colab notebook working when using the default settings for suite2p?
Hey @chriski777, thanks for giving me some more things to try! I just changed the keep_movie_raw
to False, and got the same data.bin
related error again, unfortunately. But, in re-trying to run the code using all the default suite2p settings through colab I received a new error, saying that there is "no space left on device" to save some of the outputs to our Google Drive. The weird thing, however, is that we have plenty of space on our Google Drive where this is trying to be saved, and have had no other issues saving files from other notebooks into the Drive -- which, leads me to think that this might be a suite2p specific error that is causing this.
Thanks for the update! This error now leads me to believe that this is a Google Colab-specific issue.
This StackOverflow post indicates that the disk space in google drive is not the same as the disk space in Google Colab. I'm not sure if there is a way to adjust the disk space available when using Google Colab even if the directory you're saving to is in your Google Drive. Generally, we'd not recommend having your suite2p workflow on Google Colab as you run into a lot of issues of this nature (e.g., Google Colab might have limited space because it might be caching files even if you don't explicitly tell it to). Instead, I'd recommend setting up a jupyter notebook on a local machine and trying to run your analysis scripts on that machine.
Another thing you could do is try running suite2p with default settings on a much smaller version of the dataset you're using. My guess is that you're running into this data.bin not being saved and space issue due to the space constraints imposed in Google Colab.
Describe the issue:
When trying to run suite2p registration, roi detection, classification, etc. on my 2-photon imaging data through Google Colab, suite2p will run through registration and try to save the corresponding files into the folder on my Google Drive, but will not be able to proceed past registration due to it saying there is no directory of the 'data.bin' file which it is supposed to be creating. This is not an issue of having the permission to save or write the file in the drive as I have given it access and it is able to make the 'suite2p' and 'plane0' folders, but not this 'data.bin' file. This is an issue with all of my 2-photon files, not just one of them -- and furthermore, when running these same data files through the GUI locally on my device there is no issue with saving the output files. Please help !!! Thank you
Reproduce the code example:
Error message:
Version information:
suite2p v0.14.3
Context for the issue:
I am unable to run my 2-photon imaging data through the registration pipeline through Google Colab due to this issue - only allowing me to run the data through the GUI locally on a computer instead. This does not allow for high-throughput processing of the data and specific and accurate tailoring of the suite2p parameters on a per 2p file basis. Please help!! Thanks so much