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

Refactor vep process to support different commands and versions - HIGH PRIORITY (CLIN-3407) #38

Open
LysianeBouchard opened this issue Oct 31, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@LysianeBouchard
Copy link
Contributor

LysianeBouchard commented Oct 31, 2024

Description of feature

We should limit hard-coded command line options to the minimum.

If possible, we would like the implementation to work with other VEP versions (>= v103). This means that if we switch the Docker container to one matching an older VEP version, it should still function correctly. If this requires too much effort, it can be addressed in a dedicated issue.

See https://ferlab-crsj.atlassian.net/browse/CLIN-3407

@LysianeBouchard LysianeBouchard added the enhancement New feature or request label Oct 31, 2024
@LysianeBouchard LysianeBouchard changed the title Refactor vep to support different vep commands and vep versions Refactor vep process to support different commands and versions - HIGH PRIORITY Oct 31, 2024
@LysianeBouchard LysianeBouchard changed the title Refactor vep process to support different commands and versions - HIGH PRIORITY Refactor vep process to support different commands and versions - HIGH PRIORITY (CLIN-3407) Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant