matplotlib-users Mailing List for matplotlib

Ok. I'll look forward to that.

Ted

On Sat, Jul 24, 2010 at 4:26 PM, mdekauwe <mde...@gm...> wrote:
>
> Hi,
>
> Is there a nice way to plot an array where there are say missing days and
> you wouldn't want the line to join over these data gaps, i.e. show the gaps.
>
> E.g.
>
> 1 4.5
> 2 4.6
> 4 6.7
> 8 5.7
> 9 1.2
>
> The only way I could think to get around this involved appending NaNs and
> then masking the array, but I wonder if this isn't a tad convoluted?

This is probably the easiest way.  You could also construct a custom
compound path and then use a PathPatch where the facecolor was set to
'None'

http://matplotlib.sourceforge.net/users/path_tutorial.html
http://matplotlib.sourceforge.net/examples/api/compound_path.html

JDH

Hi,

Is there a nice way to plot an array where there are say missing days and
you wouldn't want the line to join over these data gaps, i.e. show the gaps. 

E.g.

1 4.5
2 4.6
4 6.7
8 5.7
9 1.2

The only way I could think to get around this involved appending NaNs and
then masking the array, but I wonder if this isn't a tad convoluted?

thanks,

Martin
-- 
View this message in context: http://old.nabble.com/plotting-an-array-with-gaps-tp29257116p29257116.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Hello, I have just updated to v1.0.0 and am trying to run the test
suite to make sure everything is ok.  There seems to be two different
suites and I am not sure which is correct/current:

$python -c 'import matplotlib; matplotlib.test()'
[...snipped output...]
Ran 138 tests in 390.991s
OK (KNOWNFAIL=2)

$nosetests matplotlib.tests I get:
[...snipped output]
Ran 144 tests in 380.165s
FAILED (errors=4, failures=1)

Two of these errors are the known failures from above, and the other
two are in "matplotlib.tests.test_text.test_font_styles":
ImageComparisonFailure: images not close:
/home/adam/result_images/test_text/font_styles.png vs.
/home/adam/result_images/test_text/expected-font_styles.png (RMS
23.833)
ImageComparisonFailure: images not close:
/home/adam/result_images/test_text/font_styles_svg.png vs.
/home/adam/result_images/test_text/expected-font_styles_svg.png (RMS
12.961)

The module that fails is:

FAIL: matplotlib.tests.test_mlab.test_recarray_csv_roundtrip
----------------------------------------------------------------------
Traceback (most recent call last):
 File "/usr/local/lib/python2.6/dist-packages/nose-0.11.4-py2.6.egg/nose/case.py",
line 186, in runTest
   self.test(*self.arg)
 File "/usr/local/lib/python2.6/dist-packages/matplotlib/tests/test_mlab.py",
line 24, in test_recarray_csv_roundtrip
   assert np.allclose( expected['x'], actual['x'] )
AssertionError



I am not sure of the importance level of these - but I wanted to ask
to see if I should do anything or if they can safely be ignored.

Thanks,
Adam.

On Sat, Jul 24, 2010 at 3:22 PM, Satish Raghunath <qg...@my...>wrote:

> Hi,
>  Can anyone please tell me about the tk development packages. Where  can I
> find the tk development packages .
> I am using the following operating system
>
> *Red Hat Enterprise Linux Client release 5.3 (Tikanga)*
>
> Also can anyone tell  me about what  mpl is ?
>
> Thanks!
> Satish
>

Satish,

mpl is a short name for MatPlotLib, a kind of nickname for the project.
'tk' is also another short name for Tkinter, which is the GUI system that
python uses.  The tk development packages can be found using the package
manager to search for and install the 'python-tk' package.

I hope this is helpful,
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
>
>

On Sat, Jul 24, 2010 at 2:46 PM, arsbbr <ar...@gm...> wrote:

>
> Thank you for looking into it!
> It would be perfectly fine for me to merge the two objects, so that one
> surface_plot command will do it.
> Maybe someone can give me a hint how to accomplish that?
>
> I appreciate any tips.
>
>
>
> Benjamin Root-2 wrote:
> >
> > On Sat, Jul 24, 2010 at 7:18 AM, arsbbr <ar...@gm...> wrote:
> >
> >>
> >> Hi,
> >> i'm trying to make a simple 3d plot of a cylinder with plot_surface.
> >> There are two problems in my output:
> >> 1) the shading, shading does not work on the cylindric shell and at the
> >> same
> >> time produces weird
> >> artifacts on the top cover.
> >> http://old.nabble.com/file/p29254649/cyl-shade-error.png
> >>
> >> 2) Sometimes, not reproducible, the inner back of the cylindric shell is
> >> plotted in front of the top cover. It seems, that it depends somehow on
> >> the
> >> order of the plot commands, so that switching the two plot command
> >> helps...
> >> but not all the time.
> >> http://old.nabble.com/file/p29254649/cyl-clip-error.png
> >>
> >> Am I doing something fundamentally wrong here?
> >>
> >> ##########################
> >> from mpl_toolkits.mplot3d import Axes3D
> >> import matplotlib.pyplot as plt
> >> import numpy as np
> >> from matplotlib import cm
> >> fig = plt.figure()
> >> ax = Axes3D(fig)
> >>
> >>
> >> # Cylindrical shell
> >> phi = np.linspace(0, 2 * np.pi, 100)
> >> r = np.ones(100)
> >> h = np.linspace(0, 1, 100)
> >>
> >>
> >> x = 10 * np.outer(np.cos(phi), r)
> >> y = 10 * np.outer(np.sin(phi), r)
> >> z = 10 * np.outer(np.ones(np.size(r)), h)
> >>
> >>
> >> # Top cover
> >> phi_a = np.linspace(0, 2 * np.pi, 100)
> >> h_2 = np.ones(100)
> >> r_2 = np.linspace(0, 1, 100)
> >>
> >> x_2 = 10 * np.outer(np.cos(phi), r_2)
> >> y_2 = 10 * np.outer(np.sin(phi), r_2)
> >> z_2 = 10 * np.ones([100,100])
> >>
> >> ax.plot_surface(x, y, z,  rstride=9, cstride=15, linewidth=1, alpha=1)
> >> ax.plot_surface(x_2, y_2, z_2,  rstride=5, cstride=20, linewidth=1,
> >> alpha=1)
> >>
> >> ax.set_xlabel('X')
> >> ax.set_ylabel('Y')
> >> ax.set_zlabel('Z')
> >>
> >> plt.show()
> >> ##########################
> >>
> >>
> >> I'm just a beginner and installed the Enthought Python Distribution
> >> 6.2-2,
> >> which unfortunately
> >> does not use the matplotlib version 1.0. Since I could not find the .egg
> >> install file on the matplotlib site I guess I'll have to wait until they
> >> update EPD.... self compiling is not a real option for me.
> >>
> >> Thanks any suggestions!
> >>
> >>
> > arsbbr,
> >
> > The second problem you mention is a known issue with 3D axes and it is
> > largely due to issues with overlapping objects and trying to determine
> > which
> > one gets displayed on top of the other in a 3D -> 2D environment (oh, how
> > I
> > wish holographic displays were a reality!).  You will find that viewing
> an
> > object from certain angles will cause this issue, and then slightly
> moving
> > away from those angles will make everything right again.  Unfortunately,
> I
> > do not anticipate this issue being solved anytime soon, although it
> > probably
> > should become a higher priority to me.
> >
> > I think I have seen the first issue before, but I never fully explored
> it.
> > I think I just found my mini-project for the weekend!  I will let you
> know
> > what I find.
> >
>

Actually, looks like your problem was relatively simple.  The construction
of the top surface wasn't done quite right and the striding was causing
blocks to be skipped.  Try this:

phi_grid, r_grid = np.meshgrid(phi_a, r_2)
x_2 = 10 * np.cos(phi_grid) * r_grid
y_2 = 10 * np.sin(phi_grid) * r_grid
z_2 = 10 * np.ones([100,100])

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

Hi,
 Can anyone please tell me about the tk development packages. Where  can I
find the tk development packages .
I am using the following operating system

*Red Hat Enterprise Linux Client release 5.3 (Tikanga)*

Also can anyone tell  me about what  mpl is ?

Thanks!
Satish

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

Thank you for looking into it!
It would be perfectly fine for me to merge the two objects, so that one
surface_plot command will do it.
Maybe someone can give me a hint how to accomplish that?

I appreciate any tips.



