Added plotXY to re-use scater's aesthetics for arbitrary x/y plots.#223
Merged
Conversation
This reduces the hassle of re-assembling the ggplot2 calls manually.
Owner
|
Looks good thanks. Re: docs, I'd be more inclined to liberally apply |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Again useful for some workflows where you have some unassociated X/Y coordinates and you want to create a scater-style workflow without mocking up an SCE to run, e.g.,
plotColData().As an aside, the documentation for some of the newer functionality in
.central_plottercould probably be pushed fromplotColDatatoscater-plot-argsif it's shared across multiple plotting functions, it would save the effort of redocumenting them in each one. Even the overview of the types of plots (violin, grouped violin, scatter, etc.) could probably be moved there.