Slackbot
04/19/2024, 4:49 AMPhil Ewels
04/19/2024, 6:32 AMPhil Ewels
04/19/2024, 6:32 AMStephen Kelly
04/19/2024, 12:48 PMeval output type
however it seems to leave a void in deciding how that same data should now be formatted
its on my To-Do list for that repo to also implement a method that can handle a plain Map interface, or maybe I could even expose the ProcessVersion class interface directly https://github.com/stevekm/nf-niceutils/blob/ca7fe6470123f5b46854f12ec55e001ae8c2d[ā¦]0cb/src/main/groovy/com/nextflow/plugin/ExampleFunctions.groovy , so that users might be able to immediately bind their versions into a coherent object format inside their pipeline, which could then also be serialized for external use e.g. with MultiQCsteve
04/19/2024, 1:24 PMprocess FASTQ {
container "docker/fastqc-1.2"
input:
path(files)
output:
path(report)
version:
val("FastQC"), eval('fastqc --version | sed -e \'s/FastQC v//g\'')
script:
"""
multiqc ...
"""
}
workflow QC_WORKFLOW{
take:
files_ch
main:
FASTQ(files_ch)
}
workflow {
QC_WORKFLOW(files_ch)
QC_WORKFLOW.version.view()
// [ ["software": "FastQC",
// "version": "1.2",
// "container": "docker/fastqc-1.2"
// "process":"FASTQC",
// "id": "QC_WORKFLOW:FASTQC"] ]
}
This would make it easier for both MultiQC, and other methods, to access the versionsPhil Ewels
04/19/2024, 2:15 PMPhil Ewels
04/19/2024, 2:16 PMPhil Ewels
04/19/2024, 6:29 PMeval directive. I thought that they had! But thought that I was going crazy as I couldn't remember what we called it and couldn't see it referenced there š
Phil Ewels
04/19/2024, 9:45 PMPhil Ewels
04/19/2024, 9:46 PMsteve
04/19/2024, 10:31 PMPhil Ewels
04/19/2024, 10:39 PMeval should be implemented but I don't think that there's been a serious effort to figure out how to update modules and the template yet.Ben Sherman
04/20/2024, 2:46 AM