-
Notifications
You must be signed in to change notification settings - Fork 99
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
Imputation panels #41
Comments
Thanks for your interest, and sorry for the slow reply. The T2T Variants team recently produced genotypes for the 1000 Genomes Project samples, which are described in this paper: https://www.biorxiv.org/content/10.1101/2021.07.12.452063v1.full The "Data and materials availability" section provides links to download these data. Note that the genotypes are currently unphased, but we are currently working on phasing. |
With the release of the 1KGP genotypes, do you know someone in the consortium is working on phasing the calls? Do you all anticipate the phasing being performed by, say, April? (If not, I might be interested in helping out on that project.) |
Hi @JosephLalli, I can confirm that we are working on this, and I apologize that it has taken so long. While we think we have worked out how to replicate phasing pipeline used previously by the NYGC, we are now trying to evaluate the accuracy of the phasing results and their consistency with earlier phased genotype data generated using other reference genomes. We welcome your help in this effort if you're interested. If you email me (rajiv.mccoy jhu.edu) and my student, Andrew Bortvin (abortvi2 jhu.edu), we can share more details about the current status. Best, Rajiv |
I've reached out to you via email @rmccoy7541. For those who may be interested, I've taken the liberty of phasing the T2T dataset myself. The repository, describing the methods used and performance metrics, can be found here. The panel itself can be downloaded as a tarball from a Zenodo repository located here. |
Hi, Are you aware of any CHM13 based imputation panels?
The text was updated successfully, but these errors were encountered: