matplotlib-users Mailing List for matplotlib (Page 8)

This seems to be related to the bug reported by Eric Emsellem. If I do 
an imshow of an image with aspect='preserve' and activate the 'zoom to 
rectangle' function, the zoomed portion of the image is offset from the 
portion I outline with the cursor.

Stephen Walton wrote:
> second would be a windowed, scrollable view into an image which is 
> larger than the physical display.
Actually, imshow seems almost to do this. I did
imshow(imdata,interpolation='nearest')
where imdata was a 1024 square image. Zooming and panning _seems_ to 
show the full resolution image with individual pixels visible at high 
zooms. Is this right?

John Hunter wrote:
> Stephen> [...] ability to load multiple aligned images and blink between
> Stephen> them.
>
>With the new keypress event handling in matplotlib-0.70, and the
>cleanup to make sure the visible property is respected, this is pretty
>easy.
> 
>
You're right, thanks for the example code!
>What's the second item on the list :-)
> 
>
Well, since you asked, and Todd originally mentioned a DS9 replacement: 
second would be a windowed, scrollable view into an image which is 
larger than the physical display. I have 2K square cameras at my 
observatory, and HST ACS images are 4K square; both are quite a bit 
larger than any display I'm likely to be able to afford in the 
forseeable future.
Third item, and this will be a lot harder, is display and readout of 
FITS WCS information on the screen.
Acronym glossary:
HST--Hubble Space Telescope
ACS--Advanced Camera for Surveys
FITS--Flexible Image Transport System, the default format for 
astronomical images (http://fits.gsfc.nasa.gov)
WCS--World Coordinate System, a standard for embedding information for 
mapping pixel to physical coordinates in the FITS image header

It's a bug in the contour function. 
In axes.py, in function 'contour', put the line 
y, x = indices((jmax,imax), 'd')
in a condition, for example:
if x == None and y == None:
 y, x = indices((jmax,imax), 'd')
A permanent fix will go in CVS next week.
Nadia Dencheva
---- Original message ----
>Date: 2005年1月01日 08:05:12 -0700
>From: Jeff Whitaker <js...@fa...> 
>Subject: [Matplotlib-users] contour question 
>To: "'matplotlib-users'" <mat...@li...>
>
>Hi all:
>
>I was experimenting with the contour demo and discovered that
the x and 
>y keyword arguments don't behave like I expect them to (i.e.
they don't 
>behave as they do in pcolor).
>
>For example:
>
>from pylab import *
>delta = 0.025
>x = y = arange(-3.0, 3.0, delta)
>X, Y = meshgrid(x, y)
>Z1 = bivariate_normal(X, Y, 1.0, 1.0, 0.0, 0.0)
>Z2 = bivariate_normal(X, Y, 1.5, 0.5, 1, 1)
>#levels, colls = contour(Z2-Z1, x=X,y=Y,levels=6,
># linewidths=arange(.5, 4, .5),
># colors=('r', 'green', 'blue', (1,1,0), 
>'#afeeee', 0.5),
># origin='lower')
>pcolor(X,Y,Z2-Z1,shading='flat')
>show()
>
>plots the data with the x and y axes going from -3 to +3. 
Uncommenting 
>the contour call, the axes then are the same as the
dimensions of the Z 
>array, regardless of whether the x=X, y=Y keyword args are
given. In 
>other words, contour seems to ignore the x,y keywords. Am I
missing 
>something?
>
>-Jeff
>
>-- 
>Jeffrey S. Whitaker Phone : (30the3)497-6313
>NOAA/OAR/CDC R/CDC1 FAX : (303)497-6449
>325 Broadway Web : http://www.cdc.noaa.gov/~jsw
>Boulder, CO, USA 80305-3328 Office: Skaggs Research Cntr 1D-124
>
>
>
>-------------------------------------------------------
>The SF.Net email is sponsored by: Beat the post-holiday blues
>Get a FREE limited edition SourceForge.net t-shirt from
ThinkGeek.
>It's fun and FREE -- well,
almost....http://www.thinkgeek.com/sfshirt
>_______________________________________________
>Matplotlib-users mailing list
>Mat...@li...
>https://lists.sourceforge.net/lists/listinfo/matplotlib-users

I'm taking off this afternoon for a vacation in sunny Brazil! So I
may not be as responsive around here as I sometimes am, though I will
be occasionally checking my email.
Hold down the fort, and I'll think warmly of all of you who may be
stuck in the northern hemisphere :-)
JDH

Hi all:
I was experimenting with the contour demo and discovered that the x and 
y keyword arguments don't behave like I expect them to (i.e. they don't 
behave as they do in pcolor).
For example:
from pylab import *
delta = 0.025
x = y = arange(-3.0, 3.0, delta)
X, Y = meshgrid(x, y)
Z1 = bivariate_normal(X, Y, 1.0, 1.0, 0.0, 0.0)
Z2 = bivariate_normal(X, Y, 1.5, 0.5, 1, 1)
#levels, colls = contour(Z2-Z1, x=X,y=Y,levels=6,
# linewidths=arange(.5, 4, .5),
# colors=('r', 'green', 'blue', (1,1,0), 
'#afeeee', 0.5),
# origin='lower')
pcolor(X,Y,Z2-Z1,shading='flat')
show()
plots the data with the x and y axes going from -3 to +3. Uncommenting 
the contour call, the axes then are the same as the dimensions of the Z 
array, regardless of whether the x=X, y=Y keyword args are given. In 
other words, contour seems to ignore the x,y keywords. Am I missing 
something?
-Jeff
-- 
Jeffrey S. Whitaker Phone : (30the3)497-6313
NOAA/OAR/CDC R/CDC1 FAX : (303)497-6449
325 Broadway Web : http://www.cdc.noaa.gov/~jsw
Boulder, CO, USA 80305-3328 Office: Skaggs Research Cntr 1D-124