matplotlib-devel Mailing List for matplotlib

Travis,

I think the big problem is in numerix, not scipy.  The builtin min and 
scipy amin are getting confused, so that min is being called when amin 
should be; almost all the extra time is in calls to min and max.

I can't sort it out right now, but I may be able to get to it this 
evening--but maybe someone will beat me to it!

Once that numerix problem is fixed, I expect the timing difference 
between scipy and Numeric for the mpl demos will be small, and can be 
checked at leisure.

Eric

Travis Oliphant wrote:
> Eric Firing wrote:
> 
>> John,
>>
>> Something must not have gotten rebuilt when it should have; removing 
>> build and doing a complete rebuilt (with and without VERBOSE) solved 
>> the problem. So, --scipy is now working with svn version of scipy and 
>> cvs version of matplotlib--at least for the few demos I have tested so 
>> far.
>>
>> Speed is disappointing, though; contour_demo on my machine takes twice 
>> as long with scipy as with Numeric.
> 
> 
> We'll start looking at speed issues more closely soon.    There are 
> several optimizations planned already, but it would be nice to get some 
> real-world experience as to what is actually slow and what isn't.  Some 
> thing will always be slower, but I'd like to get rid of any obvious, and 
> unnecesary slow-downs.
> 
> Good benchmark data is very helpful for this exercise.  So, if you could 
> determine exactly what operations are slower in contour demo that would 
> be very helpful.
> One issue is that backward-compatibility is achieved by going throw 
> another layer of function calls.   This will always introduce something 
> of a slow-down.    I will continue to work to make things as fast as 
> they can be.   There were a lot of new features added and there has been 
> very-little time spent on optimization. 
> -Travis.
> 
> 
> 

I've made a small alteration to my code for AFM mathtext to show digits
and brackets () in the roman rather than the italic font, as is normal
in mathtext.  The patch is attached.

Nicholas

Alright, I'll give it a shot and let you know.

On 12/7/05, John Hunter <jdh...@ac...> wrote:
> >>>>> "Charlie" =3D=3D Charlie Moad <cw...@gm...> writes:
>
>     Charlie> Would it be considered cleaner to embed the mpl data into
>     Charlie> the matplotlib module?  This would make it easier to
>     Charlie> clean a mpl install.  The data path could be expressed
>     Charlie> fairly easily too, as a one-liner:
>
>     Charlie> os.sep.join([os.path.split(matplotlib.__file__)[0],
>     Charlie> 'matplotlib-data'])
>
> Yes, if you can engineer in a way that works with setup w/ and w/o a
> --prefix arg it would be preferable, in my view.
>
> JDH
>

>>>>> "Charlie" == Charlie Moad <cw...@gm...> writes:

    Charlie> Would it be considered cleaner to embed the mpl data into
    Charlie> the matplotlib module?  This would make it easier to
    Charlie> clean a mpl install.  The data path could be expressed
    Charlie> fairly easily too, as a one-liner:

    Charlie> os.sep.join([os.path.split(matplotlib.__file__)[0],
    Charlie> 'matplotlib-data'])

Yes, if you can engineer in a way that works with setup w/ and w/o a
--prefix arg it would be preferable, in my view.

JDH

Would it be considered cleaner to embed the mpl data into the
matplotlib module?  This would make it easier to clean a mpl install.=20
The data path could be expressed fairly easily too, as a one-liner:

os.sep.join([os.path.split(matplotlib.__file__)[0], 'matplotlib-data'])

Just a thought.....

- Charlie

John,

Something must not have gotten rebuilt when it should have; removing 
build and doing a complete rebuilt (with and without VERBOSE) solved the 
problem. So, --scipy is now working with svn version of scipy and cvs 
version of matplotlib--at least for the few demos I have tested so far.

Speed is disappointing, though; contour_demo on my machine takes twice 
as long with scipy as with Numeric.

Eric

John Hunter wrote:
>>>>>>"Eric" == Eric Firing <ef...@ha...> writes:
> 
> 
>     Eric> John, I found and fixed more missing bits of scipy support;
>     Eric> changes are in cvs.  With the svn version of scipy, though,
>     Eric> I have not yet been able to make everything work.  I am
>     Eric> getting segfaults.  It might be a simple typo somewhere.
> 
> You might try rm -rf build and then turn VERBOSE on in setup.py and
> rebuilding.  That might give you a good clue where the segfault is
> happening.  Do you see the crash in Agg and PS?
> 
> JDH