For import to work, do the movies need to be located under the same directory tree as the project dirs?
I just tried importing the same file from 3 different locations:
FSx: /fsx/movie.tif
S3: /mymountedS3bucket/movie.tif
scratch partition: /scratch/movie.tif
I cloned the movie import job so the parameters are identical.
File permissions + ownership are identical.
My workspace folders are created under /fsx
CryoSPARC loads the /fsx/movie.tif fine.
With the file on S3 or on /scratch, it throws the error:
Traceback (most recent call last):
File "cryosparc_worker/cryosparc_compute/run.py", line 84, in cryosparc_compute.run.main
File "/shared/cryosparc/cryosparc_worker/cryosparc_compute/jobs/imports/run.py", line 585, in run_import_movies_or_micrographs
assert len(all_abs_paths) > 0, "No files match!"
AssertionError: No files match!
I cloned the movie import job so the parameters are identical.
identical except for the path to the movie! The job log shows the full path of the file it is trying to import and I double-check that it is correct in all 3 instances.
Please can somebody point me to a reference if my question is trivial? I have searched and tested for 2 days now and getting nowhere.
Here is the job.log with the error and the command that shows that the file cryosparc cannot open actually exists and is readable by the user running cryosparc:
imports.run cryosparc_compute.jobs.jobregister
TIFFOpen: /mnt/rawdata/21feb08b_gs_uw/21feb08b_00004sq_00002hl_00003en.frames.tif: No such file or directory.
***************************************************************
**** handle exception rc
set status to failed
========= main process now complete.
========= monitor process now complete.
The file cryoSPARC is failing to open exists and is readable by the cryosparc user:
The output from your “ls -l” command shows the file is owned by root, but with r-x permissions that should allow all users to read the file. Are you sure permissions are also set correctly for the /mnt/rawdata/21feb08b_gs_uw/ and /mnt/rawdata/ folders?
If not a problem with permissions, perhaps the file system or mount type can have an effect? Not something I’ve encountered, so I’m just guessing here.