On Mon, Apr 13, 2009 at 5:40 PM, Reinier Heeres wrote:
> Hi,
>
> Should be working now: I did commit and push my changes, but forgot to
> update the http indices (that was a real head-breaker!).
>
> Instead of demo.py it is nicer to try "python axes3d.py".
>
> Hope it works!
Worked beautifully --
Hi,
Should be working now: I did commit and push my changes, but forgot to
update the http indices (that was a real head-breaker!).
Instead of demo.py it is nicer to try "python axes3d.py".
Hope it works!
Cheers,
Reinier
On Mon, Apr 13, 2009 at 6:51 PM, John Hunter wrote:
> On Sun, Apr 12, 20
On Sun, Apr 12, 2009 at 6:09 PM, Reinier Heeres wrote:
> Hi,
>
> It took me a while to get this done, but I managed to make mplot3d
> working with svn trunk again!
Hmm, this does not seem to be against svn HEAD on the trunk. I cloned
your repo with
> git clone http://qtwork.nano.tudelft.nl/pu
Hi,
It took me a while to get this done, but I managed to make mplot3d
working with svn trunk again!
It's available for viewing at
http://qtwork.nano.tudelft.nl/cgi-bin/gitweb.cgi?p=users/rwh/mplot3d;a=summary.
An http link to clone it is on that same page.
JDH: If there are no further issues wi
Hey Reiner -- please make sure you "reply-to-all" so others can
participate in the thread. I'm am CC-ing the reply to the list.
On Wed, Apr 1, 2009 at 5:19 PM, Reinier Heeres wrote:
> That is one issue, but if I try to solve that I get some
> strange-looking result. It seems that the patches I
On Mon, Mar 30, 2009 at 2:13 AM, Reinier Heeres wrote:
>
> That sounds good. I assume you mean adding it to lib/mpl_toolkits in
> the matplotlib source? It would be great to do this soon.
>
> I also tried to create a separate mpl_toolkit installer with
> setuptools, but can't get that to work pro
Hi,
I think that except for contourf3D everything is functioning fine
again, so I'm thinking about packaging/distributing it. (I will try to
fix contourf3D as well when I can find some time)
2009/3/3 John Hunter :
>
>
> On Mon, Mar 2, 2009 at 10:13 PM, Jonathan Taylor
> wrote:
>>
>> Hi,
>>
>> I
Hi all,
I reworked the code in axis3d so that the XYZ-planes are always behind
the object you're plotting. I also updated the label/ticks drawing a
bit and dropped a lot of unnecessary code. I pushed it to my git repo
at
http://qtwork.nano.tudelft.nl/cgi-bin/gitweb.cgi?p=users/rwh/mplot3d;a=summa
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
wrote:
> Hi, that is great! Can you give me a git repository address to pull
> from?
a
On Wed, Mar 11, 2009 at 1:29 PM, Jonathan Taylor <
jonathan.tay...@utoronto.ca> 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
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.
B
On Wed, Mar 11, 2009 at 3:25 AM, Reinier Heeres 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 histog
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 wrote:
> Hi,
>
> I updated my patch a bit more, and now all tests are running (try
> "python axes3d.py"). Only the contourf3D is not
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
On Mon, Mar 9, 2009 at 2:39 PM, Jonathan Taylor
wrote:
> Sure, I thought it was going to the list too ;) So no problem.
>
> I am not sure what you can do with that module. It seems a shame to
> waste. Perhaps it should be split out into a seperate 3d only
> plotting library that cares less abou
Sure, I thought it was going to the list too ;) So no problem.
I am not sure what you can do with that module. It seems a shame to
waste. Perhaps it should be split out into a seperate 3d only
plotting library that cares less about being matplotlib'ish than
something packaged with MPL would. W
On Mon, Mar 9, 2009 at 2:34 PM, Ondrej Certik wrote:
> I posted only to you by a mistake -- can I reply to the list?
Oops, I posted to the list by mistake too -- sorry about it. Anyway,
here is the email that I sent to Jonathan only by a mistake:
On Sun, Mar 8, 2009 at 9:44 PM, Jonathan Taylor
I posted only to you by a mistake -- can I reply to the list?
On Mon, Mar 9, 2009 at 2:20 PM, Jonathan Taylor
wrote:
> I think that it would be a little bit more complicated than that. I
> believe that the current backends act as a canvas that you paint onto.
> I do not think an OpenGL "canvas"
Just because we are using all the 2D drawing code to make the plots,
which is why the 3d code is so small, maintainable and is visually
consistent with 2D matplotlib. I believe that moving to OpenGL would
require a substantial effort.
J
On Mon, Mar 9, 2009 at 12:17 AM, Ondrej Certik wrote:
> On
On Sun, Mar 8, 2009 at 9:01 PM, Jonathan Taylor
wrote:
> Hi,
>
> Thanks for the patch. How slow is it for you? I find it slow but
Well, when I use mouse to rotate the image, I can see that it lags behind.
> quite usable. The main problem, I imagine, is that sympy is using
> OpenGL and thus yo
Hi,
Thanks for the patch. How slow is it for you? I find it slow but
quite usable. The main problem, I imagine, is that sympy is using
OpenGL and thus your graphics card performs all the 3d -> 2d rendering
whereas we do much of this in python/numpy. When I get a chance I am
going to see if I c
On Sun, Mar 8, 2009 at 7:45 PM, Jonathan Taylor
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 qu
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
Hi,
I've done some further refactoring of mplot3d:
- Almost all of the test plotting functions work, except for
test_bar2D. Filled contours are not perfect yet and need a bit more
work. Try "python axes.py" with the attached files to see how it
looks!
- I removed the Wrap2D class, which was usin
On Thu, Mar 05, 2009 at 07:03:00PM +0100, Cohen-Tanugi Johann wrote:
> Nevertheless, I hate to think of matplotlib sending people to mayavi2 each
> time 3D plotting is needed. Basic functionalities built-in would still be
> highly desirable.
Absolutely. I think we need basic 3D plotting function
On Thu, Mar 05, 2009 at 11:44:16AM -0500, Rob Clewley wrote:
> If I have a set of scalar sample data on a rectangular 2D mesh that I
> want to plot in the 3D I'd want a simple wireframe rectangular surface
> plot. Can it do that?
My experience from trying to design a simple API to do simple 3D plo
On Thu, Mar 5, 2009 at 11:44 AM, Rob Clewley wrote:
> On Thu, Mar 5, 2009 at 10:39 AM, Ondrej Certik wrote:
>
>>> OK, but it wasn't clear from the example that I could plot a 3D array
>>> of arbitrary data points. The way that you put together the demo plots
>>
>> As I understand it, it plots tri
On Thu, Mar 5, 2009 at 10:39 AM, Ondrej Certik wrote:
>> OK, but it wasn't clear from the example that I could plot a 3D array
>> of arbitrary data points. The way that you put together the demo plots
>
> As I understand it, it plots triangles and/or wireframe in the end.
> Currently I think our
On Thu, Mar 5, 2009 at 10:15 AM, Rob Clewley wrote:
>>> Yes, I didn't know that either. But it's not clear if I can plot
>>> discrete data using this interface - at least the examples on the wiki
>>
>> I am not sure if I understand your question, but It only plots
>> discrete data --- it takes som
>> Yes, I didn't know that either. But it's not clear if I can plot
>> discrete data using this interface - at least the examples on the wiki
>
> I am not sure if I understand your question, but It only plots
> discrete data --- it takes some sympy expression, evaluates it on a
> discrete grid and
On Thu, Mar 5, 2009 at 10:02 AM, Rob Clewley wrote:
> On Thu, Mar 5, 2009 at 5:14 AM, Johann Cohen-Tanugi
> wrote:
>> wouaouh. if I had known that sumpy had this functionality, I would
>> have downloaded it ages ago. This is a good example of justified
>> 'taylorisation', IMHO.
>> Big +1 on s
On Thu, Mar 5, 2009 at 5:14 AM, Johann Cohen-Tanugi
wrote:
> wouaouh. if I had known that sumpy had this functionality, I would
> have downloaded it ages ago. This is a good example of justified
> 'taylorisation', IMHO.
> Big +1 on seing this moved from sympy to matplotlib. I am not expert at
wouaouh. if I had known that sumpy had this functionality, I would
have downloaded it ages ago. This is a good example of justified
'taylorisation', IMHO.
Big +1 on seing this moved from sympy to matplotlib. I am not expert at
coding guis et al, but if you need reviewers/testers or doc write
Hi,
On Wed, Mar 4, 2009 at 11:38 AM, Jonathan Taylor
wrote:
> Great. I applied your patch and pushed it to the web repository.
>
> I agree, that some more serious refactoring might be good. I have
> been leaving comments throughout the code with my thoughts on this.
John just pointed me to thi
Great. I applied your patch and pushed it to the web repository.
I agree, that some more serious refactoring might be good. I have
been leaving comments throughout the code with my thoughts on this.
Cheers,
Jon.
On Wed, Mar 4, 2009 at 4:53 AM, Reinier Heeres wrote:
> Hi all,
>
> I was also a
Hi all,
I was also a bit disappointed about the fact that 3d plotting support
was dropped. I'm happy to help out to get it going again, so here's a
patch to get surface plotting working; I'm busy with the contour plots
as well.
(We might want to do some code refactoring as well when it's functiona
On Tue, Mar 3, 2009 at 11:39 AM, John Hunter wrote:
> Well, it is painfully slow, since it does everything in software, and there
> are some corner cases where the zorder clipping is broken in the presence of
> alpha transparency, and it doesn't do lighting, shadows, etc But it
> does do eno
On Tue, Mar 3, 2009 at 9:56 AM, Jonathan Taylor wrote:
> That sounds reasonable. Can I ask what it is that was primitive?
> Having looked through the code I see that a few shortcuts were made to
> minimize the amount of code written that makes it especially
> susceptible to changes in the 2D cod
That sounds reasonable. Can I ask what it is that was primitive?
Having looked through the code I see that a few shortcuts were made to
minimize the amount of code written that makes it especially
susceptible to changes in the 2D code. That said, it seems like it
was comparable functionally to ma
On Mon, Mar 2, 2009 at 10:13 PM, Jonathan Taylor <
jonathan.tay...@utoronto.ca> wrote:
> Hi,
>
> I saw that 3D plotting was dropped from matplotlib since the last time
> I used it. Unfortunately, it is pretty necessary for some of the work
> I am doing. Thus, I have started the process of refact
40 matches
Mail list logo
