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

[BUG]: VEP version in output vcf and HTML summary report is not updated as per the vep_cache_version provided by the user. #573

Closed
IndhuPS opened this issue Jun 1, 2022 · 3 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@IndhuPS
Copy link

IndhuPS commented Jun 1, 2022

Hi there!
Am running nf-core sarek pipeline for germline variants and using VEP for variant annotation using cache file (version 106). I use the flags --annotation_cache with --vep_cache_version 106 --vep_cache . The pipeline is executed successfully. However in my output vcf file and HTML report, I observe that the version is mentioned as "v99", although the cache file path refers to the 106version file.

Run command

nextflow -log germline_vep106.log -bg run nf-core/sarek -profile docker -with-report -with-trace -with-timeline --genome GRCh38 --input input.vcf.gz --outdir ./germline_vep106 --tools vep --vep_cache /vep_cache/ --annotation_cache --vep_cache_version "106" --cpus 64

Issue observed

In the output vcf file -
##VEP="v99" time="2022-05-18 07:23:04" cache="/homo_sapiens/106_GRCh38" ensembl-funcgen=99.0832337 ensembl=99.d3e7d31 ensembl-variation=99.642e1cd ensembl-io=99.441b05b 1000genomes="phase3" COSMIC="92" ClinVar="202109" ESP="V2-SSA137" HGMD-PUBLIC="20204" assembly="GRCh38.p13" dbSNP="154" gencode="GENCODE 40" genebuild="2014-07" gnomAD="r2.1.1" polyphen="2.2.2" regbuild="1.0" sift="sift5.2.2"

Expected output

Right version to be shown on the outputs.

@IndhuPS IndhuPS added the bug Something isn't working label Jun 1, 2022
@FriederikeHanssen FriederikeHanssen added this to the 3.0 milestone Jun 10, 2022
@maxulysse
Copy link
Member

The VEP version is for the VEP tool itself, the VEP cache version would be for the version of the cache.
It does say cache="/homo_sapiens/106_GRCh38" for the cache, which is coherent with the cache asked.
Which Sarek version did you use for this command?

@IndhuPS
Copy link
Author

IndhuPS commented Jun 14, 2022

Sarek version we are using is v2.7.1

@maxulysse
Copy link
Member

Then, version is actually correctly reported:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants