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

Feature requests for data loader #87

Open
ngreenwald opened this issue May 22, 2020 · 1 comment
Open

Feature requests for data loader #87

ngreenwald opened this issue May 22, 2020 · 1 comment

Comments

@ngreenwald
Copy link
Collaborator

Right now, if you specify two different channels, the data loader will load them serially into the same array, so that it looks like you have 6 FOVs of the same channel, when in fact you have 3 FOVs, each with two channels.

I know you had talked about putting some SQL like logic in place to specify combinations of markers, I'm not sure if the plan is to add that to the data loader itself or as an internal post-processing step once the images have been loaded.

A couple of additional things that would be nice to have, but not mission critical, to improve the data loader

  1. The data loader doesn't read .tiff files, only .tif files
  2. It would be great to check if the specified folder is empty: right now it fails with pd.concat error.
@ngreenwald
Copy link
Collaborator Author

ngreenwald commented Jun 7, 2020

If we have a folder of 10 images, we want to be able to categorize them, take only a subset for a certain job, etc etc. To enable this, the data loader will need to return the filenames of the images that it has loaded, whereas currently it just returns the path to the folder itself.

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

1 participant