On Jan 18, 2008 3:40 PM, David Joyner <[EMAIL PROTECTED]> wrote:
>
>
> On Jan 18, 2008 9:23 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> >
> > Hi Fabio,
> >
> > On Jan 18, 2008 11:51 AM, Fabio Tonti <[EMAIL PROTECTED]> wrote:
> > > Hello everyone,
> > >
> > > I've just been playing around with SymPy a bit more lately, and I found
> > > that
> > > the 3D-Plot implementation is really nice!!!
> > > Why isn't that the default plot3D-way for Sage command-line use?
> >
> > I think the main reason is just that noone has implement it yet. But see
> > below.
> >
> > > I must say that I'm really looking forward to getting mayavi2 into Sage
> > > (I
> > > know it's already there, but more stable, better supported). Still, I have
> > > no experience with mayavi, and I think the symPy (pyglet) plotting
> > > capabilities are very good. So in my opinion that should be the default
> > > plot3D for command line use.
> > > Of course for the notebook, there's been great work around jmol, and I
> > > like,
> > > but it never worked for me from the command line (btw. java scares the ***
> > > out of me).
> >
> > Speaking only for myself, I don't like java too. But I have a very
> > narrow minded opinion here,
> > I am sure others will not agree with me completely. I know it's GPL,
> > but that's already
> > more than a year (isn't it?), but it still isn't in Debian main, for
> > some legal or technical problems.
> > It is in non-free, so I can still install it with one command (apt-get
> > install sun-java5-plugin) and it
> > works out of the box in all browsers, but I am very picky, I don't
> > want to depend on something
> > that isn't in main (that includes Sage too for the moment). I hope
> > Sage will get into Debian
> > eventually, and java hopefully too. But I don't want to wait 30 years
> > for that. :)
> >
> > So that's why I don't like java, but one shoud use the best tool to do
> > the job. So we want 3D graphing
> > in the browser that just works and I don't know any better solution
> > than the one in Sage.
> >
> > But as to commandline, I think pyglet is a better solution than jmol,
> > because pyglet can be made
> > working for almost everyone (unlike java). But I remember that some
> > people tried that on this list
> > and had some problems too. It does work for me though, even in the old
> > Sage 2.8.13. Try this:
> >
> >
> > $ ./sage
> > ----------------------------------------------------------------------
> > | SAGE Version 2.8.13, Release Date: 2007-11-21 |
> > | Type notebook() for the GUI, and license() for information. |
> > ----------------------------------------------------------------------
> >
> > sage: from sympy import Plot, symbols
> > sage: x, y = symbols("xy")
> > sage: Plot(x*y)
> > [0]: x*y, 'mode=cartesian'
> > sage:
> > Exiting SAGE (CPU time 0m1.18s, Wall time 0m16.36s).
> >
> >
> > And it plots a graph in pyglet, through sympy.
>
> These commands gave me a segfault (amd64bit, running 64bit feisty fawn):
>
> [EMAIL PROTECTED]:~/sagestuff/sage-2.10.alpha1$ ./sage
> ----------------------------------------------------------------------
> | SAGE Version 2.10.alpha1, Release Date: 2008-01-09 |
> | Type notebook() for the GUI, and license() for information. |
> ----------------------------------------------------------------------
>
> sage: from sympy import Plot, symbols
> sage: x, y = symbols("xy")
> sage: Plot(x*y)
> [0]: x*y, 'mode=cartesian'
> sage: Window initialization failed: No conforming visual exists
>
>
> ------------------------------------------------------------
> Unhandled SIGSEGV: A segmentation fault occured in SAGE.
> This probably occured because a *compiled* component
> of SAGE has a bug in it (typically accessing invalid memory)
> or is not properly wrapped with _sig_on, _sig_off.
> You might want to run SAGE under gdb with 'sage -gdb' to debug this.
> SAGE will now terminate (sorry).
> ------------------------------------------------------------
>
> /home/wdj/sagestuff/sage-2.10.alpha1/local/bin/sage-sage: line 210:
> 4052 Segmentation fault (core dumped) sage-ipython -c
> "$SAGE_STARTUP_COMMAND;" "$@"
> [EMAIL PROTECTED]:~/sagestuff/sage-2.10.alpha1$
Thanks for the bug report. :) Could you please try this:
$ wget http://sympy.googlecode.com/files/sympy-0.5.11.tar.gz
$ tar xzf sympy-0.5.11.tar.gz
$ cd sympy-0.5.11
$ python
>>> from sympy import Plot, symbols
>>> x, y = symbols("xy")
>>> Plot(x*y)
[0]: x*y, 'mode=cartesian'
>>>
So that we can determine, if it's a bug in the most recent pyglet
(that is in sympy-0.5.11), or in the pyglet in sympy in Sage.
Thanks a lot,
Ondrej
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
