You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ok so I can see a bug report having a working colorbar #4952. So I figure maybe the issue is that specifying individual series for x, y and z dimensions is not working. Instead I should provide the dataframe and then specify which columns to use for what?
But how to do this is not documented in the reference example or docstring
Maybe I would know if I am a super user of HoloViews. But it is not a fair requirement that users should be that. Using the docstring in combination with the reference guide should be enough for non-advanced use cases. It should take a few minutes at most to get a working example not 3 hours of studying a tutorial/ guide, looking at discourse and looking at github.
So my option now is to study a bug report on Github !!!! in the hope to figure out how this works.
After studying that example I get something working
But I'm left with the feeling that this cannot really be the solution (renaming columns to x, y, z), I've not learned anything and it works for this use case but probably a little tweak on the use case will raise new questions.
Solution
Either fix bug if this is a bug or add a meaningful, working example of this use case to the reference documentation.
The text was updated successfully, but these errors were encountered:
Ok, so after studing the code of Scatter3D I can see x,y,z should be kdims. This is not documented in an easy to find place like docstring or reference documentation. Its not obvious as for a 2D Scatter x is a kdim and y is a vdim. If I should have guessed, I would have guessed x,y were kdim and z was vdim. Making them all kdim is a mistake I believe. It makes HoloViews unintuitive.
Can we close this issue since the original issue was resolved in #5418 and showing of docstring in hv.help output is in #5421? @MarcSkovMadsen, if you want to bring up the issue of "Making them all kdim is a mistake".. I think that's best done in a new issue.
I am trying to help a user add a colorbar to his
Scatter3D
plot https://discourse.holoviz.org/t/colorbar-in-plotly-scatter3d/1864But it does not work
Original Bug
Try to get it working
Ok so I can see a bug report having a working colorbar #4952. So I figure maybe the issue is that specifying individual series for
x
,y
andz
dimensions is not working. Instead I should provide the dataframe and then specify which columns to use for what?But how to do this is not documented in the reference example or docstring
Maybe I would know if I am a super user of HoloViews. But it is not a fair requirement that users should be that. Using the docstring in combination with the reference guide should be enough for non-advanced use cases. It should take a few minutes at most to get a working example not 3 hours of studying a tutorial/ guide, looking at discourse and looking at github.
So my option now is to study a bug report on Github !!!! in the hope to figure out how this works.
After studying that example I get something working
But I'm left with the feeling that this cannot really be the solution (renaming columns to x, y, z), I've not learned anything and it works for this use case but probably a little tweak on the use case will raise new questions.
Solution
Either fix bug if this is a bug or add a meaningful, working example of this use case to the reference documentation.
The text was updated successfully, but these errors were encountered: