-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fuel Recipe Problem for Transition Scenarios #45
Comments
We will need to run an enormous number of simulations to generate necessary
data to inform demand driven deployment models. The recipe reactor saves
time per simulation over bright lite. For computing time reasons,
therefore, I would not put these solutions in the same order. Good : fix
existing, Better: use Bright-lite or CyBORG, Best: Produce your own recipes.
Have you (@jbae11) been able to communicate with louis kissinger about his
serpent model ? Ideally it and variations of it can be used to generate the
recipes needed for the SFR type reactors at least.
…On Sun, Jul 2, 2017 at 6:52 PM, Jin Whan Bae ***@***.***> wrote:
Problem:
The deployment schedule of transition scenarios are currently heavily
dependent
on the output recipe of Cycamore::Reactor. (How many LWRs are needed to
start FRs, etc.)
A model fuel recipe for the transition scenarios are needed:
Scenarios Type of Reactor (Conversion Ratio) Type of Input Fuel
eg23 Breeder (~1.2) Pu + dep.U
eg24 Breeder (~1.2) TRU + dep.U
eg29 Burner (~0.8) Pu + dep.U
eg30 Burner (~0.8) TRU + dep.U
The input fuel and output fuel recipes have to be semi-compatible with the
mixer facility.
i.e.)
The reprocessed Pu or TRU from spent fuel, and its mixture with dep U
should
resemble the input fuel recipe closely. In short:
(Reprocessed Pu or TRU recipe)(ratio) + (dep U)(1-ratio) ~= input recipe
Solution:
Various solutions are available, some better than others
Weak:
use vision recipe and modify to fit need
Better:
Produce own recipe using depletion codes
Best:
Use Bright-lite, which would be better in the longer run to
demonstrate cyclus capabilities.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#45>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AAYCq0My3BCaL3AY3m5-1Kx6U4iDwdBpks5sKC0-gaJpZM4OLugd>
.
--
Kathryn Huff
Assistant Professor
Nuclear, Plasma, and Radiological Engineering
University of Illinois at Urbana-Champaign
kdhuff.web.engr.illinois.edu
|
That makes sense. I will look into producing my own recipes. Do you have Louis' contact information? I can't find him on slack or github. I guess I can work with him to find a recipe. |
Please don't repeat work that is part of louis' summer proposal. @lkissin2 on github |
Okay thanks! I'll talk to him about it |
may offer a crude solution. |
According to Appendix B, the spent fuel compositions are grouped into four categories, and the Breeding ratio of Fast reactors in each scenario can be estimated.
The Breeding ratios are quite low to accumulate Pu or TRU to start up new reactors,
|
A Weak Solution is offered in this repository. This issue will be closed, but two new issues #50 #49 address the better and best solutions. |
Coordinate merge(pris, webscrape)
Problem:
The deployment schedule of transition scenarios are currently heavily dependent
on the output recipe of
Cycamore::Reactor
. (How many LWRs are needed to start FRs, etc.)A model fuel recipe for the transition scenarios are needed:
Note the only difference between 23/24 and 29/30 is the MOX PWR.
The input fuel and output fuel recipes have to be semi-compatible with the mixer facility.
i.e.)
The reprocessed Pu or TRU from spent fuel, and its mixture with dep U should
resemble the input fuel recipe closely. In short:
(Reprocessed Pu or TRU recipe)(ratio) + (dep U)(1-ratio) ~= input recipe
Solution:
Various solutions are available, some better than others
Weak:
use vision recipe and modify to fit need
Better:
Produce own recipe using depletion codes
Best:
Use Bright-lite, which would be better in the longer run to
demonstrate cyclus capabilities.
The text was updated successfully, but these errors were encountered: