Saheed Adeyanju
08/31/2024, 5:44 AM.nextflow.log file
Aug-31 063809.646 [Actor Thread 189] ERROR nextflow.extension.OperatorImpl - @unknown
nextflow.exception.WorkflowScriptErrorException: The sample-sheet only contains normal-samples, but the following tools, which were requested with "--tools", expect at least one tumor-sample : mutect2
Aug-31 063809.678 [main] ERROR nextflow.cli.Launcher - @unknown
nextflow.exception.WorkflowScriptErrorException: This path is not available within annotation-cache.
Please check https://annotation-cache.github.io/ to create a request for it.
I've verified that my explicit_sample.csv file contains both normal (status 0) and tumor (status 1) samples.
I've checked for and removed any trailing spaces in the CSV file.
The pipeline works when I use a simplified sample sheet with just one pair of normal and tumor samples.
I'm unsure why the pipeline is not recognizing the tumor samples in my full sample sheet.
The annotation-cache error seems to be related to the VEP cache, but I'm not sure how to resolve this.
Any assistance in resolving these issues would be greatly appreciated. Thank you!Thomas Danhorn
08/31/2024, 11:57 PM--genome, which is supposed to pull in the iGenomes reference files (which work well for sarek; I would not suggest deviating much from those unless you really know what you are doing), but then you are using a whole bunch of parameters to override what is in the igenomes.config of the pipeline. This does not make sense.
⦠You are setting --igenomes_base to the default (S3 bucket), but then you are overriding that pretty much every single file with a local path (/home/drseed/BAM2/folder/...). If you have you downloaded the iGenomes reference files (at least for GATK.GRCh38) and preserved the direcotory structure, you can jut set --igenomes_base to that location (the parent directory of Homo_sapiens/ ) and remove all other parameters pointing to individuals file (1000-genomes, dbSNP, germline resource, etc.).
⦠BTW, some you these individual file parameters were specified twice, in the config file and the command line. Note that because of the way the config file is read, parameters there are often overwritten later, so you should not have params{} in a config file used with -c (although that would be fine in a profile). Instead, you can use the parameters on the command line or put them in a JSON or YAML file and use that with -params-file.
⢠In your command line, you have --vep_cache twice, and only the second time with a directory as argument. If that directory contains the downloaded VEP cache, then just removing the extraneous --vep_cache should be enough.
š¤
Pro tip: Typing ````` will open a window to paste your code or error messages, which separates them from the rest of the text and makes them more readable.Saheed Adeyanju
09/01/2024, 12:44 PM