Data limits incorrectly computed in Image Lookup Tables
The following behaviour observed in releases 2013.10 and 2014.05 on Debian testing (jessie):
For certain images the computation of the correct data limits fails. The data limits min/max text boxes display 0/0 where the values should range from -3000 to 2000. The slider for the min value goes to -1 and any manipulation of it effectively leads to a thresholding of the image at 0 intensity (or so it looks anyway). The other text boxes in the slider section just display 0. Manual setting of the data limits still works, and the sliders become usable again if they're set to sensible values.
Possible cause: The images were generated by warping of an image (for which the computation does not fail), so it could be that the NaNs introduced where the displacement field exceeds the image bounds invalidate the computation.