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

Do we need a step to move non-bialellic SNPs from the VCF? #39

Open
janaobsteter opened this issue Nov 9, 2023 · 2 comments
Open

Do we need a step to move non-bialellic SNPs from the VCF? #39

janaobsteter opened this issue Nov 9, 2023 · 2 comments
Assignees

Comments

@janaobsteter
Copy link
Collaborator

In the ancestral allele inference, we filter the variants for SNPs, but we do allow multi-allelic SNPs since that is not a problem for the ancestral inference (it's just an allele count). However, some rule might fall if there are multiallelic variants in the VCF and the INFO file (for example, the get_major rule in prepare_files_for_tsinfer.smk.

@gregorgorjanc
Copy link
Member

We discussed in one of the meetings how we could convert multi-allelic sites to multiple bi-allelic sites. My understanding was that bcftools enables this conversion. Would that help?

@janaobsteter
Copy link
Collaborator Author

For now, let's filter the VCF to only keep biallelic SNPs to see how it behaves and then we can progress with adding other types of variants in the future.

@janaobsteter janaobsteter self-assigned this Nov 17, 2023
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

2 participants