Screening the design space for optimized plutonium incineration performance in the thorium-based I2S-LWR

D. Kotlyar, G. T. Parks, E. Shwageraus

Research output: Contribution to journalArticlepeer-review

Abstract

This paper presents an optimization of a thorium-plutonium (Th-Pu) fuel cycle by screening various design options for the Integral Inherently Safe Light Water Reactor (I2S-LWR). The I2S-LWR is an advanced 2850 MWt integral pressurized water reactor with enhanced safety beyond that of Gen-III+ reactors. The features of this reactor, such as material choice, make it attractive for alternative fuel cycles including the use of thorium. Recently, the feasibility of the Th-Pu cycle was studied and the benefits associated with it were demonstrated. More specifically, the Pu incineration performance was enhanced by adopting multi-batch (i.e. more than 3-batch) schemes and extended burnup (above 100 MWd/kg). The optimized design with the most favorable loading pattern was obtained by applying the Simulated Annealing optimization technique. This paper demonstrates further plausible modifications to the Th-Pu cycle design that may enhance its performance considerably. The paper seeks to identify the contributory factors, such as cladding types, plutonium vectors and initial plutonium loadings, with major impact on the incineration performance. The post-irradiation characteristics are also analyzed and suggest that such a cycle may simplify the design and operation of the waste repository.

Original languageEnglish
Pages (from-to)237-249
Number of pages13
JournalAnnals of Nuclear Energy
Volume101
DOIs
StatePublished - 1 Mar 2017
Externally publishedYes

Keywords

  • BGCore
  • IS-LWR
  • PANTHER
  • Plutonium incineration
  • Simulated Annealing
  • Thorium cycles
  • WIMS

ASJC Scopus subject areas

  • Nuclear Energy and Engineering

Fingerprint

Dive into the research topics of 'Screening the design space for optimized plutonium incineration performance in the thorium-based I2S-LWR'. Together they form a unique fingerprint.

Cite this