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

tiff -> mrmatrix? #72

Open
mccalluc opened this issue Apr 22, 2019 · 0 comments
Open

tiff -> mrmatrix? #72

mccalluc opened this issue Apr 22, 2019 · 0 comments
Assignees
Labels

Comments

@mccalluc
Copy link
Contributor

mccalluc commented Apr 22, 2019

It's on our plate to be able to handle tiff files. I do remember your wariness about adding support for more matrix forms beyond TSV but...

  • For our audience, we want to be able to say that it can be handled out of the box.
  • Big tiffs could get very, very, big if translated into an intermediate TSV
  • Getting the details of the tiling right is finicky... Now that it's done, I feel like the TSV parser itself should really just parse to a numpy array, and then do the same thing for tiffs with this: https://pypi.org/project/tifffile/

If this is going to happen, would you rather the work be done in clodius, or should there be a new clodius-imaging where it would go?

Also, just a gut check: You do feel confident that we're not getting too far into wheel reinvention here? I think there's an alternate route, where we work on the client side to handle a wider range of image tiling formats.

Would a DAG diagram of filetypes -> tiletypes -> tracktypes be useful?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants