|
From: Ethan G. <eth...@gm...> - 2012-09-07 18:16:14
|
On Sep 7, 2012, at 11:04 AM, Eric Firing wrote: > On 2012/09/07 4:00 AM, Benjamin Root wrote: >> >> >> On Fri, Sep 7, 2012 at 9:49 AM, Shahar Shani-Kadmiel >> <ka...@po... <mailto:ka...@po...>> wrote: >> >> On Sep 7, 2012, at 4:25 PM, Benjamin Root wrote: >> >>> >>> >>> On Fri, Sep 7, 2012 at 8:44 AM, Shahar Shani-Kadmiel >>> <ka...@po... <mailto:ka...@po...>> wrote: >>> > <snip> > Normalization has to handle all sorts of inputs--masked or not, all > sorts of numbers, scalar or array--and it is much easier to do this > efficiently if all these possibilities are reduced to a very few at the > start. Specifically, it needs to supply a copy of the input (so that > normalization doesn't change the original) in a floating point masked > array, using float32 if possible for space efficiency. It needs to keep > track of whether the input was a scalar, so that normalization can > return a scalar when given a scalar input. > > Eric Another option as I understand it is to pass in a 1D (greyscale) or 3d (color) array (where the 3rd dimension is RGB and optionally A) of type uint8(?). This array does not need to get normalized, it will be displayed as raw pixel values. I don't remember if you also have to specifically tell it not to normalize the data. But the easier answer for your case would probably be imshow(data[::10,::10]) which will take every 10th element in x and y thus reducing the size by a factor of 100 (depending on the size of your data you could use ::2 or ::50, etc) Ethan |