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
Ok, indeed my suspicion was correct but goes deeper than I thought: nf-core/tools#823
I will need to manually go through and fix our parameter schema (not hard, but will take a bit of time). Will do this in the patch release with the readgroup issue in #655
Check Documentation
I have checked the following places for your error:
- nf-core/eager FAQ/troubleshooting can be found here
Description of the bug
Using
"bt2n": "1"
in the.json
file doesn't work properly and produces an error message that the parameter is invalid.Steps to reproduce
Steps to reproduce the behaviour:
nextflow run nf-core/eager -r 2.2.2 -params-file run.json -c awoonga.config
run.json
includes the following:error: invalid bowtie2 --bt2n (-N) parameter. Options: 0, 1. Found parameter: --bt2n 1.
Expected behaviour
The workflow should run and supply the
-N 1
parameter tobowtie2
(it works as intended when provided in the CLI with--bt2n 1
)Log files
Have you provided the following extra information/files:
.nextflow.log
file (see at bottom)error: invalid bowtie2 --bt2n (-N) parameter. Options: 0, 1. Found parameter: --bt2n 1.
System
Nextflow Installation
Container engine
Additional context
.nextflow.log
:The text was updated successfully, but these errors were encountered: