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

NA and SV Type in Vapor's results #5

Open
ghost opened this issue Nov 9, 2020 · 1 comment
Open

NA and SV Type in Vapor's results #5

ghost opened this issue Nov 9, 2020 · 1 comment

Comments

@ghost
Copy link

ghost commented Nov 9, 2020

Hi
I'm a little confused about vapor's output results

  1. first is about the NA and 0 in ‘VaPoR_GS’ column. I can understand that 0 means there is no support reads. But what about NA? I found in another issue where you said 'The local region is too messy for proper alignment to be generated'. So if the region is heavily repeated (STR or VNTR), the vapor cannot work well? But I found some repeat regions that can be validated by Vapor, which means not every repeat region is difficult for Vapor. So what kind of repeats can Vapor deal or is there any other conditions about 'region is too messy?

  2. About the SVTYPE column. Is this SV type predicted by Vapor? If yes, why NA and zero events in the first question still have predicted SV types? Is this SVTYPE trustable?

thanks.

Songbo Wang

@xuefzhao
Copy link
Collaborator

xuefzhao commented Nov 9, 2020

Hi, Songbo,

Thanks for your interest in VaPoR. 'NA' stands for regions that are either too repetitive that no clean recurrence pattern can be observed, or poorly covered by PacBio that not enough reads can be extracted for reliable revelation. It should be noted that VaPoR does not apply any reference panel (eg. segmental duplicates, or VNTR regions) to purposely exclude regions from validation. For the 2nd question, no vapor does not predict SVtype, it should be included as input.

Hope these would help clear our your confusion, but let me know if you have other questions,

Best,

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

No branches or pull requests

1 participant