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

Polyploid version of whatshap haplotag #267

Closed
rvicedomini opened this issue Oct 22, 2020 · 7 comments
Closed

Polyploid version of whatshap haplotag #267

rvicedomini opened this issue Oct 22, 2020 · 7 comments

Comments

@rvicedomini
Copy link

Hello,
this question might be also related to #214. Is there any plan to introduce the polyploid version of haplotag (and split) in the main development branch of whatshap?

Thanks,
Riccardo

@tobiasmarschall
Copy link
Contributor

Hi Riccardo,

absolutely! Thanks for reminding us. Presently everybody is pretty busy with other tasks, so I expect that might not happen immediately, but please do ping us again if it hasn't happened in (say) a months time.

Best,
Tobias

@tobiasmarschall
Copy link
Contributor

PS: I assume you did see the branch polyploid-haplotag, didn't you?

@rvicedomini
Copy link
Author

Thank you very much for the answer!
Yes I'm already considering the polyploid-haplotag branch. I was just thinking it would be great to have polyploid haplotag in the main branch in order to benefit from all recent whatshap improvements (without having multiple versions installed).

Best,
Riccardo

@baozg
Copy link

baozg commented Dec 6, 2020

Hi, @tobiasmarschall

Would the polyploid-haplotag will merge into the main branch?

Best,
Zhigui

@tobiasmarschall
Copy link
Contributor

That's certainly the plan, but I'm not sure what the status is. @eblerjana or @ptrebert, could you comment?

@schrins
Copy link
Collaborator

schrins commented Mar 1, 2023

Haplotag should now support polyploid input with #410 being merged. The split command is still diploid, as far as I know. Since there is another issue (#408 ) with the same request, I will close this one and refer to the other for further comments.

@schrins schrins closed this as completed Mar 1, 2023
@baozg
Copy link

baozg commented Mar 1, 2023

Great! Thanks for your support!

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

4 participants