You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
It's relatively straightforward; not much code needs to be written.
Since it processes each variant individually, it can be integrated into the Dataflow pipeline of VT.
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.
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: