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
Using haplotypecaller without passing a --dbsnp, the following error is raised:
ERROR ~ Cannot get property 'baseName' on null object
-- Check script '/scratch/mblab/chasem/nextflow/assets/nf-core/sarek/./workflows/sarek/../../subworkflows/local/bam_variant_calling_germline_all/main.nf' at line: 132 or see '.nextflow.log' file for more details
ERROR ~ Cannot get property 'baseName' on null object
-- Check script '/scratch/mblab/chasem/nextflow/assets/nf-core/sarek/./workflows/sarek/../../subworkflows/local/bam_variant_calling_germline_all/main.nf' at line: 133 or see '.nextflow.log' file for more details
-[nf-core/sarek] Pipeline completed with errors-
you have to edit the code on your local version for the moment until it gets corrected and released, but the correction i described in the original post works. Depending on what options you have set, there are a couple other spots that the same correction needs to be made.
Description of the bug
Using haplotypecaller without passing a
--dbsnp
, the following error is raised:If I replace this line:
sarek/subworkflows/local/bam_variant_calling_germline_all/main.nf
Line 133 in b5b766d
with
the subworkflow completes without error.
Sorry for the lack of a reproducible example for the time being -- will try to make one early next week.
Command used and terminal output
nextflow run nf-core/sarek -profile singularity -params-file bam_input_params.json -c /scratch/mblab/chasem/bsa/wustl_htcf.config -c kn99.config --input samplesheets/run_6991.csv --outdir run_6991_results
Relevant files
I tried this with
haplotypecaller_filter
in "skip_tools", also, with the same result.System information
Nextflow: 24.04.2
Hardware: HPC
Executor: SLURM
Container engine: Singularityce
OS: Rocky linux v8.9
nf-core/sarek: 3.4.2
The text was updated successfully, but these errors were encountered: