Julian Mazzitelli

[4W27](http://www.rcsb.org/pdb/explore/explore.do?structureId=4WZ7)

I think for now a branch is good. could give the branch a new remote and push it there eventually. branch good because then its easier to share common features

Also relevant for procedural mitochondrion mesh generation, https://github.com/biorender/biorender/issues/4

Why ``` '`gunzip -c ${input} > ${params.output}`' ``` instead of ``` `gunzip -c ${input} > ${params.output}` ``` ? Except then `input` and `params` will be undefined: I think we will...

this is related to #75

Blocked by #75. First step will be modules within this repo. Also - we should probably spec out all the responsibilities of a task module by the time we make...

Userland implementation from [9a2e750](https://github.com/bionode/bionode-watermill/commit/9a2e750b0b4675203f17f3ef8fb1e04c5c1be413) for quick reference: ```javascript const script = ({ dir, program }) => (strings, ...values) => { let content = '' strings.forEach((str, i) => { content +=...

Yes, this is definitely an important task if we wish to attract newcomers more easily. I think a thorough walkthrough might include: - go through a short pipeline by hand...

Two points: 1. We will need to be very precise about use of objects and arrays, your example could easily be: ```javascript const pipeline = { join: [ task1, task2...

Also in that case, doing ```javascript const watermill = require('bionode-watermill') const { task } = watermill({ /* options */ }) const { join } = watermill({ /* options */ })...