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

DSL1: No fasta indexing when using bowtie2. #1031

Closed
2 of 5 tasks
TCLamnidis opened this issue Nov 1, 2023 · 0 comments · Fixed by #1032
Closed
2 of 5 tasks

DSL1: No fasta indexing when using bowtie2. #1031

TCLamnidis opened this issue Nov 1, 2023 · 0 comments · Fixed by #1032
Labels
bug Something isn't working DSL1

Comments

@TCLamnidis
Copy link
Collaborator

Check Documentation

I have checked the following places for your error:

Description of the bug

When using bowtie2 as the mapper, and not providing a fasta index already, damageprofiler and genotyping is not executed, because the fasta_index is not generated at all.

Steps to reproduce

Steps to reproduce the behaviour:

nextflow run nf-core/eager -r 2.4.7 -profile test,docker --mapper 'bowtie2' --run_genotyping --genotyping_tool 'ug'

No process for damageprofiler or genotyping_ug is submitted.

Expected behaviour

Process for damageprofiler or genotyping_ug is submitted.

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

@TCLamnidis TCLamnidis added bug Something isn't working DSL1 labels Nov 1, 2023
@TCLamnidis TCLamnidis mentioned this issue Nov 1, 2023
11 tasks
@TCLamnidis TCLamnidis linked a pull request Nov 3, 2023 that will close this issue
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working DSL1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant