Tiago Jesus
Tiago Jesus
Current implementation on task definition by the user is somehow javascript dependent. Example: ```javascript const gunzipIt = task({ input: '*_genomic.fna.gz', output: '*.fa', params: { output: 'uncompressed.fa' } }, ({ params,...
Tasks could be npm modules and then one could import them as such: ```javascript const { join } = require('bionode-watermill') const samtools = require('watermill-samtools') const pipeline = join(stuff, stuff2, samtools)...
Currently bionode-watermill has a visualization tool available when running your scripts in `localhost:8084`. This visualization tool is basically a d3 force-directed graph that enables to draw vertices and edges from...
Right now bionode-watermill resolves a set of promises, ```javascript const pipeline = join(task1, task2) ``` but it would be nice to have a object-like structure in pipeline definition ```javascript const...
What do you think if we create a simple usage tutorial for some of the basic usages of tasks and orchestrators to README? We already have 4 examples but I...
Right now a task can only resolve if one input (with the same pattern, e.g. `*.txt`) is given, if pattern within `input` renders more than one possible hit task will...
Resulting from a discussion with @thejmazz in gitter, it would be great to have support for cluster computing (such as qsub and slurm (srun and so on...)) as a plugin....