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

Annotation as a Service #5

Open
Jessime opened this issue Jul 31, 2018 · 1 comment
Open

Annotation as a Service #5

Jessime opened this issue Jul 31, 2018 · 1 comment
Assignees

Comments

@Jessime
Copy link

Jessime commented Jul 31, 2018

Currently, we only parallelize VEP as far as bringing up a VM per VCF file, running VEP on each file, and storing newly annotated files back on disk. An attractive option for parallelizing VEP is to host instances of a server listening for annotation requests. Several of these components are flexible, but the stack might look something like:

App Engine → Docker → Flask server → VEP

There are several attractive aspects of this parallelization option:

  1. It's relatively straightforward; not much code needs to be written.
  2. Since it processes each variant individually, it can be integrated into the Dataflow pipeline of VT.
  3. In the long term, the docker container could contain multiple annotation programs, and users could dictate which of them to select as part of their request to the flask server.
@bashir2
Copy link
Member

bashir2 commented Oct 25, 2018

A prototype of this idea is implemented in PR #7.

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

No branches or pull requests

2 participants