JRodos User Guide
Versio n 3 .4 (JRo do s February 2017 u2 )
=> Updated Chapters to version 3.1 are marked in yellow<= => Text updates to version 3.21 are marked in cyan <= => Text updates to version 3.31 are marked in pink <= => Text updates to version 3.33 are marked in green <=
Ievgen Ievdin Ukrainian Centre for Environmental and Water Projects
Dmytro Trybushnyi, Christian Staudt, Claudia Landman Karlsruher Institute of Technology, Institut für Kern- und Energietechnik
December 2018 2
Table of Contents
ABBREVIATIONS, ACRONYMS, DENOTATIONS ...... 6
ANNOTATED FIGURE OF THE JRODOS WINDOW ...... 8
ANNOTATED FIGURE OF THE JRODOS TOOL BAR ICONS ...... 9
STARTING JRODOS; WHAT TO DO IN CASE OF PROBLEMS; TRAINING MATERIAL ...... 10 Starting JRodos and logging in; client and server ...... 10 What to do in case of problems; Bugzilla ...... 10 Filing a bug and closing a bug in Bugzilla ...... 11 Training material ...... 11
JRODOS WINDOW ...... 13 Overview of window components ...... 13 Toggling windows ...... 13 Working with Main Window tabs ...... 13 Working with the Message Window ...... 15 Help ...... 15
MAP CONTROL ...... 17 Summary ...... 17 Information about the map displayed in the Main Window ...... 17 Working with the Map Legend ...... 19 Loading non-result map layers ...... 22 File layers applicable in JRodos ...... 22 Rendering the data to the current map views ...... 22 Loading map layers from file storage ...... 22 Loading map layers from PostGIS databases ...... 23 Loading local map layers around a site from the JRodos GIS data base ...... 24 Loading map layers from a WMS source ...... 25 Loading Google Maps (hybrid view), OpenStreetMaps ...... 27 Loading and displaying map-type model results ...... 28 Loading a map-type result layer ...... 28 Zoom level of the loaded result ...... 28 Map result tool tips ...... 28 Contour plots ...... 29 Interpolate To Points tool ...... 30 Summary ...... 30 Setting up the co-ordinates file; file residence in single user and multi-user mode...... 31 Generating the interpolated results ...... 32 Map-type results in the one available Map Tab ...... 34 Working with the map tools in the Tool Bar ...... 35 Pan/move tool. Zoom tools. Reset map in Main Window...... 35 Zoom level, zoom lock ...... 36 Distance tool ...... 36 Plot Builder tool for time dependent results; saving the time series table ...... 36 Vertical Profile tool for multilevel results; saving the vertical profile table ...... 38 Information tool ...... 39 Time slider ...... 39 Printing or saving map views; exporting map layers ...... 40 Configuring the initial load layer list...... 40
VISUALIZATION OF NWP DATA AND REAL-TIME DATA ...... 41
3
NWP data ...... 41 Real time (measurement) data ...... 43 Tips for controlling the quality of NWP and real time data ...... 45
WORKING WITH PROJECTS ...... 46 Creating new projects ...... 46 Manipulating existing projects with tool bar and file menu options ...... 46 Manipulating open projects with the Project Explorer ...... 50
WORKING WITH THE PROJECT EXPLORER ...... 51 Nodes in project explorer tree and getting information about them ...... 51 Project and task operations with the Project Explorer ...... 52 Reporting related operations in the Project Explorer ...... 53 Manual report generation ...... 53 Automatically generated reports ...... 53 Result related operations in the Project Explorer ...... 54 List of visualisation options for a result ...... 54 Copy Item Path to Clipboard ...... 54 Visualize on map (Default) and Visualize on map (Iso-polygons) ...... 54 Multiple Nuclides Visualizer ...... 56 Visualize as Voronoi diagram ...... 58 Visualisation of map-type results on NUTS3 administrative unit grid ...... 58 List affected urban areas...... 59 Visualisation of spectral data ...... 61 Text / html / table results ...... 61
USER POLICIES, MULTI-SCENARIOS SUPPORT ...... 62
WORKING WITH MODELS AND MODEL CHAINS ...... 64 Working with the Emergency or the EmergencyLite model chain ...... 64 Working with the Preparedness model chain ...... 64 Working with LSMC+EMERSIM+DEPOM+FDMT ...... 66 Creating LSMC+EMERSIM+DEPOM+FDMT projects ...... 66 Initializing and running LSMC tasks...... 66 Initializing and running EMERSIM tasks...... 67 Running DEPOM tasks...... 67 Initializing and running FDMT tasks...... 67 Working with the JRodos Continuous Mode ...... 69 Working with the JRodos Automatic Mode ...... 71 Background information ...... 71 Creating a project with the Automatic model chain ...... 72 RODOS-Lite ...... 73 RODOS-Lite tabbed panel ...... 73 Selection of near range ADM and grid ...... 73 Selection of calculation grid ...... 73 RODOS-Lite tab [Site] ...... 75 RODOS-Lite tab [Source Term] ...... 75 RODOS-Lite tab [Weather]...... 76 ADM time steps and result averaging times for Lasat model ...... 76 Meteorological data from provider ...... 78 Hand input of weather data: Wind direction selection tool ...... 79 RODOS-Lite tab [Countermeasures] - not visible for EmergencyLite ...... 80 RODOS-Lite tab [Food chain] - not visible for EmergencyLite ...... 80 RODOS-Lite tab [Run] ...... 80 Viewing the RODOS-Lite input summary and saving the RODOS-Lite xml in JRodos ...... 80 Working with the ERMIN model ...... 81 Working with the IAMM model ...... 81 Working with the HDM models ...... 81 Working with the MATCH model ...... 82 Overview ...... 82 4
Preconditions for running MATCH in JRodos ...... 82 Provider definition and data supply ...... 82 Using the GRIB LSMC to MATCH data converter ...... 82 Available data for demonstrating MATCH in JRodos ...... 84 Carrying out a MATCH project ...... 84 MATCH tab “General” ...... 85 MATCH tab “Sourceterm” (MATCH stand-alone only) ...... 86 MATCH tab “Output” ...... 86 Example MATCH projects ...... 87 Working with the FDMF model ...... 88 Working with the LCMF model ...... 89 Working with the DEMM model ...... 91 Working with the FOMM model ...... 92 Working with the AgriCP model ...... 93 Working with the EmerSimCH model ...... 96 Working with the Wildfire model ...... 99 Working with the Tornado model ...... 102
APPLYING JRODOS OUTSIDE THE RANGE OF THE EU INSTALLATION ...... 103 Summary ...... 103
WORKING WITH THE MULTI-USER FEATURE ...... 104
AUTOMATIC START OF CALCULATIONS VIA INCOMING XML FILES ...... 105 RODOS-Lite models ...... 105 Kicking via Client or Server; influence of multi-user feature ...... 105 Creating suitable RODOS-Lite xml files ...... 105 Non-RODOS-Lite models ...... 106
WORKING WITH THE RECURRENT JOB LAUNCHER ...... 108
WORKING WITH THE STATISTIC DATA OUTPUT TOOL ...... 109
WORKING WITH THE REPORTING FUNCTIONALITY...... 110 Manual report creation ...... 110 Changing properties of result items ...... 113
OPTIONS IN THE MENU BAR ...... 115 Localisation (UI language) ...... 115 Time Zone ...... 115 Report Settings ...... 116 Internet Settings ...... 116 User Policy ...... 117
APPENDIX: WORKING WITH SORT-ABLE TABLES ...... 118 Sorting ...... 118 Filtering ...... 118 Selecting rows ...... 119
DOCUMENT HISTORY ...... 121
5
Abbreviations, acronyms, denotations
ADM Atmospheric Dispersion Model AGRICP Agricultural Countermeasures Program aka also known as DB Data Base DEMM RODOS deposition monitoring model DEPOM Deposition calculations for FDMT DMI Danish Meteorological Institute DWD Deutscher Wetterdienst (German Weather Service) Emergency model Sequence of models that execute one after the other once the "Emergency" calculation is chain kicked; consists of the models LSMC, EMERSIM, DEPOM, FDMT (full RODOS-Lite input possibilities) EmergencyLite model Same models as above, but EMERSIM and FDMT run with default assumptions (reduced chain RODOS-Lite input possibilities) EMERSIM Model for simulating early emergency measures and resulting doses with and without actions EMERSIMCH Modified version of EMRSIM with freely definable countermeasure areas ERMIN European model for inhabited areas (decontamination and relocation) Esri Shapefile - see shapefile - FDM... RODOS Food chain and Dose Models, F Forest T Terrestrial FOMM RODOS Food Monitoring Model GeoTiff file Public domain metadata standard which allows geo-referencing information to be embedded within a TIFF file. Additional information may include everything necessary to establish the exact spatial reference for the file, e.g. projection type and coordinate system. Source: Wikipedia GIS Geographical Information System GMT - see UTC - GUI Graphical User Interface HDM RODOS Hydrological Models HIRLAM HIRLAM, the High Resolution Limited Area Model, is a Numerical Weather Prediction n forecast system developed by the international HIRLAM programme (source: Wikipedia) HP-UX UNIX-Derivative of the company Hewlett-Packard HTML Hypertext Mark-up Language IAMM Inhabited areas monitoring model INEX1P2 The demonstration scenario INEX1P2 is a RODOS-suited adaptation of Phase 2 of the INEX1-exercise; reference: INEX 1 - An International Nuclear Emergency Exercise, OECD (1995), ISBN92-64-14560. For scenario details, see the Appendix in the Result Guide for the models in the JRodos Emergency Model Chain. Java Object oriented programming language JRodos Java Version of RODOS
6
PostGIS Extension of PostgreSQL to enable working with geo-data PostGresSQL PostgreSQL, often simply "PostGres", is an object-relational database management system with an emphasis on extensibility and standards-compliance (Source: Wikipedia) QGIS QGIS (previously known as Quantum GIS) is a cross-platform free and open-source desktop geographic information system (GIS) application that provides data viewing, editing, and analysis (Source: Wikipedia) RAC Radiological Accident associated with fire RDD Radiological Dispersal Device RODOS Real-time On-line Decision Support System RODOS-Lite User-input interface of RODOS rt real time rttf real-time target format shape file The Esri Shapefile or simply shapefile is a geospatial vector data file format for GIS software developed and regulated by Esri (http://www.esri.com/). Shape files spatially describe geometries: points, poly-lines, and polygons, representing, for example, water wells, rivers, and lakes, respectively. Each item may have attributes describing the items, such as name or temperature. Tab Eng: Tabbed document interface ("tabbed browsing"), in a web browser, tabs divide open pages displayed in a single window (Source: Wikipedia) Germ: In grafischen Benutzeroberflächen von Computerprogrammen der Aufteilung dienende Elemente (in German: Registerkarte) (Quelle: Wikipedia) TIFF-file TIFF (Tagged Image File Format) is a file format for storing images. Tornado Functionality within LSMC to calculate radionuclide distribution after tornados UI User Interface UTC Coordinated Universal Time (UTC, Fr. Temps Universel Coordonné) is International Atomic Time (TAI) with leap seconds added at irregular intervals to compensate for the Earth's slowing rotation. In casual use, Greenwich Mean Time (GMT) is the same as UTC. UTM Universal Transverse Mercator Wildfire Functionality within LSMC to calculate radionuclide distribution after wildfires WMF Web Feature Service (gives vector data) WMS Web Map Service (gives pictures) XML Extensible Mark-up Language (XML) is a mark-up language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable (source: Wikipedia)
7
Annotated figure of the JRODOS window
Time Slider JRodos Version List of open tabs in Main Window
Menu Bar Map Layer Icons for 1st, prev, run, etc Description buttons Tool Bar
Main Window Properties Project Explorer
Messages
Coordinate Display Field Distance Display Field
Message Window icons for List of open tabs in "clear" and "scroll" Properties Window
8
Annotated figure of the JRODOS tool bar icons
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
1. Create New Project 2. Open Existing Project Project icons 3. Save Project
4. Show/Hide Project Explorer Window 5. Show/Hide Message Window Window toggling icons 6. Show/Hide Properties Window
7. Load... Load. Files/PostGIS/WMS layer icon
8. Reset Re-set map scale in Main Window 9. Lock Map Extent Lock map scale to view in Main Window 10. Clear Selection (<=> exit information mode) 11. Zoom in 12. Zoom out 13. Previous zoom Map tool icons 14. Next Zoom 15. Zoom to Selection (in information mode) 16. Information 17. Plot Builder (for time plots) 18. Vertical Profile (multilevel results) 19. Pan Zoom (Move) 20. Distance Tool
21. Add to report
9
Starting JRodos; What to do in case of problems; Training material
Starting JRodos and logging in; client and server
For starting JRodos, Firstly, you must start the JRodos-Server (the “JRodos Program”). Then, please, wait until message "Server is running" appears in the JRodosServer window. When the server is running, you can start the JRodosClient (your personal local JRodos application). The JRodos login window appears, asking for the user name and password, and an IP-address or a name for the computer where the JRodos Server is running (Figure 1). JRodos provides a default user "admin" with password admin (in lower case characters). A pre-defined server location is localhost, that is, the one computer you are working with, and where the Server, the Client and the JRodos Data bases are running, if JRodos is not implemented as a distributed system.
Figure 1: JRodos login window.
Note to the Server specification: If no name is present in the drop-down list for the Server location in the Combo-Box, or an invalid address, please enter a valid address in the respective field. After successful validation the entered address is stored and appears next time in the Combo-Box. If the JRodos Server crashes during work or some network problem occurred, the JRodos Client will inform the user via an Information Window and text in the main window header line. Working with functionalities not requiring the Server (map, local GRIB files analysis) can be continued. If the Server becomes available again, the Client will inform the user about this, too. In some cases restarting the Client is mandatory, even after recovery of the Server connection; please read the information in the information windows!
What to do in case of problems; Bugzilla
If you encounter a problem when applying JRodos (system crash, system hung-up, model crash, wrong or strange model results, ...) please take first a look at the available information: Messages appearing in the JRodos Messages window The "Console messages" in folder "Prognostic Results"
10
The Manager log file in folder
Filing a bug and closing a bug in Bugzilla Use a Web-browser and the address "https://resy5.iket.kit.edu/" to reach the JRodos Homepage. For proceeding to the Bug Tracking System "Bugzilla", you must be a registered user. If you are not yet a registered user, press "New account". A registration window opens where you must specify a valid email address. After submitting the request you will receive a confirmation and a password under the given email address. If you are a registered user, login with the email address that you specified during the registration, and your password. You can then inspect entries, or file a bug, or close a bug. When filing a bug, provide the details Bugzilla asks for and the affected system component. Please: Indicate JRodos Version, Operating system, 64 or 32 bits, multi-user feature active etc. Specify as detailed as possible the problem itself and the sequence of actions that led to the problem Give additional information as RODOS-Lite xml, manager or model or client log files, screen shots or any other material that can help the developers in analyzing and reproducing the bug When the bug was entered, it is added to the list of Bugzilla bugs. The developers will receive an email, assign a person responsible for solving the problem, and will ask for further clarification if necessary. When the problem is associated to NWP- or engine data, they may ask you for providing the data; if need be, the data can be treated as confidential and will be deleted afterwards. When the responsible person considers the bug fixed, it will get a respective mark in the "Resolution" columns. Bugs marked "Resolved" or "Fixed" should be closed by the bug reporter (and not the developer who issued the "Fixed" classification). As a consequence, bug reporters should test and close "their" bugs as soon as possible after a new version or patch becomes available.
Training material
The JRodos exchange Server resy5, user "jrodos" 1, folder
1 ask the KIT JRodos Team for the password 11
Latest versions of JRodos User Guide and JRodos Result Guide, Administration Guide and JRodos Customization Guide and the "Working with ..." documents; chapters that were significantly revised are additionally contained as separate files Folder
12
JRodos Window
Please note: On page 8 you find an Annotated figure of the JRODOS window. On page 9 you find an Annotated figure of the JRODOS tool bar icons.
Overview of window components
The JRodos window contains four main components: Main Window: Can contain either some map view consisting of several layers of geo-referenced information, or a diagram or table. The information in the Main Window is organised as "Tabs". A List of open tabs in Main Window is displayed above the Main Window. The Map Legend identifies all information layers contained in the Map Tab, the "map layers". Project Window: Project information presented as a tree. The Project Explorer contains Project Tabs that allows interactively browsing scenarios. Property Window: Displays information on item selected in the Main Window. Shows a Report structure. Message Window: JRodos status and run information; latest messages are displayed on top. The other component of the JRodos window are summarised below. Topmost line JRodos version. Icons representing the functions "Iconify", "Reduce size/Restore size" and "Close". To the left of the "Iconify" icon, information about "Heap Status". Menu Bar: Functions independent from the current context. Tool Bar: Functions that depend on the current context.
Toggling windows
The Project Explorer, Message Window, and Properties Window, can be toggled on and off by pressing the corresponding buttons in the Tool Bar, see Figure 2.
Figure 2: Window toggling buttons. Left to right: Project Explorer, Message Window, Properties Window.
Working with Main Window tabs
The information in the Main Window is organised as "Tabs". A List of open tabs in Main Window is displayed above the Main Window. On start-up of a JRodos client session, the list consists only of the one entry [Map]. During a JRodos session, additional tabs can be opened, containing information as diagrams and/or in tabular form. Clicking on a tab in the Tab List produces a display of the tab's content in the JRodos Main Window. Fast double-clicking on any tab in the Tab List switches to a full-screen tab view – fast double-clicking on any tab returns to the standard display.
13
Full- screen tab view
Figure 3: Standard (bottom) and full screen (top) display of a Tab.
To help navigating a Tab Preview button offers an overview of opened tabs in form of small pictures, making it easy to select the desired tab.
Tab Preview
Figure 4: Tab Overview icon (the “looking glass”) and small pictures of currently open tabs.
14
A Main Window Tab can contain information in tabular form (time series, tables, data contents of grid cells). By marking the complete table or parts of the table with the left mouse button and then clicking with the right mouse button, it is possible to copy the selected data to a clipboard or table processor (e.g. Excel) with or without column names. Complete tables can be saved as text files or Excel files with the Save icons in the tab’s tool bar (under the respective tables).
Figure 5: Save to File and Save to Excel buttons within the tab’s toolbar.
All tabs except the [Map] Tab can be removed from the Main Window. To remove a tab, right click on the tab name and select: Close to close only the selected tab Close All to close all tabs Close All but this to close all tabs except the selected one.
Figure 6: Close tabs dialogue.
Working with the Message Window
Messages are displayed in the Message Window with the latest messages on top. To clear the Message Window press the “Clear all…” button. To disable/enable auto scrolling press the “Autoscroll On/Off” button to the right of the “Clear All” button. To freeze a line on the screen, disable auto scroll and click in the Message Window on the desired line.
Figure 7: Clear all messages button.
Help
Help is available with menu item Help. Additionally, there are some windows containing a Help button which invokes help topic related to the corresponding window.
15
Figure 8: Current help window.
16
Map Control
Summary
A "map view" (or simply a "map") in the JRodos Map Tab consists of a combined display of one or more map layers of geo-referenced information. For example, each of the map items "elevation", "rivers", "population density", and each of the model result items "total dose rate" and "cell(s) with total dose rate maximum value" represents one layer of geo-referenced data. The Map Legend identifies all map layers loaded into the Map Tab and allows browsing the respective geographic information (see chapter "Working with the Map Legend") and also customizing the respective map layer styles. On start-up of a JRodos client the map view consists of a set of layers, which is defined in the initial load layer list that can be configured for each Client via a menu, see Chapter "Configuring the initial load layer list". The map layers are displayed in the Map Tab on top of each other, in the order from bottom to top, as they appear in the Map Legend; the topmost layer in the map is on the first row in the Map Legend. Via the Map Legend list, the user can influence the visual appearance of the current map view by reordering the map layers and by switching on or off the displaying of layers. As the "Annotated figure of the JRODOS tool bar icons" on page 9 shows, the JRodos Tool Bar offers various tools for operations in the current map view. Chapter "Working with the map tools in the Tool Bar" explains how to use the tools and the effects they have on the map view. The user may add new map layers to the Map Legend list, or remove map layers from the Map Legend list. Non-model result layers are added via the "Load" button, see chapter "Loading non-result map layers". Model result map layers are added via the Project Explorer, see chapter "Loading a map-type result". In either case, data from loaded layers are automatically re-projected by JRodos to the currently active map projection. The setting of the coordinate system or projection type is usually done only once during the customisation of JRodos. During a JRodos session, non-result map layers can be loaded as files - currently supported are the two common geographical data formats: ESRI shapefile (*.shp) and geotiff (*.tiff, *.tif). Layers can also be loaded from a PostGIS database (JRodos internal or external), or from a Web Map Service (WMS) server. It is also possible to use Google Maps (hybrid view) or OpenStreetMaps. Map layers from other than file storage are cut out to the current map view during the loading process. Map layers from file storage are loaded as full extent layers in one piece into the client's memory. Only after the loading, the area covering the current JRodos map view is cut out. Complete map views in the Map Tab Map can be sent to a printer or saved as static or animated images. Map layers can be exported to ESRI shape files. See Chapter "Printing or saving map views; exporting map layers".
Information about the map displayed in the Main Window
The Map Scale is positioned in the lower left map corner (Figure 9). It shows the projection name, the current scale and scale intervals for estimating distances on the map. The North Arrow is positioned in the lower right map corner (Figure 9). With World Mercator projection, the north arrow points to the North Pole from the arrow's position on the map view. With other projections, the North Arrow points to the North Pole as seen from the centre point of the map view. If the map area displayed is relatively small, the indicated direction is approximately valid for the whole map. When changing the map extent (zoom, pan) the arrow direction changes correspondingly.
17
Figure 9: Map Scale (left), North Arrow (right), and Coordinate Display field (bottom right).
JRodos supports several metric Map Projections to display geographical data: WGS 84 UTM 31N … WGS 84 35N as well as Google Mercator Projection. Please note that some background maps look better or even require special projection. For example, "World Mercator" is the projection of choice for the "OpenStreetMap" and the world wide production data layer for displaying country boundaries on the global scale. The Map Projection is user related and can be different for different users. How to set the Map Projection is described in the JRodos Customization Guide, Chapter on "Administration of customized start-up settings for users and user groups", "Tab [Map Projection]. The Coordinate Display field in the map status bar (Figure 9 and Figure 10) show the geographical coordinates of the current cursor position on the map, and also the elevation above sea level (between brackets, in "m"; only for land areas) (visible in Figure 10). To change the format of the coordinate display, right click into the coordinate field in the lower right corner of the Main Window, and then left click on "Format". In the “Coordinate format” dialogue select the desired format and click OK (Figure 11a). Please note that the format in the “Coordinate format” window is editable; this can be used for example to increase the number of digits to be displayed (Figure 11b).
Figure 10: Distance (left) and Coordinate (right) Display field in the map status bar.
18
. (a)
. (b) Figure 11: Changing the format of the coordinate display. Without editing (a). With editing (b).
Working with the Map Legend
The Map Legend is an internal frame in the Map Tab in the Main Window (Figure 12). It is possible to move the legend around inside the Map Tab. Or, one can move the legend to the Properties Window by clicking on the Close ("X") icon in the Map Legend line; in the Properties Window, the Map legend appears as a separate tab (Figure 13). For putting the Legend back to Map Tab, click again on the Close ("X") icon in the Map Legend line.
Figure 12: Map Tab with Map Legend inside.
Figure 13: Map Tab with Map Legend in Properties Window.
Figure 14 shows an example Map Layer list. The layers can be moved up and down, so that the map view will contain them in the desired order.
19
Figure 14: Map Legend with the list of available layers (example).
To move a layer around in the list select the line with the respective layer, then drag to the desired position.
Figure 15: Moving a layer to the top.
To switch on / switch off a layer in the list, click on the corresponding check box in the Legend list. Alternatively, right click on the line with the respective layer and select Hide / Show from the appearing context menu.
Figure 16: Hide a layer.
To remove a layer from the list, right click on the line with the respective layer and select “Remove layer” from the appearing context menu.
Figure 17: Remove a layer.
The data contained in a map layer cover a certain spatial extension. To zoom to the full layer extent, right click on the line with the respective layer and select “Zoom to Layer Extent” from a context menu.
Figure 18: Zoom to layer extent.
20
A map layer can possess several attributes, such as "type description", "name", and "value" for example. To export a map layer to an ESRI shape file right click on a corresponding item in the Map Legend and select “Export layer to .shp” (Figure 19). In the File Chooser dialogue, browse to the desired folder; put the name for the file and press "Save". After export, you will be asked to save the current layer style to “.sld” file.
Figure 19: Exporting a layer to an ESRI shape file.
To obtain a table with all attributes and their values, right click on the line with the respective layer and select “Show Attribute Table” from a context menu: A new frame with the table appears and stays open until you close it or remove the layer. The table is accessible only for reading. If you select a row in the table, it automatically highlights the corresponding feature on the map (you may find this feature with the “Zoom to Selection” tool). And reverse, if you select a feature on the map with the "Information" tool), the respective row in the corresponding attribute table becomes selected (the two mentioned tools you can identify via the Annotated figure of the JRODOS tool bar icons).
Figure 20: Show attribute table for layer (left). Attribute Table (right).
By default all loaded shape files are assumed to have attribute values encoded in ISO-8859-1, which is sufficient for most of the European Latin-based languages. However, if attributes were encoded with different character sets (e.g. Cyrillic based or UTF) you will see “strange unreadable symbols” in the Properties Panel or in the Attribute Table. Windows-1251 (CP1251) is the most popular set for Cyrillic data, created on Windows systems. To change the attribute encoding, right click on the line with the respective layer, select “Change Encoding” from the context menu, and change the encoding in the appearing dialogue.
21
Figure 21: Changing encoding for a layer.
Loading non-result map layers
File layers applicable in JRodos JRodos supports two common geographical data formats: ESRI shapefile (*.shp) and geotiff (*.tiff, *.tif). Before you add own such files, please study the specifications in Chapter "Shape or GeoTiff files suitable for JRodos" in the JRodos Customisation Guide.
Rendering the data to the current map views Map layers from other than file storage are cut out to the current map view during the loading process. Map layers from file storage are loaded as full extent layers in one piece into the client's memory. Please note that the loading can take a long time or even overstrain the computer if the files are large. It is only after the loading that the area covering the current JRodos map view is cut out. In particular full extent layer files containing urban areas, roads, or administrative unit information, can be heavy in size, for example 45 Megabyte for roads and about 10 Megabyte for urban areas. Therefore, with respect to these map items, JRodos offers not only the possibility to load the full extent layers as files, but to extract from the database only a small part of the data geographically related to the site under consideration, see chapter on "Loading local map layers around a site from the JRodos GIS data base".
Loading map layers from file storage JRodos supports two common geographical data formats: ESRI shapefile (*.shp) and geotiff (*.tiff, *.tif). For both formats, the projection used in the file should be one of the standard ones. This includes UTM projections, Mercator projections; Krovak based projections, Geographical lat-long projection and many others. A detailed list is available at http://spatialreference.org/ref/epsg/ (more than 85 pages, 50 projections each). When the files are used, JRodos automatically re-projects the data to the projection currently set. Note on Shape files: For JRodos, such files should be uncompressed tiff files and should contain geographic information inside as a header. ArcGIS 8.x and 9.x software is known to produce suitable geotiff files. Note on Geotiff files: For JRodos, such files should be uncompressed tiff files and should contain geographic information inside as a header. ArcGIS 8.x and 9.x software is known to produce suitable geotiff files. To load new map layer from file click on the “Load…” icon in the JRodos Tool bar, or click (Menu Bar)Map → Load layers… In the Data Chooser window, activate "Files" (if not already active). Then, select the desired file and click OK.
22
Figure 22: Load button (left) and the load file dialogue (right)
Loading map layers from PostGIS databases To load existing map layers from the JRodos or some external PostGIS data base click on the “Load…” icon in the JRodos Tool bar, or click (Menu Bar)Map → Load layers… In the File Chooser window, activate the "postgis" tab. Here, you have the possibility to select between the JRodos internal data base and an external source, see Figure 23.
JRodos internal data base The JRodos internal PostGIS data base contains at least the five layers below; they are necessary for the calculation models and must not be removed: admin_europe (administrative units of the European countries) roads (main European roads) urban_europe (European cities and villages) production (European production plus radiological regions data, used for calculation) npp (layer with nuclear power plant site location) JRodos allows adding new layers, deleting old ones, and specifying styles for existing layers; however, this is normally part of the JRodos customisation and not a subject for the general user. For managing data in the JRodos GIS data base, please refer to the JRodos Customisation Guide, GIS data base chapter. When loading the map items "roads", "urban areas" and "administrative units" separately from the JRodos PostGIS database, you should extract only a small part of the data geographically related to the site under consideration rather than loading a full extent file at once, see chapter "Summary". Therefore, select a site, mark the corresponding checkboxes of desirable layers and specify the corresponding radii around the site. It is also possible to load above items in one go, see chapter "Loading local map layers around a site from the JRodos GIS data base".
External Source Specify the connection properties and press the “Refresh” button. Then select the corresponding table rows. Also please check that this database is properly configured and allows external connection from the JRodos Server, because the data is first loaded to JRodos Server and then transferred to the JRodos Client.
23
Figure 23: Load PostGIS layer dialog.
Loading local map layers around a site from the JRodos GIS data base With respect to the map items "roads", "urban areas" and "administrative units", you can load all three items together from the JRodos GIS database, locally restricted to some region around a given site. To load local map layers, click (Menu Bar) Map → Load layer around site… The Set Site window appears. Choose a site from the combo box (). Then set a distance radius for the administrative regions and urban / roads layers and click OK. Messages about the loading status appear in the Message Window. After termination, the respective layers appear in the Legend window (Figure 25).
Figure 24: Set Site dialogue window.
Figure 25: Map Legend window with additional layers.
In the Map Tab, the three additional layers get visualised (Figure 26); however, you may have to zoom in around the site in order to see the details.
24
Figure 26: Map tab window. Roads (white lines), urban (grey polygons) with blue names and admin (black border lines) layers.
Loading map layers from a WMS source
Please note: This task is only possible with working internet connection. If you know that you have a working internet connection, but cannot load from the source, check the internet connection via (Menu Bar) Options Internet_settings (see chapter on "Internet Settings").
To load a new map layer from WMS source click on the “Load…” icon in the JRodos Tool bar, or click (Menu Bar)Map → Load layers… In the File Chooser window, activate "WMS". Then, give a valid URL and press "Connect".
An example URL is given below; use the character string between the quotes; note the “&Request=GetCapabilities” part at the end of the string - that piece is important. http://www.marine-geo.org/exe/mapserv?map=/system/link/server/apache/htdocs/marine- geo/services/ogc/wms.map&SERVICE=WMS&REQUEST=GetCapabilities
When the connection is established, a list of available layers appears in tabular form – see Figure 27. The layers which have a predefined style will have a style preview icon. Select one or several layers by clicking on them with the “Ctrl” key held pressed. As nice example WMS layer is topography ("topo").
Press the "Open" button: The WMS layer is added to the Map Legend and the map view. The map is automatically refreshed – see Figure 28. Please note that the WMS layer appearance is best with "EPSG 4326" map projection ((Menu Bar) Map Set Map Projection; select EPSG and type in the code numbers; takes effect after leaving the "Set Map Projection" menu with OK and restarting the JRodos Client.).
25
Figure 27: Example list of available layers in the connected WMS source.
26
Figure 28: WMS data as a regular map layer.
Loading Google Maps (hybrid view), OpenStreetMaps
Please note: This task is only possible with working internet connection. If you know that you have a working internet connection, but cannot load from the source, check the internet connection via (Menu Bar) Options Internet_settings (see chapter on "Internet Settings").
To load Google Maps, Hybrid view, go to (Menu Bar)Map → Load Google Maps Layer. To load OpenStreetMaps, go to (Menu Bar)Map → Load OpenStreetMaps Layer. The map is added as a separate layer, which gets automatically refreshed to the corresponding resolution on zoom changes. Please note that the Google Maps (hybrid view) / OpenStreetMap" layer appearance is best with "World Mercator" map projection ((Menu Bar) Map Set Map Projection World Mercator; takes effect after leaving the "Set Map Projection" menu with OK and restarting the JRodos Client.).
Figure 29: Google Maps (Hybrid view), OpenStreetMaps as a map layer.
27
Loading and displaying map-type model results
Loading a map-type result layer Map-type model results from a JRodos model calculation can be displayed as maps in the Main Window by browsing to the corresponding result in the Project explorer tree and clicking on it. If loaded in this way, such a result will occupy the JRodos Map Tab. As an example Figure 30 illustrates the resulting map view when the total gamma dose rate was loaded: A corresponding label and the maximum value of the respective result appear in the Map Layer Description field in the upper left corner of the map view. The label includes the result's name and physical unit, date and time of the displayed time-step, and the task and the run name. The location of the maximum value is shown as a separate layer on the map and illustrated by a transparent rectangle. The result and the maximum value layer labels appear in the Map Legend Window, and also the colour code for the result intervals. If a time-dependent map-type result layer is present in the Map Tap, a Time Slider appears in the tool bar (see chapter "Working with the map tools in the Tool Bar"). The respective map-type time series result is available for each ADM time step, until the end of the prognosis time interval. If just opened the values for the first time interval are displayed.
Figure 30: Map result in Map Tab. Map Layer Description Box. Map Legend window.
Zoom level of the loaded result By default, loading a map result layer into the Map Tab changes the map zoom to the extent of the computation grid of the loaded result. If you already have a nicely zoomed map result in the Main Window, and like to keep the zoom scale for one or more following result(s) you want to load for displaying, use the JRodos "Zoom Lock" facility, see chapter on "Zoom level, zoom lock".
Map result tool tips Hovering with the mouse over a grid cell on a map containing grid-type calculation results will produce the "Map tool tips": the cell number and the value(s) in the cell – see Figure 31. If there are several layers with grid-type calculation results under the mouse cursor position, cell-value pairs for all of them appear in Map tool-tip in the same order as they present in the Map Layer Description text box. For wind fields, the speed,
28
the original direction in the wind field data CRS and the geo direction in the WGS84 CRS is presented on the Map tool tips.
Figure 31: Map result tool tips: Cell number and result value in the cell.
Contour plots By default, the values of map-type results are displayed as colour-coded boxes on the map. Additionally, contour plots can be generated in the way described below. To generate a contour plot for a map-type result, go to the Map Legend, right click on the corresponding layer, and select “Contour plot…” – see Figure 32.
Figure 32: Contour plot generation.
The contour generation dialogue window (Figure 33) allows entering contour line values and specifying if the label for the values shall be presented on the map. You can add, edit and delete values manually. Also, you can generate values by selecting the minimum/maximum value, the step, and specifying a linear or logarithmic scale for the generated values in Multiple Contours panel. Please note that set of contour values defined in this way can be saved to and recovered from file with the “Save to File” and “Load from File” buttons. After setting up contour values as indicated above a contour map like shown in Figure 34 is generated:
29
Figure 33: Contour plot generation dialog. Minimum and maximum grid values are shown in the left part of the window
Figure 34: Contour generation results.
The generated contours can be exported to a shape file by right clicking on the layer in the Map Explorer - see Chapter on "Printing or saving map views; exporting map layers"
Interpolate To Points tool
Summary
In JRodos, map-type results are calculated at the centre points of the calculation grid cells. With the tool one can obtain such results for user-defined locations on the map. This can be useful for example when preparing realistic training scenarios with simulated measurements at given detector locations in the progression of a hypothetical accident.
30
As pre-requisite you must set up a comma separated value ("csv") file containing the co-ordinates of the target points for the interpolation. This file has to be deposited into the JRodos Client folder, or - when the "multi-user" mode is enabled, into the user's Client folder. Then, you will carry out a calculation for producing the desired result type(s) on the JRodos calculation grid. If you want to carry out the “interpolate to points” calculation, you should run the preceding model with the “Map” option “Prioritize Contour Polygons” disabled, since the “Interpolate to points” tool delivers flawed results with enabled contour polygons. Finally, you will initiate the interpolation by right-clicking in the Map Legend on the respective result and selecting "Interpolate to points". The result is then interpolated to the given points for each time step and the values are stored in a user-specified file together with the co-ordinates of the points. The above-mentioned csv-file with the co-ordinates defines the target points for the interpolation; however, it does (currently) not include information for displaying the locations of the target points in the JRodos Map tab. If displaying is desired, a respective shape-file has to be generated with some GIS tool, for example QGIS2. The .shp-file can the be added to the default map layers (see Chapter "Configuring the initial load layer list") or added on demand only to the current map view.
Setting up the co-ordinates file; file residence in single user and multi-user mode
To start with, create a comma-separated value (".csv") file with prescribed name "export-stations", for example with Microsoft Excel. The file must contain the longitude and latitude of the desired points as comma separated values in decimal format with dots as decimal separator. It is highly recommended also to specify a name for an easier identification in the output file. Figure 35 shows the .csv-file that was used to produce the demonstration application; here, names are given to the locations, too.
Figure 35: Example for an "export-stations.csv" file
When the multi-user feature is not active3 then: You must deposit file "export-stations.csv" into folder
2 http://www.qgis.org/en/site/ 3 See Chapter "Working with the multi-user feature". 31
Comment: When you got it wrong, the system issues a message; from the text you can see where JRodos expects the folder to be, see example below:
Generating the interpolated results
Carry out a calculation for producing the desired results on the JRodos calculation grid. Then, initiate the interpolation for a result by right-clicking on the respective line in the Map Legend and selecting "Interpolate to points". Figure 36 gives an example. There, the total effective gamma dose rate, effective, was requested for interpolation to the locations defined in the demonstration "export-stations.csv" file from. Please note that the stations are displayed too in Figure 36, because a respective shape-file was generated with QGIS and added to the initial Load Layer List. The interpolated values will be saved in a ".csv" file; you will be asked to specify a name and a location for that
file after the click on "Interpolate to Points", see
Figure 37.
When finished, a message " " will appear in the JRodos Messages window. The generated values are stored in the specified file as comma-separated values, for all the ADM time step intervals covered in the calculation, for one location after the other. Please note: For getting interpolated results (and not only an empty file), the plume must have hit at least one of the stations in at least one time step in the considered calculation area !!! As example, Figure 38 shows the upper part of the .csv-file containing the interpolated the total effective gamma dose rates from the demonstration application for the demonstration "export-stations.csv" file; please note that the locations are also distinguished by name (and not only by their co-ordinates), which is generally recommended.
32
Figure 36: Initiating the interpolation via the Map Legend.
Figure 37: "Save as .csv file" menu.
33
Figure 38: Example for an output .csv - file.
Map-type results in the one available Map Tab When selected via the Project Explorer Tree, only one map-type result per run of a model chain component ("task") can occupy the Map Tab. Selecting a second map-type result from the task will remove the first one from the Main Window and the Legend window, and the newly selected result occupies the Map Tab. Please realize that the whole EMERGENCY model chain represents only one task (consider it as a one-component model chain comprising the four physical models LSMC, EmerSim, DepoM, and FDMT). Exception: One can display map-type results from the LSMC branch "Meteorological information" (e.g. wind fields) at the same time with some other map-type result of LSMC. The selected meteorological information and the other result appear in the Map Tab overlaid in the order as indicated in the Legend Window. If you load map-type results from different projects, all maps related to the previously selected project disappear. If you load map-type results from different tasks in the same project, all of them reside in the Map Tab. In the Main Window, the maps appear overlaid in the order as indicated in the Legend Window. Figure 39 below shows exemplarily two overlaid results (sheltering areas, top, and I-131 ground concentrations, bottom) from two different tasks (EmerSim and LSMC) within one project with the four- component LSMC + EmerSim + DepoM + FDMT model chain.
34
Figure 39: Two grid maps from two tasks in one model chain overlaid in the Main Window.
Working with the map tools in the Tool Bar
Pan/move tool. Zoom tools. Reset map in Main Window. To move a map view left / right / up / down, Click into the Main Window, then use the Left / Right / Up or Down key accordingly. Or: Click on the “Pan Zoom” icon in the Tool Bar (see Annotated figure of the JRODOS tool bar icons), press and hold the left mouse button and drag the map to move it. When the desired view is achieved, release the mouse button. To zoom a map view in or out, Turn the mouse wheel up or down. Or: Click on the “Zoom In / Out” icon in the Tool Bar (see Annotated figure of the JRODOS tool bar icons), make a selection rectangle with keeping the left mouse button pressed, and then release the mouse button.
35
Figure 40: Zoom In / Zoom Out with selection rectangular.
You can return to the previous zoom scale by clicking on the "Previous Zoom” icon, if this icon appears enabled. After that you can return to the prior zoom scale by clicking on “Next Zoom” icon. To reset the map view to the initial context, click the “Reset” icon in the Tool Bar (see Annotated figure of the JRODOS tool bar icons), or select Map → Reset Map on the Menu Bar.
Zoom level, zoom lock By default, visualizing grid maps via the Project Explorer Tree changes the map zoom to the extent of the computation grid of the respective result. If you have a nicely zoomed map result in the Main Window, and like to keep the zoom scale for one or more following result(s) you want to display, click on the "Zoom Lock" icon in the JRodos Toolbar: The zoom lock becomes active and all zoom-related map icons are blocked (Figure 41); all freshly loaded result will appear in the locked zoom scale. Clicking again on the Zoom Lock icon releases the zoom lock.
Figure 41: Zoom Lock icon (left). With active zoom-lock, zoom-related icons are blocked (right).
Distance tool For measuring distances along a curve, click on the "Distance" icon in the Tool Bar (see Annotated figure of the JRODOS tool bar icons), then left click at the starting point of the curve, and continue left clicking until you reach the end point of your intended curve. Watch the Distance Field in the left part of the Status Bar at the bottom of the Main Window: When moving the cursor, the accumulated distance since the start click and the current distance to the last click is shown. To stop measuring, right click with the mouse. To erase measuring lines in the map view, click again on the "Distance" icon.
Plot Builder tool for time dependent results; saving the time series table For time-dependent results it is possible to display the time-dependence in a selected point, or to compare time-dependencies in several points.
36
For that, first click on the Plot builder icon in the Tool Bar (see Annotated figure of the JRODOS tool bar icons). Then, right-click on a desired point on the map - the graph-building menu will pop up. When opened for the first time, there will be only one option: “Build time graph in a new tab”. Select this option by clicking on the offer. A new tab opens, depicting the time dependence in the selected grid point. Under the plot there is also a table with the data for each point of the chart. The data table can be saved to either text or Excel file with the respective Save icons in the tab’s tool bar ( ). As soon as you have created at least one such time profile tab, the right-click menu is enriched with one more option “Build time graph in an existing tab”. When you hover over this option with the mouse cursor a submenu opens, containing a list of all time profile tabs opened so far. You may select an existing tab by clicking on it, or select “Build time graph in a new tab”.
Figure 42: Plot Builder menu for time dependent results
Each time you repeat “Build time graph in an existing tab”, the table under the plot is extended to contain the data of all the added charts. NOTE: You cannot add a chart to an existing tab unless the value types of the charts coincide. If you try to add a chart to a tab which already contains a chart for another physical parameter you will see the warning message in the Message Window.
Figure 43: Plot Builder tab with time dependent results and "Save" icons.
37
Vertical Profile tool for multilevel results; saving the vertical profile table For multilevel results or data (for example, the wind field in the LSMC-NWP data base) it is possible to display the vertical profile in a selected point in the layer, or even compare time-dependencies in several points. For that, first click on the Vertical Profile icon in the Tool Bar (see Annotated figure of the JRODOS tool bar icons). Then, right-click on a desired point on the map. The graph-building menu will pop up. For the first time, there will be only one option in it: “Build vertical profile in a new tab”. Select this only option by clicking on the offer. A new tab opens, depicting the vertical profile in the selected grid point. Under the plot you can also see a table containing the data for each point of the chart. The data table can be saved to either text or Excel file with the respective Save icons in the tab’s tool bar ( ). As soon as you have created at least one such vertical profile tab, the right-click menu is enriched with one more option “Build vertical profile in an existing tab”. When you hover on this option with the mouse cursor a submenu opens, containing a list of all vertical profile tabs opened so far. Select an existing tab by clicking on it, or select “Build vertical profile in a new tab”. Each time you repeat this action, the table under the plot is extended to contain the data of all the added charts. NOTE: You cannot add a chart to an existing tab unless the value types of the charts coincide. If you try to add a chart to a tab which already contains a chart for another physical parameter you will see the warning message in the Message Window.
Figure 44: Vertical Profile tab with multilevel results and "Save" icons.
38
Information tool To highlight an object in a desired layer, please ensure that the object in this layer is not covered by another object from an upper layer. Click on the Information icon in the Tool Bar (see Annotated figure of the JRODOS tool bar icons) and left click on the layer: the selected object (the object under mouse cursor, belonging to the topmost layer) will be highlighted in white. The information about all of the objects, present in visible layers under mouse cursor, will appear in the Properties window along with the map coordinates, corresponding to the mouse cursor position. By default all loaded shapes are assumed to have attribute values encoded in ISO-8859-1, which is sufficient for the most of European Latin-based languages. But if attributes were encoded with different Character sets (e.g. Cyrillic based or UTF) the use will see “strange unreadable symbols” in the Properties window. To change the encoding, please refer to the JRodos Customisation Guide.
Figure 45: Kremenchug reservoir (Ukraine),, selected by the Information Tool and the corresponding information in the Properties window (right), extracted from layers.
For grid maps, the Information Tools shows a value in the click point as well as the maximum grid value in the current grid map. To zoom to selected feature, e.g. if you missed it by accident, click on the Zoom to selection icon in the Tool Bar (see Annotated figure of the JRODOS tool bar icons). The selected object will appear in the centre of the map. To clear selection, e.g. because you don’t need it any more, click on the Clear Selection icon in the Tool Bar (see Annotated figure of the JRODOS tool bar icons), or select Map → Clear Selection on the Menu Bar.
Time slider If a time-dependent layer is present in the Map Tap, a Time Slider appears in the tool bar.
Figure 46: Time slider. Left to right: current time-step, slider, buttons First - Previous - Run - Pause - Next - Last.
39
To start an animation, press the “Run” button. To make a pause in an animation, press the “Pause” button. To go to the first time step, press the “First” button. To go to the last time step. press the “Last” button. To go to the previous time step, press the “Prev” button. To go to the next time step, the “Next” button. To go to some middle time step, press the “Pause” button and drag the slider to the desired position. The current time-step is shown in the left of the time slider. Besides watching the animation, you can check the time-dependence of a parameter in a particular pixel of the layer or even compare time-dependencies in several pixels.
Printing or saving map views; exporting map layers
Please note that for printing or exporting a map view with together with the Map Legend, the Legend must be positioned in the Map Tab (and not in the Properties Window).
To print a current map view, go to (Menu Bar)Map → Print map… In the Print options dialogue, select appropriate parameters and press "Print". To export a current map view as an image go to (Menu Bar)Map → Save as image… In the File Chooser dialogue, browse to the desired folder and type the name of the file; select the format and press "Save". Please note that the default format is "png". If you choose another format, you must type the extension .jpg, .gif explicitly in the file name. To create an animated image first make sure a time-dependent result is present in the Map Tab. Then go to (Menu Bar)Map → Create Animated GIF… In the File Chooser dialogue, browse to the desired folder, fill in the name of the file and press "Save": JRodos will start moving the time slider and capturing map screenshots. Do not touch the Map Tab during file creation! For exporting a map layer to an ESRI shape file please see Chapter "Working with the Map Legend".
Configuring the initial load layer list
On start-up, JRodos offers a default map view consisting of the "initial load layers" which can be configured via a menu. The "initial load layer list" is user related and can be different for different users. The layers from the list are also used in automatic report generation; make sure that they are loaded to the Server part; see Chapter "Options in the Menu Bar, "Report Settings". How to configure the Layer List is described in the JRodos Customization Guide, Chapter on "Administration of customized start-up settings for users and user groups", "Tab [Layer List].
40
Visualization of NWP data and real-time data
Numerical weather prediction (NWP) data are available from meteorological services - in JRodos called "providers". The data may cover limited areas: parts of the own country, the complete own country plus some surroundings, parts of Europe, parts of the northern (or southern) hemisphere. In addition, there are open data from models predictions covering the whole world, for example the world-wide applicable data from the American NOMAD server4. In JRodos, NWP data are used for near range calculations with one of the models for the Local Scale Model Chain (LSMC), and for far range calculations, by default with model MATCH. Measured of "real time (rt)" meteorological and source term data are used as input in JRodos for diagnostic calculations, for special models, or simply for displaying.
NWP data
To visualize NWP data select (Menu Bar) Prognosis Show NWP data…. The Choose NWP data dialogue opens. To begin with, select a provider from the expandable list, see Figure 47.
Figure 47: Choose NWP data dialog - Selection of provider.
The further appearance of menu "Choose NWP data" and the respective specifications is different for standard and special providers; see Figure 48, which means, that the appearance depends on the type of the selected provider.
4 US National Oceanic and Atmospheric Administration NOAA operates four different NOMADS Servers that host NCEP Model Products. National Centers for Environmental Prediction. NCEP www.ncep.noaa.gov/ - The U.S. National Weather Service office that provides worldwide forecast guidance products. 41
(a) DB based providers (b) File based providers Figure 48: Choose NWP data dialog for "standard" (a) and "special" (b) providers.
Standard provider, Figure 48a: Select the analysis time (in UTC). Watch the status bar at the bottom of the menu, and wait until the "Field name" shows entries. Then, choose between single or multi-level fields, and select the data field to be displayed. After pressing OK the preparation of the data may take some time - watch the status bar at the bottom. When finished, the chosen field will be shown for the full extend of the spatial area covered by the data.
Special provider, Figure 48b: Firstly, specify the centre point around which the NWP data shall be displayed, either by selecting a site from the expandable list, or by indicating the location on the map using icon . You must also give radius around the location for the distance up to which the data shall be displayed. Only after that select the analysis time (in UTC). Watch the status bar at the bottom of the menu, and wait until the "Field name" shows entries. Then, choose between single or multi-level fields, and select the data field to be displayed. After pressing OK the preparation of the data may take some time - watch the status bar at the bottom. When finished, the chosen field will be shown in a square that is centred at the chosen location. Note that the data chooser dialogue does not block map functions; that is, zoom in/zoom out, pan, animation control, are available.
The Choose NWP data window remains on top of the map and may block your view. You can click on the Collapse Dialog/Show Dialogue line (just below the window title) and can move the collapsed window out of the way. Afterwards, press Show Dialogue to restore the window.
If the Provider slider does not contain entries, or the Analysis time slider does not contain entries then one must check the provider and data definition and import. If the selected field will not show values in selected area / site for several or all fields, one should check if the "Zoom lock" feature is responsible. If the selected field will not show values in selected area / site for specific fields, then one should check the Grib- to-LCMC mapping table. Please see the Customization Guide for more details (Chapter on "Recommended procedure after defining a new provider and using new data"). If the selected field will not show any values in the intended area, the data of the selected provider do not cover the area, or it was not specified that the data of the selected provider apply for the given site or location - check the provider settings. Multilevel field data contain data for several vertical levels. With the slider on the left side of the picture that appears in the window, you select the vertical level to be shown (Figure 49). Note: If you have the feeling that "the picture does not change", pay attention to the legend - the values for the colours change when changing the level (except for the wind field). Figure 49 shows the "Wind field" as an example for multilevel field data. Please note: The vertical layer numbers do not represent "meters above ground", but are a level identification number. Number "zero" represents "ground level" (temperature at 2 m, wind at 10 m). Except for number zero, physically higher levels have lesser numbers (e.g. level 23 lies physically higher then level 24).
42
Figure 49: Prognosis visualization example: Wind field. To the left, vertical level silder.
Real time (measurement) data
To visualize measurement data as graph+table select (Menu Bar) Measurements → Show MeasurementsWindow "Choose Measure Data" pops up. Please select first the Provider. Then select Station and Height. "Stations" means locations of -detectors with own geo-co-ordinates independent of the JRodos grid cells. To see the locations of the stations click "Show_Stations" at the bottom and all stations are displayed on the map. The name of a station you get in the Properties window at the right side by choosing the information mode in the Tool bar and clicking to a station. The available measurements are shown in the window. Select one measurement type and then set the time period. Minimal and maximal available time steps for the chosen measure are shown in the grey fields. A new tab with the corresponding information appears in the Main panel. One may collapse the dialogue by clicking Collapse Dialogue or Show Dialog. The dialogue doesn’t block the map (zoom in/zoom out, pan, animation control is available).
Figure 50: Choose measure data dialogue (left) and Measurements visualization: wind velocity.
43
To visualize measurement data on the map select Measurements → Show Measurements on Map…. A popup window of the Choose measurement data dialogue opens. A user should select Provider, parameter set (measure type, aggregation, unit, medium and measure object) and Height. The available measurements will be presented in the table. Select one measure type and then set the period; the minimal and maximal available time steps for the chosen measure are shown. The dialogue remains on top of the map but a user can collapse/restore it if needed (click on Collapse Dialogue or Show Dialogue button). The dialogue doesn’t block the map (zoom in/zoom out, pan, animation control is available). Measurements will be shown in the map (just close the dialog) and can be treated as time-dependent results (including time slider, plot function etc).
If time-dependent results and measurements are displayed on map one common time slider is used. This can lead to problems when results from very different time intervals are present. It is therefore recommended to remove unnecessary items from the map view before displaying measurement data.
Figure 51: Choose measure data for geo-spatial measurements dialog.
44
Figure 52: Choose measure data for geo-spatial measurements dialog.
Tips for controlling the quality of NWP and real time data
For single level field data Use the time slider to obtain an impression of the time development of the spatial field on the grid. Use the Plot Builder tool for time dependent results to display time profiles at a selected grid points in graphical and tabular form; the tables can be saved as text files or as Excel files.
For multi level field data Use the vertical layer slider to obtain an impression of vertical profile of the data field on the grid. Use the time slider to obtain an impression of the time development of the field at the selected vertical level. Use the Plot Builder tool for time dependent results and the Vertical Profile tool for multilevel results for displaying time and vertical profiles at selected grid points in graphical and tabular form; the tables can be saved as text files or as Excel files.
45
Working with projects
A JRodos "project" contains of one or more "tasks", that is, realisations of a model or a model chain.
Creating new projects
To create a new project click (JRodos Tool Bar) “Create New Project”, or select (JRodos Menu Bar) File → New project. The “Create new project” dialogue will pop up. Fill in the project name, optionally a project description, and select the model chain. The project name must not coincide with the name of already opened projects and stored in the database projects. If there is a name coincidence, a corresponding error message is issued. A newly created project gets stored in a database automatically. NOTE: The string, entered in “Project name” text field, is trimmed so that opening and closing spaces aren’t included in the project’s name. Therefore a string ” name 1 example ” will result in “name 1 example” being saved as the project’s name.
Figure 53: “Create New Project” button and “Create new project” dialog.
Manipulating existing projects with tool bar and file menu options
Note: The “Open / Rename / Delete project” dialogue is realised as sort-able tables. Such tables offer features like sorting and marking several lines, either connected ones or not connected ones which are explained in "Appendix: Working with sort-able tables".
To open an existing project click (JRodos Tool Bar) “Open Existing Project”, or select (JRodos Menu Bar) File → Open project. The “Open project” dialogue will popup with information about available projects: project name, user name, dates, description, and model chain.
Figure 54: “Open Existing Project” button and “Open project” dialog.
46
Figure 55: “Open project” dialog; selecting projects from the table.
To rename an existing project select (JRodos Menu Bar) File → Rename Project. A list showing all existing projects will appear; select the project to be renamed from the list by clicking on it (Figure 56 left). The “Rename Project” dialogue will pop up (Figure 56 right). In the “Rename Project” dialog you can change the project name and/or the project description. The project name must not coincide with the name of already opened projects and of any5 project stored in the database. If there is a name coincidence, a corresponding error message is issued. NOTE: The changed name and description of a project get stored in a database automatically. NOTE: The string, entered in “Project name” text field, is trimmed so that opening and closing spaces aren’t included in the project’s name. Therefore a string ” name 1 example ” will result in “name 1 example” being saved as the project’s name.
Figure 56: Project selection from the list of existing projects (left), and the “Rename Project” dialog (right).
To save an open project click (JRodos Tool Bar) “Save Project”, or select (JRodos Menu Bar) File → Save project. The “Save project” dialogue will pop up. Select the name of the project you want to save and press OK. If there is only one project which is open the “Save project” dialogue won’t popup and saving will start right away.
Saving a project allows continuing the work with the project at later times. Users with user privilege can save only own projects. A user with Admin privilege can save every project.
Figure 57: “Save Project” button and “Save project” dialog.
To copy an existing project select (JRodos Menu Bar) File → Copy project and the “Copy project” dialogue will popup. Select the name of the project you want to copy, press OK, and then give a name for the project
5 At present, this is not user-specific, that is, one cannot use a project name even when the project is associated with another user. 47
copy. The project name shouldn’t coincide with a name of projects already open or stored in the data base. If there is at name coincidence a corresponding message is issued. If some user A copies a project from some user B, then the copy user will be “A” and user A can perform all operations on the copy. The project copy will contain all input information from the original. Output (information and results) is not copied.
Figure 58: “Copy Project” dialogue and the dialogue for setting a name for a project’s copy.
To close an existing project select (JRodos Menu Bar) File → Close project and the “Close project” dialogue will popup. Select the name of the project you want to close and press OK. If there is only one project which is open the “Save project” dialogue won’t popup and closing will start right away. Before closing you will be asked if you want to save the project to the data base.
Figure 59: “Close Project” dialog.
To delete a saved project from the JRodos project database select (JRodos Menu Bar) File → Delete project and the “Delete project” dialogue will popup with information about available projects: project name, user name, dates, description, and model chain. Please note: You can sort - for example by name or by creation date - by clicking on the respective label on the topmost line. You can also filter by typing a regular expression in one of the empty boxes in the line below the topmost line (all columns except dates). This project to be closed must not be open. If it is, a corresponding message is issued and you will be asked to close the project first. Please note, that users with user privilege can delete only own projects. A user with Admin privilege can delete every project.
Figure 60: “Delete project” dialog.
48
With JRodosMay2013, it is possible to export and import complete JRodos projects (input, results, and messages) to/from file. This is useful for taking runs made elsewhere back home or exchanging runs between users e.g. by mail or communication with JRodos team for debugging etc. Please note: Re-running of an exported project on the import machine is only possible if the input data are completely available there; this may not be always the case (example: NWP data). File size example: about 40 Mega-Byte for 24 hours INEX1P2 scenario (short source term, 24 hour prognosis, hand weather). To export an existing project, select (JRodos Menu Bar) File → Export Project to File ... and then select a project in the opening window (Figure 61). A message is issued in the JRodos Messages window that exporting the project is on the way, and that this may take a while (bottom message line in Figure 62). After some time, the “Save Exported Project to File” dialogue will pop up; browse to a suitable folder and give a name to the file. The project becomes saved in the data base. For importing an existing project exported to file to the JRodos DB, select (JRodos Menu Bar) File → Import Project from File to DB" and browse to the target file in the opening window (Figure 63).
Figure 61: “File - Export Project to File ...” menu and project selection dialog.
Figure 62: JRodos messages, and “Save Exported Project to File” dialog.
49
Figure 63: Importing a Project from File to the JRodos DB.
Manipulating open projects with the Project Explorer
For opened projects - that is, those appearing in the Project Explorer Window - project manipulations are possible directly in the Project Explorer. To get the project manipulation list for an open project in the Project Explorer, select the project by right-clicking on the respective project node, and then select the desired manipulation by clicking on it, see Figure 64. Details about the offered operations can be found in the Chapter on "Manipulating existing projects with tool bar and file menu options".
Figure 64: Popup menu for project node.
50
Working with the Project Explorer
A JRodos "project" consists of one or more realisation - aka "task" - of a model or a model chain. A successfully carried out task (that is, one that terminated normally and did not abort) is called a "task instance" or "instance" for short. The JRodos Project Explorer Window shows all messages, input, and output information related to a project and the respective task(s) in form of an information tree, the Project Explorer tree.
Nodes in project explorer tree and getting information about them
To get more information about some node in the tree, hover - without clicking - with the mouse pointer over the text label to the right of the node, and information appears in the tool tip box. For a project node: Name, description (if specified), user name, creation date and last modification date, number of tasks etc. For a task node: Name, project name, task status. For a data node: Name, description (if specified), unit (if specified), task name, folder name (as parent) etc. If some node in the information tree bears the plus-icon, clicking on it will produce an information sub-tree. Clicking on a visible minus-icon will close the opened information sub-tree.
Figure 65: Tool tip boxes for different nodes. Top to bottom: for project, task, data node.
51
Project and task operations with the Project Explorer
Right clicking on a project or task node produces a pop-up list with varying items that depend on the selected node. On the level of a project node, for example, project manipulations like “Save project” and “Close project” are possible, see Chapter on "Manipulating open projects with the Project Explorer". On the level of a task node, for example, task manipulations like “Init”, "Run" and “Stop” are possible, seeFigure 66.
Figure 66: Popup menu for a task node.
To initialize a task select the task node, right click on it and select “Init”. The initialisation interface for the task appears. NOTE that after successful initialisation, the task state will change to “Ready”, and all results related to a previous run of the task will be cleared and the results folder becomes empty. If the task depends on results of another task (model), such as for example EMERSIM depends on LSMC results, for some models like EMERSIM and FDMT the respective result link is established manually during the task initialization step via the Select previous task dialogue which starts after selecting “Init”. For other models like MATCH and ERMIN the Select previous task dialogue is called from the model's own user interface. Please note: Only open projects can be selected in the model linking dialogue. If you select a project calculated earlier and then closed, you must open it before.
Figure 67: Select previous task dialog
To run a task select the task node, right click on it and select “Run”. The calculation will start and the task state changes to “Running”. After successful completion the task state changes to “Ready, else to or “Failed”. To stop a task select the task node, right click on it and select “Stop”. The task will be stopped and the state changes to “Stopped” which is synonymous to “Failed”. Some actions can be done after stopping because of delays in the communication between the computational model and the JRodos system.
Figure 68: Initializing, running and stopping the task in Project Explorer Tree.
To rename task select the task node, right click on it and select “Rename task”. The “Set new name dialog” appears where you can change the name of the task.
52
Figure 69: Rename task menu item and Set new name dialog in Project Explorer Tree..
Please note: A “star” (*) always appears before the task name after task state changes. The star disappears after saving the project into the data base.
Reporting related operations in the Project Explorer
Manual report generation To generate reports manually select the respective data node, right click on it and select the desired report layout or all report layouts.
Figure 70: Generate Task Report item in the Project Explorer Tree.
Automatically generated reports The automatic report generation was moved from the Client to the Server. General users access the automatically generated reports on the Client as before, however, the reports first must be transferred from the Server to the client. This is achieved by right-clicking on a project that generated automatic reports, selecting "Load Generated Reports", and specifying a suitable location on the Client (Figure 71). In the example shown, only one result (Cloud arrival time) was automatically generated.
Figure 71: Load generated Reports item in the Project Explorer Tree.
53
Tip: For selecting a series of results from the list for the transfer, click on the first and the last while keeping the "Shift" key pressed. For selecting a single result, click on it while keeping the "Control" key pressed. The background layers visible in the generated reports are the ones defined in the user-dependent Initial Load Layer list. The map layers defined in that list have to be loaded to the Server side; see also Chapter "Options in the Menu Bar, "Report Settings". The generated reports are stored in the Server part, in folder
Result related operations in the Project Explorer
List of visualisation options for a result Right clicking on a result node produces a pop-up list showing the visualisation options for the result item (Figure 72). The items in the list depend on the selected result type: maps of spatial fields and time-dependent spatial fields - optionally as coloured grid cells or as coloured iso-polygons series of values on the grid spectral data (EMERSIM, FDMT) text / html / table data The example in Figure 72 shows the visualization types available for the time-dependent map result of LSMC "Total potential dose [mSv]" at the end of the calculation episode.
Figure 72: Data visualize types selectable in Project Explorer Tree.
To choose a data visualization type for an individual result in the Project Explorer tree, select the respective result node, right click on it and select the desired data visualization type from the list of available types presented in the pop-up menu. To visualize data with the default data visualization type double-click with the left mouse button on the desired data node. Since February 2017, the selection of nuclide-specific map-type results is done via the Multiple Nuclides Visualizer, see respective sub-chapter.
Copy Item Path to Clipboard Selecting "Copy Item Path to Clipboard" allows to obtain the path of the result item in the JRodos Result Tree for further usage; this feature is for example used for setting-up the Statistic Output generator or the Access of results via a 3rd party GIS.
Visualize on map (Default) and Visualize on map (Iso-polygons) The Default visualization applies for the displaying of map-type results in the JRodos Map tab and in automatically generated reports alike, and is user specific.
54
Figure 73 gives an example for displaying the LSMC result "Total potential dose [mSv]" as colored grid cells. Figure 74 gives an example for displaying the LSMC result "Total potential dose [mSv]" as colored iso-polygons.
Figure 73: Visualisation on map as coloured grid cells, example.
Figure 74: Visualisation on map as coloured iso-polygons, example.
55
The standard default visualizing mode is "Visualize on Map (Default)". Visualization as iso- polygons can be made default by selecting in the JRodos Menu bar Map → Prioritize Contour Polygons (Figure 75).
Figure 75: Making visualisation on map as iso-polygons the default.
Multiple Nuclides Visualizer On request of operational users, the former limitation of the number of nuclides that can be considered in a run with any of the LSMC models was given up and calculations with 100 radionuclides or more became possible. Formerly, the nuclide selection presentation consisted of a mere alphabetically ordered list without any indication how much each nuclide contributed to the result. With JRodos February 2017 the way to present and select nuclides for displaying was completely changed, with the intention to facilitate the nuclide selection as well as to offer the possibility to identify and remove nuclides are not relevant for the problem considered (this allows to save computation time, too).
By default, the nuclide dependent LSMC results activity concentrations in air, on ground, and ground dose rates are viewed with the "Multiple Nuclides Visualizer": Right-click on such a result on the Result Tree and select this visualization type (Figure 76), or left click on the result to open the nuclide selection window directly.
Figure 76:Default visualization for nuclide dependent results.
Figure 77 and Figure 78 give an examples of such nuclide selection window: it consists of a status bar (appears blank in the examples), a box showing nuclides together with percentage contributions, and below a file save icon, two filters, and a "Sort by" combo-box; Figure 77 shows the "Sort by value" and Figure 78 the "Sort by name" variant.
56
Figure 77: Default visualization for nuclide dependent results (example; sorted by value).
Figure 78: Default visualization for nuclide dependent results (example; sorted by name).
The reference value "100 %" is defined in the following way: In a first step, for each nuclide the maximum value over all grid cells and time steps is determined In a second step, the sum of these maximum values over all nuclides is calculated: This defines "100 %" The numerical values for each nuclide in the Table show the contribution of the nuclide to the 100 % value. Please note that the values are updated with every time step, that is, the numbers may change with each step while a calculation is still going on. The percentage values can serve as a broad indicator for the relevance of the nuclide to the considered result; for such purpose, the "Sort by value" seems more suited than "Sort by name". The two filters regulate the coloring scheme: Red <=> Nuclides with percentage values equal to or exceeding "High" Black <=> Nuclides with percentage values between "Medium" and "High" Gray <=> Nuclides with percentage values less or equal to "medium" Two boarder settings: "Medium" [0] and "High" [0] : Nuclides with zero percentage in gray, all others in red "Medium" [0] and "High" [100] : Nuclides with zero percentage in gray, all others in black The calculation of the reference value and the percentages requires some time. This becomes noticeable e.g. when viewing nuclide-dependent results from loaded projects that were saved before the feature existed, you can then follow the progress with the status bar.
57
Visualize as Voronoi diagram
There is a possibility for to represent results as a Voronoi diagram6, including time-dependent results. This requires the preparation of such diagram on the base of JRodos grid points. The clipped envelop is the same as the default grid visualization envelop.
The option is available only for grid types that are initially constructed as a regular or a semi-regular set of grid points” (the classical telescopic JRodos grid belong to the semi-regular class). Initially irregular grids usually use the Voronoi diagram as the default visualizer. Naturally, the Voronoi diagram option is not available for river results. To visualize data as Voronoi diagram, right-click on result line in Project Explorer and select "Visualize as Voronoi diagram" (Figure 72).
Visualisation of map-type results on NUTS3 administrative unit grid
There is a possibility for representing results on the basis of NUTS3 administrative units7. This requires interpolation of the JRodos results calculated on grid points to a grid consisting of irregular NUTS3 polygons grid. This includes also time-dependent results.
In JRodos, EU NUTS3 polygons are contained in the default (EU) engine data; they can be loaded as a map layer. People with more detailed such data for a given region e.g. in the form of shp-files may add them to the data base. To visualize data on the basis of NUTS3 administrative units, Make sure you are using EU engine data Right-click on result line in Project Explorer and select "Visualize on NUTS3" grid, see Figure 79
Figure 79: Visualisation on NUTS3 grid; map view and selection in Project Explorer Tree.
6 In mathematics, a Voronoi diagram is a partitioning of a plane into regions based on distance to points in a specific subset of the plane (source: https://en.wikipedia.org/wiki/Voronoi_diagram)
7 (Source: Wikipedia) NUTS (fr. Nomenclature des unités territoriales statistiques; Systematik der Gebietseinheiten für die Statistik; Nomenclature of Units for Territorial Statistics) is a geocode standard for referencing the subdivisions of countries for statistical purposes. The standard is developed and regulated by the European Union, and thus only covers the member states of the EU in detail. There are three levels of NUTS defined, with two levels of local administrative units (LAUs) below. Note that not all countries have every level of division, depending on their size. One of the most extreme cases is Luxembourg, which has only LAUs; the three NUTS divisions each correspond to the entire country itself.
58
List affected urban areas
For map-type results, JRodos can create a list of urban areas (cities and villages) where for at least one grid cell a user-definable threshold value is exceeded; for time-dependent results, the first time step that this happens is recorded. This allows for example to identify urban areas affected by countermeasures or where dose values are exceeded for the first time, and store the list as text file or Microsoft EXCEL file.
For creating such list, first get a suitable map type result into the Map tab. Then, in the Project manager, right click on it and select “List of affected urbans” in the appearing menu (Figure 80).
Figure 80: List affected urban selection.
A table appears with the columns "Name", "Population", "Threshold Exceeding Time" and "Max. Value"; by default, the threshold value is zero (Figure 81 top). By typing a positive non-zero value and clicking on "Apply" one can filter out the urban areas where this value is exceeded (Figure 81 bottom). The result chosen for the examples in Figure 80 and Figure 81 is the total potential effective dose (mSv) until the end of the calculation episode. With the threshold value set to 10 mSV in Figure 81bottom, all urban polygons are filtered out where at least one calculation grid cell in the area exceeds that value; the first time this happens is also recorded and the maximum value found, too.
Figure 81: Example table, with threshold value zero (top), with user defined value (bottom) .
59
Please note When you use the icons below the table for saving to text file or Excel file, always all available entries are saved, independent from the filter setting. For saving the filtered table, use "Ctrl-A" to mark the complete table content and then "Ctrl-C" to copy the content into a buffer. With "Ctrl-V" you can paste the content from the buffer into a target text or Excel file. The degree of detail for "Name" and "Population" in the table is determined by the entries in the underlying urban data information layer in the JRodos GIS database. The urban data GIS table contains - among others - polygon or multi-polygon features with attribute “name”. Affected geometric features with empty or null “name” attribute are marked by a blank name field in the list. The example tables shown in Figure 81 were produced with the default "urban_europe" layer that is included in the JRodos standard installation; there are many unnamed geometric features (indicated by blank name fields), and there is no population information available (indicated by values "-1"). You can visualize the names from the underlying urban information layer names in the GIS data base in the Map tab in the way illustrated in Figure 82 (there, the default urban_europe layer is selected).
Figure 82: Displaying the underlying urban information layer in the Map tab.
By activating the information mode in addition, you can obtain detailed information about the different layers for any cell in the calculation grid; to exit the information mode, click on the "Clear selection" icon in the JRodos Tool bar.
Figure 83: Displaying detailed information about the different layers for a cell in the calculation grid.
60
Visualisation of spectral data EMERSIM and other models may offer several results in spectral form, for example the result “Population spectra, inhalation, thyroid organ”. This visualization type produces a histogram with logarithmic scales for both axes.
Figure 84: Data visualization type selection for spectral data.
Figure 85: Histogram plot visualizing spectral data.
Text / html / table results It is possible to search within texts / tables by entering a part of the search word in the Search Bar and navigate with “Find Next “/ “Find Previous” if needed.
Figure 86: Text data and the Search Bar.
Text / table results can also be copied to clipboard. Select the information with the mouse and press Ctrl + C. Text / table results can be saved to a file. This can be done with the Save button connected to Search Bar or, in some cases by right clicking on the item in the Project Explorer tree (e.g. for Console Messages, High Level Messages).
Figure 87: Save button within the Search Bar (left) and ”Save to file” right click option (right).
Text / table results can be sent to a printer. This can be done with the Print button connected to the Search Bar. Examples of text / table results are the “Input Summary” from the RODOS-Lite interface, the Console Messages and the Table results of LSMC.
61
User policies, multi-scenarios support
JRodos supports the user policy "Simple" (default) and "Advanced". The policy can be set by the user via (JRodos Menu Bar) Options → User policy (Figure 88).
Figure 88: Change User policy option.
Below follows a summary of the practical consequences the two policies. Please note that the Emergency model chain always implies "Simple" user policy.
Simple (default): One project can contain only one task For new projects only: On creation of a new project - by choosing “Create New Project”, or by copying an existing project - the input windows appear automatically for each model in the model chain of the project, one after another. If some model in the project ("ModelB") depends on the results of another model ("ModelA") (as EMERSIM depends on LSMC for example): - If the project contains a successfully completed "ModelA" task instance, the link establishes automatically inside the project, as defined for the model chain (<=> no linking dialogue will appear). - If no such result delivering task instance is present in the project, the user must establish a link to an applicable task instance in some other open project. In such cases, the linking dialogue will appear during the initialization step. After terminating the initialisation (e.g. after pressing the RODOS-Lite “Submit” button for the last model in the chain) all models in the project's model chain will start running one after another. After termination, the project is saved automatically to the data base. For new and existing projects: You can always initialise a task individually by right mouse clicking on the respective task node. If some model of the task ("ModelB") depends on the results of another model ("ModelA") (as EMERSIM depends on LSMC for example) the user must establish a link to an applicable task in an open project (the current one or another one). The linking dialogue will appear during the initialization. After terminating the initialization (e.g. by pressing the RODOS-Lite “Submit” button) only the task under consideration starts running. Saving to the data base has to be done manually.
Advanced: One project can contain several tasks One project may have a node folder containing several tasks. Each task can be processed separately. Tasks within one project can be copied, renamed, and deleted. Note that it is not possible to delete the last task: at least one task must be present in any project. For new or existing projects: To init or run any task right mouse click on the respective task node. If the model of the task ("ModelB") depends on the results of another model ("ModelA") (as EMERSIM depends on LSMC for example) the user must establish a link to an applicable task in an open project (the current one or another one). The linking dialogue will appear during the initialization. Saving to database has to be done manually.
Because user policy "Advanced" means that a project can contain several tasks, for example several LSMC runs, it can be useful for model comparisons and multiple scenario studies.
62
Figure 89illustrates an LSMC-EMERSIM-DEPOM-FDMT project with a task node folder EMERSIM that contains three instances (each for example with a different countermeasure timing), and also the possible task manipulations.
Figure 89: Multi-instance support.
For multi-instance support, you must switch to user policy "Advanced" via (JRodos Menu Bar) Options → User policy.
63
Working with models and model chains
Working with the Emergency or the EmergencyLite model chain
JRodos offers a model chain called Emergency that contains the models LSMC + EMERSIM + DEPOM + FDMT and is designed for straightforward assessments of the radiological situation and the areas with a potential for early phase and food countermeasures for up to about 1000 km distance to the release point. For an easier handling, there is also a model chain called EmergencyLite; it consists of the same model sequence but has reduced input possibilities and reduced result tree. The "Result Guide for the models in the JRodos Emergency Model Chain" describes all available result types from models LSMC, EMERSIM, DEPOM, and FDMT. To create an Emergency or EmergencyLite project, select File → New project… or press the “New project” button in the toolbar. In the dialog, select as model chain Emergency (Figure 90 left) or EmergencyLite (Figure 90 right), enter the project name, and press OK.
Figure 90: Creating an Emergency (left) or EmergencyLite (right) project.
The respective project becomes created. The user input application, RODOS-Lite8, is realised a JRodos tab and the RODOS-Lite window will appear automatically. Fill out each RODOS-Lite input tab9, one after the other, and then press the RODOS-Lite “Submit” button: LSMC, EMERSIM and then DEPOM and FDMT become started. After termination, the project with all result and input information gets automatically saved to the database. Within one project, the Emergency or EmergencyLite model chain cannot be executed again, and the individual models in the chain cannot be started on their own right. However, one may copy a complete such project (the copy contains all input information), then modify the input data, and finally execute the project copy as a new project.
Working with the Preparedness model chain
This new model chain is for non-expert users employing JRodos with the sole intention to get an overall impression of the severity of a given radiological situation resulting from a nuclear accident or a nuclear emergency, without technical explanations or scientific reasoning.
User input is basically reduced to the selection of the site, specification of the source term, and the selection of pre-defined weather conditions (relation of turbulence to weather conditions taken from http://oregonstate.edu/instruct/dce/ne581/eleven/index.htm).
8 The RODOS-Lite input interface serves for initiating any model chain containing an LSMC, EMERSIM, DepoM or FDMT model, as for example Emergency or EmergencyLite; a summary of it's main features you find in the Chapter on "RODOS-Lite". 9 In an EmergencyLite project, the RODOS-Lite tabs [Countermeasures] and [Food chain] are hidden; the models EmerSim and FDMT run with default settings 64
All other required input is fixed (for example, the selection of the LSMC model, or the inner grid cell size i.e. the calculation distance) to pre-defined settings.
The Result Tree is reduced to results of type "Areas affected by" for giving an at-a-glance indication where, and which, actions are needed or not needed, and limited information allowing at least a most basic understanding of the exposure that leads to the observed severity indications, and also of the possible influence of uncertainties. To create a Preparedness project, select File → New project… or press the “New project” button in the toolbar. In the dialog, select Preparedness as model chain, enter the project name, and press OK, see Figure 91.
Figure 91: Selecting the Preparedness model chain.
A Preparedness project becomes created, and the RODOS-Lite tab and window will appear automatically. However, the Preparedness RODOS-Lite interface has only four theme tabs, and the weather tab is special, see Figure 92: The user can choose between pre-defined weather sequences by clicking in the "Enter your weather" box and selecting one of the weather descriptions by clicking on it, and can specify a wind direction using the magic rod, see Chapter on "RODOS-Lite". When ready, press the RODOS-Lite “Submit” button. A summary of RODOS-Lite features you find in the Chapter on "RODOS-Lite" in this User Guide. In JRodos, the RODOS-Lite input summary can be inspected by clicking Input → UI-Input → Input summary in the Project Explorer.
Figure 92: RODOS-Lite tabs with open [Weather] tab in the Preparedness model chain.
LSMC, EMERSIM and then DEPOM and FDMT become started. When finished, the Project with all result and input information gets automatically saved to the database.
65
Working with LSMC+EMERSIM+DEPOM+FDMT
In current release LSMC, EMERSIM, DEPOM and FDMT models are integrated, therefore in the following section the creation and running of an LSMC+EMERSIM+DEPOM+FDMT project is discussed. Explanations concerning RODOS-Lite functionalities are included.
Creating LSMC+EMERSIM+DEPOM+FDMT projects To create a project with the L+E+D+F tasks (L+E+D+F project) Click on the “Create New Project” button in the Tool Bar. Or: Choose File → New project in the Menu Bar. The “Create new project” dialogue will popup. Give a project name, optionally a project description and set the model chain to LSMC+EMERSIM+DEPOM+FDMT. If your project name coincides with some already existing project you will get a corresponding message. A project with the name of your L+E+D+F task will appear in the Project Explorer tree, showing a task node for each model chain component.
Figure 93: Project with L+E+D+F task inside and Input/Output folders for each model.
The default L+E+D+F project contains a Messages folder, which contains High-level messages and Console messages. During working with L+E+D+F project the related high-level messages will appear both in Message Window and Messages folder. Also the console messages will appear in Messages folder too in the correspondent section. To read the messages a user should select the desired section and click on it. The tab with the messages and other information will appear in Main Window. Information contains message time and level. Level can be Info, Warning or Error. The latest messages appear on top of the table.
Figure 94: Messages. The tab with the high-level messages and other information
Initializing and running LSMC tasks. To init the LSMC task a user should init it like any other Task (see Chapter on "Working with the Project Explorer A JRodos "project" consists of one or more realisation - aka "task" - of a model or a model chain. A successfully carried out task (that is, one that terminated normally and did not abort) is called a "task instance" or "instance" for short. The JRodos Project Explorer Window shows all messages, input, and
66
output information related to a project and the respective task(s) in form of an information tree, the Project Explorer tree. "): navigate to the task node, right-click on it and select the “Init” item. RODOS-Lite application, which is integrated inside JRodos, will start and RODOS-Lite wizard will appear as a tab in Main Window. Tab’s name for RODOS-Lite will be the following: “RODOS-Lite:
Initializing and running EMERSIM tasks. As EMERSIM depends on LSMC results on the task initialization the model linking dialogue starts. Select the LSMC model on the base of which you want to calculate EMERSIM model and press OK. RODOS-Lite with windows for EMERSIM model starts in a new tab. After submitting data a user can run it like any other Task (see Chapter on "Project and task operations with the Project Explorer"): select the task node, right click on it and select the “Run” item. EMERSIM produced tables, histogram results and map fields both time dependent and static.
Running DEPOM tasks. As DEPOM depends on the LSMC results on the task initialization the model linking dialogue starts. Select LSMC model on the base of which you want to calculate DEPOM model and press OK. Than run it like any other Task (see Chapter on "Project and task operations with the Project Explorer"): select the task node, right click on it and select the “Run” item. Three map results are produced by DEPOM: Sum of rainfall, total deposition from iodine and total deposition from aerosol.
Figure 95: Selection of available LSMC model and its results to run EMERSIM, DEPOM model
Initializing and running FDMT tasks. As FDMT depends on the DEPOM or FOMM results on the task initialization the model linking dialogue starts. Select DEPOM or FOMM model on the base of which you want to calculate FDMT model and press OK. RODOS-Lite with windows for FDMT model starts in the new tab. After submitting data a user can run it like any other Task (see Working with the Project Explorer A JRodos "project" consists of one or more realisation - aka "task" - of a model or a model chain. A successfully carried out task (that is, one that terminated normally and did not abort) is called a "task
67
instance" or "instance" for short. The JRodos Project Explorer Window shows all messages, input, and output information related to a project and the respective task(s) in form of an information tree, the Project Explorer tree. chapter): select the task node, right click on it and select the “Run” item. FDMT produces as results map fields (static and time-dependent) time series, histograms and tables.
3
2 5 4 1
Figure 96: LSMC+EMERSIM+DEPOM+FDMT model results visualization. 1) – data item in the Project explorer, 2) – grid map visualization, 3) – annotation and maximum value of the current field, 4) – current value, maximum value and cell number of the pixel selected with the information tool, 5) – colour legend.
68
Working with the JRodos Continuous Mode
Background information The JRodos Continuous Mode Can be started for every location covered by LSMC-NWP data Carries out periodic prognostic near range ADM calculations starting anew every N minutes (customizable), with a user-defined scenario - one release location, same source term, provider, background data Results are kept for the current calculation and a number of previous calculations (customizable); if the number of calculations gets bigger, for each new one the oldest one gets thrown away For starting, create a project with the "Continuous" model chain, initialize the scenario with RODOS-Lite, and submit Once kicked, it will operate continuously until you stop it Please note: For the customisation of the repetition time interval and the number of results that are to be kept please refer to the JRodos Customisation Guide, Chapter on "Mode and model control parameters". Remark: From version July 2014 Update 3 onwards there is another tool, the "Recurrent Job Launcher", that allows recurrent starts of calculations for other use cases, see the corresponding Chapter in this User Guide.
Checking if JRodos contains a "Continuous" model chain" The JRodos requires a model chain that contains the task "Continuous" which is currently not part of the standard JRodos installation. As a user, first check if your “New project” dialogue already contains a "Continuous" model chain. If not, use the JRodos Model Chain Editor to create a model chain consisting only of the "Continuous" task, and add it to the JRodos “New project” dialogue.
Starting the JRodos Continuous Mode Create a new project with the Continuous Mode model chain. Wait until the RODOS-Lite tab appears.
RODOS-Lite input theme [Site] Choose as event type =>Nuclear_power_plant_accident. Choose a country and an NPP. Or choose "Unspecified NPP" and specify the location.
RODOS-Lite input theme [Source term] Specify a "Start of release" time. Choose a source term of your liking, or input one yourself. Please note that you cannot select "Stack release".
RODOS-Lite input theme [Weather] The JRodos Continuous Mode works exclusively with LSMC-NWP data => you must choose Meteorological data from provider in the Meteorological data section. Tip If the Meteorological data from provider button appears blocked, and the selection slider below says No Data, there is no provider and/or no data for the site. Assign a provider and/or import data, or example with the help of JRodos Special Exercise - .LSMC-NWP data import and use. If you choose "User input", the Continuous Mode will refuse to start with a corresponding message in the JRodos Message window, but only after pressing "Submit" in the RODOS-Lite [Summary] tab.
RODOS-Lite input theme [Run] In the "Red Box" section, do not forget to select =>Exercise.
69
Select the calculation grid.
RODOS-Lite input theme [Summary] Click =>Submit. The Continuous Mode will start immediately if the time you specified in the RODOS-Lite [Source term] tab for the beginning of the release is "now" or in the past. If it is in the future, it will start when the clock reaches the specified starting time.
The Continuous Mode in operation The Project Explorer tree - it contains a result folder for the Current calculation, and for the number of previous calculations that was specified in the Continuous Mode Parameters. The example shown below was already running since about 18 hours, restarting every 60 minutes (with the "rounded to full hours" option set):
Figure 97: Continuous Mode Explorer Tree structure.
►For stopping the Continuous mode, right-click on the "Continuous" node in the project, and select stop.
70
Working with the JRodos Automatic Mode
Background information In the JRodos Automatic mode, diagnostic calculations are running continuously whenever measurements - also referred to as "real time data" data are available in the system: JRodos starts calculating with data from the first time interval containing the "Start of release" time specified in the initialization phase via RODOS-Lite. JRodos continues with following intervals as long as appropriate measurement data are available in the real time data base. When there are no data, JRodos waits for the arrival of new ones. Reports are generated regularly. Prognostic calculations are made periodically on top of the diagnostic calculations. The Automatic DIAGNOSIS model chain contains the models RMC3diag + RIMPUFFdiag or DIPCOTdiag + DOSEdiag. The Automatic PROGNOSIS model chain contains the models LSMC auto + EMERSIM + DEPOM + FDMT. The results of the Diagnosis and Prognosis are collected into two subfolders in the Project Explorer tree:
Figure 98: Diagnostic and Prognostic results subfolders.
For running the Automatic Mode, the presence of measured meteorological data in JRodos is mandatory. With respect to source term information, it is possible to apply measured data; however, this is not mandatory, and user specified source terms can be applied instead. Real time data are delivered to JRodos from so-called "providers". An example for such a provider is the German Nuclear Reactor Remote Surveillance System (KFÜ, Kernreaktor Fernüberwachung). JRodos works exclusively with measurement data contained in the JRodos real-time database (RTDB); all such data that are kept in file containers must be imported to the RTDB before they can be used. The steps that are required to prepare the use of measurement data in JRodos are described in the JRodos Customisation Guide, Chapter "Real time (measurement) data in JRodos")
71
Creating a project with the Automatic model chain
Figure 99: Mode selection dialogue.
In the JRodos Create new project dialogue, select Automate. Then, right-click on the Automatic mode task in the Project Explorer, and select “Start new automate”.
Figure 100: New Automata start.
The RODOS-Lite window will open.
Notes In RODOS-Lite tab [Source Term] you may select either “Stack Release” or “User Defined”.
In RODOS-Lite tab [Weather] you must select "Meteorological data from provider" for NWP data, and "On site meteorological data” for measurement data. To stop the Automatic task, right click on the running Automatic mode task and select Stop. After this, please wait until the current calculation step is finished.
Figure 101: Stopping Automate.
After calculation is stopped a project can be saved to a database or resumed. Stopped and saved project can be loaded from database and resumed calculation. To resume the calculation right click on Automatic mode task in Project Explorer and select “Resume stopped automate”.
Figure 102: Resuming Automate.
72
RODOS-Lite
RODOS-Lite tabbed panel LSMC, EMERSIM, FDMT, Emergency, EmergencyLite, and the Automatic mode, use the general RODOS- Lite input interface. Depending on the model chain and the JRodos user policy, the RODOS-Lite interface either opens automatically. Or it must be kicked manually by navigating to the respective task node, right- clicking on it, and then selecting “Init”. After a while the RODOS-Lite application starts and the input interface appear as a tab in the JRodos Main Window; the tab’s name being as follows: “RODOS-Lite::
Figure 103: RODOS-Lite tab content.
Selection of near range ADM and grid Three operational near range atmospheric dispersion models are included, RIMPUFF (puff model) and LASAT and DIPCOT (particle models). For changing the ADM, click (RODOS-Lite) Options → Dispersion model in the current RODOS-Lite tab (and not the "Options" in the JRodos Menu Bar), see Figure 104.
Selection of calculation grid One task in frame of the ENSI Switzerland contract with KIT consisted in the implementation of a new "ENSI grid" that was to be made available also for non-ENSI users. As a consequence, from JRodos July 2014 onwards there are three grid types "ENSI", "Default", and "OLD", see below. Previously generated RODOS-Lite xml files can still be used. The selection between grids is under "(RODOS-Lite) Options => Grid" in the current RODOS-Lite tab (not the "Options" in the JRodos Menu Bar), see Figure 105.
73
Figure 104: RODOS-Lite near-range LSMC model selection.
Figure 105: Grid switch in RODOS-Lite.
ENSI grid With this grid type, the user first selects the number of rings (between 1 and 5) and then chooses between 5 possible configurations for the combination of calculation radius and inner grid cell size. The total number of points in the calculation grid depends on the number of rings (1 ring: 36864; 2 rings: 64512; 3 rings: 92160; 4 rings: 119808, 5 rings: 147456). The larger the number of points, the larger the computation requirements with respect to computing time, memory, disk space. Select "ENSI grid" via RODOS-Lite "Options". In tab [Run], first select the number of rings, and then the radius of the calculation area, which is coupled to the size of the inner grid cells, see Figure 106.
74
(default)
Figure 106: RODOS-Lite ENSI grid selections.
Default grid For this grid type, select "Default grid" via RODOS-Lite "Options". This grid has 8056 grid points with square cells in five frames (i.e. the "ring number" is fixed and cannot be selected by the user). The side lengths of the cells double in size in each more outwardly frame; for the innermost frame, the user can select between different cell side lengths that correspond to different corresponding distances, see Figure 112.
Figure 107: RODOS-Lite NEW grid selection.
OLD grid The historical "OLD" grid is obsolete and will not be maintained much longer
RODOS-Lite tab [Site] In the site tab, choose the accident type and the location.
RODOS-Lite tab [Source Term] The source term tab serves for the specification of items related to the release of radioactive material into the atmosphere.
75
Up to five source terms can be considered. However, JRodos treats each one as an completely independent entity, which is: Suited for releases from independent nuclear facilities Suited for simultaneous releases from same reactor e.g. with different release heights when using "Bq per nuclide and time interval (F6)" input format (experts did necessary assessments and deliver the required activity released per nuclides) Not suited for simultaneous releases from same reactor when using input formats other that F6 (decomposition into nuclides is the problem) Manual input of co-ordinates via Pin Tool: Click on the "Pin tool". The Map tab opens, navigate to the desired location on the map tab and left-click. You come automatically back into RODOS-Lite tab [Source term] with the co-ordinates entered in the two input boxes for the longitude and the latitude. Please note that you can change the format for displaying the co-ordinates by selecting from the combo-box, see below.
Figure 108: RODOS-Lite "Pin tool" for entering manual co-ordinates in tab [Source term].
A note on using source terms for nuclear power plants and the role of the reactor inventory: When you want to use a source term from one of the JRodos source term libraries, or define a source term by hand on your own, please consider: For a release location not associated with a nuclear power plant, or a NPP showing the entry "UNDEFINED" in the "Inventory" field in the JRodos "Site" data base , the only possible source term input in JRodos is via input mode "(F6) Released activity without inventory reference" When using a source term of type "(F6) Released activity without inventory reference" from the JRodos source term libraries for some NPP of your own choice, one should be aware of the fact that the respective library source term was derived for a specific reactor with given characteristics such as reactor type, nominal thermal power, and days of operation. Applying it for a NPP with some other characteristics may require either scaling or some form of scientific argument or justification.
RODOS-Lite tab [Weather] The weather tab serves for the specification of meteorological items. The dialogue area is divided into the sections "Meteorological data" and "Prognosis time setup" and contains a button "Show Advanced Parameters". Features that are not available are not accessible and appear locked. Example: The presence of meteorological measurement data in the JRodos data base is a pre-condition for running Diagnostic calculations in the JRodos Automatic Mode. If such data are not there, button "Measurements" in tab [Weather] cannot be pressed.
ADM time steps and result averaging times for Lasat model
Lasat can calculate with 30 minutes or 60 minutes time steps; this makes sense for instance when NWP data are not available with a 10 minutes time resolution. The time step selection is made In RODOS-Lite tab [Weather], two options are offered: Specifying the time step in the same way as for Dipcot, and Rimpuff, or indirectly via two time sliders.
ADM time step selection for LASAT, Method 1 - as for the other ADM models
76
Under RODOS-Lite "Options", make sure that model Lasat is selected, and that "Show sliders" is not ticked for Lasat. In RODOS-Lite tab [Weather], select the ADM time step from the Combo-Box, see below. For Rimpuff and Dipcot, the result presentation will be with the same time step. For Lasat, the default setting seen with "Show sliders" is in operation.
Figure 109: RODOS-Lite selection of time step from combo-box option when using Lasat.
ADM time step selection for LASAT, Method 2 - via time sliders Under RODOS-Lite "Options", make sure that model Lasat is selected, and that "Show sliders" is ticked for Lasat:
Figure 110: RODOS-Lite selection of time step with time sliders option when using Lasat.
Then, use the two time sliders: the smallest possible result aggregation time defined by the slider settings will become the ADM calculation time step for the complete calculation period for Lasat. The other times (if any) are taken to be the time points for the result presentation, as in the March 2014 version. See the below examples.
(default): Result presentation every 10 minutes until 8 hours, then every 30 minutes until 16 hours, then every 60 minutes until the end of the calculation period; ADM calculation time step: 10 minutes.
Result presentation every 30 minutes until 12 hours, then every 60 minutes until the end of the calculation period; ADM calculation time step: 30 minutes. If you want result presentation also only every 30 minutes, drag the 60 minutes slider to the upper end.
Result presentation every 60 minutes, from the beginning to the end; ADM calculation time step: 60 minutes. 77
Meteorological data from provider
Button “Meteorological data from provider” is accessible only when there is at least one NWP data provider registered for the site under consideration in the JRodos database AND there are NWP data from the provider(s) available in JRodos Else, the button appears locked.
For registering a provider and setting-up the NWP data supply, please refer to the JRodos Customisation Guide, chapter on "Numerical weather prediction data for LSMC and MATCH". For the following explanations, please take a look at Figure 111.
Figure 111: RODOS-Lite [Weather] tab, sections "Numerical data" and "Prognosis time setup".
In Figure 111, the Button “Meteorological data from provider” is selected. To the right of label "Provider" there is an expandable list showing the provider(s) available for the site under consideration. In Figure 111, provider "nomadgre2" is selected. To the right of label "UTC" there is an expandable list showing the analysis times of all NWP data sets available from the selected provider. Below is a switch "Show adaptable data": When there is NWP data with analysis date/time matching the "Start of prognosis" in section "Prognosis time set-up" and these data shall be used, then the switch must be not ticked By default, the switch is not ticked when there are matching data In all other cases, the switch has to be ticked It is then the responsibility of the user to select a NWP data set that covers the starting time (in UTC) of the prognosis; the date will become adapted to the start date of the prognosis calculation
78
In the example in Figure 111, the start date of the prognostic calculation is in 2017. For the selected nomadgre2 provider only data from 2013 were implemented in JRodos => switch "Show adaptable data" is ticked. The data sets apply for analysis times 00:00, 06:00, 12:00, 18:00 UTC and cover a 6 hour time interval each. The prognosis start date is 16:05 UTC => an appropriate analysis time for the NWP data is 12:00 UTC; the date will be adapted to the start date of the prognosis calculation.
Prognosis data sets from a given provider may cover overlapping time periods. Section "Advanced parameters" offers a choice between two possibilities for the way to treat such overlaps: "Stay with the selected set": Start with the set selected in the combo box and stay with it as long as possible "Switch to newer set":. Switch to a newer set as soon as possible Example Provider data with analysis time update period 6 hours, prognosis duration 48 hours in time steps of 1 hour. Start of calculation at 1 May 2011, 10:24 UTC; prognosis duration: 24 hour; analysis time stamp of LSMC- NWP set selected by user: 1 May 2011, 06:00 The following prognosis data will be used (assuming that all sets for the mentioned analyses times are available in the database) Stay with selected set: 1 May 06:00 (04, 05, .., 28 hours of prognosis). If all data from the selected set are used, then the newest set is selected as the source for the NWP data; Switch to the newer set: 1 May 06:00 (04, 05), 1 May 12:00 (00, 01, .., 05), 1 May 18:00 (00, 01, …, 05), 2 May 00:00 (00, 01, …, 05), 2 May 00:06 (00, 01, …, 04);
Hand input of weather data: Wind direction selection tool
RODOS-Lite tab [Weather] contains a wind direction selection tool in the "User input [Create/Edit] branch, see Figure 112.
It is recommended to zoom first to a suitable level and then use the Zoom Lock feature before applying the wind direction selection tool. Click on the magic rod in the input field for the wind direction. A map tab opens where you can indicate the direction into which the wind blows by "drag-and-drop" drawing an arrow. The corresponding meteorological wind direction appears in the "Wind direction" input field.
(2)
Figure 112: RODOS-Lite [Weather] tab, wind direction selection tool for "hand input". 79
RODOS-Lite tab [Countermeasures] - not visible for EmergencyLite This tab serves for the specification of intervention levels and timing for early countermeasure calculations, EmerSim.
RODOS-Lite tab [Food chain] - not visible for EmergencyLite This tab serves for the selection of results to be calculated with the Terrestrial Food Chain and Dose model, FDMT
RODOS-Lite tab [Run] All options can be changed arbitrarily.
Viewing the RODOS-Lite input summary and saving the RODOS-Lite xml in JRodos The RODOS-Lite input summary can be inspected by clicking Input → UI-Input → Input summary in the Project Explorer, see Figure 113. The RODOS-Lite xml-file that contains all the input can be save by clicking Input → UI-Input → Rodos Light in the Project Explorer, and then clicking on the "Save to File" icon for the tab that shows the xml, see Figure 114.
Figure 113: Viewing the RODOS-Lite Input Summary in JRodos.
Figure 114: Saving the RODOS-Lite input xml to file in JRodos.
80
Working with the ERMIN model
For dealing with the ERMIN model in JRodos, please see document “Working with ERMIN.doc” in the JRodos Client documents folder.
Working with the IAMM model
For dealing with the IAMM model in JRodos, please see document “Working with IAMM.doc” in the JRodos Client documents folder.
Working with the HDM models
For dealing with the HDM models in JRodos, please see document “Working with HDM.doc” in the JRodos Client documents folder.
81
Working with the MATCH model
Overview For far range atmospheric dispersion and deposition calculations, the JRodos standard package contains a version of model MATCH, the multi-scale Atmospheric Transport and Chemistry developed by the Swedish Meteorological and Hydrological Institute (SHMI)10. MATCH is an Eulerian grid model solving the general "advection – diffusion differential equation" for the transport of matter in turbulent fluids. The spatial resolution corresponds to the grid cell size of the numerical weather prediction (NWP) data that are required as input. By design, MATCH can work with meteorological HIRLAM data from the Danish Meteorological Institute (DMI), or from the European Centre for Medium- Range Weather Forecasts (ECMWF) models in GRIB format (both not free). NWP data that are usable for calculations with the JRodos LSMC models are not automatically also usable for MATCH because of different data requirements. JRodos February 2017 contains a command line tool for converting LSMC suitable GRIB1 or GRIB2 NWP data for use also in MATCH. In JRodos, one can either run stand-alone MATCH or LSMC-MATCH with coupling to the results of a near- range dispersion calculation. In JRodos February 2017u2, LSMC-MATCH can be applied with the LSMC models Rimpuff and LASAT. Before running an LSMC for the use in LSMC-MATCH, the value for the parameter “DWDUse” needs to be set to ”true”. This can be done in “Model Parameters – LSMC…”. The results available from MATCH comprise Concentration- and deposition fields, nuclide specific (instantaneous and time-integrated) Doses and dose rates from the radioactive cloud, nuclide specific Meteorological fields (mixing height, heat flux, humidity, precipitation, temperature)
Preconditions for running MATCH in JRodos For more details about the topics in this Chapter, please refer to the JRodos Customization Guide, Chapter on "MATCH NWP: data formats, provider definition, LSMC to MATCH NWP data converters".
Provider definition and data supply
MATCH requires as input numerical weather prediction data fulfilling some defined minimum requirements from some meteorological service or "provider". Before one can successfully start a MATCH in JRodos: At least one MATCH data provider has to be registered Only users with "admin" user privilege can define such provider. MATCH-suitable data from the MATCH provider(s) must be available in folder
Using the GRIB LSMC to MATCH data converter
Users who do not have access to MATCH suitable NWP data can use the GRIB LSMC to MATCH data converter for generating such data from openly available large scale GRIB NWP data, for example the
10 http://www.smhi.se/en/research/research-departments/air-quality/match-transport-and-chemistry-model-1.6831 (in English) 82
NOMADS11 data that are supported in JRodos12. The converter is a command line tool written as a Java console application. It works on Windows/Linux/Mac 32/64 bit OS and can be used in Scheduler / Cron for creating an automatic conversion. The necessary tool and equipment for the conversion is contained in folder
Figure 115: Folder
The user must specify the folder containing the data to be converted, and the folder that shall hold the converted data. This can be achieved in two ways (read also the "README" file): 1. By entering the specifications while starting the command line tool 2. By supplying the specifications in file "parameters.list"; then, the tool can be started simply by double- clicking on the script "run.sh (Linux)| .cmd (Windows)" in folder
Figure 116: Example for an I/O folder specification in file "parameters.list".
The converted data have then to be placed into a folder
11 US National Oceanic and Atmospheric Administration NOAA operates four different NOMADS Servers that host NCEP Model Products. National Centers for Environmental Prediction. NCEP www.ncep.noaa.gov/ - The U.S. National Weather Service office that provides worldwide forecast guidance products 12 See also Chapter "Applying JRodos outside the range of the EU installation" in this User Guide 83
Figure 117: Displaying the MATCH data folder name via the "NWP Provider Options" menu
Available data for demonstrating MATCH in JRodos
The JRodos exchange server "resy5.iket.kit.edu", username "jrodos" 13 contains in directory
Carrying out a MATCH project To start with, open a new project and select model MATCH, see Figure 118:
Figure 118: Creating a MATCH project
After clicking [OK], the MATCH user interface opens. It consists of three tabs: General, Source term, and Output; the corresponding windows are shown further below. Each of the tab-windows contains a button [Init]. Note that after pressing the [INIT] button in any of the tabs, the input of all tabs gets checked. If not correct, a message window with a list of all possible errors appears, and before proceeding, the error(s) must be corrected. If correct, on simple user policy, the project will start automatically. On advanced user policy, right click on the MATCH task in the project tree and select "Run". Viewing of MATCH results is done via browsing to the items in the Project tree and clicking on them.
13 ask the KIT JRodos Team for the password 14 HIRLAM: High Resolution Limited Area Model from the international HIRLAM programme 15 US National Oceanic and Atmospheric Administration NOAA operates four different NOMADS Servers that host NCEP Model Products. National Centers for Environmental Prediction. NCEP www.ncep.noaa.gov/ - The U.S. National Weather Service office that provides worldwide forecast guidance products 84
MATCH tab “General”
Figure 119 shows tab [General]. The example is filled out for a MATCH stand-alone run using the demonstration data from the match-nomads provider described in Chapter "Available data for demonstrating MATCH in JRodos". Select [MATCH] for running stand alone. Select [LSMC-MATCH] for running MATCH coupled to the results of a near range LSMC calculation. When selecting LSMC-MATCH, a dialogue opens for specifying a project that contains a correctly terminated and loaded LSMC calculation. When the linking dialogue shows no such project, you must first load an existing one or create and carry out a new one.
Figure 119: MATCH tab "General" (with example filling)
Provider selection If the provider combo-box is empty, a provider must be registered and the data from the provider must be supplied, see Chapter "Provider definition and data supply" in this User Guide. Force end of calculation, UTC For “calculate until end of available data” specify “-1” (default). In the example shown in the Figure, the setting is so that the calculation shall stop 24 hours after the onset of the one release specified in tab [Source term]. Cut out domain The cut domain is a square with a side length (in km) defined by the user (Default: 64 km). Cutting out domains around the release point will increase the calculation speed. Reconstruct hybrid level coefficients "Do not" is default => use this setting for the dmi and nomads-dmi provider. Make use of the option only if you know that this is required, for example, for the "knmi" provider. Otherwise, MATCH can produce wrong results or crashes (see JRodos Customisation Guide, chapter on "Numerical weather prediction data for LSMC and MATCH"). Nuclide selection Select up to 10 nuclides that shall be considered in the calculation, from the following available ones: Kr-88, Xe-133, Xe-135; I-131, I-132, I-133, I-135; Rb-88, Sr-89, Sr-90, Zr-95, Te-132, Ba-140, Cs- 134, Cs-137
85
MATCH tab “Sourceterm” (MATCH stand-alone only)
When running MATCH, clicking on [Sourceterm] will open tab [Sourceterm]. When running LSMC-MATCH, the input via this tab is blocked. Figure 120 shows tab [Sourceterm]. The example is filled out for a MATCH stand-alone calculation for a single release starting on September 10, 2013 at 3:00 UTC and lasting for three hours.
Figure 120: MATCH tab "Sourceterm" (with example filling)
One can put in between 1 and 4 source terms; select the number in the little number box on top of the window. For each source term, the following specifications are needed Co-ordinates of the release point You specify the co-ordinates of the release point with the pin tool, or by selecting a site from the combo box, or by entering the values by hand. In the end, only the values from the Latitude and Longitude text field are used in the calculation. Using the 'pin icon': Single-click on the icon brings you to the JRodos Map tab. One click in the JRodos Map tab brings you back to the Source term tab and the co-ordinate at which you made the click appears in the Latitude and Longitude boxes for the release point. Tip: You can repeat this procedure as often as you like until you are satisfied with the result, in between zooming etc. in the map for optimal visibility. Release height Give the release height in metres. Volume flux If you have no idea what to do with the volume flux, specify -1 for “take default”. Start time and end time of the release (UTC) Tip: Make sure that the times are within the time span covered by the available MATCH data !!! Emission rate of radioactivity for each of nuclide previously selected in tab General Double-click in a nuclide line under “Emission” to enable the data input.
MATCH tab “Output” Click on [Output] to open the tab for the selection of the results that shall be calculated and displayed, seeFigure 121. The default setting is “Select all” which is fine for most purposes.
86
Figure 121: MATCH tab "Output" (with default selection)
Example MATCH projects Worked-out examples for MATCH projects with use of the data described in Chapter "Available data for demonstrating MATCH in JRodos" you can find on the JRodos exchange server "resy5.iket.kit.edu", username "jrodos"16, directory
16 ask the KIT JRodos Team for the password 87
Working with the FDMF model
The Food Chain Module Forest (FDMF) calculates the activity concentration in raw wild food (berries, game meat, mushrooms) and the ingestion doses from the intake of these products by different population groups. It calculates the external dose-rate in forests and the external doses in different population groups that spend some time in forests, either for work or recreation. In addition, it calculates the collective dose from these pathways. Furthermore, FDMF calculates the activity concentration in forestry products, i.e. logs, pellets, split firewood, and briquettes, and it assesses the activity concentration in ash and the external dose from ash used as garden fertilizer. In the distribution package FDMF model is not included to any predefined model chain, so first create model chains with FDMF. FDMF model should be connected to successfully finished LSMC (Emergency) calculation results. The FDMF user interface contains 1 tab with three sections on it. Nuclides. This is the list of nuclides that is received from ADM. Some nuclides are excluded from FDMF calculations. These are noble gases, nuclides with half-lives shorter than 1 day. A user can exclude further nuclides. Population groups. These are the population groups for which radiation doses are calculated. A user can activate/deactivate arbitrary. Parameter set. The model calculation depends on dozens of parameters. These are grouped into forest, mushroom, berry, and game related parameter sets. The database may contain several alternative parameter sets for each group. You can choose from the database the actual model parameterization in each radio-ecological region by specifying 'Forest type', 'Mushroom type', 'Berry type', and 'Game type'. Data are stored in tables 'forest_id.dat', 'mush_id.dat', 'berry_id.dat', and 'game_id.dat' in the database directory RodosHome\roextern\data\fdmf\dbase. Radio-ecological regions are retrieved during the initialization of FDMF user interface.
Figure 122: FDMF user interface.
If some data is entered in the wrong way then after pressing Init button a message with all error appears. After fixing all wrong input values it is possible to run the model. To finish working with user interface a user should press Init button. If the calculation will not start according to user policy, right click on FDMF task in the project tree and select Run button. To see the result, browse to the item in Project tree and click on it.
88
Working with the LCMF model
The Late Countermeasures Module Forest (LCMF) simulates different countermeasures and provides results in form of tables, maps and time series. LCMF allows a user to compare different countermeasure options, also different parameters for one countermeasure options. In the distribution package LCMF model is not included to any predefined model chain, so first create model chain with LCMF. LCMF model should be connected to FDMF. LCMF stores all result from the different model runs for comparison. If a user recalculates FDMF, then no more LCMF run is possible to be done. A user should either clear all LCMF results, or create a new project with LCMF model. The LCMF user interface contains 2 tabs: Countermeasure tab. This tab contains the list of all available countermeasures. A user should either select countermeasure and press Next>> button to go to the Parameters tab, or press Clear calculated results button, to clear all already calculated results. Clearing results allow a user to connect LCMF to another run of FDMF, or compare results in the different way with the same FDMF run. Parameters tab. This tab allows a user to specify parameters for the selected countermeasure. ID field, which is not editable, allows a user identify calculated results for this particular input parameters in the countermeasure folder in Project explorer. Short information about countermeasure is shown at the bottom of the tab. When all data is specified a user should press Init button. Pressing < Figure 123: LCMF user interface, countermeasure tab. 89 Figure 124: LCMF user interface. Parameters tab for countermeasure "Access restriction". If some data is entered in the wrong way then pressing Next>> or Init button will have no effect. After fixing all wrong input values it is possible to run the model. If the calculation will not start after pressing Init button according to user policy, right click on LCMF task in the project tree and select "Run". To see the result, browse to the item in Project tree and click on it. To initialize model again, please, right click on LCMF task in the project tree and select "Init". 90 Working with the DEMM model The task of the deposition monitoring module (DEMM) is to update the predicted total (dry + wet) deposition on the ground and on all kinds of plant surfaces. The predicted deposition data is calculated with a deposition model using results from atmospheric dispersion modelling. The update is based on measurements of net gamma dose rates after the deposition process has ended. The endpoints of DEMM are essentially the total (i.e. dry + wet) deposition of the different radionuclides to a variety of crops. This data is input to the Food Monitoring Module FOMM. Moreover, DEMM provides information about uncertainty of this data in form of a covariance matrix; this information is required from FOMM. Measured values file for Food Monitoring Module FOMM is updated in DEMM. This file has to be stored in the file RodosHome\roextern\data\fomm\m.dat. In the distribution package DEMM model is not included to any predefined model chain, so first create model chains with DEMM. DEMM model should be connected to successfully finished LSMC. DEMM does not have a user interface. Model configuration can be done in the RodosHome\roextern\data\demm\demm.config file. As DEMM depends on the LSMC (Emergency) results on the task initialization the model linking dialogue starts. Select LSMC model on the base of which you want to calculate DEMM model and press OK. If the calculation will not start according to user policy, right click on FDMF task in the project tree and select "Run". To see the result, browse to the item in Project tree and click on it. 91 Working with the FOMM model The Food Monitoring Module (FOMM) calculates activity concentrations of feedstuffs and foodstuffs (in Bq/kg). For this, FOMM uses model predictions as well as measured values of the activity concentration of feedstuffs and foodstuffs. The results of the data assimilation are associated with less uncertainty than the uncertainties of the model predictions and measured values. Measured values have to be stored in file RodosHome\roextern\data\fomm\m.dat. In the distribution package FOMM model is not included to any predefined model chain, so first create model chains with FOMM. FOMM model should be connected to successfully finished DEMM calculation results. FOMM user interface contains one tab with four sections on it. Feedstuff activity. Allows selection of feedstuffs, whose activity concentration will be displayed graphically. Foodstuff activity. Allows selection of foodstuffs, whose activity concentration will be displayed graphically. Data assimilation settings. Here it can be chosen, whether deposited activities and activity concentrations in air are part of the data assimilation. If no, model parameters only are used for data assimilation. Various selections. The listed feedstuffs and foodstuffs are processed products. By choosing 'raw products' in the fourth section the activity concentration of the corresponding raw products will be displayed graphically. Figure 125: FOMM user interface. If some data is entered in the wrong way then after pressing Init button a message with all error appears. After fixing all wrong input values it is possible to run the model. To finish working with user interface a user should press Init button. If the calculation will not start according to user policy, right click on FOMM task in the project tree and select Run button. The total number of product (feedstuff and foodstuff) selections is limited, but the exact number depends on data from DEMM model and can be obtained only after running the model in the first time. If a user selects too many products it will see the following message in the Message window (numbers may be different): Figure 126: Error message if too many products selected. To see the result, browse to the item in Project tree and click on it. 92 Working with the AgriCP model In the current standard JRodos package, model AgriCP model is not assigned to any predefined model chain, so please first create model chains with AgriCP. When running AgriCP model should be connected to successfully finished DEPOM calculation results. The AgriCP user interface contains two tabs, the Countermeasure tab and the Results tab. Figure 127: AgriCP user interface, countermeasure tab. Countermeasure tab (Figure 127): Allows creating a countermeasure strategy, zones for each countermeasure strategy, and sets of countermeasures for each zone. A user can add/delete a countermeasure strategy using corresponding buttons in the “Countermeasure strategies” section. For each countermeasure except “No countermeasure” a user can add zones. To create a zone, select strategy, then press the “Add” button of the “CM Strategy” section, enter a name and select a colour of your choice for it in order to make the zone distinguishable. To edit a deposition zone name and colour double-click on it in the list. To delete a zone, select the zone in the list and press the “Delete” button of the “CM Strategy” section. To assign computational cells to the zone, select the zone in the list and press the “Draw” button of the “CM Strategy” section: You will see the RODOS computational grid. Create a polygon, clicking in the places where the apices of the polygon should be located. Finally enclose the polygon, by clicking on the apex created earlier. You will see the computational grid cells, enclosed by the polygon, painted to the colour selected before. Use the button on the toolbar to delete cells from the selection. To start selecting zones again, use button. A user can change the zone, to which new selected cells shall be assigned, by changing the combo box value. To go back to the Countermeasures panel, press the button on the AgriCP toolbar. 93 Figure 128: Selected area on calculation map, assigned to zone “Zone”. At least one countermeasure should be set for each zone. To add/delete a countermeasure from a zone, select the zone in the list and use the “Add”/”Delete” buttons in the “Countermeasures for countermeasure zone” section. A number of parameters can be entered for each countermeasure technique. Select the countermeasure in the list and then change values in the “Parameters for countermeasure” section. Use the “Additional data>>” button for more parameters (this button is not available for all countermeasures). Each countermeasure can be applied for one foodstuff only (or for “all products” if such option is allowed). If you want to select more than one foodstuff, a new countermeasure for each additional foodstuff should be added. NOTE: Currently, only one strategy except “No countermeasures” and only one zone allowed. These restrictions will be removed soon. If some data is entered in the wrong way then after pressing Next>> button a message with all error appears. After fixing all wrong input values it is possible to make the result selection. Results tab. Allows selecting results which will be calculated by AgriCP. It is possible to choose the graphical output type (maps, time plots, collective doses, frequency distribution), the cell number for which time plots shall be generated, feed-/foodstuffs, nuclides for activity concentrations, age group, organs, times etc for dose calculations. To check/uncheck a leaf node in the tree, single click on it. To check/uncheck a folder node in the tree double click on it. Opening/closing a folder node can be made by clicking on “+”/”-” button left to the node of interest. Toolbar button “Select defaults” does a default selection in the tree and graphical output types. Toolbar button “Select defaults for node” makes a default selection for the selected tree node. Toolbar button “Unselect node” un-checks a selected tree node. “Default” button in the “Graphical output types” selects default graphical output types leaving all other selection untouched. “Screening mode” adds 4 additional results: maps for activity concentration in cow milk for iodine, cesium, strontium and alpha isotope groups. 94 Figure 129: AgriCP user interface. Results tab. During selection the estimated number of results is shown in the left bottom corner. If this number exceeds maximum allowed results number (200), this field becomes red, indicating that some nodes or graphical output types must be unselected. You can return to Countermeasure tab using << Previous button. If some data is entered in the wrong way then after pressing Init button a message with all error appears. After fixing all wrong input values it is possible to run the model. To finish working with the AgriCP user interface press the Init button. If the calculation will not start - this depends on the active user policy - right click on FOMM task in the project tree and select Run button. To see a result, browse to the item in Project tree and click on it. 95 Working with the EmerSimCH model The EmerSimCH model is a modified version of the EmerSim early countermeasure model. It allows for the geometric specification of areas for early countermeasures “sheltering”, evacuation” and iodine tablets”. In addition to this, the EmerSim interval is increased from 24h to 48h. For carrying out a calculation with the EmerSimCH model, you must first have a project containing a successfully terminated calculation with one of the JRodos atmospheric dispersion and deposition models (ADM) of the near range local scale model chain (LSMC), the results of which is used as input for the EmersimCH project. The ADM-results to be used can either be in a separate project or in the same EmersimCH project, if it was set up as a model chain. The EmerSimCH tab allows for the geographical definition of areas and the allocation of countermeasures and countermeasure duration to those areas (Figure 130). Figure 130: JRodos tabbed panel for the EmerSimCH model on start-up In the graphical definition of geometrical areas (aka zones) section of the Graphical User Interface, the user can draw such zones on the map from scratch and save them as Shape-Files (extension .shp) for re-use. Alternatively, existing Shape files that were created with JRodos or some other software that produces JRodos suitable ESRI Shape files can be loaded and then modified. With [Add] you can add a new geometrical countermeasure zone. Click on [Add]. In the opening window, give a name ("demozone" in the example) and click [OK]. The [Choose Colour Window] appears; select a colour and click [OK] (Figure 130). The name of the new zone appears in the window of the ["Graphical definition of geometrical areas]" tab section. Figure 131: Adding a new geometrical area Geographical zones can be managed by using the “Delete”, “Save” and “Load buttons” in the upper part of the window. To define the shape and location of a zone, select the zone of interest and press the “Draw” 96 button. The dialog window becomes hidden and the map with all already defined areas is displayed together with an [EmerSimCH Geometrical Area Editor] Toolbar (Figure 132). Figure 132: Map toolbar buttons from left to right: [Select zone], [Remove zone], [Reshape zone] and [Back to GUI]. To draw a zone in the map, go to the map, zoom to the area of interest, select a zone for drawing in the combo box, and press the ["Select zone]" map tool button (with the ["Draw]" map toolbar button, the zone and the map toolbar button is selected automatically). With the mouse, create a zone on the map. For this a polygon has to be created by clicking in the map locations, where the apices of the polygon should be. Finally enclose the polygon, by clicking on the first apex created. Zones may lie on top of each other. To delete a zone from the map, go to the map and select the [Remove zone] map toolbar button. Move the mouse pointer into the desired zone and make a single click. To reshape a zone on the map, go to the map and select the [Reshape zone] map toolbar button. Move the mouse to one apex of desired zone, then drag it with the mouse, move to some position you like and drop it there. Please note, that the intersection of a zone with itself is not allowed. To go back to the [Zone Designer] dialog, press the "[Back to GUI]" map toolbar button. Figure 133: Map toolbar buttons in action. From left to right: [Select zone], [Remove zone], [Reshape zone]. In the lower part of the EmerSimCh tab, you can add a new countermeasure definition for a given geometrical area with [Add]. Click on [Add] in the bottom part of the GUI tab. A blank coloured line appears for the input. Clicking in the empty ["Data]" field opens an expandable list from which you select an available geometrical area from the available ones for which you want to define the countermeasure and the timing. Clicking in the empty ["Countermeasure]" field opens an expandable list from which you select from the available ones the available countermeasure that shall be applied in the area. Clicking in the empty ["Start [UTC]]" field and the ["Stop [UTC]]" field allows the specification of the timing for the selected action. Please note the current restrictions: • Currently, the timing has to be specified manually as dd.mm.yyyy ij.kl, for example 15.05.2017 10:00 • The ["Start [UTC]]" time must always be given AND it must lie within the EmerSim Interval. • The ["Stop [UTC]]" can may be but need not be specified. If the field is empty, duration until the end of the EmerSim Interval is assumed. If the specified Stop time exceeds the EmerSim Interval, it is shortened to the EmerSim Interval. You can add several countermeasure definitions for a geometrical area by repeating this operations. By clicking on an existing definition, the line becomes active and can be modified. Countermeasure definitions 97 can also be deleted, saved and loaded. Pressing the “Submit” button will start the calculation. The Output folder in the Result Tree for the EmerSimCH model contains all components also produced by a calculation with the standard EmerSim model, and, in addition, a specific folder "Input countermeasures" (Figure 134). Figure 134: Result example from folder "Input countermeasures" 98 Working with the Wildfire model The Wildfire model is a functionality implemented into the LSMC model of JRODOS to assess the redistribution of radionuclides by wildfires in contaminated areas. The modelling of resuspension and atmospheric transport of radionuclides by wildfires in the CEZ in JRodos is analogous to the one used in the work of Evangeliou et al.. Emissions are fed to the Lagrangian particle transport model LASAT, which simulates the transport and deposition of the fire-redistributed radionuclides. When selecting the Wildfire functionality in the LSMC Site Tab, LASAT is automatically used as the dispersion model. Other dispersion models cannot be used for the calculation. The centre of the calculation grid for the ADM is also defined in the Site Tab under “Location”. That centre should be close to the location of the wildfire. Figure 135: Site tab of the LSMC model. Defining a wildfire event requires selection of "Wildfire" in the "Other accident" radio button group. Evangeliou et. al. assessed the impact of two major fires in the Chernobyl Exclusion Zone (ChEZ) which happened in April and August 2015. These wildfires last for 7 days in spring 2015 and for 4 days in August 2015. Therefore the JRodos wildfire model allows user specification of wildfire areas for different release- time periods. The amount of emission of each release-time period will be dispensed on the ADM time steps using a constant emission rate for each nuclide. Four classes of wildfire are used: weak, modest, strong and very strong. In addition to this, two different resuspension models will be implemented: 1. simple model used in Evangeliou et. al. for the emission rates • 20% of labile radionuclides will be redistributed in the atmosphere after a fire, no matter whether they are deposited in the soil or biomass/vegetation. • 10% of the refractory radionuclides will be redistributed in the atmosphere. 99 2. more complex model based on burning experiments by Amiro et al, 1996 The emission strength of the radionuclides depends on the fire class reflecting the different fire temperatures. Figure 136: Sit tab of the LSMC model. Defining a wildfire event requires selection of "Wildfire" in the "Other accident" radio button group. if the event happens in an area where maps of nuclide depositions are available, JRodos is capable to generate the actual nuclide release from area and fire intensity. In this case only the area definition and fire intensity parameters are required. If this source term type is selected it is up to the operator to assure that the required nuclide deposition maps are available and registered in JRodos. if the event happens in an area without maps of nuclide depositions no automatic generation of the actual nuclide release is possible. In this case a manual definition of the nuclide deposition in [Bq/m²] is required. With this information in addition to area and fire intensity JRodos can generate the actual nuclide release. Figure 136 shows an example input mask for a wildfire source term with manual definition of nuclide deposition. Additionally to the common interval parameters each interval allows the definition of the area in connection with the JRodos GIS and the selection of a fire intensity category. The common nuclide values based on [Bq/m²] in contrast to the definition of other source terms that are based on [Bq]. Area definition can be managed by three methods executed by an according button. These buttons are: New creation and editing of a wildfire area: clicking onto the button opens the JRodos GIS where one can define the area as a polygon on the map. 100 Importing a wildfire area: clicking onto the button opens a file open dialog. Selecting a shapefile will import the contained polygon as area. Exporting a wildfire area: clicking onto the button opens a file save dialog. The area will be exported as a polygon into a shapefile. If a new wildfire area is created, a map view with a tool bar for drawing, deleting and modifying polygons is opened (Figure 137). To draw a polygon, use the “Select Zone” button and click on the place in the map view where the apices of the polygon should be located. To close a polygon, click on the first apex. To delete a polygon first click the “Remove Zone” button and then the polygon in the map view. Polygons can be modified by pressing the “Reshape Zone” button, clicking and holding the left mouse button on a polygon apex in the map view and pulling it to a new location. The area of the polygon is stated inside the polygon in hectare. The map view is originally centered on the coordinates selected in the “Site” window (Figure 135). To aid the drawing of polygons or to improve the presentation of data, street map or satellite data layers may be added to the map. This view can be exited by pressing the exit button. The areas have to be defined for every interval, representing growing or shrinking wildfire areas over time. The “Fire intensity” of “0.12 (weak)”, “1.2 (moderate)”, “6 (strong)” and “36 (very strong)” can be selected for every interval in the corresponding dropdown menus. This fire intensity is the same for all areas represented by polygons in the corresponding interval. Radionuclide activities can be entered manually for every interval, if contamination maps are not used. Figure 137: Window for the definition of wildfire areas. The tabs after the source term tab are the same as in previous LSMC applications and were described in the RODOS-Lite chapter. N. Evangeliou, S. Zibtsev, V. Myroniuk, M. Zhurba, T. Hamburger, A. Stohl, Y. Balkanski, R. Paugam, T.A. Mousseau, A. P. Møller, S.I. Kireev, Resuspension and atmospheric transport of radionuclides due to wildfires near the Chernobyl Nuclear Power Plant in 2015: An impact assessment, Scientific Reports, 2016, 6, 1 101 B. D. Amiro, S. C. Sheppard, F. L. Johnston, W. G. Evenden, D. R. Harris, Burning radionuclide question: what happens to iodine, cesium and chlorine in biomass fires?, The Science of the Total Environment, vol. 187, 1996 Working with the Tornado model The Tornado model can be used to estimate the radiological impact in the case of remobilization of radionuclides by a tornado. To create a new Tornado model, the option “Tornado” in the “Other Accident” group in the “Site” tab needs to be selected (Figure 135). The definition of the source term is similar to the Wildfire model, with either a manually defined source term, or source term maps. In addition to the strength of the tornado, its point of origin can be defined (Figure 138). Figure 138: The input mask for the tornado source term with manual definition of nuclide deposition. Figure 138 shows an example of a tornado source term with manual definition of nuclide deposition. An important difference between wildfire and tornado events is the guaranteed limited duration of the tornado. Therefore the tornado source term only contains a single interval of fixed 10 minutes duration. Additionally the tornado is not described by its area but its pathway, which in turn is derived from origin, wind direction and wind speed. The actual area contributing to the nuclide release is automatically determined by JRodos according to the path and the tornado class. The tornado class implies the load factor, i.e. the fraction of deposited nuclides picked up by the tornado. The load factor may be changed by expert users but only after explicitly enabling this change. 102 Applying JRodos outside the range of the EU installation Summary For applying JRodos for any location on Earth, a "World Wide" package is contained with the following data and tools: A set of globally applicable geo-referenced calculation ("engine") data - elevation, land use, soil data, population density, and production; for the data origin, see "References for reactor and engine data entries in the JRodos World Wide package". Text files containing information about all reactors and selected facilities of the nuclear fuel cycle in the world with thermal power exceeding 1 MW, and a tool that allows dumping/restoring the complete JRodos Site DB to/from text files; for the data origin, see "References for reactor and engine data entries in the JRodos World Wide package". A tool for downloading globally applicable meteorological weather prediction (NWP) data in Grib2 and Grib1 format from the American NOMAD Server17 for a given time span or for one given date. Document "WorkingWith_JRodosWorldWide" in the JRodos Document folder contains general information and tips for making JRodos fit for calculations outside the range covered by the default EU installation. Document "WorkingWith_NOMADS_Downloader+Data" in the JRodos Document folder explains the use of the NOMADS downloader, the resulting data files, and how to apply them in JRodos.References for reactor and engine data entries in the JRodos World Wide package Reactor details (coordinates, type etc.) https://en.wikipedia.org/wiki/List_of_nuclear_power_stations http://world-nuclear.org/NuclearDatabase/rdResults.aspx?id=27569 http://world-nuclear.org/NuclearDatabase/popMapSearch.aspx?width=970&height=540 http://www.iaea.org/PRIS/home.aspx Elevation - GLOBE data http://www.ngdc.noaa.gov/mgg/topo/globe.html Land use - GlobCover 2009 set reclassified to RODOS land use classes http://due.esrin.esa.int/page_globcover.php (new link) Soil maps - reclassifying the USGS Global Soils Regions 60 arc-sec map to the RODOS soil classes ftp://ftp-fc.sc.egov.usda.gov/NHQ/pub/outgoing/soils/global_soil_suborders_data.zip http://soils.usda.gov/use/worldsoils/mapindex/order.html Links no longer available; no replacement found (June 2017) Population density - Global population density estimates, projected 2015 (FGGD) http://www.fao.org/geonetwork/srv/en/metadata.show?id=14053 Table 1: References for reactor and engine data entries in the JRodos WorldWide package 17 US National Oceanic and Atmospheric Administration NOAA operates four different NOMADS Servers that host NCEP Model Products. National Centers for Environmental Prediction. NCEP www.ncep.noaa.gov/ - The U.S. National Weather Service office that provides worldwide forecast guidance products. 103 Working with the multi-user feature Some organisations deploy JRodos in such a way that several operating system (OS) users can connect in parallel to one central JRodos Client PC. The design for such usage is to have one JRodos Client folder on this PC, so different OS users can launch an individual instance of the JRodos Client application in their OS session. For this the JRodos Client folder is recommended to be set into "read only" mode. All read-write files and folders involved in the Client operation are automatically located in The multi-user feature should be activated or deactivated only by the system administrator. To activate the multi-user feature, create an empty folder with the name "multiuser" in the 104 Automatic start of calculations via incoming xml files JRodos can be used to carry out model chain calculations in a batch-job fashion by placing xml-files that contain the input specifications in a special directory which is scanned periodically by the system; when new files are detected, respective calculations are started. Until JRodos version July 2014 Update 3, this was only possible for the Emergency/EmergencyLight and Automatic model chains and the models contained therein, by using the xml-files generated by the RODOS- Lite user interface; this feature is described in Chapter "RODOS-Lite models". With release February 2017, this feature became generalized to any registered model chain; this feature is described in Chapter "Non RODOS-Lite models". RODOS-Lite models Kicking via Client or Server; influence of multi-user feature For automatically kicking a calculation via RODOS-Lite xml-files, they must be placed in a special directory which is scanned periodically by the system: when new such files are detected, the respective calculations are started. How to use the "Automatic start on incoming RODOS-Lite xml" feature depends on the way JRodos is deployed. Users without access to the JRodos Server folder must place the xml files into a Client folder; the path depends on the status of the multi-user feature: Multi-user feature not active18: Users who work with their individual JRodos Client have to place the xml-files into folder Creating suitable RODOS-Lite xml files There are two possibilities which are described below. You may either start a JRodos run directly with the desired model chain, specify all run parameters with the RODOS-Lite input interface, and save the run specifications via that interface (by pressing RODOS-Lite Tool Bar => File => Save). You may eventually edit the file later with some editor, but then make sure the file is in ANSI encoding and correct in syntax and content as if created by RODOS-Lite (!). Alternatively, you can edit an xml-file created with the RODOS-Lite input interface for the EMERGENCY chain or the AUTOMATE mode. To execute different model chains, the xml file must 18 There is no folder with name "multiuser" in the be extended - make sure the file is in ANSI encoding (!). The following data should be put inside the roliteInterface tag: Non-RODOS-Lite models With release February 2017, it became possible to trigger calculations with any registered model chain by placing xml files containing input data in a special folder. For some models, however, it is impossible to have all input data in one xml file. For such models an additional binary “huge data” file has to be delivered simultaneously with the xml file. The steps that are necessary for triggering an automatic calculation are described below. Firstly, create the desired model chain. Then, create the project, initialize all tasks in the project, and start the calculation. Right-click on the project line in Project Explorer and select "Create InputXML file" (Figure 139). In the appearing dialog select the name (e.g. selected-name) and press “Save” button. The operation creates two files (here: selected-name.xml and selected-name.hugeData). Figure 139: Creating the set of incoming xml and huge data files. Open the selected-name.xml file. It contains inside a root tag the following tags: . modelsChain – desired model chain name. . userName – owner of the automatically created project. . template – this defines name of the automatically created project in the format prefix%date- time-format%suffix, my%YYYY-MM-dd-HH-mm%auto. If a date-time-format is not given, the current time is added to the end of project name to make it unique. . A set of model tags. Each tag describes a single model in the chain. This tag has id and name attributes, which should be left unchanged. The model tag contains several sub tags: previous-models – defines the previous (parent) model. Remove the tag if no parent is required, otherwise fill location and uid attributes: location – can have external or internal value. Put internal if previous model is within current project and external if another project from database should be loaded. 106 uid – previous task ID. If location is set to internal, then uid value should be the same as id attribute of the previous model in this xml file. If location is set to external, then put task UID as uid value (see information below on how to obtain such UID). input-data – defines (a part of) input values and follows the structure of corresponding task Input folder in Project Explorer. A user can modify UI-input sub tags. For the moment it is not possible to modify input binary values, which are described in selected-name.hugeData file. Put both files (first selected-name.hugeData, then selected-name.xml) into Figure 140: Obtaining UID from Project/Task. 107 Working with the Recurrent Job Launcher Since version July 2014 Update 3 contains the first version of a so-called JRodos Recurrent Job Launcher is available. This tool allows to initiate and kick-start prognostic calculations with a fixed release scenario that shall be carried out in a recurrent manner with a user-given frequency for one or more predefined nuclear power plant (NPP) blocks. By default, the launcher will kick calculations with the standard JRodos Emergency model chain. For initiating a set of such calculations select "JRodos Recurrent Job Launcher..." from the tool box in the JRodos Menu bar. There, you have to define: the target NPP units, the release time pattern (round the release start to minutes, hours, days), the desired project name template, a pre-fabricated RODOS-Lite xml serving as project template. The template RODOS-Lite xml contains all required information required by the model chain to be applied. For the standard Emergency model chain, this includes the source term, the meteorological provider / hand input weather, the ADM model to be used, the prognosis duration, the selected grid, and other specifications if any. Once defined by some JRodos user, the calculations are launched with the given frequency and release time pattern for each of the selected units. The recurrent process takes place in the background on the Server side, even when the Client session is closed. Information about the processing status and the possibility to stop the automatic launching process is contained in a separate tab in the "Properties" section of the JRodos User Interface. In the frame of JRodos, each single calculation is represented as one individual project; the project name includes the NPP unit name and the assumed starting time of the release. After a calculation is performed it is automatically saved into the JRodos project database where it can be accessed by the authorized users in the usual way. A separate "Working with the JRodos Recurrent Job Launcher" document is included in sub-folder "Documents" of the 108 Working with the Statistic Data Output tool Since version July 2014 the first version of a tool for generating statistically distributed results with JRodos for further analysis with external tools is available; the statistics comes purely from a variation of the weather conditions. As pre-requisite, one needs to have numerical weather prediction (NWP) data available for some prolonged period of time - the more, the better the statistical quality of the analysis. The recommended span is 3-5 consequent years. To use this meteorological data in JRodos, a meteorological provider has to be defined and the data to be imported into the data base (DB) in the usual way. Two preparatory steps are required before the tool can be started. The first step requires creating an Emergency project that specifies all necessary RODOS-Lite settings including the meteorological provider. These settings are then fixed for all the runs within one batch; the only changing part is the date and the time of the release - this generates the statistics. When satisfactory and tested, the RODOS-Lite xml is saved as a file to serve as template. The second step consists in pre-selecting the results to be generated for the statistical analysis; this has to be done by copying the JRodos result path and inserting it into the file A separate "Working with the Statistic Data Generation Tool" document is included in sub-folder "Documents" of the 109 Working with the reporting functionality Manual report creation 1. Create a new report by clicking (Menu Bar)Report → New report. The Page Setup window opens. After clicking OK, the report appears as a "Report: 'Report name'" tab in the Properties Window. Figure 141: Create a new report. Figure 142: Page setup window. 2. Display some map result in the Main Window's Map Tab and make it a nice view (scale, styling, layer order, and appearance of legend). Add the view to the report by clicking (Menu Bar) Report → Add_to_Report, or by clicking on the "(Tool Bar) Add to report" icon; give a name to the image. The map view appears in the "Report: 'Report name'" Tab in the Properties Window. Figure 143: Add to report button. Figure 144: Report item for the selected map view. 110 3. Add a temporary tab with a chart and a table view, simulating results from a model by selecting (Menu Bar)Report → (Temporary) Chart. Activate the chart view tab and press the “Add to report” button; give a name to the current chart and (or) table. The view appears in the reporting section. Figure 145: Report item for the selected chart and table view. To change the report item header / footer right click on the selected report item and choose “Edit header / footer”. Alternatively go Report → Edit header / footer. Put the desired text, format it and close the editor. The text entered will be saved automatically. Figure 146: Edit header / footer. Figure 147: Header / footer editor window. To add the item to report select the correspondent report tab, choose the desired tab in the Main Panel with Map, Chart or Table and press “Add to report” button, giving the name to the current item. Alternatively go Report → Add to Report. The view appears in the reporting section. To add text to report select the correspondent report tab go Report → Add to Report and give the name to the current text item. The view appears in the reporting section. To change the content of the text item right click on the selected text item and choose “Edit text…” The text entered will be saved automatically. 111 Figure 148: Add text to report. To remove the item from report right click on the selected report item and choose “Remove”. Alternatively press Delete key. Figure 149: Remove report item. To delete the whole report select the correspondent report tab and go to Report → Delete Report. To reorder report items select the correspondent item and drag it to the desired position. To preview the report item, double click on the corresponding item in the report panel. The Print preview window appears, making possible to Export to PDF, XML etc and Print the current item. To preview the whole report select the correspondent report tab go to Report → Show report. The Print preview window appears, making possible to Export to PDF, XML etc and Print the current report. To export report to PDF, RTF, XML etc make preview of the report and go to Export → Export to Figure 150: Print preview window. 112 To change whole report properties select the correspondent report tab such as orientation, margins, insert/delete page count, insert/delete page breaks go to Report → Page setup. The Page setup dialogue appears. Changing properties of result items To change report item properties select the corresponding item and change the desired property in the table. Figure 151: Report element properties. Height / Width – height and width (in pixels) of the rectangle where the report item will be printed. One of them (not both) can be shown in percentage of page height / width correspondingly. If one or both values are bigger then page size this parameters are taken as page width or height correspondingly. For map images Height and Width is calculated automatically. Figure 152: Height is too big (the chart is too high) and Height is too small (not enough to show the whole image). Scale – if switched on the image will be scaled to fit the report page. Otherwise only part of the picture will be presented in the report. 113 Figure 153: Scale switched on (left) and switched off (right). Visible – if switched on then the item will be visible in the report. X / Y – the coordinates of the top left corner of the rectangle where the report item will be printed. X- parameter can be shown in percentage of the page width. See (Height / Width). Alignment, colour, font name, font size, fsbold, fsitalic, fcunderline, vertical-alignment – font properties for the report item represents table. For tables all these parameters can be edited separately for each column. 114 Options in the Menu Bar Localisation (UI language) JRodos supports several languages for the user interface (UI) via the "Localisation" option. For changing the UI language, click Options → UI localisation and then select one of existing locales. Figure 154: Custom localisation Time Zone You can specify the Time Zone in which all dates20 will be presented. For changing the Time Zone, click on Options → Time Zone and select the ID for the wanted time zone ID. Figure 155: Select Time Zone dialogue (left) and Time Zone dialogue (right). The selected Time zone can be seen (for example) in the Message Window. Figure 156: Time Zone change in the Message Window. 20 Except dates for NWP and measurement data. 115 Report Settings Your can change report options and specify if automatic report generation enabled, and the format of all output files. To change report options click on Options → Report Settings. Report Settings dialogue will appear, see Figure 157. Figure 157: Report settings dialog. If you selected “Generate report automatically” option reports on base of assigned layers will be generated automatically after successful running of the project. If you selected “Generate PDF”, “Generate RTF”, “Generate HTML as ZIP folder” options, selected report type will be created. No reports will be generated if neither type checkbox is selected. Please Note: The background layers visible in the generated reports are the ones defined in the user-dependent Initial Load Layer list. At present, the map layers defined in that list have to be loaded to the Server side manually, once after the installation for a new user, and again when the Initial Load Layer list was modified by the user. For loading the maps to the Server part, click (JRodos Menu Bar) => Options => Report Settings. There, click on [Load Maps to Servers]. In the message window, you will get information about the loaded Initial Load Layers. Internet Settings You can change internet options and HTTP proxy, HTTP port, user name, password if required to access information from web. To change internet options, click on Options Internet Settings. Internet Settings dialogue will appear. Figure 158: Internet settings dialog. Please NOTE that internet options should be defined for each user. 116 User Policy There are currently two user policies available: Simple and Advanced. To change the user policy, click on Options User policies and select the policy. The selected policy is saved in the configuration and will be used on start of the next JRodos run. 117 Appendix: Working with sort-able tables Sorting Sorting can be achieved by clicking on the respective column label field. The entries in the table become sorted with respect to the selected attribute. A little arrow appears in the label field that indicates the sorting order. Figure 159 shows the "Open Project" dialogue with the entries sorted by the values of attribute "Date Created", newest creation date on top. Clicking on the arrow will reverse the sorting order. Clicking again on it undoes the sorting, and the arrow disappears. Note: Sorting can only be done with respect to one attribute. You should take care that only one label shows the sorting arrow. If there are several labels marked for sorting, they can block each other. In such case, undo unnecessary sorting selections. Figure 159: Sort-able table with sorting by "Date Created", most recent one on top. Filtering There are two ways to use Filters: Filtering out for showing all entries that do contain a given text field: Type the text in one of the empty boxes in the line below the topmost line. This is possible for all columns except dates. Example: Figure 160 shows an "Open Project" dialogue window with filter set to show all user names starting with the three characters "hon" Filtering out for showing only entries that do not contain a given text field: Type an exclamation mark ("!" for "not"), then the text in one of the empty boxes in the line below the topmost line Example: Figure 161, left part, shows an "Open Project" dialogue window that contains many projects that were generated automatically, without a filter. Figure 160, right part, shows the same window with with filter "!auto" for supressing all descriptions starting with characters "auto" Both ways of filtering are possible for all columns where one can enter a filter. To return from the filtered view, erase the search string from the filter field. 118 Figure 160: Sort-able table with filter set for showing all user names starting with characters "hon". Figure 161: Sort-able table without filtering (left), and with filter set for supressing all descriptions starting with characters "auto". Selecting rows It is possible to select one or several individual rows, or a block of connected rows; selected rows are marked by a yellowish colour: One and only one individual row: Simply left click on the desired row Several individual rows: Left click on each desired row while holding the Control key pressed Block of connected rows: Left click on the upper and lower row of the desired block while holding the Shift key pressed For the selection of individual rows and blocks of connected rows together, keep the Control key pressed , too, while selecting the block(s) as described above. Figure 161shows the "Open Project" dialogue with three selected individual rows (via pressing the Control- key) and two blocks of connected rows (via pressing the Shift-key in addition to the Control-key). If there are several rows marked, you can deselect any individual row by left clicking on the desired row while holding the Control-key pressed. Attention: If you click on any row without holding the Control key pressed, all rows except the one you did clicked on get unselected. 119 Figure 162: Sort-able table, with several rows selected. 120 Document History Document Title: JRodos User Guide Version and status: Version3.4 (JRodos February 2017 u2) Issued by: KIT Campus Nord/IKET History: Version3.4 (JRodos February 2017 u2) Version 3.31 (JRodos February 2017) Version 3.3 (JRodos February 2017) Version 3.2 (JRodosJuly2014update3) Version 3.1 (JRodosJuly2014update1) Version 3.0 (JRodosJuly2014) Version 2.6 (JRodosMay2013) Version 2.5 (draft) Version 2.4 (draft) Version 2.3 (draft) Version 2.2 (draft) Version 2.1 (draft) Version 2.0 (draft) Version 1.5 (draft) Version 1.4 (draft) Version 1.3 (draft) Version 1.2 (draft) Version 1.1 (draft) Version 1.0 (draft) Date of Issue: 26 March 2019 File Name: JRodos_UserGuide 121