Open matteofloris opened 2 years ago
Hi @matteofloris I'm sorry to hear you're having problems. The VCF looks fine. I think the MRCIEU/gwasglue package is parsing the values incorrectly. I have created an issue.
thank you so much Matthew!
Il giorno gio 30 giu 2022 alle ore 19:12 Matthew Lyon < @.***> ha scritto:
Hi @matteofloris https://github.com/matteofloris I'm sorry to hear you're having problems. The VCF looks fine. I think the MRCIEU/gwasglue package is parsing the values incorrectly. I have created an issue https://github.com/MRCIEU/gwasglue/issues/33.
— Reply to this email directly, view it on GitHub https://github.com/MRCIEU/gwas2vcf/issues/78#issuecomment-1171476997, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACZ5JNG2L5PL5PKI2KCFRGLVRXIPZANCNFSM52GPEJQQ . You are receiving this because you were mentioned.Message ID: @.***>
--
Matteo Floris, PhD Associate Professor - Medical Genetics Department of Biomedical Sciences University of Sassari (Italy) Tel +39.333.48.57.679 email: @., @.
Tutto quello che non so l'ho imparato a scuola (Leo Longanesi)
During an attempt to perform a colocalization test with gwasglue, I noticed that a dataset processed with gwas2vcf is different from the same dataset preprocessed by Opengwas. I give an example below.
1) download sumstats for GCST90001585 study:
2) extract first 10.000 rows from sumstats (just for debugging)
3) run main.py on the test sumstats:
with the following params:
4) with the Opengwas dataset I am able to perform colocalisation of this dataset against itself, while it is not possible to do the same process with the dataset generated by gwas2vcf, because I obtain this error:
To understand the reason, I tried to compare the vcf generated by gwas2vcf with the vcf available at https://gwas.mrcieu.ac.uk/datasets/ebi-a-GCST90001585/, for example at position 54421:
the only difference I see is the presence of AF and SS fields in the last column of the VCF. Do you have any explanation about this issue?