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

How to use single breakend to increase detection sensitivity for insertions #33

Open
tgong1 opened this issue Feb 11, 2021 · 2 comments

Comments

@tgong1
Copy link

tgong1 commented Feb 11, 2021

Hi Daniel,

I have some questions regarding how to use single breakend calls to increase calling sensitivity, especially for insertions. The version of GRIDSS I have used was 2.8.3.

Q1. This is what I'm doing now to obtain SV types. I'd like to confirm that "breakpointRanges" will remove all single breakend calls?
vcf = readVcf("gridss.vcf") ###the output vcf from gridss_somatic_filter.R
gr = breakpointRanges(vcf)
svtype <- simpleEventType(gr) ### following simple-event-annotation.R

Q2. Is this the right way to obtain single breakend calls? How I classify them into SV types? Can I see all of them as insertions detected?
begr = breakendRanges(vcf)

Thank you for your time and help.
Tingting

@DarioS
Copy link

DarioS commented Feb 11, 2021

This could be moved to StructuralVariantAnnotation Issues by the moderator.

@d-cameron d-cameron transferred this issue from PapenfussLab/gridss Feb 11, 2021
@d-cameron
Copy link
Member

breakpointRanges will remove all single breakend calls?

By default, it only reports breakpoint calls.

Q2. Is this the right way to obtain single breakend calls?

Use breakendRanges() for single breakend calls (or unpartneredBreakends=TRUE - they do the same thing).

How I classify them into SV types?

Fundamentally, GRIDSS is a breakpoint (/single breakend) detection tool. It does not classify SVs.

Can I see all of them as insertions detected?

Not necessarily. An insertion will have two single breakends at the same/nearby position in opposite orientation. LINE integrations are frequently reported as a breakpoint to the donor site and a single breakend to poly-A sequence in the opposite orientation. MSI expansions also get frequently reported as single breakends. Viral integrations also show up as single breakends (but are more reliably detected with VIRUSBreakend)

If you want to do SV classification, then I strongly suggest using LINX classifications (it now supports tumour-only runs). LINX actually does perform SV classification and has pretty good event resolution capabilities.

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

3 participants