WSRC Approach to Validation of Criticality Safety Computer Codes

WSRC Approach to Validation of Criticality Safety Computer Codes
Author:
Publisher:
Total Pages: 11
Release: 1991
Genre:
ISBN:

Recent hardware and operating system changes at Westinghouse Savannah River Site (WSRC) have necessitated review of the validation for JOSHUA criticality safety computer codes. As part of the planning for this effort, a policy for validation of JOSHUA and other criticality safety codes has been developed. This policy will be illustrated with the steps being taken at WSRC. The objective in validating a specific computational method is to reliably correlate its calculated neutron multiplication factor (K{sub eff}) with known values over a well-defined set of neutronic conditions. Said another way, such correlations should be: (1) repeatable; (2) demonstrated with defined confidence; and (3) identify the range of neutronic conditions (area of applicability) for which the correlations are valid. The general approach to validation of computational methods at WSRC must encompass a large number of diverse types of fissile material processes in different operations. Special problems are presented in validating computational methods when very few experiments are available (such as for enriched uranium systems with principal second isotope 236U). To cover all process conditions at WSRC, a broad validation approach has been used. Broad validation is based upon calculation of many experiments to span all possible ranges of reflection, nuclide concentrations, moderation ratios, etc. Narrow validation, in comparison, relies on calculations of a few experiments very near anticipated worst-case process conditions. The methods and problems of broad validation are discussed.

A Technique for Code Validation for Criticality Safety Calculations

A Technique for Code Validation for Criticality Safety Calculations
Author:
Publisher:
Total Pages: 22
Release: 1991
Genre:
ISBN:

There are probably as many techniques to validate computer codes for criticality safety purposes as there are computer codes and code validators. One method used at Martin Marietta Energy Systems, Inc., to validate the KENO code and associated cross sections consists of determining a single-sided, uniform-width, closed-interval, lower tolerance band for k{sub eff} of critical systems. For application, this lower tolerance band becomes the upper safety limit (USL) acceptance criteria for subcriticality based upon the KENO calculations. A system is considered acceptably subcritical if a calculated k{sub eff} plus 2 standard deviations lies below this upper safety limit (i.e., k{sub eff} + 2[sigma]

Certification Process of Safety Analysis and Risk Management Computer Codes at the Savannah River Site

Certification Process of Safety Analysis and Risk Management Computer Codes at the Savannah River Site
Author:
Publisher:
Total Pages: 10
Release: 1992
Genre:
ISBN:

The commitment by Westinghouse Savannah River Company (WSRC) to bring safety analysis and risk management codes into compliance with national and sitewide quality assurance requirements necessitated a systematic, structured approach. As a part of this effort, WSRC, in cooperation with the Westinghouse Hanford Company, has developed and implemented a certification process for the development and control of computer software. Safety analysis and risk management computer codes pertinent to reactor analyses were selected for inclusion in the certification process. As a first step, documented plans were developed for implementing verification and validation of the codes, and establishing configuration control. User qualification guidelines were determined. The plans were followed with an extensive assessment of the codes with respect to certification status. Detailed schedules and work plans were thus determined for completing certification of the codes considered. Although the software certification process discussed is specific to the application described, it is sufficiently general to provide useful insights and guidance for certification of other software.

Criticality Safety Validation: Simple Geometry, Single Unit[sup 233]U Systems

Criticality Safety Validation: Simple Geometry, Single Unit[sup 233]U Systems
Author:
Publisher:
Total Pages:
Release: 2001
Genre:
ISBN:

Typically used LMITCO criticality safety computational methods are evaluated for suitability when applied to INEEL[sup 233]U systems which reasonably can be modeled as simple-geometry, single-unit systems. Sixty-seven critical experiments of uranium highly enriched in[sup 233]U, including 57 aqueous solution, thermal-energy systems and 10 metal, fast-energy systems, were modeled. These experiments include 41 cylindrical and 26 spherical cores, and 41 reflected and 26 unreflected systems. No experiments were found for intermediate-neutron-energy ranges, or with interstitial non-hydrogenous materials typical of waste systems, mixed[sup 233]U and plutonium, or reflectors such as steel, lead, or concrete. No simple geometry experiments were found with cubic or annular cores, or approximating infinite sea systems. Calculations were performed with various tools and methodologies. Nine cross-section libraries, based on ENDF/B-IV, -V, or -VI. 2, or on Hansen-Roach source data, were used with cross-section processing methods of MCNP or SCALE. The k[sub eff] calculations were performed with neutral-particle transport and Monte Carlo methods of criticality codes DANT, MCNP 4A, and KENO Va.

Validation and Verification Plan for Safety and PRA Codes

Validation and Verification Plan for Safety and PRA Codes
Author:
Publisher:
Total Pages: 47
Release: 1991
Genre:
ISBN:

This report discusses a verification and validation (V V) plan for computer codes used for safety analysis and probabilistic risk assessment calculations. The present plan fulfills the commitments by Westinghouse Savannah River Company (WSRC) to the Department of Energy Savannah River Office (DOE-SRO) to bring the essential safety analysis and probabilistic risk assessment codes in compliance with verification and validation requirements.