-
Notifications
You must be signed in to change notification settings - Fork 9
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
loadImages Subscript Error #93
Comments
Hmm, did you try executing the function on the |
No, but I retried with Error in .valid.loadImage.input(x, pattern, single_channel, name) :
The files are of type other than 'jpeg', 'tiff', 'png' or different file types are mixed. The function is flummoxed by a single text file in the same folder as the various TIFF files.
If I specify
All imaging mass cytometry data sets generated in our university seem to have this structure returned to the customer. |
I think when your team supplied example data in the past there was no TXT file included. The function assumes that only single channel files of the same type are included per folder. The pattern is only in place to select individual images, not channels. So could you try it again after excluding the TXT file from the individual folders and not supplying a |
Ah, O.K. Excluding the text file from each folder avoids the error. However, I subsequently see another error. > loadImages("IMC_oSCC_Angela2024/TMA01_OS/1_A3/", single_channel = TRUE, on_disk = TRUE, h5FilesPath = "/tmp/")
Error in .valid.loadImage.input(x, pattern, single_channel, name) :
Setting 'single_channel' requires 'x' to be a single path. It should be fine according to my reading. Previously, I showed that 1_A3 folder contains a set of TIFF files.
|
Is the path accesible from your working directory? Maybe provide the full path rather than the relative path. |
Oh, how strange. It works with an absolute path but not a relative path.
|
Better error handling would be nice to have.
I show the data set's directory structure.
It is not clear from loadImages.Rd whether it does recursive search for file names matching the specified pattern or not.
The text was updated successfully, but these errors were encountered: