-
Notifications
You must be signed in to change notification settings - Fork 20
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
Genotype Interpretation and Possible bugs #45
Comments
Hi @anh151
This means that you have *2 and *41 with an extra SNP rs368858603 that is not part of either *2 or *41 definition.
This is *68; :2 is just an internal distinction between two *68 variants present in the database.
This means that you have *4.021 augmented with some extra SNPs (or, in some cases, with some SNPs removed). Such alleles were observed in some of our samples (see
This means that you have 3 copies of CYP2D6: *1, *94 and *10. Each copy has a distinct star-allele.
This is a complete gene deletion on both chromosomes. |
Hi @inumanag For the *5/*5 scenario my question was related to the |
Hi @anh151 That is expected... right now. I can address this in the next release (the file will be still empty, but I can add a comment--- would that work?) |
Hi @inumanag Thanks, |
It should only happen if you have two deletion alleles (*5/*5 in CYP2D6 case; for other genes, the * number might differ). |
Sounds good. Thanks for the help. |
Hello,
I have several questions about Aldy genotypes and a possible bug report. I am using the latest version of Aldy with the default ILP solver. I have WGS samples that I am using to call CYP2D6.
I have a few genotype results that I need help interpreting.
I have a few samples where the stdout call from Aldy is *5/*5. However, the output .tsv file is blank. Why would this be the case? Example is shown below.
I can provide a debug report for anything shown here if needed.
The text was updated successfully, but these errors were encountered: