matplotlib-users Mailing List for matplotlib

> > Cocoa-agg works and has been there for the last few releases.
>
> Will it build by default on OS-X?

It is pure python and a bundled nib, so it is included in all distributions=
.

I think 1.4g is the way to go. It's fixed in svn 2252.

On Sunday 02 April 2006 22:55, John Hunter wrote:
> >>>>> "Steve" == Steve Schmerler <el...@gm...> writes:
>
>     Steve> I get strange "histogram-like" plots if the y-axes scale is
>     Steve> some orders of magnitude smaller than the x-axis (latest
>     Steve> svn version).
>
> This appears to be a truncation error due to the formating string we
> use to represent floats in backend_ps.  Darren, should we prefer 1.3e
> instead of 1.3f, or perhaps 1.4e or 1.5e?
>
> JDH
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live
> webcast and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

-- 
Darren S. Dale, Ph.D.
Cornell High Energy Synchrotron Source
Cornell University
200L Wilson Lab
Rt. 366 & Pine Tree Road
Ithaca, NY 14853

dd...@co...
office: (607) 255-9894
fax: (607) 255-9001

John Hunter wrote:
>>>>>>"Steve" == Steve Schmerler <el...@gm...> writes:
> 
> 
>     Steve> I get strange "histogram-like" plots if the y-axes scale is
>     Steve> some orders of magnitude smaller than the x-axis (latest
>     Steve> svn version).
> 
> This appears to be a truncation error due to the formating string we
> use to represent floats in backend_ps.  Darren, should we prefer 1.3e
> instead of 1.3f, or perhaps 1.4e or 1.5e?
> 

Replacing %f by %e and %1.3f by %1.5e in the latest svn version's 
backend_ps.py solves the problem.

cheers,
steve

-- 
Random number generation is the art of producing pure gibberish as 
quickly as possible.

T24gMy8yOS8wNiwgRGl3YWtlciBHdXB0YSA8ZGl3YWtlci5saXN0c0BnbWFpbC5jb20+IHdyb3Rl
Ogo+IEluIGdudXBsb3QsIGFzIG9uZSBwbG90cyBtdWx0aXBsZSBsaW5lcyBvbiB0aGUgc2FtZSBn
cmFwaCwgdGhlIGRlZmF1bHQKPiBiZWhhdmlvciBpcyB0aGF0IGdudXBsb3QgYXV0b21hdGljYWxs
eSBzZWxlY3RzIGxpbmVzdHlsZSwgY29sb3JzIGFuZAo+IG1hcmtlcnMuIEluIG1hdHBsb3RsaWIs
IHRoZSBkZWZhdWx0IGJlaGF2aW9yIChpZiBJIGRvbid0IHNwZWNpZnkKPiBmb3JtYXQgZXRjKSBp
cyB0byBkcmF3IGV2ZXJ5IGxpbmUgaW4gc29saWQgc3R5bGUsIG5vIG1hcmtlcnMsIGJsdWUKPiBj
b2xvci4gSSBtdWNoIHByZWZlciBnbnVwbG90J3MgZGVmYXVsdCBiZWhhdmlvciAtLSBpcyB0aGVy
ZSBzb21lIHdheQo+IG9mIGNvbmZpZ3VyaW5nIG1hdHBsb3RsaWIgdG8gZG8gdGhlIHNhbWU/CgpJ
IGp1c3QgdGVzdGVkIHRoaXMgd2l0aCBtYXRwbG90bGliIDAuODcsIGFuZCByZXBlYXRlZCBjYWxs
cyBvZiBwbG90KCkKd2l0aG91dCBhbnkgc3R5bGUgYXJndW1lbnRzIHByb2R1Y2VzIGxpbmVzIGlu
IHNvbGlkIHN0eWxlLCBubwptYXJrZXJzLCBidXQgZGlmZmVyZW50IGNvbG9ycy4KCkNoZWVycywK
LS0gRGF2ZQpFbWFpbDogZGF2aWQudy5oLmNoaW5AZ21haWwuY29tCg==

Diwaker Gupta wrote:
> Re-sending one last time in case someone has any ideas.
> 
> ============
> In gnuplot, as one plots multiple lines on the same graph, the default
> behavior is that gnuplot automatically selects linestyle, colors and
> markers. In matplotlib, the default behavior (if I don't specify
> format etc) is to draw every line in solid style, no markers, blue
> color. I much prefer gnuplot's default behavior -- is there some way
> of configuring matplotlib to do the same?
> 
> Thanks,
> Diwaker

The short answer is no, this is not configurable.  You can get somewhat 
the same effect with some programming.  Here is a minimal illustration 
in ipython, using the attached module:

In [1]:from cycle_markers import cplot

In [2]:x = arange(0,10, 0.1)

In [3]:y1 = sin(x)

In [4]:y2 = cos(x)

In [5]:cplot(x, y1, x, y2)

If you want to be able to call cplot repeatedly and get the next 
color/marker combination in the cycle each time, you could use a 
generator instead of the simple markers list.

Eric

Re-sending one last time in case someone has any ideas.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
In gnuplot, as one plots multiple lines on the same graph, the default
behavior is that gnuplot automatically selects linestyle, colors and
markers. In matplotlib, the default behavior (if I don't specify
format etc) is to draw every line in solid style, no markers, blue
color. I much prefer gnuplot's default behavior -- is there some way
of configuring matplotlib to do the same?

Thanks,
Diwaker
--
Web/Blog/Gallery: http://floatingsun.net/blog

John Hunter wrote:
>>>>>>"Steve" == Steve Schmerler <el...@gm...> writes:
> 
> 
>     Steve> I get strange "histogram-like" plots if the y-axes scale is
>     Steve> some orders of magnitude smaller than the x-axis (latest
>     Steve> svn version).
> 
> This appears to be a truncation error due to the formating string we
> use to represent floats in backend_ps.  Darren, should we prefer 1.3e
> instead of 1.3f, or perhaps 1.4e or 1.5e?

John, Darren,

I would suggest something like 1.5g, which will be less bulky for common 
cases than 1.5f.

Matlab ps files have all paths already transformed to paper coordinates 
but in very small units (thousandths of an inch?) so that they can be 
given as integers.

Eric

>>>>> "Steve" == Steve Schmerler <el...@gm...> writes:

    Steve> I get strange "histogram-like" plots if the y-axes scale is
    Steve> some orders of magnitude smaller than the x-axis (latest
    Steve> svn version).

This appears to be a truncation error due to the formating string we
use to represent floats in backend_ps.  Darren, should we prefer 1.3e
instead of 1.3f, or perhaps 1.4e or 1.5e?

JDH