You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is about how to appropriately handle rsIDs with more than one alternate allele. See #5 for some context.
PharmGKB provides variant-level clinical annotations with additional phenotype descriptions provided per genotype - for example this annotation for rs10420097. Open Targets uses VCF-style chr_pos_ref_alt variant identifiers that are allele-specific.
Currently the code explodes records by genotype but only generates one variant identifier for the RS (using the 1st alternate allele lexicographically), which doesn't seem appropriate.
We should discuss with Open Targets how they'd like the information presented and what is feasible to generate from the data, and update the implementation accordingly.
The text was updated successfully, but these errors were encountered:
We forgot to talk about VEP, which of course predicts consequences for variants not genotypes... I guess we might need lists of consequences associated with a genotype? Might need to think about this more.
This is about how to appropriately handle rsIDs with more than one alternate allele. See #5 for some context.
PharmGKB provides variant-level clinical annotations with additional phenotype descriptions provided per genotype - for example this annotation for rs10420097. Open Targets uses VCF-style
chr_pos_ref_alt
variant identifiers that are allele-specific.Currently the code explodes records by genotype but only generates one variant identifier for the RS (using the 1st alternate allele lexicographically), which doesn't seem appropriate.
We should discuss with Open Targets how they'd like the information presented and what is feasible to generate from the data, and update the implementation accordingly.
The text was updated successfully, but these errors were encountered: