matplotlib-users Mailing List for matplotlib

On Sun, Jul 25, 2010 at 5:04 PM, John Hunter <jd...@gm...> wrote:
> On Sun, Jul 25, 2010 at 3:14 PM, Benjamin Root <ben...@ou...> wrote:
> > I tried a bunch of the animation examples and widget examples with and
> > without the patch. I could not find one that was affected by this bug,
> > however, none of them were adversely affected by the patch. However,
> both
> > of the plot_moves.py scripts were improved by the patch.
>
> Since this is a bugfix, it should go into the 1.0 release branch and
> then merged into the trunk using svnmerge. Are you familar with this
> (it's described in the coding guide). If so, would you mind
> committing this?
>
> Thanks for the testing Ben and the patch João
>
> JDH
>
Sure, I can commit it.
committed to v1.0 branch as r8575
and merged with trunk as r8576.
Ben Root

Ben,
your code fixed the shading problem, but it did not change anything on the
clipping error.
I also found that changing the cstride/rstride helps 'sometimes'. But also
does changing the 
linewidth. The problem is consistency with my loop...
I understand this is a bug that is not easy to fix. It would be totally
sufficient for me if I could only find some parameters that'll always work.
But this is not the case. Since there is no random procedure in the code
there must be some footprint so that the starting parameters are not the
same all the time. Maybe it is a memory thing and I have just to clear a
cache/display buffer or something?
Benjamin Root-2 wrote:
> 
> 
> arsbor,
> 
> Actually, in your case, I think the issue was also caused by the bad array
> construction and plot_surface() was getting bad data depending on the
> strides. There is no random number generator in the code-path, so
> *something* must change. I noticed that it would happen as I changed the
> cstride/rstride values for the top cover (before I had fixed the top
> cover). If you still notice the issue now, let me know and I will look
> into
> it further, but it shouldn't be happening for you.
> 
> Ben Root
> 
> 
> 
> 
-- 
View this message in context: http://old.nabble.com/plot_surface-shading-and-clipping-error-tp29254649p29262268.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

On Sun, Jul 25, 2010 at 3:14 PM, Benjamin Root <ben...@ou...> wrote:
> I tried a bunch of the animation examples and widget examples with and
> without the patch. I could not find one that was affected by this bug,
> however, none of them were adversely affected by the patch. However, both
> of the plot_moves.py scripts were improved by the patch.
Since this is a bugfix, it should go into the 1.0 release branch and
then merged into the trunk using svnmerge. Are you familar with this
(it's described in the coding guide). If so, would you mind
committing this?
Thanks for the testing Ben and the patch João
JDH

On Sat, Jul 24, 2010 at 3:11 PM, John Hunter <jd...@gm...> wrote:
> On Sat, Jul 24, 2010 at 1:56 PM, Benjamin Root <ben...@ou...> wrote:
> > On Sat, Jul 24, 2010 at 12:17 PM, João Luís Silva <js...@fc...>
> wrote:
> >>
> >> On 07/13/2010 02:31 AM, John Hunter wrote:
> >>>
> >>> On Mon, Jul 12, 2010 at 8:05 PM, John Hunter<jd...@gm...>
> wrote:
> >>>>
> >>>> All of which is discouraging: we both see bugs but different ones on
> >>>> linux, the appearance of the bug is caused by adding a combobox which
> >>>> is not used (on my system), the bug appears on some platforms (linux)
> >>>> but not others (win) and it appears for both gtk and gtkagg.
> >>>
> >>> The last thing I'll add for now is that my bug, the black pixel noise
> >>> (fills the axes window when motion starts in a zoom-to-rect event)
> >>> which may be unrelated to your bug, is happening in
> >>> backend_gtk.NavigationToolbar2GTK.draw_rubberband in the pair of
> >>> calls:
> >>>
> >>> # this is used to copy the background that the zoom to rect
> >>> "rubberband" will be drawn over
> >>> self._imageBack = axrect, drawable.get_image(*axrect)
> >>>
> >>> # this is used to restore the background before redrawing the
> >>> rectangle for the zoom box
> >>> drawable.draw_image(gc, imageBack, 0, 0, *lastrect)
> >>>
> >>> Since the bug is only exposed when a combo box is added to the
> >>> hierarchy, and appears to be platform or gtk specific, I'm suspecting
> >>> a gtk bug at this point. But I don't have anything conclusive or a
> >>> minimal example which I could use to post to the gtk list. The mpl
> >>> calls and values (axrect, lastrect, etc) look correct on inspection.
> >>> Somehow the call to drawable.get_image is getting a buffer full of
> >>> noise if and only if the combobox is added to the vbox.
> >>>
> >>> JDH
> >>
> >> >From what I could understand from the pygtk documentation get_image /
> >> draw_image are client-side operations. In particular:
> >>
> >> "If the source drawable is a Gdk::Window and partially offscreen or
> >> obscured, then the obscured portions of the returned image will contain
> >> undefined data."
> >>
> >> Anyway they recommend using Pixmap, which is server-side and a offscreen
> >> drawable. I've attached a patch that replaces the get_image / draw_image
> >> with Pixmap operations and fixes this bug. I've tested this patch on
> Linux
> >> and Windows.
> >>
> >> Regards,
> >> João Luís
> >
> > The patch works for me. I am using the mpl from svn.
>
> Have you tested with any of the animation and blit examples? How
> about some of the widget examples? If all these work for you, I
> suggest committing it to the branch and merging to the trunk.
>
> Thanks,
> JDH
>
I tried a bunch of the animation examples and widget examples with and
without the patch. I could not find one that was affected by this bug,
however, none of them were adversely affected by the patch. However, both
of the plot_moves.py scripts were improved by the patch.
Ben Root

On Sun, Jul 25, 2010 at 1:27 PM, Satish Raghunath <qg...@my...>wrote:
> Hi
> I got this error when I was trying to build the matplot lib .src/backend_gdk.c:8:25: error: pygtk/pygtk.h: No such file or directory
> src/backend_gdk.c: In function âpixbuf_get_pixels_arrayâ:
> src/backend_gdk.c:18: error: âPyGObjectâ undeclared (first use in this
> function)
> src/backend_gdk.c:18: error: (Each undeclared identifier is reported only
> once
> src/backend_gdk.c:18: error: for each function it appears in.)
> src/backend_gdk.c:18: error: âpy_pixbufâ undeclared (first use in this
> function)
> src/backend_gdk.c:19: error: âGdkPixbufâ undeclared (first use in this
> function)
> src/backend_gdk.c:19: error: âgdk_pixbufâ undeclared (first use in this
> function
>
> i tried to install pygtk-2.12.0 and pygobject- 2.12.1 but I got the error
> No package 'pygobject-2.0' found
>
> can anyone please explain me the above errors
>
> Thanks!
> Satish
>
>
Satish,
Perhaps it would be useful to first read up on RHEL 4 (and Linux in general)
package managers:
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/sysadmin-guide/ch-rpm.html
In a link I have provided in a previous email, it contains a list of
packages you should ensure are installed on your system before attempting to
build matplotlib. In this case, you are missing some of the development
libraries for pygtk.
In addition, given the amount of difficulties you are having with installing
matplotlib, you might want to consider Enthought's Python Distribution
(often called EPD) to help make the entire process easier for you.
http://enthought.com/products/epd.php
Ben Root

Hi
 I got this error when I was trying to build the matplot lib
.src/backend_gdk.c:8:25: error: pygtk/pygtk.h: No such file or
directory
src/backend_gdk.c: In function âpixbuf_get_pixels_arrayâ:
src/backend_gdk.c:18: error: âPyGObjectâ undeclared (first use in this
function)
src/backend_gdk.c:18: error: (Each undeclared identifier is reported only
once
src/backend_gdk.c:18: error: for each function it appears in.)
src/backend_gdk.c:18: error: âpy_pixbufâ undeclared (first use in this
function)
src/backend_gdk.c:19: error: âGdkPixbufâ undeclared (first use in this
function)
src/backend_gdk.c:19: error: âgdk_pixbufâ undeclared (first use in this
function
i tried to install pygtk-2.12.0 and pygobject- 2.12.1 but I got the error
No package 'pygobject-2.0' found
can anyone please explain me the above errors
Thanks!
Satish

On Sun, Jul 25, 2010 at 1:55 AM, Satish Raghunath <qg...@my...>wrote:
> Hi
> I am getting this error*
> File "aerialvision1.py", line 79, in <module>
> import startup
> File "/home/satish/gpgpusim/gpgpu-sim_v2.1.1b/aerialvision/startup.py",
> line 68, in <module>
> import guiclasses
> File
> "/home/satish/gpgpusim/gpgpu-sim_v2.1.1b/aerialvision/guiclasses.py", line
> 68, in <module>
> matplotlib.use('TkAgg')
> AttributeError: 'module' object has no attribute 'use'
>
> " AttributeError: 'module' object has no attribute 'use' " *
>
> Can anyone please explain me this error
>
> Thanks!
> Satish
>
>
It means the authors of gpgpu-sim_v2.1.1b made a mistake and did not import
matplotlib in guiclasses.py. Contact them about the bug.
Ben Root

On Sun, Jul 25, 2010 at 5:19 AM, arsbbr <ar...@gm...> wrote:
>
> Thanks, this was quite a tiny weekend project for you :)
> I'll keep you tip in mind.
>
> Concerning the foreground/background issue: The problem here seems quite
> random. It does not depend on the viewing angle. I rather just have to be
> lucky everytime the plot command is executed.
> If the plotting went right, I can rotate everything without any errors.
>
> I'm by no means a coder, but I find it hard to understand that executing
> the
> same script leads to a different outcome. My plan is to make a movie of the
> cylinder while shrinking. If the problem would
> just depend on the viewing angle, I would find a 'good angle', make it
> constant and start the loop. But at the moment the outcome is just
> arbitrary.
>
> Regards,
> arsbbr
>
>
arsbor,
Actually, in your case, I think the issue was also caused by the bad array
construction and plot_surface() was getting bad data depending on the
strides. There is no random number generator in the code-path, so
*something* must change. I noticed that it would happen as I changed the
cstride/rstride values for the top cover (before I had fixed the top
cover). If you still notice the issue now, let me know and I will look into
it further, but it shouldn't be happening for you.
Ben Root

Thanks, this was quite a tiny weekend project for you :)
I'll keep you tip in mind.
Concerning the foreground/background issue: The problem here seems quite
random. It does not depend on the viewing angle. I rather just have to be
lucky everytime the plot command is executed.
If the plotting went right, I can rotate everything without any errors. 
I'm by no means a coder, but I find it hard to understand that executing the
same script leads to a different outcome. My plan is to make a movie of the
cylinder while shrinking. If the problem would
just depend on the viewing angle, I would find a 'good angle', make it
constant and start the loop. But at the moment the outcome is just
arbitrary.
Regards,
arsbbr
Benjamin Root-2 wrote:
> 
> On Sat, Jul 24, 2010 at 2:46 PM, arsbbr <ar...@gm...> wrote:
> 
> 
> 
> The thing to keep in mind when creating a surface in 3d is that the data
> needs to be considered as parameterizable in 2D and constructed as such.
> 
> I hope that helps,
> 
> Ben Root
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
> 
-- 
View this message in context: http://old.nabble.com/plot_surface-shading-and-clipping-error-tp29254649p29259207.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Hi
 I am getting this error*
 File "aerialvision1.py", line 79, in <module>
 import startup
 File "/home/satish/gpgpusim/gpgpu-sim_v2.1.1b/aerialvision/startup.py",
line 68, in <module>
 import guiclasses
 File "/home/satish/gpgpusim/gpgpu-sim_v2.1.1b/aerialvision/guiclasses.py",
line 68, in <module>
 matplotlib.use('TkAgg')
AttributeError: 'module' object has no attribute 'use'
 " AttributeError: 'module' object has no attribute 'use' " *
Can anyone please explain me this error
Thanks!
Satish

On Sat, Jul 24, 2010 at 8:08 PM, Satish Raghunath <qg...@my...>wrote:
> Hi,
> I am getting this error when using matplot . No module named _tkagg . Can
> anyone please tell me about this error and what does tkagg mean .
> Thanks!
> Satish
>
>
Satish, this error occurs if you build matplotlib from source without having
the tk development libraries installed on your system. Tk is the short name
for Tkinter, which is the GUI system for Python. If you intended to use
gtk, qt, or wx, then you would have to specify it in your configuration
file. For any of these GUI systems, you will need the development files
installed.
http://matplotlib.sourceforge.net/users/installing.html#installing-from-source
I hope this helps,
Ben Root

Hi,
 I am getting this error when using matplot . No module named _tkagg . Can
anyone please tell me about this error and what does tkagg mean .
Thanks!
Satish