documentation of the sourceinfo/i software …documentation of the sourceinfo/i software package in...

Documentation of the SourceInfo/I software package inRODOS PV4.0F2 (interactive operation mode)

(Draft) RODOS(RA1)-TN(01)-01

C. Landman

ForschungszentrumKarlsruheTechnik und Umwelt

P.O.Box 3640, D-76021 KarlsruheEmail: [email protected]

December 7, 2001

Documentation of the SourceInfo/I software package in RODOS PV4.0F2 (interactive operation mode) (Draft) RODOS(RA1)-TN(01)-01

draft - 2 - 7.12.2001

Management SummaryThe interactive operation mode of RODOS shall serve in real emergency situations aswell as for training and exercises. With respect to the source term input this means thatRODOS must be able to deal with frequently used data formats and parametrisations inorder to make adaptations to real or fictive scenarios as easy as possible. The source terminterface for other programs of RODOS, however, should not depend on the particularformat of the source term specification. Such a uniform source term interface is pro-duced by the software package SourceInfo/I of RODOS, which also provides a data pro-tocol with source term information for the user.

This document is part of the RODOS system documentation.


draft - 3 - 7.12.2001

Contents

Documentation of the SourceInfo/I software package in RODOS PV4.0F2 (interactive opera-tion mode) 1

1 General Information and Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1.1 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1.2 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1.3 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2.1 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2.2 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2.3 Proposed Methods and Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.3 Development Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2 Operation Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.1 Program Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.2 Description of Operation Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.3 Connections to Other RODOS Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.4 Help Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3 Functional Specification and Data Specification Documents . . . . . . . . . . . . . . . . . . . . 13 3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.1.1 Software Organisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.1.2 Program Inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.1.3 File Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.2 Data and Interface Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2.1 Input Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2.2 Output Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.2.3 Description of the SourceInfo/I Shared Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.2.3.1 Shared Memory Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.2.3.2 Archiving and Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.2.3.3 Assignment of Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3.3 Module description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.4 Description of Runs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4 Program Maintenance, Integration and Test Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 4.1 Operating Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4.1.1 Program Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.1.2 Programming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.1.3 Support Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4.2 Maintenance Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.2.1 Verification Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.2.2 Error Correction Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4.2.2.1 Runtime Errors Probably Not Caused by User Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 4.2.2.2 Runtime Errors Probably Caused by User Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.3 Test Plan and Test Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25


draft - 4 - 7.12.2001

4.3.1 Tests for Task SETSRC - Setup of Source Term. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 4.3.1.1 Test Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 4.3.1.2 Test Analysis Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4.3.2 Tests for Task SETRLG - Setup of Release Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274.3.3 Tests for Task SETCHN - Setup of Decay Chains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274.3.4 Tests for Task SETINV - Setup of Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274.3.5 Tests for User Input via Initialisation Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274.3.6 Tests for Permanent Input Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

5 Model Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 5.2 Checks and Modifications of Input Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

5.2.1 Start of Initial Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.2.2 Height of Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.2.3 Release Thermal Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305.2.4 Fractions of Elementary, Organically Bound, and Aeosol Iodine. . . . . . . . . . . . . . . . . . . 30

5.3 Nuclides in SourceInfo/I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 5.4 Calculation of Activity Release Rates for Source Term Input Modes F/ST1 to F/ST5 .

315.4.1 General Formalism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315.4.2 Application of General Formalism for Source Term Input Mode F/ST1 . . . . . . . . . . . . . 335.4.3 Application of General Formalism for Source Term Input Mode F/ST5 . . . . . . . . . . . . . 345.4.4 Application of General Formalism for Source Term Input Mode F/ST4 . . . . . . . . . . . . . 345.4.5 Application of general formalism for source term input mode F/ST3 . . . . . . . . . . . . . . . 355.4.6 Remark on Using the Calculation Nuclides When Applying Equation 4 . . . . . . . . . . . . . 355.4.7 Calculation Flow, Possible Release Time Steps and Release Groups . . . . . . . . . . . . . . . . 36

5.5 Setup of Nuclide Release Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 5.6 Setup of Decay Chains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 5.7 Setup of Inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 5.8 Description of Source Term Data Protocol for the User. . . . . . . . . . . . . . . . . . . . . . . 39

6 Appendix A : Description of the Release Group File <in.releasegroups> . . . . . . . . . . 41 6.1 File Syntax and Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 6.2 File Maintenance and Tests for Contents of File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

7 Appendix B : Description of the Decay Chain Data File <in.decaychains> . . . . . . . . . 44 7.1 File Syntax and Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 7.2 File Maintenance and Tests for Contents of File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

8 Appendix C: Description of the Source Term Entry Mode "File" . . . . . . . . . . . . . . . . 47 8.1 File Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 8.2 Input Mode Dependent Data - Source Term Input Mode FT1 . . . . . . . . . . . . . . . . . . 49 8.3 Input Mode Dependent Data - Source Term Input Modes FT3 and FT4 . . . . . . . . . . 50 8.4 Input Mode Dependent Data - Source Term Input Mode FT5 . . . . . . . . . . . . . . . . . . 52 8.5 Input Mode Dependent Data - Source Term Input Modes FT6 and FT7 . . . . . . . . . . 53 8.6 Use of Source Term Output Files <FT6.STERMout> and <FT7.STERMout> as Input

Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54


draft - 5 - 7.12.2001

9 Appendix D: Description of an Inventory Data File. . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

10 Appendix E: Description of the Aerosol Fraction Library File <in.aerosolfractions> .59

11 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61


draft - 6 - 7.12.2001

List of Figures

Fig. 1 on p. 15 : Tasks, program flow and subroutines in SourceInfo/IFig. 2 on p. 31 : Time axis for source term calculations with SourceInfo/I

List of Tables

Table 1 on p. 10 : Source term input in entry mode "Standard" (interactive operation mode)Table 2 on p. 11 : Source term input in entry mode "File" (interactive operation mode)Table 3 on p. 14 : Calling of SourceInfo/I file read routines in entry mode "File"Table 4 on p. 14 : Calling of SourceInfo/I steering routinesTable 5 on p. 16 : Program inventory of SourceInfo/ITable 6 on p. 18 : File inventory of SourceInfo/I (permanent files)Table 7 on p. 18 : Input for SourceInfo/ITable 8 on p. 20 : Output from SourceInfo/ITable 9 on p. 23 : Archive/load requirements for SourceInfo/ITable 10 on p. 24 : Support software used by SourceInfo/ITable 11 on p. 25 : Test cases for task SETSRC of SourceInfo/ITable 12 on p. 37 : Nuclide release groups provided by defaultTable 13 on p. 42 : The release group data file <in.releasegroups>Table 14 on p. 44 : The decay chain data file <in.decaychains>Table 15 on p. 48 : File header of a SourceInfo/I source term fileTable 16 on p. 50 : Input Mode Dependent Data - Source Term Input Mode FT1Table 17 on p. 51 : Input Mode Dependent Data - Source Term Input Modes FT3, FT4Table 18 on p. 52 : Input Mode Dependent Data - Source Term Input Mode FT5Table 19 on p. 54 : Input Mode Dependent Data - Source Term Input Modes FT6 and FT7Table 20 on p. 57 : Structure of an inventory fileTable 21 on p. 60 : Structure of file <in.aerosolfractions>

List of Equations

Equation 1 on p. 32 : Radioactive decay and decay chain contributionsEquation 2 on p. 33 : Activity released from and activity remaining in reactorEquation 3 on p. 33 : Derived release fractions for source term input mode F/ST1Equation 4 on p. 34 : Derived release fractions for source term input mode F/ ST5Equation 5 on p. 40 : Calculation of the activity inventory at the end of the chain reaction


draft - 7 - 7.12.2001

1 General Information and Overview

1.1 General Information

1.1.1 Summary

The SourceInfo/I software (Source Term Information/Interactive Mode) is part of the "Real-time Online Decision Support System" RODOS which is under development under collaborationof different institutes in many countries of the European Union and also from other countries.This system provides information on the radiological situation to decision makers or their ad-visors in the case of accidental releases from nuclear installations. Its application is possible forthe near, intermediate and far distant ranges and for the short- and longterm radiological situation.

The SourceInfo/I software provides unified information about the source term and a unifiedsource term interface independent of the input mode of the source term for the interactiveoperation mode of RODOS. As support software, SourceInfo/I is also used in the automaticoperation mode of RODOS.

In the frame of the RODOS system, SourceInfo/I is part of the Analysing Subsystem ASY. Italso exists as a self-consistent stand-alone program.

1.1.2 Environment

SourceInfo/I is developed at the Institut für Kern- und Energietechnik of the ForschungszentrumKarlsruhe (FZK/IKET).

1.1.3 References

[DRSA1981] Gesellschaft für Reaktorsicherheit: Deutsche Risikostudie Kernkraftwerke. Fach-band 8, Unfallfolgerechnungen und Risikoergebnisse. Verlag TüV Rheinland, ISBN 3-88585-019-2 (1981).

[EVAN1955] R.D. Evans, The Atomic Nucleus. Mc.Graw-Hill Book Co., New York (1955),Tenth Printing September 30, 1965.

[LEIT1995] Leitfaden für den Fachberater Strahlenschutz der Katastrophenschutzleitung beikerntechnischen Notfällen. Veröffentlichungen der SSK, Band 13, 2. Aufl. (1995), ISBN 3-437-11639-8.

[KOCH1981] D.C.Kocher: Radioactive Decay Data Tables. DOE/TIC-11026, U.S. Departmentof Energy (1981).

Referenced RODOS documentation (unpublished reports, available at FZK/IKET)

[Prognosis USER GUIDE] User Guide of the Prognosis Models in RODOS-PV4.0F

[RODOS(WG1)-TN(96)-11] C. Steinhauer, Documentation of the NucInfo software packagein RODOS/RESY PV3.11.

[RODOS(RA7)-TN(00)-01] C. Landman, Scanario data sets and scenarios for RODOS.

[RODOS(RA1)-TN(00)-02] C. Landman, Documentation of the SourceInfo/ A software pack-age in RODOS PV4.0F.

1. No changes in in current RODOS version with respect to the reference.


draft - 8 - 7.12.2001

1.2 Overview

1.2.1 Background

The interactive operation mode of RODOS shall serve in real emergency situations as well asfor training and exercises. With respect to the source term input this means that RODOS mustbe able to deal with frequently used data formats and parametrisations in order to make adap-tations to real or fictive scenarios as easy as possible. The source term interface for other programsof RODOS, however, should not depend on the particular format of the source term specification.Such a uniform source term interface is produced by the software package SourceInfo/I ofRODOS, which also provides a data protocol with source term information for the user.

1.2.2 Objectives

The objectives of the SourceInfo/I software are to provide by means of one single programpackage a uniform source term interface for other programs, independent of the input mode ofthe source term, and text information about the source term for the user, in the interactive oper-ation mode of RODOS.

1.2.3 Proposed Methods and Procedures

- none -

1.3 Development Plan

There existed no development plan. The SourceInfo/I software was written "top to bottom" in1996 and is in use within RODOS since then. Apart from general modifications due to codemaintenance, the following changes were made on request of users:

(1998) New source term entry mode "File".

(1998) Change of activity release interface from "Bq released in the time interval" to "releaserate in the time interval".

(1999) New input mode FT7.

(2000) Output of source term as files <FT6.STERMout> and <FT7.STERMout>. Former inputmode ST2 replaces former ST1 mode; ST2 becomes defunct. Input mode F/ ST4 gets newmeaning (possibility to put in aerosol fractions). New parameter in file <in.releasegroups> tocope with the aerosol fraction input facility.

(2001) Re-definition of input mode 3 (iodine131 instead of total iodine, total aerosols insteadof cesium137, possibility to put in aerosol fractions).


draft - 9 - 7.12.2001

2 Operation Manual

2.1 Program Description

For a computation of the radiological situation with RODOS, the following information is re-quired with regard to the source term and is input to SourceInfo/I:

• Start of initial release.

• Height of release as a function of time.

• Released thermal power as a function of time.

• Released activity as a function of time.

• Fractions of elementary iodine, organically bound iodine and iodine aerosols of total iodinereleased (“iodine fractions”) as a function of time.

One of the tasks of SourceInfo/I is to check all incoming data for consistency. With respect tothe start of the initial release, the release height, the released thermal power, and the iodinefractions, there is only one input format for specifying these informations. For the releasedactivity several different formats are possible which cover a large range of user needs. Onecomplete set of source term data containing all above input items is called source term inputmode in the following.

In the interactive operation mode of RODOS, there are two possible ways, or entry modes, toenter source terms into the system:

• Source term entry mode "Standard" : Via source term data sets contained in the FixDatabase of RODOS, or by user input via the RODOS initialisation windows, or from RODOS as-sign files.

• Source term entry mode "File" : Via data files which are read by SourceInfo/I.

The entry mode "Standard" allows to make full use of the RODOS system facilities such aseditors, initialisation windows etc. for manipulating the data. The specifications of the releasedactivity, however, are strictly limited to the currently five pre-defined input modes shown inTable 1 on p. 10.

The input modes in the entry mode "File" are shown in Table 2 on p. 11. Mode FT6 is identicalwith the entry mode "Standard" counterpart. With file modes FT1, FT3, FT4, and FT5, however,it is possible to make full use of the SourceInfo/I capability of dealing with activity releasespecifications for nuclide groups of practically any definition and composition. Their "Standard"counterparts ST1, ST3, ST4, ST5 are only one special realisation of such a nuclide group pa-rameterisation. The input of activity release rates is currently (by technical reasons) only possiblein the "File" mode FT7.

For SourceInfo/I there is no difference whether the source term comes from file or from elsewhereonce the corresponding file was read and processed.

As can be seen from Table 1 and Table 2, input modes 6 and 7 specify the activity release interms of individual nuclides, whereas input modes 1 to 5 give these data in terms of groupsof nuclides or individual nuclides representing groups of nuclides. In all cases, SourceInfo/Iproduces one nuclide-specific release rate array for use by other programs in RODOS.


draft - 10 - 7.12.2001

Table 1 : Source term input in entry mode "Standard" (interactive operation mode)

Mode Description1)

ST1 Fractions ([%]) of the initial core inventory released for the nuclide release

groups3)

• noble gases• iodine• alkaline metals• tellurium and selenium• alkaline earths• ruthenium group (e.g. Ru, Rh, Mo, Tc)• lanthanides (e.g. Y, La, Zr, Nb, Ce, Pr, Np, Pu, Am, Cm)

ST2 - at present not used -

ST3 Released activity ([Bq]) for the sum of calculation nuclides2) in the nuclide re-lease groups noble gases and total aerosol, and for the individual nuclide I-131,together withrelease fractions for the nuclide release groups3) alkaline metals / tellurium andselenium / alkaline earths / ruthenium group /lanthanides.

ST4 Released activity ([Bq]) for the sum of calculation nuclides2) in the nuclide re-lease groups noble gases, iodine, total aerosol,together with

release fractions for the nuclide release groups3) alkaline metals / tellurium andselenium / alkaline earths / ruthenium group /lanthanides.

ST5 Released activity ([Bq]) for the sum of calculation nuclides in the nuclide re-

lease groups2) listed for ST1.

ST6 Released activity ([Bq]) for individual nuclides.

Notes1) The formats for specifying the start of initial release, the release height, the released ther-

mal power and the iodine fractions are the same for ST1-ST6.2) Calculation nuclides are the subset of 1 to 15 nuclides from all possible nuclides selected

for a run. If, for instance, a release of 10E18 Bq is specified for the noble gas group, the re-sults will be different when Kr- 88 only or Kr- 88, Xe-133, Xe-135 were selected as calcu-lation nuclides.


draft - 11 - 7.12.2001

The complete output source term interface for other programs consists of the following infor-mation:

• Start of release.

• Height of release as a function of time.

• Released thermal power as a function of time.

• Activity release rates as a function of time.

• Fractions of elementary iodine, organically bound iodine and iodine aerosols of total iodinereleased (“iodine fractions”) as a function of time.

In addition, SourceInfo/I generates a textfile for the user which contains information about the

Table 2 : Source term input in entry mode "File" (interactive operation mode)

Mode Description1)

FT1 Fractions ([%]) of the initial core inventory released for user-definable nuclide

release groups2).

FT2 - at present not used -

FT3 Released activity ([Bq]) for the sum of calculation nuclides2) in the nuclide re-lease groups noble gases and total aerosol, and for the individual nuclide I-131,together withrelease fractions for user-definable aerosol release groups2).

FT4 Released activity ([Bq]) for the sum of calculation nuclides2) in the nuclide re-lease groups noble gases, iodine, total aerosol,together with

release fractions for user-definable aerosol release groups2).

FT5 Released activity ([Bq]) for the sum of calculation nuclides2) in user-definable

nuclide release groups2).

FT6 - as ST6 in Table 1 -

FT7 Activity release rate ([Bq/s]) for individual nuclides

Notes1) The formats for specifying the start of initial release, the release height, the released ther-

mal power and the iodine fractions are the same for FT1-FT7.2) The definition of the nuclide groups must be contained in file <in.releasegoups>. The nu-

clide release groups provided by default in this file are shown in Table 12 on p. 37.3) Calculation nuclides are the subset of 1 to 15 nuclides from all possible nuclides selected

for a run. If, for instance, a release of 10E18 Bq is specified for the noble gas group, the re-sults will be different when Kr- 88 only or Kr- 88, Xe-133, Xe-135 were selected as calcu-lation nuclides.


draft - 12 - 7.12.2001

user input and the generated output..

2.2 Description of Operation Modes

The SourceInfo/I software was originally developped for the interactive operation mode of RO-DOS. As support software, SourceInfo/I is used in the automatic operation mode of RODOS[RODOS(WG1)-TN(00)-01].

It also exists as a self-consistent stand-alone program.

2.3 Connections to Other RODOS Software

At present, the SourceInfo/I software is part of the RODOS program PROGNOSIS (and, assupport software, also of the RODOS program DIAGNOSIS) of the analysing subsystem ASY.The information generated by SourceInfo/I is kept in special sections in shared memory and isaccessible for all RODOS programs containing the corresponding sections, either directly, afterthe information was generated by SourceInfo/I, or indirectly, in RODOS programs other thanDIAGNOSIS or PROGNOSIS after the corresponding shared memory sections have been filledusing load instructions for the respective archived information.

2.4 Help Functions

Help functions are neither available nor foreseen. For trouble-shooting see Chapter 4.2.2.


draft - 13 - 7.12.2001

3 Functional Specification and Data Specification Documents

In this chapter, program, subroutine and variable names are written in capital letters, file namesare written in italics between the brackets <>. The numbering of the source term input modesis the one from Table 2 on p. 11.

3.1 Overview

3.1.1 Software Organisation

SourceInfo/I is a package of FORTRAN subroutines. Figure 1 on p. 15 shows the tasks,program flow and subroutines.

The main steering subroutine SETQTR analyses the incoming information and calls the steeringsubroutines for the respective subtasks. SETQTR itself is called from the PROGNOSIS or theDIAGNOSIS module of ASY of RODOS.

The source term entry mode is characterised by the values of a flag array named ISTFIL. Thesource term input mode is characterised by the values of a flag array named IRLTYP.

In source term entry mode "File", which is characterised by ISTFIL=(0,1), a corresponding filemust be read prior to any further action. This is done by the subroutines SETQT_READ0 ...SETQT_READ_FT67; the detailed calling arrangement is shown in Table 3 on p. 14. Aftersuch files were read and processed, there is no longer any difference between the modes "Stand-ard" and "File".

For each source term input mode, there is a corresponding steering subroutine; the correspondingvalues of array IRLTYP and the calling arrangement is shown in Table 4 on p. 14.

Only input modes F/ST6 and FT7 (input for individual nuclides) do not require preparatoryactions, and the corresponding source term setup routines SETQT6 or SETQT7 are calleddirectly.

For all other input modes, the activity release data refer to groups of nuclides or individualnuclides representing groups of nuclides. In this case, the nuclide-specific release rates requiredfor RODOS will be generated by SourceInfo/I using the following additional information:

• composition of release groups;

• decay chains for the nuclides considered;

• nuclides-specific activity inventory of the reactor under consideration.

As it can be seen in the figure, this information is provided by the subroutines belonging to thetasks called "SETRLG" (SETup of Release Groups), "SETCHN" (SETup of decay CHaiNs)and "SETINV" (SETup of INVentory).

When all above information is set up, the source term setup steering routines SETQT1, SETQT3,SETQT4, or SETQT5 of task "SETSRC" (SETup of SouRCe term2) are called, respectively.These subroutines call other lower level subroutines, which are also shown in Figure 1.

In addition, there are auxiliary routines called for all source term input modes (SETQT_PRINT

2. Source term in German is "Quellterm", which explains the names SETQT... chosen by the Germanspeaking programmer.


draft - 14 - 7.12.2001

and its lower level subroutines), or by some of them (SETQT_ERROR; RDCHRS, RDECAY,EHOCHX,UERROR_MESSAGE, UERROR_RETURN, UERROR_STOP). They performauxiliary tasks which are summarised in Table 5 on p. 16. All the auxiliary routines are omittedin Figure 1.

When the source term is set up, finally a subroutine SETQT_OUTF67 (not shown in Figure 1)is called from the steering routine SETQTR, which writes two files, <FT6.STERMout> and<FT7.STERMout>. These files contain the source term in entry mode formats FT6 and FT7and can be used as source term input files for RODOS. This facility is helpful for scenariodevelopment.

Table 3 : Calling of SourceInfo/I file read routines in entry mode "File"

subroutine steering parameter ISTFIL=(0,1) and ...source term in-put mode

read data in file header

SETQT_READ0 --- all F-modes

read data which depend on source term input mode

SETQT_READ_TF15 IRLTYP(1)=1 or IRLTYP(5)=1 (all other elements zero) FT1 and FT5

SETQT_READ_FT34 IRLTYP(4)=1 or IRLTYP(3)=1 (all other elements zero) FT4

SETQT_READ_FT67 IRLTYP(6)=1 or IRLTYP(7)=1 (all other elements zero) FT6 and FT7

Table 4 : Calling of SourceInfo/I steering routines

subroutine steering parametersource term in-put mode

SETQT1 IRLTYP(1)=1 (all other elements zero) F/ST1





SETQT7 IRLTYP(7)=1 (all other elements zero) FT7


draft - 15 - 7.12.2001

Figure 1: Tasks, program flow and subroutines in SourceInfo/I

SETQTR

SETCHN

Task SETCHN : SETUP OF DECAY CHAIN INFORMATION

Task SETINV : SETUP OF INVENTORY

Task SETSRC : SETUP OF SOURCE TERM

SETCH1 SETCH2 SETCH3

SETQT1

RDCHRS

RDEDAY

EHOCHX

Steering Routine

Task SETFIL - READ DATA FROM FILE

SETRLG

Input from file

Task SETRLG - SETUP OF RELEASE GROUPS

SETQT6

SETINV SETINV_READ SETINV_PRINT

_START_WORK

_CLOSE

SETQT7

SETQT5_START

_WORK_CLOSE

SETQT3

- see Table in text -

see

Table

in text

SETQT4

_NOREL

SETQT

_PRIN0 to_Prin6

_PRINT

SETQT

_ERROR

_START_WORK

_CLOSE

_START_WORK

_CLOSE


draft - 16 - 7.12.2001

3.1.2 Program Inventory

Table 5 shows the program inventory belonging to SourceInfo/I. The support software used bySourceInfo/I is described in Chapter 4.1.3.

Table 5 : Program inventory of SourceInfo/I

file1) content type /task

Include-Files

PAR_QTERM PAR_QTERM Include-file with parameter statements (uses also include filePAR_NUCLS of program package NucInfo)

SHM_QTERM SHM_QTERM Include-file for shared memory

Main STEERING ROUTINE

setqtr.ff SETQTR STEERING ROUTINE

Task SETSRC - SETUP OF SOURCE TERM

setqtr.ff SETQT1SETQT1_STARTSETQT1_WORKSETQT1_CLOSE

MODE FT1:USER INPUT ARE RELEASE FRACTIONS FOR RELEASEGROUPS


MODE FT3:USER INPUT IS ACTIVITY SUM RELEASED FOR NOBLE GAS-ES AND TOTAL AEROSOL AND ACTIVITY RELEASED FOR I-131 TOGETHER WITH AEROSOL RELEASE FRACTIONS.


MODE FT4:USER INPUT IS ACTIVITY SUM RELEASED FOR NOBLE GAS-ES, IODINE, AEROSOLS TOGETHER WITH AEROSOL RE-LEASE FRACTIONS.


MODE FT5:USER INPUT IS ACTIVITY RELEASED FOR RELEASEGROUPS.

setqtr.ff SETQT6 MODE FT6:USER INPUT IS ACTIVITY RELEASED FOR NUCLIDES

setqtr.ff SETQT7 MODE FT7:USER INPUT IS ACTIVITY RELEASE RATE FOR NUCLIDES

setqtr.ff SETQT_AERFRA SETUP OF AEROSOL-FRACTIONS FROM USER-INPUT.

setqtr.ff SETQT_AERPRI PRINTOUT OF AEROSOL FRACTIONS

setqtr.ff SETQT_ERROR LENGTHY MESSAGE FOR A PROBLEM CAUSED BY INPUTSPECIFICATION OF RELEASED AVTIVITY

setqtr.ff SETQT_NOREL SET FLAG FOR TIME STEPS WITHOUT RELEASE.

1) Extension .f: FORTRAN source code. Extension .ff: FORTRAN source code plus specially coded language-dependent lines; must be processed with "Language.awk" instructions before compiling.


draft - 17 - 7.12.2001

setqtr.ff SETQT_PRINTSETQT_PRIN0SETQT_PRIN1SETQT_PRIN2SETQT_PRIN3SETQT_PRIN4SETQT_PRIN5SETQT_PRIN6

CHECKS AND PRINTPRINT HEADER LINESPRINT RELEASE GROUP INFORMATIONPRINT ANJOD, HFS AND QH / CHECKS OF DATAPRINT RELEASED ACTIVITY FOR NUCLIDE GROUPSPRINT RELEASED ACTIVITY FOR NUCLIDESPRINT RELEASED ACTIVITY RATE FOR NUCLIDESSTOP RUN IF THERE IS NO RELEASE

setqtr_auxi.f EHOCHX EXPONENTIAL WITH AVOID OF UNDER/OVER-FLOW

setqtr_auxi.f RDECAY CALCULATION OF ACTIVITY WITH RADIOACTIVE DECAY/BUILDUP

setqtr_auxi.ff RDCHRS RADIOACTIVE DECAY CONSTANTS ("ISO"-NUCLIDES) INHOURS

Task SETSRC - SETUP OF SOURCE TERM - Subtask FILE INPUT/OUTPUT

setqtr_read.ff SETQT_READ0 READ SOURCE TERM FROM FILE -> FILE HEADER DATA

setqtr_read.ff SETQT_READ_FT15 READ SOURCE TERM FROM FILE -> MODES FT1, FT5

setqtr_read.ff SETQT_READ_FT34 READ SOURCE TERM FROM FILE -> MODEs FT3, FT4

setqtr_read.ff SETQT_READ_FT67 READ SOURCE TERM FROM FILE -> MODES FT6, FT7

setqtr_read.ff SETQT_OUTF67 FILE OUT PUT OF SOURCE TERM -> FORMATS FT6 AND FT7

setqtr_read.ff SETQT_READ_ANTAER

READ FILE WITH AEROSOL-FRACTION-LIBRARY

Task SETRLG - SETUP OF RELEASE GROUPS !!! MUST BE CALLED FIRST !!!

setrlg.ff SETRLG SETUP OF RELEASE GROUPS

Task SETCHN - SETUP OF DECAY CHAIN INFORMATION !!! NEEDS SETRLG !!!

setchn.ff SETCHN READ AND DECODE DECAY CHAIN DATA

setchn.ff SETCH1 CHECK CONTINUATION CARD CODE

setchn.ff SETCH2 MARK NUCLIDE AS SELECTED AND BUILD UP TEMPORARYMOTHER LIST

setchn.ff SETCH3 BUILD UP FINAL MOTHER LIST

Task SETINV - SETUP OF INVENTORY !!! NEEDS SETRLG AND SETCHN !!!

setinv.ff SETINV MAKE INVENTORY A0ISO FOR POWER IANLEI AND BURN-UP IANTGE

setinv.ff SETINV_READ READ INVENTORY FROM FILE

setinv.ff SETINV_PRINT PRINT INVENTORY INFORMATION

General Auxiliary Subroutines





draft - 18 - 7.12.2001

3.1.3 File Inventory

SourceInfo/I uses the three permanent data files shown in Table 6.

In addition to above files, files with inventory data and/or files with the source term data maybe read from directory ~rodos/roextern/data/sourceterm/input/.

3.2 Data and Interface Description

3.2.1 Input Data

Table 7 shows the input for SourceInfo/I (1st column), where the information comes from (2ndcolumn), and where it resides (3rd column).

uerror.ff UERROR_MESSAGE

MESSAGE (FILE) TO INDICATE THAT AN ERROR HAS HAP-PENED.

uerror.ff UERROR_RETURN MESSAGE (RODOS SCREEN) TO LOOK INTO <OUTALL>, FOL-LOWED BY RETURN.

uerror.ff UERROR_STOP MESSAGE (RODOS SCREEN) TO LOOK INTO <TERMLOG>,FOLLOWED BY STOP.

Table 6 : File inventory of SourceInfo/I (permanent files)

directory = ~rodos/roextern/data/sourceterm/setup/file name =

content

in.decchain decay chains definition data

in.releasegroups release groups definition data

in.aerosolfractions aerosol fractions data library

Table 7 : Input for SourceInfo/I

input coming from residing in

general information

input/output logical unit numbers for messag-es/text

calling subroutine argument list

information about FixData nuclides NucInfo program package shared memory

information about calculation nuclides NucInfo program package shared memory





draft - 19 - 7.12.2001

steering flags for source term entry and inputmode; inventory input mode

FixData base or initialisation windowor assign editor

shared memory

Task SETSRC - SETUP OF SOURCE TERM - Subtask FILE INPUT OR OUTPUT

source term file name initialisation window or assign editor shared memory

Task SETSRC - SETUP OF SOURCE TERM - all source term input modes

source term input data FixData base or initialisation windowor assign editor or data file

shared memory

length of release time interval (Prognosis) assign file shared memory

Task SETSRC - SETUP OF SOURCE TERM - input mode F/ST3/4

aerosol fractions Initialisation window or assign editoror data file

shared memory

Task SETSRC - SETUP OF SOURCE TERMall source term input modes except the mode "input of activity released for individual nuclides"

information about which nuclides shall be con-sidered for source term calculations

task SETRLG SourceInfo/I COM-MON blocks

information about decay chains task SETCHN SourceInfo/I COM-MON blocks

information about inventory task SETINV SourceInfo/I COM-MON blocks

Task SETRLG - SETUP OF RELEASE GROUPS

directory path for data file RODOS system shared memory

release group data data file <in.releasegrps> permanent file

Task SETCHN - SETUP OF DECAY CHAIN INFORMATION

directory path for data file RODOS system shared memory

decay chains data data file <in.decchain> permanent file



Task SETINV - SETUP OF INVENTORY

inventory data file INVE.{name of inventory} shared memory

name of inventory (variable BlockInve)a FixData base SourceInfo/I COM-MON blocks

power plant block power and burn-up days(variables IANLEI, IANTGE)

FixData base shared memory

information about decay chains task SETINV SourceInfo/I COM-MON blocks



Table 7 : Input for SourceInfo/I

input coming from residing in


draft - 20 - 7.12.2001

3.2.2 Output Data

Table 8 on p. 20 shows the input for SourceInfo/I (1st column), where the information comesfrom (2nd column), and where it resides (3rd column).

3.2.3 Description of the SourceInfo/I Shared Memory

The source term, nuclide, power plant and inventory input variables for SourceInfo/I and all ofthe output interface variables reside in shared memory. In RODOS, the instructions for definingthe shared memory, the loading of variables into it or archiving of variable values from it, andof assigning values to shared memory variables are contained in separate files for differentprograms. Because SourceInfo/I is not a RODOS program of its own, the corresponding state-ments or instructions are not contained in files of their own, but must be included in the corre-sponding files of any program which executes the NucInfo software or wants to make use of thecorresponding archived data.

3.2.3.1 Shared Memory Definition

The variables are grouped into data classes (example "DSTRM0"), which represent FORTRAN

a. At present, the name of the inventory which belongs to a power plant block (variable BlockInve) isread from a file <~rodos/roextern/data/sourceterm/setup/in.inventory.configurations>, and the nameinformation is kept in an internal SourceInfo/I COMMON block. It is planned to include the name in theRODOS FixData base and in the shared memory. The file <in.inventory.configurations> is not descri-bed in this document.

Table 8 : Output from SourceInfo/I

output coming from residing in

shared memory interface for other programs

DRLSPM: length of release time interval (Prog-nosis)

assign file shared memory

BEGFRE : Start of release relative to timezero ="end of chain reaction" (half-hour resolution)

input data (eventually modifiedby task SETSRC

shared memory

HFS : Release height for 24 half-hour intervals input data (eventually modifiedby task SETSRC)

shared memory

QH : Thermal power released for 24 half-hour in-tervals

input data shared memory

ANTJOD : Percent fractions of iodine element./org.bound/aerosol to total iodine for 24 half-hourintervals

input data (eventually modifiedby task SETSRC)

shared memory

ARRATE : Activity release rate of individual nu-clides for 24 half-hour intervals

calculated by task SETSRC shared memory

for information of user

file with text information about the source term written by task SETSRC temporary file


draft - 21 - 7.12.2001

common blocks. The definition of each variable consists of two lines:

• the first line contains the name of the variable, the dimensions of the array, the type of thevariable, upper and lower range for the values of the variable ("(0:0)" means that no ranges areset), and the physical unit;

• the second line contains a description of the variable.

The variables for SourceInfo/I are distributed over several data classes. The necessary definestatements are listed below; details are given only for those data classes which are specific forSourceInfo/I. The shared memory sections referring to FixData nuclides and calculation nuclidesare filled with data set up by program package NucInfo and are described in detail in [RO-DOS(WG1)-TN(96)-11].

Statements for FixData nuclides - input only

Data classes CNUKSD and DNUKSD; for details see a corresponding define file.

Statements for calculation nuclides - input only

Data classes CNUKPD and DNUKPD; for details see a corresponding define file.

Statements for power plant data - input only

Data classes CANLAG and DANLAG; for details see a corresponding define file.

Statements for source term - input only DSTRM0: ACS137 [1:24] Real (0:0) Bq '*** no longer in use ***'; AI131 [1:24] Real (0:0) Bq 'Activity released (I-131) for 24 time intervals'; ARBQ3 [1:24][1:3] Real (0:0) Bq 'Activity released (3 groups) for 24 time intervals'; ARBQ7 [1:24][1:7] Real (0:0) Bq 'Activity released (7 groups) for 24 time intervals'; ARISO [1:24][1:68] Real (0:0) Bq 'Activity released (nuclides) 24 time intervals'; ARNOB [1:24] Real (0:0) Bq '*** no longer in use ***'; IAEMOD [1:2] Integer (0:1) --- ’Aerosol fraction input via shared memory (1,0) or from file (0,1); IRLGRP [] Integer (3:7) --- 'Number of release groups'; IRLTYP [1:12] Integer (0:1) --- 'Indicator flag for source term input type';

ISTFIL [1:2] Integer (1:1) --- 'Source term input via shared memory (1,0) or from file (0,1)'; PROZF3 [1:24][1:3] Real (0:0) Prozent '*** no longer in use ***'; PROZF7 [1:24][1:7] Real (0:0) Prozent 'Activity release fractions (7 groups) for 24 intervals'; ZDSTR0 [] Real (0:0) --- '8-Byte-Lueckenfueller';


draft - 22 - 7.12.2001

END CLASS

Statements for source term - input/output or output only (latter marked by *) CSTRMX: CAEBLK [1:16] Char (0:0) --- 'Release group specifier for aerosol fractions'; CAECAT [1:16] Char (0:0) --- 'Release category specifier for aerosol fractions'; COMFR1 [1:80] Char (0:0) --- 'Comment on the source term data (line 1)'; COMFR2 [1:80] Char (0:0) --- 'Comment on the source term data (line 2)'; CRLGID [1:16] Char (0:0) --- 'Release group specifier'; CSTFIL [1:16] Char (0:0) --- 'Filename when source term input from file'; END CLASS DSTRMX: ANTAER [1:16] REAL (0:0) percent 'Aerosol fractions (fraction of 1)'; BEGFRE [] Real (0:0) h 'Begin of initial release relative to end of chain reaction'; ZDSTRX [] Real (0:0) --- '8-Byte-Lueckenfueller'; END CLASS DSTRMP: ANTJOD [1:24][1:3] Real (0:0) percent 'Percent of elem./org./aerosol iodine for each release time intervals (sum=100%)'; * ARRATE [1:15][1:24] Real (0:0) Bq/s 'Release rate for each release time interval (NNUKL nuclides)'; DRLSPM [] Real (0:0) min 'Length of release time interval (Prognosis)'; HFS [1:24] Real (0:0) m 'Release height for each release time interval'; QH [1:24] Real (0:0) MW 'Thermal power released for each release time interval'; ZDSTRP [] Real (0:0) --- '8-Byte-Lueckenfueller'; END CLASS

3.2.3.2 Archiving and Loading

Table 9 lists the SourceInfo/I data classes which need archiving/loading in dependence of theRODOS programs. The corresponding instructions are not listed here; they will be provided bythe RODOS support team when required.

3.2.3.3 Assignment of Data

As can be seen from Table 7 on p. 18, input for the source term and inventory can be given va-lues with the RODOS assign editor.


draft - 23 - 7.12.2001

3.3 Module description

As SourceInfo/I is not a RODOS module on its own right and consists only of relatively fewsubroutines and tasks, no further detailes than those already given in Chapter 3.1 are provided.

3.4 Description of Runs

None. For test runs see Chapter 4.3.

Table 9 : Archive/load requirements for SourceInfo/I

program data classes to be archived data classes to be loaded

PROGNOSIS(interactive mode)

CSTRMX (COMFR1 & COMFR2)DSTRMX and DSTRMP (complete)

complete shared memory as de-scribed in Chapter 3.2.3.1

all other programs - nothing - as necessary, for exampleCNUKPD and DNUKPD.


draft - 24 - 7.12.2001

4 Program Maintenance, Integration and Test Plan

4.1 Operating Environment

4.1.1 Program Language

SourceInfo/I is written in FORTRAN 77. Program development was on a HP Workstation Series9000-7xx with UNIX operation system HPUX-10.20 and HPUX F77 compiler.

Some extensions to standard FORTRAN 77 have been used:

• FORTRAN include statements for including files with definitions of parameters, variables etc.;

• the statement IMPLICIT NONE

• names can be longer than 6 characters;

• in a few places, lower case characters are used.

4.1.2 Programming Conventions

- none -

4.1.3 Support Software

The support software used by SourceInfo/I is shown in Table 10.

4.2 Maintenance Procedures

4.2.1 Verification Procedures

The formalism and software of SourceInfo/I were checked for proper perfomance. For detailssee Chapter 4.3.

4.2.2 Error Correction Procedures

SourceInfo/I performs several checks on the input data. In most cases it is impossible to interpret,let alone to correct, an input specification which fails a test, and program execution is not possible.The following two chapters describe how the program deals with such conditions.

4.2.2.1 Runtime Errors Probably Not Caused by User Input

There a number of errors or problems with data out of range which are most likely caused by(a) loading problems, (b) wrong entries in the FixData base, or (c) wrong entries in data files.Such errors are called "installation errors". When SourceInfo/I encounters an installation error,

Table 10 : Support software used by SourceInfo/I

type software used

FORTRAN intrinsic functions EXP and other basic mathematic functions not specif-ically mentioned here

FORTRAN subroutines of RODOS Subroutines UHEADL and UGETM5


draft - 25 - 7.12.2001

a brief message is flashed on the RODOS screen with the information, that and in which sub-routine an error occured, and where to look for more detailed information (into "RODOS term-log"). After that, program execution stops.

The messages in "RODOS termlog" have the following format:

• One or more lines describing the problem, and, eventually, the data causing the problem.

• Last line : ERROR EXIT (INSTALLATION ERROR) .

4.2.2.2 Runtime Errors Probably Caused by User Input

There a number of errors which are most likely caused by user input. When SourceInfo/I en-counters such an error, a brief message is flashed on the RODOS screen with the information,that an error occured, and where to look for more detailed information (into data set <~rodos/roextern/outall/userId/runId/Prognose.STermData>). After that, an error flag is set and controlis returned to the caller.

The checks for user errors and the respective error messages are listed in the [Prognosis USERGUIDE] .

4.3 Test Plan and Test Analysis Report

4.3.1 Tests for Task SETSRC - Setup of Source Term

Initially, the radioactive decay formula and the decay chain formalism were checked for selectednuclides and decay chains of the type m->n and p->m->n using the full analytic formulae (e.g.[EVAN1955, Chapter 15] and all was found to work all right. After that, SourceInfo/I underwentadditional tests which are described below.

4.3.1.1 Test Plan

Checking of task SETSRC was done with several blocks of test cases shown in Table 11 on p.25. All tests were performed with the source term entry mode "File".

Table 11 : Test cases for task SETSRC of SourceInfo/I

items checked test case descriptionfile name of sourceterm

Test Block <TestMixed>: Miscellaneous Tests

Error checks and processing of userr eques t s a s de sc r i bed i nChapter 4.2.2.

Waste bin procedure;radioactive decay without chains

Several requests and errors in the releasespecifications

All aerosols assigned to the waste bin, whichleaves iodine isotopes without mothers.

FTi.TestSetup

FT1.TestWaste-3FT1.TestWaste-7

Test Block <TestRdeca>: algorithm for rad. decay incl. decay chains


draft - 26 - 7.12.2001

The checking/printing software (subroutine SETQTP and its lower level subroutines) is the samefor all input modes. The waste bin procedure is the same for all input modes which requirerelease groups. This part of the software checked with Test Block <TestMixed>.

Source term input modes FT1 to FT5 use the same central algorithm for the radioactive decayincluding decay chains. This part of the software is checked with Test Block <TestRdeca>. Asreference cases the inventory tables from [LEIT1995] are used, which give the inventory of aPWR Reactor with 3733 MW thermal power for four different days of operation and five timesafter the end of the chain reaction (0h, 1h, 6h, 24h, 120h). The corresponding inventories arecontained in the permanent data file <INVE.Leitfaden95>. With the model implemented inRODOS, the time matrix with respect to the time after reactor shutdown can be obtained byspecifying a release of 100% of the core inventory at the correponding times after the end of thechain reaction. Five source terms (FT1.Leitfdn000h - FT1.Leitfdn120h in Table 11) were set upfor comparison with the complete time matrix for the equilibrium core (p. 8/9 in [LEIT1995]).

Test Blocks <TestModes-7> and <TestModes-3> tests if all different source term input modesgive the same or explainable different results when applied to the same source term. The basesource terms for the 7 and 3 release group parametrisation was derived from the RODOS versionof release category FK2 from the German Risk Study Phase A. To generate the test source terms,first runs with input mode FT1 were performed. The source term file output, FT6.STERMoutand FT7.STERMout, and the source term data protocol of these runs were then used to derivethe test data for the other input modes.

For several time steps and radionuclides, the SourceInfo/I results were hand-checked with

• radioactive decay formula• decay chain algorithm• start of release

Inventory: [Leit1995]Release: One 100% puff release at giventime.

FT1.100at000hFT1.100athlfhFT1.100at001hFT1.100at006hFT1.100at024hFT1.100at120h

Test Block <TestModes-7>: Different input modes for same source term (7 release groups)

All different input modes for thesame source term must give the sameor explainable different results forthe activity release rate.

Inventory: [Leit1995]Release: Derived from the RODOS versionof release category FK2 from the GermanRisk Study Phase A.

FT1.TestModes-7FT3.TestModes-7FT4.TestModes-7FT5.TestModes-7FT6.TestModes-7FT7.TestModes-7

Test Block <TestModes-3>: Different input modes for same source term (3 release groups)

All different input modes for thesame source term must give the sameor explainable different results forthe activity release rate.

Inventory: [Leit1995]Release: Derived from the RODOS versionof release category FK2 from the GermanRisk Study Phase A.

FT1.TestModes-3FT3.TestModes-3FT4.TestModes-3FT5.TestModes-3FT6.TestModes-3FT7.TestModes-3

Table 11 : Test cases for task SETSRC of SourceInfo/I

items checked test case descriptionfile name of sourceterm


draft - 27 - 7.12.2001

respect to radioactive decay, decay chains, and activity release by repeating the calculationstimestep by timestep with pocket calculator and analytical radioactive decay formula with 1storder decay chains.

4.3.1.2 Test Analysis Report

All test input and output files and a test analysis summary are kept on disk and can be madeavailable on request. They are used as a reference when tests are repeated after changes in theSourceInfo/I software. Errors or problems detected with the tests are removed or clarified beforeimplementing the software in the RODOS.

4.3.2 Tests for Task SETRLG - Setup of Release Groups

By specifying a special print flag for task SETRLG it generates detailed output about its actions.In the initial test phase in 1996 and after the inclusion of the new "waste bin group" in 1998,this output was inspected and it was ascertained that the task performs correctly. Apart fromthat, the task is in frequent use and no errors were detected at FZK or reported by external users.

4.3.3 Tests for Task SETCHN - Setup of Decay Chains

By specifying a special print flag for task SETCHN it generates detailed output about its actions.In the initial test phase in 1996, this output was inspected and it was ascertained that the taskperforms correctly. Since that time, the task is in use and no errors were detected at FZK orreported by external users.

4.3.4 Tests for Task SETINV - Setup of Inventory

Most of the properties of task SETINV were already checked when performing the tests describedin Chapter 4.3.1 (including the inventory data file <INVE.Leitfaden95>). In addition, the scalingformulae for thermal power and operation days were tested by putting in some new values andcomparing the result with hand-calculations.

4.3.5 Tests for User Input via Initialisation Windows

It was checked that input made with the initialisation windows of RODOS are correctly passedto the SourceInfo/I shared memory.

4.3.6 Tests for Permanent Input Data Files

See Chapter 6.2 and Chapter 7.2 for tests on syntax and content of the permanent input data filesused by SourceInfo/I.


draft - 28 - 7.12.2001

5 Model Description

5.1 Introduction

The interactive operation mode of RODOS shall serve in real emergency situations as well asfor training and exercises. With respect to the source term input this means that RODOS mustbe able to deal with frequently used data formats and parametrisations in order to make adap-tations to real or fictive scenarios as easy as possible. The source term interface for other programsof RODOS, however, should not depend on the particular format of the source term specification.Such a uniform source term interface is produced by the software package SourceInfo/I ofRODOS and contains the information listed below.

Release data in the interactive operation mode of RODOS can currently cover a period of twelvesuccessive hours following the start of the initial release in 30 minutes’ time steps. All releasedata which depend on the time are parameterised for the corresponding 24 half-hour time steps.

• Start of the initial releaseThe start of the initial release is the time the release from the reactor sets in after the end ofthe chain reaction. For synchronisation with the atmospheric dispersion models, this informa-tion is given in multiple of half-hours relative to the time zero = end of the chain reaction.

• Released thermal power as a function of time.The released thermal power is equal to or greater zero in each release time interval.

• Height of the release as a function of time.The release height normally corresponds to the height of the stack or the point of release fromthe reactor building. In case of a release of unknown thermal energy and an estimation of theexcess height of the plume being available, the latter may be taken into account by enteringthe estimated effective height for the height of release and zero for the thermal power.

• Fractions of elementary iodine, organically bound iodine and iodine aerosols of total io-dine released (“iodine fractions”) as a function of time.The fractions of elementary iodine, organically bound iodine and iodine aerosols (“iodinefractions”) refer to the total amount of iodine released during a release time interval, and thesum of the three fractions is 100% for each interval.

• Activity release rates as a function of time for between 1 and 15 nuclides.

Apart from the activity release rates, all above data an directly be used in the form they wereentered into the system by the user. However, SourceInfo/I performs checks on and eventualmodification of the data to ensure that they comply with the interface requirements. This isdescribed in Chapter 5.2.

All application-oriented calculations with RODOS are carried out with between 1 and 15 userselectable nuclides; SourceInfo/I, however, may need some more on occasion. This is describedin Chapter 5.3.

The main task of SourceInfo/I is to derive nuclide-specific activity release rates from the variousinput specifications for the released activity. The user input for the two modes F/ST6 and FT7needs either no processing whatsoever (FT7), or simple division by the length of the releasetime interval (F/ST6). The procedure for source term input modes F/ST1 to F/ST5, however,


draft - 29 - 7.12.2001

is not so straighforward and is described in detail in Chapter 5.4. The corresponding task inSourceInfo/I is named "SETSRC - SETup of SouRCe term".

Source term input modes ST1 to ST5 (Table 1 and Table 2) specifiy the released activity in termsof groups of nuclides or of individual nuclides representing groups of nuclides. Such nuclidegroups are called "release groups" in the frame of SourceInfo/I. They contain nuclides with thesame physical and chemical behaviour with respect to the release properties, which means thatat any given time for all nuclides belonging to the same group the same fraction of the activityin the reactor is released. The nuclide release groups currently provided by default with Sour-ceInfo/I are listed in Table 12 on p. 37.Whenever there are release specifications for groups orfor single nuclides representing a group, SourceInfo/I uses the following additional informationto derive the nuclide-specific release rates for the source term interface:

• the composition of the release groups;

• all decay chains containing any of the nuclides considered in the actual RODOS calculation;

• the time-dependent nuclide-specific activity inventory of the reactor under consideration.

The setup of this information is described in Chapter 5.5, Chapter 5.6 and Chapter 5.7, respec-tively.

The data specified by the user, some derived information and all warnings and error messagesissued by any of the subtasks of SourceInfo/I are recorded in a "source term data protocol",which is described in Chapter 5.8.

With respect to the setup of source terms, there is no difference whether the source term entrymode is "Standard" or "File", once the files are read, and this aspect plays no role in the modeldescription. The normal user of the system is likely to prefer the "standard" mode. The inputfor the more powerful "file" mode is described in detail in Chapter 8.

5.2 Checks and Modifications of Input Data

SourceInfo/I performs checks for consistency/interpretability on the source term input data.Most of the checks lead to an error exit if they fail. Sometimes it makes sense to adjust formissing or incorrect input values, or to substitute special values at runtime on request by theuser. Such adjustments are described below. In any case, the program reports the nature of theproblem in the source term data protocol; user errors leading to an error stop are also flashedon the RODOS main screen.

5.2.1 Start of Initial Release

The starttime of the release must be specified rounded off to half hours relative to the time point"end of chain reaction". If the user gave a value which is not a multiple of 0.5, that value willbe reset to the nearest multiple of 0.5.

5.2.2 Height of Release

The release height must be 10 m at least. If the user gave a value between 0 m and 10 m in arelease time interval, a height of 10 m will be inserted for that interval.

When a negative value for the release height was given by the user in a release time interval,the stack height for the site under consideration, which is contained in the FixData Base, will


draft - 30 - 7.12.2001

be inserted for that time interval.

5.2.3 Release Thermal Power

The released thermal power must be greater or equal to zero. If the user gave a value below zeroin a release time interval, execution stops.

5.2.4 Fractions of Elementary, Organically Bound, and Aeosol Iodine

The iodine fractions are not used in SourceInfo/I itself but are important for the subsequentatmospheric disperion and deposition models. Therefore, the substitution of values is orientedon the needs of those models.

If there is a release of iodine in a release time interval, but the user did not specify the iodinefraction, 100 % elementary iodine will be inserted for that time interval. This represents themost conservative assumption because elementary iodine has the strongest deposition.

If there is no release of iodine in a release time interval, 100 % aerosol iodine will be insertedfor that time interval. That is done so because the iodine resulting from mother decays afteremission from the reactor is in the aerosol form.

5.3 Nuclides in SourceInfo/I

The FixData base of RODOS contains a larger number of free or chemically bound radionuclides,which are called "FixData nuclides". However, all application-oriented calculations with RO-DOS are carried out with a subset currently consisting of between 1 and 15 user selectablenuclides, which are termed "RODOS calculation nuclides". The source term interface generatedby SourceInfo/I contains the activity release rates for these calculation nuclides, which may varyfrom run to run.

However, only for source term input modes which give the release data in terms of individualradionuclides, the nuclides considered internally in SourceInfo/I for the calculation of the releaserates are always identical with the calculation nuclides. For all other input modes this need notnecessarily be the case. In the following, the nuclides used internally in the SourceInfo/I calcu-lations are called "SourceInfo/I internal nuclides".

SourceInfo/I internal nuclides for input modes F/ST1 to F/ST53 consist of the following nuclides:

• Primary nuclides(+) all calculation nuclides, but (-) excluding those marked for exclusion by task "setup ofrelease groups" (i.e. all nuclides assigned to the waste bin release group, see below).

• Auxiliary nuclides(+) all FixData nuclides which were found by task "setup of decay chains" as feeders for aboveprimary nuclides via some decay chain, and all which again feed the feeders, and so on, forthe whole chain, but (-) excluding again those marked for exclusion by task "setup of releasegroups".

The possibility to exclude radionuclides from the calculations by "assigning them to the waste

3. SourceInfo/I internal nuclides for input mode F/ST6 and FT7 are identical with the calculation nu-clides.


draft - 31 - 7.12.2001

bin" is necessary for input modes F/ST1 to F/ST5, because for these it must be required that allFixData base nuclides are assigned to one and only one nuclide release group in order to guarantee(mathematical) completeness of the specifictions. The waste bin is for all radionuclides notfitting into the release group scheme desired for the calculations. This is for instance currentlythe case for the FixData nuclides tritiated hydrogen and tritiated water.The activity release ratefor calculation nuclides assigned to the waste bin is always zero. A warning message is issuedin the source term data protocol to remind the user of this special setting.

5.4 Calculation of Activity Release Rates for Source Term Input Modes F/ST1 to F/ST5

5.4.1 General Formalism

When the activity release is specified in terms of nuclide groups or in terms of individual radi-onuclides representing groups of nuclides, a reference is needed which allows to decomposethat information into the nuclide-specific activity release rates required by RODOS. For this,SourceInfo/I uses the time-dependent nuclide-specific activity inventory in the reactor togetherwith information about the release.

Figure 2 shows the time scale used for the calculations. The internal time axis of SourceInfo/Ibegins with the end of the chain reaction, and the internal clock ticks in the unit [hours]4. Therelease sets in after some time interval ∆t0 after the end of the chain reaction5. This time is thetime zero for all release calculations. Starting with t0, the time axis is divided into imax timepoints ti which define the boundaries for imax-1 time intervals (ti, ti+1 ) = (ti, ti + ∆tr) with equalwidth ∆tr.

Figure 2 : Time axis for source term calculations with SourceInfo/I

Between the end of the chain reaction and the begin of the release, and in all release-free periodsafterwards, only radioactive decay is considered. Equation 1 shows the calculation of the radi-oactive decay of the activity inventory AI of some nuclide n in a release-free time interval (t,

4. The central radioactive decay calculation, which is done in subroutine RDECAY, works with exter-nally specified physical unit for the time, and is, for instance, also used by SourceInfo/A, the clockof which ticks in minutes.

5. ∆t0 is given by SourceInfo/I shared memory variable BEGFRE.

time

end ofchain reaction

begin ofinitial release

∆t0 ∆tr

ti ti+1t0=0


draft - 32 - 7.12.2001

t+∆t). Equation 1a is applied when no mother feeds radionuclide n, and Equation 1b, when it isfed by one or more mother m by a decay of the type m->n (based on e.g. [EVAN1955, Chapter15]).

The calculations are carried out for all SourceInfo/I internal nuclides, which do not only consistof the calculation nuclides and their direct mothers, but also of of the mothers of the directmothers, and so on, if the chain at some position contains a calculation nuclide. This means, theactivities on all levels above nuclide n in a chain are actually accounted for, only the contributionsto all repective downward nuclides appear with a time delay of (number of decay steps betweennuclides - 1)*∆t. One approach to reduce (but not eliminate) the error for all nuclides n at timet+∆t due to this time shift is to subdivide the time interval ∆t into finer intervals and performingthe calculations with equation 1b on these time intervals until time t+∆t is reached. For currentapplications with RODOS, which do not contain decay chains with contributions from morethan about 2 levels, a division of ∆t/10 is sufficient. Other approaches to the problem are possible,but the above one is independent of in which sequence mothers and daughters on the differentlevels are calculated, which allows a relatively straightforward and simple implementation intoa computer code.

For all time periods with release, at first the calculated nuclide-specific activity inventory in thereactor at the time of the release is used to derive the nuclide-specific activity release from therelease data specified for nuclide groups. After that, the activity released is substracted from theactivity inventory in the reactor. The release calculations in SourceInfo/I are based on two con-ditions:

Condition 1: If there is a release in some time interval (t , t+∆tr), the simplifying assumptioncan be made that it occurs instantaneously at time t and the time span ∆tr is release-free.

Condition 2: All nuclides belonging to the same nuclide release group are released with identicalfractions of the activity inventory present in the reactor.

Equation 2 on p. 33 shows the calculation of the activity released from the reactor, and theactivity inventory remaining in the reactor just after the release with the two conditions above.The index n stands for some SourceInfo/I internal radionuclide which belongs to some releasegroup denoted j.

The activity in the reactor at the beginning of the next time interval with release is obtained byapplying Equation 1 to AI (t,n) from Equation 2 (with ∆t being the duration of the release-free

Equation 1 : Radioactive decay and decay chain contributions

AI(t+∆t,n) = AI(t,n)(1a)

(1b)

t, ∆t : time, time step length [hour]

of decays of nuclide m which lead to nuclide n (0<fmn<1)

λ : radioactive decay constant [hour]-1

fmn : fraction

with

λn e(- ∆t)

n, m : radionuclide n with mother(s) m (n, m are SourceInfo/I internal nuclides)

AI(t+∆t,n) = (λn-λm)λme

(- ∆t)-

AI : Activity inventory [Bq]

m}λne

(- ∆t)][λn fmn AI(t,m){Σ AI(t,n) λn e(- ∆t) +


draft - 33 - 7.12.2001

period); this is then the start value for the next release calculation.

.

For the calculation nuclides, the activity released from the reactor, AR, is converted to an activityrate using the length of the release time interval. This quantity is the one which is output to theSourceInfo/I source term interface.

5.4.2 Application of General Formalism for Source Term Input Mode F/ST1

The user specifications in source term input mode F/ST1 are "initial release fractions" given fornuclide release groups j for each release time interval (ti, ti + ∆tr). These fractions refer to theactivity inventory initially present in the reactor at the end of the chain reaction and are denotedwith the symbol xo(ti,j).

In Equation 2, however, the nuclide-specific release fractions x(ti,j) applying to the inventoryremaining in the reactor before the releases take place are needed. Because for each time ti afterthe initial release the activity remaining in the reactor after the releases which took place untilti is given by (1-xo(t1,j)-xo(t2,j)-...-xo(ti-1,j)*AI(t=EOC,j)), the fractions x(ti,j) can be obtainedfrom the initial fractions with Equation 3.

Equation 3 is evaluated before application of Equation 2 for all release groups j and times ti to

Equation 2 : Activity released from and activity remaining in reactor

Equation 3 : Derived release fractions for source term input mode F/ST1

AR(t,n) = x(t,j) AI(t,n)

AI (t,n) = AI(t,n) - AR(t,n)

with

AR : Activity [Bq] released from reactor at time tAI : Activity [Bq] remaining in reactor at time t just after release

x : fraction of activity inventory of nuclide n in nuclide group j released at time t

(2a)

(2b)

AI : Activity inventory [Bq] in reactor at time t just before the release

t : time [hour]n, j : SourceInfo/I internal nuclide n belonging to nuclide release group j(n)

For i = 1 :

For i > 1 :

x(t1,j) = xo(t1,j)

xo(ti,j) < 1 Σi xo(ti,j) < 1

x(ti,j) = xo(ti,j) / (1 - Σ x(tk,j))k=1

i-1

withti : time after initial release [hour]

n, j : SourceInfo/I internal nuclide n belonging to nuclide release group j(n)

xo : initial release fractions; and (user input)


draft - 34 - 7.12.2001

obtain the fractions x(ti,j) for all SourceInfo/I internal nuclides. Apart from that, the calculationsproceed as described in Chapter 5.4.1.


The user specification in source term input mode F/ST5 is the released activity summed up overall calculation nuclides6 belonging to nuclide release groups j for each release time interval (ti,ti + ∆tr).

With the calculated activity inventory in the reactor, AI(ti,n), the user-specification of the activityreleased from the ractor, AR(ti,j), and condition 2 from Chapter 5.4.1, the release fractions x(ti,j)required for Equation 2 can be obtained with Equation 4 .

Equation 4 is evaluated before application of Equation 2 for all release groups j and times ti toobtain the fractions x(ti,j) for all SourceInfo/I internal nuclides. Apart from that, the calculationsproceed as described in Chapter 5.4.1.

One problem can obviously occur when applying Equation 4: The user specification of thereleased activity may exceed the calculated activity present in the reactor in one or more releasetime intervals. In such cases, the calculated value is taken, a corresponding message is issued,and execution continues.


The user specification in source term input mode F/ST4 consists of two different types of data.The first set of data is the released activity for the sum of nuclides belonging to the three releasegroups noble gases, iodine, total aerosol, for each release time interval (ti, ti + ∆tr). The secondset of data are (currently) time-independent "initial" aerosol release fractions for aerosol releasegroups jaer .These fractions refer to the activity inventory initially present in the reactor at theend of the chain reaction and are an expression of the effect that not all aerosol nuclides havethe same properties with respect to the release; they are denoted with the symbol xo(ti,jaer) inthe following.

The release fractions for the noble gas group and the iodine group are calculated with Equation 4,

using the calculation nuclides belonging to each group6. and the user-specified activities for the

6.See also Chapter 5.4.6.

Equation 4 : Derived release fractions for source term input mode F/ ST5

x(ti,j) = AR(ti,j) / Σ AI(ti,n) nεj

with

AR : Activity sum [Bq] for nuclide release group j released from reactor at time ti

AI : Activity inventory [Bq] in reactor at time ti before the release

ti : time after initial release [hour]n, j : SourceInfo/I internal nuclide n belonging to nuclide release group j(n)

(user input)


draft - 35 - 7.12.2001

respective group.

For the aerosol nuclides, however, account must be taken for the user-supplied initial aerosolfractions xo(jaer). In SourceInfo/I this is done by using - within the framework laid out inChapter 5.4.1 - the aerosol fractions as weights for the different aerosol nuclide release groupsto the user-specified total aerosol activity released in the manner described below.

To start with, the initial release fractions xo(jaer) are divided by the total number of release timesteps to ensure that the algorithm does not artificially create an emptied reator in the process ofthe calculations. Then, intermediate fractions x(ti,jaer) applying to the inventory remaining inthe reactor before the releases take place are derived: for time intervals with aerosol release byusing xo(jaer) in Equation 3; for time intervals without aerosol release, x(ti,jaer) is zero. In anext step, these intermediate fractions x(ti,jaer) are used to calculate nuclide-specific activityreleases AR(ti, n) with Equation 2, and after that the quantity ARaer is calculated by summingover all aerosol calculation nuclides. However, as the user-specified activity release is ARaerand not ARaer, the fractions x(ti,jaer) are in a last step multiplied with the ratio F=AR/AR toobtain fractions x(ti,jaer) which are applicable in Equation 2 and yield ARaer as a total.

Finally, equipped with the release fractions x(ti,j) for all times ti and release groups j, the cal-culation of the nuclide-specific activity release proceeds as described in Chapter 5.4.1.

If the user specification of the released activity exceeds the calculated activity present in thereactor in some release time interval, the calculated value is taken, a corresponding message isissued, and execution continues.

5.4.5 Application of general formalism for source term input mode F/ST3

The user specification in source term input mode F/ST3 consists of two different types of data.The first set of data is the released activity for the sum of nuclides belonging to the two releasegroups noble gases and total aerosol, and the activity released for the nuclide I-131, for eachrelease time interval (ti, ti + ∆tr). The second set of data are (currently) time-independent "initial"aerosol release fractions for aerosol release groups jaer .These fractions refer to the activityinventory initially present in the reactor at the end of the chain reaction and are an expressionof the effect that not all aerosol nuclides have the same properties with respect to the release.

The procedure for obtaining the release fractions for the noble gas group is the same as inChapter 5.4.3. The procedure for obtaining the release fractions for the various aerosol groupsis the same as in Chapter 5.4.4. The release fractions for the iodine group are obtained withEquation 4 and the user-specified activities of I-131.

Finally, equipped with the release fractions x(ti,j) for all times ti and release groups j, the cal-culation of the nuclide-specific activity release proceeds as described in Chapter 5.4.1.

If the user specification of the released activity exceeds the calculated activity present in thereactor in some release time interval, the calculated value is taken, a corresponding message isissued, and execution continues.

5.4.6 Remark on Using the Calculation Nuclides When Applying Equation 4

When Equation 4 is applied to obtain the release fractions x(ti,j), it is obvious that the result


draft - 36 - 7.12.2001

depends on which nuclides belonging to group j are included in the evaluation of the sum.

It is less obvious what to do - take into account all nuclides of the respective group for whichinventory data are available in RODOS, or all SourceInfo/I internal nuclides, or only the calcu-lation nuclides selected by the user for the run? An in addition, it is not too clear what exactlythe user expects or thinks when the specification is the amount of activity released for a group,but only very few nuclides from the group are selected for the calculations.

For the time being, it was chosen to calculate the sums with the RODOS calculation nuclidesonly, because this provides a unique and controllable reference for the quantity "released activityfor nuclides in a given group" by specifying exactly which nuclides contribute to the sum valuefor the group.

5.4.7 Calculation Flow, Possible Release Time Steps and Release Groups

With respect to the release time steps, SourceInfo/I currently loops internally over 24 intervalsof equal width ∆tr=0.5 hours, starting with the time of the initial release (see Figure 1 on p.15). In a first step, the activity inventory at the beginning of the release, t=t1, is calculated by

applying Equation 1 with ∆t=∆t0 to the inventory at the time of the end of the chain reaction.Then, for all times ti , Equation 2 is evaluated if there is a release in a time interval. This isfollowed by application of Equation 1 to AI (ti,n), with ∆t=∆tr, if there is a release in the nexttime interval, or, if there no release in the next time interval(s), with ∆t being the time spanbetween ti and the time of the next release, that is, release-free time intervals are skipped inorder to save computing time.

The number of time steps can be set to any reasonable value greater than 17.

In principle it should also be possible to use release time step lengths other than half hours byadjusting the corresponding parameter8. However, it must be remarked that the latter possibilitydid not belong to the original design objectives and was so far neither tested nor attempted.

With respect to release groups, the maximum number of considerable groups is currently 16;this number can be changed by adjusting the corresponding parameter9. The software of Sour-ceInfo/I treats the groups as abstract items and does not care about their specific composition.However, the composition must be defined in a file with name <in.releasegroups>.

For source term entry mode "Standard", the references to the time intervals and release groupsis not so abstract in the syntax for the RODOS input windows and the FixData base, which isalso the reason for the contraint that in the source term input modes ST1 to ST5 only oneparticular parameterisation of the release groups could be realised.

5.5 Setup of Nuclide Release Groups

SourceInfo/I task "SETRLG - SETup of ReLease Groups" produces a cross-reference betweenFixData nuclides and nuclide release groups by providing the following information10:

• the number of release groups considered in the actual run,

7.SourceInfo/I parameter MAXRLS8.SourceInfo/I shared memory-variable DRLSPM9.SourceInfo/I parameter MAXRLG


draft - 37 - 7.12.2001

• a reference array specifying for each FixData nuclide to which release group it belongs,

• a name array containing the names of the groups.

The composition of the release groups is read from the file <in.releasegrps> and is based onthe attachment of chemical elements or individual molecules to groups. The file is described indetail in Chapter 6 and contains the definition all sets of groups or "release blocks" foreseen inSourceInfo/I. The four release blocks currently provided by default are listed in Table 12 on p.37.

10. SourceInfo/I internal common block variables NRLGRP (actual release group number), JRLGRP(reference array) and CRLGRP (name array).

Table 12 : Nuclide release groups provided by default

Blockidentifier

Release group description

NOBLE-JOD-AEROSO Nr. 1 : noble gasesNr. 2 : iodineNr. 3 : aerosols(all non-noble gase, non-iodine nuclides are treatedequally)

DRS-A_7_GROUPS Groups f rom German R i sk S tudy, Phase A[DRSA1981].Nr. 1 : noble gasesNr. 2 : iodineNr. 3 : alkaline metalsNr. 4 : tellurium and seleniumNr. 5 : alkaline earthsNr. 6 : ruthenium groupNr. 7 : lanthanides

DRS-A_7_GROUPS09 Groups from German Risk Study, Phase A [DRSA1981]plus HT and HTO.Nr. 1 : noble gasesNr. 2 : iodineNr. 3 : alkaline metalsNr. 4 : tellurium and seleniumNr. 5 : alkaline earthsNr. 6 : ruthenium groupNr. 7 : lanthanidesNr. 8 : tritium (HT)Nr. 9 : tritiated water (HTO)


draft - 38 - 7.12.2001

Each source term input mode parameterized in terms of release groups contains an identifier11

specifying the release block it refers to. SourceInfo/I starts with searching the data file for thecorresponding block name. If it was not found, an error message is issued and execution isstopped.

If the block was found, the name array for the groups belonging to the block and the referencearray are set up. The latter is achieved by comparing the names of the group members read fromthe file, which are two character abbreviations specifying a chemical element or molecule, withthe first two characters of the FixData nuclides names, and, when equal, assigning the followingvalue for the corresponding FixData nuclide:

• if not assigned to the "waste bin", the number of the release group it belongs to (numbering is1...NRLGRP-1 in the order as the groups stand in the file);

• if assigned to the "waste bin", the value zero.

On exit of task SETRLG, the actual number of release groups is set to the number of releasegroups read from file minus one for getting rid of the "waste bin group", which is always thelast group in each release block in the data file.

There are a number of constraints for the data file itself and consistency requirements betweensource term input and content of data files which are checked by task SETRLG; they all lead toan error stop of the task when the test fails.

5.6 Setup of Decay Chains

SourceInfo/I task "SETCHN : SETup of decay CHaiNs" sets up the final SourceInfo/I internalnuclides list and specifies all feeders ("mothers") via a decay chain for all calculation nuclides,and all nuclides which again feed the feeders, and so on, for the whole chain, by providing thefollowing information12:

• an array containing the number of mothers for each SourceInfo/I internal nuclide,

11. SourceInfo/I shared memory variable CRLGID.

MAAP4_10_GROUPS Nr. 1 : noble gasesNr. 2 : iodineNr. 3 : rubidiumNr. 4 : strontiumNr. 5 : ruthenium groupNr. 6 : alkaline earthsNr. 7 : bariumNr. 8 : lanthanidesNr 9 : actinidesNr.10 : tellurium

Table 12 : Nuclide release groups provided by default

Blockidentifier

Release group description


draft - 39 - 7.12.2001

• an array specifying the adresses of the mothers in the FixData nuclide array,

• an array containing the fractions of the mother decays leading to the daughter; the fractionswere taken from [KOCH1981, Appendix 4].

The definition of the decay chains, their members and decay fractions are read from the file<in.decchain>, which is described in detail in Chapter 7.

Task SETCHN starts processing by activating all calculation nuclides except the ones markedfor exclusion by task "setup of release groups" in the SourceInfo/I internal nuclides list.

SETCHN then begins to read the decay chain file. For each decay chain it first builds a temporaryarray which maps all daughter and mother nuclides belonging to the decay chain with the avail-able fix data nuclides, again ignoring all those marked for exclusion by task "setup of releasegroups".

When the information for the decay chain is complete, SETCHN inspects the temporary arrayfor the presence of a at least one active calculation nuclide with a mother in the chain. If nonewas found, the chain is ignored. If one was found, all chain members are added to the lists forthe SourceInfo/I internal nuclides, number of mothers, mother adresses and decay fractions, andSETCHN turns to the next decay chain.

5.7 Setup of Inventory

SourceInfo/I task "SETINV : SETup of INVentory" provides a nuclide-specific activity inven-tory of the reactor under consideration or each internal SourceInfo/I nuclide in the unit [Bq]for the time point "end of the chain reaction".

The input inventory data come from a file, which contains sets of data for the activity A0inv validfor thermal power pinv and between one and four days of operation dinv. The required inventoryA0r for a reactor block with thermal power pr and operation days dr is calculated with Equation 5from [LEIT1995, p.10]):

If the input inventory consists only of one data set for the days of operation d1inv, the secondpart of the equation is of course not applicable.

5.8 Description of Source Term Data Protocol for the User

The source term data protocol resides on disk13 but can also be inspected with the RODOSgraphics; it has the following content:

• Information about the inventory data used for the calculation (source term input modes ST1to ST5 only).

• Information about the start of the intial release; the release height as a function of time, thereleased thermal power as a function of time, the iodine fractions as a function of time (allsource term input modes), including the modifications made on user request or adjustments.

• The input specifications for the released activity.

12. SourceInfo/I internal common block variables ISOCHN (SourceInfo/I internal nuclides), NMO-THR (number of mothers), IMOTHR (mother adresses), FMN (decay fractions).

13. Path ~rodos/roextern/outall/userID/runID/{Prognose|Diagnose}.STermData


draft - 40 - 7.12.2001

• Derived information about the released activity for the calculation nuclides considered in therun:

- the activity released [Bq] per release time interval and the time sum summed oved the cal-culation nuclides in the nuclide groups "noble gases", "iodine", "aerosols" and "specials"14;

- the activity released [Bq] per release time interval and the time sum for individual nuclides;

- the activity release rate [Bq/s] per release time interval for individual nuclides.

The data protocol also contains all warnings and error messages issued by any of the tasksbelonging to SourceInfo/I.

14. The group "specials" contains e.g. HT, HTO.

Equation 5 : Calculation of the activity inventory at the end of the chain reaction

A0r(pr, dr) = (pr/pinv) * A0inv(pinv,d1inv)

with

A0inv : Activity inventory [Bq] at end of chain reaction for

A0r : Activity inventory [Bq] at end of chain reaction for

thermal power pr [MW] and operation days dr [day]

+ (pr/pinv) * [A0inv(pinv,d2inv)-A0inv(pinv,d1inv)] * (dr-d1inv)/(d2inv-d1inv)

thermal power pinv [MW] and operation days d1inv and d2inv [day]

d1inv < dr < d2invwhere


draft - 41 - 7.12.2001

6 Appendix A : Description of the Release Group File <in.releasegroups>

6.1 File Syntax and Content

SourceInfo/I reads the definition of release groups from the file named <in.releasegroups>which must reside in direcory ~rodos/roextern/data/sourceterm/setup/. By default, file <in.re-leasegroups> contains the data listed in Table 12 on p. 37. Table 13 on p. 42 shows a part ofthe file together with the respective FORTRAN format statements.

The arrangement of release blocks in the file is totally arbitrary. Inside each block a "waste bingroup" must be present, even if it is empty (NMEMBR=0), and it must be the last group in theblock. Apart from that, the arrangement of release groups in a block is in principle arbitrary.However, because other tasks (e.g. the initialisation windows) or data (e.g. source terms speci-fications for nuclide release groups) refer to the blocking defined in the file, release groupsbelonging to an already existing release block must not be re-arranged unless all side effects areconsidered and cared for (!).

The file syntax is as described below. The character "^" represents the blank character.

Comment lines

• Line 1 in file : Obligatory comment line ("--- ... ---" in Table 13).

• Line 2 in file : Number of comment lines to follow (NCOMM).

• Lines 3 to 2+NCOMM in file : Comment lines.

• Line 2+NCOMM+1 in file : Number of release blocks present in the file (NRLBLK).

Then for each release block

• Line 1 in release block : Obligatory comment line ("--- ... ---" in Table 13).

• Line 2 in release block : Name of release block; number of lines to follow for this block (in-cluding the obligtory comment line 3 following the release block name ("--- ... ---" inTable 13), and excluding the separator comment line preceeding the name of the next releaseblock (if any), because that line is already Line 1 of the next release block).

• Line 3 in release block : Comment line (must be present, but can contain anything).

• Line 4 in release block : Number of release groups in current release block (NRLGRP).

Then for each release group

• Line 1 in release group : Name of group in German (CRLGRP); number of members(NMEMBR; can be zero).

• Line 2 in release block : Name of group in English (CRLGRP); number of members(NMEMBR; can be zero); characterisation of release group (n for noble gases, i for iodine, afor aerosol, x for unspecified).

• If the number of members is greater zero, the next line(s) contain the members of thecurrent group : Release group members must be specified by the first 2 characters (includingthe blank character for names with only one character, e.g. "I^ "!) of the NucInfo names de-scribed in [RODOS(WG1)-TN(96)-11]; separator between entries are one or more blanks..Members can be entered on 1 or more lines; each line can contain any number of entries in any


draft - 42 - 7.12.2001

Table 13 : The release group data file <in.releasegroups>

format file contents (example)F-01F-02F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-02F-01F-03F-01F-02F-04F-04see textF-04F-04see textF-04F-04see textsee textF-04F-04see textF-01F-03....

------------------------------------------------------------------------NCOMM = 26 ************ number of comment lines to follow **********------------------------------------------------------------------------C. Landman/FZK ***** file in.releasegroups ***** Version: July 2000------------------------------------------------------------------------Release group members must be specified by the first 2 characters of theNucInfo names described in [RODOS(WG1)-TN(96)-11].------------------------------------------------------------------------NRLBLK = Number of release blocks to follow.--------------------------------------------SPECIFICATIONS FOR EACH RELEASE BLOCK--------------------------------------------NRLGRP = Number of release groups to follow.CRLGRP = Name of release group (CHARACTER*16) * There MUST be a "waste bin group" (even if NMEMBR=0) * The "waste bin group" MUST come last. * The "waste bin group" name MUST start with character "+".NMEMBR = Number of members in release group. (NEW IN JULY 2000)FOLLOWED BY (1 BLANK, CHARACTER*1) n to characterise noble gases, i to characterise iodine, a to characterise aerosols, x to characterise all other types.CMEMBR = Names of members (CHARACTER*2). All entries must be separated by at least one blank. Last character in each line must be the blank character.* All fixdata nuclides must be assigned to one and only one group.------------------------------------------------------------------------NRLBLK = 3------------------------------------------------------------------------NOBLE-JOD-AEROSO******SKIP*15*****************************************------------------------------------------------------------------------NRLGRP = 4CRLGRP = Edelgase NMEMBR = 2 n + CMEMBR follows belowCRLGRP = Noble gases NMEMBR = 2 n + CMEMBR follows belowKr XeCRLGRP = Jod NMEMBR = 1 i + CMEMBR follows belowCRLGRP = Iodine NMEMBR = 1 i + CMEMBR follows belowICRLGRP = Aerosole NMEMBR = 25 a + CMEMBR follows belowCRLGRP = Aerosols NMEMBR = 25 a + CMEMBR follows belowAg Am Ba Ce Cm Co Cs La Mn Mo Na Nb Nd Np Pr Pu Rb Rh Ru SbSr Tc Te Y ZrCRLGRP = +Ignorieren NMEMBR = 2 x + CMEMBR follows belowCRLGRP = +To be ignored NMEMBR = 2 x + CMEMBR follows belowT TO------------------------------------------------------------------------DRS-A_7_GROUPS ******SKIP*26******************************************......................26 lines for release block 2 ....................

Formats

F-01 : 72 arbitrary charactersF-02 : 9 arbitrary characters, integer with 4 digitsF-03 : 16 characters (block name), 11 arbitrary characters, integer with 2 digitsF-04 : 9 arbitrary characters, 16 characters (group name), 10 arbitrary characters, integer with 2 digits(*) Condition will be checked by program on execution. Violation leads to error stop.


draft - 43 - 7.12.2001

order. However, character 72 in each line must be the blank character (if it is not, the programmwill issue a corresponding message and stops execution).

6.2 File Maintenance and Tests for Contents of File

Because other tasks (e.g. the initialisation windows) or data (e.g. source terms for nuclide groups)refer to the blocking defined in the file, release groups belonging to an already existing releaseblock must not be re-arranged unless all side effects are considered and cared for.

The file should be checked for completeness when new nuclides were introduced in the FixDatabase.

The file syntax is checked at runtime by task SETRLG which reports format errors or structureinconsistencies and exits.

Problems with the file content can arise

• when new nuclides are introduced in the FixData base which have no reference in the releasegroups file, because it was forgotten to update the file;

• when the same release group member name is specified in more than one release group.

If after modification of the file <in.releasegrps> there are error stops by task SETRLG and theproblem cannot be detected by eye inspection of the file, calling subroutine SETRLG withprintflag IPRINT>0 helps - SETRLG then writes to the source term data protocol it’s interpre-tation of the input, and inconsistencies can thus be located.


draft - 44 - 7.12.2001

7 Appendix B : Description of the Decay Chain Data File <in.decaychains>

7.1 File Syntax and Content

Task SETCHN of SourceInfo/I reads information about decay chains from the file named <in.de-caychains>, which must reside in direcory ~rodos/roextern/data/sourceterm/setup/. Table 14shows a part of the file together with the respective FORTRAN format statements.

The arrangement of decay chains in the file is arbitrary. The file syntax is as described below.The character "^" represents the blank character.

Comment lines

Table 14 : The decay chain data file <in.decaychains>

format file contents (example)

F-01F-02F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-03F-04F-03F-04F-04F-04F-04F-04F-04F-03F-04F-04F-04F-04F-05....

------------------------------------------------------------------------NCOMM = 13 ************ number of comment lines to follow **********------------------------------------------------------------------------C. Steinhauer/FZK ******* file in.decchain ******* Version : 30.7.1998------------------------------------------------------------------------Nuclide names must comply with the conventions described in [RODOS(WG1)-TN(96)-11].------------------------------------------------------------------------Decay data from D.C.KOCHER: Radioactive Decay Data Tables, Appendix 4,DOE/TIC-11026, U.S. Department of Energy (1981).------------------------------------------------------------------------For inventory calculations (decay branches to stable nuclides omitted).Special setup for isotopes in RODOS/RESY-P3.1 (A few decay branches werecombined to one channel so nothing gets lost).------------------------------------------------------------------------& chain-idepth=1------------times : nstep= -1 dstep=0.000E+00h---crd=01 & I -132 from Te-132 fmd=100.00%&skchain-idepth=4------------times : nstep= -1 dstep=0.000E+00h---crd=06 d Te-133 from Te-133m fmd= 13.00% d I -133 from Te-133m fmd= 87.00% d I -133 from Te-133 fmd=100.00% d Xe-133m from I -133 fmd= 2.88% d Xe-133 from I -133 fmd= 97.12% & Xe-133 from Xe-133m fmd=100.00%& chain-idepth=3------------times : nstep= -1 dstep=0.000E+00h---crd=05 d Te-133 from Te-133m fmd= 13.00% d I -133 from Te-133m fmd= 87.00% d I -133 from Te-133 fmd=100.00% c Xe-133 from I -133 fmd=100.00% & Simplified chain (Xe-133m state left out).& chain..............................................................

Formats (FORTRAN notation)F-01 : 72 arbitrary charactersF-02 : 9 arbitrary characters, integer with 4 digitsF-03 : A16,I1,26X,I3,7X,1PE9.3,A1,7X,I2F-04 : A3,7X,A7,3X,A4,3X,A7,7X,0PF6.2 (Note: Apart from the key-word "from", the key word "void" is possible; how-

ever, cards with this key-word are ignored in RODOS).F-05 : A3, A69


draft - 45 - 7.12.2001

• Line 1 : Obligatory comment line ("--- ... ---" in Table ).

• Line 2 : Number of Comment lines to follow (NCOMM).

• Lines 3 to 2+NCOMM : Comment lines.

Then for each decay chain

• The chain definition card ("&-cards"):The first character must be "&" and characters 4-16 must be "chain-idepth="15; the value ofidepth is not used in RODOS. NSTEP and DSTEP must have the values as shown in the ex-ample. The value following "crd=" is the number of lines to follow for the decay chain and

must be greater than zero15..

If the first three characters in the line are "&^^", then the decay chain represented by the chaindefinition card is evaluated; if they are "&sk", then the chain will be ignored (i.e. the numberof cards given by "crd=" is skipped).

• Data cards ("d-cards"):The first three characters tell the type of the next card and can have the values "^&^", "^d^" or

"^c^" 15. 16. Then follow the name of the daughter, the keyword ’from’, the name of the motherand the fraction of the mother decay leading to the daughter (in percent). The nuclide namesmust comply with the conventions described in [RODOS(WG1)-TN(96)-11].

• Comment cards ("c-cards"):The first three characters tell the type of the next card and can have the values "^&^", "^d^" or

"^c^"15. 16.. The rest of the line can contain any arbitrary comment.

7.2 File Maintenance and Tests for Contents of File

After the introdution of new nuclides in the FixData base, file <in.decaychains> must be checkedfor for missing or partial decay chains:

• If a new nuclide is member of a decay chain not yet implemented in the file => Implement thenew decay chain.

• If a new nuclide complements a decay chain which was already implemented in a simplifiedform to include the contribution from the nuclide formerly not present => Implement the decaybranch for this nuclide.

An example is shown in Table 14: nuclide Xe-133m is currently not in the FixData base ofRODOS, and the simplified chain part I-133 -> Xe-133 is implemented (the full chain is in-cluded in the file but marked for skipping). If Xe-133m would be included among the FixDatanuclides, the full chain should be activated and the reduced chain eliminated or skipped.

When new data are added, the decay fractions from [KOCH1981, Appendix 4] should be usedto preserve consistency in the file.

15. Condition will be checked by program on execution. Violation leads to error stop (seeChapter 4.2.2.1).

16. Use value "^&^" on the last card in the file.


draft - 46 - 7.12.2001

The file syntax is checked at runtime by task SETCHN which reports format errors or structureinconsistencies and exits .

If after modification of the file <in.decaychains> there are error stops by task SETCHN and theproblem cannot be detected by eye inspection of the file, calling subroutine SETCHN withprintflag IPRINT=2 helps - SETCHN writes then to the source term data protocol every card itreads, so any problem card can immediately be found.


draft - 47 - 7.12.2001

8 Appendix C: Description of the Source Term Entry Mode "File"

In the source term entry mode "File" the user must provide an input file with the source termitself. In addition, the file name must be made known to SourceInfo/Ieither by specifying it inthe initialisation windows or with the assign editor of RODOS. The file must reside in direcory~rodos/roextern/data/sourceterm/input/.

The file format and contents are described in Chapter 8.1 to Chapter 8.5. The file header is thesame for all file input modes shown in Table 2 and is subject of Chapter 8.1. The file header isthen followed by the input mode dependent data described in Chapter 8.2 to Chapter 8.5.

Each time the SourceInfo/I program is executed in a prognosis run of RODOS, the source termused is written onto two files, FT6.STERMout and FT7.STERMout, which can be re-used asinput for SourceInfo/I in the source term entry mode "File". How to do this is described inChapter 8.6.

Document [RODOS(WG7)-TN(00)-01] gives hints for successful implementation of new sourceterm data files into the RODOS system.

8.1 File Header

Table 15 on p. 48 shows the header of a source term file and the respective FORTRAN formatstatements. The file header in the example is for input mode FT1; the name of the example fileis <FT1.TestBlockB>. The file syntax is described below. The character "^" represents the blankcharacter.

Comment lines


• Line 2 : Number of comment lines to follow (NCOMM).

• Lines 3 to D0=2+NCOMM : Arbitrary comment lines.

Data lines

• Line D0+1: Flag for source term entry mode. In entry mode "File" the content of the line isignored, i.e. it is read as a comment line. However, the line may eventually be used for theFixData base, and it should be written exactly as shown in the example.

Line D0+2: Source term file name. It is recommended (but not cogent) to use the file inputmode identifier as a prefix in the file name to ensure that the file name shows to which file inputmode the file belongs - this helps to keep source term file archives managable. In any case, thefile name must not exceed 16 characters.

• Line D0+3: Flag for source term input mode; see text. in

• Line D0+4: Release block name (16 characters); see text.

• Line D0+5: Number of release groups in the block; see text.

• Lines D0+6,7: Comment for source term (80 characters each); appears in text output of a run.

• Line D0+8: Obligatory comment line.

• Line D0+9: Begin of initial release (rounded to half hours; for details concerning the data see


draft - 48 - 7.12.2001

Table 15 : File header of a SourceInfo/I source term file

format file contents (example)F-01F-02F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-03F-04F-05F-06F-06F-01F-07F-01F-01F-08F-08F-08F-08F-08F-01F-01F-08F-08F-08F-08F-08F-01F-01F-08F-08F-08F-08F-08F-08F-08F-08F-08F-08F-08F-08F-08F-08

=========================================================================# NCOMM = 10 ************ number of comment lines to follow#************************************************************************# Test Block B#************************************************************************# CSTFIL : Should contain file name (16 characters).# COMFR1, COMFR2 : Up to 80 characters. Mask for 80 characters follows below.#0========1=========2=========3=========4=========5=========6 ...........#123456789012345678901234567890123456789012345678901234567890 ...........#************************************************************************# ISTFIL = 0 1 | IRLTYP = 1 0 0 0 0 0 | IRLGRP used | Inventory necessary#************************************************************************ISTFIL = 0 1CSTFIL =FT1.TestBlockBIRLTYP = 1 0 0 0 0 0 0 0 0 0 0 0IRLGRP = 3CRLGID =NOBLE-JOD-AEROSOCOMFR1 =2 Puffs at 0.0 and 6.00 hours after EOC;COMFR2 =Inventory=Leitfaden; 2*50% noble gases & 2*0.5% iodine aerosols each# BEGFRE [h]BEGFRE = 0.00000E+00# HFS [m]HFS = 1.50000E+02 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 1.50000E+02 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00# QH [MW]QH = 2.50000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 2.50000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00# ANTJOD [%] (ELEMENTARY-ORGANICALLY BOUND-AEROSOLS)ANTJOD = 1.67000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 1.67000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 2.00000E-02 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 2.00000E-02 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 9.83100E+01 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 9.83100E+01 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00


draft - 49 - 7.12.2001

[Prognosis User Guide]).

• Lines D0+10,11: Obligatory comment lines.

• Next lines: Release height for all release time intervals (currently 24); 5 data entries per line(for details concerning the data specification see [Prognosis User Guide]).

• followed by : 2 obligatory comment lines.

• Next lines: Released thermal energy for all release time intervals (currently 24); 5 data entriesper line (for details concerning the data specification see [Prognosis User Guide]).

• followed by : 2 obligatory comment lines.

• Next lines: Iodine fractions for all release time intervals (currently 24); 5 data entries per line(for details concerning the data specification see [Prognosis User Guide]).

The flag for source term input mode must be set correctly for the chosen input mode => use thevalues given in Table 3 on p. 14.

File input modes FT1 to FT 4 refer to release groups and the release block name specified inthe source term file must be present in the file <in.releasegrps>: use an existing block or add anew block to the file <in.releasegroups> (see Chapter 6 for this). In any case, please note, thatthe number of release groups in the source term file (IRLGRP) must be equal to the number ofrelease groups in the file <in.releasegroups> (NRLGRP) diminuished by 1 (!).

File input modes FT6 and FT7 do not refer to release groups and the release block number/namein the file can be left zero (number) and blank (name), for instance (but the lines must be there!).

The file syntax is checked at runtime by task SETCHN which reports format errors, structureinconsistencies or inconsistencies between the release block names and release group numbersin the source term and release groups file and exits.

8.2 Input Mode Dependent Data - Source Term Input Mode FT1

Table 16 on p. 50 shows the input mode dependent data for source term input mode FT1 andthe respective FORTRAN format statements; the example given is for the release block "NOBLE-JOD-AEROSO" containing the three groups noble gases, iodine, aerosols.

The data follow immediately after the file header described in Chapter 8.1. The file syntax isdescribed below

Formats ("^" represents the blank character, "d" some digit 0...9)

F-01 : 81 arbitrary charactersF-02 : 9 characters, integer with 4 digitsF-03 : 8 characters, 6*(integer with 2 digits)F-04 : 8 characters, integer with 2 digitsF-05 : 8 characters, 16 characters (release block name the file refers to)F-06 : 8 characters, 80 characters (source term comment)F-07 : 8 characters, floating point number {sign}d.dddddE+ddF-08 : 5*(floating point number {sign}d.dddddE+dd "^")

Table 15 : File header of a SourceInfo/I source term file



draft - 50 - 7.12.2001

Comment lines

• Line 1,2,3,4 : Obligatory comment lines (lines ’#-----’ to ’PROZFR=’ in the example).

Then for each release group in the same order as in file <in.releasegrps> (!!!)

• One obligatory comment line.

• Fractions ([%]) of the initial core inventory released for the group for all release time in-tervals (currently 24); 5 data entries per line (for details concerning the data specification see[Prognosis User Guide]).

8.3 Input Mode Dependent Data - Source Term Input Modes FT3 and FT4

Table 17 on p. 51 shows the input mode dependent data for the source term input modes FT3and FT4 and the respective FORTRAN format statements. The data follow immediately afterthe file header described in Chapter 8.1.

The file syntax is described below. Note the additional specification of aersosol fractions! Whenthe file input mode is used, the only ways to give aerosol fractions is either to read them fromfile <in.aerosolfractions>.

Comment lines

• Line 1,2,3 : Obligatory comment lines.

followed by

Table 16 : Input Mode Dependent Data - Source Term Input Mode FT1

format file contents (example)F-01F-01F-01F-01F-01F-08F-08F-08F-08F-08F-01F-08F-08F-08F-08F-08F-01F-08F-08F-08F-08F-08

# --------------------------------------------------------------# Input are release fractions (3-Groups) in [%]# --------------------------------------------------------------PROZFR =# Noble gases 5.00000E+01 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 5.00000E+01 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00# Iodine 5.00000E-01 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 5.00000E-01 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00# Aerosols 5.00000E-01 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 5.00000E-01 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00


F-01 : 81 arbitrary charactersF-08 : 5*(floating point number {sign}d.dddddE+dd "^")


draft - 51 - 7.12.2001

• One line containing the release category name for the aerosol fractions (16 characters). Theaerosol fractions will be read from file <in.aerosolfractions> for the release category speci-fied.

• Four obligatory comment lines.


• Released activity for the noble gas group ([Bq]) for all release time intervals (currently 24);5 data entries per line (for details concerning the data specification see [Prognosis UserGuide]).


• Released activity for I-131 in case of FT3, or for the iodine group in case of FT4, respec-tively ([Bq]) for all release time intervals (currently 24); 5 data entries per line (for detailsconcerning the data specification see [Prognosis User Guide]).


• Released activity for the aerosol group ([Bq]) for all release time intervals (currently 24); 5data entries per line (for details concerning the data specification see [Prognosis User Guide]).

Table 17 : Input Mode Dependent Data - Source Term Input Modes FT3, FT4

format file contents (example)F-01F-01F-01F-02F-01F-01F-01F-01F-01F-08F-08F-08F-08F-08F-01F-01F-08F-08F-08F-08F-08F-01F-01F-08F-08F-08

# --------------------------------------------------------------# AEROSOL FRACTIONS# --------------------------------------------------------------CAECAT =DRSA-FK2# --------------------------------------------------------------# Input is released activity for n.gases, iodine, aerosols [Bq]# --------------------------------------------------------------ARGRBQ =# Noble gases 1.95995E+18 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 1.91708E+18 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 1.91025E+18 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 1.92406E+18 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 1.96411E+18 0.00000E+00 0.00000E+00 2.04799E+18# I-131 for FT3, total iodine for FT4 1.53303E+18 .00000E+00 .00000E+00 .00000E+00 .00000E+00 1.39312E+18 .00000E+00 .00000E+00 .00000E+00 .00000E+00 1.28250E+18 .00000E+00 .00000E+00 .00000E+00 .00000E+00 1.19501E+18 .00000E+00 .00000E+00 .00000E+00 .00000E+00 1.12638E+18 .00000E+00 .00000E+00 1.09528E+18# Aerosols 3.58553E+17 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 3.07671E+17 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 2.73647E+17 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 2.55348E+17 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 2.44895E+17 0.00000E+00 0.00000E+00 2.40114E+17


F-01 : 81 arbitrary charactersF-02 : 8 arbitrary characters, 16 characters containing the name specificationsF-08 : 5*(floating point number {sign}d.dddddE+dd "^")


draft - 52 - 7.12.2001

8.4 Input Mode Dependent Data - Source Term Input Mode FT5

Table 18 on p. 52 shows the input mode dependent data for source term input mode FT1 andthe respective FORTRAN format statements. The example given is for the release block "DRS-



F-01F-01F-01F-01F-01F-08F-08F-08F-08F-08F-01F-08F-08F-08F-08F-08F-01F-08F-08F-08F-08F-08F-01F-08F-08F-08F-08F-08F-01F-08F-08F-08F-08F-08F-01F-08F-08F-08F-08F-08F-01F-08F-08F-08F-08F-08

# --------------------------------------------------------------# Input is released activity (7-Groups) in [Bq]# --------------------------------------------------------------ARGRBQ =# Noble Gases 5.99000E+18 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 6.59000E+18 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00# Iodine 1.59000E+17 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 9.35000E+16 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00# Alkaline Metals 3.24000E+15 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 5.04000E+15 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00# Tellurium and Selenium 2.62000E+16 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 2.48000E+16 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00# Alkaline Earths 5.37000E+16 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 5.32100E+16 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00# Ruthenium Group 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00# Lanthanides 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00


draft - 53 - 7.12.2001

A_7_GROUPS" containing the seven groups considered in the German Risk Study, Phase A[DRSA1981]: noble gases, iodine, alkaline metals, tellurium and selenium, alkaline earths, ru-thenium group, lanthanides. A comparison with Table 16 reveals that although the file contentis different, the file structures are identical.

The data follow immediately after the file header described in Chapter 8.1. The file syntax isdescribed below.

Comment lines

• Line 1,2,3,4 : Obligatory comment lines (lines ’#-----’ to ’ARGRBQ=’ in the example).

Then for each release group in the same order as in file in.releasegrps (!!!)


• Activity released ([Bq]) for the group for all release time intervals (currently 24); 5 data en-tries per line (for details concerning the data specification see [Prognosis User Guide]).

8.5 Input Mode Dependent Data - Source Term Input Modes FT6 and FT7

Table 19 on p. 54 shows the input mode dependent data for source term input modes FT6 andFT7 and the respective FORTRAN format statements. The file structures are identical for inputmodes FT6 and FT7. The only difference is the physical unit of the data : [Bq] for FT6, and[Bq/s] for FT7.

The data follow immediately after the file header described in Chapter 8.1. The file syntax isdescribed below.

Comment lines

• Line 1,2,3,4 : Obligatory comment lines (lines ’#-----’ to ’ARISO=’ in the example).

Then for each nuclide

• Nuclide name; names should comply with the naming conventions described in [RO-DOS(WG1)-TN(96)-11] (see below).

• FT6 : Activity released ([Bq]) or FT7: Activity release rate [Bq/s] for above nuclide for allrelease time intervals (currently 24); 5 data entries per line (for details concerning the dataspecification see [Prognosis User Guide]).

Data may be given for any number and names of nuclides and in any order, as SourceInfo/Irecognises the nuclides by their names and skips any entry it is not interested in. However, if anuclide name does not comply with the naming conventions described in [RODOS(WG1)-TN(96)-11], it is not recognised and will simply be ignored.






draft - 54 - 7.12.2001

8.6 Use of Source Term Output Files <FT6.STERMout> and <FT7.STERMout> as InputFiles

Go to directory ~rodos/roextern/outall/{userID}/{runID}. There you will find the two files<FT6.STERMout> and <FT7.STERMout>, which contain the source term SourceInfo/I was

Table 19 : Input Mode Dependent Data - Source Term Input Modes FT6 and FT7

format file contents (example)F-01F-01F-01F-01F-09F-08F-08F-08F-08F-08F-09F-08F-08F-08F-08F-08F-09F-08F-08F-08F-08F-08F-09F-08F-08F-08F-08F-08............F-09F-08F-08F-08F-08F-08............

# --------------------------------------------------------------# Input is FT6: [Bq] or FT7: [Bq/s] for individual nuclides# --------------------------------------------------------------ARISO =# Kr- 88 1.38000E+18 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 3.20000E+17 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00# Xe-133 3.79000E+18 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 3.88000E+18 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00# Xe-135 8.25000E+17 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 2.39000E+18 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00# I -131 1.81000E+16 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 1.78000E+16 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00......................................................................................................................................................................................................# Cs-137 1.49000E+15 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 1.49000E+15 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00......................................................................................................................................................................................................



F-09 : 2 arbitrary characters, 7 characters containing nuclide name; names must comply with the naming conventions de-scribed in [RODOS(WG1)-TN(96)-11])


draft - 55 - 7.12.2001

using in the respective RODOS run. File <FT6.STERMout> contains the source term in formof source term input mode FT6, and file <FT7.STERMout> in form of source term input modeFT7.

Rename the file(s) you want to keep. It is recommended (but not cogent) to keep the identifier"FT6." or "FT7." as a prefix in the file name to ensure that the file name shows to which fileinput mode the file belongs - this helps to keep source term file archives managable. In any case,the new file name must not exceed 16 characters. After that, edit the file name inside the file inthe line starting with "CSTFIL=" to the new file name.

Copy the file(s) to directory ~rodos/roextern/data/sourceterm/input. After that, it is ready foruse in RODOS.


draft - 56 - 7.12.2001

9 Appendix D: Description of an Inventory Data File

If an inventory is required, the inventory data are read from a file. The file name must start withthe 5 characters "INVE." followed by the name of the inventory. The file must reside in directory~rodos/roextern/data/sourceterm/input/.

Table 20 on p. 57 shows a part of the inventory data file named <INVE.Leitfaden95> and therespective FORTRAN format statements. The file syntax is described below. The character "^"represents the blank character.

Document [RODOS(WG7)-TN(00)-01] gives hints for successful implementation of new orinventory data files into the RODOS system.

Comment lines




Data lines - general information about the inventory

• Line D0+1: Name of the inventory (up to 32 characters).

• Line D0+2: Nominal power [MW] for which the inventory applies.

• Line D0+3: Number of inventrory data subsets to follow (between 1 and 4). Each subset ap-plies to the thermal power specified in the previous line, and to a specific burn-up time in theunit [day] which will be specified in the following line.

• Line D0+4: Specification of the burn-up times in the unit [day] (specify zero for unused sub-sets).

Then for each burn-up subset

• One obligatory comment line (shown as bold in the example).

followed in turn by

• One line with nuclide names (between 1 and seven per line)

• One line with inventory data for above nuclides

ended by

• BLCKEND (if another subset follows) or FILEEND (nothing more to follow).

Data may be given for any number of nuclides in any order; however, each data line must notcontain less than one or more than seven entries. SourceInfo/I recognises the nuclides by theirnames and skips any entry which is not of interest. If a nuclide name does not comply with thenaming conventions described in [RODOS(WG1)-TN(96)-11], it is not recognised and will beignored.

The file syntax is checked at runtime by task SETINV, which reports format errors, structureinconsistencies, or inconsistencies between the inventory name in the file and the required in-


draft - 57 - 7.12.2001

ventory name.

Table 20 : Structure of an inventory file

format file contents (example)F-01F-02F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-03F-04F-04F-05F-01........F-06F-07........F-06F-07........F-06F-01............F-06F-01............F-06F-01........F-06F-07........F-06F-07........F-06

# ======================================================================# NCOMM = 11 ************ number of comment lines to follow **********# ======================================================================# INVNME maximally 32 characters.# INVPOW in [MW therm.]# INVNUM number of inventories with INVDAY in ascending order (max. 4).# INVDAY in [days]; 999 for equilibrium core.# RINVIN in [Bq] for time point <end of chain reaction>.# ======================================================================# Inventare aus Leitfaden fuer den Fachberater ... , Veroeffentlichungen# der SSK, Band13, 2.Aufl.(1995), ISBN 3-437-11639-8, Seiten 2-9# || Stand : 24.11.1999# ======================================================================INVNME =Leitfaden95INVPOW = 3733INVNUM = 4INVDAY = 1 33 333 999# ------------------ RINVIN fuer 3733 MW therm.; Betriebsdauer 1 Tage ...................................... ......................................# Kr- 85m Kr- 85 Kr- 87 Kr- 88 1.43E+18 4.08E+13 2.86E+18 4.03E+18 ...................................... ......................................# I -129 I -131 I -132 I -133 I -134 I -135 0.00E+00 2.36E+17 9.66E+17 4.16E+18 8.76E+18 6.76E+18 ...................................... ......................................# BLCKEND ---------# ------------------ RINVIN fuer 3733 MW therm.; Betriebsdauer 33 Tage ...................................... ............. and so on .............. ......................................# BLCKEND ---------# ------------------ RINVIN fuer 3733 MW therm.; Betriebsdauer 333 Tage ...................................... ............. and so on .............. ......................................# BLCKEND ---------# ------------------ RINVIN fuer 3733 MW therm.; Betriebsdauer 999 Tage ...................................... ......................................# Kr- 85m Kr- 85 Kr- 87 Kr- 88 1.04E+18 2.81E+16 1.95E+18 2.77E+18 ...................................... ......................................# I -129 I -131 I -132 I -133 I -134 I -135 0.00E+00 3.63E+18 5.32E+18 7.58E+18 8.21E+18 7.06E+18 ...................................... ......................................# FILEEND -----------


draft - 58 - 7.12.2001


F-01 : 81 arbitrary charactersF-02 : 9 arbitrary characters, integer with 4 digitsF-03 : 8 characters, 32 characters with inventory nameF-04 : 8 characters, integer with 5 digitsF-05 : 8 characters, 4 * (integer with 5 digits)F-06 : 7 * (3 blank characters, 7 characters with nuclide names)F-07 : 7 * (1 blank character, floating point number {sign}d.ddE+dd)

Table 20 : Structure of an inventory file



draft - 59 - 7.12.2001

10 Appendix E: Description of the Aerosol Fraction Library File <in.aero-solfractions>

File <in.aerosolfractions> contains a library of pre-defined aerosol release fractions for differentrelease categories. The file must reside in directory ~rodos/roextern/data/sourceterm/setup/.

Table 21 on p. 60 shows a part of the file and the respective FORTRAN format statements. Thefile syntax is described below. The character "^" represents the blank character.

Comment lines




Data lines

• Line D0+1: Number of lines following for data block with name CAECAT.

• Line D0+2: Name of data block to follow (max. 16 characters).

• Line D0+3: Name of nuclide release group parametrisation CAECAT refers to (max. 16 char-acters)

• Line D0+4: One obligatory comment line ("ANTAER =" in the example).

Then follow the data for this aerosol release block

• One line for each release fraction ANTAER

The fractions ANTAER must begiven EXACTLY for the number, sequence and type of releasegroups selected with parameter CAEBLK, including noble gases, iodine, and eventual othernon-aerosol groups. The fractions for the non - aerosol-groups are needed in order to synchro-nisethe aerosol fractions with the release groups, but they have no physical meaning and areignored in the calculations. Names for the groups may be written to the right of the fractions,but they are for control only.

Each aerosol fraction must be greater or equal 0 and less or equal 1. The sum of all aerosolfractions must not exceed 1.


draft - 60 - 7.12.2001

Table 21 : Structure of file <in.aerosolfractions>

format file contents (example)F-01F-02F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-01F-03F-04F-04F-01F-06F-06F-06F-06F-06F-06F-06F-03F-04F-04F-01F-06F-06F-06F-06F-06F-06F-06

#=======================================================================# NCOMM = 18 ************ number of comment lines to follow **********#************************************************************************# VERSION 04.09.2000#************************************************************************##The fractions ANTAER must be given EXACTLY for the number,sequence and type#of release groups selected with parameter CAEBLK, including noble gases,#iodine, and eventual other non-aerosol groups. The fractions for the non -#aerosol-groups are needed in orderto synchronise the aerosol fractions with#the release groups, but they have no physical meaning and are ignored in the# calculations. Names for the groups may be written to the right of the# fractions, but they are for control only.##NSKIP : Number of lines following for data block with name CAECAT.#CAECAT : Name of data block to follow (max. 16 characters).#CAEBLK : Name of nuc.rel.group parameterisation CAECAT refers to(max16 c).#ANTAER : Release fractions of 1 of initial inventory.##************************************************************************NSKIP =11-----------------------------CAECAT =DRSA-FK1CAEBLK =DRS-A_7_GROUPSANTAER =1.00000E+02 Noble gases7.97000E-01 Iodine5.00000E-01 Alkaline Metals3.50000E-01 Tellurium and Selenium6.70000E-02 Alkaline Earths3.80000E-01 Ruthenium Group2.60000E-03 LanthanidesNSKIP =11-----------------------------CAECAT =DRSA-FK2CAEBLK =DRS-A_7_GROUPSANTAER =1.00000E+02 Noble gases4.07000E-01 Iodine2.90000E-01 Alkaline Metals1.90000E-01 Tellurium and Selenium3.20000E-02 Alkaline Earths1.70000E-01 Ruthenium Group2.60000E-03 Lanthanides


F-01 : 81 arbitrary charactersF-02 : 9 arbitrary characters, integer with 4 digitsF-03 : 8 arbitrary characters, integer with 2 digitsF-04: 8 arbitrary characters, 16 characters with the name specificationsF-06 : floating point number {sign}d.dddddE+dd)


draft - 61 - 7.12.2001

11 Index

aerosol fractionsinput file for ~, detailed description, Chapter 10use of ~ in the source term calculations, Chapter 5.4.4

decay chainsinput file for ~, detailed description, Chapter 7input file for ~, overview, Chapter 5.6run time error reported by task "setup of ~", Chapter 4.2.2.1, Chapter 7.2use of ~ information in SourceInfo/I, Chapter 5.3, Chapter 5.4.1

iodine fractionsadjustments made to ~ by SourceInfo/I, Chapter 5.2.4

nuclidescalculation ~, definition of term, Chapter 5.3FixData ~, definition of term, Chapter 5.3FixData ~, what to do in SourceInfo/I on inclusion of new ones, Chapter 6, Chapter 7.2SourceInfo/I internal ~, definition of term, Chapter 5.3use of SourceInfo/I internal ~ information in SourceInfo/I, Chapter 5.3, Chapter 5.4.1

release blockdefinition of term ~, Chapter 5.5implemented ~s, Chapter 5.5

release duration -> see release times

release groupdefinition of term ~, Chapter 5.1input file for ~s, detailed description, Chapter 6input file for ~s, overview, Chapter 5.5run time error reported by task "setup of ~", Chapter 4.2.2.1, Chapter 6.2waste bin ~, definition of term, Chapter 5.3waste bin ~, why and how it is used, Chapter 5.3waste bin ~, syntax for specification, Chapter 6

release heightadjustments made to ~ by , Chapter 5.2.2

release times~ realised in SourceInfo/I, Chapter 5.1SourceInfo/I internal ~ clock, Chapter 5.4.1

source termentry modes for ~, definition of term, Chapter 2.1files for use as input~ formats, Chapter 8.1 to Chapter 8.5~ generated by SourceInfo/I, Chapter 3.1.1 and Chapter 8.6~ names, Chapter 8.1input modes for ~, definition of term, Chapter 2.1release groups possible in ~ calculations, Chapter 5.4.7


draft - 62 - 7.12.2001

runtime error reported by task "setup of ~", Chapter 4.2.2.2, Chapter 5.2~ interface for other programs, Chapter 2.1, Chapter 3time steps possible in ~ calculations, Chapter 5.4.7

trouble shooting on error exit, Chapter 4.2.2


draft - 63 - 7.12.2001

Document History

Document Title: Documentation of the SourceInfo/I software package in RODOSPV4.0F

Rodos number: RODOS(RA1)-TN(01)-01Version and status: Version 1.3 (draft)Author/Editor: C. LandmanAddress: ForschungszentrumKarlsruhe, Technik und Umwelt, P.O.Box 3640,

D-76021 KarlsruheIssued by: C. LandmanDate of Issue: 7.12.2001Circulation: - none -File Name: ratn0101v40f2.frm

Date of print: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.12.2001