user guide for the long term countermeasure model lcmt6.2 of rodos … · 2008. 4. 15. · version...

User Guide for the Long Term Countermeasure Model LCMT6.2 of RODOS-PV6.0

- 1 -

User Guide for the Long Term Countermeasure Model LCMT6.2 of RODOS-PV6.0

Tom Charnock

Contents

USER GUIDE FOR THE LONG TERM COUNTERMEASURE MODEL LCMT6.2 OF RODOS-PV6.0 ............................................................................................................1

1 Overview.................................................................................................................................................................3

2 Starting the long-term counter measure module ........................................................................................5 2.1 Before the run...............................................................................................................................................5 2.2 Starting the module .....................................................................................................................................5 2.3 Passing archived LCMT results to the graphics server.........................................................................9

3 Input options for long-term countermeasures: terrestrial (LCMT)................................................... 12 3.1 Introduction................................................................................................................................................12 3.2 LCMT Initialisation windows .................................................................................................................12

3.2.1 Selection of long term countermeasure module ..............................................................................14 3.2.2 (LCMT6-1.0) Selection of tasks ........................................................................................................14 3.2.3 (LCMT6-2.0) Selection of input for relocation + agr. countermeasures....................................15

3.3 Initialisation windows for relocation and agricultural countermeasures (Option 1)......................16 3.4 Initialisation windows for relocation (Options 1 and 2).....................................................................16

3.4.1 (LCMT6-3.0) Re location: Selection of input..................................................................................16 3.4.2 (LCMT6-3.3) Relocation: Relocation criteria .................................................................................17 3.4.3 (LCMT6-3.4) Relocation: Decontamination options.....................................................................19 3.4.4 (LCMT6-3.4.1) Decontamination strategy options........................................................................20 3.4.5 (LCMT6-3.5) Relocation: Dose options ..........................................................................................25

3.5 Initialisation windows for agricultural countermeasures (Options 1, 3 and 5) ...............................26 3.5.1 (LCMT6-4.01 or LCMT6-4.02) Agricultural countermeasures: Selection of input.................26 3.5.2 (LCMT6-4.3) Agr. countermeasures: Selection of intervention levels for food groups..........27 3.5.3 (LCMT6-4.5) Agr. countermeasures: Selection of effect of relocation......................................28

3.6 Initialisation windows for decontamination only (Option 4) .............................................................29 3.7 LCMT dynamic windows ........................................................................................................................30 3.8 Dynamic windows for user defined areas .............................................................................................30 3.9 Dynamic window for worker doses........................................................................................................35 3.10 Dynamic windows for the relocation (Options 1 and 2).....................................................................37 3.11 Dynamic windows for the agricultural subsystem (Options 1, 3 and 5) ..........................................44 3.12 Dynamic windows for decontamination (Option 4)............................................................................52 3.13 Modifying input data.................................................................................................................................54

3.13.1 Files which can be changed...........................................................................................................54 3.13.2 Files which should remain unchanged........................................................................................55

4 Results and endpoints ...................................................................................................................................... 56 4.1 Graphical output ........................................................................................................................................56 4.2 The evaluation subsystem endpoints......................................................................................................63 4.3 Abbreviations used....................................................................................................................................68

5 References ........................................................................................................................................................... 71

Version 1 User Guide for the Long Term Countermeasure Model LCMT6.2 of RODOS-PV6.0

- 2 -

Document History........................................................................................................................................................ 72


- 3 -

1 Overview

This document describes Version 6.2 of the Late Countermeasures Module (LCMT). LCMT includes the facility for the user to define countermeasure zones graphically and for relocation and decontamination strategies to be passed to the decision evaluation module (ESY). LCMT also includes a methodology for calculating the dose received by workers undertaking the countermeasures. LCMT version 6.2 has various usability enhancements over previous versions, identified and implemented under the EVATECH project. These include:

1. The user may select a subset of the food passed from FDMT to analyse. In previous versions, LCMT either performed calculations for all foods passed or, in ESY mode, performed calculations for just one food.

2. There is no longer a specific ESY (evaluation subsystem) mode for agricultural countermeasures.

3. The user may create a large ESY file – a comprehensive set of endpoints – or a very much smaller ESY file.

4. The “disposal and stopping production” agricultural countermeasure has been modified to produce endpoints comparable with other agricultural countermeasures.

5. The agricultural countermeasures “change of crop” and “change of land use” have been implemented.

6. Additional run information is stored with each run and with each individual countermeasure within each run.

LCMT considers three major groups of countermeasures: relocation of the population, decontamination of inhabited land, and agricultural countermeasures. LCMT links closely with other modules of RODOS, particularly the Food chain and Dose Module (FDMT) which provides input on activity concentrations in air, foods and animal feedstuffs, deposition rates as a function of location, nuclide and time, and models to calculate doses from the relevant exposure pathways without countermeasures. Using this information, along with information on the countermeasure criteria and on the effectiveness of countermeasures in reducing external gamma doses from material deposited on the ground, reducing resuspension and in reducing activity concentrations in foods, LCMT calculates endpoints of use to a decision-maker for scoping possible countermeasure strategies.

The principal endpoints evaluated within LCMT include, for each countermeasure, the extent (area, quantities of food, population numbers) and duration of restrictions, doses received and saved and additional data required for evaluating the costs of countermeasure


- 4 -

implementation. A selection of key results are transferred to the RODOS graphical system for presentation to the user in the form of maps, plots of information as a function of time etc. Information is also passed to the economics and health sub-modules of RODOS Late Consequences Module. Information can also be passed to the evaluation system (ESY) for formal decision evaluation.


- 5 -

2 Starting the long-term counter measure module

2.1 Before the run

To run LCMT, the results of a previous run of FDMT and, dependent on the configuration, from EmerSim, are required as input data to LCMT. Make sure that the Load list selected is appropriate. When the effects of evacuation calculated by EmerSim have to be considered in LCMT, a Load list must be activated which contains the Data Class emerlcmt with the arrays:

• kennev(2520)

• outeva.

By default, a Load list without consideration of EmerSim is implemented in the system. In this case, kennev is loaded from the assign-file where it is filled with zeros (indicating that no evacuation has occurred).

2.2 Starting the module

An interactive computation run of LCMT is started in the usual way:

• Ensure the graphics server is running by pressing [Graphics].

• In the Main Dialogue window of RODOS select the button [Interactive].

• In the Interactive Manager window choose [Configuration] and then [Importing Result-Dataset To] from the menu bar at the top to select the results of a previous runs of FDMT and, optionally, EmerSim as input to LCMT.


- 6 -

• A window called Target-Programs appears.

• Press [LCMT] and a window appears in which all archived input module runs are listed.

There are two possible modes of operation in LCMT:

1. only a single previous run of the FDMT module is input into LCMT,

2. archived runs of both the early countermeasure module EmerSim and FDMT are input in LCMT.

The second mode is necessary if the impact of evacuation on relocation is to be included in LCMT or if the user wishes to set relocation or decontamination countermeasure zones to match the area of evacuation calculated by EmerSim. The user must provide the load list accordingly, either with or without the inclusion of EmerSim.

An archived run is selected by clicking on it and then pressing the button [Apply], control then returns to the Interactive Manager window. To select a second run, repeat the procedure by pressing


- 7 -

[Configuration] and [Importing Result-Dataset To] on the Interactive Manager window.

• When the required input archived module runs have been selected, click on the button [LCMT] in the Interactive Manager window to start a new run of LCMT.

• A Start window for the definition of the Run-Id pops up, the Run-Id (here ‘lcmt’) has to be entered by the user.

The Run-ID can be any character string using letters and numbers (maximum 12 characters) and must be different from the Run-IDs of previous runs that are still archived in the database.

• When [Initializing] is pressed the Program Initialization window is displayed. From here the input parameters and endpoint options can be modified via a set of initialisation windows access by pressing [LCMT62], as described in Section 3.

• When the selections and changes are complete the user leaves the set of initialisation windows and returns to the Program Initialization window. The button [LCMT62] will now be greyed to indicate the selections have been made. At this point three options are available.

1. To apply the selection made in the set of initialisation windows click on [Apply] and then [Return].


- 8 -

2. To make new selections and changes in the set of Initialisation windows click on [unlock buttons ] to ungrey [LCMT62], and then [LCMT62] again to re-enter the windows.

3. To discard the selections and start the program with the previous selections click on [Return].

If the user presses [Return] without [Apply] or chooses not to enter the Program Initialization window in the first place, the input-parameters and endpoint options used will either be a default set or based on the previous LCMT run depending on the options chosen in the Interactive Manager window.

• The program run is started by clicking on [Start ] in the Start window.

NB After pressing [Initializing] or [Start] in the Start window an info message may be displayed that indicates there is no load list available and that an automatic copy of the load list will be generated by the system. Wait until that process has finished. Then press [Initializing] or [Start] again and continue.

After the program has been started, a Control & Services window appears. This control window is divided into an upper and lower part. The upper part contains the Run-ID of the currently selected run as well as four buttons to control the progress of the run. The lower part contains five buttons with which various services can be chosen. All buttons are described in detail in the User Guides for the RODOS system and the Graphics Server.


- 9 -

2.3 Passing archived LCMT results to the graphics server

Graphical data from LCMT is archived by RODOS in the usual way.

• Archived graphical output of LCMT can be displayed by selecting [File] and [Display Results] in the menu bar of the Interactive Manager window of RODOS.

• The Program Groups window is displayed which lists all the modules in RODOS as buttons.

• By pressing the button [LCMT] to select the LCMT module, a window pops up with the list of all LCMT runs archived.


- 10 -

• One run out of the list has to be selected and the button [Apply] has to be pressed. If they are not already present, two windows appear: The Control & Services window and the Application List window.

The Application List window lists all the runs of any module that are currently resident in memory. Runs may be in memory because they are currently running, because they have been run within the current RODOS session or because they have been retrieved from the archive. The Control and Services window gives information and control of whichever run is selected in the Application List window.

• The next step is first to select the run in the Application List window by clicking on it (colour does not change) and second to select the [Graphics] button in the Control & Services window. A window with the hierarchy of all results archived for this run is displayed.


- 11 -

• Descend the hierarchy and select the endpoints of interest by clicking on them. Selected end-points are marked with a red cross. Alternatively, select all endpoints by pressing [All]. Once the required selection is made press the [Apply] button to pass the results to the Graphics Server. If no further results are required, press [Close] to close the window.


- 12 -

3 Input options for long-term countermeasures: terrestrial (LCMT)

3.1 Introduction

The calculation of the effects of long-term countermeasures requires the user to choose options by the use of three methods.

• The overall options for the calculation runs are chosen by accessing the RODOS initialisation windows before the program is started (see Section 3.2).

• In addition a number of dynamic windows may appear as the program progresses (see Section 3.7).

• The parameter values describing the effectiveness of the chosen options, which are used during run-time of LCMT, are chosen by examining, and editing where necessary, a number of data files containing default or user-modified input values pertaining to LCMT (see Section 3.13).

3.2 LCMT Initialisation windows

This section describes how the user can set options for the calculations within the initialisation windows. The advantage of initialisation options is that once they have been set they can be used repeatedly for several LCMT runs without the need to re-entering them on each run.


- 13 -

LCMT6-1.0 Selection of tasks

Option 1: Relocation + agricultural countermeasures• LCMT6-2.0 Selection of input for relocation + agricultural countermeasures

• Input for relocation: LCMT6-3.0 Selection of input• options as in “Option 2: Relocation only – LCMT6-3.0 selection of input“

• Input for agr.countermeasures: LCMT6-4.01 Calculations• options as in “Option 3: Agricultural countermeasures only – LCMT6-4.02“• Selection of effects of relocation: LCMT6-4.5 Effect of Relocation

Option 2: Relocation only• LCMT6-3.0 Selection of input

• Comment: LCMT6-3.1 Comment• Selection of relocation criteria: LCMT6-3.3 Options• Decontamination options: LCMT6-3.4 Decontamination options

• Decontamination strategy options: LCMT6-3.4.1• Decontamination techniques option: LCMT6-3.4.2• Decontamination factors option: LCMT6–3.4.3

• Dose options: LCMT6-3.5 Outdoor or normal living doses

Option 3: Agricultural countermeasures only• LCMT6-4.02 Calculations

• Comment: LCMT5-4.1• Selection of intervention levels: LCMT6-4.3 Food groups

• Food group 1: LCMT6-4.3.1 Intervention levels (milk products)• Food group 2: LCMT6-4.3.2 Intervention levels (others except beer)• Food group 3: LCMT6-4.3.3 Intervention levels (beer)• Food group 4: LCMT6-4.3.4 Intervention levels (not used)• Food group 5: LCMT6-4.3.5 Intervention levels (not used)

Option 4: Decontamination only• LCMT6-3.4.0 Decontamination only

• Decontamination options: LCMT6-3.4 Decontamination options• Decontamination strategy option: LCMT6-3.4.1• Decontamination techniques option: LCMT6-3.4.2

• Dose options: LCMT6-3.5 Outdoor or normal living doses

Figure 3-1 hierarchy of windows for selection of tasks and corresponding options. (Each window is numbered to indicate its position in the hierarchy and to aid cross-referencing).

Figure 3-1 provides an overview of the input options for the user and shows the sequence of initialisation windows. The windows are organised in a tree-structure. There are 4 basic options that lead the user to further windows for modifying input parameters or selecting specific endpoints:

1. Relocation and agricultural countermeasures Option 1 (default)

2. Relocation only Option 2

3. Agricultural countermeasures only Option 3

4. Decontamination only Option 4


- 14 -

Most of the windows have the usual buttons for [Close], [Update] and [Help]. The close option does not modify any settings that the user has changed. The [Update] button saves the settings entered by the user. Further explanation of the window options is given in the [Help] window.

3.2.1 Selection of long term countermeasure module

By selecting [Initializing] in the Start window (see Chapter 2) and then selecting [LCMT62] in the following Program Initialization window, the Dataset Selection window comes up.

This window switches between modification of either the options from the previous initialisation, or the option from another initialisation made earlier. After pressing the appropriate button, the Initialization windows are called to define parameter values to be used by the LCMT calculations.

Whichever button is pressed, the first window (LCMT 1.0) in the LCMT input hierarchy is displayed.

3.2.2 (LCMT6-1.0) Selection of tasks

The user can select one of the first four options given in this window. The fifth option is not used in initialisation and should be ignored.

• Relocation and agricultural countermeasures - Option 1 (default)


- 15 -

Option 1 is a combination of Options 2 and 3 described below – relocation only and agricultural countermeasures only. Selecting this option takes the user to window LCMT6-2.0.

• Relocation only - Option 2

Under Option 2, LCMT will assess the impact of relocation, with a user-selected decontamination strategy (including that of no decontamination). Selecting this option takes the user to window LCMT6-3.0.

• Agricultural countermeasures only - Option 3

Under Option 3, LCMT will assess the impact of agricultural countermeasures. For up to 5 foods selected in FDMT, the user may choose up to 12 agricultural countermeasures including the decontamination of agricultural land. Selecting this option takes the user to window LCMT6-4.02.

• Decontamination only - Option 4

Under option 4, LCMT will assess the impact of a chosen decontamination strategy on external and resuspension doses. No calculations involving relocation or agricultural countermeasures are undertaken. Selecting this option takes the user to window LCMT5-3.4.1.

[Close] exits the window without storing any selections from this or subordinate windows, [Update] confirms any selections.

3.2.3 (LCMT6-2.0) Selection of input for relocation + agr. countermeasures

This window is presented only if the default option 1 is selected in LCMT6-1.0. From here the user may review and modify the inputs required for relocation and for agricultural countermeasures.

• Input for relocation

Selecting this option takes the user to window LCMT6-3.0.

• Input for agricultural countermeasures

Selecting this option takes the user to window LCMT6-4.01.


- 16 -

[Close] exits the window without storing any selections on subordinate windows, [Update] confirms any selections.

3.3 Initialisation windows for relocation and agricultural countermeasures (Option 1)

The first initialisation window for Option 1, allows the user to assess the windows for initialising the relocation subsystem (section 3.4) or the agricultural subsystem (section 3.5).

3.4 Initialisation windows for relocation (Options 1 and 2)

The input windows for the relocation options are identical for the two options:

• Relocation + Agricultural countermeasures (Option 1)

• Relocation only (Option 2)

3.4.1 (LCMT6-3.0) Relocation: Selection of input

• Comment

This option takes the user to window LCMT6-3.1, which allows entry of a brief comment.

• Selection of relocation criteria


- 17 -

This option takes the user to window LCMT6-3.3

• Decontamination options


• Dose options


[Close] exits the window, updates are made in the individual selections.

3.4.2 (LCMT6-3.3) Relocation: Relocation criteria

In this input window the relocation intervention and withdrawal criteria are defined.

The criteria for implementing relocation are made EITHER on the basis of potential outdoor external and resuspension doses OR expected normal living external and resuspension doses. The default is Normal Living. The user toggles between the options by checking and unchecking the button [Compare against outside doses]. The doses displayed in the graphics window and those passed to the HEALTH-module are always specified separately irrespective of the dose that the relocation criteria are based on.


- 18 -

In LCMT, two types of relocation are considered – temporary and permanent. Permanent relocation is the removal of people from an area with no expectation of their return. However, the land may be released at a later stage and resettled by different individuals. Temporary relocation is the removal of people from an area for an extended but limited period of time.

Note that both temporary and permanent relocation areas may be identified by LCMT following an accident.

The user can modify the dose (Sv) and integration periods (days) for imposition and relaxation of relocation, the time when relocation is first considered (days), the implementation time for relocation (days), the maximum duration of temporary relocation (days) and the minimum duration of relocation (days).

NB if the user sets a minimum duration for relocation that is larger than maximum duration of temporary location, LCMT will calculate all relocation as permanent.

Default criteria and timings are given in Table 1.

At each location, LCMT finds the start of the period when the imposition criterion is exceeded and the start of the period when the dose is below the relaxation criteria. Both the algorithm for finding the imposition and relaxation proceed on daily steps.

NB LCMT does not check whether future doses exceed the relaxation criteria again.

Figure 3-2, illustrates the procedure for calculating the relocation period. The length of AB is the imposition-criteria-period, AB is the first period in which the dose exceeds the imposition-criteria dose. The length of CD is the relaxation-criteria-period, CD is the first period after A in which dose drops below the relaxation-criteria-dose. The period of relocation is the period AC.


- 19 -

A B

C D

Relocation period

Time

Dose

Figure 3-2 Example of finding the period of relocation at an area.

Table 1: Default relocation criteria and timings

Parameter Default value Imposition criteria 0.015 Sv Time period 365 days Relaxation criteria 0.015 Sv Time period 365 days Time when relocation first considered 1 day Implementation time: temporary relocation

permanent relocation 0 days 0 days

Maximum duration of temporary relocation 200 days Minimum duration of relocation 28 days

[Close] exits the window without storing any selections/user changes, [Update] confirms any selections.

3.4.3 (LCMT6-3.4) Relocation: Decontamination options

Window LCMT6.3.4 is accessed from LCMT6-3.0.


- 20 -

The user can indicate whether decontamination is to be considered. If the [No decontamination] option is selected, no decontamination occurs. This is the default.

If [Decontamination] is pressed the window LCMT6-3.4.1 is displayed.

[Close] exits the window without storing any selections, [Update] confirms any selections.

3.4.4 (LCMT6-3.4.1) Decontamination strategy options

Selected techniques and implementation times can be considered by selecting [Techniques] in window LCMT6-3.4.1. The alternative is that the user can consider a selection of decontamination factors, urban surfaces and implementation times by selecting [Decontamination factors ] in window LCMT6-3.4.1.

[Close] exits the window without any selection. If the decontamination factors option is chosen no output will be generated for the Economics module or for decision evaluation module (ESY).

3.4.4.1 The decontamination option "Techniques"

If [Techniques] is selected in LCMT6-3.4.1, the user can choose up to five technique and implementation time combinations from the list provided in LCMT6-3.4.2. A technique is chosen by entering a ‘1’ in the box adjacent to an implementation time for that technique. A ‘0’


- 21 -

indicates that the technique is not selected. More than one implementation time may be selected for a given technique. If more than five techniques and implementation times are selected, only the first five selections are considered. By default the first two options are selected (1) and the remainder are not selected (0). The techniques available are listed in Table 2.


- 22 -

Table 2: Default work rates and waste arising for decontamination techniques

Technique

Skim and burial ploughing Rotovating / digging gardens

Shrub and plant removal Fire hosing roads

Grass cutting Vacuum sweeping roads

Road planing Sand blasting external walls

Standard ploughing Roof brushing

Soil removal Vacuuming indoors

Double digging gardens Tree / bush removal

3.4.4.2 The decontamination option "Decontamination factor"

If [Decontamination factor] is selected in LCMT6-3.4.1, the user can choose up to five decontamination factor, urban surface and implementation time combinations from the list provided in LCMT6-3.4.3. A combination is chosen by placing an index number for the chosen decontamination factor, surface and implementation time against each strategy, taken from the lists in the top part of the window. These options are listed in Table 3.


- 23 -

Table 3: Index values for DF, surface and implementation time

Decontamination Factor (DF)

Urban surface Implementation Times, days

Index Index Index 1.2 1 Walls 1 1 1 1.5 2 Roofs 2 7 2 2 3 Internal surfaces 3 14 3 3 4 Paved (roads and

pavements) 4 30 4

5 5 Soil and grass 5 90 5 10 6 Trees 6 365 6 50 7 730 7

100 8 3650 8

3.4.4.3 Timing of decontamination techniques Within RODOS, releases of up to 48 days duration may be modelled (see Reference 3, RODOS(RA3)-RP3_01). LCMT allows decontamination to be performed before the end of the release. However, the user should be aware of the consequences of doing this.


- 24 -

Surface activity is passed from FDMT as a time series of activity concentrations for each location and deposition day1. If the user chooses to decontaminate before the end of the release, the profiles subsequent to the decontamination will not be affected. Profiles for deposition that occurred before the decontamination will be affected from the time of decontamination onwards. See Figure 3-3.

The longer material remains on a surface the more it adheres to that surface. Therefore, for decontamination techniques implemented after the deposition has stopped, material deposited early in the deposition period may be less easily removed than material deposited later during the deposition period. This will be especially true for techniques that use a mechanical action to remove material from a surface as opposed to those techniques that remove the surface itself or bind the material within the surface. LCMT uses an ‘effectiveness time window’ in order to model this. The ‘effectiveness time window is measured back towards time zero from the time of decontamination. Only deposition occurring within the window is affected by the technique, and a single uniform decontamination factor specific to the technique is assumed.

LCMT assumes that techniques specified by a DF-surface-implementation combination have an effectiveness-window that extends to the beginning of the release from the time of implementation of the decontamination. Currently for named techniques, the default data files also assume that the effectiveness window extends to the start of the release. This is because of the paucity of the data available. This is an optimistic assumption, however it is only optimistic when applied to very long duration releases and to techniques that remove deposited material, whilst leaving the surface intact, and are applied near to the end of the release. However, LCMT is coded such that if the data files were revised to specify a shorter effectiveness window, this would be modelled explicitly within LCMT, as described in the previous paragraph.

1 Strictly they are passed as a set of normalised activity concentrations.


- 25 -

a

b

Time (days)

day 1day 2day 3day 4

Do

se d

ue t

od

ep

osi

ted

act

ivit

y

1 2 3 4 5 6 7 8Time (days)

day 1day 2day 3day 4

Do

se d

ue t

od

ep

osi

ted

act

ivit

y

1 2 3 4 5 6 7 8

Figure 3-3 (a) Summation of deposition-day dose profiles without decontamination. (b) Summation of deposition-day dose profiles with decontamination applied at 2 days. In (b) the profiles for deposition on days 3 and 4 are unaffected, the profiles for deposition on days 1 and 2 are only affected from the end of the second day

3.4.5 (LCMT6-3.5) Relocation: Dose options

The Dose Options window LCMT 6-3.5 is accessed from LCMT6-3.0. Here the user can specify the type of doses that should be presented as results in the graphics and also whether the effects of evacuation should be included in the calculation of doses. Two selections can be activated:


- 26 -

• Pressing the button [Display outdoor doses] results in LCMT calculating the doses without any shielding (i.e. staying outdoors). Otherwise normal living conditions with the corresponding location factors are calculated. The type of doses selected by the user on this window will determine both the doses displayed in the graphics server and also the doses passed to the HEALTH-module and the decision evaluation module (ESY). If the HEALTH-module is to be used, then normal- living doses should be chosen.

• Pressing the button [Include the effect of evacuation] allows the user to consider the dose reduction due to evacuation as calculated in EmerSim. If this option is chosen, the user has to ensure that an appropriate run of EmerSim is available in the archive and that the correct Load list (which loads both FDMT and EmerSim results) is activated (see also section 2.1). If the selected Load List is not correct, the user will receive a warning message saying that the impact of evacuation could not be considered, even if it is selected in the input window here.


3.5 Initialisation windows for agricultural countermeasures (Options 1, 3 and 5)

3.5.1 (LCMT6-4.01 or LCMT6-4.02) Agricultural countermeasures: Selection of input

Following the window LCMT6-2.0, options related to agricultural countermeasures will be made available via the window LCMT6-4.01 (Option 1) or LCMT6-4.02 (Options 3 and 5). If Option 1 is selected, the additional possibility of investigating the effect of relocation on the agricultural production is available (LCMT6-4.01).


- 27 -

[Close] exits the window, updates are made in the individual selections.

3.5.2 (LCMT6-4.3) Agr. countermeasures: Selection of intervention levels for food groups

Selecting ‘selection of intervention levels’ gives window LCMT6-4.3.

This window allows the user to define intervention levels for up to five food groups. The food groups 1 to 3 are used by default and default data are only provided for these three groups. The user may define intervention criteria for additional food groups (or modify the default values) by changing the data (see section 3.13):

• Group 1: milk and milk products (excluding cheese)

• Group 2: all others except liquid foods

• Group 3: liquid foods (only beer at the moment)

• Group 4 and 5 are not used in the data sets

The maximum permissible activity concentrations in foodstuffs, defined by the European Commission in 1987 – 1989 are set as default values.

As an example the input window for the first food group is displayed.


- 28 -


3.5.3 (LCMT6-4.5) Agr. countermeasures: Selection of effect of relocation

When relocation and agricultural countermeasures are selected (Option 1), the impact of relocation on agricultural production can be defined. For areas with temporary relocation, it is assumed that crop production and livestock management are unaffected for the duration of relocation. Only areas with permanent relocation may have the normal agricultural production interrupted. Three options are available for both arable crops and livestock production as shown in LCMT6-4.5:

• production is not affected, i.e. pre-accident production is continued;

• production of all crops and/livestock ceases;

• production is continued only for specified foods.


- 29 -

When selecting the second or third option, the default settings from the database will be activated (see Section 3.7). There is no choice via the input windows to select further parameters.


3.6 Initialisation windows for decontamination only (Option 4)

The considerations and issues to take into account when analysing decontamination are the same as when analysing decontamination in conjunction with relocation. The same windows are used in both cases.

After selecting Option 4 (decontamination only) on window LCMT6-1.0 (see Section 3.2.2), the user is presented with window LCMT6-3.4.0.

• Decontamination strategy option

This option takes the user to window LCMT6-3.4.1. This window is described in section 3.4.4.

• Dose options

This option takes the user to window LCMT6-3.5. This window is described in section 3.4.5.


- 30 -

3.7 LCMT dynamic windows

During a run of LCMT, dynamic windows are displayed to the user which request information and present choices on how the run should proceed. The windows displayed depend on the options chosen in the initialisation windows, as well as options chosen in previous dynamic windows.

Most of the windows have the usual buttons for [Close], [Update] and [Help]. The close option does not modify any settings that the user has changed. The [Update] button saves the modifications made.

The use of dynamic windows means that there are many more pathways through LCMT version 6.2 than there were in previous versions. Some options will produce results that are equivalent to previous versions other options will produce results that are subtly different. The label (LCMT5) next to an option indicates that the option will replicate the behaviour of the previous version of LCMT.

3.8 Dynamic windows for user defined areas

In LCMT, the user is able to define or modify the areas or zones over which countermeasure or calculations are performed (See Reference 4, RODOS(RA4)-RP04_01). In LCMT, zones are delineated by marking grid-squares on a map. For whatever purpose the zone is defined, the procedure is the same and the dynamic windows presented are similar. The example below is for the decontamination zone, however it could be for relocation or for food countermeasure zones.

As the module progress the user will first be asked if the zone is to be defined graphically or by some other method. If some other method is selected (for example dose criteria) there may then be an opportunity for the user to graphically modify the calculated area. Whether they have chosen to graphically define an area or to modify a calculated area, the user is presented with an Input Mode window that gives three input choices.

1. Edit calculated zone

2. Modify the archived zone

3. New zone input


- 31 -

Selecting any of options will access the dynamic windows that allow the user to graphically define or modify the area, however each has slightly different behaviour. Option 1 should only be selected if the zone has previously been calculated by some other method or has been modified previously. Option 2 allows the user to selected an archived LCMT run and to use the zone defined within (whether that area was defined graphically or by some other method). If Option 2 is chosen any calculated or modified area will be discarded. Option 3 allows the user to start from a blank grid. If Option 3 is chosen, any calculated or modified area will be discarded. The overall procedure for graphically defining or modifying zones is illustrated in Figure 3-4.

The user is presented with options e.g.

Calculate zone by method 1

Calculate zone by method 1 and then modify graphically

Calculate zone by method 2

Calculate zone by method 2 and then modify graphically

Define zone graphically

An input mode window ispresented:

Edit calculated zone

Modify archived zone

New Zone Input

Close

Apply method 1

Apply method 2

Only press Close when zonehas been defined eithergraphically or by a calculationmethod

Retrieve calculated and/orpreviously modified area. Allowuser to modify it, if no such areaexists then present a blank map

Discard any calculated and/ormodified zone and allow user toselect the zone from an archived runto modify

Discard any calculated and/ormodified zone and present user witha blank map to modify

Start zone definition

Zone definition finished

Apply method 1

Apply method 2

Figure 3-4 Zone definition process.

If the user chooses [Edit Calculated] or [New Zone Input ] a sequence of windows begins that is illustrated in Figure 3-5. If the user selects [Modify Archived Zone ] two additional windows are added to the sequence as illustrated in Figure 3-6. Whichever, route is chosen the user will eventually be required to interact with the Graphics Server.


- 32 -

If the user selects the 1st or 3rd Option, theGraphics Input window is displayed

When called from the Graphics Input windowthe graphics server will appear as the usual mapwindow along with a second window withvarious options. On the actions tab-sheet selectmodule on the Save to drop down. Click [Save]when edits* are complete to return to theGraphics Input window.

*Editing processes described below

From the Graphics Input window the GraphicsServer can be called. When returning from theGraphics Server, click [Close] to discard edits or“Update” to write them to shared memory

Figure 3-5 Sequence of dynamic windows if the user selects [Edit Calculated Zone] or [New Zone Input].


- 33 -

If the user selects the 2nd Option, the ArchivedSelection window is displayed

From the Archived Selection window the usercan call up a list of archived runs by pressing[Continue]. Press [Close] to return to the InputMode window.

When called from the Graphics Input windowthe graphics server will appear as the usual mapwindow along with a second window containingvarious options. On the Actions tab-sheet selectModule on the Save to drop down. Click [Save]when edits* are complete to return to theGraphics Input window.

*Editing processes described below

From the Graphics Input window the GraphicsServer can be called. When returned from theGraphics Server, click [Close] to discard edits or[Update] to write them to shared memory

Select a previous archived run and press [Apply]to go to the Graphics Input window. Press closeto return to Archived Selection.

Figure 3-6 Sequence of windows if the user selects “modify Archived Zone”.


- 34 -

The Graphics server appears as two windows, the first is the familiar graphics map window, the second is the Input window. Before marking grid-squares on the map the user must perform the following steps.

• Select the Action tab-sheet on the Input window.

• Set the Save to drop-down list to Module.

• Click the [User Input] button.

Grid-squares may be marked with one of two values. The value “0” indicates grid-squares that are not part of the zone. Therefore, “0” should be used to erase parts of the zone. The second value, for example Decontaminate, indicates grid-squares that are part of the zone.

There are two modes for drawing onto the map, Pencil Mode and Area Mode.

To draw or erase onto the map in Pencil Mode, select the appropriate value. Position the mouse pointer on a location and hold the left mouse-button down. Drag the pointer to create a line. The line is finished when the mouse-button is released.

To draw or erase onto the map in Area Mode, select the appropriate value. Click a location with the left mouse-button. Move the mouse-pointer to a second location and click the left mouse-button to draw a line. Move the mouse-pointer to a third location and click to create a polygon. Repeat to extend the polygon. Click the right mouse-button to finish.

Zones are marked into the underlying grid. Because the grid is more coarse away from the centre, the area marked will not follow exactly the line or area drawn. The process of marking areas in both Pencil and Area mode and the zones created are illustrated in Figure 3-7.


- 35 -

Left click to start line

Left click in anotherlocation to extend theline

Left click in anotherlocation to extend theline further and createa polygon. Right clickto finish

Refresh the mapwindow to see thearea marked on theunderlying grid

Pencil mode Area mode

Locate the startingpoint and hold the leftmouse-button down

Drag themouse-pointer todraw a line

When the line isfinished release theleft mouse-button

Refresh the mapwindow to see the linemarked on theunderlying grid

Figure 3-7 Marking grid-squares on a map.

When the zone has been marked onto the map, press [Save] to return to the Graphics Input window. Press [Update] on the Graphics Input window to write the area to shared memory. Press [Close] on each window to ascend the sequence (as in Figure 3-5 or Figure 3-6) and continue the run.

3.9 Dynamic window for worker doses

The agricultural, relocation and decontamination subsystems calculate worker doses using a common methodology and common dynamic windows (see Reference 5, RODOS(RA4)-RP04_02).

In this methodology there are two categories of countermeasures: those that are applied in a single application (or a series of single applications) and those that are applied continuously over a period of time. For example the work involved in relocation is performed as a single application, people are removed once regardless of how long the period of relocation continues. It would be illogical to calculate worker doses on the assumption that people were removed each day of the period of relocation. However, the work involved in applying a countermeasure such as adding sorbents to feed continues as long as


- 36 -

the countermeasure is applied. It would be illogical to calculate worker doses on the assumption that all sorbents can be added to the feed at the start or end of the period of application.

For continuous application countermeasures LCMT is able to directly calculate the period over which the work of the countermeasure is performed and from this estimate the number of workers required and the amount of time they are exposed. For the single application countermeasure, LCMT is not able to calculate the period as it depends on resources and manpower as well as the priorities of the decision-makers, therefore the user must supply it.

When LCMT is calculating worker dose for a particular countermeasure it will display a Countermeasure Specification window to get required information from the user. If the countermeasure is a single application countermeasure the window will appear as in Figure 3-8 otherwise if the countermeasure is applied continuously the window will appear is in Figure 3-9.

Figure 3-8 the single application version of the countermeasure specification window


- 37 -

Figure 3-9 the continuous application version of the countermeasure specification window

At the top of both versions of the window is a label indicating which countermeasure is being considered. The button next to the label is an artefact of the user interface system and can be ignored.

The next button allows the user to indicate whether the workers are using personnel protective equipment (PPE). If the button is pressed, LCMT will assume that inhalation doses are zero and these will not be calculated. LCMT will use a special work-rate specified for PPE in the countermeasure data-files.

The user can give an indication of how dusty the countermeasure is by entering a resuspension enhancement factor of 1, 10 or 100. The factor will be applied to resuspension doses if the workers are not using PPE. If the user clicks more than one enhancement factor the lowest is used.

If the window is for a single application countermeasure (as in Figure 3-8) it will have an entry for the maximum duration permitted (by the user) for the application of the countermeasure. By default the value is one day. The user must enter a value that is greater than zero and reasonable given the logistics of the countermeasure. LCMT uses this number to calculate the numbers of teams and workers required and the time individual workers are likely to be exposed. The duration entered does NOT affect the public dose calculations.

3.10 Dynamic windows for the relocation (Options 1 and 2)

If the user chose Options 1 or 2 in the initialisation windows (see Section 3.2.2), LCMT will use the relocation subsystem to calculate relocation endpoints. A sequence of dynamic windows will be displayed as the subsystem progresses. The first part of the sequence is shown in Figure 3-10. This part deals with the definition of the zone where relocation is applied. The first window presents the user with five options.


- 38 -

1 Define the relocation zone and the duration of relocation using dose criteria. This is the approach adopted in previous versions of LCMT and is the default.

2 Define the relocation and duration of relocation using dose criteria and then modify graphically.

3 Define the relocation zone based on the area that EmerSim calculated should be evacuated. For this option an EmerSim run must have been included (see Section 2.1).

4 Define the relocation based on the area that EmerSim calculated should be evacuated, and then modify graphically.

5 Define the relocation zone graphically.


- 39 -

LCMT enters relocation subsystemLCMT pauses to get user input

LCMT pauses to display an inputmode window

LCMT merges the graphically modifiedarea and the calculated area using themethod specified in Relocation Zone:merge dose criteria zone and userdefined zone window.

Calculates relocation area,start and duration in absenceof decontamination

Calculates relocation area,start and duration in absenceof decontamination

Sets relocation area to besame as evacuation area fromEmerSim run

Sets relocation area to besame as evacuation area fromEmerSim run

START

CONTINUE

Figure 3-10 First part of the sequence of Dynamic windows in LCMTR. The sequence includes an Input Mode window as described in Section 3.8.

Additionally from the first window, the user can access a sub-window by pressing [Define start and duration of relocation].

If the relocation zone is specified graphically or by editing a calculated zone, LCMT needs to know the period of relocation. The user can specify a start time and duration in the Relocation zone: start and duration window. If the relocation regime has been calculated at each location and then the user graphically modifies the overall zone, LCMT needs some method of reconciling the calculated relocation period at each location with the overall user-specified period. The user


- 40 -

can choose one of three methods from the specified at the bottom of the Relocation zone: start and duration window. The options are listed below and illustrated in Figure 3-11.

1 Set duration of relocated zones to user entered duration. Regardless of the period calculated, the period assumed at all locations will be that specified on the Relocation zone: start and duration window.

2 Set the minimum duration of all relocated zones to the user-entered duration. For example if, using dose criteria, the period of relocation at a location was calculated to start from day 5 and continue for 10 days and the user set the start of relocation to day 3 and the duration for 28 days, then the user-entered duration would take priority. However, if the calculated start was day 2 and the duration was 40 days, the period at that location would not be changed.

3 Only set additional user-entered relocation zones to the user-entered duration. If the user has increased the zone of relocation the additional locations are given the duration specified, the periods at the other locations are not changed.

Start 2Duration 10

Start 4Duration 2

Norelocation

Start 1Duration 20

Start 3Duration 15

Norelocation

Start 1Duration 40

Start 3Duration 40

Norelocation

Do notrelocate

Do notrelocate

Do notrelocate

Relocate Relocate Do notrelocate

Relocate Relocate Relocate

User set:Start 2 dayDuration 30days

Norelocation

Norelocation

Norelocation

Start 2Duration 30

Start 2Duration 30

Norelocation

Start 2Duration 30

Start 2Duration 30

Start 2Duration 30

Norelocation

Norelocation

Norelocation

Start 1Duration 30

Start 2Duration 30

Norelocation

Start 1Duration 40

Start 2Duration 40

Start 2Duration 30

Norelocation

Norelocation

Norelocation

Start 1Duration 20

Start 3Duration 15

Norelocation

Start 1Duration 40

Start 3Duration 40

Start 2Duration 30

Relocation as calculated by LCMT Relocation as set by user

Merge using method 1 Merge using method 2 Merge using method 3

Figure 3-11 The effect of merging calculated and user set relocation zones.

NB generally only an expert user will undertake graphically modifying a relocation zone calculated with dose criteria.


- 41 -

If the user chooses an option that includes graphical modification an Input Mode window is displayed. The use of the Input Mode window to graphically modify zones is described in Section 3.8.

NB if the user wishes to edit a calculated zone (either calculated by dose criteria or by setting the same as evacuation), the [Edit Calculated Zone] button should be chosen on the Input Mode window, otherwise the results of these calculations may be lost.

The final window in Figure 3-10 is the Countermeasure specification window for relocation (see Section 3.9). Worker doses for relocation are calculated for the case where there is no decontamination and for each of the named decontamination techniques chosen by the user. However, the Countermeasure specification window is only presented once. LCMT assumes that relocation is performed under the same constraints with or without decontamination.

At the end of the sequence of windows shown in Figure 3-10 a relocation regime in the absence of countermeasures, including a delineated zone and a period of relocation at each location within the zone, will have been defined. The sequence of dynamic windows continues as illustrated in Figure 3-12.

If, in the initialisation windows, the user has chosen to consider the effects of decontamination (see Section 3.4.3) a set of dynamic windows is displayed that allows the user to define the decontamination zone.

The first window presents the user with seven options.

1 Set the decontamination zone to be the same as relocation. This is one of the approaches adopted in previous versions of LCMT.

2 Set the decontamination zone to be the same as relocation and then graphically modify the zone.

3 Define the decontamination zone based on the area that EmerSim calculated should be evacuated. For this option an EmerSim run must have been included (see Section 2.1).

4 Define the decontamination zone based on the area that EmerSim calculated should be evacuated and then graphically modify.

5 Set the decontamination zone to wherever deposition occurred. This is one of the approaches adopted in previous versions of LCMT.

6 Set the decontamination zone to wherever deposition occurred and then graphically modify.

7 Define the relocation zone graphically.

If option 2, 4, 6 or 7 is chosen an Input Mode window is displayed. The use of the Input Mode window is described in Section 3.8.


- 42 -

NB if the user has chosen Option 2, 4 or 6, [Edit Calculated Zone] button should be selected on the Input Mode window, otherwise the results of these calculations will be lost.

Next the user is prompted as to whether the relocation regime should be adjusted to account for decontamination. In previous versions of LCMT the relocation dose criteria have been applied to the predicted doses following decontamination. The result of the comparison is generally that the area and the period of relocation are reduced. Consequently people are assumed to returned to the relocated areas sooner. This can have the non- intuitive consequence that the predicted doses under a decontamination and relocation regime are higher than under a regime that consists purely of relocation. In LCMT version 6.2, the user is given the choice of whether to adopt this approach or to keep a constant relocation regime regardless of the effect of decontamination. The second approach is particularly useful where the relocation regime specified in the absence of decontamination has not been calculated with dose criteria (i.e. it has been defined or modified graphically).

NB To emulate previous versions of LCMT the user should set relocation purely on dose criteria (option 1) and allow the relocation regime to be adjusted after decontamination.

If the user has chosen named to apply a named decontamination technique, a Countermeasure specification window is displayed (see Section 3.9).


- 43 -

LCMT continuesIf the user chose:

To consider decontaminationNot to consider decontamination

Pause LCMT to getuser option

Pause LCMT to allow user tographically define or modify area

Pause LCMT to ask the user whether relocation regimeunder decontamination should be adjusted by dose criteria

Continue LCMT, if the user chose:Yes: apply dose criteria to doses after decontamination,adjust relocation regime to account for lower dosesNo: do not adjust dose regime to account for lower doses

Set decontamination zone the same asrelocation

Set decontamination zone the same asrelocation

Set decontamination zone to be same asevacuation area from EmerSim run

Set decontamination zone to be same asevacuation area from EmerSim run

CONTINUE

Set decontamination zone to whereverdeposition occurred


Pause LCMT to display appropriate Countermeasure specification windows

FINISH

Figure 3-12 Second part of the sequence of Dynamic windows in LCMTR. The sequence uses an Input Mode window as described in Section 3.8.

Finally the user is prompted as to whether to generate results for the Graphics Server and for ESY. Passing graphics results to the Graphics Server is time consuming and may not be necessary if the user is intending the LCMT results to be passed to subsequent modules. Results will always be generated for the Late Consequences module.


- 44 -

Results can only be generated for ESY if the user chose to apply decontamination and chose to use named decontamination techniques. Results are not generated for ESY if decontamination was specified in terms of surfaces and DFs, because there is no information about cost and resource requirements that are an essential part of the decision.

The user has the choice of passing a very large comprehensive set of data to ESY or passing a much more compact subset of data. If the user chooses both the large and the small set, only the small set is generated.

The endpoints passed to ESY are listed in Section 4.2.

3.11 Dynamic windows for the agricultural subsystem (Options 1, 3 and 5)

When the user runs FDMT as a precursor to LCMT, the user must choose up to five foods to pass to LCMT for further analysis. The first dynamic window presented to the user in the LCMT agricultural subsystem is the Agr. countermeasure: Selected foods window. This window allows the user to select which of these foods will be analysed, see Figure 3-13. LCMT will loop over each selected food and ignore the remaining foods. Before the program enters the food loop a sequence of dynamic window is presented as illustrate in Figure 3-13.

The next dynamic window (Zones for food countermeasures) asks the user how the agriculture countermeasure zone is to be defined. The user has two options:

1 Define agriculture countermeasure zone by activity criteria. This is the approach used by previous versions of LCMT. Each food is considered individually. Activity criteria are used to find the zone where the food exceeds the criteria in the absence of any countermeasure. Only within this zone will the countermeasures for a particular food be tried.

2 Define agriculture countermeasure zone graphically. The user defines an overall zone to delineate countermeasure application. The zone applies to all foods. Activity criteria are applied to each food individually. Only where criteria are exceeded WITHIN the overall food countermeasure zone are countermeasures tried.

If the user chooses to define the zone graphically an Input Mode window is directly displayed. This window differs from the usual Input Mode window (see Section 3.8) in that there is no option to [Edit Calculated Zone ] button. This is because the calculated zone will be different for each food.

The next dynamic window asks the user how the zone over which the ingestion collective dose is calculated should be defined. The user is given three options.

1 Define the food collective dose zone by activity criteria. This is the approach used by previous versions of LCMT. Each foodstuff is


- 45 -

considered individually. Activity criteria are used to find the zone where the food exceeds the criteria in the absence of any countermeasure. The collective dose is calculated across this zone regardless of whether any countermeasure was successfully applied.

2 Define the food collective dose zone the same as food countermeasure zone. This option is included for convenience, if the user has defined a countermeasure zone graphically, they can use the same zone for the collective dose calculation. If the user has not defined a countermeasure zone the subsystem defaults to Option 1.

3 Define the food collective dose zone graphically. The user can define a zone that is independent of other zones and which remains consistent as the program loops over food.

As with the food countermeasure zone, if the user chooses to define the food collective zone graphically an Input Mode window is directly displayed. Again this window differs from the usual Input Mode window (see Section 3.8) in that there is no [Edit Calculated Zone ] button. This is because the calculated zone would be different for each foodstuff.


- 46 -

LCMT enters agricultural subsystem

LCMT pauses to ask user for a list of foods toanalyse

LCMT continuesIf user chose:Option 1: LCMT takes the zone that food activity exceeds criteria in the absence of

countermeasures as the zone over which to calculate collective dose.Option 2: LCMT checks the countermeasure zone was defined graphically. If it was

LCMT uses this zone to calculate collective dose, if not LCMT issues warningand proceeds with Option 1

Option 3: LCMT uses the zone defined graphically by the user to calculatecollective dose

LCMT continues

LCMT pauses to ask user how to define foodcountermeasure zone

LCMT continues, If user chose:Option 1: LCMT calculates zone based on activity criteria for each food and tests

countermeasure within zoneOption 2: LCMT calculates zone based on activity criteria for each food and tests

countermeasure in intersection between zone and area defined graphically by user

LCMT pauses to ask user how to define collective dose collection zone

START

CONTINUE

Figure 3-13 Beginning of the sequence of dynamic windows in the agricultural subsystem

After the preliminary choices have been made LCMT enters the loop over food.

A second set of dynamic windows is presented to the user. These windows are illustrated in Figure 3-14.


- 47 -

LCMT pauses to display list of countermeasures available for foodstuff

NB The window listingcountermeasures willchange depending onthe foodstuff beinganalysed

LCMT continuesLCMT enters loop overcountermeasure.

LCMT pauses to requesttiming information forcountermeasure.

LCMT continuesLCMT calculates endpoints for foodIf remaining countermeasures to analyse returnto start of countermeasure loop

If remaining foods to analyse return to start offood loop

NB The window requesting timinginformation will be differentdepending on the countermeasurebeing analysed, two examplewindows are shown here

LCMT enters loop over food

LCMT pauses to show appropriatecountermeasure specification windows

FINISH

CONTINUE

Figure 3-14 Sequence of the dynamic windows within the food and countermeasure loops of agricultural subsystem.


- 48 -

For each of the foods selected by the user a dynamic input window appears listing the countermeasure strategies appropriate to that food (Agri. countermeasures). Table 4 lists the countermeasures that can be applied to each food. Here the user may choose which countermeasures to consider. If no selection is made, NO ACTIONS is implemented, i.e. LCMT calculates only areas in which food activity exceeds the criteria. Whenever the button NO ACTION is activated, all selected strategies are ignored and only areas in which food activity exceeds the criteria are calculated.

An example of an input window for choosing agricultural countermeasures for cows milk is given below (LCMT5-4.6).


After the user has selected some strategies, LCMT analyses each in turn and further input windows appear which allow the user to modify timing parameters for each strategy. The appearance of the timing window (LCMT5-4.7-n) depends only the strategy n and is shown below for the action "Disposal or stopping production".

[Close] exits the window without storing any changes, [Update] confirms any selections. The default timings for each countermeasure


- 49 -

option are given in Table 5. These timings are displayed in the window and can be overridden.

Certain countermeasures are constrained not to be applicable before the end of the deposition, see (see Reference 3, RODOS(RA3)-RP3_01). If a timing value is entered that invalidates this constraint it will be adjusted forward to the time of the end of deposition and an information message will be issued.

The definition of the strategies and benefits and drawbacks are described in more detail in the RODOS report WG3-TN(99)-43 (Reference 1).

If the user tries to select more than 12 strategies for a single food only the first 12 will be analysed.

A countermeasure specification window is displayed for each countermeasure to enable LCMT to calculate the worker doses (see Section 3.9).

Finally after the loop over countermeasure the user chooses the outputs to generate via a dynamic window:


- 50 -

The user can choose to send output to the graphics server and to create output for the decision evaluation subsystem (ESY). The user has the choice of passing a very large comprehensive set of data to ESY or passing a much more compact subset of the data. Only one set of ESY data can be generated within a single LCMT run. In case of agricultural countermeasure only one food can be assigned for the ESY output. If a set has already been generated, either within the relocation or decontamination subsystems or for a different food, it will be over written if the user chooses to generate one at this point. If the user chooses both the large and the small set, only the small set is generated.

The contents of the data file is listed in Section 4.2, The data file uses the abbreviations for techniques listed in Section 4.3.

Table 4: List of agricultural countermeasures available for each foodstuff considered in LCMT.

Rmov

Rduc

countermeasure

foodstuff Dis

p

Pro

c

Stor

T=0 T>0 T=0 T>0 Add

S

Am

el

Agr

D

Cro

p

Lan

d

Spring wheat (whole) ü ü ü ü ü ü ü Winter wheat (bran) ü ü ü ü ü ü rye (whole) ü ü ü ü ü ü Oats ü ü ü ü ü ü Potatoes ü ü ü ü ü ü Leafy vegetables ü ü ü ü ü ü Root vegetables ü ü ü ü ü ü Fruit vegetables ü ü ü ü ü ü Fruits ü ü ü ü ü Berries ü ü ü ü ü Cow’s milk ü ü ü ü ü ü ü ü ü ü Goat’s milk ü ü ü ü ü ü ü ü ü Sheep’s milk ü ü ü ü ü ü ü ü ü Beef (cow) ü ü ü ü ü ü ü ü ü Beef (bull) ü ü ü ü ü ü ü ü ü Veal ü ü ü ü Pork ü ü ü ü ü ü ü ü ü Lamb ü ü ü ü ü ü ü ü ü Chicken ü ü ü ü ü ü ü ü ü Roe deer ü ü ü ü Eggs ü ü ü ü ü ü ü ü ü Beer ü ü ü ü ü

NB agricultural countermeasure abbreviations are given in Section 4.3.


- 51 -

Table 5: Default timings for agricultural countermeasure options (identical for all foods).

Countermeasure Quantity Default value Disposal or stopping production

Time when production stops 365 days

Food processing None - Maximum storage time for fresh food 180 days Storing food Maximum storage time for processed food

730 days

Removing animals from contaminated feed (t=0)

Duration of feeding – three required 7 days, 30 days, 90 days

Start time of feeding 2 days Removing animals from contaminated feed (t>0) Duration of feeding – three required 7 days, 30 days,

90 days Duration of feeding – three required 7 days, 30 days,

90 days Reducing animals’ contaminated feed (t=0)

Fraction of diet replaced 0.25 Start time of feeding 2 days Duration of feeding – three required 7 days, 30 days,

90 days

Reducing animals’ contaminated feed (t>0)

Fraction of diet replaced 0.25 Start time 2 days Adding sorbents to

animal diet Duration 7 days Start time when amelioration effective (>365 days)

365 days Land amelioration

Duration of effectiveness (5 applications) 1095 days, 0, 0, 0, 0

Time decontamination occurs 730 days Agricultural decontamination Length of time food production lost

following decontamination 30 days crops 730 days pasture grass

Time at which change of crop is considered

365

Minimum time for activity criteria in original food to be exceeded for a change of crop variety to be considered

730

Crop change

Minimum time for activity criteria in original food to be exceeded for a change of crop species to be considered

3650

Land use change Minimum for activity criteria in food to be exceeded for change in land-use to be considered.

25550 days (70 years)


- 52 -

3.12 Dynamic windows for decontamination (Option 4)

If the user chose Option 4 in the initialisation windows (see Section 3.2.2), the LCMT run uses the decontamination subsystem and a sequence of dynamic windows will be displayed as the subsystem progresses. The sequence is shown in Figure 3-15. The first window in the sequence (Zones for decontamination) presents options for defining the decontamination zone.

1 Define zone with dose criteria. This is a convenient way for the user to identify and delineate zones with a high contamination problem. Dose criteria are only used to delineate the zone, they are not used to judge whether the decontamination has been successful.

2 Define a zone with dose criteria and then modify graphically.

3 Define the decontamination zone based on the area that EmerSim calculated should be evacuated. For this option an EmerSim run must have been included (see Section 2.1).

4 Define the decontamination zone base on the area that EmerSim calculated should be evacuated and then modify graphically.

5 Set the decontamination zone wherever deposition occurred. This is the approach used in previous versions of LCMT.

