Scatter3D: arguments (c,s,...) are not taken into account #152

Closed
ddale opened this Issue Jun 20, 2011 · 6 comments

4 participants

@ddale

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
@WeatherGod
Matplotlib Developers member

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 WeatherGod was assigned Jun 21, 2011
@WeatherGod
Matplotlib Developers member

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
Matplotlib Developers member

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

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.

@WeatherGod WeatherGod added a commit to WeatherGod/matplotlib that referenced this issue Mar 13, 2012
@WeatherGod WeatherGod Fix scatter3d bug
* Found a simple solution to the "colors disappear after interacting with
  a scatter3d plot" bug. Should close #761 and close #152.
aa5bdbe
@WeatherGod
Matplotlib Developers member

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
Matplotlib Developers member

It appears @WeatherGod has fixed this.

@pelson pelson closed this Aug 19, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment