nf-core / nf-core/variantprioritization

Space in manta vcf header causes bcftools norm error

Open
#95 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Nextflow
Stars
16
Forks
11
PR merge metrics
No merged PRs in 30d

Description

Description of the bug

I now realise that this pipeline does not support manta output created by sarek, but I post this here for future releases.

This is a filename parsing / channel naming issue in the pipeline rather than a bcftools problem itself.

The process is generating this output filename:

--output HD827.HD827-manta.generatesvcandidates 1.6.0.norm.vcf.gz

Notice the space:

HD827.HD827-manta.generatesvcandidates 1.6.0.norm.vcf.gz
                                      ^

Because of that, bcftools interprets:

HD827.HD827-manta.generatesvcandidates as the output file
1.6.0.norm.vcf.gz as an input argument

So it tries to open:
1.6.0.norm.vcf.gz

Which does not exist, causing:
Failed to open file "1.6.0.norm.vcf.gz"

However, the 1.6.1 comes from the manta vcf header. It is not found in my samplesheet anywhere.

Command used and terminal output
`nextflow run nf-core/variantprioritization -r 1.0.0 -resume -profile singularity -params-file params.yaml`


` Pipeline completed with errors- ERROR ~ Error executing process > 'NFCORE_VARIANTPRIORITIZATION:VARIANTPRIORITIZATION:INPUT_PREPROCESSING:BCFTOOLS_NORM (HD827.HD827-manta.generatesvcandidates 1.6.0)' Caused by: Process NFCORE_VARIANTPRIORITIZATION:VARIANTPRIORITIZATION:INPUT_PREPROCESSING:BCFTOOLS_NORM (HD827.HD827-manta.generatesvcandidates 1.6.0) terminated with an error exit status (255) Command executed: bcftools norm \ --fasta-ref Homo_sapiens_assembly38.fasta \ --output HD827.HD827-manta.generatesvcandidates 1.6.0.norm.vcf.gz \ -m -both -cw -Oz --write-index=tbi \ --threads 6 \ HD827.manta.diploid_sv.vcf.gz Command exit status: 255 Command output: (empty) Command error: [E::hts_open_format] Failed to open file "1.6.0.norm.vcf.gz" : No such file or directory Failed to read from 1.6.0.norm.vcf.gz: No such file or directory`
Relevant files

.nextflow.log.3.txt

System information

Nextflow 25.10.4
Local executor on a workstation.
Singularity
Ubuntu
ver 1.0.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with .nextflow.log.3.txt and the NFCORE_VARIANTPRIORITIZATION:VARIANTPRIORITIZATION:INPUT_PREPROCESSING:BCFTOOLS_NORM process shown in the report. Reproduce the reported command and trace how the output filename is formed. Done means the generated filename is passed as one argument without a space and bcftools norm completes successfully.

Written by the indexing model from the issue text.

Assessment

Domain
bioinformatics
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.