matplotlib-users Mailing List for matplotlib (Page 14)

Anand Patil <an...@so...> writes:
> - How can I make my figures and axes transparent by default?
Here's one idea:
------------------------------------------------------------------------
In [1]:fig=figure(frameon=False)
In [2]:ax = fig.add_subplot(111, frameon=False)
In [3]:ax.plot([3,1,4,1,5,9,2])
Out[3]:[<matplotlib.lines.Line2D instance at 0x2c98b70>]
In [4]:show()
In [5]:savefig('foo.pdf')
------------------------------------------------------------------------
And here's another:
------------------------------------------------------------------------
In [20]:fig=figure()
In [21]:fig.figurePatch.set_alpha(0.1)
In [22]:ax=fig.add_subplot(111) 
In [23]:ax.axesPatch.set_alpha(0.1)
In [24]:ax.plot([3,1,4,1,5,9,2])
Out[24]:[<matplotlib.lines.Line2D instance at 0x16f7e490>]
In [25]:show()
In [26]:savefig('foo.pdf')
------------------------------------------------------------------------
Does either of these do what you are looking for?
> - When I inserted some of my old pdf plots into a latex presentation, to 
> my surprise their foreground color had changed from black to the color 
> of the text in the presentation. Is there a way to signal to Matplotlib 
> that I would like this to happen? Can I make this behavior default?
Were the old pdf plots produced with the pdf backend, or with the eps
backend and then converted to pdf with some external utility?
I'm guessing that what happened was that the pdf file didn't specify
any color, and when it was included, it inherited the graphics state
from the including pdf file. I'm not quite sure if that's supposed to
happen when including files, although I can of course see how it could
be considered a useful feature.
Certainly there is no such intended feature in matplotlib. I think I
could support it for monochromatic plots quite easily, but it would be
much trickier if you want part of the plot in the inherited color and
another part in a specified color.
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

Out of the box matplotlib works great with Numeric and numarray data types.
However, I have my own custom class which contains data members, methods and
an array of data (underlying C array). Is there a way to expose the C array
data to the plot() routines? For example I would like to be able to use
plot(X) where X is an instantiated object of type MyClass.
Thanks,
-Simon

kc1...@ya... writes:
> a) 2.3 doesn't have the sorted function - it uses a .sort()
> function. So, I had to change line 487 from:
I think this was taken care of by Nicolas Grilly's recent patch.
> b) No update() function (line 396)
> for (name, value) in self.markers.items():
> xobjects[name]=value[0]
Applied in svn, thanks!
> After that, I got my pdf file. However, if I print the PDF directly,
> works fine but when I create an object link to the PDF and print
> from inside Word, the printout is degraded (kind of fuzzy with
> texts).
That sounds to me like a bug in Word (as does the invalidrestore
thing).
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

I installed the numpy-1.0.1 successfully, but failed to install matplotlib
0.90. My linux env is DreamHost Debian Linux. There are some things I can't
control.
Anyone successfully doing so on DH hosted machine? Thanks!
[catalina]$ ../python2.5/bin/python setup.py install
GTK requires pygtk
GTKAgg requires pygtk
TKAgg requires TkInter
running install
running build
running build_py
running build_ext
building 'matplotlib.backends._ns_backend_agg' extension
C compiler: gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O3 -Wall
-Wstrict-prototypes -fPIC
compile options:
'-I/home/.makayla/codev/python2.5/lib/python2.5/site-packages/numpy/core/include
-I/usr/local/include -I/usr/include -I. -Isrc -Iswig -Iagg23/include -I.
-I/usr/local/include -I/usr/include -I.
-I/home/.makayla/codev/python2.5/lib/python2.5/site-packages/numpy/core/include/freetype2
-I/usr/local/include/freetype2 -I/usr/include/freetype2 -I./freetype2
-Isrc/freetype2 -Iswig/freetype2 -Iagg23/include/freetype2 -I./freetype2
-I/usr/local/include/freetype2 -I/usr/include/freetype2 -I./freetype2
-I/home/.makayla/codev/python2.5/include/python2.5 -c'
extra options: '-DSCIPY=1'
gcc: src/_image.cpp
In file included from
/home/.makayla/codev/python2.5/include/python2.5/Python.h:8,
 from src/_image.cpp:7:
/home/.makayla/codev/python2.5/include/python2.5/pyconfig.h:932:1: warning:
"_POSIX_C_SOURCE" redefined
In file included from /usr/include/c++/3.3/i486-linux/bits/os_defines.h:39,
 from /usr/include/c++/3.3/i486-linux/bits/c++config.h:35,
 from /usr/include/c++/3.3/iostream:44,
 from src/_image.cpp:1:
