-
Notifications
You must be signed in to change notification settings - Fork 120
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
'' instead of None for inexistent VEP values #639
Comments
Agreed, although currently GEMINI doesn't officially support the most recent versions of VEP that do HGVSc and HGVSp. GEMINI officially only supports up to VEP v75. @brentp Whenever you get around to officially supporting VEP v83, this is an issue for all custom VEP fields that I've tested in VEP v82 and v83. |
ok. this is news to me. any time you find something like this, an example VCF with no genotypes will be a great help. It will likely take me longer to update vep and annotate an example than it will to fix the bug-- so, yeah examples greatly appreciated. |
VEP vcf made with VEP v82/v83
|
@jxchong and @muraveill so, I made some changes and now have:
Does that look sensible? I'm |
Works for me |
Thanks guys, this will be in 0.18.1 |
Empty values when reading from custom fields added through VEP (such as HGVSc and HGVSp) are represented by the empty string in the database. I think it could be safely replaced by NULL.
The text was updated successfully, but these errors were encountered: