Skip to content

File name collision when including single stranded and double stranded of same sample #653

@aidaanva

Description

@aidaanva

Check Documentation

I have checked the following places for your error:

Description of the bug

When running single stranded and double stranded libraries of the same sample, it complains about duplicated names after the merging step.

Steps to reproduce

Steps to reproduce the behaviour:

  1. Command line: nextflow run nf-core/eager -profile pathogen_loose,sdag,shh -r 2.2.2 --fasta '/path/to/file.fasta' --input '/path/to/file.tsv ' --outdir '/path/to/directory' -w '/path/to/directory/work' --email 'blabla@blabla.de' -with-tower -name 'Nameofrun' --preserve5p --run_bam_filtering --bam_unmapped_type 'discard' --bam_mapping_quality_threshold 37 --dedupper 'markduplicates'
  2. See error:
    `Error executing process > 'sex_deterrmine (1)'

Caused by:
Process sex_deterrmine input file name collision -- There are multiple input files for each of the following file names: ARS007_libmerged_rg_rmdup.bam

Tip: you can try to figure out what's wrong by changing to the process work dir and showing the script file named .command.sh
`

Expected behaviour

Single and double stranded libraries are named automatically and they do not merge.

Log files

Have you provided the following extra information/files:

  • The command used to run the pipeline
  • The .nextflow.log file
  • The exact error:

System

  • Hardware:
  • Executor:
  • OS:
  • Version

Nextflow Installation

  • Version:

Container engine

  • Engine:
  • version:
  • Image tag:

Additional context

I have spoken to @jfy133 privately

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingminor

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions