Check for apps where image must be 3D #1017
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Lestropie
added a commit
that referenced
this pull request
Jun 28, 2017
Although this is a reasonable check when performing image processing involving interpolation, it prevents loading such images in mrview, where they can in fact be displayed reasonably. Check was originally introduced in #1017.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cobbled this together while working on other things.
Simple warning system to prevent confusing errors / segmentation faults arising from feeding XxYx1xZ images into commands / scripts where there is no way that the command could possibly not either crash or produce an empty output.
Addresses part of what was raised in #1012. The import itself may need a more prominent warning.