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
There have always been some differences after plotly conversion, but it's definitely gotten worse than before. (Before: seemed to just be that boxplots always showed outliers in the past, and jitter points have fills. Not too bad!)
Diagonal jitter banding: seems to be related to aes(text) not being successfully ignored by geom_jitter(). Potentially can fix by using plotly machinery to adjust hover info after ggplotly conversion.
violin and boxplot width/position issues only come into play when color.by is used to create sub-groupings:
boxplots don't dodge at all. need to investigate cause/fix
violin plot widths are not reduced accordingly. need to investigate cause/fix
The text was updated successfully, but these errors were encountered:
There are still some render differences, e.g. boxplots cannot be plotted in front of violin plots or jittered points, no matter what order they are given to the plots input, and boxplot outliers do not get turned off regardless of what's given to boxplot.show.outliers.
Diagonal jitter banding has been fixed in dittoViz, and will make it into the next major release of dittoSeq, where dittoViz functions will replace most dittoSeq visualization code!
There have always been some differences after plotly conversion, but it's definitely gotten worse than before. (Before: seemed to just be that boxplots always showed outliers in the past, and jitter points have fills. Not too bad!)
Multiple bits here...
The text was updated successfully, but these errors were encountered: