matplotlib-users Mailing List for matplotlib

I couldn't put an exact date on when John began matplotlib, but its 
sourceforge repository was registered in June of 2003. Python 2.2 was 
the latest version available. Microsoft Windows XP was on the shelves, 
Mac OS X was new to the scene, and Linux had yet to be made easy by the 
likes of Ubuntu and Fedora. Facebook, Twitter and the smartphone 
weren't yet available. And the idea of richly interactive and 
productive applications running in the cloud was still considered 
crazy. A decade is a long time for an open source project, and it's a 
testament to John's hard work and keen decision-making that matplotlib 
has thrived for so long and grown into such a large community of smart 
and talented users and developers. Bravo, John.
To remain relevant in its second decade, matplotlib is being pulled 
simultaneously in two directions. On the one hand, to handle larger and 
more complex data, it needs to get closer to the hardware to make better 
use of GPUs and multicore CPUs. On the other hand, it needs to become a 
first-class member of the most important GUI of our time, the web 
browser, and to do so without sacrificing any of the power and 
flexibility it gets from being a Python library. Challenging stuff, but 
not unattainable given the enormous brain trust we've got here.
Procedurally, one thing I've been feeling rather acutely lately is that 
the firehose of github issues is not always the best way to track larger 
changes. I'd like to propose that we set up an informal system of 
"Matplotlib Enhancement Proposals" (MEPs) to manage larger changes to 
matplotlib that might cut across a number of different subsystems. 
Numpy puts these in their source code repository, but we may just want 
to use the github wiki to make it even easier for non-developers to 
contribute ideas. I'm not envisioning anything super formal here -- 
just something to keep track of the larger goals that won't get lost 
among hundreds of smaller issues. Details can be discussed here (I'd 
love suggestions from other projects) and I'll set something up soon. 
I'm sure we all have our own pet projects we'd like to do "time willing" 
and I look forward to discussing and making headway on some of those.
And back to the immediate future: we've got a release to get out: the 
first release to support Python 3.x. Exciting times. Details to follow 
in another e-mail thread.
John, thanks again for the honor and I hope I can follow your example of 
leadership. They are big shoes to fill.
Mike
On 08/02/2012 05:25 PM, John Hunter wrote:
> It is a great honor for me to announce that Michael Droettboom has
> agreed to take on the role of lead developer of matplotlib. Since
> Michael joined the project in 2007, he has been responsible for much
> of the code that brought matplotlib from being an excellent tool to a
> world class one. No one in the world understands the code from the
> inside out like he does, and many of his contributions, while often
> unseen at the surface, have laid the foundation for matplotlib to
> reach further into the wild and wonderful things it can now do.
>
> To name a few of his contributions: generic, optimized caching
> transformations; dramatic backend simplification and rationalization;
> countless optimizations; implementation of Knuth mathtex layouts;
> python3 support, and dolphins! I like to tell people Michael codes
> with the force of ten men, and he's an incredible asset to our team.
>
> My role has been significantly diminished of late -- although I have
> been the nominal lead developer, in practice I have been a release
> manager. Unfortunately, I need to take some time to focus on family
> health issues, but will continue to follow development and make
> contributions as I can. We'll be looking for a release manager soon,
> and if you are interested in stepping up, we'll welcome the effort.
> We have a wonderful distributed development team using github pull
> requests, and the line between core developers, project leaders and
> plain-ole contributers is blurry. But I think it helps to have
> someone thinking about the project as a whole, who is willing and able
> to make decisions when necessary, and no one is better suited to doing
> this than Michael.
>
> I also extend my heartfelt thanks to Perry Greenfield and STScI. They
> have been supporting matplotlib since 2004 with ideas, code and
> developer resources. They employ Michael currently, and are part of
> the reason why he is able to take on the leadership of this large
> project.
>
> Michael, many thanks.
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

On Thursday, August 2, 2012, surfcast23 wrote:
>
>
>
> surfcast23 wrote:
> >
> > In the documentation it says that Axes3D.plot_wireframe(X, Y, Z, *args,
> > **kwargs) takes 2D arrays as the first two arguments. Do the arrays have
> > to have the same size dimensions?
> >
> >
>
> Any one know?
Working from memory, the first two have to at least be "broadcastable" into
the shape of Z. But absolutely, if x, y, and z are 2d, they have to be the
same shape. It makes no sense otherwise.
Cheers!
Ben Root

Hello everyone-
I'm a new Python/Matplotlib user, but I have quite a bit of plotting
experience with octave/matlab and gnuplot. So, I apologize in advance if my
python style is terrible and if I give you all the wrong information!
I'm having a problem saving figures that contain images as eps files when
my x-axis is a date/time axis. The trouble is that in the resulting eps
file, the image data is shifted relative to the axis. I've attached two
images as an example. In the .png file the alignment is correct and in the
eps file it's not. The png is also nearly identical to what I get when I
plot to the screen. The script I wrote to generate these plots is at the
end of this message.
It's worth noting that the two output images are identical if the x-axis is
simply numerical and not a time series.
I'm using python 2.7.3 and Matplotlib 1.1.0
Some Google searches dug up this old thread, however, the shift that I'm
experiencing seems to be much greater, so I don't know if it's related:
http://old.nabble.com/Saving-as-eps-file-shifts-image--td29232680.html
Can anyone help me solve this?
Thanks in advance,
--Chad
Here is a minimal script that I used to generate these plots:
import matplotlib.pyplot as plt
import matplotlib.dates as dts
from matplotlib.colors import LogNorm
imgData = [[1.0/x + 1.0/y for x in range(1,100)] for y in range(1,100)]
tMin=dts.epoch2num(1343947266)
tMax=dts.epoch2num(1343947266+100)
axImg=plt.subplot(111)
axImg.imshow(imgData, norm=LogNorm(),extent=(tMin,tMax,1,100),\
 interpolation='none', origin="upper")
axImg.xaxis_date()
axImg.set_aspect('auto')
plt.savefig("imageshift.png")
plt.savefig("imageshift.eps")

surfcast23 wrote:
> 
> In the documentation it says that Axes3D.plot_wireframe(X, Y, Z, *args,
> **kwargs) takes 2D arrays as the first two arguments. Do the arrays have
> to have the same size dimensions? 
> 
> 
Any one know?
-- 
View this message in context: http://old.nabble.com/Size-of-array-elements-when-using-Axes3D.plot_wireframe%28X%2C-Y%2C-Z%2C-*args%2C-**kwargs%29-tp34243823p34248559.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Dear Colleagues,
the SIAM CSE13 conference will be held next year in Boston, and this is a
conference that is well suited for much of the type of work that goes on in
the open source scientific Python development community (and Julia). The
conference is co-chaired by Hans-Petter Langtangen, well known around these
parts for his several books on scientific computing with Python and for
having led a campus-wide adoption of Python as the core computational
foundation across the University of Oslo. I am also on the program
committee, as well as Randy LeVeque and other Python-friendly folks.
An excellent way to participate is to organize a one- or two-part
minisymposium on a specific topic with a group of related speakers
(instructions at http://www.siam.org/meetings/cse13/submissions.php).
Please note that the MS deadline is fast approaching: August 13, 2012.
If you have any further questions, don't hesitate to contact me or one of
the other organizers if you feel they can address your concerns more
directly:
"Fernando Perez" <Fer...@be...>
"Randy LeVeque" <rj...@am...> (Reproducible research track)
"Hans Petter Langtangen" <hp...@si...> (Conference co-chair)
"Karen Willcox" <kwi...@mi...> (conference chair)
---------- Forwarded message ----------
From: Karen Willcox <kwi...@mi...>
Date: Tue, Jul 24, 2012 at 6:08 AM
Subject: [SIAM-CSE] SIAM Conference on Computational Science & Engineering
Submission Deadlines Approaching!
To: SIA...@si...
*SIAM Conference on Computational Science & Engineering (CSE13)*
February 25-March 1, 2013
The Westin Boston Waterfront, Boston, Massachusetts, USA****
** **
SUBMISSION DEADLINES ARE APPROACHING!****
August 13, 2012: Minisymposium proposals
September 10, 2012: Abstracts for contributed and minisymposium speakers****
Visit http://www.siam.org/meetings/cse13/submissions.php to submit.****
** **
Twitter hashtag: #SIAMcse13****
** **
For more information about the conference, visit *
http://www.siam.org/meetings/cse13/* or contact SIAM Conference Department
at mee...@si....****
-- 
Karen Willcox
Professor and Associate Department Head
Department of Aeronautics and Astronautics, MIT
http://acdl.mit.edu/willcox.html
_______________________________________________
SIAM-CSE mailing list
To post messages to the list please send them to: SIA...@si...
http://lists.siam.org/mailman/listinfo/siam-cse

It is a great honor for me to announce that Michael Droettboom has
agreed to take on the role of lead developer of matplotlib. Since
Michael joined the project in 2007, he has been responsible for much
of the code that brought matplotlib from being an excellent tool to a
world class one. No one in the world understands the code from the
inside out like he does, and many of his contributions, while often
unseen at the surface, have laid the foundation for matplotlib to
reach further into the wild and wonderful things it can now do.
To name a few of his contributions: generic, optimized caching
transformations; dramatic backend simplification and rationalization;
countless optimizations; implementation of Knuth mathtex layouts;
python3 support, and dolphins! I like to tell people Michael codes
with the force of ten men, and he's an incredible asset to our team.
My role has been significantly diminished of late -- although I have
been the nominal lead developer, in practice I have been a release
manager. Unfortunately, I need to take some time to focus on family
health issues, but will continue to follow development and make
contributions as I can. We'll be looking for a release manager soon,
and if you are interested in stepping up, we'll welcome the effort.
We have a wonderful distributed development team using github pull
requests, and the line between core developers, project leaders and
plain-ole contributers is blurry. But I think it helps to have
someone thinking about the project as a whole, who is willing and able
to make decisions when necessary, and no one is better suited to doing
this than Michael.
I also extend my heartfelt thanks to Perry Greenfield and STScI. They
have been supporting matplotlib since 2004 with ideas, code and
developer resources. They employ Michael currently, and are part of
the reason why he is able to take on the leadership of this large
project.
Michael, many thanks.

On 8/1/12 4:09 PM, Scott Henderson wrote:
> Hi Jeff,
>
> I'm continuing to enjoy using basemap, but have a question about the shaded relief background. I frequently use greyscale shaded relief on the continents, but blue or white for the oceans. the shadedrelief() function is really convenient, but it includes shading for the oceans. Is there a way to afterwards just shade oceans? I've included my modified shaded_relief function in this email that uses some of the other natural earth products in case you need to see it.
>
> Example:
> bmap.drawmapboundary(fill_color='aqua')
> bmap.shadedrelief()
>
> Or something like:
> bmap.shadedrelief()
> **bmap.filloceans('aqua')
>
>
> Thanks,
> Scott
Scott: You could overlay the shaded relief image on a land-sea mask, 
where the land part of the mask is transparent. Like this:
from mpl_toolkits.basemap import Basemap
import matplotlib.pyplot as plt
import numpy as np
bmap = Basemap(projection='ortho',lat_0=45,lon_0=-100,resolution='l')
bmap.drawmapboundary()
bmap.drawmeridians(np.arange(0,360,30))
bmap.drawparallels(np.arange(-90,90,30))
bmap.shadedrelief()
bmap.drawlsmask(ocean_color='aqua',land_color=(255,255,255,1))
plt.show()
>
> PS. is there a basemap mailing list I should send questions like this to?
No - just send questions to matplotlib-users (I've cc'ed the list)
-Jeff
>
>
> from PIL import Image
> from matplotlib.image import pil_to_array
>
> def shadedrelief_highres(self,style='hypsometric', region=(-75.0, -35.0, -65.0, -15.0),ax=None,scale=None,**kwargs):
> ''' can avoid Memory Error with warpimage() by pre-cutting high-res arrays with GDAL?
> region = (minLon, minLat, maxLon, maxLat)'''
> print 'NOTE: only set up for cyl coordinates with extent defined by region'
> basedir = '/Users/scotthenderson/data/natural_earth/'
> if style == 'hypsometric':
> path = os.path.join(basedir,'HYP_HR_SR_OB_DR.tif')
> elif style == 'natural':
> path = os.path.join(basedir,'NE1_HR_LC_SR_W_DR.tif')
> elif style == 'hillshade':
> path = os.path.join(basedir,'SR_HR.tif')
>
> outfile = os.path.join(basedir,'tmp.tif')
> if os.path.isfile(outfile): os.remove(outfile)
> os.system('gdalwarp -te {0} {1} {2} {3} {infile} {out}'.format(*region, infile=path, out=outfile))
>
> #copy only relevant commands from warpimage imshow() overrides colorbar for rgb or PIL arrays
> pilImage = Image.open(outfile)
> if scale is not None:
> w, h = pilImage.size
> width = int(np.round(w*scale))
> height = int(np.round(h*scale))
> pilImage = pilImage.resize((width,height),Image.ANTIALIAS)
> self._bm_rgba = pil_to_array(pilImage)
> # if pil_to_array returns a 2D array, it's a grayscale image.
> # create an RGB image, with R==G==B.
> if self._bm_rgba.ndim == 2:
> tmp = np.empty(self._bm_rgba.shape+(3,),np.uint8)
> for k in range(3):
> tmp[:,:,k] = self._bm_rgba
> self._bm_rgba = tmp
>
> im = self.imshow(self._bm_rgba, ax=ax, **kwargs)
> return im
-- 
Jeffrey S. Whitaker Phone : (303)497-6313
Meteorologist FAX : (303)497-6449
NOAA/OAR/PSD R/PSD1 Email : Jef...@no...
325 Broadway Office : Skaggs Research Cntr 1D-113
Boulder, CO, USA 80303-3328 Web : http://tinyurl.com/5telg

In the documentation it says that Axes3D.plot_wireframe(X, Y, Z, *args,
**kwargs) takes 2D arrays as the first two arguments. Do the arrays have to
have the same size dimensions? 
-- 
View this message in context: http://old.nabble.com/Size-of-array-elements-when-using-Axes3D.plot_wireframe%28X%2C-Y%2C-Z%2C-*args%2C-**kwargs%29-tp34243823p34243823.html
Sent from the matplotlib - users mailing list archive at Nabble.com.