6 Set the decontamination zone wherever deposition occurred and then modify graphically.

7 Define the decontamination zone graphically.

If the user selects Option 1 or 2, a window is presented within which the dose criterion can be set. The criterion consists of a dose, an integration period and a flag indicating whether the dose is outdoors or normal living. The criterion is applied in a similar manner to relocation imposition as described in 3.4.2. At each location the criterion is tested, if the dose at any time exceeds the criterion the location is marked for decontamination.

If option 2, 4, 6 or 7 is selected the user is presented with an Input Mode window. The use of the Input Mode window to graphically define or modify zones is described in 3.8.

NB if the user wishes to edit a calculated zone (i.e. they have selected Option 2, 4 or 6 for defining the decontamination zone), the [Edit Calculated Zone] button should be chosen on the Input Mode window, otherwise the results of these calculations may be lost.

After the decontamination zone has been defined, the decontamination subsystem proceeds to calculate the endpoints. Finally the user is prompted as to whether to generate results for the Graphics server (see Section 4.1. and whether to generate results for decision evaluation system, ESY (see Section 4.2). Results are not generated for ESY if decontamination was specified in terms of surfaces and DFs, because


- 53 -

there is not information about cost and resource requirements that are an essential part of the decision. LCMT enters decontamination subsystemsLCMT pauses to get user options

LCMT pauses to allow user tographically define or modify area

If named technique selected LCMT pauses toshow appropriate countermeasurespecification window

LCMT pauses to get output options from User.

START

Set decontamination zone with dosecriteria

Set decontamination zone with dosecriteria

Set decontamination zone to be sameas evacuation area from EmerSim run

Set decontamination zone to be sameas evacuation area from EmerSim run



FINISH

Figure 3-15 The sequence of dynamic windows in the Decontamination subsystem.

Version a User Guide for the Long Term Countermeasure Model LCMT6.2 of RODOS-PV6.0

- 54 -

3.13 Modifying input data

All the data specifying the input parameter values necessary for running relocation, agricultural countermeasures and decontamination subsystems can be found in a number of ASCII files. These files contain default values, which may be edited by the user. The values then become user input values and are read during run-time by the system. The values that the user changes become the new default values. A description of the default values and the data files is given in reference 1. A full justification of the default values with other supporting information is given in reference 2.

All these data files are located in the directory: ~rodos/roextern/data/lcm/

3.13.1 Files which can be changed

The user is advised to view or edit these files before undertaking a calculation in LCMT. The file names are listed below with a brief description of their function.

Food countermeasure subsystem files

• fcdbase6.data:

data for production per animal, dry matter content of animal feeds

• fcbans6.data

radionuclide and food groups assigned to criteria for banning foods and food groups for management of relocated areas

• fcproc6.data

choice of food decontamination (milk only), processing or both, and, decontamination factors for milk

• fcstor6.data

list of foods requiring storage only or storage following processing

• fcadds6.data

effectiveness of addition of sorbents to animal feeds (default is AFCF to feeds)

• fcamel6.data

effectiveness factors for amelioration of land (default is liming)

• fcdecf6.data

agricultural decontamination techniques effectiveness

Worker dose files

All worker dose files have a similar structure and are held in subdirectory ~rodos/roextern/data/lcm/worker6/

Version c User Guide for the Long Term Countermeasure Model LCMT6.2 of RODOS-PV6.0

- 55 -

Each file in the subdirectory corresponds to a countermeasure that can be applied in LCMT.

3.13.2 Files which should remain unchanged

It is recommended that the following files should not be changed. (Some of the data have been derived from running complex models and there are numerous interdependencies, explicit and implicit, between them).

Relocation countermeasure subsystem files

• Rdresltm_6.data

output times for relocation doses

• Rddata_6.data

life expectancy for 3 age groups for relocation

Food countermeasure subsystem files

• fcfood6.data

list of indices of output times for dose endpoint calculations.

Decontamination countermeasure subsystem files

• dcdecon_6.data

lists of decontamination techniques, time of implementation, urban surfaces and decontamination factors to link input windows to LCMT calculations.

• dcdrext1_6.data

external dose reductions for decontamination techniques

• dcresus1_6.data

resuspension from surfaces following decontamination (technique option)

• dcresus2_6.data

resuspension from surfaces following decontamination (decontamination factor option)

• dcsurfact_6.data

surface activities as a function of time under normal conditions


- 56 -

4 Results and endpoints

4.1 Graphical output

The RODOS graphics server structures data as a hierarchy of endpoints, see Figure 4-1.

a) b)

Figure 4-1 The graphics server presents end-points as a hierarchy. (a) At the top of the hierarchy are the run-Ids of all the module runs that have been performed or loaded during the current RODOS session. (b) The user can descend the hierarchy by clicking on the Run-IDs and subordinate items.

Table 6 gives the hierarchy for the agricultural subsystem, Table 7 gives the hierarchy the relocation subsystem and Table 8 gives the hierarchy for the decontamination subsystem.


- 57 -

Table 6 The hierarchy of endpoints for the agricultural subsystem.

Run.info – a text file that gives run information for the agricultural subsystem as a whole. It includes the foods chosen for analysis and the method chosen for specifying the agricultural countermeasure zone and ingestion dose calculation zone. Countermeasure.zone – if the user specified the food countermeasure zone graphically then this endpoint is created to indicate what the zone is.

Food/

Collective.dose.zone – if the user specified the collective dose zone graphically then this endpoint is created to indicate what the chosen zone is. Criteria not exceeded – only displayed if at no location is the activity criteria for the food exceeded. If this message is displayed no countermeasures are considered and no output other than Food/run.info is displayed. Run.info – a text file that gives the activity criteria used for the particular food in the particular run. The file gives the radionuclide group and the criteria in Bq kg -1 and lists the radionuclide tha belong to the group that have been passed from FDMT. A maximum of ten radionuclides important for the ingestion pathway are passed from FDMT.

Duration – a map that gives the interval over which food activity concentrations exceeds the criteria, days. It is assumed that the activity concentrations in food exceed the intervention criteria for all times between the time when the activity concentrations first exceed the criteria to the last time the criteria are exceeded. Numerical results – a text file containing a collection of summary statistics:

“Total amount of food above criteria’ is the total amount of food with activity concentration greater than the criteria after the countermeasure has been applied. For most food it is given as kg, for animals it is given as ‘Head’. “Maximum area where activity concentration exceeds criteria” is the area under production that exceeds the criteria at any time.

“Collective dose” is a table of public collective ingestion dose (manSv) integrated to 1, 2, 5 and 50 years. It is calculated for each food and organ passed from FDMT and is summed over all radionuclides considered in the ingestion pathway. No food produced above the activity criteria is consumed, all other food that is not disposed is consumed. The area over which collective dose is calculated depends on the user responses to choices presented in dynamic windows as the agricultural subsystem runs, see Section 3.11. If the user chooses to base the zone on activity criteria then, the area where food exceeds the intervention criteria at least one time on the time grid in the absence of any countermeasure is used as the zone over which collective doses are calculated. However, if the user chooses to define the zone graphically, either directly or indirectly (by setting it the same as the food countermeasure zone), then this user-defined zone will be used for calculating the collective dose and the area will be the same for all foods listed. Groups.first – a map indicating the radionuclide-groups that exceed the activity criteria at each location first.

RunID

/

Foods 1 to n/(e.g. m

ilk, leafy vegateables, pork etc).

No A

ction/

Groups.last – a map indicating the radionuclide-groups that exceed the activity criteria at each location last.


- 58 -

Table 6 The hierarchy of endpoints for the agricultural subsystem. (Cont)

Duration – same as “RunID/Foods 1 to n/No Action/Duration” Food above – a line graph that gives the mass of food or production of food with an activity concentration greater than the intervention criteria as a function of time. In all cases this is the amount of food exceeding the criteria after the countermeasure has been applied.

For crops, this endpoint is expressed as the land area growing

user guide for the long term countermeasure model lcmt6.2 of rodos … · 2008. 4. 15. · version...

Documents