-
Notifications
You must be signed in to change notification settings - Fork 0
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
Make mutation and cluster plotting single sample compatible #166
base: main
Are you sure you want to change the base?
Make mutation and cluster plotting single sample compatible #166
Conversation
@graceooh Can you please attach figures/file path to the single and multi sample plots generated? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice bug fix, need to trim down to avoid unnecessary hardcoded parameters.
@@ -118,14 +129,32 @@ create.ccf.summary.heatmap <- function( | |||
hm.args$text.col <- ifelse(arr > contrast.thres, 'white', 'black'); | |||
} | |||
|
|||
if (same.as.matrix) { | |||
hm.args$yat <- 1.5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For parameters added here (line 132 - 148), is everything necessary? Generally, we want to avoid hard coding project/user specific params
arr <- as.data.frame(arr) | ||
colnames(arr) <- as.character(unique(DF$ID)) | ||
|
||
hm <- create.ccf.heatmap( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is somewhat redundant I think, especially since users can pass through the same.as.matrix
and yat
arguments to BPGs create.heatmap
.
Description
create.ccf.summary.heatmap and create.cluster.heatmap could not handle single samples. This pull request fixes this issue. It also allows create.ccf.summary.heatmap to also plot monoclonal / single sample results without erroring out.
Closes #...
Pipeline Run Results
Analysis Results
Checklist
This PR does NOT contain Protected Health Information (PHI). A repo may need to be deleted if such data is uploaded.
Disclosing PHI is a major problem1 - Even a small leak can be costly2.
This PR does NOT contain germline genetic data3, RNA-Seq, DNA methylation, microbiome or other molecular data4.
.png
, .jpeg
),.pdf
,.RData
,.xlsx
,.doc
,.ppt
, or other output files.To automatically exclude such files using a .gitignore file, see here for example.
I have read the code review guidelines and the code review best practice on GitHub check-list.
I have set up or verified the
main
branch protection rule following the github standards before opening this pull request.The name of the branch is meaningful and well formatted following the standards, using [AD_username (or 5 letters of AD if AD is too long)]-[brief_description_of_branch].
I have added the major changes included in this pull request to the
CHANGELOG.md
under the next release version or unreleased, and updated the date.Footnotes
UCLA Health reaches $7.5m settlement over 2015 breach of 4.5m patient records ↩
The average healthcare data breach costs $2.2 million, despite the majority of breaches releasing fewer than 500 records. ↩
Genetic information is considered PHI.
Forensic assays can identify patients with as few as 21 SNPs ↩
RNA-Seq, DNA methylation, microbiome, or other molecular data can be used to predict genotypes (PHI) and reveal a patient's identity. ↩