Re: [matplotlib-devel] strange alpha legend bug

2007-03-01 Thread Perry Greenfield

On Mar 1, 2007, at 10:15 AM, John Hunter wrote:

> On 3/1/07, Jouni K. Seppänen <[EMAIL PROTECTED]> wrote:
>> I committed the following change, which seems to fix the bug.
>
>> -handles = ax.lines
>> +handles = ax.lines[:]
>
> Wow, nasty and subtle.  Good work!  Now how do I get a doughnut to you
> in Finland :-)  Any ideas Perry?

What, you didn't like the way I did it? ;-)
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] when to deprecate numeric and numarray?

2007-04-04 Thread Perry Greenfield

On Apr 4, 2007, at 9:41 AM, John Hunter wrote:

> On 4/4/07, Andrew Straw <[EMAIL PROTECTED]> wrote:
>
>> Do we add deprecation warnings for the 0.90+1 release cycle and then
>> stop building the numarray and numeric numerix backends at some point
>> after that? When? Do we keep the "numerix" name or just switch
>> everything to numpy?
>
> I agree that it is about time to begin preparing for the switch.  I
> was talking to Perry the other day about what an irony it was for him
> when he was writing the colormap support in mpl that he had to use all
> the takes and puts after spending so much effort in numarray to get
> more natural indexing and other features.  So I think most everyone is
> ready to jettison the old stuff and move forward with the new.  I've
> been waiting for the green light from STScI that they are mostly
> finished with their numarray->numpy migration since they have made
> significant contributions to mpl (and numerix) and if I recall
> correctly, I think Perry said they were mostly done, which means we
> should go forward.  Perry?

We are done internally for all our released software and have  
propagated these changes to our internal users (just this week as a  
matter of fact). The most convenient time to remove the support for  
numarray for us is when we make a public release of our software. The  
date isn't fixed yet but that would probably be in June sometime. The  
reason it is convenient for us to retain the numarray compatibility  
until then is that we release a bunch of things together that people  
can get as one download; taking numarray support out of mpl before  
then means that people with the existing release will have to install  
numpy if they want to upgrade mpl (and also face some confusion about  
what kind of array object they are dealing with if they use functions  
within mpl that create arrays).

Having said that, I've told John that I hate having held up the date  
that the transition to pure numpy in mpl can be accomplished by, and  
that if he wants to he can go ahead with it. So far he has been very  
kind in waiting for us to finish our transition to numpy. So to  
summarize on our end, the conversion to numpy has been completed and  
tested by our developers, and now is being tested by our  
institutional users, and sometime around June we will release our new  
software. At that point, we have no desire or need to have any  
further numarray option in mpl. I'll leave it to John to decide if he  
wants to go ahead with that conversion in mpl now. The effect on our  
user community probably isn't going to be great. By the time it is  
done in mpl and is available to our community there should only be a  
couple months, at most, where our users will have to deal with the  
issue (and they can either wait to upgrade mpl after we release, or  
deal with the installation/array issues that arise for the relatively  
short duration.

Perry


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] SaveFig bug in TkAgg backend

2007-05-18 Thread Perry Greenfield
We don't have anyone at the moment that can work on it, but I think  
on the order of a month or two we can. We see similar issues too. So  
if someone can deal with it before then, that would be great, but  
we'll tackle it before very long if not.

Perry

On May 18, 2007, at 7:21 AM, Mark Bakker wrote:

> This is a well known problem, reported about a year or so ago.
> John Hunter tried to get some help on the (TK?) mailinglist, but I
> don't think anybody responded. I looked into it too, but couldn't find
> a solution (that doesn't mean much, except for that it is not
> blatently obvious).
> It would be great if somebody would know how to fix this.
> Strangely enough I have written a GUI myself where I use the toolbar,
> and the save button works fine there.
> Mark


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] negative log transforms

2007-07-17 Thread Perry Greenfield
This is exactly the sort of thing that I thought a transform approach  
would make easier to do. So if it isn't urgent, waiting probably  
would be better. (by the way, we see exactly the same sort of log  
scale you propose in one of our older (non-python) packages. So there  
is a call for this sort of thing.

Perry

On Jul 17, 2007, at 10:36 AM, Paul Kienzle wrote:

> On Tue, Jul 17, 2007 at 08:33:47AM -0500, John Hunter wrote:
>> Speaking of branches, we may need to seriously consider a branch  
>> here,
>> mpl1.  The changes here may involve breaking a fair amount of code,
>> which I don't mind doing to get it right, but I'm somewhat  
>> inclined to
>> branch off here for matplotlib1.0, with the goal of using traits,
>> fixing axis handling (eg multiple y-axis with arbitrary placement),
>> and rewriting the transforms.
>
> On the topic of transforms,  I would like to be able to do dynamic  
> range
> compression on a decaying oscillatory signal.  Think of it as a  
> logarithmic
> axis which supports negative numbers.  AFAICT, the current transform
> infrastructure does not allow me to add this as a third party package.
>
> The axis would look something like:
>
>   |-  10**2
>   |
>   |-  10**1
>   |
>   |-  10**0
>   |
>   |-  10**-1
>   |
>   |-  0
>   |
>   |- -10**-1
>   |
>   |- -10**0
>
> As well as a max and min parameter, there would have to be a cutoff
> parameter.  For auto axes, choose a cutoff which allows a reasonable
> number of decades to be displayed (I'm guessing reasonable is seven).
>
> The transform would be something like the following:
>
> if (x[i] > cut) newx[i] = log10(x[i]) - log10cut;
> else if (x[i] < -cut) newx[i] = log10cut - log10(-x[i]);
> else newx[i] = 0.;
>
> with inverse:
>
> if (x[i] < 0) newx[i] = -pow(10.0, log10cut - x[i]);
> else if (x[i] > 0) newx[i] = pow(10.0, x[i] - log10cut);
> else x[i] = 0.
>
> Even extending the current LOG10 support would present a challenge of
> how to get the cut value into the transform.
>
> Suggestions how I can implement this in the current architecture, or
> should I wait for the new transforms code?
>
>   - Paul
>
>
> -- 
> ---
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> ___
> Matplotlib-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] future of mpl documentation

2008-06-01 Thread Perry Greenfield
I'm not sure either, it was something simple like having problems  
building and John suggesting that I blow away the previous  
installation. But I indeed did eventually mail the doughnut.

Perry

On May 31, 2008, at 10:35 PM, John Hunter wrote:

> On Sat, May 31, 2008 at 3:19 PM, Darren Dale  
> <[EMAIL PROTECTED]> wrote:
>
>   Darren> I have to break here for the weekend, I'll be back monday  
> afternoon.
>   Darren> Leave some for me! (although I'll owe doughnut to whoever  
> can fix the
>   Darren> arrow docstring).
>
>   John> I'll claim that doughnut.
>
>   Darren> When was the last time you received one in the mail?
>
> Well, I remember the last time quite clearly, when Perry sent me a
> doughnut in the mail from Maryland to settle a "dollars-to doughnuts"
> bet.  Unfortunately, I  can't remember the subject of the bet right
> now (Perry?), though I kept the doughnut in my freezer, in the
> addressed envelope, for many months as a souvenir.
>
> JDH


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] ANN: Michael Droettboom, matplotlib lead developer

2012-08-02 Thread Perry Greenfield

On Aug 2, 2012, at 5:25 PM, John Hunter wrote:

>
> I also extend my heartfelt thanks to Perry Greenfield and STScI.  They
> have been supporting matplotlib since 2004 with ideas, code and
> developer resources.  They employ Michael currently, and are part of
> the reason why he is able to take on the leadership of this large
> project.
>
John, it has been our great fortune have joined the matplotlib effort.  
It saved us an enormous effort. It has been an incredible pleasure  
working with you. I'm not sure you realize how very much Mike and I  
hope you can rejoin the matplotlib effort. It will always be there for  
you.

Perry

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel