matplotlib-users Mailing List for matplotlib (Page 5)

After further anlysis, I still get the light colored lined at x=10 when I
zoom-in interactively on that line (still using TkAgg). Have you tried
zooming-in?
I tried to zoom in on my eps and png files with the overlap, and they look
fine.
That's all. I can live with it just fine, but it is odd.
Still would like to know what interpolation option you used.
Thanks,
Mark
On 8/21/07, Mark Bakker <ma...@gm...> wrote:
>
> I use TkAgg on win32, and saw the line on screen and in png and eps files.
> I tried nudging it, but that didn't work either.
> So I tried the following overlap and still saw the line:
> a = ones((10,10))
> imshow(a,extent=( 0.0,11.0,0.0,10.0))
> imshow(a,extent=(10.0,20.0,0.0,10.0))
> axis((0,20,0,10))
>
> So I figured it had to do with the interpolation.
> I used the default interpolation ('bilinear').
> When I do the above overlap with interpolation set to 'nearest', I don't
> get the line!
>
> What interpolation were you using?
>
> Thanks for your help,
>
> Mark
>
>
> On 8/21/07, Eric Firing < ef...@ha...> wrote:
> >
> > Mark,
> >
> > What backend? I don't see it when I run your lines in ipython -pylab,
> > with gtkagg in use (linux).
> >
> > Have you tried using floating point extents and fudging them very
> > slightly to overlap?
> >
> > Eric
> >
> > Mark Bakker wrote:
> > > Hello all -
> > >
> > > I am trying to plot two images side byside.
> > > The problem is that I get a white line between them.
> > > Even when the extent of the two images are exactly next to eachother.
> > > Does anybody know how to get rid of the white line?
> > > Here's an easy example:
> > >
> > > from pylab import *
> > > a = ones((10,10))
> > > imshow(a,extent=(0,10,0,10))
> > > imshow(a,extent=(10,20,0,10))
> > > axis((0,20,0,10))
> > >
> > > Thanks, Mark
> > >
> > >
> > >
> > ------------------------------------------------------------------------
> > >
> > >
> > -------------------------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc.
> > > Still grepping through log files to find problems? Stop.
> > > Now Search log events and configuration files using AJAX and a
> > browser.
> > > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > >
> > >
> > >
> > ------------------------------------------------------------------------
> > >
> > > _______________________________________________
> > > Matplotlib-users mailing list
> > > Mat...@li...
> > > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> >
> >
>

I use TkAgg on win32, and saw the line on screen and in png and eps files.
I tried nudging it, but that didn't work either.
So I tried the following overlap and still saw the line:
a = ones((10,10))
imshow(a,extent=(0.0,11.0,0.0,10.0))
imshow(a,extent=(10.0,20.0,0.0,10.0))
axis((0,20,0,10))
So I figured it had to do with the interpolation.
I used the default interpolation ('bilinear').
When I do the above overlap with interpolation set to 'nearest', I don't get
the line!
What interpolation were you using?
Thanks for your help,
Mark
On 8/21/07, Eric Firing <ef...@ha...> wrote:
>
> Mark,
>
> What backend? I don't see it when I run your lines in ipython -pylab,
> with gtkagg in use (linux).
>
> Have you tried using floating point extents and fudging them very
> slightly to overlap?
>
> Eric
>
> Mark Bakker wrote:
> > Hello all -
> >
> > I am trying to plot two images side byside.
> > The problem is that I get a white line between them.
> > Even when the extent of the two images are exactly next to eachother.
> > Does anybody know how to get rid of the white line?
> > Here's an easy example:
> >
> > from pylab import *
> > a = ones((10,10))
> > imshow(a,extent=(0,10,0,10))
> > imshow(a,extent=(10,20,0,10))
> > axis((0,20,0,10))
> >
> > Thanks, Mark
> >
> >
> > ------------------------------------------------------------------------
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems? Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Matplotlib-users mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>

Eric Firing <ef...@ha...> writes:
> My guess is that this problem has been lurking all along, but was only 
> triggered when I changed font_manager to look for *all* system fonts 
> instead of only truetype, 
Another data point: a recent svn version of matplotlib segfaults on my
OS X system, and ktrace suggests it occurs while it is reading
CharcoalCY.dfont. Running under gdb causes it to exit with a traceback
that ends like this:
 File "/Users/jks/Hacking/matplotlib/matplotlib/lib/matplotlib/font_manager.py", line 200, in get_fontconfig_fonts
 status, output = commands.getstatusoutput("fc-list file")
 File "/Library/Frameworks/Python.framework/Versions/2.4//lib/python2.4/commands.py", line 54, in getstatusoutput
 text = pipe.read()
IOError: [Errno 4] Interrupted system call
Investigating...
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

Mark,
What backend? I don't see it when I run your lines in ipython -pylab, 
with gtkagg in use (linux).
Have you tried using floating point extents and fudging them very 
slightly to overlap?
Eric
Mark Bakker wrote:
> Hello all -
> 
> I am trying to plot two images side byside.
> The problem is that I get a white line between them.
> Even when the extent of the two images are exactly next to eachother.
> Does anybody know how to get rid of the white line?
> Here's an easy example:
> 
> from pylab import *
> a = ones((10,10))
> imshow(a,extent=(0,10,0,10))
> imshow(a,extent=(10,20,0,10))
> axis((0,20,0,10))
> 
> Thanks, Mark
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

On Tuesday 21 August 2007 12:46:05 pm Jouni K. Sepp=E4nen wrote:
> Darren Dale <dd...@co...> writes:
> >> The testgs.eps (for test with ghostscript) does not convert to pdf
> >> using either apple preview or adobe distiller (the adobe log is
> >> included)
> >> It does however convert successfully with epstopdf so there is some
> >> subtle difference.
> >
> > I'm sorry, I have no idea. I guess you would have to take it up with
> > ghostscript, that is the program that is producing the file that adobe
> > and apple preview is having trouble with.
>
> Since this is on Mac OS X, I suspect it is the long-standing font
> problem; that is, matplotlib finds and uses some system fonts but does
> not embed them correctly. If you force the Bitstream Vera family of
> fonts, does it work then?
I doubt this is the case. The ghostscript distiller does not embed any font=
s,=20
it renders the text as rasters.

Andrew Jaffe wrote:
> Michael Droettboom wrote:
>> Andrew,
>>
>> I believe this bug was recently discussed on matplotlib-devel and is 
>> likely related to recent changes in the font manager cache.
>>
>> http://www.mail-archive.com/mat...@li.../msg01531.html
>>
>> I believe it's being looked into, but I haven't seen a resolution 
>> (unless I missed it).
> 
> Ah, sorry, this is indeed the same problem.
> 
> Adding
> 
> pdf.use14corefonts : True
> 
> to matplotlibrc does fix it, FWIW.
It solves the immediate problem for people who run into it, and it 
provides a clue about what the underlying problem is, but it does not 
fully identify or solve that problem.
To make real progress on it, we need an OSX user who understands 
something about font matters--or maybe only enough about OSX to do some 
exploration.
In font_manager.py, in the FontManager class, is the following:
 if rcParams['pdf.use14corefonts']:
 # Load only the 14 PDF core fonts. These fonts do not need 
to be
 # embedded; every PDF viewing application is required to 
have them:
 # Helvetica, Helvetica-Bold, Helvetica-Oblique, 
Helvetica-BoldOblique,
 # Courier, Courier-Bold, Courier-Oblique, Courier-BoldOblique,
 # Times-Roman, Times-Bold, Times-Italic, Times-BoldItalic, 
Symbol,
 # ZapfDingbats.
 afmpath = 
os.path.join(rcParams['datapath'],'fonts','pdfcorefonts')
 afmfiles = findSystemFonts(afmpath, fontext='afm')
 self.afmdict = createFontDict(afmfiles, fontext='afm')
 else:
 self.afmfiles = findSystemFonts(paths, fontext='afm') + \
 findSystemFonts(fontext='afm')
 self.afmdict = createFontDict(self.afmfiles, fontext='afm')
I think that the problem is occurring in the last line. This remains to 
be verified. It looks like *.afm files are being found, but when 
createFontDict tries to parse them it doesn't find what it expects.
My guess is that this problem has been lurking all along, but was only 
triggered when I changed font_manager to look for *all* system fonts 
instead of only truetype, so that it could generate a complete cache and 
then never have to search again unless the cache (actually a pickle of 
the FontManager instance) is deleted.
Eric
> 
> Andrew
> 
> 
> 
> 
>> Cheers,
>> Mike
>>
>> Andrew Jaffe wrote:
>>> Hi All,
>>>
>>> I've got Intel OSX 10.4.10 with SVN versions of numpy, scipy and 
>>> matplotlib.
>>>
>>> The latest matplotlib seems to fail on "import pylab" or "ipython 
>>> -pylab" with very many lines of the form
>>>
>>> "Found an unknown keyword in AFM header (was"
>>> followed either by a legit character or lots of junk.
>>>
>>> For what it's worth, I tend to install eggs rather than simple setup.py 
>>> install; moving back to r3421 which I had prevviously seems to work fine.
>>>
>>> Any ideas?
>>>
>>> Yours,
>>>
>>> Andrew

Darren Dale <dd...@co...> writes:
>> The testgs.eps (for test with ghostscript) does not convert to pdf
>> using either apple preview or adobe distiller (the adobe log is
>> included)
>> It does however convert successfully with epstopdf so there is some
>> subtle difference.
>
> I'm sorry, I have no idea. I guess you would have to take it up with 
> ghostscript, that is the program that is producing the file that adobe and 
> apple preview is having trouble with.
Since this is on Mac OS X, I suspect it is the long-standing font
problem; that is, matplotlib finds and uses some system fonts but does
not embed them correctly. If you force the Bitstream Vera family of
fonts, does it work then?
>> >> : Error: No paper information available - using defaults
I think this is an xpdf error message. Adding "errQuiet yes" to
~/.xpdfrc might silence it, at the cost of omitting more serious
messages too.
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

Hi,
I have a "simple" problem with mpl, but didn't find a way to solve it so
far.
Let's say I have a set of three 2Darrays I would like to :
- load using imshow
- then connect to the mouse click event and add all X and Y coordinates
obtained when clicking
 (so each time I click, I'll get xc += event.x for example)
 and PAUSE the program until I get a click on the right button of the mouse
- when I click on the right button of the mouse, I want the program to
go on and load the second data array
- ... and continue until all data arrays have been looked at in that way.
So in principle it would look like the script below. But of course this
DOES NOT WORK!!!
So I would welcome any suggestion of how to solve this problem....
Eric
=================
import numpy as num
class offset:
 def __init__(self) :
 self.xc = 0.
 self.yc = 0.
 self.stay = 1
 def on_click(self, event) :
 if event.button == 1:
 if event.inaxes is not None:
 self.xc += event.xdata
 self.yc += event.ydata
 elif event.button == 3:
 self.stay = 0
data1 = num.random.rand(10,10)
data2 = num.random.rand(10,10)
data3 = num.random.rand(10,10)
alldata = [data1, data2, data3]
for i in range(len(alldata)) :
 imshow(alldata[i])
 newoffset = offset()
 binding = connect('button_press_event', newoffset.on_click)
 while newoffset.stay :
 pass
 disconnect(binding)
 print newoffset.xc, newoffset.yc

On Tuesday 21 August 2007 10:47:33 am you wrote:
> > No, it is not a known problem. I have never had a problem
> > converting an eps to
> > pdf, using either setting. Are you using epstopdf? Could you post
> > an example,
> > something that actually illustrates a problem?
>
> Attached is a folder with testgs.eps, testgs.ps, testxpdf.eps,
> testxpdf.ps as well as the pdf files
> where successful.
> The testgs.eps (for test with ghostscript) does not convert to pdf
> using either apple preview or adobe distiller (the adobe log is
> included)
> It does however convert successfully with epstopdf so there is some
> subtle difference.
I'm sorry, I have no idea. I guess you would have to take it up with 
ghostscript, that is the program that is producing the file that adobe and 
apple preview is having trouble with.
> >> In addition when ever I save a .eps file I get the following error
> >> even though it creates the file ok
> >>
> >> : Error: No paper information available - using defaults
> >>
> >> %%BoundingBox: 78 220 543 561
> >> %%HiResBoundingBox: 78.281998 220.589993 542.375983 560.357983
> >>
> >> Is there a way to fix this?
> >
> > Is this with verbose.level set to silent?
>
> No with verbose set to helpful
> With it silent only the "
>
> :Error: No paper information..."
>
> part prints. tthe bounding box part does not
> But usually helpful only prints something if there is an error or
> warning where as the
> bounding box doesn't appear to be either.
Again, this seems like something to take up with ghostscript. Why do they need 
to broadcast such a benign warning? 
MPL needs to catch the exit status of system calls to ghostscript, which can 
only be done across all platforms with os.system and subprocess. Only 
subprocess allows you to redirect the stdout and stderr, which is how we 
would silence such a message, but subprocess had some problems for us (I dont 
remember what) and we had to go back to os.system.
Sorry I can't be more helpful.
Darren

>
> No, it is not a known problem. I have never had a problem 
> converting an eps to
> pdf, using either setting. Are you using epstopdf? Could you post 
> an example,
> something that actually illustrates a problem?
Attached at least in a mail direct to you is a folder with 
testgs.eps, testgs.ps, testxpdf.eps, testxpdf.ps as well as the pdf 
files
where successful. (matplotlib list won't let me send attachments)
The testgs.eps (for test with ghostscript) does not convert to pdf 
using either apple preview or adobe distiller (the adobe log is 
included)
It does however convert successfully with epstopdf so there is some 
subtle difference.
>
>> In addition when ever I save a .eps file I get the following error
>> even though it creates the file ok
>>
>> : Error: No paper information available - using defaults
>>
>> %%BoundingBox: 78 220 543 561
>> %%HiResBoundingBox: 78.281998 220.589993 542.375983 560.357983
>>
>> Is there a way to fix this?
>
> Is this with verbose.level set to silent?
>
No with verbose set to helpful
With it silent only the "
:Error: No paper information..."
 part prints. tthe bounding box part does not
But usually helpful only prints something if there is an error or 
warning where as the
bounding box doesn't appear to be either.
>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a 
> browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
**********************************************************************
Samuel M. Smith Ph.D.
2966 Fort Hill Road
Eagle Mountain, Utah 84005-4108
801-768-2768 voice
801-768-2769 fax
**********************************************************************
"The greatest source of failure and unhappiness in the world is
giving up what we want most for what we want at the moment"
**********************************************************************

Michael Droettboom wrote:
> Andrew,
> 
> I believe this bug was recently discussed on matplotlib-devel and is 
> likely related to recent changes in the font manager cache.
> 
> http://www.mail-archive.com/mat...@li.../msg01531.html
> 
> I believe it's being looked into, but I haven't seen a resolution 
> (unless I missed it).
Ah, sorry, this is indeed the same problem.
Adding
pdf.use14corefonts : True
to matplotlibrc does fix it, FWIW.
Andrew
> Cheers,
> Mike
> 
> Andrew Jaffe wrote:
>> Hi All,
>>
>> I've got Intel OSX 10.4.10 with SVN versions of numpy, scipy and 
>> matplotlib.
>>
>> The latest matplotlib seems to fail on "import pylab" or "ipython 
>> -pylab" with very many lines of the form
>>
>> "Found an unknown keyword in AFM header (was"
>> followed either by a legit character or lots of junk.
>>
>> For what it's worth, I tend to install eggs rather than simple setup.py 
>> install; moving back to r3421 which I had prevviously seems to work fine.
>>
>> Any ideas?
>>
>> Yours,
>>
>> Andrew
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc.
>> Still grepping through log files to find problems? Stop.
>> Now Search log events and configuration files using AJAX and a browser.
>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/

Andrew,
I believe this bug was recently discussed on matplotlib-devel and is 
likely related to recent changes in the font manager cache.
http://www.mail-archive.com/mat...@li.../msg01531.html
I believe it's being looked into, but I haven't seen a resolution 
(unless I missed it).
Cheers,
Mike
Andrew Jaffe wrote:
> Hi All,
> 
> I've got Intel OSX 10.4.10 with SVN versions of numpy, scipy and 
> matplotlib.
> 
> The latest matplotlib seems to fail on "import pylab" or "ipython 
> -pylab" with very many lines of the form
> 
> "Found an unknown keyword in AFM header (was"
> followed either by a legit character or lots of junk.
> 
> For what it's worth, I tend to install eggs rather than simple setup.py 
> install; moving back to r3421 which I had prevviously seems to work fine.
> 
> Any ideas?
> 
> Yours,
> 
> Andrew
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

That server sounds like a good idea. At the moment I have a different 
problem:
If I close the window sometimes the script does not continue. Is there 
any function that I can call which closes pylab and continues with the 
script?
Also, how can I halt the script after the first issue of show().
thanks in advance
 Wolfgang
Bill Baxter wrote:
> Did you try
> raw_input("hit enter")
> ?
>
>
> On 8/21/07, Wolfgang Kerzendorf <wke...@go...> wrote:
> 
>> Hello,
>>
>> I am currently writing a data reduction program. I want to use pylab in
>> a script and use interactive input of pylab. The problem is that in
>> ipython -pylab the script just keeps going without waiting for input (I
>> have just tested it by plotting something but did not do
>> cid=connect....). In ipython I also have the trouble that the first time
>> I call show the shell waits until the window is closed.
>>
>> Well to simplify my question: How do I decide if pylab just shows the
>> plot or if it waits for input in a script?
>>
>> thanks
>> Wolfgang
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc.
>> Still grepping through log files to find problems? Stop.
>> Now Search log events and configuration files using AJAX and a browser.
>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>> 
>
> 

On 8/21/07, Torsten Hahn <tor...@gm...> wrote:
> The problem is, that there only the major ticklines are returned by
> ax.get_xticklines(). How do i access (and modify) the minor ticklines?
In [80]: for tick in ax.xaxis.get_major_ticks():
 print tick.tick1line, tick.tick2line
 ....:
Line2D((0,0)) Line2D((0,1))
Line2D((0,0)) Line2D((0,1))
Line2D((0,0)) Line2D((0,1))
Line2D((0,0)) Line2D((0,1))
Line2D((0,0)) Line2D((0,1))
Line2D((0,0)) Line2D((0,1))
In [82]: for tick in ax.xaxis.get_minor_ticks():
 print tick.tick1line, tick.tick2line
 ....:
for the xaxis, tick1line is the left tick, tick2line is the right
tick. for the y axis they are the bottom and top.
Here is the help on the tick attrs:
In [85]: from matplotlib.axis import Tick
In [87]: print Tick.__doc__
 Abstract base class for the axis ticks, grid lines and labels
 1 refers to the bottom of the plot for xticks and the left for yticks
 2 refers to the top of the plot for xticks and the right for yticks
 Publicly accessible attributes
 tick1line : a Line2D instance
 tick2line : a Line2D instance
 gridline : a Line2D instance
 label1 : a Text instance
 label2 : a Text instance
 gridOn : a boolean which determines whether to draw the tickline
 tick1On : a boolean which determines whether to draw the 1st tickline
 tick2On : a boolean which determines whether to draw the 2nd tickline
 label1On : a boolean which determines whether to draw tick label
 label2On : a boolean which determines whether to draw tick label

Hello,
I've recently been working with matplotlib to create some charts of some
data I've gathered. I've been impressed with how easy it is to use, but I
have a few questions. I'd appreciate any help you can offer me with the
following:
1. Just what does axes() do with pie charts, anyway? I've tried varying the
parameters, but haven't quite grasped what it's for.
2. How do I make the pie of the pie chart smaller, leaving more room for the
labels? Consider http://www.ethicsgirls.com/stuff/report/cameras_used.png
(which I may well move to a bar chart anyway). Some of the labels are
clipped at the sides. What's the best way to avoid this?
3. When plotting a chart with plot(), can I vary the alpha value of the
markers? If so, how?
4. I need to stick a footnote in the bottom corner of my charts. Can I do
this natively in matplotlib or will I have to do it with a separate library
afterwards?
5. Can I have my xtick labels oriented vertically? I'm trying to avoid an X
axis that looks like this:
http://www.ethicsgirls.com/stuff/report/date_taken.png
Thanks,
-- 
Alex Pounds (Creature) .~. http://www.alexpounds.com/
 /V\ http://www.ethicsgirls.com/
 // \\
"Variables won't; Constants aren't" /( )\
 ^`~'^

Am 21.08.2007 um 10:30 schrieb Eric Firing:
> Torsten Hahn wrote:
>> Hello,
>> I am looking for an way to set the width of the tick lines in a 
>> plot. I have not found any rc parameter for this.
>
> Good point; it does seem to be a gap in the configurability.
Would be nice to have sopmething added in a future release.
>> Doing:
>> plot(...)
>> c=gca()
>> tl=c.get_ticklines()
>> gives a list of tickline objects. Every tickline object has a 
>> method tl[0].set_linewidth(). Calling this method with different 
>> float parameters seems to have no effect.
>
> Use tl[0].set_markeredgewidth(); ticks are implemented as markers 
> now to take advantage of backend optimization of marker rendering. 
> No, this is not obvious!
Ok that works but i run into another problem. If you use log or 
loglog plots e.g.
ax = py.subplot(111)
ax.loglog(data)
xtl = ax.get_xticklines()
ytl = ax.get_yticklines()
xtl and ytl are now lists with 2 entrys, one for every axis (for xtl, 
top and bottom x-axis).
top_xtl = xtl[1]
The problem is, that there only the major ticklines are returned by 
ax.get_xticklines(). How do i access (and modify) the minor ticklines?
Torsten.

Hello all -
I am trying to plot two images side byside.
The problem is that I get a white line between them.
Even when the extent of the two images are exactly next to eachother.
Does anybody know how to get rid of the white line?
Here's an easy example:
from pylab import *
a = ones((10,10))
imshow(a,extent=(0,10,0,10))
imshow(a,extent=(10,20,0,10))
axis((0,20,0,10))
Thanks, Mark

Hi All,
I've got Intel OSX 10.4.10 with SVN versions of numpy, scipy and 
matplotlib.
The latest matplotlib seems to fail on "import pylab" or "ipython 
-pylab" with very many lines of the form
"Found an unknown keyword in AFM header (was"
followed either by a legit character or lots of junk.
For what it's worth, I tend to install eggs rather than simple setup.py 
install; moving back to r3421 which I had prevviously seems to work fine.
Any ideas?
Yours,
Andrew

Torsten Hahn wrote:
> Hello,
> 
> I am looking for an way to set the width of the tick lines in a plot. 
> I have not found any rc parameter for this.
Good point; it does seem to be a gap in the configurability.
> 
> Doing:
> 
> plot(...)
> c=gca()
> tl=c.get_ticklines()
> 
> gives a list of tickline objects. Every tickline object has a method 
> tl[0].set_linewidth(). Calling this method with different float 
> parameters seems to have no effect.
Use tl[0].set_markeredgewidth(); ticks are implemented as markers now to 
take advantage of backend optimization of marker rendering. No, this is 
not obvious!
Eric

Hello,
I am looking for an way to set the width of the tick lines in a plot. 
I have not found any rc parameter for this.
Doing:
plot(...)
c=gca()
tl=c.get_ticklines()
gives a list of tickline objects. Every tickline object has a method 
tl[0].set_linewidth(). Calling this method with different float 
parameters seems to have no effect.
Thanks for any hint on this,
	Torsten. 

Did you try
 raw_input("hit enter")
?
On 8/21/07, Wolfgang Kerzendorf <wke...@go...> wrote:
> Hello,
>
> I am currently writing a data reduction program. I want to use pylab in
> a script and use interactive input of pylab. The problem is that in
> ipython -pylab the script just keeps going without waiting for input (I
> have just tested it by plotting something but did not do
> cid=connect....). In ipython I also have the trouble that the first time
> I call show the shell waits until the window is closed.
>
> Well to simplify my question: How do I decide if pylab just shows the
> plot or if it waits for input in a script?
>
> thanks
> Wolfgang
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Hello,
I am currently writing a data reduction program. I want to use pylab in
a script and use interactive input of pylab. The problem is that in
ipython -pylab the script just keeps going without waiting for input (I
have just tested it by plotting something but did not do
cid=connect....). In ipython I also have the trouble that the first time
I call show the shell waits until the window is closed.
Well to simplify my question: How do I decide if pylab just shows the
plot or if it waits for input in a script?
thanks
 Wolfgang

On 8/21/07, Geoffrey Zhu <zyz...@gm...> wrote:
> Hi Everyone,
>
> I just started to use pylab, and there are two issues I can't figure
> out a way to get around.
>
> 1. show() does not return until I close the plot window. This makes it
> impossible to show multiple plots at the same time. How can I show
> multiple plots?
The way pylab displays things requires you to have an active GUI main
loop running in order for the plots to show up and be active. One
way around it is to use the ipython -pylab mode. This starts the GUI
in a thread and does some magic behind the scenes so that you can keep
typing at the prompt while a figure is showing.
If you're trying to show multiple plots from a program and you don't
want to block, I wrote a pylab plot server called ez_plot that you may
find of use. You can get it from pypi or via "easy_install ez_plot".
 Basically when you call ez_plot.Plotter().<pylab command> it packs
the method name and all its arguments up and sends it to the plot
server to plot. If the server isn't running it starts one up. The
plot server is just a separate process that sits around waiting for
people to send it plotting commands. But since it's a separate
process it can sit in the GUI loop without affecting the control flow
of your code.
I use it mostly for debugging. You can do something like this in the
header of your python file to switch back and forth:
if debug:
 import ez_plot
 Plot = ez_plot.Plotter()
else:
 from matplotlib import pylab as Plot
> 2. How can I get a handle or object reference to the plot window so
> that I can manipulate it specifically?
>
> I found some references to the API. The API seems quite different from
> the plot interface and is considerably low-level. So am just wondering
> if using the API is the only way to do these things. It seems to me
> that if plot(...) can return an object reference to the chart winodw,
> all these can easily be solved.
Most commands do return an object that you can manipulate. Again
ipython is a big help here. Just try x = pylab.plot(somethign), and
then you can use ipython's tab completion and such to quickly see what
sort of things you can do with the x you got back.
--bb

On 21/08/07, Geoffrey Zhu <zyz...@gm...> wrote:
> Hi Everyone,
>
> I just started to use pylab, and there are two issues I can't figure
> out a way to get around.
>
> 1. show() does not return until I close the plot window. This makes it
> impossible to show multiple plots at the same time. How can I show
> multiple plots?
>
> 2. How can I get a handle or object reference to the plot window so
> that I can manipulate it specifically?
Is this what you're after?
import pylab as p
f0 = p.figure()
f1 = p.figure()
ax0 = f0.add_subplot(111)
ax0.plot(data)
ax1 = f1.add_subplot(111)
ax1.plot(otherdata)
> I found some references to the API. The API seems quite different from
> the plot interface and is considerably low-level. So am just wondering
> if using the API is the only way to do these things. It seems to me
> that if plot(...) can return an object reference to the chart winodw,
> all these can easily be solved.
>
> Thanks,
> Geoffrey
-- 
AJC McMorland, PhD Student
Physiology, University of Auckland

Hi Everyone,
I just started to use pylab, and there are two issues I can't figure
out a way to get around.
1. show() does not return until I close the plot window. This makes it
impossible to show multiple plots at the same time. How can I show
multiple plots?
2. How can I get a handle or object reference to the plot window so
that I can manipulate it specifically?
I found some references to the API. The API seems quite different from
the plot interface and is considerably low-level. So am just wondering
if using the API is the only way to do these things. It seems to me
that if plot(...) can return an object reference to the chart winodw,
all these can easily be solved.
Thanks,
Geoffrey