Repository navigation
Scatter3D: arguments (c,s,...) are not taken into account #152
Description
Original report at SourceForge, opened Thu Nov 19 15:42:05 2009
Following code does not represents the asked color variation for the plots in 3D.
Same problem appends if a variable size is asked for exemple (via s=z argument).
from mpl_toolkits.mplot3d.axes3d import *
import pylab as plt
x=y=z=range(10)
fig = plt.figure()
ax = Axes3D(fig)
ax.scatter3D(x,y,z,c=z,cmap=plt.cm.jet)
plt.show()
SourceForge History
- On Mon Jan 4 19:13:49 2010, by heeres: assigned_to: 100
Activity
WeatherGod commented on Jun 21, 2011
While this particular bug does not seem to exist any more, there does appear to be a new bug where rotating the 3d grid results in color lost.
WeatherGod commented on Jun 22, 2011
Further details: when interacting with a scatterplot that has been colored based on a colormap, the scatterpoints loses their color and turn blue. This only happens for colormapped plots, and only after interaction.
WeatherGod commented on Jul 11, 2011
I am not certain if I can fully resolve this. Since I don't believe that it is a release stopper, I will take it off the milestone list.
claumann commented on Oct 16, 2011
Any progress on this? I've just run into the same issue using the new ipython HTML notebook in addition to the osx backend (current masters on mpl and ipython). Color mapped scatter 3d plots work on first draw in the osx window, but revert to all blue points on interaction or when calling display(gcf()) to push them into the inline note book. Took me a while to figure out it seems to be a mpl bug rather than a ipy one.
Fix scatter3d bug
WeatherGod commented on Mar 13, 2012
For those still following this bug report, PR #762 should fix this issue and will be included in the v1.1.x bugfix release.
pelson commented on Aug 19, 2012
It appears @WeatherGod has fixed this.