An approach to verification and validation of MHD codes for fusion applications

S. Smolentsev, S. Badia, R. Bhattacharyay, L. Bühler, L. Chen, Q. Huang, H. G. Jin, D. Krasnov, D. W. Lee, E. Mas De Les Valls, C. Mistrangelo, R. Munipalli, M. J. Ni, D. Pashkevich, A. Patel, G. Pulugundla, P. Satyamurthy, A. Snegirev, V. Sviridov, P. SwainT. Zhou, O. Zikanov

Research output: Contribution to journalArticleResearchpeer-review

59 Citations (Scopus)

Abstract

We propose a new activity on verification and validation (V&V) of MHD codes presently employed by the fusion community as a predictive capability tool for liquid metal cooling applications, such as liquid metal blankets. The important steps in the development of MHD codes starting from the 1970s are outlined first and then basic MHD codes, which are currently in use by designers of liquid breeder blankets, are reviewed. A benchmark database of five problems has been proposed to cover a wide range of MHD flows from laminar fully developed to turbulent flows, which are of interest for fusion applications: (A) 2D fully developed laminar steady MHD flow, (B) 3D laminar, steady developing MHD flow in a non-uniform magnetic field, (C) quasi-two-dimensional MHD turbulent flow, (D) 3D turbulent MHD flow, and (E) MHD flow with heat transfer (buoyant convection). Finally, we introduce important details of the proposed activities, such as basic V&V rules and schedule. The main goal of the present paper is to help in establishing an efficient V&V framework and to initiate benchmarking among interested parties. The comparison results computed by the codes against analytical solutions and trusted experimental and numerical data as well as code-to-code comparisons will be presented and analyzed in companion paper/papers.

Original languageEnglish
Pages (from-to)65-72
Number of pages8
JournalFusion Engineering and Design
Volume100
DOIs
Publication statusPublished - 1 Nov 2015
Externally publishedYes

Keywords

  • Blanket
  • Computer code
  • Liquid metal magnetohydrodynamics

Cite this