-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vis_compare expansion #109
Comments
Heya @Maschette ! :) Thanks for putting the time into this :) Do you think you could provide an example of the kinds of data you were imagining being compared here? I think that the idea is worthwhile exploring! |
Hey @njtierney, Anyway, use case: this is a subset of genetics data from a technical replicate.
The other option would be to display both columns of data and show side by side how they are different. |
I like this a lot! I would like to include this in visdat! Two things to think about:
Thanks again for taking the time to do this, I really like it! |
Hi Nick, |
Hi Dale,
|
This is where go to; since it would be a new function I removed the "same" option from case_when() the thing that would be cool would be to work out if you are comparing data frames with different names to have the names of both the columns in the x-axis.
|
oh it just occurred to me by removing the 'same' from type option you would also remove the if statement as it will always do it. |
Suggestion for a new function which would essentially be an extension of vis_compare but has colors to specify what the 'not same' change is. Admittedly this is limited use case as too many variables and it would be super messy. The main thing purpose I was thinking of is tracking changes in genetics technical replicates where the possible values are 0, 1, 2, NA and you want to keep track of what these values change to between replicates.
Halfway through writing this I thought I may as well have a crack, this works although the 'new bit' could be a better, I'm primarily a base kid so that is what I did it in rather than mutate. Also I didn't use your colors and went with viridis. Finally the only thing I didnt do out of lazyness was NA's being used in from/to scenarios should be "NA" so that ggplot doesn't remove them and they get a color.
You could also not implement this if you think it is weird and that would be super fine.
The text was updated successfully, but these errors were encountered: