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

Misleading info in error message concerning invalid path to VEP-cache #1326

Open
asp8200 opened this issue Nov 13, 2023 · 4 comments
Open

Misleading info in error message concerning invalid path to VEP-cache #1326

asp8200 opened this issue Nov 13, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@asp8200
Copy link
Contributor

asp8200 commented Nov 13, 2023

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.

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

@asp8200 asp8200 added the bug Something isn't working label Nov 13, 2023
@FriederikeHanssen
Copy link
Contributor

Canyou check whether this is still relevant on dev? Pretty sure a bunch of stuff was fixed around this

@FriederikeHanssen
Copy link
Contributor

OK found the corresponding slack thread, and it is also present on dev

@asp8200
Copy link
Contributor Author

asp8200 commented Nov 14, 2023

Canyou check whether this is still relevant on dev? Pretty sure a bunch of stuff was fixed around this

I also wrote in the description of the issue that I check it on dev.

@bounlu
Copy link
Contributor

bounlu commented Aug 14, 2024

I confirm that this issue still persists in version 3.4.3.

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