Original report at SourceForge, opened Fri Jun 10 12:29:24 2011
If you enable a log scale when doing a 3D scatter plot, nothing is created and the program crashes. Attached is the error output.
You can easily reproduce this by taking the example scatter3d_demo.py and adding the line "ax.set_xscale('log')".
Confirmed, however the problem is more nuanced than this. First, the problem does not error-out if one does ax.w_xscale.set_scale('log'), however, this does not set the scale properly because the projection never takes it into account.
Calling ax.set_xscale (or ax.set_yscale) appears to trigger some other stuff that leads to an error for displaying the coordinates in the corner. ax.set_zscale does not appear to exist. However, given that scaling does not appear to work properly right now, I am not inclined to add it.
Problem seems to persist. I'm setting:
And then the ticks of the axes change to logarithmic scale:
While I'd expect the ticks to be equidistant and the data re-scaled, as it happens when using 2D plotting.
Well... it is better than it used to be. The issue is that there is a lot of code in mplot3d that just completely ignores the projection information of the axes. While significant progress has been made in axes3d.py, it is axis3d.py that still needs a lot of TLC.
@gllor or @WeatherGod t, I am facing the same problem (and hence is happy to find this discussion).. could you finally got it to work? Getting the 3d plot with data logarithmically rescaled??
@Panchie I'm sorry I cannot shed more light into the issue, I didn't get it working and didn't find any solution googling around.
+1 on this issue, stuck with exactly this problem
I would also like to see this issue resolved.
The problem is till there apparently. It is a big issue for me. I hope someone could resolve it soon.
any progress 3 years later? set_(x,y,z)scale still just sets axis labels, not axis scaling.
-1, just kidding, the log won't work with that .
The problem described sounds like a very simple problem, I mean as all the axes exist orthogonal to one another the problem should in theory exist no different for 3d as for 2d or for that matter any number of plotable dimensions. The fact that this problem has lasted so long tells me that the code says otherwise, in which case I imagine, as with a lot of the codebase, it needs a refactor, the good news I like doing.
The biggest problem though lies in the amount that needs refactoring. Starting at the base and working our way up, with bringing tools out of the backend (MEP 22) finished and general backend refactoring (MEP 27) on its way, I guess the main plotting functions will come next.
As @WeatherGod says, if anyone feels like jump in and looking through the code, then feel free (I only jumped in about a month or two ago myself), we can give guidance if needed and it works a lot better than +1s .
how hard would it be to make a workaround which prevents all set_scale('log') in 3D and calls a module which calculates the affected data array log (e.g. np.log(data) ) and changes the ticks labels to decimal power?
As long the bug exists a patch like this could help.
I will try to add an extra module in my 3D Scripts, where the data and fixed scale values will be modified, sth like this:
newscale = 
newscale = np.power(10,scale)
ax.scatter(xs., ys, np.log(zs), c=c, marker=m)