-
Notifications
You must be signed in to change notification settings - Fork 1
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
Named alleles #33
Named alleles #33
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes looks ok.
The current model (if kept as is) would have to thoroughly explain though because it is a bit confusing.
The new haplotypeId
seems to make sense since the named alleles represent haplotypes but in some case it won't match. (haplotypeId: GSTT1 non-null/non-null
). Maybe we should discuss with OT to have a more appropriate name
For the genotype
, it is similarly ambiguous although more often wrong than right.
The options are:
- Changing the name to something that reflect the heterogenicity of the data
- Document the heterogenicity in the field's description.
Updates to schema as per this thread |
Better diff of test output here
Example named-allele evidence: