Checkpoints
Opened this issue · 1 comments
standage commented
We discussed including "checkpoints" at each step to help orient the user. What kind of checkpoints do we want?
- software installation tests? (e.g.
which fastqc
) - path checks? (e.g.
ls $DATADIR/
) - file checks? (e.g.
ls -lh reads.fq; wc -l reads.fq
) - environment checks? (e.g.
hostname; whoami
) - any others?
ctb commented
On Fri, Dec 16, 2016 at 11:42:00AM -0800, Daniel Standage wrote:
We discussed including "checkpoints" at each step to help orient the user. What kind of checkpoints do we want?
- software installation tests? (e.g. `which fastqc`)
- path checks? (e.g. `ls $DATADIR/`)
- file checks? (e.g. `ls -lh reads.fq; wc -l reads.fq`)
- environment checks? (e.g. `hostname; whoami`)
- any others?
A few thoughts --
* short and sweet at the beginning and end
* maybe hide the rest in foldouts? I'd rather they not be too intrusive