Alan -
You started a discussion about dpi on the figures.
Yet here you claim that 1pt = 1/72 inch.
Is that always the case?
And why? How does mpl figure that out, if there are also different dpi
settings?
The plot thickens...
Mark
Alan Isaac wrote:
Note: 1pt = 1/72 inch
hth,
Alan Isaac
New version is available now. Just select matplotlib component from Boa
pallete and plot any number of different plots as easy as with Pylab. See
runtime sample. My e-mail is [EMAIL PROTECTED] If you are interested, please,
write me. It costs $50. Igor V. Khromushin
Mark Bakker wrote:
Alan -
You started a discussion about dpi on the figures.
Yet here you claim that 1pt = 1/72 inch.
Is that always the case?
Yes, I that's *by definition* always the case !
pt is a point - not a dot or a pixel !!!
Point is a unit of measurement used in typography that is
On Fri, 1 Feb 2008, Mark Bakker apparently wrote:
you claim that 1pt = 1/72 inch. Is that always the case?
And why? How does mpl figure that out
Based on the discussion for far,
I assume it works like this.
(figsize in inches) * dpi = (size in pixels)
So if you draw a line 72 points long,
On Fri, 1 Feb 2008, Stephen George wrote:
bit confused what your asking.
are you looking for the pylab API savefig
Stephen/Alan/Chloe:
Yes, it turns out that I am.
or you asking how to convert your variable+.png into a filename?
is your variable a number?, string?
The variable is a
Hi,
I'm trying to export a MAtplotlib figure which has some axes labels, such as
'coût'.
The problème is that the generated eps is corrupted because of these
accents. Is there a way to generate an acceptable eps file ?
Matthieu
--
French PhD student
Website :
Unicode in Python is tricky. It is explained in gory detail here:
http://www.amk.ca/python/howto/unicode
But to save you the trouble of reading the whole thing, unless you're an
i18n geek like me, here's my list of recommendations to (somewhat)
reliably get non-ASCII characters to work in
Some additional information : it does not work with the pdf backend and with
the svg one, the accents are corrupted (I tried to export utf8 encoded
labels).
I'm using pycrust, BTW. But I don't know how to change the default encoding
(the display is correct but not the saved image).
Matthieu
No problem with the png backend.
I tried with Latex for the accent, but it didn't work :
Traceback (most recent call last):
File input, line 1, in module
File
/home/brucher/local//lib/python2.5/site-packages/matplotlib/pyplot.py,
line 265, in draw
get_current_fig_manager().canvas.draw()
Can you provide an example of your code? Often, it is a matter of
configuring/using Python correctly to indicate accents. Is the problem
only with EPS or other backends as well?
Cheers,
Mike
Matthieu Brucher wrote:
Hi,
I'm trying to export a MAtplotlib figure which has some axes labels,
Alan G Isaac wrote:
On Fri, 1 Feb 2008, Mark Bakker apparently wrote:
you claim that 1pt = 1/72 inch. Is that always the case?
And why? How does mpl figure that out
I wrote this to help clarify some of these issues:
http://www.scipy.org/Cookbook/Matplotlib/AdjustingImageSize
By the
On Fri, 1 Feb 2008, Eric Firing wrote:
What changed is that I added a warning where previously there was only a
silent error--the matplotlib.use command was being ignored. Sometimes
this (ignoring the command) is harmless, but it is never the user's intent
and in some cases it can cause
On Jan 31, 2008 6:03 AM, Thomas Tanner [EMAIL PROTECTED] wrote:
Hi,
I'd like to have figure with 3 (or 4) plots having different scales
but sharing the same x-axis.
Basically I want an extension of the twinx command (see, e.g,
two_scales.py demo).
I'm using 0.91.2svn on MacOSX10.5.1 from
On Fri, 1 Feb 2008, Eric Firing wrote:
One way to find out where the warning is coming from is to invoke your script
as
python -Werror myscript.py
Eric,
That did the trick. Two modules needed to have the backend specification
commented out.
Many thanks,
Rich
--
Richard B. Shepard,
Rich Shepard wrote:
On Fri, 1 Feb 2008, Eric Firing wrote:
What changed is that I added a warning where previously there was only a
silent error--the matplotlib.use command was being ignored. Sometimes
this (ignoring the command) is harmless, but it is never the user's intent
and in some
When using the PostScript backend, and plotting several lines with the same
call to plot (or when plotting a LineCollection), kwargs are applied to the
first line only, and not to every line.
Included is a minimal script that exhibits this problem. The saved figure shows
only one thick red
Included is a patch to change the behavior when legend() is called with
numpoints less than or equal to 0. Currently if one makes such a call, some
cryptic error messages are printed out and the plot is not generated.
The included patch produces a warning, and defaults to using numpoints = 4,
17 matches
Mail list logo
