matplotlib-devel Mailing List for matplotlib

Hi Jon,
Good point, I forgot about that!
It's available for cloning now: git clone
http://qtwork.nano.tudelft.nl/public_git/users/rwh/mplot3d
Cheers,
Reinier
On Wed, Mar 11, 2009 at 6:43 PM, Jonathan Taylor
<jon...@ut...> wrote:
> Hi, that is great! Can you give me a git repository address to pull
> from? I can't from the web viewer.
>
> Thanks,
> J.
>
> On Wed, Mar 11, 2009 at 4:25 AM, Reinier Heeres <re...@he...> wrote:
>> Hi,
>>
>> I updated my patch a bit more, and now all tests are running (try
>> "python axes3d.py"). Only the contourf3D is not working correctly yet,
>> but I'm sure it's fixable soon. There are also some obvious bugs (e.g.
>> the semi-3D histograms are not depth-sorted).
>>
>> Anyway, I have applied the commit in a different git repo that also
>> has gitweb.cgi for viewing:
>> http://qtwork.nano.tudelft.nl/cgi-bin/gitweb.cgi?p=users/rwh/mplot3d;a=summary
>>
>> Jon, I got rid of the spurious commit-and-revert entries but included
>> your latest commits; perhaps you can clone from this tree now?
>>
>> Although I've not had a close look at the BSD license it definitely
>> sounds like a good idea to add it if it applies to the original code.
>> Shall we try to work to some sort of easily-installable form of the
>> again-working code?
>>
>> Regards,
>> Reinier
>>
>> On Mon, Mar 9, 2009 at 3:45 AM, Jonathan Taylor
>> <jon...@ut...> wrote:
>>> Hi Reinier,
>>>
>>> Awesome. Those plots are making me smile! I also agree with your
>>> refactoring and have applied your patch to my git repository.
>>>
>>> I agree with you concerning the sympy plotting routines. I think what
>>> we have here is quite flexible and does a very good job of replicating
>>> the equivalent functionality of MATLAB. I think it would be a huge
>>> effort trying to make 2D plots and 3D plots look consistent if another
>>> approach was taken. Indeed, this is a desirable characteristic. In
>>> addition, the code is actually very short and easy to maintain. Given
>>> that matplotlib has had trouble maintaining 3D code in the past, it
>>> might not be a good idea to switch to a more complicated codebase.
>>>
>>> You should grab some of my more recent changes as I have added a few
>>> more fixes. Most importantly, if you reuse the same figure, the old
>>> event handlers will still attached preventing Axes objects from dieing
>>> and causing interactive manipulation of the plots to be very sluggish.
>>> Also, in terms of performance, I have found that switching to TkAgg
>>> from GTKAgg was helpful.
>>>
>>> Also, I think the original code from John Porter was under a BSD
>>> license. I am thinking of adding our names and the BSD license to the
>>> top of each file to protect it while its not officially part of
>>> matplotlib. What do you think?
>>>
>>> Best,
>>> Jonathan.
>>
>> --
>> Reinier Heeres
-- 
Reinier Heeres
Waalstraat 17
2515 XK Den Haag
The Netherlands
Tel: +31 6 10852639

Eric Firing wrote:
> I have applied your patch, plus related changes to backend_wx and 
> backend_wxagg as suggested by Chris, to the 0.98.5 maintenance branch, 
> and then used svnmerge to propagate the changes to the trunk. (In other 
> words, I judged the changes to be a bug fix rather than a new feature.)
Great, thanks! thanks for taking care of us wx users...
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

On Wed, Mar 11, 2009 at 20:49, Eric Firing <ef...@ha...> wrote:
> I have applied your patch, plus related changes to backend_wx and
> backend_wxagg as suggested by Chris, to the 0.98.5 maintenance branch, and
> then used svnmerge to propagate the changes to the trunk. (In other words,
> I judged the changes to be a bug fix rather than a new feature.)
Yes, indeed they are a bugfix... hence: thanks for merging them!! :)
Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

Sandro Tosi wrote:
> On Fri, Mar 6, 2009 at 22:24, Sandro Tosi <mo...@de...> wrote:
>> On Fri, Mar 6, 2009 at 22:12, Sandro Tosi <mo...@de...> wrote:
>>>>>> import wxversion
>>>>>> wxversion.select('2.8')
>>>>>> from wx import *
>>>>>> wx.__version__
>>> '2.8.7.1'
>>>
>>> That solves the problem of multi-wx on a system.
>>>
>>> What do you think about adding those 2 line into wx examples?
>> Moreover, I will provide a patch to move from
> 
> Here it is the promised patch (sorry for the late, that proves how
> busy I am these days).
> 
> It uses the 'wxversion.ensureMinimal' function as Chris pointed out,
> and move from "from wx import *" to "import wx".
> 
> I tested them on a sys (Debian sid) with both wx2.6 and wx2.8: before
> the patch the examples goes in abort, after they select wx2.8 and uses
> it displaying the windows (even though ex2 and 3 seems a little "too
> compress" do not know if it's due to code or patch ;) ).
Sandro,
I have applied your patch, plus related changes to backend_wx and 
backend_wxagg as suggested by Chris, to the 0.98.5 maintenance branch, 
and then used svnmerge to propagate the changes to the trunk. (In other 
words, I judged the changes to be a bug fix rather than a new feature.)
Eric

a
On Wed, Mar 11, 2009 at 1:29 PM, Jonathan Taylor <
jon...@ut...> wrote:
> Hi John,
>
> You should be able to check out a copy from my git repo via
>
> git clone http://jonathantaylor.ca/mplot3d.git
> cd mplot3d
> git pull
OK thanks.
Just a word of warning. It appears you are developing against an older
version of mpl (0.98?). For example, matplotlib.text.TextWithDash used in
axis3d has been removed from svn HEAD. The attribute self._autoscaleon in
axes3d is no longer available (use self.get_autoscale_on())
As soon as feasible, I suggest getting a svn co of mpl HEAD and working with
that, to speed integration with the main line. You could resurrect
TextWithDash internally for mplot3d if you want, but we found it difficult
to maintain.
JDH

Hi John,
You should be able to check out a copy from my git repo via
git clone http://jonathantaylor.ca/mplot3d.git
cd mplot3d
git pull
I am missing Reiniers final update though but you should be able to
run demo.py and the first few examples in the __name__ == '__main__'
clause of axes3d.py.
Best, J.
On Wed, Mar 11, 2009 at 2:21 PM, John Hunter <jd...@gm...> wrote:
>
>
> On Wed, Mar 11, 2009 at 3:25 AM, Reinier Heeres <re...@he...> wrote:
>>
>> Hi,
>>
>> I updated my patch a bit more, and now all tests are running (try
>> "python axes3d.py"). Only the contourf3D is not working correctly yet,
>> but I'm sure it's fixable soon. There are also some obvious bugs (e.g.
>> the semi-3D histograms are not depth-sorted).
>>
>> Anyway, I have applied the commit in a different git repo that also
>> has gitweb.cgi for viewing:
>>
>> http://qtwork.nano.tudelft.nl/cgi-bin/gitweb.cgi?p=users/rwh/mplot3d;a=summary
>>
>> Jon, I got rid of the spurious commit-and-revert entries but included
>> your latest commits; perhaps you can clone from this tree now?
>>
>> Although I've not had a close look at the BSD license it definitely
>> sounds like a good idea to add it if it applies to the original code.
>> Shall we try to work to some sort of easily-installable form of the
>> again-working code?
>
> One thing you can do is send a patch against lib/mpl-toolkits and I'll apply
> it to svn trunk.
>
> I was briefly scrolling through the recent diffs on art3d, and noticed
>
> +  try:
> +    zs = float(zs)
> +    zs = [zs for i in range(len(paths))]
> +  except:
> +    pass
>
> Except in very special cases, we do not allow blanket excepts -- eg you
> should catch explicitly the error you are trying to trap. Also, it is
> usually better to try just the part you are trying to catch and then do the
> rest in an else. So if you are trying to catch the case where zs is not a
> float
>
> try:
>   zs = float(zs)
> except TypeError:
>   pass
> else:
>   zs = [zs for i in range(len(paths))]
>
>
> Also, again I am not excatly sure what you are trying to do here, mpl has
> "duck typing" helpers to test whether something is iterable or num-like. So
> you can do
>
>
>  import matplotlib.cbook as cbook
>  if not cbook.iterable(zs):
>    zs =float(zs)
>    zs = [zs for i in range(len(paths))]
>
> Anyway -- great work so far. I'm having trouble making a git co work so I
> am looking forward to testing this when you have a snapshot or svn diff.
>
> JDH
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

On Wed, Mar 11, 2009 at 3:25 AM, Reinier Heeres <re...@he...> wrote:
> Hi,
>
> I updated my patch a bit more, and now all tests are running (try
> "python axes3d.py"). Only the contourf3D is not working correctly yet,
> but I'm sure it's fixable soon. There are also some obvious bugs (e.g.
> the semi-3D histograms are not depth-sorted).
>
> Anyway, I have applied the commit in a different git repo that also
> has gitweb.cgi for viewing:
>
> http://qtwork.nano.tudelft.nl/cgi-bin/gitweb.cgi?p=users/rwh/mplot3d;a=summary
>
> Jon, I got rid of the spurious commit-and-revert entries but included
> your latest commits; perhaps you can clone from this tree now?
>
> Although I've not had a close look at the BSD license it definitely
> sounds like a good idea to add it if it applies to the original code.
> Shall we try to work to some sort of easily-installable form of the
> again-working code?
One thing you can do is send a patch against lib/mpl-toolkits and I'll apply
it to svn trunk.
I was briefly scrolling through the recent diffs on art3d, and noticed
+ try:
+ zs = float(zs)
+ zs = [zs for i in range(len(paths))]
+ except:
+ pass
Except in very special cases, we do not allow blanket excepts -- eg you
should catch explicitly the error you are trying to trap. Also, it is
usually better to try just the part you are trying to catch and then do the
rest in an else. So if you are trying to catch the case where zs is not a
float
try:
 zs = float(zs)
except TypeError:
 pass
else:
 zs = [zs for i in range(len(paths))]
Also, again I am not excatly sure what you are trying to do here, mpl has
"duck typing" helpers to test whether something is iterable or num-like. So
you can do
 import matplotlib.cbook as cbook
 if not cbook.iterable(zs):
 zs =float(zs)
 zs = [zs for i in range(len(paths))]
Anyway -- great work so far. I'm having trouble making a git co work so I
am looking forward to testing this when you have a snapshot or svn diff.
JDH

Hi,
What's the status of interactive property editors for mpl graphs?
I would like something that would allow me to change properties such 
as the size and position of the graph, grids, scales, ranges, colors, 
symbols, line styles, fonts, etc., and add annotations. Some of this 
already exists, but allowing users to enter specific values will need 
an underlying widget toolkit.
Does anybody have anything that I can build on for wx?
Thanks,
 - Paul

Hi, that is great! Can you give me a git repository address to pull
from? I can't from the web viewer.
Thanks,
J.
On Wed, Mar 11, 2009 at 4:25 AM, Reinier Heeres <re...@he...> wrote:
> Hi,
>
> I updated my patch a bit more, and now all tests are running (try
> "python axes3d.py"). Only the contourf3D is not working correctly yet,
> but I'm sure it's fixable soon. There are also some obvious bugs (e.g.
> the semi-3D histograms are not depth-sorted).
>
> Anyway, I have applied the commit in a different git repo that also
> has gitweb.cgi for viewing:
> http://qtwork.nano.tudelft.nl/cgi-bin/gitweb.cgi?p=users/rwh/mplot3d;a=summary
>
> Jon, I got rid of the spurious commit-and-revert entries but included
> your latest commits; perhaps you can clone from this tree now?
>
> Although I've not had a close look at the BSD license it definitely
> sounds like a good idea to add it if it applies to the original code.
> Shall we try to work to some sort of easily-installable form of the
> again-working code?
>
> Regards,
> Reinier
>
> On Mon, Mar 9, 2009 at 3:45 AM, Jonathan Taylor
> <jon...@ut...> wrote:
>> Hi Reinier,
>>
>> Awesome. Those plots are making me smile! I also agree with your
>> refactoring and have applied your patch to my git repository.
>>
>> I agree with you concerning the sympy plotting routines. I think what
>> we have here is quite flexible and does a very good job of replicating
>> the equivalent functionality of MATLAB. I think it would be a huge
>> effort trying to make 2D plots and 3D plots look consistent if another
>> approach was taken. Indeed, this is a desirable characteristic. In
>> addition, the code is actually very short and easy to maintain. Given
>> that matplotlib has had trouble maintaining 3D code in the past, it
>> might not be a good idea to switch to a more complicated codebase.
>>
>> You should grab some of my more recent changes as I have added a few
>> more fixes. Most importantly, if you reuse the same figure, the old
>> event handlers will still attached preventing Axes objects from dieing
>> and causing interactive manipulation of the plots to be very sluggish.
>> Also, in terms of performance, I have found that switching to TkAgg
>> from GTKAgg was helpful.
>>
>> Also, I think the original code from John Porter was under a BSD
>> license. I am thinking of adding our names and the BSD license to the
>> top of each file to protect it while its not officially part of
>> matplotlib. What do you think?
>>
>> Best,
>> Jonathan.
>
> --
> Reinier Heeres
> Waalstraat 17
> 2515 XK Den Haag
> The Netherlands
>
> Tel: +31 6 10852639
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Hi,
I updated my patch a bit more, and now all tests are running (try
"python axes3d.py"). Only the contourf3D is not working correctly yet,
but I'm sure it's fixable soon. There are also some obvious bugs (e.g.
the semi-3D histograms are not depth-sorted).
Anyway, I have applied the commit in a different git repo that also
has gitweb.cgi for viewing:
http://qtwork.nano.tudelft.nl/cgi-bin/gitweb.cgi?p=users/rwh/mplot3d;a=summary
Jon, I got rid of the spurious commit-and-revert entries but included
your latest commits; perhaps you can clone from this tree now?
Although I've not had a close look at the BSD license it definitely
sounds like a good idea to add it if it applies to the original code.
Shall we try to work to some sort of easily-installable form of the
again-working code?
Regards,
Reinier
On Mon, Mar 9, 2009 at 3:45 AM, Jonathan Taylor
<jon...@ut...> wrote:
> Hi Reinier,
>
> Awesome. Those plots are making me smile! I also agree with your
> refactoring and have applied your patch to my git repository.
>
> I agree with you concerning the sympy plotting routines. I think what
> we have here is quite flexible and does a very good job of replicating
> the equivalent functionality of MATLAB. I think it would be a huge
> effort trying to make 2D plots and 3D plots look consistent if another
> approach was taken. Indeed, this is a desirable characteristic. In
> addition, the code is actually very short and easy to maintain. Given
> that matplotlib has had trouble maintaining 3D code in the past, it
> might not be a good idea to switch to a more complicated codebase.
>
> You should grab some of my more recent changes as I have added a few
> more fixes. Most importantly, if you reuse the same figure, the old
> event handlers will still attached preventing Axes objects from dieing
> and causing interactive manipulation of the plots to be very sluggish.
> Also, in terms of performance, I have found that switching to TkAgg
> from GTKAgg was helpful.
>
> Also, I think the original code from John Porter was under a BSD
> license. I am thinking of adding our names and the BSD license to the
> top of each file to protect it while its not officially part of
> matplotlib. What do you think?
>
> Best,
> Jonathan.
-- 
Reinier Heeres
Waalstraat 17
2515 XK Den Haag
The Netherlands
Tel: +31 6 10852639