matplotlib-users Mailing List for matplotlib

Paul Ivanov skrev 2011-03-17 20:58:
> Jörgen Stenarson, on 2011-03-16 18:04,  wrote:
>>  Hi,
>>
>>  I'm interested in making plots that are plotted on a polar grid or a
>>  smith chart grid but where the data coordinates still are normal
>>  rectangular. It is not clear for me if this is possible with the
>>  standard gridding machinery or if some other approach is necessary.
>>
>>  Another question is how would I get the data to clip inside the maximum
>>  circle of the polar or smithchart?
>
> Hi Jörgen,
>
> there's probably a way of doing this, and not knowing your other
> constraints maybe this isn't an option, but the path of least
> resistance would be to make a polar subplot and transform your
> rectangular data to polar coordinates for the purposes of
> plotting (rather than transforming the grid to polar). This way
> you'll get your clipping "for free."
>
Hi Paul,

I'll test that approach for the polar plots, but it won't work for the 
Smith chart where I need another grid.

/Jörgen

Evan Mason, on 2011-03-16 15:27,  wrote:
> Hi, I get unexpected behaviour using the script below.  xticks only appear in
> the 4th subplot.  If the lines marked ### are moved out of the loop (and edited
> so that they are constants), then xticks do appear on each subplot.  Is this a
> bug or am I missing something?
> 
> I am using matplotlib 1.1.0svn.

Hi Evan,

What you're seeing is the result of each instance of locator
belonging to one and only one axis (namely months.axis), and
every time you call ax.xaxis_major_locator, you're moving it to
the newest subplot.

Just move the 'months = ...' line inside the for-loop, and you'll
be all set.

best,
-- 
Paul Ivanov
314 address only used for lists,  off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 

Stef Mientki, on 2011-03-16 19:45,  wrote:
> hello,
> 
> The text in matplotlib pictures is very fuzzy (certainly if you compare that to fixed texts).
> The picture below is from an html page, the html page is generated from a python script,
> which also produces the matplotlib pictures, which are stored in a png-file and linked in the html page.
> 
> Are there ways to improve the font quality of the texts in the MatPlotLib image ?

Hi Stef,

Have you tried increasing the resolution of the images before you
save them, via plt.savefig("something.png",dpi=160) or by setting
the savefig.dpi rcParam to affect all plots. You might also play
with using different fontsize parameters when calling .text(...)
 
best,
-- 
Paul Ivanov
314 address only used for lists,  off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 

Jörgen Stenarson, on 2011-03-16 18:04,  wrote:
> Hi,
> 
> I'm interested in making plots that are plotted on a polar grid or a 
> smith chart grid but where the data coordinates still are normal 
> rectangular. It is not clear for me if this is possible with the 
> standard gridding machinery or if some other approach is necessary.
> 
> Another question is how would I get the data to clip inside the maximum 
> circle of the polar or smithchart?

Hi Jörgen,

there's probably a way of doing this, and not knowing your other
constraints maybe this isn't an option, but the path of least
resistance would be to make a polar subplot and transform your
rectangular data to polar coordinates for the purposes of
plotting (rather than transforming the grid to polar). This way
you'll get your clipping "for free."

best,
-- 
Paul Ivanov
314 address only used for lists,  off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 

Francesco Montesano, on 2011-03-17 12:05,  wrote:
> Dear all,
> 
> I have a rather complex code that takes a list of file names and of
> legend tags from command line and compute contour plots
> 
> ./contour_plots.py [options] filename1 ... filename2 tag1 ... tagn
> 
> The codes make filled contours at required levels, then line contours.
> >From the latter I extract one line from each file and create a legend
> 
> spl.legend(lines, [tag1...tagn], other options)
> 
> All it works fine. The only problem is that sometimes I have tags that
> are long and I would like to be able to break between multiple lines.
> In examples/legend_demo3.py is shown that 'ax1.plot([1],
> label="multi\nline")' the \n is interpreted (correctly) as new line.
> 
> Normaly I have something like
> ./contour_plots.py [options] filename1 \(long\)tag\$_\{very long\}\$
> that gives me a legend with the correct formatting. If I try to add a
> '\n' after 'tag', I get out the tag as before plus a 'n' after 'tag'.
> I've tried to enclose the whole string or just \n in "" or r"" but
> nothing good happens (either I get 'n' or 'rn').
> Is there a way to do what I want to do?

Hi Francesco,

If you are using bash, you can insert newlines using the
Enter/Return key if you start an argument with a quote like this:

$ cat commandline.py
#!/usr/bin/env python
import sys
print "Program output:", sys.argv
print sys.argv[-1]

$ ./commandline.py "something
with
newlines"

Program output: ['./commandline.py', 'something\nwith\nnewlines']
something
with
newlines

best,
-- 
Paul Ivanov
314 address only used for lists,  off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 

/usr/lib64/python2.7/site-packages/matplotlib/font_manager.py:1242: UserWarning: 
findfont: Font family ['STIXSizeOneSym'] not found. Falling back to Bitstream 
Vera Sans
  (prop.get_family(), self.defaultFamily[fontext]))
/usr/lib64/python2.7/site-packages/matplotlib/font_manager.py:1242: UserWarning: 
findfont: Font family ['STIXSizeThreeSym'] not found. Falling back to Bitstream 
Vera Sans
  (prop.get_family(), self.defaultFamily[fontext]))
/usr/lib64/python2.7/site-packages/matplotlib/font_manager.py:1242: UserWarning: 
findfont: Font family ['STIXSizeFourSym'] not found. Falling back to Bitstream 
Vera Sans
  (prop.get_family(), self.defaultFamily[fontext]))
/usr/lib64/python2.7/site-packages/matplotlib/font_manager.py:1242: UserWarning: 
findfont: Font family ['STIXSizeFiveSym'] not found. Falling back to Bitstream 
Vera Sans
  (prop.get_family(), self.defaultFamily[fontext]))
/usr/lib64/python2.7/site-packages/matplotlib/font_manager.py:1242: UserWarning: 
findfont: Font family ['STIXSizeTwoSym'] not found. Falling back to Bitstream 
Vera Sans
  (prop.get_family(), self.defaultFamily[fontext]))
/usr/lib64/python2.7/site-packages/matplotlib/font_manager.py:1242: UserWarning: 
findfont: Font family ['STIXNonUnicode'] not found. Falling back to Bitstream 
Vera Sans
  (prop.get_family(), self.defaultFamily[fontext]))

But I have stix fonts installed
stix-pua-fonts-1.0.0-1.fc14.noarch
stix-variants-fonts-1.0.0-1.fc14.noarch
stix-fonts-doc-1.0.0-1.fc14.noarch
stix-sizes-fonts-1.0.0-1.fc14.noarch
stix-fonts-1.0.0-1.fc14.noarch
stix-integrals-fonts-1.0.0-1.fc14.noarch

What could be wrong?

Dear all,

I have a rather complex code that takes a list of file names and of
legend tags from command line and compute contour plots

./contour_plots.py [options] filename1 ... filename2 tag1 ... tagn

The codes make filled contours at required levels, then line contours.
>From the latter I extract one line from each file and create a legend

spl.legend(lines, [tag1...tagn], other options)

All it works fine. The only problem is that sometimes I have tags that
are long and I would like to be able to break between multiple lines.
In examples/legend_demo3.py is shown that 'ax1.plot([1],
label="multi\nline")' the \n is interpreted (correctly) as new line.

Normaly I have something like
./contour_plots.py [options] filename1 \(long\)tag\$_\{very long\}\$
that gives me a legend with the correct formatting. If I try to add a
'\n' after 'tag', I get out the tag as before plus a 'n' after 'tag'.
I've tried to enclose the whole string or just \n in "" or r"" but
nothing good happens (either I get 'n' or 'rn').
Is there a way to do what I want to do?

Thanks in advance
Francesco

On 13 Jan 2011, at 5:50 AM, Michael Droettboom wrote:

> Can you provide a simple LaTeX document that illustrates the problem  
> with psfrag?  This is still compliant Postscript, AFAICT.

It is not a postscript compliance issue, but rather a requirement of  
the psfrag package which relys on searching for complete strings of  
the form "(...) show" for replacement.

Here is a simple example.  Prior to this change, matplotlib would  
output the entire string "(0) show", "(1) show" and "(Np) show".  The  
psfrag package replaces these with typeset versions of "zero", "one"  
and "$N_+$ in whatever font, size, etc. is active in the LaTeX file  
(providing an exact match with the surrounding text).

The new version of matplotlib has instead the individual characters  
followed by glyphshow: "/zero glyphshow" etc. and psfrag can no-longer  
locate the appropriate strings and replace them.  Please provide a way  
for users to revert to the old behaviour of outputing the complete  
string rather than one glyph at a time as some of us use psfrag  
extensively for publication-quality figures.

% import matplotlib.pyplot as plt
% plt.plot([0,1],[0,1])
% plt.xticks([0,1], ['0', '1'])
% plt.xlabel(r'Np')
% savefig('bad.eps')
\documentclass{article}
\usepackage{graphicx}
\usepackage{psfrag}
\begin{document}
\psfrag{0}{zero}
\psfrag{1}{one}
\psfrag{Np}{$N_+$}
\includegraphics[width=\textwidth]{bad.eps}
\end{document}

> On 01/11/2011 10:43 AM, Benjamin Root wrote:
>>
>>
>>
>> On Tue, Jan 11, 2011 at 8:45 AM, Lebostein <Leb...@gm...> wrote:
>>
>> I have compared the new and old output. For example the "0.0" in a  
>> diagram:
>>
>> old eps (1.0.0):
>>
>> 35.223 19.934 m
>> 0 0.141 rmoveto
>> (0.0) show
>> [1 2] 0 setdash
>> 0.502 setgray
>>
>> new eps (1.0.1):
>>
>> 35.222810 19.933563 translate
>> 0.000000 rotate
>> 0.000000 0.140625 m /zero glyphshow
>> 6.362305 0.140625 m /period glyphshow
>> 9.541016 0.140625 m /zero glyphshow
>> grestore
>> [1 2] 0 setdash
>> 0.502 setgray