Looking for anyone's input here. I am trying to en...
# random
e
Looking for anyone's input here. I am trying to encapsulate what are the most reduced key-elements of "good" Nexflow pipelines. Please share your suggestions • Containerized, modular processes • De-coupled, well-tuned, and flexible configuration • Optimized Dataflow Programming (channel I/O, etc.) • Robust built-in linting/testing • Clear, up-to-date syntax and pipeline directory hierarchy (nf-core tools compatible, ideally)
I want to emphasize here that I'm saying Nextflow pipeline and not nf-core pipeline..
t
I might add a certain error tolerance, e.g. through automatic retries. (You could argue that's part of the configuration, but either way, it should be there, because the main reason we are using pipelines it to manage complexity, and once something is complex, it has many moving pieces, each of which can break. Good pipelines anticipate that.)
✅ 1