matplotlib-users Mailing List for matplotlib

Anthony M. Floyd wrote:
>> -----Original Message-----
>> From: Eric Firing [mailto:ef...@ha...] 
> 
> [snip]
> 
>> It probably comes down to program simplicity and readability, 
>> not speed, in your case.
>>
>> Eric
> 
> 
> Hi Eric,
> 
> Thanks for this. That's essentially the decision I had reached, but I
> was also wondering if I'd missed something significant. I think I will
> code it up as-is right now, and if the routine is unacceptably slow
> re-examine it with an eye to shifting over to using line-collections.
> 
> In the same vein, if I need to refactor, is there any benefit to
> treating single series as a collection with only one segment? I would
> rather treat single series and multiple series in the same manner --
> either plotting single series and multiple single-series or plotting
> single-series collections and multiple-series collections. That is, I'd
> rather not have to treat plotting a single series in one manner and
> multiple series in another.
A collection with only one member should work fine, although I don't 
know whether it has been explicitly tested. So, I don't see any reason 
why you should have to treat a single series as a special case.
Are you aware that the plot method can plot the columns of 2-D arrays? 
Any kwargs apply to all the lines. When plot does this, it makes a list 
of lines, not a line collection, so it is similar to looping over a set 
of single plot commands. There is no particular speed advantage, but it 
is nice and concise, if it yields what you actually want.
Eric
> 
> Thanks,
> Anthony. 
> 
> 

> -----Original Message-----
> From: Eric Firing [mailto:ef...@ha...]=20
[snip]
> It probably comes down to program simplicity and readability,=20
> not speed, in your case.
>=20
> Eric
Hi Eric,
Thanks for this. That's essentially the decision I had reached, but I
was also wondering if I'd missed something significant. I think I will
code it up as-is right now, and if the routine is unacceptably slow
re-examine it with an eye to shifting over to using line-collections.
In the same vein, if I need to refactor, is there any benefit to
treating single series as a collection with only one segment? I would
rather treat single series and multiple series in the same manner --
either plotting single series and multiple single-series or plotting
single-series collections and multiple-series collections. That is, I'd
rather not have to treat plotting a single series in one manner and
multiple series in another.
Thanks,
Anthony.=20

Anthony,
When I do a quick test of line_collection.py versus a modification that 
makes individual plot calls, with the results written to a png file, I 
get about 1.05 s with the collection and 1.2 s with the lines. But a 
trivial plot still takes 0.52 seconds, so if you subtract out this 
general startup overhead the improvement with the line collection is 
about 30%.
It probably comes down to program simplicity and readability, not speed, 
in your case.
Eric
Anthony M. Floyd wrote:
> I'm trying to figure out the best way to handle the following situation:
> I have a wxApp that embeds a matplotlib figure in a panel. I use custom
> code to control adding and removing series from the axes in this figure,
> with some pretty fine grained control on when things get drawn, zoomed,
> etc. To be clear, I'm not using pylab here, I'm coding directly into
> matplotlib.
> 
> Anyhow, I now have the case where I want to be plotting a modest number
> of series (say 100) with a reasonably large density (say >1000 pts).
> These series will all have the same or similar styles (thickness,
> colour, etc) and will definitely have the same length.
> 
> In context of my current app, I could achieve this simply by calling my
> .addSeries routine multiple times. Or, I could use a Line Collection to
> handle them en masse.
> 
> The thing is, after taking a quick read through of the source code, I'm
> not certain that I'm gaining anything by using a line collection in this
> case. 
> 
> I did a quick comparison using the line_collection.py example, and even
> using pylab there didn't seem to be any performance hit to doing:
> 
> lines = [zip(x,y) for y in ys]
> for series in x:
> 	plot(lines[series])
> 
> Instead of using:
> 
> line_segments = ...
> ax.add_collection(line_segments)
> 
> Can anyone give me advice if I should code targeting collections or to
> just use my current single-series code?
> 
> Thanks,
> Anthony.
> 
> 
> 
> --
> Anthony Floyd, PhD
> Convergent Manufacturing Technologies Inc.
> 6190 Agronomy Rd, Suite 403
> Vancouver BC V6T 1Z3
> CANADA
> 
> Email: Ant...@co... | Tel: 604-822-9682
> WWW: http://www.convergent.ca | Fax: 604-822-9659 
> 
> CMT is hiring: See http://www.convergent.ca for details
> 
> 
> 
> -------------------------------------------------------------------------
> 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'm trying to figure out the best way to handle the following situation:
I have a wxApp that embeds a matplotlib figure in a panel. I use custom
code to control adding and removing series from the axes in this figure,
with some pretty fine grained control on when things get drawn, zoomed,
etc. To be clear, I'm not using pylab here, I'm coding directly into
matplotlib.
Anyhow, I now have the case where I want to be plotting a modest number
of series (say 100) with a reasonably large density (say >1000 pts).
These series will all have the same or similar styles (thickness,
colour, etc) and will definitely have the same length.
In context of my current app, I could achieve this simply by calling my
.addSeries routine multiple times. Or, I could use a Line Collection to
handle them en masse.
The thing is, after taking a quick read through of the source code, I'm
not certain that I'm gaining anything by using a line collection in this
case. =20
I did a quick comparison using the line_collection.py example, and even
using pylab there didn't seem to be any performance hit to doing:
lines =3D [zip(x,y) for y in ys]
for series in x:
	plot(lines[series])
Instead of using:
line_segments =3D ...
ax.add_collection(line_segments)
Can anyone give me advice if I should code targeting collections or to
just use my current single-series code?
Thanks,
Anthony.
--
Anthony Floyd, PhD
Convergent Manufacturing Technologies Inc.
6190 Agronomy Rd, Suite 403
Vancouver BC V6T 1Z3
CANADA
Email: Ant...@co... | Tel: 604-822-9682
WWW: http://www.convergent.ca | Fax: 604-822-9659 =20
CMT is hiring: See http://www.convergent.ca for details

That did it.
thanks!
Eric Firing wrote:
> Johann Cohen-Tanugi wrote:
>> hello,
>> I am using matplotlib to make a drawing, so though I am using 
>> distances on the pad I do not need to display the axes and would 
>> rather have no frame and no tick.
>> To achieve this, I tried using :
>> rc('axes', edgecolor='white')
>
> If your axes instance is "ax", try
> ax.set_frame_on(False)
> ax.set_axis_off()
>
> The api is inconsistent, but there it is...
>
> This will actually wipe out the axes patch as well as the boundary, 
> and all traces of the axes; maybe this is more than you want.
>
> Eric
>
>> rc('xtick', color='white')
>> rc('ytick', color='white')
>>
>> The first command works, but not the 2 tick commands (the ticks still 
>> show up, in black)...... Bug or feature? Besides, I am sure there is 
>> a better way to do that, but could not find out.
>> I am using the GTKAgg backend.
>>
>> thanks,
>> Johann
>>
>>
>> ------------------------------------------------------------------------- 
>>
>> 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
>

Johann Cohen-Tanugi wrote:
> hello,
> I am using matplotlib to make a drawing, so though I am using distances 
> on the pad I do not need to display the axes and would rather have no 
> frame and no tick.
> To achieve this, I tried using :
> rc('axes', edgecolor='white')
If your axes instance is "ax", try
 ax.set_frame_on(False)
 ax.set_axis_off()
The api is inconsistent, but there it is...
This will actually wipe out the axes patch as well as the boundary, and 
all traces of the axes; maybe this is more than you want.
Eric
> rc('xtick', color='white')
> rc('ytick', color='white')
> 
> The first command works, but not the 2 tick commands (the ticks still 
> show up, in black)...... Bug or feature? Besides, I am sure there is a 
> better way to do that, but could not find out.
> I am using the GTKAgg backend.
> 
> thanks,
> Johann
> 
> 
> -------------------------------------------------------------------------
> 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 20/08/07, Darren Dale <dd...@co...> wrote:
> On Monday 20 August 2007 12:11:30 pm Samuel M.Smith wrote:
> > I can only generate .eps files that will successfully distill
> > into .pdf files when I use
> >
> > ps.usedistiller : xpdf
> > not
> > ps.usedistiller : ghostscript
> > nor
> > ps.usedistiller : None
> >
> > Is this a known problem?
> > ghostscript does work fine for .ps files just not .eps
>
> 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?
>
> > 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?
Interestingly I just installed ubuntu gutsy AMD64 on my machine (yes I
know it's alpha) and found that I get a strangely similar problem
(with subversion matplotlib). But only if i use *xpdf* as the
distiller, not ghostscript. I also get the same error with the
bounding box / no paper information. I put it down to ubuntu alpha
status rather than matplotlib which is why I didn't report it, but
this has made me think possibly otherwise?? I'll send more details if
you're interested.
John

On 2007年8月20日, Johann Cohen-Tanugi apparently wrote:
> I am sure there is a 
> better way to do that 
Set the ticks to an empty tuple.
hth,
Alan Isaac

hello,
I am using matplotlib to make a drawing, so though I am using distances 
on the pad I do not need to display the axes and would rather have no 
frame and no tick.
To achieve this, I tried using :
rc('axes', edgecolor='white')
rc('xtick', color='white')
rc('ytick', color='white')
The first command works, but not the 2 tick commands (the ticks still 
show up, in black)...... Bug or feature? Besides, I am sure there is a 
better way to do that, but could not find out.
I am using the GTKAgg backend.
thanks,
Johann

On Monday 20 August 2007 12:11:30 pm Samuel M.Smith wrote:
> I can only generate .eps files that will successfully distill
> into .pdf files when I use
>
> ps.usedistiller : xpdf
> not
> ps.usedistiller : ghostscript
> nor
> ps.usedistiller : None
>
> Is this a known problem?
> ghostscript does work fine for .ps files just not .eps
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? 
> 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?

I can only generate .eps files that will successfully distill 
into .pdf files when I use
ps.usedistiller : xpdf
not
ps.usedistiller : ghostscript
nor
 ps.usedistiller : None
Is this a known problem?
ghostscript does work fine for .ps files just not .eps
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?
I have
ps.papersize : letter
my configuration
Mac OS X 10.4.10 PPC
python 2.5.1
Matplotlib 0.90.1
ipython 0.8.1
wxPython2.8-osx-unicode-2.8.3.0-universal10.4-py2.5
ghostscript 8.54
xpdf 3.02
**********************************************************************
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"
**********************************************************************