1. Filling up FENDL with an all-in-one nuclear data evaluation and validation system around TALYS Arjan Koning NRG Petten, The Netherlands FENDL-3 meeting March 23-26 2010, IAEA, Vienna

2. 2 Contents Introduction The TALYS code system Complete nuclear data libraries (TENDL) -n, g, p, d, t, h and a, 2400 nuclides, 200 MeV -Uncertainties and covariance data Performance -Differential data -Integral data This meeting -What can TENDL do for FENDL? -What can FENDL do for TENDL? Conclusions

3. 3 Neutronics, activation and nuclear data for fusion Monte Carlo calculational procedure specifically suitable for ITER/IFMIF/DEMO neutronics analyses Many relevant parameters can be determined: -Neutron flux distributions -Gamma flux distributions -Radiation dose in optical fibers + required shielding -Dose rates in port cell -Nuclear heating -Other relevant response parameters Activation issues: - activity, radiotoxicity, gamma dose rate, decay heat Complete and good quality transport and activation data libraries are essential for a full simulation of all these effects.

4. 4 Relative importance of regions of ITER upper port plug Contributions of: equatorial port plugdivertor port plug neutron flux distributions MCNP calculations (A. Hogenbirk, NRG)

5. 5 Loop over energies and isotopes PRE-EQUILIBRIUM Exciton model Partial densities Kalbach systematic Approx DSD Angular distributions Cluster emissions  emission Exciton model Hauser-Feshbach Fission  cascade Exclusive channels Recoils MULTIPLE EMISSIONSTRUCTURE Abundances Discrete levels Deformations Masses Level densities Resonances Fission parameters Radial matter dens. OPTICAL MODEL Phenomenologic Local or global Semi-Microscopic Tabulated (ECIS) DIRECT REACTION Spherical / DWBA Deformed / Coupled channel Giant Resonances Pickup, stripping, exchange Rotational Vibrational COMPOUND Hauser-Feshbach Fluctuations Fission  Emission Level densities GC + Ignatyuk Tabulated Superfluid Model INPUT projectile n element Fe mass 56 energy 0.1. TALYS code scheme OUTPUT Spectra XS ENDF Fission yields Res params. FF decay How ? 11/09/2007 - FINUSTAR 2 6/20

6. 6 TALYS-1.2 Released December 21, 2009, see www.talys.eu Use of TALYS still increasing -Estimated 400-500 users -About 160-200 publications using TALYS Some recent additions (present in TALYS-1.2): -Better fission + level density model from Bruyeres-le-Chatel -The option to easily/safely store the best input parameter set per nucleus (“best y”) -More flexibility for covariance development and adjustment to experimental data TALYS can be used for -In-depth nuclide/reaction evaluations (Recent examples from NRG: Na, Ca, Sc,Fe,Ge,Pb,Bi) -Global multi-nuclide calculations -We are now merging these two

7. 7

8. 8 The total TALYS code system TALYS: Nuclear model code, Fortran, 70000 lines (open source) TEFAL: ENDF-6/EAF formatting code, Fortran, 15000 lines TASMAN: Optimization and covariance program for TALYS, Fortran 10000 lines TARES: Resonance data and covariance generator, C++ 10000 lines TAFIS: code for data and covariance of average number of fission neutrons, C++ and Fortran, 3000 lines TANES: code for fission neutron spectra and covariances, C++ and Fortran, 3000 lines (includes RIPL code) AUTOTALYS: script to use the above codes and to produce nuclear data libraries in a systematic manner

9. 9 Resonance Parameters. TARES Experimental data (EXFOR) Nucl. model parameters TALYS TEFAL Output ENDF Gen. purpose file ENDF/EAF Activ. file NJOY PROC. CODE MCNP FIS- PACT Nuclear data scheme + covariances -K-eff -Neutron flux -Etc. -activation - transmutation Determ. code Other codes +Uncertainties +Covariances +(Co)variances +Covariances TASMAN Monte Carlo: 1000 TALYS runs

10. 10 Resonance Parameters. TARES Experimental data (EXFOR) Nucl. model parameters TALYS TEFAL Output ENDF Gen. purpose file ENDF/EAF Activ. file NJOY PROC. CODE MCNP FIS- PACT Nuclear data scheme: Total Monte Carlo -K-eff -Neutron flux -Etc. - activation - transmutation Determ. code Other codes +Uncertainties +Covariances TASMAN Monte Carlo: 1000 runs of all codes

11. 11

12. 12

13. 13

14. 14

15. 15

16. 16 TENDL: Complete ENDF-6 data libraries MF1: description and average fission quantities MF2: resonance data MF3: cross sections MF4: angular distributions MF5: energy spectra MF6: double-differential spectra, particle yields and residual products MF8-10: isomeric cross sections and ratios MF12-15: gamma yields, spectra and angular distributions MF31: covariances of average fission quantities (TENDL-2010) MF32: covariances of resonance parameters MF33: covariances of cross sections MF34: covariances of angular distributions MF35: covariances of fission neutron spectra (TENDL-2010) and particle spectra (TENDL-2011) MF40: covariances of isomeric data (TENDL-2011)

17. 17

18. 18 Some examples: differential data

19. 19

20. 20

21. 21

22. 22 Oktavian for Co Rochman and Koning, to appear in Fusion Engineering and Design

23. 23 Contents of TENDL-2009 Neutron, proton, deuteron, triton, Helium-3, alpha and gamma libraries: transport (ENDF-6) and activation (EAF) 2400 nuclides (all with lifetime > 1 sec.) 1170 nuclides (lifetime > 1000 sec) < 200 MeV, the rest < 60 MeV Neutron library: 1170 nuclides (lifetime > 1000 sec) with complete covariance data (MF31-MF35) For all nuclides processed MCNP-libraries (n,p and d) and processed multi-group covariances (neutrons only) Strategy: Always keep completeness, global improvement in 2010, 2011,… Extra effort for important nuclides, especially when high precision is required (e.g. actinides): TALYS input file + uncertainties, resonance parameters + uncertainties, “unphysical actions” All libraries are always reproducible from scratch All libraries based on compact reaction info The ENDF-6/EAF libraries are created, not touched

24. 24 Resonance Parameters. TARES Experimental data (EXFOR) Nucl. model parameters TALYS TEFAL Output ENDF Gen. purpose file ENDF/EAF Activ. file NJOY PROC. CODE MCNP FIS- PACT Current system: Data for all isotopes -K-eff -Neutron flux -Etc. - activation - transmutation Determ. code Other codes +Uncertainties +Covariances TASMAN Monte Carlo: 1000 runs of all codes Basic data

25. 25 Quality of data library = Completeness (all reactions) (MF1-MF35, all MT-numbers) Robust underlying physics (TALYS + improvements) Reproduce diff. measurements (TALYS+EXFOR; EXFOR only) Includes complete uncertainties (small for known reactions, large for unknown ) Small uncertainties (for important and well-measured nuclides) Correctness and processability (perfect format, flawless NJOY-processing) Reproduce integ. measurements (responses, k-eff, etc.)

26. 26 Quality of proton nuclear data (A. Konobeyev, ND-2010) ENDF/B-VII-p (LA-150): 30 nuclides TENDL-2009: 1170 nuclides

27. 27 TENDL for FENDL: possibilities Fill gaps: Proton libraries: Complete, versus 30 nuclides in ENDF/B- VII (JENDL/HE?) Deuteron libraries: is the only one existing (?), but requires development of MCNPX Neutron libraries -Take nuclides which do not exist elsewhere -Complete covariance data: adopt? -Extends up to 200 MeV: adopt? -Complete gamma production data: adopt? Or even: Take TENDL when better than existing libraries

28. 28 FENDL for TENDL Feedback on the performance of TENDL, good or bad. We may normalize TENDL to FENDL for nuclide-reaction combinations where TALYS can not beat FENDL. After that, TENDL provides completeness with MF1-MF35. Progress on processing and validation issues for protons and deuterons (NJOY + MCNPX + FISPACT issues)

29. 29 Conclusions We are approaching the situation in which the production of a complete ENDF-6 file is standard, quality assured and reproducible. When this is indeed accomplished, the main challenges are: Better physics models and parameterization of the nuclear models Selecting and measuring good experimental data Next, computer power does the rest NRG offers TENDL to FENDL To fill gaps in the fusion material chart To adopt covariance data, for transport and activation libraries To adopt high-energy data To adopt complete proton and deuteron libraries To adopt entire or parts of neutron libraries whenever the FENDL group thinks that is appropriate and only requests feedback in return.