ML20211F279
| ML20211F279 | |
| Person / Time | |
|---|---|
| Issue date: | 09/25/1997 |
| From: | Mace M NRC OFFICE OF ADMINISTRATION (ADM) |
| To: | Smithson C PURDUE RESEARCH FOUNDATION |
| References | |
| CON-FIN-W-6749, CON-NRC-04-97-046, CON-NRC-4-97-46 NUDOCS 9710010001 | |
| Download: ML20211F279 (7) | |
Text
-e a
p.Mic
, k-UNITED STATES p *-
j j
NUCLEAR REGULATORY COMMISSION 2
WASHINGTON, D.C. 20E!M001
- /
SEP 171957 Purdue Research Foundation
-ATTN: Chris Smithson
-1021 Hovde Hall Purdue University West Lafayette IN 47907-1021
Dear Mr. Smithson:
SUBJECT:
TASK 0RDER N0. 2 ENTITl.ED 'HODULARIZATION OF TRAC-P" UNDER CONTRACT NO. NRC-04-97-046 In accordance with Section G.4. Task Order Procedures, of the subject contract, this letter definitizes Task Order No. 2.
This effort shall be performed in accordance with the enclosed Statement of Work, The period of performance for Task Order No 2 is September 30, 1997 through May 31, 1998. The total estimated cost for full performance of this task order is $262,012.00. Funds in the amount of $162.000 are hereby obligated for performance of this task order. The Contractor shall not incur costs for this
~'
task order which exceed this obligated amount.
Accounting data for Task Order No. 2 is as follows:
B&R No.: 760-15-11-500-5 Job Code: W-6749 BOC Code: 252A RES ID: RES-C97-087 Appropriation No.: 31X0200 Obligated Amount: $162.000.00 The following individuals are considered by the Government to be essential to the successful. performance of the work hereunder:
John Mahaffey The contractor agrees that such personnel shall not be removed from the effort Q g[
under this task order without compliance with Contract Clause H.2-Key Personnel od I!ll!OEllOll01:lll[Illjilllli 00 O g 970925 NRC-04-97-046 PDR
Purdue:
--Contract No..NRC-04-97-046-
~ Task Order No. 2 Page 2 of 2
. The issuance of this task order does not amend any. terms or conditions of the subject cont'ract.
~
LYour contacts during the course of this task order are:
Technical Matters:
Jennifer Uhle. Project Officer
-(301) 415-6023 Contractual Matters:
Stephen Pool Contract Specialist (301) 415-8168 Please indicate your acceptance of this task order by having an' official.
-authorized to bind your organization.-execute three copies of this document in the space provided and return two copies to the Contract Specialist. You should retain the third copy for your records, Sincerely, jd E Ad&
Mary H.' ' Mac. Contracting Officer Contract Management Branch No. 1 Division of Contracts and Property Management Office of Administration
Enclosure:
As stated-
' ACCEPTED: TtSK ORDER N0. 2 y q)a C 9 - m, >
d NAME-DATE AM~
TITLE-j.
l m
a STATEMENT OF WORK TASK ORDER #2, *MODULARIZATION OF TRAC-P"
Background
To minimize the duplication of effort in improving the current suite of NRC thermal-hydr ~aulic and kinetics codes, the NRC plans to consolidate the codes into a single state of the art code or Advanced Reactor Code (ARC). ARC willincorporate all of the capabilities embodied in the separate' codes, so that the user needs will not be compromised. TRAC-P will serve as the basis for the consoldation process. To facilitate this effort and to support long term code improvements, TRAC-P will first be modemized, employing Foitran 90 as the coding language and restructured into a more modular design. Incorporation of the
- currently available code capabilities will then ensue.
High level functional modularity means that the functions of the code will be done in
. sections of the code, in essence subroutines that perform the pre-processing of the input deck will be separated from those that evaluate the physical models, which in tum are not merged with the subroutines that build the matrix or with those that solve the matrix. This distect zoning of funchons will fe6!itate the coordination of multiple developers that will be
-_ modifying the code simultaneously. This task order will modify the architecture of the TRAC-P code, which will be used as the basis of the consolidated code, to enhance the high-level functional modularity as a means of expediting Me consolidation effoit.
Additionally, during the modularization of the numerics, the code will be structured to facsistate the deveiop, Tent of a parallelized version, wh!ch will also be completed as part of ~
this task order. Parallehzaten will increase the speed of the code and the memory
- avastable for_each simulation. The goal of the parallelizaten is to provide a code version with a computational time that is much smaller than the time required to analyre the results. _ Reduced computation time wil' dbw the capabilities of the code to be more fully
' exercised. In addition to one of its current uses of providing detailed analyses to audit vendor or licensee analyses of new or existing designs, reduced run time wold allow more sensitivity calculations to be performed in support risk-informed regulation, to establish and revise regulatory requirements, to study operating events and to anticipate problems of potential significance.
Objectives The ob ectives of this contract are:
l
+
To enhance the high-level functional modulanty of the consolidated code;
-+
To provide NRC with support in planning the consolidation of its current suite of thermal-hydraulic systems and kinetics codes into the framework of TRAC-P;
+
To develop a coarse-grain parallelized version of TR AC-P.
c m
5 2
Work Requirements Task 1: Modularization of theTRAC-P Solution Procedure This task will essentially separate the building of the matrix from the reduction of the matrix (no subroutine will develop the terms of the finite volume equation matrix and also proceed with the matrix solution) and will also separate the development of the terms for the 3D components from those of the 1D components. These activities willincrease the high-level functional modularity of the solution procedure and will enhance the ability to implement various differencing schemes, facilitating the consolidation effort. TQe deliverables of this task include the documentation specified in Subtask 1.6 and a working version of the
- consolidated code with the required modifications.
This task is comprised of 5 subtasks:
Subtask 1.1: Development of Test Matrix The standard set of 42 test problems, developed under Job Code W6245, TRAC Code i
Maintenance, will be used to test the functionaPty of the new coding that evaluates the.
terms in the finite volume egration matrix and solves the matrix Since the test problems must exercise all new lines cf code, an appropriate software tool that evaluates code coverage will be used in Subtask 1.5 to determine the lines of code exercised by the problems. If coverage is not 100%, then test problems will be developed until all lines are executed. In dubtask 1.5, the test problems will be run with the old and new version of the -
solution procedure to confirm that the results are consistent.
Completion date: 0.25 after the initiation of the task order Subtask 1.2: Removal of Solution Coding from Subroutines that Evaluate Terms of the Finite Volume Equations -
In the subroutines that evaluate terms of the finite volume equation matrix, there is some coding that performs steps of the matrix solution. This coding shall be removed from the subroutines to enhance high level functional modularity. The functionality of the coding will be encompassed in the solution module developed in Subtask 1.4.
Completion date: 0.75 months after the initiation of the task order I
Subtask 1.3: Separation of 1D and 3D Term Evaluation Currently, some of the terms of the finite volume equation matrix for the 1D components are evaluated in subroutines that perform this function for the 3D components. Coding will
- be modified so that terms of the 1D and 3D components are evaluated in separate subroutines.
Completion date: 1.25 months after the initiation of the task order
=
l 3' Subtask 1 Af Craation of a Linear Solution Module All functionality removed in Subtask 1.2 will be included in the module developed in this subtask and will be incorporated into TRAC-P. This module will solve the matrix only and
- will not evaluate any terms of the equations. Furthermore, the matrix reduction of the 1D components shall be separated from that of the 3D components in the module.
Completion date: 2.75 months after the initiation of the task order Subtask 1.5: Testing and Modification The test matrix developed in Subtask 1.1 will be used to evaluate the changes to the code made in Subtasks 1.2-1 A. Since the test problems must exercise all new lines of code, an p
appropriate software tool that evaluates code coverage will be used to determine the lines l
of code exercised by the problems. If coverage is not 100%, then additional test problems
- will be developed until all lines are executed. The test problems will be run with the old and new version of the solution procedure to confirm that the results are consistent. Corrections -
i to the coding will be made until a null result is achieved.
Completion date: 3.5 months after the initiation of the task order Subtask 1.6: Documentation The code modifications and results of Subtask 1.5 shall be documented in a variety of
. forms including: SQA documents, as outlined in the Software Quality Assurance Document provided by the NRC at a later date, updates to manuals and submission to the; Verification test matrix in both text and electronic format.
Completion date: 4.5 months after the initiation of the task order Task 2: Modularization of Component Communication 1 Coding will be developed to modularize the communication between components.
Boundary information will be provided to each component at initiakzation and at each tima step in a consistent and organized fashion. A communication manager subrouhne will be called during initialization to provide the location of the required boundary data for each l component, so that at every time step, the proper information is provided to each component. The delivorables of th'3 task include the documentation specified in Subtask 1.5 and a working version of TRAC-P with the required modifications.
' This task is comprisea of five subtasks:
Subtask 2.1: Development of a Test Mainx i.
The stancard set of 42 test problems, developed under Job Code W6245, TRAC Code 4
Maintenance, will be used to test the functionality of the new coding that manages the
\\;
4 communication between components. Since' the test problems must exercise all new lines of code, an appropriate software tool that evaluates code coverage will be used in Subtask 2.5 to determine the lines of code exercised by the problems. If coverage is not 100%,,
. then test problems will be developed until all lines alte executed. in Subtask 2.5, the test problems will be run with the old and new version of the solution procedure to confirm that the results are consistent.
Completion date: 4.75 months after the initiation of the task order Subtask 2.2: Deletion of Coding Currently Performing Component Communication
. Presently, boundary information is provided to the components in a disorderly fashion through the use of pointers embedded into a variety of subroutines that evaluate the terms i
of the finite volume equations. This coding will be deleted but its functionality will be encompassed in the coding developed in Subtask 2.3.
j Completion date: 5.25 months after the initiation of the task order Subtask 2.3:- Development of a Modular Component Communication Package A module will be developed to manage the communication between components.
Essentially, this module will function as a communication manager and will be called during initialization to provide the location of the required boundary data for each component, so that at every time step, the proper information is provided to each component. This module -
. will provide the identical functionality as the coding deleted in Subtask 2.2 but will be located in one module rather than be dispersed amongst a variety of other subroutines that perform other functions as is currently the situation.
Completion.date: 6.75 months after the initiation of the task order -
Subtask 2.4: Testing and Modification
.' The test matrix developed in Subtask 2.1 will be used to evaluate the changes to the code made in Subtasks 2.2 and 2.3. Since the test problems must exercise all new lines of code, an appropnate software tool that evaluates code coverage will be used to determine the lines of code exercsed by the problems. If coverage is not 100%, then additional test problems will be developed until all lines are executed. The test problems will be run with the old and new version of the component communication manager to confirm that the results are consistent. Modifications to the coding will be made until a null result is achieved.
Completion date: 7.5 months after the initiation of the task order Subtask 2.5: Documentation Code modifications and results of Subtask 2.4 will be documented in a variety of forms, i including: SQA documents, as outlined in the Software Quality Assurance Document
.j
c
.c
..a.
5 provided by the NRC at a later date, updates to manuals and submission to the Verification test matrix in both text and electronic format.
Completion date: 8.5 months after the initiation of the task or' der Total task estimated level of effort: 4.0 s/m Task 3: Support for Planning and Management Provide consultation to NRC staff conceming code structure, solution methods, code development and developmental assessment activities. Assist with documentation of these activities.
Completion date: g.5 months after the initiation of the task order Task 4: ParalleHzation
- The contractor shall develop a coarse grain parallel solution technique for the TRAC-P code.. This parallel solution tecnnique will be implemented in either Parallel Virtual Machine (PVM) or Message Passing Interface (MPI). The code that is developed for this project must run on the NRC/RSPB's computers and must get the same answer whethar it is run in parallel or serial mode. This solution technique shall be designed such that it can be easily implemented in the future into the modemized TRAC-P code (TRAC-M).
The first deliverable will be the source code for the parallel TRAC-P code which can be compiled and executed on the NRC/RSPB's computers. The second deliverable will be the documentation required by the NRC/RSPB's Software Quality' Assurance plan. This documentation will be written in FrameMaker and delivered to the NRC in hard copy and electronic form.
Completion date: 8.5 months after the initiation of the task order Meetings and Travel For successful completion of the \\vork required in this contract, it is anticipated that the contractor shall travel to the NRC effice in Rockville, MD at the times specified below. The contractor may propose additional travel deemed necessary for the successful completion
- of this effort. Additional travel shall be approved in advance by the Project Manager, be specifically performed in support of this contract ans be in compliance with Federal Transportation RegulMions.
Task 1 Upon completion of Task 1, one one-day meeting for one person.
Task 2 Upon completion of Task 2, one one-day meeting for one person.
Task 3 in support of Task 3, two one-day meetings for one person.
.