-
Notifications
You must be signed in to change notification settings - Fork 34
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
23andMe deletions #11
Comments
Found a bunch more info on the 23andme API docs https://api.23andme.com/docs/reference/#genotypes "For the user's profile, returns the base-pairs, like AA, for the given locations. The value can have Ds or Is for deletions and insertions (for example, DD or DI). It can be __ if the customer is not on a chip that calls that location, or hasn't yet unlocked their call since it corresponds to a sensitive report. It can be -- if the customer is on a chip that calls that location, but we could not determine it. To keep consistency with the /genomes endoint, which always returns two base pairs, hemizygous calls (such as on X-linked genes in males) will also return two base pairs." Cases to cover correctly: --, DD, DI, __ For __ we should probably log an error that says the user needs to go click "unlock" or whatever on 23andme to get the data |
Note that some users cannot unlock this data at all:
|
fixed in 1.1.2 |
No call ( |
@zhaofengli That makes sense, want to send a PR? I think https://github.com/genomejs/gql might need some tweaks for that. Have you seen any docs on the 23andme csv format? |
genomejs/gql#4 (comment)
genomejs/gql#4 (comment)
The text was updated successfully, but these errors were encountered: