Ah yes, I forget :/ I was focused on images as being "pure" things that
should be displayed, and forgot about the image processing angle.
So would the solution be a keyword argument that tells imshow/BboxImage and
friends not to interpolate when at native resolution, which is set to the
current b
On Thu, Oct 13, 2011 at 10:06 AM, Daniel Hyams wrote:
> Isn't the purpose of interpolation to handle situations where the image is
> being displayed at a different size than its native resolution? It seems
Not solely, it can also be used to do local average of noisy images to
get a smoother vie
>
>
> imshow() does take an "interpolation" kwarg, where you can specify
> "nearest" for pre v1.1.0 versions and "none" (not None) in the recent
> release. "nearest" would be close to what you want, while "none" is exactly
> what you want.
>
> Personally, I don't think it would be a good idea to a
On Thursday, October 13, 2011, Daniel Hyams wrote:
> I was playing around with images.BboxImage, and found that if I displayed,
say a 100x100 image at its native resolution (exactly 100x100 pixels on the
plotting window), it was blurred. This is because of the interpolation
jumping in and interpo
I was playing around with images.BboxImage, and found that if I displayed,
say a 100x100 image at its native resolution (exactly 100x100 pixels on the
plotting window), it was blurred. This is because of the interpolation
jumping in and interpolating when it is not needed.
This might not be the b
