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

Make SCIFIO First ImageIO if present #3

Open
hinerm opened this issue Jul 1, 2013 · 4 comments
Open

Make SCIFIO First ImageIO if present #3

hinerm opened this issue Jul 1, 2013 · 4 comments
Milestone

Comments

@hinerm
Copy link
Member

hinerm commented Jul 1, 2013

If ITK already has an ImageIO that covers the same format as SCIFIO, it is queried first. But the data isn't guaranteed properly formatted for the SCIFIO writer. It would be nice to ensure that SCIFIO Writers are only invoked if given a SCIFIO ImageIO.. and one way to do that would be to just always make SCIFIO ImageIO the top choice.

@ghost ghost assigned hinerm Jul 1, 2013
@ctrueden
Copy link
Member

ctrueden commented Jul 1, 2013

My understanding is that reordering the discovered ImageIO handlers is not currently possible.

@hinerm
Copy link
Member Author

hinerm commented Jul 2, 2013

Then we could add a check in the ImageIO::CanWrite method that verifies the image was read with the SCIFIOImageIO... or figure out what's actually organized differently between the native ITK imageIOs and SCIFIOImageIO and translate or fix it on the SCIFIO side..

@ctrueden
Copy link
Member

Sounds good! The heuristic for "fixing" data which was generated from a source other than the SCIFIOImageIO will be limited, but we can do it on a best effort basis.

@ctrueden
Copy link
Member

Took me a while to dig up the supporting reference for my claim, but here it is: http://www.itk.org/pipermail/insight-users/2012-July/045252.html.

@hinerm hinerm added this to the m1 milestone Mar 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants