linuxgus wrote:
> The past few days I installed Sage 4.2.1 from source on 64-bit Ubuntu
> karmic with stock kernel and I also installed the binary for the Atom
> N270 on a eeePC 1000, also running Ubuntu karmic (32 bit, as the Atom
> is a 32-bit processor). To test things out, I executed the one-line
> script 'plot(sin(x),(-3*pi,+3*pi))' and I observed that in both
> environments the plot missed the (0,0) point not by much, perhaps a
> couple of pixels, but enough to be observable. (0,0) was clearly
> outside the plot pixels.
>
> Since this happened on two very different architectures and two very
> different graphics cards, I would tend to suspect that this is
> architecture-independent.
This illustrates it a bit better:
show(circle((0,0),radius=.05)+plot(sin(x),(-pi,+pi)), aspect_ratio=1)
or this:
var('x,y')
density_plot(1/(x^10+y^10), (x, -10, 10), (y, -10, 10))
However, notice that:
show(circle((0,0),radius=.05)+plot(sin(x),(-pi,+pi)),
aspect_ratio=1,frame=True,axes=True)
and
var('x,y')
density_plot(1/(x^10+y^10), (x, -10, 10), (y, -10, 10),frame=True,axes=True)
both look correct. So it looks like there might be a problem in the
codepath dealing with axes without frames.
At first I thought it was http://trac.sagemath.org/sage_trac/ticket/5599
again. Now I'm not so sure.
Jason
--
Jason Grout
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-support
URL: http://www.sagemath.org
