-
Notifications
You must be signed in to change notification settings - Fork 522
Fix: Correct vep_cache_path_full when refseq/merged option is present #1563
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Contributor
Author
|
I changed the signature of If adding a new parameter to this workflow is ok, I guess we need to change the declarations to 11? Nevermind, I forget one line of code. |
maxulysse
approved these changes
Jun 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this PR, I'm trying to fix this issue: ensembl-vep refseq/merged option broken.
Let's assume these param values:
As of sarek 3.4.2, we can feed custom VEP options via
params.vep_custom_argsto the pipeline.If
--refseqor--mergedis inparams.vep_custom_args, it will be passed to VEP's final command, and result in the following effects:--refseqis provided, VEP will use${vep_cache}/${vep_species}_refseq/${vep_cache_version}_${vep_genome}as the annotation source--mergedis provided, VEP will use${vep_cache}/${vep_species}_merged/${vep_cache_version}_${vep_genome}as the annotation sourceReference: https://useast.ensembl.org/info/docs/tools/vep/script/vep_options.html
When this happens (Let's assume
--refseqis inparams.vep_custom_args), in theANNOTATION_CACHE_INITIALISATIONworkflow, a wrongvep_cache_path_fullpath will be tested if exists, because it won't check ifparams.vep_custom_argscontains--refseq.I modified the related code such that in the
ANNOTATION_CACHE_INITIALISATIONworkflow,vep_cache_path_fullwill be built correctly by taking into consideration if--refseqor--mergedis present inparams.vep_custom_args.I've tested with in-house data, and it worked as expected: when
--refseqis present, VCF files will be annotated with RefSeq cache (e.g. "homo_sapiens_refseq/111_GRCh37"); when neither--refseqnor--mergedis present, they will be annotated with normal cache (e.g. "homo_sapiens/111_GRCh37).PR checklist
nf-core lint).nf-test test tests/ --verbose --profile +docker).nextflow run . -profile debug,test,docker --outdir <OUTDIR>).docs/usage.mdis updated.docs/output.mdis updated.CHANGELOG.mdis updated.README.mdis updated (including new tool citations and authors/contributors).