Skip to content
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

warn when pick flag is expected but not observed #36

Closed
zlskidmore opened this issue Feb 12, 2020 · 1 comment · Fixed by #70
Closed

warn when pick flag is expected but not observed #36

zlskidmore opened this issue Feb 12, 2020 · 1 comment · Fixed by #70

Comments

@zlskidmore
Copy link
Member

I have encountered issues wherree VEP --flag_pick appears to be broken, it will not flag a mutation with pick if that mutation intersects with multiple gene/transcript features. It would be beneficial if vep-annotation-reporter warned when it encounters entries where a pick flag is expected but not seen. In these cases it appears to pick the last consequence item from the vcf

@susannasiebert
Copy link
Collaborator

As it turns out, the underlying issue was already resolved in some previous version but as of 5.1.0 we now also output a warning for variants where none of the transcripts were PICK'ed and all transcripts' values are written to the output.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants