issues

# cycamore::reactor should have a fungibility factor
### Current:
`cycamore::reactor` will not accept output from `cycamore::Fuelfab` (mox) because the `cycamore::reactor`  
judges material acceptance depending on recipe, not commodity name. The `cycamore::Fuelfab`  
does not create output according to a recipe, but mixes input fissile material streams to fulfil a certain
neutronics property. eg) [simple_reprocess.xml](https://gist.github.com/3e8e2cb882597c040b93fe66de4261ca.git)

### Suggested Long Term Solution:
Adding a fungibility (error, substitution) factor as an optional configuration in the `cycamore::reactor`
archetype will allow the `cycamore::reactor` to accept mox from fuelfab, and use it,  
if the 'mox' out of the `cycamore::Fuelfab` is remotely close to the mox recipe in the reactor.

This is, of course, in case the user really wants to use `cycamore::Reactor`,  
and not `Bright-Lite` or `Cyborg`.

### Current Workaround:
For a single burnup simulation only (output recipe is the same for all reactors),  
it is possible to use the `cycamore::Mixer` to manually fit the fissile stream
to satisfy the mox recipe. eg) [simple_reprocess_mixer.xml](https://gist.github.com/3e8e2cb882597c040b93fe66de4261ca.git)'


# cycamore::Mixer should request 'streams' proportionately
### Current
The `cycamore::Mixer` archetype does not have a term for how much  



# cycamore::Reactor should have exited reactors in the agentstate_cycamore_reactorinfo table
### Current:
The table `agentstate_cycamore_reactorinfo` does not have  
exitted reactors (reactors exitted in the simulation).
This poses a problem since the `power_cap` column is only accessible  
in the `agentstate_cycamore_reactorinfo` table.
eg) [Europe Case Study](https://github.com/arfc/transition-scenarios/issues/25)

### Demonstration of Problem:
The following query outputs blank, in any simulation with `cycamore::DeployInst`:

~~~~
SELECT power_cap, entertime
FROM agentexit INNER JOIN
agentstate_cycamore_reactorinfo
ON agententry.agnetid = agentstate_cycamore_reactorinfo.agentid
~~~~

I also tried using other tables, but it seems that the 'agentstate_cycamore_reactorinfo`  
is the only table with the column `power_cap`.

With the current issue it is difficult to display the capacity fluctuation  
with time if there are reactor agents with more than one unique capacity.