manta FILTER==PASS and any cnv with 90% overlap #77
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.
Purpose/implementation Section
What scientific question is your analysis addressing?
Update scripts/merged_to_individual_files.py to create the Snakemake file and run the module only for tutor WGS and generate 2/3 cnv caller consensus calls
Adding a FILTER==PASS for manta calls used in copy_number_consensus_call. I think this filter is necessary so that we use a subset of high-confidence broad SVs called by manta.
After investigation of consensus call with only Manta FILTER==PASS we see the CNV alterations n controlfreec and cnkit .
We believe criteria for cnvs to have 50% reciprocal overlap might be too stringent. After the Update manta FILTER=='PASS' Part3 : oncoprint rerun AlexsLemonade/OpenPBTA-analysis#1116 we are missing some subtype defining CNVs. For example chr19 amplification in BS_K07KNTFY is seen in both controlfreec and cnvkit but missed out of consensus calls because cnvkit region is 11% of controlfreec region so we want to expand the overlap to include any CNV that overlaps 90% or more of a CNV in other caller.
What was your approach?
Added
since 11th column is FILTER
AND add the logic below to include any CNV that has 90% or more overlap with a CNV in another caller
What GitHub issue does your pull request address?
d3b-center/ticket-tracker-OPC#151
d3b-center/ticket-tracker-OPC#152
Directions for reviewers. Tell potential reviewers what kind of feedback you are soliciting.
Which areas should receive a particularly close look?
Does the update in scripts/merged_to_individual_files.py look right? We want to make the consensus cnv module only for WGS for OT I believe but handling WXS can be added as an update in another PR.
Is there anything that you want to discuss further?
NA
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)?
tables
What is your summary of the results?
This summary is specific to PBTA data
Broad SVs calls from manta that don't have FILTER=='PASS' are removed.
The manta FILTER columns are distributed as :
Since looking at some deep deletion in chrX discrepancy lead to this investigation I'm pointing out the differences in deep deletions in consensus cnv in this PR compared to master
We see comparable calls in both versions of consensus cnv calls in all chromosome except chrX. Majority of the deep deletions in chrX are removed if we only filter for calls that PASS all filters in manta. Suggesting, that majority of the chrX deep deletions in the current master branch are low confidence calls.
Reproducibility Checklist
Documentation Checklist
README
and it is up to date.analyses/README.md
and the entry is up to date.