-
Notifications
You must be signed in to change notification settings - Fork 1
Assess BRAF fusion breakpoint distribution by ancestry #43
Conversation
Can you add a run script with this module please |
…rvival-by-breakpoint
…rvival-by-breakpoint
Script 02 runs ok - will review again once 01 is working |
Note from slack: BS_SDZY6RZ3 this sample has two common breakpoints- inspecting arriba files, it looks like chr7:138867975 chr7:140787584 is the lower confidence one, so we should probably remove that one from analysis (I did this in #45 with a manual mutate making keep == no) |
@rjcorb i also realize I can remove a bunch of code from the next pr if we export the fusion results with breakpoint type, breakpoint here. That way it's not all duplicated. Do you want to export a data frame by patient id or add that onto the annotation file? |
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.
Will approve this, noting the ENSEMBL has been down for a week with no timeline on getting it back up 😬
https://www.ensembl.info/2024/01/18/downtime-of-the-ensembl-search-and-asia-mirror/
…oint Assess survival in BRAF fusion LGG by ancestry and breakpoint type
Purpose/implementation Section
What scientific question is your analysis addressing?
This PR assesses BRAF fusion breakpoint distribution by predicted ancestry, CNS region, and extent of tumor resection
What was your approach?
What GitHub issue does your pull request address?
#41
Directions for reviewers. Tell potential reviewers what kind of feedback you are
soliciting.
Which areas should receive a particularly close look?
Please review code in
02-fusion-breakpoints-by-ancestry.Rmd
and ensure script runs successfully:Rscript -e "rmarkdown::render('02-fusion-breakpoints-by-ancestry.Rmd')"
Is there anything that you want to discuss further?
I am currently pulling all breakpoint data for each patient rather than sample. Let me know if sample would be more appropriate
Is the analysis in a mature enough form that the resulting figure(s) and/or table(s) are
ready for review?
Yes
Results
What types of results are included (e.g., table, figure)?
What is your summary of the results?
Reproducibility Checklist
project Dockerfile.
Documentation Checklist
README
and it is up to date.