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

figure out why some annotations don't implement Annotation and decide if they should #2493

Closed
lbergelson opened this issue Mar 20, 2017 · 2 comments

Comments

@lbergelson
Copy link
Member

Some annotation base classes don't implement the Annotation marker interface. (i.e. VariantAnnotation) This was the case in gatk3 as well, but it's unclear why. It may be a historical artifact rather than a design decision, in which case it should be corrected. If it's important to have the marker interface then all the annotations should implement them. If it isn't, then we should probably remove it or move abstract functions into the interface.

@droazen droazen added this to the 4.0 release milestone Mar 20, 2017
@droazen droazen assigned jamesemery and unassigned lbergelson Jul 17, 2017
@droazen
Copy link
Contributor

droazen commented Jul 17, 2017

Adding to annotation epic #3274

@jamesemery
Copy link
Collaborator

This has been handled by other annotation pull requests like #3851

lbergelson pushed a commit that referenced this issue Feb 26, 2018
* Beta port of GATK3 version of VariantAnnotator with the necessary changes to the annotation engine and client annotations to support annotating variants independent of the haplotype caller.
* The annotations closely match the GATK3 output, including replicating existing bugs in some cases
* closes #51 
* close #2493
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants