Joris De Ridder wrote:
> As far as I understand, the algorithm works as follows:
>
> 1) Define what you mean by "dense" points
> a) init what you mean by far_away
> b) start at the first point, and loop over the points until you find one
> far_away
> c) hop to that one, continue loop
[CB]: What is the maximum precision in Postscript? It seems unlikely that
you
[CB]: could plot 80,000 points and not have number of them overlap, unless
[CB]: it's clipped, so removing essentially redundant points may be another
[CB]: way to to go.
This seems to be the way that xm
Alan G Isaac wrote:
> Does anyone really care about 25% enough to make this
> worthwhile? Just wondering.
I tend to think not. You put 80,000 points in a PS, it's going to be
big. That's all there is to it, it's the nature of Postscript.
I do think clipping is a good idea though.
What is the
On Wed, 6 Sep 2006, John apparently wrote:
> could make it an rc param for those who want to trade
> accuracy for space.
Does anyone really care about 25% enough to make this
worthwhile? Just wondering.
Cheers,
Alan Isaac
> "humufr" == humufr <[EMAIL PROTECTED]> writes:
humufr> Another things that can be good to add is a better
humufr> clipping. For the moment there are no clipping that means
humufr> if I have something like::
Here is a little demo that shows you how to do a line that clips
itself
Le mercredi 6 septembre 2006 09:49, Darren Dale a écrit :
> On Wednesday 06 September 2006 07:49, [EMAIL PROTECTED] wrote:
> > Hi,
> >
> > The following plot
> >
> > >>> from numarray import *
> > >>> x = arange(8)
> > >>> from pylab import plot,show
> > >>> plot(x,x)
> > >>> show()
> >
> > and
On Wednesday 06 September 2006 09:49, John Hunter wrote:
> > "Darren" == Darren Dale <[EMAIL PROTECTED]> writes:
>
> Darren> which is 17 bytes long. 17*8 = 1.36MB. Maybe we dont
> Darren> need as many sig figs, that could cut the size down by
> Darren> maybe 25%.
>
> We could ma
> "Darren" == Darren Dale <[EMAIL PROTECTED]> writes:
Darren> which is 17 bytes long. 17*8 = 1.36MB. Maybe we dont
Darren> need as many sig figs, that could cut the size down by
Darren> maybe 25%.
We could make the fmt string for PS and SVG output floats a
configurable parame
> "joris" == joris <[EMAIL PROTECTED]> writes:
joris> Hi, The following plot
from numarray import * x = arange(8) from pylab import
plot,show plot(x,x) show()
joris> and saving in postscript format generated a file of 1.5MB,
joris> while the equivalent is o
On Wednesday 06 September 2006 07:49, [EMAIL PROTECTED] wrote:
> Hi,
>
> The following plot
>
> >>> from numarray import *
> >>> x = arange(8)
> >>> from pylab import plot,show
> >>> plot(x,x)
> >>> show()
>
> and saving in postscript format generated a file of 1.5MB, while the
> equivalent is
I cannot help you with making matplotlib create smaller files but sam2p is an image
conversion program that creates small files. You might be able to
convert your file to make it smaller.
Bill
[EMAIL PROTECTED] wrote:
Hi,
The following plot
from numarray import
Hi,
The following plot
>>> from numarray import *
>>> x = arange(8)
>>> from pylab import plot,show
>>> plot(x,x)
>>> show()
and saving in postscript format generated a file of 1.5MB, while the equivalent
is
only 288KB in xmgrace (another plotting program). If I use plot(x,x,"k,"), this
ev
12 matches
Mail list logo
