Diego Alvarez Saravia
12/11/2024, 5:08 PMinput:
tuple val(meta), path(fasta, stageAs:'tmp_input/*')
val mode // Required: One of genome, proteins, or transcriptome
val lineage // Required: lineage to check against, "auto" enables --auto-lineage instead
path busco_lineages_path // Recommended: path to busco lineages - downloads if not set
path config_file // Optional: busco configuration file
And the current meta:
input:
- - meta:
type: map
description: |
Groovy Map containing sample information
e.g. [ id:'test', single_end:false ]
- fasta:
type: file
description: Nucleic or amino acid sequence file in FASTA format.
pattern: "*.{fasta,fna,fa,fasta.gz,fna.gz,fa.gz}"
- - mode:
type: string
description: The mode to run Busco in. One of genome, proteins, or transcriptome
pattern: "{genome,proteins,transcriptome}"
- - lineage:
type: string
description: The BUSCO lineage to use, or "auto" to automatically select lineage
- - busco_lineages_path:
type: directory
description: Path to local BUSCO lineages directory.
- - config_file:
type: file
description: Path to BUSCO config file.
Why does this to new field need to be added to the input? What information should this field contain?James Fellows Yates
12/11/2024, 8:01 PMnf-core modules lint --fix
For some reason the linting fixer was picking up the third word in a comment and thought it was an input... 😅
See line 14 of the <http://main.nf|main.nf> here: https://github.com/nf-core/modules/pull/7199/commits/f3184f4da5b6f69d4fc8bc4a1e9a45329f857b3b
I think it's because the fixer looks for any form of string called path and will take the word after it as an input, regardless if it's in a comment or not. By removing the word 'path' it then starting working.James Fellows Yates
12/11/2024, 8:03 PM