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

[FEATURE] Optional output from VEP in vcf-, json- or tab-format #1774

Closed
asp8200 opened this issue Jun 13, 2022 · 0 comments · Fixed by #1775
Closed

[FEATURE] Optional output from VEP in vcf-, json- or tab-format #1774

asp8200 opened this issue Jun 13, 2022 · 0 comments · Fixed by #1775
Assignees

Comments

@asp8200
Copy link
Contributor

asp8200 commented Jun 13, 2022

Is your feature request related to a problem? Please describe

As part of the Sarek-project, we would like the VEP-module ENSEMBLVEP (modules/ensemblvep/main.nf) could be configured to output either a vcf-file, a json-file or a tab-file, c.f. nf-core/sarek#575

Describe the solution you'd like

The output-file-format is controlled through task.ext.args while the output-file-extension is set by task.ext.args2. This approach was developed with @maxulysse and @FriederikeHanssen, here: nf-core/sarek#582

Describe alternatives you've considered

No response

Additional context

No response

@asp8200 asp8200 self-assigned this Jun 13, 2022
asp8200 added a commit to asp8200/modules that referenced this issue Jun 13, 2022
asp8200 added a commit that referenced this issue Jun 15, 2022
* Making the output from the VEP-moduel (ENSEMBLVEP) optionally vcf, json or tab. #1774

* Trying to fix tests

* Still trying to fix tests

* Fetching the vep-output-file-extension from the args.

* Update meta.yml

* WIP: Adding tests for vep-output json and tab

* updated the test.yml

Co-authored-by: nvnieuwk <[email protected]>
Co-authored-by: nvnieuwk <[email protected]>
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

Successfully merging a pull request may close this issue.

1 participant