Benjamin Root-2 wrote:
> 
> On Sat, Jul 24, 2010 at 7:18 AM, arsbbr <ar...@gm...> wrote:
> 
>>
>> Hi,
>> i'm trying to make a simple 3d plot of a cylinder with plot_surface.
>> There are two problems in my output:
>> 1) the shading, shading does not work on the cylindric shell and at the
>> same
>> time produces weird
>> artifacts on the top cover.
>> http://old.nabble.com/file/p29254649/cyl-shade-error.png
>>
>> 2) Sometimes, not reproducible, the inner back of the cylindric shell is
>> plotted in front of the top cover. It seems, that it depends somehow on
>> the
>> order of the plot commands, so that switching the two plot command
>> helps...
>> but not all the time.
>> http://old.nabble.com/file/p29254649/cyl-clip-error.png
>>
>> Am I doing something fundamentally wrong here?
>>
>> ##########################
>> from mpl_toolkits.mplot3d import Axes3D
>> import matplotlib.pyplot as plt
>> import numpy as np
>> from matplotlib import cm
>> fig = plt.figure()
>> ax = Axes3D(fig)
>>
>>
>> # Cylindrical shell
>> phi = np.linspace(0, 2 * np.pi, 100)
>> r = np.ones(100)
>> h = np.linspace(0, 1, 100)
>>
>>
>> x = 10 * np.outer(np.cos(phi), r)
>> y = 10 * np.outer(np.sin(phi), r)
>> z = 10 * np.outer(np.ones(np.size(r)), h)
>>
>>
>> # Top cover
>> phi_a = np.linspace(0, 2 * np.pi, 100)
>> h_2 = np.ones(100)
>> r_2 = np.linspace(0, 1, 100)
>>
>> x_2 = 10 * np.outer(np.cos(phi), r_2)
>> y_2 = 10 * np.outer(np.sin(phi), r_2)
>> z_2 = 10 * np.ones([100,100])
>>
>> ax.plot_surface(x, y, z,  rstride=9, cstride=15, linewidth=1, alpha=1)
>> ax.plot_surface(x_2, y_2, z_2,  rstride=5, cstride=20, linewidth=1,
>> alpha=1)
>>
>> ax.set_xlabel('X')
>> ax.set_ylabel('Y')
>> ax.set_zlabel('Z')
>>
>> plt.show()
>> ##########################
>>
>>
>> I'm just a beginner and installed the Enthought Python Distribution
>> 6.2-2,
>> which unfortunately
>> does not use the matplotlib version 1.0. Since I could not find the .egg
>> install file on the matplotlib site I guess I'll have to wait until they
>> update EPD.... self compiling is not a real option for me.
>>
>> Thanks any suggestions!
>>
>>
> arsbbr,
> 
> The second problem you mention is a known issue with 3D axes and it is
> largely due to issues with overlapping objects and trying to determine
> which
> one gets displayed on top of the other in a 3D -> 2D environment (oh, how
> I
> wish holographic displays were a reality!).  You will find that viewing an
> object from certain angles will cause this issue, and then slightly moving
> away from those angles will make everything right again.  Unfortunately, I
> do not anticipate this issue being solved anytime soon, although it
> probably
> should become a higher priority to me.
> 
> I think I have seen the first issue before, but I never fully explored it.
> I think I just found my mini-project for the weekend!  I will let you know
> what I find.
> 
> 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-tp29254649p29256632.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

On Sat, Jul 24, 2010 at 7:18 AM, arsbbr <ar...@gm...> wrote:

>
> Hi,
> i'm trying to make a simple 3d plot of a cylinder with plot_surface.
> There are two problems in my output:
> 1) the shading, shading does not work on the cylindric shell and at the
> same
> time produces weird
> artifacts on the top cover.
> http://old.nabble.com/file/p29254649/cyl-shade-error.png
>
> 2) Sometimes, not reproducible, the inner back of the cylindric shell is
> plotted in front of the top cover. It seems, that it depends somehow on the
> order of the plot commands, so that switching the two plot command helps...
> but not all the time.
> http://old.nabble.com/file/p29254649/cyl-clip-error.png
>
> Am I doing something fundamentally wrong here?
>
> ##########################
> from mpl_toolkits.mplot3d import Axes3D
> import matplotlib.pyplot as plt
> import numpy as np
> from matplotlib import cm
> fig = plt.figure()
> ax = Axes3D(fig)
>
>
> # Cylindrical shell
> phi = np.linspace(0, 2 * np.pi, 100)
> r = np.ones(100)
> h = np.linspace(0, 1, 100)
>
>
> x = 10 * np.outer(np.cos(phi), r)
> y = 10 * np.outer(np.sin(phi), r)
> z = 10 * np.outer(np.ones(np.size(r)), h)
>
>
> # Top cover
> phi_a = np.linspace(0, 2 * np.pi, 100)
> h_2 = np.ones(100)
> r_2 = np.linspace(0, 1, 100)
>
> x_2 = 10 * np.outer(np.cos(phi), r_2)
> y_2 = 10 * np.outer(np.sin(phi), r_2)
> z_2 = 10 * np.ones([100,100])
>
> ax.plot_surface(x, y, z,  rstride=9, cstride=15, linewidth=1, alpha=1)
> ax.plot_surface(x_2, y_2, z_2,  rstride=5, cstride=20, linewidth=1,
> alpha=1)
>
> ax.set_xlabel('X')
> ax.set_ylabel('Y')
> ax.set_zlabel('Z')
>
> plt.show()
> ##########################
>
>
> I'm just a beginner and installed the Enthought Python Distribution 6.2-2,
> which unfortunately
> does not use the matplotlib version 1.0. Since I could not find the .egg
> install file on the matplotlib site I guess I'll have to wait until they
> update EPD.... self compiling is not a real option for me.
>
> Thanks any suggestions!
>
>
arsbbr,

The second problem you mention is a known issue with 3D axes and it is
largely due to issues with overlapping objects and trying to determine which
one gets displayed on top of the other in a 3D -> 2D environment (oh, how I
wish holographic displays were a reality!).  You will find that viewing an
object from certain angles will cause this issue, and then slightly moving
away from those angles will make everything right again.  Unfortunately, I
do not anticipate this issue being solved anytime soon, although it probably
should become a higher priority to me.

I think I have seen the first issue before, but I never fully explored it.
I think I just found my mini-project for the weekend!  I will let you know
what I find.

Ben Root

Hi,

>  Can anyone please tell me about the tk development packages. Where  can I
> find the tk development packages .

This heavily depends on which operating system and distribution you are using.

Always give as much info as you can about your system so others can help you.


Have a nice day,

Malte

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.

Ben Root

  Hello,

I looked on your website for the different line styles. In the 
documentation for matplotlib.lines.line2D.set_linestyle, the dashed 
linestyle is listed as '-' and not '--'. It it my understanding that 
dashed should be '--'. If I'm incorrect, sorry for the noise.

Cheers,

-- 
Josh Lawrence
Ph.D. Student
Clemson University

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

Hi,
 Can anyone please tell me about the tk development packages. Where  can I
find the tk development packages .
Thanks!
Satish

Hi Ted,

There is currently no clipping of data outside the visible region; I
hope to implement this partly soon. For scatter plots it's not so
hard, but for surfaces it's a bit more complicated.

Regards,
Reinier

On Sat, Jul 24, 2010 at 11:51 AM, Ted Kord <ted...@gm...> wrote:
> Hi
>
> I'm trying to set the axes limits in MPlot3d but the bits I'm trying to
> exclude still appear. I've done something like this:
>
> ax.set_xlim3d([340, 600])
> ax.set_ylim3d([0, 14.0])
> ax.set_zlim3d([0, 300])
>
> but it still shows all the data from 0, 600 for the x-axis and 0 to 14 for
> the y-axis.
>
> Is there something I'm doing incorrectly?
>
> Thx
>
> Ted
>
>
> ------------------------------------------------------------------------------
> 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
>
>



-- 
Reinier Heeres
Tel: +31 6 10852639

Hi,
i'm trying to make a simple 3d plot of a cylinder with plot_surface.
There are two problems in my output:
1) the shading, shading does not work on the cylindric shell and at the same
time produces weird 
artifacts on the top cover. 
http://old.nabble.com/file/p29254649/cyl-shade-error.png 

2) Sometimes, not reproducible, the inner back of the cylindric shell is
plotted in front of the top cover. It seems, that it depends somehow on the
order of the plot commands, so that switching the two plot command helps...
but not all the time.
http://old.nabble.com/file/p29254649/cyl-clip-error.png 

Am I doing something fundamentally wrong here? 

##########################
from mpl_toolkits.mplot3d import Axes3D
import matplotlib.pyplot as plt
import numpy as np
from matplotlib import cm
fig = plt.figure()
ax = Axes3D(fig)


