Thank you! Unfortunately I think you are also right with your last
assumption. It just looks like an empty plot.
As a consequence, I tried this example with the new "knoboo" spkg, but here
is what I get:
from pylab import *
Traceback (most recent call last):
File "<input>", line 1, in <module>
File
"/home/fabio/sage-2.11-debian32-intel-i686-Linux/local/lib/python2.5/site-packages/pylab.py",
line 1, in <module>
from matplotlib.pylab import *
File
"/home/fabio/sage-2.11-debian32-intel-i686-Linux/local/lib/python2.5/site-packages/matplotlib/pylab.py",
line 197, in <module>
from cbook import flatten, is_string_like, exception_to_str, popd, \
File
"/home/fabio/sage-2.11-debian32-intel-i686-Linux/local/lib/python2.5/site-packages/matplotlib/cbook.py",
line 8, in <module>
import numpy as npy
File
"/home/fabio/sage-2.11-debian32-intel-i686-Linux/local/lib/python2.5/site-packages/numpy/__init__.py",
line 43, in <module>
import linalg
File
"/home/fabio/sage-2.11-debian32-intel-i686-Linux/local/lib/python2.5/site-packages/numpy/linalg/__init__.py",
line 4, in <module>
from linalg import *
File
"/home/fabio/sage-2.11-debian32-intel-i686-Linux/local/lib/python2.5/site-packages/numpy/linalg/linalg.py",
line 25, in <module>
from numpy.linalg import lapack_lite
ImportError: liblapack.so: cannot open shared object file: No such file or
Should I open a new thread about this error? (I'm not sure how spkgs are
handled)
Best wishes, Fabio
On Sat, Apr 12, 2008 at 6:24 PM, Carl Witty <[EMAIL PROTECTED]> wrote:
>
> On Apr 8, 4:34 am, "Fabio Tonti" <[EMAIL PROTECTED]> wrote:
> > sage: from pylab import *
> > sage: imshow([[(0,0,0)]])
> > sage: savefig('foo.png')
> > Traceback (most recent call last):
> > ...
> > NameError: global name 'npy' is not defined
> >
> > I would just like to make an image from a 2-dimensional Array (of
> > rgb-values)!
>
> This is a bug in our current version of matplotlib; it is being
> tracked here: http://trac.sagemath.org/sage_trac/ticket/2900
>
> For now, it looks like you may be able to work around the problem by
> using RGBA 4-tuples instead of RGB 3-tuples; that is, add an extra ",
> 255" on the end of each pixel.
>
> You also need to be sure to use Python ints instead of Sage integers.
> So with the commands:
> sage: imshow([[(0r,0r,0r,255r)]])
> sage: savefig('foo.png')
> I at least don't get any more exceptions, and I do get a saved image.
> However, I don't see a black pixel in the saved image, so it may not
> actually be working.
>
> Carl
> >
>
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@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-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
