POC: topics #9159
POC: topics #9159
Conversation
|
So this one replaces #8978 ? |
|
Not yet, I still need to update the subworkflows here |
| output: | ||
| tuple val(meta), path("bwamem2"), emit: index | ||
| path "versions.yml" , emit: versions | ||
| tuple val("${task.process}"), val('bwa-mem2'), eval("bwa-mem2 version 2>&1 | tail -1"), topic: versions, emit: versions1 |
There was a problem hiding this comment.
Just to be picky here, but the harshil alignment is not correct 😂
| - - process: | ||
| type: string | ||
| description: The process the versions were collected from | ||
| - tool: | ||
| type: string | ||
| description: The tool name | ||
| - version: | ||
| type: string | ||
| description: The version of the tool |
There was a problem hiding this comment.
this looks good!
but if we want to automate it somehow, the values of the topic channel should be the same that we add for versions1: ${task.process}, bwa-mem2 and bwa-mem2 version 2>&1 | tail -1.
It doesn't look as nice, but it's the only way we can automate the generation of the meta.yml
There was a problem hiding this comment.
Thanks the main issue here is that the versions topic can consist of multiple tools here. I'm also not sure this needs automation as this will be in the template anyways. I've tried adding the automation, but it's not that trivial to do :/
3 participants
This PR serves as an example of the work being done in nf-core/tools#3779