Re: [matplotlib-devel] basemap installation problem with mpl master

n Sat, Jul 6, 2013 at 11:04 AM, Jeff Whitaker <jsw...@fastmail.fm> wrote: Damon McDougall July 6, 2013 9:32 AM If I do a clean install of mpl master, and then of basemap, basemap lands in dist-packages/mpl_toolkits, as it always has.  But now it is not found--I can&

Re: [matplotlib-devel] basemap installation problem with mpl master

Damon McDougall July 6, 2013 9:32 AMIf I do a clean install of mpl master, and then of basemap, basemap lands in dist-packages/mpl_toolkits, as it always has.  But now it is not found--I can't import it.  It seems that now the *real* mpl_toolkits is cleverly hidden inside an egg

Re: [matplotlib-devel] basemap link broken on matplotlib.org page

On 9/12/12 7:49 PM, Michael Droettboom wrote: > I believe I've now fixed this. > > Mike Yep, it's good now. Thanks Michael. -Jeff > > On 09/12/2012 09:28 PM, Jeff Whitaker wrote: >> The link points to matplotlib.org/basemap (which doesn't exist), should

[matplotlib-devel] basemap link broken on matplotlib.org page

The link points to matplotlib.org/basemap (which doesn't exist), should be matplotlib.github.com/basemap. Either that, or matplotlib.org/basemap should redirect there. -Jeff -- Live Security Virtual Conference Exclusiv

Re: [matplotlib-devel] Bug in print_figure with bbox_inches='tight'? Plots in ipython notebook losing titles and labels...

? > I was just going to ask the same. And as Jeff Whitaker points out, > all x and y (longitude/latitude) labels also get clipped. > > I can understand not considering the position of arbitrarily laid out > text that a user could have put in a random location. From matplotlib&#x

Re: [matplotlib-devel] Bug in print_figure with bbox_inches='tight'? Plots in ipython notebook losing titles and labels...

On 1/29/12 8:42 AM, Benjamin Root wrote: On Sunday, January 29, 2012, Fernando Perez > wrote: > Hi all, > > in ipython for the qtconsole and notebook, we send inline figures using > > fig.canvas.print_figure(bytes_io, format=fmt, bbox_inches='tight') > > as seen he

Re: [matplotlib-devel] is basemap-1.0.1-examples.tar.gz corrupted?

On 9/2/11 1:33 AM, Sandro Tosi wrote: > Hello, > I'm trying to download basemap examples tarball from SF but it seems > to be corrupted - could you confirm/fix it? > > Thanks, Should be fixed now. -Jeff -- Why Cloud-Based

Re: [matplotlib-devel] Coverity defects in python-basemap

On 8/11/11 4:11 AM, Pavel Raiskup wrote: > Hi, > >> Coverity is an interesting product and I heard of it before on >> TheDailyWTF.com (in positive light, of course!). However, it appears >> that >> you were scanning an outdated version of our software. The current >> release >> version is v1.0.

Re: [matplotlib-devel] What's the status of the py3k branch?

On 2/26/11 5:30 AM, Michiel de Hoon wrote: >> In any case it appears that with the exception of Tkinter, it may take a >> long time before interactive mpl backends can be used with py3k. > The MacOSX backend has already been ported to Py3k (at least the C part of > it, which is the largest and mos

Re: [matplotlib-devel] git-svn matplotlib mirror

On 1/25/11 1:06 PM, Darren Dale wrote: > On Tue, Jan 25, 2011 at 1:31 PM, Pauli Virtanen wrote: >> Tue, 25 Jan 2011 12:19:37 -0500, Darren Dale wrote: >>> There is a potential problem converting the entire basemap history to >>> git. In svn commit 4418, trunk/toolkits had basemap and basemap-testi

Re: [matplotlib-devel] git-svn matplotlib mirror

On 1/24/11 7:11 AM, Darren Dale wrote: > On Mon, Jan 24, 2011 at 8:48 AM, John Hunter wrote: >> On Mon, Jan 24, 2011 at 7:18 AM, Jeff Whitaker wrote: >> >>> Regarding basemap, what do people recommend? Should I create a separate >>> github project for basem

Re: [matplotlib-devel] git-svn matplotlib mirror

t to me ASAP. > I think we are getting close. Here are the remaining commit authors > that do not have git commit information. Do we know how to reach some > of these folks directly to ask if they want to provide it? > > mdboom > mdehoon > jswhit jsw...@github.com Jeff Whitak

Re: [matplotlib-devel] Patch for Qt4 backend for IPython GUI

On 9/5/10 6:32 PM, Fernando Perez wrote: > Hi Jeff, > > On Sun, Sep 5, 2010 at 5:25 PM, Jeff Whitaker wrote: >> Fernando: That works, but it seems like I have to run show() to make the >> plot appear inline. draw() doesn't do it. Is this the expected behavior?

Re: [matplotlib-devel] Patch for Qt4 backend for IPython GUI

On 9/5/10 3:15 PM, Fernando Perez wrote: > Hi Jeff, > > On Sun, Sep 5, 2010 at 10:18 AM, Jeff Whitaker wrote: >> Fernando: I've got ipython-newkernal ipythonqt working on my mac - how do I >> tell it to switch between external plot windows and inline plots? External

Re: [matplotlib-devel] Patch for Qt4 backend for IPython GUI

On 8/30/10 1:21 AM, Fernando Perez wrote: > Hi Eric, > > On Sat, Aug 28, 2010 at 4:27 PM, Eric Firing wrote: >> Impressive--but I don't think I understand why one would want plots rendered >> inline rather than in separate windows. Fernando: I've got ipython-newkernal ipythonqt working on my m

[matplotlib-devel] macos x backend not functioning in trunk

I've started to see these errors today: TypeError: function takes exactly 3 arguments (4 given) Traceback (most recent call last): File "/Users/jwhitaker/.local/lib/python2.6/site-packages/matplotlib/artist.py", line 55, in draw_wrapper draw(artist, renderer, *args, **kwargs) File "

Re: [matplotlib-devel] [Matplotlib-users] Basemap r8403 and numpy 2.0

On 6/10/10 11:50 AM, Pierre GM wrote: > On Jun 10, 2010, at 1:30 PM, Christoph Gohlke wrote: > >> >> On 6/10/2010 10:14 AM, Pierre GM wrote: >> >>> On Jun 10, 2010, at 12:51 PM, Jeff Whitaker wrote: >>> >>>> On 6/10/

Re: [matplotlib-devel] [Matplotlib-users] Is there a way to link axes of imshow plots?

On 6/10/10 11:13 AM, Benjamin Root wrote: On Thu, Jun 10, 2010 at 11:56 AM, Jeff Whitaker <mailto:jsw...@fastmail.fm>> wrote: On 6/10/10 10:41 AM, Benjamin Root wrote: On Thu, Jun 10, 2010 at 11:05 AM, Jeff Whitaker mailto:jsw...@fastmail.fm>> wrote: On

Re: [matplotlib-devel] [Matplotlib-users] Basemap r8403 and numpy 2.0

On 6/10/10 11:14 AM, Pierre GM wrote: > On Jun 10, 2010, at 12:51 PM, Jeff Whitaker wrote: > >> On 6/10/10 10:40 AM, Pierre GM wrote: >> >>> All, >>> Sorry, it's been a while since I've been using Basemap. I was just trying >>>

Re: [matplotlib-devel] Basemap r8403 and numpy 2.0

On 6/10/10 10:40 AM, Pierre GM wrote: > All, > Sorry, it's been a while since I've been using Basemap. I was just trying to > update my local svn directory to r8403 and reinstall basemap, but an import > fail w/ the following message: > """ > Traceback (most recent call last): >File "", line

Re: [matplotlib-devel] duplicate draw operations in basemap?

Eric Firing wrote: > Jeff Whitaker wrote: >> Eric Firing wrote: >>> Jeff, >>> >>> Basemap methods like plot() include a "draw_if_interactive" command, >>> followed by a call to the set_axes_limits() method, which ends with >>> &g

Re: [matplotlib-devel] duplicate draw operations in basemap?

Eric Firing wrote: > Jeff, > > Basemap methods like plot() include a "draw_if_interactive" command, > followed by a call to the set_axes_limits() method, which ends with > > # force draw if in interactive mode. > if is_interactive(): > figManager = _pylab_helpers.Gc

Re: [matplotlib-devel] Elusive bug plotting masked arrays

On 3/19/10 11:10 AM, David J. Raymond wrote: I am trying to plot two 1-D masked arrays against each other in a line plot and an extraneous straight line appears on the plot. This phenomenon only occurs sporadically and with certain data sets. I have noticed a similar phenomenon with masked arro

Re: [matplotlib-devel] git migration

John Hunter wrote: > On Tue, Mar 2, 2010 at 11:41 PM, Eric Firing wrote: > >> Andrew Straw wrote: >> [...] >> >>> This is a good point. My preferred option is that we jettison all the >>> stuff that is not going to be shipped with MPL 1.0 from the git repo. >>> (More correctly - we build a

Re: [matplotlib-devel] missing projections

on't get it from the matplotlib svn trunk. Instead of svn co https://matplotlib.svn.sourceforge.net/svnroot/matplotlib/trunk/matplotlib matplotlib do svn co https://matplotlib.svn.sourceforge.net/svnroot/matplotlib/trunk/toolkits/basemap basemap -Jeff > > Jeff Whitaker wrote:

Re: [matplotlib-devel] missing projections

Phillip M. Feldman wrote: > Jeff Whitaker wrote: >> Phillip M. Feldman wrote: >>> Andrew Straw wrote: >>>> Jeff Whitaker wrote: >>>> >>>>> Dr. Phillip M. Feldman wrote: >>>>> >>>>>> Basemap offers

Re: [matplotlib-devel] with projection=aeqd, width has no effect

Dr. Phillip M. Feldman wrote: > When I generate a map with the aeqd projection, the width parameter has no > effect. This looks like a bug. > Philip: I don't see this. Here's an example, does this fail for you? lon_0=-105; lat_0=40 width=4000.e3 height=4000.e3 m =\ Basemap(resolution='c',pro

Re: [matplotlib-devel] missing projections

Phillip M. Feldman wrote: > Andrew Straw wrote: >> Jeff Whitaker wrote: >> >>> Dr. Phillip M. Feldman wrote: >>> >>>> Basemap offers many projections, but is missing two of the most >>>> useful ones: >>>> >

Re: [matplotlib-devel] missing projections

Dr. Phillip M. Feldman wrote: > Basemap offers many projections, but is missing two of the most useful ones: > > - For satellite applications, it would be helpful to have a "camera" > projection, i.e., a projection that shows the Earth as viewed from a > specified point in space. This would be a g

Re: [matplotlib-devel] griddata bug

James Conners wrote: > Hi, > > I did a quick search of the archives and didn't find anything so > here's a post of what I'm pretty sure is a bug in griddata of > matplotlib.mlab: > Matplotlib version: 0.99.1.1 > > > mlab.py: Line 2527 > > if hasattr(z,'mask'): > x = x.compress(z.mask == False

Re: [matplotlib-devel] error with basemap and pdf

Jouni K. Seppänen wrote: > Could somebody test that script with current trunk (rev. 7899)? I don't > have basemap installed, but I think my latest change might shake out the > bug. > > Jouni: That test script now crashes with: Traceback (most recent call last): File "testpdf.py", line 28, in

Re: [matplotlib-devel] Basemap.shiftgrid without cyclic point

Eric Bruning wrote: > I'm using basemap to plot a dataset* that has longitude values like so: > > lon = [0, 2, 4, ..., 356, 358] > > I'd like to use Basemap.shiftgrid to transform the longitudes and data > to the -180, 180 interval, but I get 'ValueError, cyclic point not > included' since 360 isn'

Re: [matplotlib-devel] Basemap.drawmapscale: units='m'

Stephane Raynaud wrote: > Hi Jeff, > > how about allowing units to be set as meters when calling > Basemap.drawmapscale ? > And maybe adding the keyword "format" for formatting numeric values. > That would be interesting when plotting maps with small area. > > Thanks. > > Stephane: I don't use

Re: [matplotlib-devel] Running basemap 0.99.4 on RHEL

didn't seem to > work with the version of geos that EPD uses. I built GEOS in a local > home directory. Do I need to build it in a global location (like > /usr/local)? > > --Mike Mike: Sounds like you need to modify LD_LIBRARY_PATH to add the directory where you inst

Re: [matplotlib-devel] Running basemap 0.99.4 on RHEL

Michael Hearne wrote: > I just built matplotlib and basemap from source on a RHEL system, with > EPD as my base Python installation. > > The build procedure for matplotlib was fairly straightforward, as was > basemap (once I read Jeff's documentation on installing). > > However, once I try to i

Re: [matplotlib-devel] Building matplotlib on os x

Ariel Rokem wrote: > Hi Jeff, > > >> import matplotlib >> matplotlib.__version__ >> >> >>> '0.98.5.2' >>> >>> >> Ariel: This tells me you really didn't install it, or you installed it in a >> different version of python than you are trying to import it with.

Re: [matplotlib-devel] Building matplotlib on os x

e one hand, it doesn't crash while building and installing. > On the other hand, it doesn't work. > We'll need more details on this one - a simple script that triggers it and what backend you're using, for starters. -Jeff > Cheers, > > Ariel > > On Thu, A

Re: [matplotlib-devel] Building matplotlib on os x

Ariel Rokem wrote: > Hi - that's interesting - I am actually on OS10.5. For some reason, > the MPL libraries get built under a directory called > "lib.macosx-10.3-fat-2.5" and the SDK set in the Python Makefile is > /Developer/SDKs/MacOSX10.4u.sdk, which is why you see these mentioned > in the outp

Re: [matplotlib-devel] Building matplotlib on os x

Michael Hearne wrote: > I apologize for cross-posting - I realized I probably shouldn't have > posted this on the user's list first... > > Hello - I am attempting to build matplotlib from source on os X, and > getting an error about a shared library being the wrong architecture. > The confus

Re: [matplotlib-devel] basemap not working with GEOS 3.1

Adam Mercer wrote: > On Tue, Jul 28, 2009 at 05:14, Jeff Whitaker wrote: > > >> Chris: This usually happens when you build mix different versions of >> geos, i.e. build with the 3.1 lib but the 2.2.3 headers, or link with >> the 3.1 shared lib and then have it pick

Re: [matplotlib-devel] basemap not working with GEOS 3.1

Chris Petrich wrote: > Hi, > > I get a Topology Exception with GEOS 3.1: > > import mpl_toolkits.basemap as bm > print "GEOS version: ", bm._geoslib.__geos_version__ > print "basemap version: ", bm.__version__ > > m = bm.Basemap(width=1200,height=800, \ > resolution='l',projecti

Re: [matplotlib-devel] Jagged plot in macosx backend

Michiel de Hoon wrote: > I've written a patch that fixes this bug; see > > https://sourceforge.net/tracker/?func=detail&atid=560722&aid=2508440&group_id=80706 > > --Michiel > Just commited your patch (SVN r6787) - thanks Michiel. -Jeff > > --- On Mon, 1/12/09, Tony Yu wrote: > > >> From: T

Re: [matplotlib-devel] Basemap inclusion of pupynere

Ryan May wrote: > Jeff Whitaker wrote: >> Ryan May wrote: >>> Jeff, >>> >>> Would it be a lot of work for basemap to use the system copy of >>> pupynere if it's installed, instead of installing its own copy? >>> (like what's alrea

Re: [matplotlib-devel] Basemap inclusion of pupynere

Ryan May wrote: > Jeff, > > Would it be a lot of work for basemap to use the system copy of pupynere if > it's > installed, instead of installing its own copy? (like what's already done for > dap > and httplib2) > > Ryan > > Ryan: The basemap version is modified to automatically unpack sca

Re: [matplotlib-devel] Basemap question for Jeff: different data directory?

Drain, Theodore R wrote: > Jeff, > Is it possible to install the basemap data into a different directory? > > I'm trying to set up a tool delivery layout for our users that allows me to > rapidly update packages that tend to change. We have a core set of software > that our code is built on and

Re: [matplotlib-devel] Bug in Basemap

Pierre GM wrote: > All (with a special hello to Jeff W.), > I'm running into a problem with the latest basemap (r6355), illustrated in > the > following. Looks like the resolution 'i' causes a TopologyException > > GEOS_ERROR: TopologyException: found non-noded intersection > between -42.7171 -2

Re: [matplotlib-devel] Basemap docs?

Ryan May wrote: > Jeff, > > I just noticed that the 0.99.1 tarball for Basemap does not include a > pdf of the docs, while 0.99 did. Was this intentional or just an > oversight? I only ask because it broke the gentoo option for installing > the docs. > > Ryan > > Ryan: That wasn't the re

Re: [matplotlib-devel] part of r5520 is bad for oceanography

Eric Firing wrote: > Jeff, > > http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/trunk/toolkits/basemap/lib/mpl_toolkits/basemap/__init__.py?r1=5520&r2=5534 > > Lines 2311 and 2312 in changeset 5520 have bitten me badly, and I think > they are ill-advised. They are based on the assumption t

Re: [matplotlib-devel] Any short plan for a new release (0.98.2 for real or 0.98.3)?

Christopher Barker wrote: > arrg! > > When am I going to learn not to click "send" until after I've read the > entire thread! > > Jeff Whitaker wrote: > >> John: I just contacted NCAR again, and it seems that they have >> relicensed the so

Re: [matplotlib-devel] Any short plan for a new release (0.98.2 for real or 0.98.3)?

John Hunter wrote: > On Fri, Jul 18, 2008 at 12:52 PM, Jeff Whitaker <[EMAIL PROTECTED]> wrote: > > >> What do you think? If it's OK I say we use the natgrid package in >> matplotlib, since it's more bulletproof than the scikits package (it passes >>

Re: [matplotlib-devel] Any short plan for a new release (0.98.2 for real or 0.98.3)?

Jeff Whitaker wrote: > John Hunter wrote: > >> On Fri, Jul 18, 2008 at 10:11 AM, Jeff Whitaker <[EMAIL PROTECTED]> wrote: >> >> >> >>> I'd like to see griddata functionality and Ryan May's wind barb patch in >>> 0.98.3

Re: [matplotlib-devel] Any short plan for a new release (0.98.2 for real or 0.98.3)?

John Hunter wrote: > On Fri, Jul 18, 2008 at 10:11 AM, Jeff Whitaker <[EMAIL PROTECTED]> wrote: > > >> I'd like to see griddata functionality and Ryan May's wind barb patch in >> 0.98.3. >> > > OK things seem to be moving pretty fast righ

Re: [matplotlib-devel] Any short plan for a new release (0.98.2 for real or 0.98.3)?

John Hunter wrote: > On Thu, Jul 17, 2008 at 7:48 AM, Sandro Tosi <[EMAIL PROTECTED]> wrote: > >> Hi All, >> I'd like to "resubmit" the request below: any new version to be >> released soon? in the process to generate the doc in Debian, something >> got fixed upstream, so a new release would be

Re: [matplotlib-devel] (Wind) Barbs

Ryan May wrote: Hi, I've got (what seems to me) a nice clean, self-contained implementation of wind barbs plots. I'd like to see if I can get this into matplotlib, as it would be very useful to the meteorology community. I've borrowed heavily from Quiver for rounding out rough edges (like

Re: [matplotlib-devel] Skew-T

Ryan May wrote: > (Sorry if this is a duplicate) > > Hi, > > I'm trying to make a Skew-T LogP plot, an important plot in meteorology, > using matplotlib (mainly to help convert people away from much more > horrible solutions). You can see one here: > http://www.rap.ucar.edu/weather/upper/oun.gi

Re: [matplotlib-devel] date2num/num2date and ordinal date

Eric Firing wrote: > Stephane Raynaud wrote: > >> Hi, >> >> date2num and num2date perform conversion between datetime and 'days >> since 0001-01-01' and vice versa. >> For such task, they strictly use ordinal dates for their numeric days, >> 1 meaning '0001-01-01' by definition. >> Thus, date2n

Re: [matplotlib-devel] rotate_vector major bug in basemap

Eric Firing wrote: > Jeff, > > The problem is not in basemap, it is numpy. Basemap is doing the > right thing, using the astype method to ensure a copy--but that is not > what the method is actually doing in this case. I filed a numpy > ticket (788). I took a quick look at the numpy code but

Re: [matplotlib-devel] new release?

gt; > Cheers, > Mike Mike: The egg issue required renaming matplotlib.toolkits to mpl_toolkits. We discussed this at the time, and decided it would cause too much code breakage to be included in 0.91.x. I'm OK with a 0.98 beta, but that's more work for Charlie to make extra installers and egg

[matplotlib-devel] new release?

What do people think of releasing 0.98 after numpy 1.1 is released this weekend? The main reason I'd like to do this (instead of releasing another 0.91.x) is that the toolkits are broken in 0.91 - if matplotlib is installed as an egg basemap (or any other toolkit) cannot be installed. -Jeff

Re: [matplotlib-devel] basemap drawcoastlines: suppress legend label

Eric Firing wrote: > Jeff, > > When putting a legend on a basemap plot, I find that the legend command > picks up the coastline line collection and gives it an uninformative > label. I suspect this is rarely what one wants. Two suggestions: > > 1) In drawcoastlines, use "coastlines.set_label('_

Re: [matplotlib-devel] Basemap.resolution

Stephane Raynaud wrote: > Hi, > > how about adding the possibility to give a Basemap instance to the > resolution parameter when creating a new Basemap object, and to > directly set some of its attributes (like coastsegs, cntrysegs, etc) > thus preventing from computing them? > It may be interestin

Re: [matplotlib-devel] resurrecting namespace packages

Eric Firing wrote: > Jeff Whitaker wrote: >> Ted Drain wrote: >>> Could someone point me at a discussion/article that explains the >>> need for namespace packages? I'm sure there is some good reason for >>> it but on the surface it seems very conf

Re: [matplotlib-devel] resurrecting namespace packages

empty. So in the case of basemap, this means that the import has changed from from matplotlib.toolkits.basemap import Basemap to from mpl_toolkits.basemap import Basemap. We don't actually need to stuff things into an api.py file. -Jeff > > At 08:11 AM 1/10/2008, Jeff Whitaker wr

Re: [matplotlib-devel] resurrecting namespace packages

Andrew Straw wrote: > Great -- hopefully that saved you some API re-arrangement pain. No > problem on shuffling mpl_sizer around -- please go ahead do it if you > have time. > > -Andrew > > Jeff Whitaker wrote: >> Andrew: Thanks, you've convinced me. Is it O

Re: [matplotlib-devel] resurrecting namespace packages

Andrew Straw wrote: > Jeff Whitaker wrote: > >> Darren Dale wrote: >> >>> On Wednesday 09 January 2008 7:01:14 pm Jeff Whitaker wrote: >>> >>> >>>> Andrew Straw wrote: >>>> >>>> >&g

Re: [matplotlib-devel] resurrecting namespace packages

Darren Dale wrote: > On Wednesday 09 January 2008 7:01:14 pm Jeff Whitaker wrote: > >> Andrew Straw wrote: >> >>> As the author of the only other known MPL toolkit (at least in the MPL >>> tree), I'm happy with the idea of using a namespace packag

Re: [matplotlib-devel] resurrecting namespace packages

d now in several projects. The lib directory is not necessary, you would just change the package_dirs = {'':'lib'} line in setup.py accordingly. -Jeff > > > Jeff Whitaker wrote: > >> Now that the transforms branch has merged wit

Re: [matplotlib-devel] resurrecting namespace packages

ut I question is whether it's necessary to have the >> "lib" directory -- it seems entirely redundant. I'm fine with either >> way, though. >> >> -Andrew >> >> Jeff Whitaker wrote: >> >>> Now that the transforms branch has

[matplotlib-devel] resurrecting namespace packages

Now that the transforms branch has merged with the trunk, I'd like to resurrect namespace packages so that toolkits will work again when matplotlib is installed as an egg. As was discussed in a previous thread, all __init__.py files in the toolkit hierarchy must be empty (aside declare_namesp

Re: [matplotlib-devel] API change in transforms branch

ion. This comes into play when setting the position of colorbar axes, since you want them to line up with the axes of the image. -Jeff > > Jeff Whitaker wrote: >> >> Mike: I see that ax.apply_aspect now has a 'position' argument. To >> maintain backward compa

Re: [matplotlib-devel] API change in transforms branch

m your code, is anything different? > > Cheers, > Mike Mike: Perhaps I am just misusing it - I thought you had to call it for the set_aspect to take effect. I didn't realize it was called from draw(). I'll try removing it and re-run all the basemap examples to see if there

[matplotlib-devel] API change in transforms branch

Mike: I see that ax.apply_aspect now has a 'position' argument. To maintain backward compatibility, may I suggest that you make it a kwarg, with default value None, and then add if position is None: position = self._originalPosition at the top of apply_aspect? -Jeff -- Jeffrey S. Whita

[matplotlib-devel] pcolor bug in transforms branch

Mike: shading='faceted' doesn't work (no edges are drawn around the polygons). -Jeff -- Jeffrey S. Whitaker Phone : (303)497-6313 NOAA/OAR/CDC R/PSD1FAX : (303)497-6449 325 BroadwayBoulder, CO, USA 80305-3328 -

Re: [matplotlib-devel] pcolormesh in transforms branch

Michael Droettboom wrote: > The transforms branch has seen very little outside of the matplotlib > examples, so it's good to find all of these error cases. Fixed in r4569. > > Cheers, > Mike > >> Michael: And one more - contourf will die if you there are no >> contours at the requested levels.

Re: [matplotlib-devel] pcolormesh in transforms branch

Michael Droettboom wrote: > Jeff Whitaker wrote: >> John Hunter wrote: >>> On Dec 3, 2007 2:08 PM, Jeff Whitaker <[EMAIL PROTECTED]> wrote: >>> >>> >>>> try: >>>> l,b,w,h = ax.get_position() >>>> except: >&

Re: [matplotlib-devel] pcolormesh in transforms branch

John Hunter wrote: > On Dec 3, 2007 2:08 PM, Jeff Whitaker <[EMAIL PROTECTED]> wrote: > > >> try: >> l,b,w,h = ax.get_position() >> except: >> l,b,w,h = (ax.get_position()).bounds >> > > In general, blanket excepts are bad prac

Re: [matplotlib-devel] pcolormesh in transforms branch

Michael Droettboom wrote: > The transforms branch has seen very little outside of the matplotlib > examples, so it's good to find all of these error cases. Fixed in r4569. > > Cheers, > Mike > >> Michael: And one more - contourf will die if you there are no >> contours at the requested levels.

Re: [matplotlib-devel] animation blit under gtk*

John Hunter wrote: > I just noticed that the blit API in GTK* is causing a seg fault on my > desktop. Can anyone confirm this on another system. Has anyone made > any changes that you are aware of that might have affected this part > of the code? I am seeing problems with > examples/animation_bl

Re: [matplotlib-devel] pcolormesh in transforms branch

Jeff Whitaker wrote: > Michael Droettboom wrote: >> Thanks for finding this. It was an x,y reversal indexing the mesh >> array. Fixed in r4565. >> >> Cheers, >> Mike >> >> Jeff Whitaker wrote: >>> >>> Hi Michael: I've been te

Re: [matplotlib-devel] pcolormesh in transforms branch

Michael Droettboom wrote: Thanks for finding this. It was an x,y reversal indexing the mesh array. Fixed in r4565. Cheers, Mike Jeff Whitaker wrote: Hi Michael: I've been testing basemap with the transforms branch. All the examples now run, but the ones that use pcolormesh don&#

[matplotlib-devel] pcolormesh in transforms branch

Hi Michael: I've been testing basemap with the transforms branch. All the examples now run, but the ones that use pcolormesh don't work correctly. I've attached an example. In the trunk, using either pcolor or pcolormesh produce an identical plot. In the transforms branch, using pcolor

Re: [matplotlib-devel] site docs

John Hunter wrote: > For the 0.91 release, I have updated the web site, which had become > woefully out of date. In addition to some 91 specific things like > "what's new", credits and updating a bunch of links to point to > pyplot, I also cleaned out some dead wood (removed numeric and > numarray

Re: [matplotlib-devel] build error in transforms branch

Michael Droettboom wrote: > Jeff Whitaker wrote: >> Michael Droettboom wrote: >>> Actually, this is the inverse error to the other one ;) Keeping >>> track of which APIs are "current" is proving difficult. >>> >>> Try r4448... Thanks for yo

Re: [matplotlib-devel] build error in transforms branch

I change that I need to adjust to, or a bug? -Jeff drive_gfs.o306841 > > Jeff Whitaker wrote: >> Michael Droettboom wrote: >>> Sorry. Try now (r4447). I realised I have to skip even one more >>> level. >>> >>> Cheers, >>> Mike >> &g

Re: [matplotlib-devel] build error in transforms branch

type219/include/freetype2 -I/usr/include/freetype2 -I/sw/include/freetype2 -I/usr/X11R6/include/freetype2 -I./freetype2 -I/sw/include/python2.5 -c src/backend_agg.cpp -o build/temp.macosx-10.4-i386-2.5/src/backend_agg.o" failed with exit status 1 -Jeff > > Jeff Whitaker wrote: >&

Re: [matplotlib-devel] build error in transforms branch

Michael Droettboom wrote: > [Jeff -- I don't know why your original e-mail never got delivered to > me, but I was able to see it in the archive.] > > The problem arises on platforms with 64-bit pointers -- in Numpy the > datatype used to store the shape of an array is different from the > dataty

[matplotlib-devel] build error in transforms branch

Michael: I'm seeing the following error on OS X (Tiger) with numpy 1.0.4 when building the latest svn transforms branch: src/path.cpp: In member function 'Py::Object _path_module::affine_transform(const Py::Tuple&)': src/path.cpp:700: error: invalid conversion from 'npy_intp*' to 'int*' cc1plu

Re: [matplotlib-devel] [Matplotlib-users] ANN: basemap toolkit version 0.9.7 released

Vincent Schut wrote: > Jeff Whitaker wrote: > > >> There is an extra dependency on the GEOS (Geometry Engine) library >> (http://geos.refractions.net). The source code is included with basemap, >> but requires a separate ./configure; make ;make install step before

[matplotlib-devel] ANN: basemap toolkit version 0.9.7 released

(sorry for botched subject line in the first message) Basemap 0.9.7 is available for download. http://www.python.org/pypi/basemap/0.9.7 http://sourceforge.net/project/showfiles.php?group_id=80706&package_id=142792&release_id=555980

[matplotlib-devel] [Fwd: ANN: matplotlib-0.90.0]

Basemap 0.9.7 is available for download. http://www.python.org/pypi/basemap/0.9.7 http://sourceforge.net/project/showfiles.php?group_id=80706&package_id=142792&release_id=555980 Windows installe

Re: [matplotlib-devel] RFC on basemap changes

Christopher Barker wrote: > Jeff, > > as you mentioned license as one issue in not using shapely, I thought > you might be interested in this: > > Original Message > Subject: [Community] Proposal to change Shapely license from LGPL to BSD > From: Sean Gillies <[EMAIL PROTECTED]>

Re: [matplotlib-devel] RFC on basemap changes

Christopher Barker wrote: > Jeff Whitaker wrote: > >> 1) an external dependency on the GEOS lib (which is LGPL). >> > > Would it be any better to depend on an existing python binding GEOS? > Here's one option: > > http://trac.gispython.or

[matplotlib-devel] RFC on basemap changes

I've created a new basemap branch https://matplotlib.svn.sourceforge.net/svnroot/matplotlib/trunk/toolkits/basemap-testing with lots of under-the-hood optimizations and code refactoring. The most significant change is that I now use the GEOS library (http://geos.refractions.net) to determine

Re: [matplotlib-devel] Basemap toolkit: problem with polarplot example

xpecting nothing > ok > Trying: > print '%9.3f %9.3f %9.3f %11.3f %11.3f %11.3f' % xy > Expecting: > 567703.344 351730.944 728553.093 4298200.739 4353698.725 4292319.005 > ok > Trying: > xy = x2+y2 > Expecting nothing > ok > Trying: > print &#x

Re: [matplotlib-devel] Basemap toolkit: problem with polarplot example

xpecting nothing > ok > Trying: > print '%9.3f %9.3f %9.3f %11.3f %11.3f %11.3f' % xy > Expecting: > 567703.344 351730.944 728553.093 4298200.739 4353698.725 4292319.005 > ok > Trying: > xy = x2+y2 > Expecting nothing > ok > Trying: > print &#x

Re: [matplotlib-devel] Basemap toolkit: problem with polarplot example

David Huard wrote: > Hi, the pyproj package seems to cause a problem in the polarmap > example of the basemap toolkit. > > Thanks, > > david > > [EMAIL PROTECTED]:~/svnrepos/toolkits/basemap/examples$ python polarmaps.py > min/max etopo20 data: > -9026.625 6228.8125 > plotting North Polar Lambert

[matplotlib-devel] small fix for colorbar

Eric: I came across what may be a small bug in colorbar. If you pass a list to colorbar with the 'ticks' keyword, and the list is longer than 10, you don't actually get the ticks at the locations you specify. This patch seems to fix it: --- colorbar.py 2007-04-09 11:12:19.0 -0600 +++

Re: [matplotlib-devel] corner artifacts

John Hunter wrote: > I seem to be getting some corner artifacts when using *Agg that I > haven't seen before. Anyone else seeing something strange and any > idea why? > > import numpy > > from pylab import figure, show > > t = numpy.arange(0.0, 1.0, 0.1) > s = numpy.ones(len(t), dtype=numpy.float_

Re: [matplotlib-devel] memory leaks

Tom Holroyd (NIH/NIMH) [E] wrote: >> import os,matplotlib >> matplotlib.use('Agg') >> from matplotlib.figure import Figure >> from matplotlib.cbook import report_memory >> >> def plot(): >> fig = Figure() >> i = 0 >> while True: >> print report_memory(i) >> fig.clf() >>

Re: [matplotlib-devel] memory leaks

John Hunter wrote: > On 3/28/07, Jeff Whitaker <[EMAIL PROTECTED]> wrote: > >> John: I just added macos x support in the report_memory function. >> Regarding Eric's memory leak #2 (which occurs even for non-gui >> backends), here's a simple script to trigg

  1   2   >