ML20090M295

From kanterella
Jump to navigation Jump to search
Rev 4 to FATE-84-100, Vipre Code Maint Procedures Manual
ML20090M295
Person / Time
Site: Columbia Energy Northwest icon.png
Issue date: 11/17/1987
From: Lauhala V, Srikantiah G, Stewart C
Battelle Memorial Institute, PACIFIC NORTHWEST NATION
To:
Shared Package
ML20090M286 List:
References
FATE-84-100, NUDOCS 9203240140
Download: ML20090M295 (30)
v • d • e


Text

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ - _ _ - -

.:.. ~,

et ONQO , ,.

.d* b. #

Le<.-Q < -

/ FATE-84-100 REVISION 4 VIPRE CODE MAINTENAllCE PROCEDURES MAfiUAL September 1987 A

APPROVED C. C Stewart, Manager Fluid and Thermal Science Energy Sciences Department APPROVED , -M~[7 V. M uhal p ality Engineer APPROVED [b 2k G. S. SAfkantiah, t?RI Program Manager '

bk ok$40 tjjpg16 PDR

_j

1 a

4 REVIS10f4 4 NOTEt This revision makes extensive changes'throughout the manual and individual 4 changes are not shown. This is a complete copy of FATE-84-100 Revision 4. l Please return Revision 3 to C. W. Stewart,-P.O. Box 999, Batteile Northwest, l Richland, Washington 99352. -

l 1

i i i f

i l

l l

t i

I

)

i

?

t i

l

)

1 I

- , . .-..:-.-, - :.; . .- - -.......,----.:- . . -. - - --- - , . . - ~ , , - . . . . . . - . . . . - . - . - .

... j l

i CONTENTS i

1.0 INTRODUCTION

....................... ... 1 1.1 PROCEDURE MANUAL . . . . . . . . . . . . . . . . . . . . . . . 1 1.2 VIPRE CODE PACKAGE . . . . . . . . . . . . . . . . . . . . . . 2 1.3 RESPONSIBILITIES . . . . . . . . . . . . . . . . . . . . . . . 2

]

i 1.4 CONTROL OF DOCUMENTS AND RECORDS . . . . . . . . . . . . . . . 3  !

2.0 CODE PACKAGE CONFIGURATION AND RESIDENCE . . . - . . . . . . . ~ . .. 5 2.4 VERSION IDENTIFICATION . . . . . . . . . . . . . . . . . . . . 5 2.2 RESIDENCE . . . . . . . ................... 5 3.0 ERROR CORRECTION . . ._. . . ................. . 6 3.1 ERROR REPORTING , . . . ................... 6 3.2 ERROR CORRECTION . . .-. . . . . . . . . . . . . . . . . . . . 8 4.0 RELEASE OF A NEW MOD . . . . ...........-........ 9 4.1 lNITIATION . . . . . . . . . . . . . . . . . . . . . . . . '.-. 9 4.2 TESTING AND REVIEW . . . . . . . . . . . . . . . . . . . . . 10 5.0 CODE MANUAL REVISION , . . . . . .-. . . ... .-. . . . .-. . . . . 12 5.1 REVISION CONTROL . . . . . . . . . . . . . . . . . . . . . . . 12 5.2 REVIEW AND TRANSMITTAL . . . . . . . . . . . . . . . . . . . . 12 6.0 FORMS . . . . . . . . . . . . . . . . . . . . .-. . . . . . . . . .

14 6.1 CONTROLLED DOCUMENT LOG , .- . . . . . . . . . . . . ... . .- 14 ,

6.2 DOCUMENT LOG . . . . . . ... . . .-. . . . . . . . . . . . . . 14 -;

6.3 VIPRE CHANGE REQUEST-. . . . . . . . . . . . . . .:. . . . . .- -

14 6.4 VIPRE CHANGE REQUEST LOG . . . . . . . . . . . . . . . . . .- 14 Last Page .:.............................. 18 Revision 4' FATE-84-100' Page iii_

.. -- -..-,z..- , , ..- a., ,- - . . , -,.;.,.

9 1

l i

TABLES  ;

t 1 Documents and Records Prescribed by FATE-84-100 . . . . . . . . . . . 4 i

a.

W d

1 e

d, f

4 4

9 Revision 4._ FATE-84-100 Page iv_

. .. .m____.._-m.._. . . _ . . . . _ . _ _ . . . . _ _ , _ . _ _ _ _ , - . _

- . - - - . _ . _ _ - . . . - . ~ . - - - - _ - - . . . - - - -

i i l  !

j i VIPRE CODE PACKAGE MAINTENANCE PROCEDURES MANUAL

1.0 INTRODUCTION

This manual descr'.'^es procedures for maintenance and control of the VIPRE code package. These procedures shall be followed in maintaining publicly released versions of VIPRE and other versions as required by the sponsor, the  ;

Electric Power Research Institute (EPRI). No version of the VIPRE code package shall be maintained under this procedure without written approval from EPRI.  !

?

1.1 PROCEDURE MANUAL 1.1.1 The Battelle VIPRE project manager is responsible for preparation, control, and review of the manual and revisions under the provisions of the Battelle Quality Assurance Manual (PNL-MA-70), and the VIPRE project QA plan (APC-012). ,

1.1.2 The original manual and revisions shall be approved by the Section i Manager, Battelle Fluid and Thermal Science Section, Quality Engineer,

, and EPRI. Approval shall be indicated by the responsible person's  !

signature on the cover page. '

1.1.3 The project manager is responsible for control of distribution of this manual and revisions.

1.1.3.1 Each person performing work that uses the procedures Lin  !

this manual shall be given a controlled copy.

1.1.3.2 Controlled copies of the manual shall be given a unique control. number before being assigned to an individual. A 1 record of distribution (Section 6.1) will'be maintained and revisions will be distributed to holders of controlled copies.

1.1.3.3 Uncontrolled copies of the maiual sh'all be distributed on request. These copies will not be-numlared or recorded, and will not be updated whei revisions _are made. '

. Revision 4 . FATE-84-100 Page- 1 ,

1 v.+-,,- $.+-i+,,iv d . E . e -.,- r -- . - y.,--e..-v.,- ~-.-.,.+,-,,.e,.4y._,,.y.,-w,- . . , . . , , 4- ,.,,.,,c, ., -..m, .my-..,e'.-w_,,:,e , -e.,.#~y.. e, wy

j 1.1.3.4 Controlled copies shall be marked " CONTROLLED COPY NO. "

, on the title page. Uncontrolled copies shall be marked

" UNCONTROLLED COPY" on the title page.

1.2 VIPRE CODE PACKAGE 1.2.1 A VIDDE code package shall be det:ribed by its currently published code manuals, as revised.

1.2.1.1 A list of the code manuals for each code package shall be -

maintained by the project manager.

1.2.1.2 In cases where selected components of a code package are maintained under this procedure, the project manager shall indicate those components on the list prescribed in 1.2.1.1 >

above.

1.3 RESPONSIBILITIES 1.3.1 The persons who perform the functions of this procedure are the project manager, the code custodian, and individual developers. Their responsibilities are described as follows:

1.3.1.1 The project manager is responsible to EPRI for meeting -

the technical and schedule requirements of this procedure.

The project manager also schedules and assigns participants for internal reviews and has internal approval authority as defined for this procedure.

1.3.1.2 The code custodian is responsible to the project manager for maintaining the tape and disk files of the code package and preparing and maintaining the QA documents in accordance with this procedure. t 1.3.1.3 Individual developers assigned to the VIPRE project are responsible to the project manager for developing and.

testing error corrections to the code package. Tney also participate in internal reviews as assigned by the project manager.

- Revision 4 FATE-84-100 Page 2 i

+.Yy y y.gyr r-g-, w a-,9 4.-#.4y-97 4+-w c .y.. 9 mi,v.- ,e.w-- awe. gM^ -948,

t l

1.3.2 The project manager shall assign and maintain a list of qualified persons assigned to perform the responsibilities of code custodian and developers as described in Section 1.3.1 above.  :

1.4 CONTROL OF DOCUCNTS AND RECORDS 1he records prescribed by this procedure are listed in Table 1. Other i records maintained by the project shall be listed in the Project File Index.

, The responsible individual shall maintain these records as provided in the Battelle Quality Assurance Manual (PNL-MA-70), the VIPRE Project QA Plan (APC- t 012) and this procedure manual. I 1.4.1 Records in use shall be stored in a location that is readily accessible. When ready access is no longer required, the project manager may-move records to long term storage.

1.4.1.1 Records in long-term storage shall be retained in a repository with a two hour fire rating or at dual facilities and shall be properly identified.

1.4.1.2 Prior to long-term storage the project manager shall inventory the records to insure that all those identified have been accumulated and are complete and legible.

1.4.1.3 Records shall be maintained as described in the project  ;

RecordsInventory.a'ndDispositionSchedule(RIDS).

1.4.1.4 The-project manager shall maintain a log of records and data placed in long-term storage. The log shall include the storage receipt number and retention period.

1.4.2 At the termination of the VIPRE project, the project manager shall deliver all quality. assurance records to EPRI.

i

~ Revision 4 FATE-84-100 Page- 3 l

c  ;

_._ _ _ . . . . _ . ~ - .._..;_.__.u_.~.- ~,._ _ _.. -. _ .a _ - . _. -

. - . _ - - . - . . . - . . - - . _ . . . - ~ . . . - - . . - . _ . - . - . . - . - . ._ _-. ... - -.

. l TABLE 1. Documents and Records Prescribed by FATE-84-100 Applicable Responsible Retention Descriptien Sections Person

1. EPRI approval for maintaining 1.0 Project Manager a version under FATE-84-100
2. VIPRE Code Package Maintenance 1.1.1 Project Manager Procedures Manual FATE-84-100
3. Log of distribution of 141.3.2 Project Manager FATE-84-100
4. List of VIPRE Code Manuals 1.2.1.1 Project Manager
5. List of assigned staff 1.3.2 Project Manager
6. Project File 'Index 1.4.0 ProjectManager
7. Project Records Inventory and 1.4.1.3 ProjectManager Disposal Schedule
8. Log of records in long term 1.4.1.4 Project Manager storage
9. Backup tapes 2.2.1 Code Custodian
10. Tape log and file directories 2.2.2.1 Code Custodian
11. Change Request Log 3.1.2.2 Code Custodian
12. VIPRE Change Request File 3.1.2.3 Code Custodian
13. Error Notification File 3.1.3.4 Code Custodian
14. New Mod Document 4.2.2 Code Custodian
15. Master copies of code manuals 5.1.1 . Project Manager Page 4 Revision 4 FATE-84-100

2.0 CODE PACKAGE CONFI(MATION AND RESIDENCE _

This chapter describes the configuration and location of versions of the VIPRE code package in terms of site, machine, and device.

C.1 VERSION IDENTIFICATIC.'l 2.1.1 The VIPRE code package shall be identified by name, major version number, reletse MOD number, computer system, and latest change identifier. For example:

e VIPRE-01-MOD-1, VAX VERSION OFJATED THROUGH CHANGE 16 2.1.2 Each code version that is released to EPRI shall print a heading in its output that identifies the code version with the infonnation prescribed in Section 2.1.1 above. .

(

2.2 RESIDENCE 2.2.1 The code custodian shall maintain the master copy of the current MOD of VIPRE on computer disk accessible by VIPRE developers at Battelle.

A backup copy of the current VIPRE MOD and the most recent previous MOD shall De stored on magnetic media at Battelle and at least one other site.

2.2.2 _The code custodian shall assure that magnetic tapes stored at Battelle areclearlylabeledtoidentifythembycodeversion,(Section2.2.1) creation date, and general contents.

2.2.2.1 The code custodian shall maintain a log-(Section 6.2) of-all tapes ' stored under this section showing their location,

. identification, status and general contents. A directory of the tape contents shall be filed with the _ log.

2.2.2.2 The tape log shall be ' :tained as long. as tapes referenced -

on it are being stored.

Revision 4 FATE-84-100 Page 5 l

_ _ _ l

3.0 ERRORCORRECTIOJJ This chapter describes procedures for requesting, developing, testing, reporting, and controlling changes to programs and data in the VIPRE code l package for the purpose of error correction.

3.1 ERROR REPORTING ill reports and requests for error corrections shall be submitted in writing to the code custodian for processing.

3.1.1 The error correction request shall contain at least the following-information:

, (1) The name, address, and telephone number of the person making the requt.at.

(2) Identification of the VIPRE code or document version-that I exhibits the error.

(3) A description of the problem and the conditions that caused it.

(4) Input data for a simulation that exhibits the-error (not required fordocumentationerrors).

3.1.1.1 The code custodian may reject those requests that do not

)- contain the information specified above, and return them to the r.quenor without action.  !

3.1.1.2 A completed VIPRE Change Request form (Section 6.3), an EPSC Trouble Report, or similar form-is acceptable for the-purpose of Section 3.1.1.1. A VIPRE Change' Request form may be prepared from information submitted for use as a cover sheet.

3.1.1.3 If the error correction request satisfies the requirements of Section 3.1.1, the code custodian shall process it in accordance with 3.1.2 below.

3.1.2 The code custodian shall. assure that a test simulation is run with theinputprovidedasdescribedin3.1.1(4)toduplicatethereported

- error and/or that= documentation errors are investigated.

Revision 4 FATE-84-100 Page 6

, J

E 3.1.2.1 If it cannot be determined that an error exists with the input provided above, or it is found that the input is in error, no code change shall be made and the change request returned te da originator.

3.1.2.2 If the error occurs as de'eribed, a documentation error is confirmed, or any other errors occur in the test simulation, the code custodian shall assign the change request with a log number and enter it in the change request log (Section 6.4) and assure that corrections are developed in accordance with Section 3.2 if correction is possible.

3.1.2.3 Whether or not an error is found, the code custodian shall enter the appropriate disposition (3.1.2.1 or 3.1.2.2) on the action section of a change rt. quest form and file a copy.

3.1.3 The code custodian shall supply a list of all-code errors logged during a month to the EPRI program manager, the Electric Power Software Center (EPSC), and VIPRE subscribers by the fifteenth of the following month as prescribed below.

3.1.3.1 New code errors for the month shall be reported to EPRI by letter. If no new errors were logged, the letter shall so state.

3.1.3.2 A description of new code errors for the month shall be reported to EPSC by appending _ such descriptions to a disk file on an EPSC computer. EPSC shall be notified by telephone when the file _is updated or that no new errors were logged.

3.1.3.3 The names and addresses of VIPRE subscribers shall be determined by the latest list supplied by the EPRI project manager.

-3.1.3.4 The code custodian shall file a copy-of .the error notification each month as a project record.

Revision 4 FATE-84-100 Page 7 1

j

3.2 ERROR CORRECTION Interim error corrections shall be developed if possible-as a service to '

VIPRE subscribers, who may obtain them when available upon request. - However, their installation and application shall be at the user's r_isk since such corrections are not fully verified-until a-new MOD is released in accordance with SE: tic' 4.0.

l i Revision 4 FATE-84-100- Page 8 l ,

l

4.0 RELEASE OF A NEW MOD New MODS of VIPRE are publicly released from time to time to incorporate the error corrections and modifications developed as described in Section 3.2. Procedures are prescribed in this chapter for creating, te: ting, review, and documentation of each new M00.

4.1 INITIATION 4.1.1 A new MOD shall be created at the written direction of EPR1, The new MOD creation procedure shall begin with a review of the following items by the project manager and at least one other qualified person.

This group shall be referred to throughout this section as the

" reviewers".

1) The set of all code modifications and corrections developed since the last MOD under Section 3.2 (revision set) and the corresponding individual test cases.
2) Standard test cases and other data sets revised since the last M00.

4.1.2 The reviewers shall provide the code custodian with an approved code revision set and a set of test case input to validate the new M00.

4.1.2.1 The approved revision set shall consist of all code modifications and corrections developed since the last MOD that are approved by the reviewers for inclusion in the new MOD.

4.1.2.2 The test case input shall include at least the standard test cases revised since the last M00.

4.1.2.3 EPRI shall approve the selected test cases in writing before they are used to validate the new M00.

Revision 4 FATE-84-100 Page 9

4.2 TESTING AND REVIEW 4.2.1 The code custodian shall assure that a test version of the new MOD is created t'y applying the approved set of code revisions to the current MOD and that the new version is tested on each computer system it is to be released on using the approved test input.

4.2.1.1 The reviewers shall check the listings of the test version source and test case output from each computer system to insure the following criteria are satisfied:

1) The results of the standard test cases are identical to those of the current MOD, or, if different, all differences are documented in the new MOD Document (NMD - Section 4.2.2) as the result of error correction, or approved test case revision.
2) The test case output from each computer system agrees to five significant digits or the reason for the difference is explained in the NMD.

4.2.1.2 When the review is satisfactory, as indicated by the reviewers' signatures on the front page of the listings, the following actions shall be perforced by the code custodian:

1) Copy the new MOD and revised standard test cases into the Battelle master computer files and purge the existing MOD (Section 2.2.1).
2) Create backup tapes of the new M00.
3) Transmit a version of the new MOD for each computer system to EPRI or other organization designated by__

EPRI for distribution.

4) Complete and file the new MOD document in accordance I

with Section 4.2.2 below.

l 1

Revision 4 FATE-84-100 Page 10

4.2.1.3 If the review is not satisfactory the reviewers shall document the deficiencies and necessary remedial action.

! The code custodian shall assure that the code revision set is modified as necessary and the test cases are rerun until all discrepancies have been corrected. Subsequent reviews shall be documented as above or as in 4.2.1.2.

4.2.2 A New MOD Document (NMD) shall be compiled by the code custodian for each new MOD released. The NMD shall contain at least the following items:

1) -List of all code revisions as revised in 4.2.1.3 above that are approved for inclusion in the new M00.
2) EPRI approvals of test cases from Section 4.1.1.2
3) Final test case output from Section 4.2.1.2 above for each computer system.
4) Final code source listings on paper, computer tape, or microfilm for each computer-system.
5) Documentation of deficiencies and resolution from Section 4.2.1.3.
6) Copies of transmitt-1 documents ~to EPRI or other designated organization.
7) Copies of code manual revisions as printed by EPRI.

Revision 4 FATE-84-100 Page 11

5.0 CODE MANUAL REVISION The procedures in this chapter shall apply only to those manuals that define a VIPRE code package and are listed by the project manager under Section 1.2.1. Revisions to the VlPRE code manuals shall be prepared and submitted to EPRI when a new MOD is created if such revisions are required.

5.1 REVISION CONTROL 5.1.1 The project manager shall maintain master copies of the latest t approved version of each volume of VIPRE code manuals. Master copies shall be retained until the changes they contain are published under Section 5.2 below. Atthattimethenewversions(revisedpages replaced) shall become the master copies.

5.1.2 The project manager shall assure that all changes are edited manually into a copy of the master documents.

5.1.2.1 Significant code manual changos arising from error reports shall be documented and reviewed under Section 3.1 and shall be reviewed by EPRI under 5.2.1 below.

5.1.2.2 Minor changes to the manuals that do not alter their basic meaning or organization (e.g., correction of typographical errors, editorial changes for clarification, renumbering of pages or figures, etc.) shall be reviewed by EPRI under Section 5.2.1 below.

5.2 REVIEW AND TRANSMITTAL 5.2.1 Upon EPRI request, or when EPRI has directed Battelle to create a new MOD of the code, the project manager shall compile draft replacement pages, if any, from document changes accumulated since_the previous M00.

5 . 2 .1. ~1 When complete, the project manager shall transmit the draft replacement pages to-EPRI for review.

Revision 4 FATE-84-100 Page 12 i

5.2.1.2 The project manager shall incorporate EPRI comments and corrections into the draft replacement pages and resubmit them to EPRI for further review as necessary.

5.2.2 When EPRI is satisfied that their comments have been resolved, the draft replacement pages shall be copied to EPRI mats and delivered' to EPRI for final printing and distribution. Final EPRI approval is indicated by receipt of the published revision package.

5.2.3 A copy of the code manual revisions as printed by EPRI shall be included in the new MOD document under Section 4.2.2.

u _

Revision 4 FATE-84-100 Page 13 4

6.0 FORMS This section contains-forms referred to in previous sections of this manual. A brief description of the purpose of each- fonn is provided below.

6.1 CONTROLLED DOCUMENT LOG The Controlled Document Log is used to record the distribution of a given controlled document and its revisions (Section 1.1.3.2).

6.2 DOCUk_NT LOG The Document Log records creation, content, and changes in the location of documents generated by procedures in this manual. It is used to record backup tapes (Section 2.2.2.1).

6.3 VIPRE CHANGE REQUEST-The Change Request may be used to_ report code errors (Section 3.1.1.2).

6.4 VIPRE CHANGE REQUEST LOG The VIPRE' Change Request Log records each change request received and its disposition from receipt to installation of a change to the code-(Section3.1.2.2).

Revision 4 FATE-84-100 Page '14

i V

E LR A

T e

g T

I a M P S N

AV RE TR N

O I

S I

V EV RE R

F O

E T

A D

V E

R D

' E

_ EN /

f

_ TG AI a DS S

G A O

L T

N $

E M

U )

. C S O S D E

. R '

. D D

. E D

  • L A L

O ,

R N T O

. N I

. O T C A -

Z I

N A

G R

O E E L M T A I N T (

0 T

D E

N G

I S

S

+

A 9

T N

E M .

U C .

O _

D _

ll1Ill l!l l!

DOCUMENT LOG Page TITLE IDENT LOCATION AND DATE NO. CONTENTS 1 2 .3 4 5 9

Revisica 4 FATE-84-100-6.2 16 1

_ _ _ . _ _ _ _ _ _ . _ _ _ _ _ _ :i

l I

VIPRE CHANGE REQUEST No.

OPERATING

1. VERSION ID. SYSTEM ,
2. REQUESTOR PHONE /

ADDRESS:

3. DESCRIPTION (attachcontinuation_sheetsifnecessay)

To be completed by Battelle.

DATE RECEIVED ASSIGNED T0 ACTION:

(

l

-Change Reviewed by Date Approval for New MOD Date Project-Manager Revision 4 FATE-84-100-6.3 17 l

l 1

! .: _ . 2 , _

A -m .- %k=*MksT,d n -r' -MP' JA,iAs---s, ,4 , ne t.,  :-w-,e,-<AMs4- *4.-@ -MM4 43 m ,<Ga &4 Mm~o- 4_, ,onk nns. ma- o<4-- , _ o-, Ewmv Jay k

0 h_

Cn O trl W A W>

WO

< C4 O CL O.

=

O '

< w N.

e-M O

Q sn.=

O O

W 2':

, LD C M&

M M

4 e LD O i

.J c

h (

M ,

W D e Q'

W (.

C:C (

W .

CD g'

=

U W

% 2 Oe e

> p

  • Q.

! M ct:

U t/)

W Q

f L

l i

I W e b-- U '

a:C W OE t i .

O

c.
  • WO C:C = ,

- , , w w , -e--

/

1d ,

i i

a f

4

+

I Attachment.3 I

4 4-l 4

4 if I

l

.I a

i 8

<f a

4 4

l n

1 4'

4 e

i.

4 i

I i

k 4

4 i

N ll t.i a

e if T

A 1

4

+

1 I l f

I l

.j 1

l l

1 J

i i

1 i

i

. ,.. , _ . , ,...m... 1..,___,.,._., ,,-..._...m ,. ., , ...,,,_,,i.,,,__...,,,$. . . . , , , , _ ,,..J,,,#.i-_,... # Li , .,

Print ll frigg313007.preplot.out ll Drift Flux Model Verification: FRIGG test 313007 1.00 -

~

0.90 -

.0.80 FRIGG test no. 313007

4. -
a measured data 0.70 -. VIPRE-01 with drift flux model C ~

- 0.60 -

o .

E -

~

' O.50 -

..E -

o -

O.40 -

c-  :

I

^

0.30 -

a

~

0.20 --

~

^

0.10 -. 3

a

~

' ' ' ' ' ' ' ^ ^ ' ' ' ' ' ' ' ' ' ' ' '

[ 0.00 ' ' ' '

50 '75 100 .

125 150 axial' distance, (inches) 3

Print ll frigg313016.preplot.out ll Drift Flux Model Verification: FRIGG test 313016 t

t 1.00 -

0.90 -

o 8o i FRIGG test no. 313016 1

~

0.70 -

a measured data i
Vli- RE-01 with drift flux model

.g 0.60 t  :

~

i

$ 0.50 -

^

4 o

'5 -

a

> 0.40 -

~ i i

0.30 --

3 i 0.20 "--

- ^

0.10 -- a

' E '

0.00 ' ' '

25 50 75 100- 125 150 axial distance, (inches) ,

4 e

Print ll frigg313019.preplot.out ll Drift Flux Mode! Verification: FRIGG test 313019 1.000 --

0.900 E

FRIGG test no. 313019

~

0.800 -

0.700 --

^

@ 0.600 h-3 ts  :

"- ^

. $ 0.500 o  :

~5  :

> 0.400 -

n 0.300 h a measured' data

^

VIPRE-01 with drift flux model 0.200 -

0.100 --

0.000 ''''''''''''''''''''' 4- ' ' ' ' '

O 25 50 75 -100 125 150 axial distance, (inches)

Print ll frigg313020.preplot.orit ll Drift Flux Model Verification: FRIGG test 313020 1.000 --

0.900 --

~*

E FR GG test no. 313020 0.700 h a measured data a

VIPRE-01 with drift flux model a

~

,8 0.600 -

ucts

. A

.b 0.500 --

ao  : .

> 0.400 h 3

~

0.300 --

6 0.200 h

. a 0.100 --

O.000..

0 25 '50 75 100 125 150 axial distance, (inches) .

=w u -___.__' .--.__--_-.-.__m_____

_ _ - - . _ _ _ . _ - . . _. _ _ . . _ . __ . . _ __- ~ - . . _ . . . . . . . _ . - _ . . _ . _ - _ _ . . _ _ . _ . _ _ _ _ _ _ . . . _ _ ___

l

- Attachment 4-r s

b

.I I

4 E

t f

i i

- . , . . - . , . , , _ , , - . . , , . . , u, , ,.,0,,,_ , , . . , , , . , ., _,-ms.,, 4

84 Ge fft A4fCN 1P

. L., n.

~

n. .. 7.s.

syvE t**

o ab CD40if@# e, r j ... t, l p

save =esov esom amen 6 swane av J e t l l

.gg EQuatois son

' I m oo.itLEv .

A -

  1. O m bhaf 'v1

- tsvis soLwe Poa f Enf AT>s ashat#tSes

  1. 8 8T anc Caussatows A*C Cow.T4 Lhth poussvag Of aNafNes 99

[~

d6

' M LaSt uvth 7

fts i

T Ca6Cubart C04fatafV ta*0as

  1. 1 au CELA$

7 gates soa Avatays seasswa s ..

=

CuanGE et Anw ano 6afen46 eas46.anomo a

T 45Ge setssuag nvaaren l l

} C:> suit Ftut0 PWC*ttfits (Peop) l I Cnamnet-av twammes nowfen l l paa estssues CuanGs as au CELLS ,

COMPUTE aEAf IEftff TO LACI CMMht'. [

y tutAf) i I tivet av tavat sowtion l 1 l poa metssues cmanus se au Catts {

3%W EMEIG7 IQUAflGd FCR NEW ENTML71 (thERGT) meassuas efftartD4

% CO8ewt4GED dt;H ...

FIs. x +

7 sava nvA.p.,.mst wmconstavatlee euen.

C:yyutt Ogustff 00iOM10C) [ uposts peasksAqs ea0 8kOw9 l g } we au ttus l u t. i.u va,w weiw easy w;-m..sn sauma =o

$1 co>m, acro vis nefung l l Figure ,iM H b RECIRC Solution Sequence, wih ddn flux Worle) t.1 - 1 1

2 23 " -( SCvi;i^" 2) '

j

Retrieved from "https://kanterella.com/w/index.php?title=ML20090M295&oldid=2795359"