Skip to content
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

Closed
jbae11 opened this issue Jul 2, 2017 · 7 comments
Closed

Fuel Recipe Problem for Transition Scenarios #45

jbae11 opened this issue Jul 2, 2017 · 7 comments

Comments

@jbae11
Copy link
Collaborator

jbae11 commented Jul 2, 2017

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) Burnup (Driver, Blanket, PWR) Type of Input Fuel
eg23 Breeder (slightly over 1.0) 81.5 GWd/t, 23.5 GWd/t, (avg. 72.6 GWd/t) Pu + rep.U
eg24 Breeder (slightly over 1.0) 73 GWD/t (no blanket) TRU + rep. U
eg29 Breeder (~1.2), MOX PWR 97GWd/t, 21GWd/t, 50GWd/t nat U, rep U, Pu // Pu + rep. U
eg30 Breeder (~1.2), MOX PWR 107 GWd/t, 23GWd/t, 50GWd/t nat U, rep U, TRU // Pu + rep U

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.

@katyhuff
Copy link
Member

katyhuff commented Jul 4, 2017 via email

@jbae11
Copy link
Collaborator Author

jbae11 commented Jul 4, 2017

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.

@katyhuff
Copy link
Member

katyhuff commented Jul 4, 2017

Please don't repeat work that is part of louis' summer proposal.

@lkissin2 on github
@lkissin2 on slack
[email protected] via email

@jbae11
Copy link
Collaborator Author

jbae11 commented Jul 4, 2017

Okay thanks! I'll talk to him about it

@jbae11
Copy link
Collaborator Author

jbae11 commented Aug 4, 2017

this PR

may offer a crude solution.

@jbae11
Copy link
Collaborator Author

jbae11 commented Aug 9, 2017

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 BR of SFRs are calculated by

BR = (UNF_'fissile'_composition) * (reprocessing_efficiency) /  (SFR_Fuel_Composition)
  • EG23: 13.101*.998/12.9 = 1.0136
  • EG24: 13.95*.998/13.78 = 1.0103
  • EG29: 9.114*.998 / 7.05 = 1.29
  • EG30: 12.3206*.998/11.655 = 1.055

The Breeding ratios are quite low to accumulate Pu or TRU to start up new reactors,
which prolongs the LWR-only period so that enough Pu inventories can be accumulated.
In the Orion analysis,
two things are done differently:

  1. ORION does not decommission reactors mid-cycle, and waits until all cycles are finished, and the decommissioned reactor has a fully transmuted core (while CYCAMORE::REACTOR only transmutes half of core when decommissioned mid-cycle -> EDITED: This is needs to be checked).

  2. In the power-increase scenario (1% annual energy demand increase case), the BR of the SFR is set to 1.2, which is higher than what is given in the E&S report Appendix B.

@jbae11
Copy link
Collaborator Author

jbae11 commented Aug 28, 2017

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.

@jbae11 jbae11 closed this as completed Aug 28, 2017
gyutaepark pushed a commit that referenced this issue Apr 24, 2018
Coordinate merge(pris, webscrape)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment