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
The error message for invalid VEP-cache contains some seeming misleading info about invalid sample-sheet.
The sample-sheet only contains tumor-samples, but the following tools, which were requested by the option "tools", expect at least one normal-sample : ascat
The sample-sheet only contains normal-samples, but the following tools, which were requested with "--tools", expect at least one tumor-sample : ascat, controlfreec, mutect2
Path provided with VEP cache is invalid.
Make sure there is a directory named homo_sapiens/110_GRCh38 in /home/ubuntu/dev/./nPlease refer to https://nf-co.re/sarek/docs/usage/#how-to-customise-snpeff-and-vep-annotation for more information.
My guess is that the lines about the invalid sample-sheet comes from nf-validation.
Command used and terminal output
nextflow run main.nf -profile test_full,docker --vep_cache /some/invalid/path --outdir foo
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered:
Description of the bug
Observed on Sarek 3.3.2 (and on dev 51c7676) :
The error message for invalid VEP-cache contains some seeming misleading info about invalid sample-sheet.
My guess is that the lines about the invalid sample-sheet comes from nf-validation.
Command used and terminal output
nextflow run main.nf -profile test_full,docker --vep_cache /some/invalid/path --outdir foo
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: