Re: [matplotlib-devel] contourf segfaults
Eric, It appears to be caused by an infinite loop, and may well be due to my changes. I'll take a look on Wednesday and get back to you. Ian On 22 February 2010 01:07, Eric Firing wrote: > Ian, > > I hit a bug (segfault) in cntr.c that is likely related to your changes. It > is ID 2956378 in the tracker. Sample script and data file are there. Will > you be able to take a look soon? > > (Not sure whether the following link will work for you.) > https://sourceforge.net/tracker/?func=detail&aid=2956378&group_id=80706&atid=560720 > > Thanks. > > Eric > -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Path length in the cairo backend
Can you write it in such a way that the check is only removed on cairo <
1.8? My employer is still standardized on RHEL4, for example, which has
cairo 1.2.
Mike
Michiel de Hoon wrote:
> Dear all,
>
> The draw_path method in backend_cairo.py starts with a check for the number
> of vertices in the path, and raises an error if the path contains more than
> 18980 vertices:
>
> def draw_path(self, gc, path, transform, rgbFace=None):
> if len(path.vertices) > 18980:
> raise ValueError("The Cairo backend can not draw paths longer
> than 18980 points.")
>
> This was needed in the past when cairo version 1.4.10 / pycairo version 1.4.0
> would segfault:
>
> http://sourceforge.net/mailarchive/message.php?msg_name=487E2E78.1050501%40stsci.edu
>
> However, we're now at cairo, pycairo version 1.8.8, and I haven't seen any
> segfaults after removing this check.
>
> Does anybody object if I remove this check from the code?
>
> --Michiel.
>
>
>
>
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> Matplotlib-devel mailing list
> Matplotlib-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
--
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Path length in the cairo backend
Sorry -- I meant remove the check for cairo >= 1.8.
Michael Droettboom wrote:
> Can you write it in such a way that the check is only removed on cairo <
> 1.8? My employer is still standardized on RHEL4, for example, which has
> cairo 1.2.
>
> Mike
>
> Michiel de Hoon wrote:
>
>> Dear all,
>>
>> The draw_path method in backend_cairo.py starts with a check for the number
>> of vertices in the path, and raises an error if the path contains more than
>> 18980 vertices:
>>
>> def draw_path(self, gc, path, transform, rgbFace=None):
>> if len(path.vertices) > 18980:
>> raise ValueError("The Cairo backend can not draw paths longer
>> than 18980 points.")
>>
>> This was needed in the past when cairo version 1.4.10 / pycairo version
>> 1.4.0 would segfault:
>>
>> http://sourceforge.net/mailarchive/message.php?msg_name=487E2E78.1050501%40stsci.edu
>>
>> However, we're now at cairo, pycairo version 1.8.8, and I haven't seen any
>> segfaults after removing this check.
>>
>> Does anybody object if I remove this check from the code?
>>
>> --Michiel.
>>
>>
>>
>>
>>
>> --
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> ___
>> Matplotlib-devel mailing list
>> Matplotlib-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>>
>
>
--
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] quick 'n dirty favorite
ok, this is how i do it pro'ly could make this better ./plot file.dat just does the first two columns needs smarts Tom Holroyd wrote: here's the old way cut and paste some numbers from a web page like the number of live births by year dump it in a file named moo run gnuplot and say plot '/tmp/moo' w l 3 boom default graph to show friends the thing is in the new way [python import pylab plot show] what's the best default graph i wanna say what? ipython -c 'readplotfile blah ... parse file ugh ...' um i need a one liner ya know find the baby boom 19102777000 30.1 19152965000 29.5 1920295 27.7 19252909000 25.1 19302618000 21.3 19352377000 18.7 19402559000 19.4 19452858000 20.4 19503632000 24.1 1952 3913000 25.1 1953 3965000 25.1 1954 4078000 25.3 19554104000 25.0 1956 4218000 25.2 1957 4308000 25.3 1958 4255000 24.5 1959 4295000 24.3 1960 4257850 23.7 1961 4268326 23.3 1962 4167362 22.4 1963 4098020 21.7 1964 4027490 21.0 1965 3760358 19.4 1966 3606274 18.4 1967 3520959 17.8 1968 3501564 17.5 1969 3600206 17.8 1970 3731386 18.4 1971 3555970 17.2 19723258411 15.6 19733136965 14.9 19743159958 14.9 19753144198 14.8 19763167788 14.8 19773326632 15.4 1978279 15.3 19793494398 15.9 19803612258 15.9 19823680537 15.9 19833638933 15.5 19843669141 15.5 19853760561 15.8 19863731000 15.5 19873829000 15.7 19883913000 15.9 19894021000 16.2 19904179000 16.7 19914111000 16.2 19924084000 16.0 19934039000 15.7 19943979000 15.3 19953892000 14.8 19963899000 14.7 19973882000 14.5 19983941553 14.6 19993959417 14.5 20004058814 14.7 20014025933 14.1 20024021726 13.9 20034089950 14.1 20044112052 14.0 20054138349 14.0 -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel -- Dr. Tom --- I would dance and be merry, Life would be a ding-a-derry, If I only had a brain. -- The Scarecrow #! /usr/bin/env python import sys if len(sys.argv) != 2: print 'usage: %s file' % sys.argv[0] sys.exit() file = sys.argv[1] ll = open(file).readlines() c = len(ll[0].split()) r = len(ll) import numpy a = numpy.zeros((r, c)) for i in range(r): a[i] = map(float, ll[i].split()) import pylab pylab.plot(a[:,0], a[:,1]) pylab.show() -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Path length in the cairo backend
Michiel de Hoon wrote:
> Dear all,
>
> The draw_path method in backend_cairo.py starts with a check for the number
> of vertices in the path, and raises an error if the path contains more than
> 18980 vertices:
>
> def draw_path(self, gc, path, transform, rgbFace=None):
> if len(path.vertices) > 18980:
> raise ValueError("The Cairo backend can not draw paths longer
> than 18980 points.")
>
> This was needed in the past when cairo version 1.4.10 / pycairo version 1.4.0
> would segfault:
>
> http://sourceforge.net/mailarchive/message.php?msg_name=487E2E78.1050501%40stsci.edu
>
> However, we're now at cairo, pycairo version 1.8.8, and I haven't seen any
> segfaults after removing this check.
>
Is path simplification in effect? If so, have you tested after turning
simplification off, so that you can be sure how many points cairo is
trying to plot?
Eric
> Does anybody object if I remove this check from the code?
>
> --Michiel.
>
>
>
>
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> Matplotlib-devel mailing list
> Matplotlib-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] quick 'n dirty favorite
On Mon, Feb 22, 2010 at 11:00 AM, Tom Holroyd (NIH/NIMH) [E]
wrote:
> ok, this is how i do it
> pro'ly could make this better
python -c "import pylab; pylab.plotfile('temp.dat', cols=(0,2),
delimiter=' '); pylab.show()"
JDH
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] quick 'n dirty favorite
sweet!
John Hunter wrote:
> On Mon, Feb 22, 2010 at 11:00 AM, Tom Holroyd (NIH/NIMH) [E]
> wrote:
>> ok, this is how i do it
>> pro'ly could make this better
>
> python -c "import pylab; pylab.plotfile('temp.dat', cols=(0,2),
> delimiter=' '); pylab.show()"
>
> JDH
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> Matplotlib-devel mailing list
> Matplotlib-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
--
Dr. Tom
---
I would dance and be merry,
Life would be a ding-a-derry,
If I only had a brain.
-- The Scarecrow
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Path length in the cairo backend
Yes I tried without path simplification, and I don't get any crashes. If we
need to support older versions of cairo / pycairo, I suggest that we have the
path length check after checking the version of cairo / pycairo, and that we
perform the path length check after path simplification, so we know how many
points will actually be drawn.
--Michiel.
--- On Mon, 2/22/10, Eric Firing wrote:
> From: Eric Firing
> Subject: Re: [matplotlib-devel] Path length in the cairo backend
> To: "Michiel de Hoon"
> Cc: matplotlib-devel@lists.sourceforge.net
> Date: Monday, February 22, 2010, 1:00 PM
> Michiel de Hoon wrote:
> > Dear all,
> >
> > The draw_path method in backend_cairo.py starts with a
> check for the number of vertices in the path, and raises an
> error if the path contains more than 18980 vertices:
> >
> > def draw_path(self, gc, path,
> transform, rgbFace=None):
> > if
> len(path.vertices) > 18980:
> > raise
> ValueError("The Cairo backend can not draw paths longer than
> 18980 points.")
> >
> > This was needed in the past when cairo version 1.4.10
> / pycairo version 1.4.0 would segfault:
> >
> > http://sourceforge.net/mailarchive/message.php?msg_name=487E2E78.1050501%40stsci.edu
> >
> > However, we're now at cairo, pycairo version 1.8.8,
> and I haven't seen any segfaults after removing this check.
> >
>
> Is path simplification in effect? If so, have you
> tested after turning simplification off, so that you can be
> sure how many points cairo is trying to plot?
>
> Eric
>
>
> > Does anybody object if I remove this check from the
> code?
> >
> > --Michiel.
> >
> >
> >
> >
> >
> --
> > Download Intel® Parallel Studio Eval
> > Try the new software tools for yourself. Speed
> compiling, find bugs
> > proactively, and fine-tune applications for parallel
> performance.
> > See why Intel Parallel Studio got high marks during
> beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > ___
> > Matplotlib-devel mailing list
> > Matplotlib-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
