Menu
▾
▴
matplotlib-users
|
From: Matthew K. G. <mk...@cs...> - 2011-09-07 18:34:26
|
How can I make a 3D plot without showing the axes? When plotting a 3d plot, Matplotlib not only draws the x, y, and z axes, it also draws light gray grids on the x-y, y-z, and x-z planes. I would like to draw a "free-floating" 3D graph, with none of these elements. My matplotlib.__version__ is 1.0.1. Stuff I've tried: # Doesn't work; this hides the plot, not the axes my_3d_axes.set_visible(False) # Doesn't do anything. Also, there's no get_zaxis() function. my_3d_axes.get_xaxis().set_visible(False) my_3d_axes.get_yaxis().set_visible(False) -- Matt |
|
From: Benjamin R. <ben...@ou...> - 2011-09-07 18:52:53
|
On Wed, Sep 7, 2011 at 1:34 PM, Matthew Koichi Grimes <mk...@cs...>wrote: > How can I make a 3D plot without showing the axes? > > When plotting a 3d plot, Matplotlib not only draws the x, y, and z > axes, it also draws light gray grids on the x-y, y-z, and x-z planes. > I would like to draw a "free-floating" 3D graph, with none of these > elements. My matplotlib.__version__ is 1.0.1. > > Stuff I've tried: > > # Doesn't work; this hides the plot, not the axes > my_3d_axes.set_visible(False) > > # Doesn't do anything. Also, there's no get_zaxis() function. > my_3d_axes.get_xaxis().set_visible(False) > my_3d_axes.get_yaxis().set_visible(False) > > -- Matt > > Matt, Try "my_3d_axes.set_axis_off()". I should probably override set_visible() to work as expected... Ben Root |
|
From: Benjamin R. <ben...@ou...> - 2011-09-07 19:21:26
|
On Wed, Sep 7, 2011 at 2:14 PM, Joe Kington <jki...@wi...> wrote: > This no longer seems to work with matplotlib 1.0.1. > > As a quick example: > > import numpy as np > import matplotlib.pyplot as plt > from mpl_toolkits.mplot3d import Axes3D > > fig = plt.figure() > ax = fig.add_subplot(111, projection='3d') > > x,y,z,c = np.random.random((4,10)) > ax.scatter(x, y, z, c=c) > ax.set_axis_off() > > plt.show() > > The attached .png shows the result on my system... Is this a bug, or am I > doing something strange? > > Thanks! > -Joe > > Hmmm, try putting that call right after the add_subplot() call. I don't have time to test it out right now, but I wonder if the axes are being drawn once prior to the call to set_axis_off(). I would also be interested to know if the axes disappear when you interact with it. Ben Root |
|
From: Ethan G. <eth...@gm...> - 2011-09-07 19:33:36
|
I see the same thing here (from within ipython -pylab), and moving the ax.set_axis_off() immediately after the add_subplot call doesn't change anything. Interacting with the plot doesn't change anything either. Ethan On Sep 7, 2011, at 1:21 PM, Benjamin Root wrote: > On Wed, Sep 7, 2011 at 2:14 PM, Joe Kington <jki...@wi...> wrote: > This no longer seems to work with matplotlib 1.0.1. > > As a quick example: > > import numpy as np > import matplotlib.pyplot as plt > from mpl_toolkits.mplot3d import Axes3D > > fig = plt.figure() > ax = fig.add_subplot(111, projection='3d') > > x,y,z,c = np.random.random((4,10)) > ax.scatter(x, y, z, c=c) > ax.set_axis_off() > > plt.show() > > The attached .png shows the result on my system... Is this a bug, or > am I doing something strange? > > Thanks! > -Joe > > > Hmmm, try putting that call right after the add_subplot() call. I > don't have time to test it out right now, but I wonder if the axes > are being drawn once prior to the call to set_axis_off(). I would > also be interested to know if the axes disappear when you interact > with it. > > Ben Root > > ------------------------------------------------------------------------------ > Using storage to extend the benefits of virtualization and iSCSI > Virtualization increases hardware utilization and delivers a new > level of > agility. Learn what those decisions are and how to modernize your > storage > and backup environments for virtualization. > http://www.accelacomm.com/jaw/sfnl/114/51434361/_______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users |
|
From: Matthew K. G. <mk...@cs...> - 2011-09-07 19:40:32
|
I tried Joe's code, with the call to ax.set_axis_off() moved to right after add_subplot(), as Ben suggested. The axes are still not disappearing, nor do they disappear when I interact with it (by rotating the plot). -- Matt On Wed, Sep 7, 2011 at 3:21 PM, Benjamin Root <ben...@ou...> wrote: > On Wed, Sep 7, 2011 at 2:14 PM, Joe Kington <jki...@wi...> wrote: > >> This no longer seems to work with matplotlib 1.0.1. >> >> As a quick example: >> >> import numpy as np >> import matplotlib.pyplot as plt >> from mpl_toolkits.mplot3d import Axes3D >> >> fig = plt.figure() >> ax = fig.add_subplot(111, projection='3d') >> >> x,y,z,c = np.random.random((4,10)) >> ax.scatter(x, y, z, c=c) >> ax.set_axis_off() >> >> plt.show() >> >> The attached .png shows the result on my system... Is this a bug, or am I >> doing something strange? >> >> Thanks! >> -Joe >> >> > Hmmm, try putting that call right after the add_subplot() call. I don't > have time to test it out right now, but I wonder if the axes are being drawn > once prior to the call to set_axis_off(). I would also be interested to > know if the axes disappear when you interact with it. > > Ben Root > > |
|
From: Joe K. <jki...@wi...> - 2011-09-07 19:44:10
|
Interestingly, things work perfectly with the latest build from guithub. Presumably the bug was fixed already? On Wed, Sep 7, 2011 at 2:40 PM, Matthew Koichi Grimes <mk...@cs...>wrote: > I tried Joe's code, with the call to ax.set_axis_off() moved to right after > add_subplot(), as Ben suggested. The axes are still not disappearing, nor do > they disappear when I interact with it (by rotating the plot). > > -- Matt > > > On Wed, Sep 7, 2011 at 3:21 PM, Benjamin Root <ben...@ou...> wrote: > >> On Wed, Sep 7, 2011 at 2:14 PM, Joe Kington <jki...@wi...> wrote: >> >>> This no longer seems to work with matplotlib 1.0.1. >>> >>> As a quick example: >>> >>> import numpy as np >>> import matplotlib.pyplot as plt >>> from mpl_toolkits.mplot3d import Axes3D >>> >>> fig = plt.figure() >>> ax = fig.add_subplot(111, projection='3d') >>> >>> x,y,z,c = np.random.random((4,10)) >>> ax.scatter(x, y, z, c=c) >>> ax.set_axis_off() >>> >>> plt.show() >>> >>> The attached .png shows the result on my system... Is this a bug, or am I >>> doing something strange? >>> >>> Thanks! >>> -Joe >>> >>> >> Hmmm, try putting that call right after the add_subplot() call. I don't >> have time to test it out right now, but I wonder if the axes are being drawn >> once prior to the call to set_axis_off(). I would also be interested to >> know if the axes disappear when you interact with it. >> >> Ben Root >> >> > |
|
From: Benjamin R. <ben...@ou...> - 2011-09-07 20:04:30
|
On Wed, Sep 7, 2011 at 2:43 PM, Joe Kington <jki...@wi...> wrote: > Interestingly, things work perfectly with the latest build from guithub. > Presumably the bug was fixed already? > > Uhm, sure! I totally intended for that nasty bug to be fixed for the upcoming release... <_< Seriously, though, I made many changes to mplot3d as a part of my refactoring efforts. I would not be surprised if things magically break or get fixed because of it. I am glad you can confirm that the latest build works. I will take a peek at the v1.0.1 branch and see if there is an obvious fix for them. Ben Root |
|
From: Matthew K. G. <mk...@cs...> - 2011-09-07 20:14:06
|
Thanks Ben, I for one would be very interested in any workarounds you might find that don't require an upgrade from 1.0.1. -- Matt On Wed, Sep 7, 2011 at 4:04 PM, Benjamin Root <ben...@ou...> wrote: > On Wed, Sep 7, 2011 at 2:43 PM, Joe Kington <jki...@wi...> wrote: > >> Interestingly, things work perfectly with the latest build from guithub. >> Presumably the bug was fixed already? >> >> > Uhm, sure! I totally intended for that nasty bug to be fixed for the > upcoming release... <_< > > Seriously, though, I made many changes to mplot3d as a part of my > refactoring efforts. I would not be surprised if things magically break or > get fixed because of it. I am glad you can confirm that the latest build > works. I will take a peek at the v1.0.1 branch and see if there is an > obvious fix for them. > > Ben Root > > |
|
From: Benjamin R. <ben...@ou...> - 2011-09-07 20:35:54
Attachments:
hide3daxes.patch
|
On Wed, Sep 7, 2011 at 3:13 PM, Matthew Koichi Grimes <mk...@cs...>wrote: > Thanks Ben, I for one would be very interested in any workarounds you might > find that don't require an upgrade from 1.0.1. > > -- Matt > > Ok, looks like the hiding of the 3d axes was a feature added after the v1.0 release (but before I started working on mplot3d). This patch should enable the basic feature without interfering with existing functions. To hide the axes, you would have to set the private member "_axis3don" to False, like so: ax = plt.gca(projection='3d') ax._axis3don = False If you do it this way, then you will get what you want now, and your code will still be compatible with mplot3d when you upgrade (although the preferred method would be to call set_axis_on() or set_axis_off()). I hope that helps! Ben Root |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X