Add a basic server that can accept uploaded datasets and settings objects and provide API calls to retrieve both to plug into the renderer.

One row per comparison (instead of one row per unique ID) is being drawn as shown below

Currently the plots are handled collectively and (one way or another) all plotting methods run in a loop on a d3 selection of multiple svgs. (chart.plots.svgs.each(function(d, i) {...}) This is a bit of a mess for more complex interactions, like the one we need to implement for brushing in #30 .

Goal is to Refactor to treat each plot as a unique object with it's own methods, then each chart can easily have it's own components (like brushes) and can be called directly on the chart (multiple.brush.init()).

Refactor search functionality from v0.1 for use in v0.2.

Text search filters the plots.

Refactor for https://github.com/RhoInc/Volcano/blob/master/client/src/volcano.v0.1.js#L871-L987

Seems most volcano plots employ a negative log10 p-value scale on the y-axis which effectively creates the "v-shaped" volcano plot that is standard.

Add an option to invert the y-axis here.

Brushing a large number of points is slow in the current implementation. Almost certainly because we're running this chunk on every panel.

d.values.forEach(function(e){
    e.overlay = currentIDs.indexOf(e[settings.vars.id])>-1
})

Consider the best way to refactor the process.

Options (var names, etc) are currently hard-coded in src/volcano/table/init.js

Create a JSON Schema to fit the settings object needed by the renderer.
Use that schema server-side to validate uploaded settings objects.

Add Table View from v0.1 to v0.2.

When a user brushes the charts, a table listing of selected points should be shown.

Refactor this code from the pilot

Implement Quad overlay from v0.1 in v0.2

See https://github.com/RhoInc/Volcano/blob/master/client/src/volcano.v0.1.js#L467

Allow users to filter the points shown in the plots using the buttons at the top of the page.

The pilot code for building the phylum filters is here, but we'll probably want to have a design discussion about the best way to create new filters. The paradigm used for webcharts controls might be useful

Refactor detail view from v0.1 to use in v0.2.

Allow a user to highlight a single point be either:
a) using mouseover on the plot or
b) clicking a row on the table

Show details for a highlighted point in a separate panel.

Refactor the Details function triggered by mouseover on a point or the overview table

The setting is currently ignored