Tim O'Donnell

Potentially could use something like vagrant? https://coreos.com/kubernetes/docs/latest/kubernetes-on-vagrant.html Help wanted

There are pretty much no docstrings currently

Currently if the user reruns a computation using the same cache-key, we assume without any checks that the i'th task is computing the same piece of input in the current...

Instead of just dumping out tons of logs, it would be nice if every minute or so on stdout we'd get a status summary similar to what's in the html...

Currently our notions of the state a task can be are: - completed (detected by presence of the result file in the bucket) - submitted (we submitted this task but...

Currently we just fork off `kubectl` commands. May want to switch to something like [pykube]( https://pypi.python.org/pypi/pykube/), [kube](https://pypi.python.org/pypi/kube), or [kubernetes-py](https://pypi.python.org/pypi/kubernetes-py)

We currently detect what tasks have completed by issuing a bucket list request with the prefix set to the common prefix of the result names for all running tasks. This...

Simultaneously examine multiple runs

7

Interested if people thinks this makes sense, and how much work it would entail. For the pt189 analysis, I'd like to view pileups for an arbitrary set of BAMs (normal...

Kind of a random idea. Interested if people think it'd make any sense. Possibly this should be filed against pileupjs. IPython + matplotlib etc. is a pretty reasonable place to...

We are hitting situations where we have multiple BAMs for an individual (say 5 - 20), and are interested in looking at a summary of the read evidence at particular...