This is a good idea, but why not let the graph be dumped at any point along the way?  It can be a regular pipeline pattern, just like STATS or DUMP_FASTA. STATS currently dumps to HDFS but there's no reason it shouldn't have local output, IMHO.  I think DUMP_FASTA does local output to something like genome.fasta.

What if our "-localOutput" folder contained several items instead of just the last steps contents? By default, there is no localOutput, but let's pretend it was `genomix-results`.  What I'm envisioning is something like: `-pipelineOrder BUILD,STATS,MERGE,STATS,BUBBLE,STATS,SHOW_GRAPH,DUMP_FASTA` leading to _local_ output like:
```
genomix-results/
|-- 01-BUILD-STATS
|   |-- coverage-hist.png
|   |-- kmerLength-hist.png
|   `-- stats.txt
|-- 02-MERGE-STATS
|   |-- coverage-hist.png
|   |-- kmerLength-hist.png
|   `-- stats.txt
|-- 03-BUBBLE-DUMP_FASTA
|   `-- genome.fasta
|-- 03-BUBBLE-SHOW_GRAPH
|   |-- graph.dot
|   `-- graph.svg
`-- 03-BUBBLE-STATS
    |-- coverage-hist.png
    |-- kmerLength-hist.png
    `-- stats.txt
```