Dear ALL,
Am I intending to change the world's geography? No, not quite. I just
would like to know how to deal with the following problem, I have
stumbled upon in MPL/Basemap: I have a line:
continents = map.fillcontinents(color='coral, lake_color='blue')
where map is, of course, a Basemap
Dear ALL,
I just noted that the remove() method which worked OK in version 0.99
of MPL Basemap to remove country borders and rivers is not working
anymore after I upgraded to Basemap version 0.99.2.
What have changed?
Thanks in advance.
Best regards,
--
Dr. Mauro J. Cavalcanti
Ecoinformatics
Mauro Cavalcanti wrote:
Dear ALL,
Am I intending to change the world's geography? No, not quite. I just
would like to know how to deal with the following problem, I have
stumbled upon in MPL/Basemap: I have a line:
continents = map.fillcontinents(color='coral, lake_color='blue')
where map
Mauro Cavalcanti wrote:
Dear ALL,
I just noted that the remove() method which worked OK in version 0.99
of MPL Basemap to remove country borders and rivers is not working
anymore after I upgraded to Basemap version 0.99.2.
What have changed?
Thanks in advance.
Best regards,
Mauro:
Good Day!
In the course of testing two ode solvers (stiff and non-stiff) I noticed
that the figures that were saved (either eps or pdf) were fuzzy. The figures
produced by the command pylab.plot(xdata, ydata) followed by pylab.show()
were essentially smooth. When I zoomed in all lines were
On Sat, Dec 13, 2008 at 9:38 AM, John Hunter jdh2...@gmail.com wrote:
My guess is that you may be seeing the antialiasing of your pdf
renderer. matplotlib has a pretty good antialiasing renderer for the
screen display (antigrain) but your mileage may vary for your pdf
renderer. Since pdf is
John Hunter jdh2...@gmail.com writes:
One more thought -- you should be able to turn off the antialiased
property, eg with
plot(x, y, antialiased=False)
Unfortunately, I poked into our backend_pdf and it appears this
property is ignored. Jouni: is there a way to turn off antialiasing
There's something funny going on with line caps, maybe? It looks like
the corners aren't getting capped in the same way as Agg does.
I've created screenshots of Jesse's pdf file in acrobat and evince.
Any thought, Jouni?
Cheers,
Mike
John Hunter wrote:
On Thu, Dec 11, 2008 at 11:16 PM,
Also -- for mtcoder:
Can you send us the script that generates your plot?
Also, if you set your backend to Cairo, and then generate the pdf, to
you get the same result?
Cheers,
Mike
Michael Droettboom wrote:
There's something funny going on with line caps, maybe? It looks like
the corners
Mauro Cavalcanti wrote:
Dear Jeff,
2008/12/13 Jeff Whitaker jsw...@fastmail.fm:
Mauro: That's a bug - the fillcontinents method was only returning the last
Polygon instance drawn. I've fixed it in SVN (r6579) to return a list of
all the Polygon instances. You can now iterate over that
Years ago I observed a similar behaviour with gnuplot. This behaviour
appears if you use line join style 'miter' and if your data is very fine
spaced with small noise. Then in the figure the noise appears much
larger than it actually is. Limited output precision for representing
the plot data
Mauro Cavalcanti wrote:
Dear Jeff,
Thanks for your attention.
2008/12/13 Jeff Whitaker jsw...@fastmail.fm:
Mauro: Did you update from SVN? If so, can be more specific about what
didn't work? The return value of fillcontinents should be a list of Polygon
instances, each with a remove
Hi,
I am having a problem building matplotlib on OS X. It seems it has
come up quite a few times, but I haven't seen an answer. The problem
is that it seems to be trying to build a fat binary (-arch i386 -arch
ppc) but some of the depencies (installed via macports) are i386 only
so I get
Oops.. I'll continue
I am having a problem building matplotlib on OS X. It seems it has
come up quite a few times, but I haven't seen an answer. The problem
is that it seems to be trying to build a fat binary (-arch i386 -arch
ppc) but some of the depencies (installed via macports) are i386 only
Hi,
As in my other mail I am having trouble building from source.
Previously I used the mac .egg to get around this, but the
matplotlib-0.98.5-py2.5-macosx-10.3.egg for 0.98.5 doesn't appear to
work.
I install with -N as I found recommended elsewhere on the list, since
otherwise it tries to
On Sat, Dec 13, 2008 at 3:01 PM, Robin robi...@gmail.com wrote:
As in my other mail I am having trouble building from source.
Previously I used the mac .egg to get around this, but the
matplotlib-0.98.5-py2.5-macosx-10.3.egg for 0.98.5 doesn't appear to
work.
I think the egg may be broken.
On Sat, Dec 13, 2008 at 9:17 PM, John Hunter jdh2...@gmail.com wrote:
On Sat, Dec 13, 2008 at 3:01 PM, Robin robi...@gmail.com wrote:
As in my other mail I am having trouble building from source.
Previously I used the mac .egg to get around this, but the
I had the same problem with the matplotlib-0.98.5-py2.5-macosx-10.3.egg on OS X
10.5 and finally determined that it expected the latest png library. The one on
the most recent release of the OS is a littler earlier. I compiled the library
from the png website and redid the easy_install and
All,
Thanks for the quick and informative responses. I've attached the code
(testode.c). It requires the GSL library. I've also attached the script I
was using to read and plot the data (odetest.py). [Note: If you do any tests
with the python script make sure to change the savefig directory in
19 matches
Mail list logo