# Cylindrical shell
phi = np.linspace(0, 2 * np.pi, 100)
r = np.ones(100)
h = np.linspace(0, 1, 100)


x = 10 * np.outer(np.cos(phi), r)
y = 10 * np.outer(np.sin(phi), r)
z = 10 * np.outer(np.ones(np.size(r)), h)


# Top cover
phi_a = np.linspace(0, 2 * np.pi, 100)
h_2 = np.ones(100)              
r_2 = np.linspace(0, 1, 100)

x_2 = 10 * np.outer(np.cos(phi), r_2)
y_2 = 10 * np.outer(np.sin(phi), r_2)
z_2 = 10 * np.ones([100,100])

ax.plot_surface(x, y, z,  rstride=9, cstride=15, linewidth=1, alpha=1)
ax.plot_surface(x_2, y_2, z_2,  rstride=5, cstride=20, linewidth=1, alpha=1)

ax.set_xlabel('X')
ax.set_ylabel('Y')
ax.set_zlabel('Z')

plt.show()
##########################


I'm just a beginner and installed the Enthought Python Distribution 6.2-2,
which unfortunately
does not use the matplotlib version 1.0. Since I could not find the .egg
install file on the matplotlib site I guess I'll have to wait until they
update EPD.... self compiling is not a real option for me. 

Thanks any suggestions!

-- 
View this message in context: http://old.nabble.com/plot_surface-shading-and-clipping-error-tp29254649p29254649.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

   I have exactly the same problem on a program that I'm writing.
I attach a figure to show what I see.
I run python 2.6.2, Matplotlib 0.99.1.1, OpenSUSE 11.2 64 bit.

I thought that there was a problem with how I wrote the code since I'm a 
real beginner, but I'm "happy" to see that the problem is different.

My program has labels and entries, no comboboxes...

Does anyone know how to do with this?

Hello,

I've installed the following Python packages on a Windows XP machine:

Python 2.6.5

Python 2.6 numpy-1.4.1

Python 2.6 matplotlib-0.99.3 [installer - matplotlib-0.99.3.win32-py2.6]

Python and Numpy work correctly. Matplotlib also works and as a test I tried successfully the following on the python interpretor:

from matplotlib.pyplot import *
plot([1,2,3])
show()

A graph then appears and thus so far so good.

However, when I try to run a certain python script, a problem occurs when importing from matplotlib:




	
	
	
	

Traceback (most recent
call last):
  File
"C:\Pythoncode\Games\Bridge_war_2\unitload2.py", line 2, in
<module>
    from matplotlib.pyplot
import plot, ylabel,xlabel, show
  File
"C:\Python26\lib\site-packages\matplotlib\pyplot.py", line
78, in <module>
    new_figure_manager,
draw_if_interactive, show = pylab_setup()
  File
"C:\Python26\lib\site-packages\matplotlib\backends\__init__.py",
line 25, in pylab_setup
    globals(),locals(),[backend_name])
  File
"C:\Python26\lib\site-packages\matplotlib\backends\backend_tkagg.py",
line 7, in <module>
    import Tkinter as Tk,
FileDialog
  File
"C:\Python26\lib\lib-tk\FileDialog.py", line 12, in
<module>
    from Dialog import
Dialog
  File
"C:\Pythoncode\Games\Bridge_war_2\Dialog.py", line 2, in
<module>
    import  wx
ImportError: No module
named wx
And then no graph appears.


The same script works fine on my Linux computers. On the unitload2.py script, the following is imported:

from numpy import array, append, .. 
from numpy.linalg import solve

No further modules are imported. Once I've ran the unitload2.py script, that session of the python interpretor produces the same error when I try a test plot again.

Regards

Alex









 		 	   		  
_________________________________________________________________
http://clk.atdmt.com/UKM/go/197222280/direct/01/
Do you have a story that started on Hotmail? Tell us now

Hi

I'm trying to set the axes limits in MPlot3d but the bits I'm trying to
exclude still appear. I've done something like this:

ax.set_xlim3d([340, 600])
ax.set_ylim3d([0, 14.0])
ax.set_zlim3d([0, 300])

but it still shows all the data from 0, 600 for the x-axis and 0 to 14 for
the y-axis.

Is there something I'm doing incorrectly?

Thx

Ted