Approximate CLOVER behavior with fuel recipes corresponding to single assemblies

[nsryan2]

Users might be able to achieve the behavior we are envisioning for CLOVER by using a different recipe for each fuel assembly in the Cycamore Reactor. We need to demonstrate the value of any features of CLOVER over this method. You wouldn't even need to have a unique recipe for each assembly, you could simply give the commodity different names and the same recipe. This would match the type of lowest fidelity case outlined in #11.

This issue can be closed with a PR that creates a simple example of one of the baseline cases that uses recipes in the way described above.

[nsryan2]

Reactor currently does batch recipes, you can expand this to take multiple recipes per batch in the hacky way above.

[nsryan2]

By making one batch = one assembly, we can use EVER or Cycamore's reactor with preferences

Someone could always make recipes that incorporate generic movements ahead of time to get some sort of average composition of the fuel (especially where we have 3 assemblies, which is a huge simplification anyways).

• Reactor runs from 10-730 (720 time steps)
• Every 18 steps after step 10, we get 1 new assembly
  • Refuel for 1 time step
• There’s 3 total in core at once and 1 gets replaced in the refuel

Number of new "central" assemblies	1	1	0	0	1	0	0	1	0	0
Associated time step	9	29	49	69	89	109	129	149	169	189