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
We had been talking about a tooltip where hovering over a transcript reveals a dot plot of abundance in every replicate, so that the user can see more than just aggregated means or medians.
I'm not sure where to put it, though. The MA plot is no good because some squares will have hundreds of genes when we only want a dotplot for one at a time. Putting it in the table sounds like it might be difficult. Maybe it would just be a third feature down at the bottom next to the heatmap? Idk, let's discuss.
The text was updated successfully, but these errors were encountered:
One thing occurred to me is that I could put it where p-value cutoff thing is, showing the individual abundances when a treatment row is hovered.
Question is, what's more useful-- small plot showing all the points? Or a data table?
The small plot idea might be weird because it would be showing individual abundances for both of the different treatments (i.e. the scales would be different)
If we could put all the individual abundances onto one plot I think that would be the most useful. I'm not sure I understand why the scales would be different—if three replicates for sample A are 5,6 and 7 RPKMs, and three replicates for sample B are 400, 650, and 675 RPKMs, that can all go on one plot (or on two plots side by side, with matching axes).
We had been talking about a tooltip where hovering over a transcript reveals a dot plot of abundance in every replicate, so that the user can see more than just aggregated means or medians.
I'm not sure where to put it, though. The MA plot is no good because some squares will have hundreds of genes when we only want a dotplot for one at a time. Putting it in the table sounds like it might be difficult. Maybe it would just be a third feature down at the bottom next to the heatmap? Idk, let's discuss.
The text was updated successfully, but these errors were encountered: