As discussed in nextflow/README.md, the lack of a dry-run feature in nextflow is a problem for riboviz and slows down many users as it makes testing harder.
How much time and difficulty would it take for us to help create that capability in nextflow? Is it worth our time? The payoff is that the feature would both help riboviz, and have impact beyond our project, as described in the pathways to impact statement for our grant.
The nextflow contributor guide suggests that this could be a slow process that starts with discussions on nextflow's issue tickets.
As discussed in nextflow/README.md, the lack of a dry-run feature in nextflow is a problem for riboviz and slows down many users as it makes testing harder.
How much time and difficulty would it take for us to help create that capability in nextflow? Is it worth our time? The payoff is that the feature would both help riboviz, and have impact beyond our project, as described in the pathways to impact statement for our grant.
The nextflow contributor guide suggests that this could be a slow process that starts with discussions on nextflow's issue tickets.