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

whatshap haplotag and split for polyploid #408

Closed
fangdm opened this issue Oct 31, 2022 · 4 comments
Closed

whatshap haplotag and split for polyploid #408

fangdm opened this issue Oct 31, 2022 · 4 comments

Comments

@fangdm
Copy link

fangdm commented Oct 31, 2022

Hi, I am using whatshap to analyze polyploid data, and when I run 'whatshap haplotag', I find that it can't handle polyploid data, there is no "--ploidy" parameter. The results of haplotag are shown as diploids (H1, H2 and none) in resule "haplotypes.tsv".
Any ideas on how to fix for polyploid?

the command as:
whatshap haplotag -o haplotagged.bam --reference ref.fa phased.vcf.gz aln.best.sort.bam --output-threads=5 --ignore-read-groups
--output-haplotag-list haplotypes.tsv

Thank you.

Whatshap version 1.6

@fangdm
Copy link
Author

fangdm commented Oct 31, 2022

it's previous command as:
whatshap polyphase -o phased.vcf --reference=ref.fa --mapq 20 --ploidy 3 -t 1 --indels --ignore-read-groups --distrust-genotypes variants.vcf aln.best.sort.bam

"variants.vcf" was based on FreeBayes with illumina, and "aln.best.sort.bam" from HIFI data mapping.

Thank you.

@schrins
Copy link
Collaborator

schrins commented Nov 1, 2022

I never participated in the haplotag command, but there was supposed to be a polyploid version of it at some point. I think it's still hidden in the polyploid-haplotag branch, which is based on quite an old whatshap version now. I might have a look at this, when I have the time, because it is a useful feature, but I can make no promises.

@Adamtaranto
Copy link

Polyploid haplotagging would be super useful! 1++ for this feature.

@schrins
Copy link
Collaborator

schrins commented Oct 16, 2023

Closing this, as the feature has been implemented in the meantime.

@schrins schrins closed this as completed Oct 16, 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

3 participants