/usr/include/features.h:131:1: warning: this is the location of the previous
definition
gcc: src/ft2font.cpp
In file included from
/home/.makayla/codev/python2.5/include/python2.5/Python.h:8,
 from CXX/Objects.hxx:9,
 from CXX/Extensions.hxx:19,
 from src/ft2font.h:18,
 from src/ft2font.cpp:2:
/home/.makayla/codev/python2.5/include/python2.5/pyconfig.h:932:1: warning:
"_POSIX_C_SOURCE" redefined
In file included from /usr/include/c++/3.3/i486-linux/bits/os_defines.h:39,
 from /usr/include/c++/3.3/i486-linux/bits/c++config.h:35,
 from /usr/include/c++/3.3/iosfwd:45,
 from /usr/include/c++/3.3/ios:44,
 from /usr/include/c++/3.3/istream:44,
 from /usr/include/c++/3.3/sstream:44,
 from src/ft2font.cpp:1:
/usr/include/features.h:131:1: warning: this is the location of the previous
definition
gcc: Internal error: Killed (program cc1plus)
Please submit a full bug report.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:///usr/share/doc/gcc-3.3/README.Bugs>.
In file included from
/home/.makayla/codev/python2.5/include/python2.5/Python.h:8,
 from CXX/Objects.hxx:9,
 from CXX/Extensions.hxx:19,
 from src/ft2font.h:18,
 from src/ft2font.cpp:2:
/home/.makayla/codev/python2.5/include/python2.5/pyconfig.h:932:1: warning:
"_POSIX_C_SOURCE" redefined
In file included from /usr/include/c++/3.3/i486-linux/bits/os_defines.h:39,
 from /usr/include/c++/3.3/i486-linux/bits/c++config.h:35,
 from /usr/include/c++/3.3/iosfwd:45,
 from /usr/include/c++/3.3/ios:44,
 from /usr/include/c++/3.3/istream:44,
 from /usr/include/c++/3.3/sstream:44,
 from src/ft2font.cpp:1:
/usr/include/features.h:131:1: warning: this is the location of the previous
definition
gcc: Internal error: Killed (program cc1plus)
Please submit a full bug report.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:///usr/share/doc/gcc-3.3/README.Bugs>.
error: Command "gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O3 -Wall
-Wstrict-prototypes -fPIC
-I/home/.makayla/codev/python2.5/lib/python2.5/site-packages/numpy/core/include
-I/usr/local/include -I/usr/include -I. -Isrc -Iswig -Iagg23/include -I.
-I/usr/local/include -I/usr/include -I.
-I/home/.makayla/codev/python2.5/lib/python2.5/site-packages/numpy/core/include/freetype2
-I/usr/local/include/freetype2 -I/usr/include/freetype2 -I./freetype2
-Isrc/freetype2 -Iswig/freetype2 -Iagg23/include/freetype2 -I./freetype2
-I/usr/local/include/freetype2 -I/usr/include/freetype2 -I./freetype2
-I/home/.makayla/codev/python2.5/include/python2.5 -c src/ft2font.cpp -o
build/temp.linux-i686-2.5/src/ft2font.o -DSCIPY=1" failed with exit status 1
[catalina]$

Suresh Pillai wrote:
> Great, matshow() works for my requirements.
> 
> Although, I must comment that its placement of tickbars seems 
> inappropriate for a matrix visualisation. For example, for the following 
> simple example:
> 
> import pylab
> 
> matrix = pylab.array([[1,2,3],[4,5,6],[1,1,4]])
> pylab.matshow(matrix, cmap=pylab.cm.gray)
> pylab.show()
> 
> tick marks and labels are produced for [0.5,1.5,2.5] in addition to the 
> appropriate integral ones. It's obviously not an issue for larger 
> matrices.
I agree, and this is a problem with spy also. If I remember, I will fix 
it. It is only a minor annoyance, so it is low priority, though.
There is a difference in the way the axes are labeled between spy and 
matshow, and I would like to change matshow to agree with spy, unless 
there is an outcry to the contrary. Specifically, I think the integer 
axis ticks should land in the middle of a given row or column, not on 
the edge. To see what I mean, compare
xx = zeros((3,3))
xx[1,1] = 1
spy(xx, marker='s')
to
matshow(xx)
Maybe this is exactly what you mean by your next statement?
> 
> Further, I would think a setting like align='center' in pylab.bar() would 
> be appropriate. Any simple way of doing this without manually setting the 
> ticks and labels (ironically using forced *.5 ticks)?
Eric

Great, matshow() works for my requirements.
Although, I must comment that its placement of tickbars seems 
inappropriate for a matrix visualisation. For example, for the following 
simple example:
import pylab
matrix = pylab.array([[1,2,3],[4,5,6],[1,1,4]])
pylab.matshow(matrix, cmap=pylab.cm.gray)
pylab.show()
tick marks and labels are produced for [0.5,1.5,2.5] in addition to the 
appropriate integral ones. It's obviously not an issue for larger 
matrices.
Further, I would think a setting like align='center' in pylab.bar() would 
be appropriate. Any simple way of doing this without manually setting the 
ticks and labels (ironically using forced *.5 ticks)?
I guess I should code and submit it myself. :)
Thanks very much,
Suresh
On Thu, 1 Mar 2007, Eric Firing wrote:
> Suresh Pillai wrote:
>> I am using imshow to visualise matrices. When I use align='upper'
>> (default), the origin is still displayed in the lower left corner on the
>> axes - i.e. the y-axis is wrong. The data is plotted correctly with the
>> origin in the upper left corner.
>>
>> Seems to be a bug?
>
> No, this is just the way it was designed and has always been. You can use 
> the "extent" kwarg to control the axes:
>
> * origin is either upper or lower, which indicates where the [0,0]
> index of the array is in the upper left or lower left corner of
> the axes. If None, default to rc image.origin
> * extent is a data xmin, xmax, ymin, ymax for making image plots
> registered with data plots. Default is the image dimensions
> in pixels
>
> See the code in axes.spy() for an example of how to get what you want using 
> imshow and the extent kwarg; or use pylab.matshow instead of pylab.imshow. 
> (Probably there should be an axes.matshow convenience method, with 
> pylab.matshow as a wrapper that autogenerates a figure if needed. But at the 
> moment there isn't.)
>
> Eric
>
>>
>> Cheers,
>> Suresh
>>
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share
>> your
>> opinions on IT & business topics through brief surveys-and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>
>

Suresh Pillai wrote:
> I am using imshow to visualise matrices. When I use align='upper' 
> (default), the origin is still displayed in the lower left corner on the 
> axes - i.e. the y-axis is wrong. The data is plotted correctly with the 
> origin in the upper left corner.
> 
> Seems to be a bug?
No, this is just the way it was designed and has always been. You can 
use the "extent" kwarg to control the axes:
 * origin is either upper or lower, which indicates where the [0,0]
 index of the array is in the upper left or lower left corner of
 the axes. If None, default to rc image.origin
 * extent is a data xmin, xmax, ymin, ymax for making image plots
 registered with data plots. Default is the image dimensions
 in pixels
See the code in axes.spy() for an example of how to get what you want 
using imshow and the extent kwarg; or use pylab.matshow instead of 
pylab.imshow. (Probably there should be an axes.matshow convenience 
method, with pylab.matshow as a wrapper that autogenerates a figure if 
needed. But at the moment there isn't.)
Eric
> 
> Cheers,
> Suresh
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

I am using imshow to visualise matrices. When I use align='upper' 
(default), the origin is still displayed in the lower left corner on the 
axes - i.e. the y-axis is wrong. The data is plotted correctly with the 
origin in the upper left corner.
Seems to be a bug?
Cheers,
Suresh

I found an example on the web that illustrates the question I posted earlie=
r about axes. See:=0A=0Ahttp://www.scipy.org/Cookbook/Matplotlib/Multicolo=
redLine=0A=0ANotice that the y-axis goes from (-1.1, 1.1) but the first lab=
el is at -1.0. I really don't like that because when I read values off th=
e graph, I have to keep reminding myself that the origin is at -1.1. This=
 may seem trivial but if you have to think, walk, chew gums at the same tim=
e you're reading the graph, it gets annoying - particularly if you have to =
read lots of these graphs.=0A=0AIs there a way to force the label to start =
at -1.1 instead of -1.0?=0A=0AThanks,=0A =0A--=0AJohn Henry=0A=0A

Hello darkside,
I set up a little program hoping it offers a solution to your problem.
Matthias
>-------------------------------------------------------------------------------
from numpy.random import uniform 
import pylab 
Nt = 20
x,y = uniform(size=(100,Nt+1)),uniform(size=(100,Nt+1))
pylab.ion()
ax1 = pylab.subplot(211)
pylab.ylabel('Posiciones')
ax2 = pylab.subplot(212)
pylab.ylabel('Momentos')
line1,= ax1.plot(x[:,0], x[:,1])
line2,= ax2.plot(y[:,0], y[:,1])
pylab.draw()
pylab.draw()
# alternative you could use
"""
pylab.axes(ax1)
line1,= pylab.plot(x[:,0], x[:,1])
pylab.axes(ax2)
line2,= pylab.plot(y[:,0], y[:,1])
pylab.draw()
"""
for k in pylab.arange(Nt):
 line1.set_ydata(x[:,k+1])
 line2.set_ydata(y[:,k+1])
 pylab.draw()
 pylab.draw()
pylab.ioff()
pylab.show()
>-------------------------------------------------------------------