Overview of TRACE V5.0 - NRC

Overview of TRACE V5.0

Regulatory Information Conference by

Christopher Murray March 14, 2007

2/21/2007 [email protected]

1

Project Goals TRACE: TRAC/RELAP Advanced Computational Engine Goals of the Modernization Project „

Develop a modern, maintainable, and extensible code that encompassed all of the capabilities of RAMONA, RELAP5, TRAC-PWR, TRAC-BWR

„

Maintain investment in existing RELAP5, TRAC-PWR, and TRAC-BWR input models

„

Provide a productivity-enhancing graphical analysis environment (SNAP)

„

Maintain in-house control of the code development and testing process

2/21/2007 [email protected]

2

TRACE Background „

TRACE is a component-oriented reactor systems analysis code designed to analyze reactor transients and accidents up to the point of significant fuel damage.

„

TRACE is a finite-volume, two-fluid compressible flow code with one, two, and three dimensional flow geometry and can model heat structures and control systems that interact with component models and the fluid solution.

„

Typical TRACE reactor models range in size from a few hundred to a few thousand fluid volumes. TRACE can be run in parallel.

„

TRACE can be run in a coupled mode with the PARCS three-dimensional reactor kinetics code.

„

TRACE has been coupled to CONTAIN through its Exterior Communications Interface (ECI). TRACE could be coupled to detailed fuel models or CFD codes in the future using the ECI. 2/21/2007 [email protected]

3

Development History The architecture of TRACE was driven by NRC requirements that the code be: „ „ „ „

Readable and understandable Maintainable Extensible Portable

In computer science, the general means to achieving these goals is to write code that is: „ „

Modular Object Oriented

NRC made the decision to follow an evolutionary path to create a consolidated code. The properties of TRAC made it the natural choice as a starting point rather than RELAP5.

2/21/2007 [email protected]

4

Development Timeline „ „

„ „ „

1997: Begin modernization of the TRAC-P code base to Fortran 95 1998 – 2003: Consolidation of capabilities of TRAC-P, TRAC-B, RELAP, and RAMONA into a single computational platform – “TRAC-M” (v3.0 up to v4.0) 2003: TRAC-M renamed TRACE (version 4.0) 2002 – 2004: Initial assessment, identification of various code problems, support for new reactors 2003 – present: Model improvement & error corrections made. Assessment continued & automated (version 4.0 up to version 5.0)

2/21/2007 [email protected]

5

TRACE Roadmap

V5.0RC1

V5.0-stable branch

Feature Freeze

Assessment “Freeze”

1/31/06

6/7/06

2/21/2007 [email protected]

V5.0RC2

V5.0RC3

10/25/06

12/12/06

V5.0 Declared

12/31/06

V6.0 development progress

V5.0 External Release

Bug Fix Releases As Needed (V5.0a, V5.0b, etc)

7/31/07

Main Development trunk

6

TRACE Roadmap (cont.) Tasks Remaining: „

Documentation z z z z

„ „

Assessment Manual (April 2007) User’s Guide (May 2007) Theory Manual (June 2007) Theory Manual Supplement will follow full release (September 2007)

Distribute full release to users Conduct Peer Review

2/21/2007 [email protected]

7

Applicability „

„

TRACE (and other T/H codes) are assessed and considered “valid” only over specific ranges and specific applications TRACE Version 5.0 is intended to be applicable to: z z z

„

Conventional PWRs (W 3-,4-loop and CE) Conventional BWRs ESBWR

For scenarios involving: z z

LBLOCA SBLOCA

2/21/2007 [email protected]

8

Applicability (cont…) „

Future assessments will be performed for: z z z z z z

W 2-loop PWRs with UPI B&W PWRs AP1000 EPR Transients BWR stability

2/21/2007 [email protected]

9

Assessment Matrix Separate Effects Tests: Phenomena

UPTF 1:1

Marviken MB-2 SG Tests G-2 Bundle; 336 rods FLECHT-SEASET ; 161 rods

FLECHT-Skewed; 108 rods

FLECHT ; 98 rods

THTF; 64 rods THETIS: 61 rods RBHT ; 45 rods FRIGG; 36 rods

CISE Adiabatic Tube

Dehbi Condensation ANL Nat. Circ. Loop

LWR 1:1

SCTF 1:25 CCTF 1:25

ROSA 1:48 LOFT 1:50

Bethsy 1:100

APEX 1:192 PUMA; 1/400 SPES 1:430 FIST; 1/624

FIX-II; 1/777 Semiscale 1:1600

10 2/21/2007 [email protected]

Full Scale (Volume Scale)

Small Scale

Integral Effects Tests: System Interactions

Assessment Matrix „

Comparison to previous NRC code assessment efforts: z z z

More comprehensive. The total number of simulations with comparisons to data exceeds 500 Broader range of T/H conditions covered Larger number of tests per facility Î Example z z

Previous Assessment: UPTF Test 6; Run 133 Current Assessment: UPTF » » » »

2/21/2007 [email protected]

– ECC Bypass

Test 6; Runs 131, 132, 133, 135, 136 Test 7; Runs 201, 202, 203 Test 5 Test 21

11

TRACE Assessment Documentation „

“Generic” Assessment Manual: z z z

„

New & Advanced Plant Support z z

„

Fundamental Problems (Appendix A) Separate Effects Tests (Appendix B) Integral Effects Tests (Appendix C) ESBWR Specific (ESBWR Code Applic. Report) EPR (EPR Code Applic. Report)

During the initial assessment and report preparation phase, emphasis placed on producing a calc note for each experimental facility z z z

Provides reference for input deck parameters Provides means to track input deck changes Assists in standardizing nodalization and various user options

2/21/2007 [email protected]

12

Use of Automation „

The assessment / documentation process is now automated. z z

z

z

AVScript: Controls code execution, processes input and output files. AcGrace: Graphics package for code to data and/or code to code comparisions. FrameMaker: Word processing with links to figures produced by AcGrace. Input decks, calc notes, and associated assessment reports are all under version control

2/21/2007 [email protected]

TRACE Executable AVScript

Input Decks

AcGrace

Test Data

Figures FrameMaker Report Sections

Analyst

13

Peer Review „

Upon completion of documentation, we will initiate a peer review of TRACE. z z z

Provide critical review of governing equations, models and correlation packages in TRACE Comment on the assessment matrix; breadth & range of conditions Comment on the documentation; clarity, ease-of-use, thoroughness

2/21/2007 [email protected]

14

Summary & Conclusions „

We are nearing the completion and public release of TRACE Version 5.0. Documentation is a priority, and will be the focus of our attention until final release - expected to be completed in Spring/Summer 2007.

„

Extensive assessment has been performed with a “frozen” version of TRACE – assessment reports are currently being finalized.

„

In general, TRACE Version 5.0 demonstrates reasonable agreement with data.

„

Subsequent versions of TRACE (6.0, 7.0, etc.) will attempt to resolve conservatisms and incorporate new features as requested by users.

2/21/2007 [email protected]

15