= GUARDYAN Basic Features == Aims GUARDYAN simulates the time evolution of fission chains. The neutrons are followed from the beginning to the end of a time interval. This tracking philosophy differs from the usual source convergence calculations where neutrons are followed from generation to generation, i.e. from fission event until the next fission event. The source term for GUARDYAN is a "snapshot" of the neutron population at a time instance consisting of delayed neutron precursors waiting to "hatch" and prompt neutrons crossing the time boundary. The time dependent changes in the neutron population may originate from time dependent changes of the cross sections either as change of a material or of the temperature of a certain material. The current version of GUARDYAN is not capable of simulating thermal or any other feedback this feature is planned for future releases. == Software and Hardware Environment A code written in CUDA/C++ is basically separated responsible for reading cross section data from the input, the second for host side tasks, the third part is the GPU kernel which runs the simulation. Currently the host side code consists of cca. 65000 lines and the device side code consists of cca. 5000 lines. Dependencies: CUDA: 8.0, NVIDIA driver: 375.66, GCC: 5.4.0, Qt: 5.5.1 Hardware: 2 x Geforce GTX 690, 4 x Geforce GTX 1080 == Features === Geometry descriptors In order to run simulations on a real reactor geometry we need to create the tools for defining geometry. Similarly to other particle transport codes (Serpent, MCNP, OpenMC) in GUARDYAN geomety is defined by cells containing isotopes. Cells are defined by bounding surfaces. These data can be given in ''xml'' files. ==== Surfaces In the current version general positioned sphere, plane and infinite cylinder are supported in special cases according to Table 1. More surface types are added in later releases. [[Image(table1.png, 80%)]] ==== Cells Cells may be defined as an intersection or union of spaces divided by surfaces. Cells may be filled into either rectangular or hexagonal lattices. [[Image(VVER440_v1.png, 30%)]] ''' Fig. 1. Fuel rods in a hexagonal lattice''' === Isotopes and Cross Sections Cells are considered homogeneous and filled with a single material defined by the isotopes, their relative abundance and material density. Cross sections are read from ACE format files. [[Image(XS.png, 50%)]] ''' Fig. 2. Cross section of U-235 as read by GUARDYAN''' In current implementation GUARDYAN stores the energy partitioning structure separately for every isotope. To find the cross section of a neutron with given energy GUARDYAN useS binary search and linear interpolation. GUARDYAN createS materials from isotopes using the fraction of the constituent in the material and the material density. Before the simulation GUARDYAN generates the total macroscopic cross sections and the majorant cross sections for the Woodcock method for every material. ==== Memory Use of Cross Section Data Considering the most important isotopes in a e.g. VVER-440 reactor with fresh fuel: 1H, 2H, 4He,10B, 11B 16O, 17O, 90Zr, 91Zr, 92Zr, 94Zr, 96Zr, 93Nb, 152Gd, 154Gd, 155Gd, 156Gd, 157Gd, 158Gd, 160Gd,174 Hf, 176Hf, 177Hf, 178Hf, 179Hf, 180Hf,235 U, 238U, with 8 different materials definedto store the cross section data for a given temperature 102,4 MB memory is needed on the GPU. For a realistic VVER-440 power plant with full detailed modelling the cross section date reaches 5Gb in memory need. The videocards available contain 2 (GTX 690) or 8 (GTX 1080) GB memory each for realistic simulations therefore modern videocards offer enough physical memory. == Variance Reduction == Dynamic Capabilities == Validation == Project Participants & Contacts == Funding