From aecb2188edabb99581ef283a9fdc80e18f776a0c Mon Sep 17 00:00:00 2001 From: Alexander Peltzer Date: Wed, 17 Apr 2024 10:21:22 +0000 Subject: [PATCH] Fix passing on adapter seq to mirtrace module --- subworkflows/local/mirtrace.nf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/subworkflows/local/mirtrace.nf b/subworkflows/local/mirtrace.nf index 3d2b6002..528e4233 100644 --- a/subworkflows/local/mirtrace.nf +++ b/subworkflows/local/mirtrace.nf @@ -14,7 +14,7 @@ workflow MIRTRACE { //Directly using val(reads) as in previous versions is not reliable as staging between work directories is not 100% reliable if not explicitly defined via nextflow itself //mirtrace is a bit peculiar in parsing these config files, so looked it up in the source how its done. this way should work ch_mirtrace_config = - reads.map { adapter, ids, reads -> [ids,reads]} + reads.map { adapter, ids, reads -> [adapter, ids,reads]} .transpose() .collectFile { adapter, id, path -> "./${path.getFileName().toString()},${id},${adapter},${params.phred_offset}\n" } // operations need a channel, so, should be outside the module