Skip to content
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

PindelRecordParser - investigate accurate VAF #42

Open
keiranmraine opened this issue Dec 11, 2015 · 1 comment
Open

PindelRecordParser - investigate accurate VAF #42

keiranmraine opened this issue Dec 11, 2015 · 1 comment

Comments

@keiranmraine
Copy link
Contributor

Currently we just parse out the reads that Pindel calls, it would be nice to evaluate that an event has no normal support and then run ssearch36 over reads in the primary BAM to generate an accurate VAF upfront and then use new values for the flagging/filtering.

@liangkaiye
Copy link

The new pindel reports the numbers of reads supporting normal and tumor allele. But as we cannot split reads near edges, the VAF is always underestimated. There is one competitive mapping perl script in ICGC validation evaluation exercise but it is slow as it extracts reads and calls bwa for mapping.

Sent from my iPhone

On Dec 11, 2015, at 11:59, Keiran Raine [email protected] wrote:

Currently we just parse out the reads that Pindel calls, it would be nice to evaluate that an event has no normal support and then run ssearch36 over reads in the primary BAM to generate an accurate VAF upfront and then use new values for the flagging/filtering.


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants