Skip to content

Revisit need for separate repeat expansion processing #458

Description

@apriltuesday

In 2019-2020, consequence prediction for repeat expansion variants was implemented via a bespoke pipeline, not going through VEP and using a limited set of consequence terms (short tandem repeat & trinucleotide). We should review the reasons for this decision (refer e.g. to minutes), discuss pros/cons of this strategy vs. unifying consequence prediction in VEP, and implement any necessary changes

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions