Rainbow Operator's Manual Vol. 1radar.irimo.ir/images/file/RainbowApplication_4_2.pdf · Rainbow® Operator's Manual • Volume 1 (General Description) Overview Gematronik GmbH •

Gematronik GmbHRaiffeisenstr. 1041470 Neuss - GermanyTel.: (+49) 2137 782 0Fax: (+49) 2137 782 11EMail: [email protected]

Rainbow®

Operator's Manual

Volume 1

General Description

Rainbow Version 3.4Document Release 4.2

(2001-05-02)

Document Code: GEMA-SD-0150-3442-1

This documentation is copyright 1989-2001 by GEMATRONIK GmbH, Raiffeisenstrasse 10, 41470 Neuss, Germany.

All rights reserved. This product and related documentation are protected by copyright and distributed under licenses restrictingits use, copying, distribution or de-compilation. No part of this product or related documentation may be reproduced in any formby any means without prior written authorization of GEMATRONIK GmbH and its licensors, if any.

Portions of this product may be derived from UNIX and Berkeley 4.3 BSD systems, licensed from UNIX System Laboratories,Inc., a wholly owned subsidiary of Novell, Inc., and the University of California, respectively.

The products described in this manual may be protected by one or more German or U.S. patents, foreign patents, or pendingapplications.

TRADEMARKSRainbow® is a registered trademark of GEMATRONIK GmbH. DEC is a trademark of Digital Equipment Corporation. DECstationis a trademark of Digital Equipment Corporation in the U.S. and certain other countries. Sun, Sun Microsystems ComputerCorporation, Solaris and SunOS are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and certainother countries. UNIX is a registered trademark of UNIX System Laboratories, Inc., a wholly owned subsidiary of Novell, Inc..Motif and OSF/Motif are registered trademarks of Open Software Foundation, Inc.. Motorola is a registered trademark ofMotorola, Inc.. Tektronix and TekXpress are registered trademarks of Tektronix, Inc.. Microsoft and Microsoft Windows areregistered trademarks of Microsoft Corporation.

All other product names mentioned herein are the trademarks of their respective owners.

The XWindows System is a product of the Massachusetts Institute of Technology (MIT).

THIS PUBLICATION IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE, OR NON-INFRINGEMENT.

THIS PUBLICATION MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES AREPERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEWEDITIONS OR THE PUBLICATION. GEMATRONIK MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S)AND/OR PROGRAM(S) DESCRIBED IN THIS PUBLICATION AT ANY TIME WITHOUT FURTHER NOTICE.

Rainbow® Operator's ManualVolume 1General Description

Part 1: Overview Release 4.2

Part 2: Supervisor Manager Release 4.1

Part 3: Radar Manager Release 4.2

Part 4: Display Manager Release 4.1

Part 5: Rainbow Utilities Release 4.2

Part 6: Rainbow Configuration Files Release 4.2

This manual describes all available features of the Rainbow® software,independent of the customer specific configuration.

Rainbow® Operator's Manual •••• Volume 1 (General Description) Overview

Gematronik GmbH • Rainbow® Version 3.4 • Document Release 4.2 (2001-05-02) 1–1

Part1

Overview



Table of Contents

1 OVERVIEW........................................................................................................... 1–3

1.1 General Layout of the Rainbow® Data Processing and Networking System .....1–31.2 Rainbow® Environment ............................................................................................1–51.2.1 Hardware Environment..........................................................................................1–51.2.2 Software Environment ...........................................................................................1–61.2.2.1 UNIX ................................................................................................................1–61.2.2.2 X-WINDOW X11 .............................................................................................1–61.2.2.3 OSF/Motif.........................................................................................................1–61.3 Distributed Processing in the Rainbow® System..................................................1–71.3.1 Rainbow® Processes.............................................................................................1–71.3.2 Operational Flow .................................................................................................1–101.3.3 The Meteorological User at the Rainbow® Workstation .....................................1–11



1 Overview

1.1 General Layout of the Rainbow® Data Processing andNetworking System

The general layout of the Rainbow® data processing system is shown in the following figure. Theaim of this system is

• to collect data from a radar sensor

• to perform real-time processing using a dedicated signalprocessor, to treat a large amount of "raw" data.

• to generate processed data sets or "products"

• to distribute these products via a communication network to one or more users or to acompositing computer centre.

A user-friendly interface (GUI = graphical-user-interface) at the user workstation providescommunication between the sensors and the users. Products can be formatted, stored andvisualised there.

The figure (next page) shows a typical installation. This manual refers to the UNIX part. Becauseof the configuration flexibility of the network, database and the Rainbow® system, this operator'shandbook does neither explain which software processes run on which hardware componentsnor by means of which transmission medium the hardware components are connected.



21"

21"

21"

21"

21"

RA

INB

OW

®M

ain

Wo

rkst

atio

n

Eth

erne

t

Mic

row

ave

Link

toW

eath

er

Radar

Site

2 M

bit/s

RA

DA

R R

OO

M A

T C

EN

TR

E

Bridge

Mo

de

mR

ain

Gauge

Data

Serv

er,

Dis

play

PC

RA

INB

OW

®B

ac

ku

p W

ork

sta

tio

n

Dia

l-up L

ines

Public

Te

leco

mm

un

ica

tion

Netw

ork

Rai

n G

aug

e N

etw

ork

Mic

row

ave

Tra

nsc

eiv

er

Eth

erne

t

Co

lor

La

serj

et

Printe

r

Sate

llite

Rec

eivi

ng S

yste

m

Public

Te

leco

mm

un

ica

tion

Netw

ork

Re

mo

teM

ain

tenance

Te

rmin

al

SU

N U

LT

RA

5S

parc

RA

INB

OW

®D

ispla

y W

ork

statio

n

AN

AL

YS

IS D

IVIS

ION

Dis

play

PC

Eth

erne

t

19''

ISD

N-S

0O

ffic

e R

ou

ter

Dis

play

PC

RA

INB

OW

®D

ispla

y W

ork

statio

n

RE

SE

AR

CH

DIV

ISIO

N

4 IS

DN

Lin

esto

Re

mo

te U

sers

10B

AS

E2 R

epeate

rC

om

mu

nic

atio

n S

erv

er

ISD

N-S

2M

ap

p.

15

0 m

ap

p.

15

0 m

ap

p.

10

0 m

21"

21"

Co

lor

Inkj

et

Printe

r

Eth

erne

t

RA

INB

OW

®D

ispla

y W

ork

statio

n

HY

DR

O D

IVIS

ION

21"

SU

N U

LT

RA

10

128

MB

Mem

ory

9 G

B H

ard

Dis

kD

DS

-3 G

B D

AT

Driv

e

19"

Co

lor

Inkj

et

Printe

r

Co

lor

Inkj

et

Printe

r21"

21"

Co

lor

La

serj

et

Printe

r

10B

AS

E2

Re

pe

ate

r

26 fre

e IS

DN

Line

s

SU

N U

LT

RA

10

128

MB

Mem

ory

9 G

B H

ard

Dis

kD

DS

-3 G

B D

AT

Driv

e

SU

N U

LT

RA

10

128

MB

Mem

ory

9 G

B H

ard

Dis

kD

DS

-3 G

B D

AT

Driv

e

SU

N U

LT

RA

10

128

MB

Mem

ory

9 G

B H

ard

Dis

kD

DS

-3 G

B D

AT

Driv

e

SU

N U

LT

RA

10

128

MB

Mem

ory

9 G

B H

ard

Dis

kD

DS

-3 D

AT

Drive

ISD

N-S

0O

ffic

e R

ou

ter

ISD

N-S

0O

ffic

e R

ou

ter

ISD

N-S

0O

ffic

e R

ou

ter

19''

Dis

play

PC

19''

Co

lor

Inkj

et

Printe

r

Dis

play

PC

19''

Co

lor

Inkj

et

Printe

r

Co

lor

InkJ

et

Printe

r

Co

lor

Inkj

et

Printe

r

21"

RA

INB

OW

®D

isp

lay

Wo

rkst

atio

n

21"

SU

N U

LT

RA

10

128

MB

Mem

ory

9 G

B H

ard

Dis

kD

DS

-3 G

B D

AT

Driv

e



1.2 Rainbow® Environment

1.2.1 Hardware EnvironmentThe typical Rainbow® workstation consists of:

• Keyboard,

• Mouse and

• Colour graphic monitor.

The keyboard is used to communicate with the Rainbow® application software, the UNIXoperating system and all associated tools and utilities. By typing in a character or text sequencethe user sends information to the application program currently running. In some cases, themenus or texts, seen on the monitor, will ask the operator to type in a text to obtain the desiredresult. The communication with the Rainbow® or operating system, using keyboard entry, isreduced to a minimum because almost all functions are controlled using the mouse. Only texts,comments or operating system commands still have to be entered on the keyboard.

Most commands are given using the mouse. An associated cursor (usually an arrow or a cross)seen on the colour monitor moves simultaneously to any movement of the mouse on the screen.

The mouse has 2 or 3 buttons which allow the operator to click, to select or to drag objects onthe screen in various ways. (In almost all applications only the left mouse button is used forthese actions.)

The colour graphic monitor visualises the information obtained by the graphical user interface(GUI) on a high resolution screen, using pull-down menus or graphical images. Most user activity(i.e. an input action) is routed to the application software via a mouse "point and click" on thecolour monitor. All meteorological products are converted into a displayable format which arevisualised in a colour monitor window frame.

Mass storage media such as hard disks are used to provide short term storage ofmeteorological products (e.g. 3 to 5 days), whereas the tape is used to provide long termstorage.

The communication interfaces assure the link to the Rainbow® radar processor (via radio link,serial, LAN) or to external users who may be configured to receive a subset of the productsavailable at the workstation (via modem telephone link(s)).

A number of Rainbow® workstations may be interconnected to form a wide area network (WAN)or a local area network (LAN).



1.2.2 Software EnvironmentThe meteorological radar workstation software system is designed to operate in the operatingsoftware environment of UNIX, X-WINDOW and OSF/Motif.

1.2.2.1 UNIX

The UNIX Operating System is a set of programs, which controls the computer, acts as a linkbetween the user and the computer and provides a tool for carrying out the work of theapplication software. It is :

• a general purpose system to perform a variety of jobs,

• an interactive environment which allows the user to communicate directly with the com-puter and to receive immediate response to requests and messages,

• a multi-user environment which allows the user to share the computer's resources withother users on a timesharing basis,

• a multi-tasking environment that enables the user to run more than one program simul-taneously.

Commands are names of programs that the user wishes to run. Packages of programs arecalled tools.

For a detailed explanation for the use of UNIX commands and tools, please refer to the vendormanuals provided for the specific workstation.

The user normally does not quit the Rainbow® Software System, thus he will never have to dealwith the UNIX operating system directly, as he remains always within the Rainbow® system.

The system supervisor or the Rainbow® supervisor usually carries out all necessary maintenanceof the UNIX environment.

1.2.2.2 X-WINDOW X11

The X Window system, called X11 for short, is a network-based graphics window system. It runson the large screen colour monitor and allows the user to work with multiple programs(applications) simultaneously, each in a separate window.

The operations performed in the windows can vary considerably, depending on the function ofthe program running. Certain windows accept input from the user, other windows displayinformation (i.e. weather radar products).

1.2.2.3 OSF/Motif

Motif is a set of guidelines that specify how a user interface of the graphic computer "looks andfeels". This term describes how the application programs appear on the screen (the look) andhow the user interacts with it (the feel).



1.3 Distributed Processing in the Rainbow® System

1.3.1 Rainbow® ProcessesTypically, the Rainbow® system consists of the following processes:

Supervisor Manager Radar Manager Display Manager Message Logger Rainbow® Product Generation Projection Communication and administration utilities

Supervisor Manager, Radar Manager and Display Manager form the main user interface.Rainbow® product generation and communication do not appear as windows on the screen.These processes are described in the table below.





Process Function User interaction Remark

Radar Manager

(RadRainMan)

- radar control

- product generationcontrol

- definition of productparameters, scanprocedure, scheduler

-survey radar operationby means of BITE

- initiate radar operationand real-time productgeneration

- initiate interactive product generation fromexisting data

- some functions areonly accessible insupervisor mode

Rainbow®

Product Generation

(RainBow)

- calculation of dis-playable productsfrom volume raw datasets (raw dataprocessing)

- calculation of dis-playable second levelproducts from existingproducts (image dataprocessing)

- product generation iscontrolled by means ofthe Radar Manager

- invisible to the user

Display Manager

(DisRainMan)

- receive and displayof products in a window on the screen

- main tool for meteorological users

- configure Display Manager to receive onlyselected product types

- load products fromdisk

- display overlay

- start animation

- zoom

- receive text messages

- modify colours

- several DisplayManagers can be active at the sametime

SupervisorManager

(RainSuper)

- tool to controlnetwork andcommunication

- view network status

- send/receive textmessages

- open/close DisplayManagers

- one SupervisorManager on everyRainbow® hostmachine

Projection

(RainProject)

- projection of Radarimages into differentmap projections

- projection typeselectable by the user


Communication andAdministrationUtilities

(RainLog)

(RainAdmin)

(RainRCLStatus)

(RainRCLData)

- control distributed data base

- makes inter processcommunicationpossible

- survey file system

- message logging

- no user accessnecessary duringnormal operation

- is configured in factory


(except RainLog)



1.3.2 Operational FlowThe general Rainbow® radar data processing concept is shown in the following figure.

An appropriate scan procedure, depending on the desired product (e.g. volume processing), isinitiated either directly by the user or automatically by the automatic control system Scheduler.

The system manager can set up the generation of desired products controlled by the schedulerat certain time intervals in the Radar Manager.

In the Radar Manager radar operational parameters such as scan scheme, scan velocity, pulsewidth and PRF, are chosen by the Rainbow® supervisor according to the requirements of thedesired products.

The Rainbow® supervisor normally uses Scan & Product Worksheets to configure radar andproduct parameters.

Plausibility checks are performed to prevent combinations of parameters which lead either to ameaningless system operation or which can damage the system (e.g. the duty cycle of themagnetron).



The radar operation, including the antenna scans, is performed under full BITE (Built-In TestEquipment) control.

The "raw" Radar data (sometimes also called "ingest data/files") including logarithmicReflectivity (Z), mean radial Velocity (V), Spectral Width (W) and Differential Reflectivity (ZDR)are generated by the Signal Processor.

After the pre-processing in the signal processor has been performed according to the productrequirements, the 3-dimensional "raw" (or ingest) volume data set of Z, V, W, ZDR in polarcoordinates is then transferred by the Radar Processor to the Rainbow® raw data base.

Now the Rainbow® product generation process is started automatically in order to calculate thedesired product.

This product generation involves transformations from a 3-dimensional polar coordinate systemto a 3-dimensional or a 2-dimensional cartesian coordinate system. Additionally, integration,interpolation and/or projection to a 2-dimensional layer are performed to yield a displayableproduct.

For detailed description of the products supported by Rainbow® please refer to Volume 2 of theRainbow® Operator's Manual.

The products are finally stored in the product data base and are automatically displayed by theDisplay Manager.

The Display Manager is used to display products on the screen, the products can also bepresented in an animation. To do this, the Display Manager uses the complete capacities ofUNIX/X-WINDOWS.

In some cases the newly generated products are not only displayed by the Display Manager, butthey are also used as base for further so-called "second level products", which carry out e.g.accumulations or further automatic analysis.

In this case a new automatic Rainbow® product generation is started, the result is a second levelproduct, which is stored in the product data base and displayed in the Display Manager.

1.3.3 The Meteorological User at the Rainbow® WorkstationThe Rainbow® workstation can support a variety of users, including forecasters, meteorologists,hydrologists, road and airport authorities, air traffic controllers, pilots and flight planningpersonnel.

The flexible Rainbow® system can be configured to deliver the specific products needed by anyof these users.

By means of the Rainbow® Radar Manager the supervisor can configure and/or reconfigure theproduct generation scheme at any time (via interactive software configuration procedure).

Generally, the first step is to create a new product by setting the various parameters for thedesired product type. The parameters are set by means of scan and product worksheets. Theseworksheets contain all vital parameters which are necessary for the system to generate aproduct (i.e. range, height levels, integration parameters, data range etc.). After having set theparameters in the scan and product worksheets, the parameter sets are stored as SDF (scandefinition file) and PDF (product definition file). They can be recalled at any time.



Now there are two possibilities to initiate the product generation. Either the product generationstarts in the immediate mode, which means that the desired product is generated, transferredand displayed immediately at the workstation.

The other possibility is to generate the product using an arbitrarily configurable scheduler. Thisscheduler allows the user to create a timed list of product generation processes which will bestarted at a certain time at the radar.

After the generation, the product is sent to a selected destination (workstation window, networknode, archive etc.) for further processing. This timed production can be looped to runcontinuously (e.g. every 15 minutes). Different time loops can be generated throughout the day.

After all desired products have been defined in detail and placed in the scheduler, the systemruns completely unattended generating, distributing and displaying the products in the DisplayManager.

At the user workstation the Display Manager provides a large number of tools to work with thedisplayable products. These image and display system processing tools are of the following:

• Zoom, Scroll

• Colour palette choice

• Threshold level (to hide low level phenomena)

• Data level distinction using different colours (Isolevel display)

• Animation, with arbitrary number and type of products

• Overlay choice, landscape, text, contours

• Analysis of picture data by means of histograms

• Modification of values via filters

• Geographical orientation (altitude, longitude, latitude as option)

• System information

• Audio alarm and pictogram message on error event, error message text and errornumber.

Rainbow® Operator's Manual •••• Volume 1 (General Description) Supervisor Manager


Part 2

Supervisor Manager



Table of Contents

2 SUPERVISOR MANAGER........................................................................................ 2–3

2.1 System Status Icon ...................................................................................................2–42.2 Message Window ......................................................................................................2–42.3 Menu 'Show Display Management' .........................................................................2–42.4 Menu 'Show Target Management' ...........................................................................2–72.4.1 Target Management..............................................................................................2–72.4.2 Broadcast and Message input ..............................................................................2–82.5 Menu 'Show Version Info' ........................................................................................2–92.6 Menu 'Local Shutdown' ............................................................................................2–9



2 Supervisor ManagerThe Supervisor Manager runs on every Rainbow® host computer. Its main tasks are:

• monitor system configuration and networkusing a target list

• initialise targets

• open or close local and remote displays

• send / broadcast text messages to other targets

• display network/system/Rainbow® errors

In contrast to the Radar Manager, whose tasks are related to controlling radar operation andproduct generation, the Supervisor Managers tasks are related to the administration of the localhost computer and the Rainbow® network.

System messages concerning the file system or the Rainbow® network are displayed in themessage window. The Target List Window gives an overview about the current status of all localRainbow® processes and the Rainbow® network.

The Supervisor Manger window consists of the following elements:

• message window

• system status icon, indicating the latest message type

• menu bar with the item 'System', offering the options

'Show Display Management' 'Show Target Management' 'Show Version Info' 'Print' 'Local Shutdown'



2.1 System Status IconThe System Status Icon indicates the type of the latest message by changing its colourcorresponding to the message type.

2.2 Message WindowThree kinds of messages are displayed in the message field:

• Text messages from other users entered in a Supervisor Manager on a remote Rainbow®

host computer.

• System messages

• Rainbow® messages

Four categories of system messages and Rainbow® messages have to be distinguished:

• INFO (I, green)

• WARNING (W, yellow)

• ERROR (E, red)

• CRITICAL ERROR (CE, magenta)

Up to 50 messages are stored in the message window, they can be accessed using thescrollbars. The latest message is added to the top of the list, the list scrolls down automatically.

By a click with the right mouse button into one Message line there are two options available:

• 'Maximise Message List' maximises the message field to full window size. Menu bar andsystem status icon are then invisible. This is used to minimise the Supervisor Managerwindow for saving space on screen.

• 'Restore' switches back to standard window.

The Message field is surrounded by a coloured line which indicates the type of the latestmessage. This is helpful when at maximised message list the system status icon is not visible.

With the help of the menu bar option "File"->"Print" a hardcopy of the message window text lineswill be printed.

2.3 Menu 'Show Display Management'The Rainbow® Display Manager is the tool for the display and examination of all radar andsatellite images.

On each Rainbow® host computer a limited number of Display Managers can be started fordisplay on the local host screen or on a remote X-terminal screen. The maximum number ofDisplay Managers depends on the specific Rainbow® system layout and is not user configurable.It can be read from the target list (see 'target list window').

By clicking on 'Show Display Management' a window entitled 'Display Management' is opened.It consists of four columns: 'Status', 'Configuration name', 'PID' and 'Display'.



Status

By clicking the 'Status' button the display's status is toggled between 'active' and 'closed'.Toggling the status button means opening or closing of the corresponding Display Manager.

Configuration name

When closing a Display Manager all Display Manager Parameters are stored in a configurationfile.

Before opening a new Display Manager a new configuration name can be entered into the fieldbelow 'Configuration name' e.g. "MyNewConfig". When closing this Display Manager again thecurrent configuration will be stored in a file called "MyNewConfig.cfg". From now on thisconfiguration can be recalled by entering "MyNewConfig" and pushing the 'Status' button. TheDisplay Manager will then come up with exactly the same configuration as it had when it wasclosed.

By clicking on the field below 'Configuration name' a file selection box called 'SelectConfiguration' is opened. An old configuration can be recalled by selecting it from the table inthe right window with the mouse and pushing the 'OK' button. A new configuration name can becreated by entering the name in the field below 'Selection' and pushing the 'OK' button.



PID

PID is the abbreviation of 'process identifier'. In this field the UNIX process identifier of eachDisplay Manager is displayed. If the process is not active a "0" is displayed, otherwise the currentprocess identifier. By means of the PID the supervisor can see, if a Display Manager is actuallyrunning although it might be displayed on a remote X-terminal.

Display

The entry in the field below 'Display' specifies on which terminal the Display Manager appears.The name consists of the symbolic IP terminal name (or IP address), a colon and the display ID(usually "0.0").

A click on the field below 'Display" opens a dialog box where a new IP terminal name can beentered.



2.4 Menu 'Show Target Management'In the upper part of the Target Management window all target processes and remote Rainbow®

host computers are listed with which the local Rainbow® host can communicate. In the lower partBroadcast or Message text can be entered. "Print" is used for printing out the target list. With"Close" the target list window will be closed.

2.4.1 Target ManagementThe target list depends on the specific Rainbow® system layout and is not user configurable.

The first column contains the process ID. To each process on a Rainbow® host correspondsa unique process ID.

The second column offers information about the current state of a target. Possible values are:

• 'active'

• 'down'

• 'terminating'

• 'n.a.' (not available)

The content of the third column can be 'local', 'TCP/IP', 'SLIP' or 'zmodem' depending on thetype of connection.



The names in the right column correspond to the Rainbow® processes. The number and typeof indicated processes depend on the specific Rainbow® installation:

RainSuper Supervisor Manager

RainBow Rainbow® genesis (product generation)

RadRainMan Radar Manager

RainLog Message logger

RainAdmin File system administration

RainFTP Data dissemination

RainAcq Data acquisition

RainProject Projection task

RainRCLData Communication with RCP (data port)

RainRCLStatus Communication with RCP (status port)

DisRainMan Display Manager

The Target List window is subdivided into five subsections. The targets in these subsectionshave different types. As a consequence the possible user interactions vary from target type totarget type.

LOCAL PROCESSES

This section displays the names of all processes that are configured to run on the local hostcomputer. Their target identification number (TID) is 0. This indicates that these processes areconfigured as local processes.

All local processes are started automatically when the local Rainbow® system is started. As aconsequence the state of the local processes is always 'active'. In case the state of a localprocess is 'down', the process can be restarted by selecting the respective line in the Target ListWindow with the Mouse pointer and the left mouse button, then clicking on the right mousebutton and selecting 'Init Target'.

LOCAL DISPLAYS

All Display Managers that are configured to run on the local host computer are displayed in thissection.

Display Managers cannot be started using the 'Init Target' option. This is only possible in the'Display Management' window.

2.4.2 Broadcast and Message inputThe only targets able to receive text messages are the Radar Manager and the DisplayManager(s). It does not matter, if these targets are configured as 'local' or 'remote'. Messagesto other targets have no effect.

Message dissemination:

• click on the Message / Broadcast input field and enter the message text

• select a target from the target list (e.g. the Radar Manager or a Display Manager)



• push the Message / Broadcast button in order to send the message to the selected target

The message will then appear in the targets message window.

2.5 Menu 'Show Version Info'The 'Show Version Info' item activates a window which indicates the installed Rainbow® version.As part of the version number the date stamp of compilation is displayed.

2.6 Menu 'Local Shutdown'The 'Local Shutdown' procedure starts after typing in the requested password. Then all localRainbow® processes are stopped including the Supervisor Manager itself.

At first all the displays that were opened by the Supervisor Manager are closed automatically(including those on remote X-terminals). For each Display Manager the current displayconfiguration is saved and proposed as startup configuration the next time the Display Manageris started again.

After a local shutdown there is no Rainbow® process running on the local Rainbow® hostcomputer. This applies also to the Rainbow® networking functions.

This function should be used to stop Rainbow® before a shutdown of the complete hostcomputer is performed.

Rainbow® Operator's Manual •••• Volume 1 (General Description) Radar Manager


Part 3

Radar Manager



Table of Contents

3 RADAR MANAGER ................................................................................................ 3–4

3.1 Radar Manager Control Panels................................................................................ 3–43.1.1 Activity Indicator Panel .......................................................................................... 3–43.1.1.1 Communication Indicator Section ................................................................... 3–43.1.1.2 Acquisition Indicator Section ........................................................................... 3–53.1.1.3 Processing Indicator Section........................................................................... 3–53.1.1.4 Status Indicators and Notification Request ..................................................... 3–53.1.2 Product Generation Panel..................................................................................... 3–73.1.2.1 Create Product Definition ................................................................................ 3–83.1.2.2 Create Scan Definition .................................................................................... 3–93.1.2.3 Create Schedule Task..................................................................................... 3–93.1.2.4 Show Automatic Generation Task Menu ........................................................ 3–93.1.2.5 Create Immediate Schedule Task................................................................... 3–93.1.2.6 Show Toolbox.................................................................................................. 3–93.1.3 BITE Control Panel.............................................................................................. 3–103.1.3.1 Show BITE Status Menu ............................................................................... 3–103.1.3.2 Show BITE Review Menu.............................................................................. 3–123.1.3.3 Get Current BITE Status ............................................................................... 3–123.1.4 Schedule Task Control Panel ............................................................................. 3–133.1.4.1 Select Schedule Task.................................................................................... 3–133.1.4.2 Start Schedule Task ...................................................................................... 3–133.1.4.3 Stop Current Schedule Task ......................................................................... 3–133.1.4.4 Edit Schedule Task Menu ............................................................................. 3–143.1.5 Switch to Supervisor Mode ................................................................................. 3–153.2 Product Definition ................................................................................................... 3–163.2.1 Supported Product Types ................................................................................... 3–163.2.2 The Product Parameter Board ............................................................................ 3–183.3 Scan Definition ........................................................................................................ 3–203.3.1 The Scan Worksheet .......................................................................................... 3–203.3.1.1 Global functions............................................................................................. 3–213.3.1.2 Scan Mode section........................................................................................ 3–213.3.1.3 DSP Settings Section .................................................................................... 3–223.3.2 How to Use the Scan Worksheet........................................................................ 3–223.3.2.1 Azimuth Scan ................................................................................................ 3–223.3.2.2 Elevation Scan............................................................................................... 3–223.3.2.3 Volume Scan ................................................................................................. 3–233.3.2.4 DSP Settings ................................................................................................. 3–233.3.2.5 Additional parameters ................................................................................... 3–253.4 Cyclic Loop - Watchdog Scheduler Definition..................................................... 3–273.4.1 Edit Toolbox ........................................................................................................ 3–283.4.2 Scan Folder ......................................................................................................... 3–293.4.3 PDF Folder .......................................................................................................... 3–293.4.4 Base Scheduler Definition................................................................................... 3–303.4.5 Watchdog Scheduler Definition .......................................................................... 3–303.4.6 Hybrid Scan Scheduling...................................................................................... 3–313.4.7 Start Time field .................................................................................................... 3–323.4.8 Killing a Running Scheduler ................................................................................ 3–32



3.5 Automatic Generation Scheduler Definition ........................................................ 3–333.5.1 Automatic Generation of PAC, PAL, RIH and RSA Products (PAC example).. 3–343.5.2 Automatic Generation of Warning and Tracking products (TRK example)........ 3–353.5.3 Conditional Scheduler Definition......................................................................... 3–373.6 Immediate Scheduler Definition ............................................................................ 3–383.7 Toolbox .................................................................................................................... 3–393.7.1 Raw Data Processing Tool.................................................................................. 3–393.7.2 Image Data Processing Tool............................................................................... 3–413.7.3 Rainbow® Offline Processing Tool ...................................................................... 3–433.7.3.1 Configuration Files ........................................................................................ 3–443.7.3.2 Offline Processing Editor............................................................................... 3–46



3 Radar ManagerThe Rainbow® Radar Manager contains all the tools which are necessary to configure the radarsystem, the data acquisition and the product generation. It's main tasks are:

• internal/external activity monitoring

• internal/external data transfer/distribution monitoring and control

• BITE monitoring and control

• product, scan and scheduler definition

• quick start schedule job facility, fully configurable

• offline generation of products

3.1 Radar Manager Control PanelsThe Radar Manager main window consists of several user input areas.

3.1.1 Activity Indicator PanelThe activity indicator panel consists of three sections.

3.1.1.1 Communication Indicator Section

The communication section visualises the communication status betweenRainbow® Unix and Rainbow® Real-time. The section contains three indicators(from left to right):

sd icon : The Send Data indicator flashes once whenever a request (BITE or schedule task) has been transferred to Rainbow® Real-time.

rd icon : The Receive Data indicator changes the colour to the busy state in case of receiving any data (BITE, corrected schedule task, notification messages,volume files) from Rainbow® Real-time.

wr icon: The Wait for Response icon switches to an egg timer icon after a request has been sent from Rainbow® Unix to Rainbow® Real-time as long as any data will



be sent back to Rainbow® Unix. This icon is meant to be a kind of communicationheart beat indicator. If no answer will be transferred to Rainbow® Unix in case ofe.g. a network failure, the icon will automatically indicate an error status.The timeout, which decides when an error messages has to be issued is tuneableby the user. Please refer to the Configuration File Management.

3.1.1.2 Acquisition Indicator Section

This section shall give an overview about scan acquisition state of the system.In detail:

sm icon : Current Scheduler Mode indicator. If Rainbow® Unix starts a schedule taskrequest in order to acquire a volume data, the icon will change to the activecolour when the scheduler has been accepted and installed by Rainbow® Real-time. The current scan acquisition setting (None, Immediate scheduletask, Watchdog/Intermediate task) will also be displayed by means ofchanging to N (=None), I (=Immediate), C (=Cyclic loop), W (=Watchdog).

as icon : Antenna Status indicator. If the antenna scans the area, this icon will change tothe active colour as long as the antenna is positioned by the scheduler task.

rr icon : Receive Rawdata indicator. If a polar volume data set has been sent successfullyto Rainbow® Unix the indicator turns to the busy state. Default: idle colour.

3.1.1.3 Processing Indicator Section

The processing indicator section monitors the Rainbow® UNIX process anddatabase activities.

pp icon : Process Product Image indicator. During a product generation based on rawdata or a second level product generation the icon will switch to the activecolour.

dp icon : Disseminate Product indicator. In case of storing any data to the Rainbow® Unix database (BITE, volume data, contents of a schedule, temporarynotification messages) or disseminating data to other Rainbow® workstations(ROW=Remote Operating Workstation, LOW=Local Operating Workstation,RDW = passive Remote Display Workstation) the icon flashes to the busycolour.

3.1.1.4 Status Indicators and Notification Request

In order to update/refresh all information indicators Rainbow® UNIX and Rainbow® Real-time areexchanging small information packages, called notification messages and notification requests.The following table shall give more detailed information about the specific indicators.

Indicator Description

sd icon The send data icon flashes the colour from white (idle colour) to blue (busycolour) and vice versa whenever the following messages were transferredto Rainbow® Real-time

1. BITE Get Status request




2. BITE Send command

3. Schedule task command

This icon indicates only the command transmission from Rainbow® Unix(Rainbow® LOW=Local Operating Workstation) to Rainbow® Real-time),i.e. this indicator shows that the socket based communication betweenRainbow® Real-time and Rainbow® Unix is OK.

The icon is not meant as an indicator which reflects the commandexecution on Rainbow® Real-time site. In case of a TCP/IP connectionfailure between Rainbow® Unix and Rainbow® Real-time you will receive anerror message (TCP/IP connection error. Can't connect to Rainbow® RT).

Initial status: white

Busy status: blue

rd icon In case of receiving data from Rainbow® Real-time the indicator will changeto the busy state.

wr icon Every time if one of the following commands has been sent to Rainbow®

Real-time, this wait-for-response indicator changes to the busy colour aslong as Rainbow® Real-time sends an command back to Rainbow® Unix

1. BITE Get Status request

2. BITE Send command

3. Immediate product schedule task command

4. Start schedule task command

5. Stop schedule task command

In case of failures concerning the communication to Rainbow® Real-timethe system will issue after a timeout an error message (communicationfailure)

By means of a configuration file (RainbowQE.ini) this timeout can be fine-tuned according to the site infrastructure (WAN/LAN bandwidth /transmission speed).

In case of problems with the WAN/LAN hardware connection to Rainbow®

Real-time the system will issue an error message after 30s (fixed).


Busy status: egg timer

Error status: exclamation mark

sm icon This indicator icon switches from idle status to active status when a newschedule task has been transmitted and accepted by Rainbow® Real-time.

The following scan acquisition settings are possible:

1. None (N)

2. Immediate schedule task (I)

3. Cyclic loop schedule task (C)

4. Intermediate/Watchdog schedule task (W)

Whenever the currently installed schedule task may be removed orexchanged, Rainbow® Real-time sends a notification message to Rainbow®

Unix to update the icon information.

When the data acquisition will be stopped or interrupted in case of

1. Kill schedule task

2. Changing the schedule task

3. Starting an Immediate product schedule task

the icon will switch back to None (N).




as icon This indicator icon switches from idle status to busy status when a newscan acquisition setting has been started by Rainbow® Real-time, i.e. whenthe antenna is scanning the area.

When the data acquisition will be stopped or interrupted in case of

1. killing schedule task

2. changing the schedule task

3. starting an immediate product schedule task

Rainbow® Real-time will send a notification message to Rainbow® Unix toupdate the icon settings.


Active status: blue

rr icon Before any raw data transmission Rainbow® Real-time sends a startvolume transfer notification message to Rainbow® Unix.

After the successful transfer to Rainbow® Unix, a stop volume transfernotification message will be sent to Rainbow® Unix.

The icon colour will change to the appropriate status.

In case of parallel processing Rainbow® Real-time will send only twonotification messages (start/stop).


Active status: blue

pp icon In case of generating any product (raw data->image, raw data->scalar,

image->image), the indicator changes to the active colour.


Active status: blue

dp icon In case of storing data to the Rainbow® database this icon will show thebusy state. Also in case of sending meteorological products to otherworkstations the icon will flash to the busy colour.

In case of distributing products with Rainbow® FTP the icon does not reflectthe transmission time needed for any FTP transfer.

The icon's purpose is only to inform the operator about the productdistribution status and database activities.


Active status: blue

3.1.2 Product Generation PanelThe Product Generation panel gives access to all worksheets which are related with interactiveand automatic Radar product generation, both online and offline. To get the product generationrunning, different steps has to be done:

• In a first step the desired product has to be defined (product definition worksheet).Result: A product definition file (PDF) which holds the complete product specification.

• Then the corresponding scan parameters has to be adjusted (scan definition worksheet).Result: A scan definition file (SDF) which holds the complete scan specification.



• To initiate automatic product generation, both SDF and PDF has to be combined to aschedule task (cyclic loop/watchdog scheduler definition worksheet).Result: A scheduler definition file which holds all information for automatic antennascanning, "raw data" sampling and product generation.

Additionally, automatic generation of so-called "second level products" can be initiated. Secondlevel products are products which use other product data instead of "raw data" as input.

3.1.2.1 Create Product Definition

By a click on the PDF button a selection box opens which allows to select the desiredproduct type to be defined. Rainbow® products are organised in several productcategories:

• Standard meteorological products, e.g. PPI(Z), CAPPI(V), ETOP(R),

• Extended meteorological products, e.g. VVP(2) (volume velocity processing),

• Hydrological products, e.g. SRI (surface rainfall intensity),

• Wind Shear detection products, e.g. RDS (radial shear),



• Warning & forecasting products, e.g. HHW (hail warning),

• Phenomena detection products, e.g. GUF (gust front detection product),

• Aviation products, e.g. LTB (layer turbulence), and

• User defined products, which can be developed by the user itself with the help of theRainbow Product Generator (optional application).

The selection of one existing product definition opens the corresponding product parameterboard (product definition worksheet). Please refer to chapter 3.2 (Product Definition) for furtherinformation.

3.1.2.2 Create Scan Definition

By a click on the SDF button the Scan Worksheet opens. It offers the possibility to defineantenna scan parameters as well as signal processor settings. There are three scancategories:

• Azimuth scan: azimuth full circle or sector, elevation fixed

• Elevation scan: azimuth fixed, elevation sector

• Volume scan: azimuth full circle, 2 to 20 elevations

Please refer to chapter 3.3 (Scan Definition) for further information.

3.1.2.3 Create Schedule Task

By a click on the LOOP button the Cyclic Loop - Watchdog Scheduler worksheet opens.Here, scan definition and product definition files can be combined for automatic Radaroperation and product generation. Please refer to chapter 3.4 (Cyclic Loop - WatchdogScheduler Definition) for further information.

3.1.2.4 Show Automatic Generation Task Menu

By a click on the AUTO button the Automatic Generation worksheet opens. Here, theautomatic generation of "second level" products can be scheduled. The desired secondlevel product as well as the necessary primary input product are selectable. Please referto chapter 3.5 (Automatic Generation Scheduler Definition) for further details.

3.1.2.5 Create Immediate Schedule Task

By a click on the IMM button the Immediate Mode scheduler worksheet opens. One scandefinition file and one corresponding product definition file are selectable forinstantaneous Radar operation and product generation. Please refer to chapter 3.6(Immediate Scheduler Definition) for further information.

3.1.2.6 Show Toolbox

By a click on the TOOL button a small Toolbox window opens which offers followingtools:



• RAW: Rawdata Processing Tool (chapter 3.7.1)This tool is used for offline generation of products with archived raw data files as input.

• IMG: Image Data Processing Tool (chapter 3.7.2)This tool is used for offline generation off second level products with archived productdata files as input.

• PROC: Offline Processing Tool (chapter 3.7.3)This tool is used for offline generation of products with online raw data files as input.

For further details please refer to the indicated chapters.

3.1.3 BITE Control PanelThe BITE (Built In Test Equipment) Control Panel allows the Rainbow® user ...

• to control the Radar hardware (e.g. Radar on/off),

• to review BITE messages coming from the Radar and stored in the Rainbow®

subdirectory bite.d and

• to request a BITE message whenever it is necessary to visualise the actual Radar status.

3.1.3.1 Show BITE Status Menu

By a click on the BITE STAT button the BITE Status window opens. Here, the Radarhardware can be switched on/off. Additionally the Radar status is indicated. This menuis only available in Rainbow® supervisor mode!



The window is divided into two sections. In the Command section there are "switches" to controlthe Radar directly:

Radar ... switches the Radar on/off.

Radiation ... switches the transmitter (high voltage) on/off.

Extended BITE ... activates/deactivates the extended BITE text transfer. In case thatit is switched on, additional information about the Radar system isavailable. this information can be visualised in a separate window bya click on the "Show Extended BITE Text ..." button.

The setting of these "switches" is not directly send to the Radar. To commit the status of theswitches you have to click on Send Command. Now it needs a few seconds for transmitting thesettings and receiving the answer (BITE message). If the Radar system is able to follow yoursettings (main power is connected), the corresponding "lamps" in the lower part of the windowwill indicate the new Radar status.

This Indicator section visualises the Radar status. The colour "red" indicates inactive res.incorrect status, whereas "green" indicates active / correct status. The display of a status, whichdoes not fit into those categories, is underlain "grey" (e.g. there is no line voltage generatorinstalled).

Get BITE Status refreshes the information. This button should always be used before clickingon "Send Command" to visualise the actual Radar status.

Show Extended BITE Text opens an additional window which displays the extended BITE textin case that "Extended BITE" is switched on.

Close dismisses the window.



3.1.3.2 Show BITE Review Menu

A click on the BITE REV button opens the BITE folder of the Message Logger window.This folder is used to visualise BITE messages of the past which are stored in theRainbow® subdirectory bite.d.

By means of the file select box on the right you can choose one already stored BITE file to bereviewed. The file content will be displayed similar to the "BITE Status" window. The extendedBITE information is directly displayed in a text field below the general status information, withoutrequiring a separate window.

If a postscript printer is installed as default printer, the Print button starts printing out thedisplayed BITE message for documentation requirements.

3.1.3.3 Get Current BITE Status

By a click on the BITE EXT button a request for an extended BITE is send to the Radar.After a few seconds the extended BITE message appears and can be visualised by thehelp of the BITE folder of the Message Logger window.



3.1.4 Schedule Task Control PanelThe Schedule Task Control panel enables the Rainbow® user ...

• to select a pre-defined schedule task,

• to start this task,

• to stop the running schedule task and

• to edit the pre-defined schedule tasks.

When you are not Rainbow® supervisor, you are only allowed to start the pre-defined scheduletasks!

3.1.4.1 Select Schedule Task

Select the desired schedule job by clicking on . As a default you have to choosebetween three pre-defined schedule tasks:

• Immediate

• Cyclic Loop

• Watchdog

The number and the type of the particular pre-defined schedule tasks is changeable by theRainbow® supervisor. In order to do this, please refer to part 6 (Rainbow® Configuration Files).

3.1.4.2 Start Schedule Task

By a click on the START button the selected schedule task will be started. The scheduleris send to Rainbow® Real-time, tested and activated. It starts immediately. Please referalso to the chapters 3.4 and 3.6 (Cyclic Loop - Watchdog / Immediate SchedulerDefinition).

3.1.4.3 Stop Current Schedule Task

Just press the STOP button and confirm the indicated question.



3.1.4.4 Edit Schedule Task Menu

By a click on the EDIT button the View/Edit Schedule window opens. Here you have thepossibility to modify a specific schedule task.

In order to change e.g. the first schedule job (in this case an Immediate Product Schedule) youhave to click on the PDF (Product Definition File) and the Scan PDF (Scan Definition File)section below the line 1. Immediate Product Schedule. A choice of available data sets found willgive you the possibility to exchange the PDF or Scan PDF. A click on the close button will storethe modifications.

To exchange e.g. a Cyclic Loop Schedule you have to choose the CYCLIC Loop section. Nowyou can select a new schedule task.

Keep in mind that you are only able to change the following parameters:

• Immediate product schedule taskTuneable parameters: PDF, SDF

• Cyclic loop schedule taskTuneable parameters: Cyclic loop schedule job

• Watchdog schedule taskTuneable parameters: Watchdog schedule job

The PDF's can be created using the appropriate worksheets (chapter 3.2). The SDF's can becreated by means of the scan worksheet (chapter 3.3). The schedule jobs (cyclic loop andwatchdog) can be defined using the Cyclic Loop/Watchdog worksheet (chapter 3.4).

In order to change the expression of a specific schedule task (menu entry or name section), youhave to edit an appropriate configuration file.



3.1.5 Switch to Supervisor ModeBy a click on the Lock button a dialog bow will ask for a password.

A valid password will give access to the Rainbow® supervisor mode (RSM).

The following table shall give an overview about all available features for the RSM and Rainbow®

operator mode (ROM).

Function/Facility ROM RSM

supervisor mode icon ✔ ✔

activity indicator panel ✔ ✔

product definition icon - ✔

scan definition icon - ✔

cyclic loop - watchdog scheduler definition icon - ✔

automatic generation scheduler definition icon - ✔

immediate scheduler definition icon - ✔

rawdata processing tool ✔ ✔

image data processing tool - ✔

offline processing tool - ✔

BITE status icon - ✔

BITE review icon ✔ ✔

extended BITE request ✔ ✔

modification of the scheduler selection panel - ✔

selection of a scheduler from the selection panel ✔ ✔

edit schedule job - ✔

start schedule job ✔ ✔

stop schedule job - ✔



3.2 Product DefinitionRainbow® offers a large number of different product types. The different products are sorted into5 categories: "Base", "Shear", "Hydro", "Warning" and "Forecasting" products. By clicking on thePDF button a selection box opens, showing all product types of the indicated product category(please refer to chapter 3.1.2.1). Please have in mind that new products can only be created inthe supervisor mode, otherwise the PDF button is not visible.

3.2.1 Supported Product TypesThe following list shows which standard product types are supported at the moment and whichproduct data types are assigned for these. In this context Z stands for log reflectivity in dBZ, Rfor rainfall rate in mm/h, V for velocity in m/s, W for spectral width estimate in m/s, S for shearin m/s/km, D for differential reflectivity in dB and O for other data sets:

ProductCategory

ProductZ R V W S D O

PPI - Plan Position Indicator • • • • •RHI - Range Height Indicator • • • • •MAX - Maximum Display • • • • •CAPPI - Constant Altitude PPI • • • • •PCAPPI - Pseudo CAPPI • • • • •VCUT - Vertical Cut • • • • •ETOP - Echo Top • • •

StandardMet.

Products

EBAS - Echo Base • • •VAD - Velocity Azimuth Display •VVP_1 - Volume Velocity Proc. (1) •VVP_2 - Volume Velocity Proc. (2) •UWT - Uniform Wind Technique •UWT_2 - Uniform Wind Technique (2) •VIL - Vertical Integrated Liquid •VIR - Vertical Integrated Reflectivity •CMM - Combined Moment • • •SMV - Spectrum at Maximum Velocity •SRV - Storm Relative Velocity •SWAD - Severe Weather Analysis

Display• • • •

PCP - KNMI Pseudo CAPPI •

ExtendedMet.

Products

ETH - KNMI Echo Top Height •SRI - Surface Rainfall Intensity •PAC - Precipitation Accumulation •PAL - Long Period PAC •SHR - Surface n-Hourly Rainfall •

HydroProducts

RSA - River Subcatchment Accum. •



ProductCategory

ProductZ R V W S D O

RIH - Rainfall Intensity Histogram •PRT - Point Rainfall Total • •RDS - Radial Shear •AZS - Azimuth Shear •ELS - Elevation Shear •RAS - Radial Azimuth Shear •RES - Radial Elevation Shear •3DS - 3D Shear •HZS - Horizontal Shear •

Wind ShearDetectionProducts

VCS - Vertical Shear •HHW - Hail Warning •WRN - Warning •TRK - Storm Tracking •

Warning &Forecasting

Products

RTR - Rain Tracking •SWI - Severe Weather Indicator •MBD - Microburst Detection •GUF - Gust Front Detection •MESO - Mesocyclone Detection •MESO(2) - Mesocyclon Detection (2) •SSA - Storm Structure Analysis •

PhenomenaDetectionProducts

SSA(2) - Storm Structure Analysis (2) •AviationProducts

LTB - Layer Turbulence •

UserDefinedProducts

Special user defined products, createdby the user itself with the optionalRainbow® Product Generator utility.

(•) (•) (•) (•) (•) (•) (•)

The exact specifications of the here used products can be found in Volume 2 of the Rainbow®

Operator's Manual (Product Description).

To create a product, you have to select a product type from the selection list (see figure inchapter 3.1.2.1).

Affirm your entry with a double-click on the selected product type or by using the "OK" button.A "Product Parameter Board" will now appear on the screen.



3.2.2 The Product Parameter BoardThe product parameter board is a tool to set all parameters necessary for the product generation.This refers to product and display specific parameters. By means of "Save" or "Save as" aproduct definition file (PDF) is created, which is stored in the Rainbow® subdirectory pdf.d.

A product parameter board belongs to every product type. All product parameter boards havesome aspects in common which are explained in this chapter. Please refer also Rainbow®

Operator's Manual Volume 2 - Product Description. There are all product parameter boardsindicated.

Some parameters are product specific and are therefore used only in special product parameterboards. To design the product parameter boards as clearly as possible the same boards havebeen used for similar products. Parameters which are not used on the actual board are markedwith "n/a" (not available). All other parameters are evaluated. The buttons of parameters whichcannot be modified are dimmed, that means that the characters are grey.

Every product parameter board consists of a menu which offers the following options under themenu title "Product":

Load: Any product parameter set stored in a PDF you choose can be loaded.The values for this product are entered automatically into the productparameter board and can be edited.

Save: The parameter set (corrected, if necessary) is stored in a PDF, whichhas the same name as indicated in the name field in the upper partof the parameter board. ("Save under the same name")

Save as: The parameter set (corrected, if necessary) is stored in a PDF, whichis created for this purpose. The file name is given by the user. Theuser enters the name of the PDF into the file selection box, e.g.



"MyNewProduct". The file extension, e.g. ".ppz" is automaticallyadded.

Default Parameters: The product parameters in the board are substituted by the defaultparameters of the selected product type.

Print Out: All product parameters are printed out.

Exit: Exit enables you to leave the product parameter board.

Under the menu bar you can find the product parameters. Usually you will see first a button withthe name of the product parameter and the corresponding value. A button with shadedcharacters indicates that the respective parameter cannot be modified in the actual board. A"n/a" next to this button indicates that the parameter is "not available" for this board. Values nextto buttons with shaded characters, are fixed values. Only a button with distinct charactersenables the user to configure the product parameter.

In order to enter a product parameter, you just have to mouse click the corresponding illustrationin the board. A "Selection" window appears on the screen by means of which the parameters canbe defined.

Parameters can be set via scales, on which the minimum and maximum value are alreadyentered, as well as directly via the entry field. Changes of the scale will change automatically thevalues in the entry field.

After changing the values, you can leave the window by means of the "OK" button. The enteredvalues are taken over automatically into the product parameter board. If you have entered valueswhich are beyond the permissible value range, the values will not be accepted and the previousvalues remain in the product parameter board. Thus Rainbow® prevents the input ofunreasonable values. In the case of a misentry, the window can be left via the "Cancel" buttonand the entered values are dismissed.



3.3 Scan DefinitionAntenna scan parameters as well as signal processor settings can be defined by the help of thescan worksheet. This worksheet opens by a click on the SDF button.

3.3.1 The Scan WorksheetIn the scan worksheet all parameters for scan geometry and signal processing are set. The wayraw data are recorded and stored to a polar ingest data set is defined here.

The scan worksheet is split into 3 sections:

global functions

scan settings

DSP settings



3.3.1.1 Global functions

In the upper left corner the pull down menu "File" is located. It consists of the following items.

Load: Load a previously defined parameter set into this worksheet.

Save: Save the parameter setting which is currently displayed in the scanworksheet, using the file name which is displayed besides the filemenu. ("Save under the same name")

Save as: Same as "Save", but with a new file name. Before the saving process,Rainbow performs an automatic consistency check. If aninconsistency is found, the parameter set is not saved and amessage box opens with an error description.

Default values: Reset all parameters in the scan worksheet to factory defined defaultvalues. They are the "initial" values when the worksheet is openedfirst.

Print: A hardcopy of the scan worksheet is sent to the printer.

Exit: Leave the scan worksheet without saving parameters.

Beside the file menu a display box for the file name is located. Here the name of the parameterfile currently edited in the scan worksheet is displayed.

In the upper right corner an user comment can be entered.

3.3.1.2 Scan Mode section

In this window all the parameters concerning the geometrical scanning of the antenna are set.Since Rainbow® distinguishes between 3 basic types of scan procedures, this window can beset to one of the following 3 modes:

• azimuth scan

• elevation scan

• volume scan

Selection of the type of scan is done by clicking on the "Scan mode" button over the scan modewindow.

The azimuth scan mode is mostly used for PPIs. The antenna moves in azimuth direction withone fixed elevation angle.

The elevation scan mode is used for RHI products only. In this mode the antenna moves inelevation direction with a fixed azimuth.

From ingest data sets recorded in the volume scan mode, all Rainbow® products with exceptionRHI can be generated. In this mode the antenna performs up to 20 constant elevation 360°azimuth scans.



3.3.1.3 DSP Settings Section

In this window all parameters for signal processing are set. The user has full access to most ofthe parameters. This requires good knowledge about radar operation and signal processing. Aparameter consistency check can be forced manually in order to prevent the user from enteringwrong parameter combinations. This check is also done automatically when saving a scandefinition.

3.3.2 How to Use the Scan WorksheetIn the following the scan worksheet functions are explained in detail. For some special DSPsettings the DSP manual should be used additionally.

3.3.2.1 Azimuth Scan

This scan mode is mostly used for PPIs. A constant elevation azimuth scan is performed. Thefollowing parameters can be entered into the text fields:

elevation for the scanning in azimuth direction, start and stop angle.

The azimuth step width is fixed to 1 degree.

3.3.2.2 Elevation Scan

This scan mode is used for RHI generation only. The antenna performs a scan in elevationdirection at a fixed azimuth. The following parameters can be entered into text fields:

azimuth for the scanning in elevation direction, a start angle and a stop angle and step

width.



3.3.2.3 Volume Scan

Here a volume scan consisting of up to 20 constant elevation 360° azimuth scans is defined. Theazimuth step is fixed to 1 deg. The number of elevation angles can be entered in the left textfield. On the right side there is a table displaying the elevation angle in degrees. In order tochange one elevation angle, one has to click on the respective line in the table on the right sideand then enter the new value in the text field "Selected angle". After pressing return, the newvalue is copied into the table. When a new angle has been entered, the angles above the newentry are re-calculated automatically.

3.3.2.4 DSP Settings

In the data mode section reflectivity, velocity or spectrum width data mode can be activated ordeactivated independently from each other. If activated, each of these data types is written intoone ingest data set (raw data file) of its own.

In the clutter filter section, clutter filtering in the signal processor can be enabled using one of theindicated clutter filters.



Range: A maximum range in km is entered.

Range resolution: A value in km is entered.

Range divided by range resolution is the number of values per ray transferred to Rainbow®. Thusrange must be a multiple of range resolution.

Range sampling ... specifies how many samples (1 to 8) on one ray are averaged inorder to obtain one data value.

Pulse width: It is possible to switch between long and short pulse.

Unfolding: It is possible to select "none", 2/3, 3/4 or 4/5.

PRF: The value of PRF is entered in hertz. Please note that PRF low is onlyused in case unfolding is active. PRF low is calculated automaticallywith respect to PRF high and the selected unfolding value.

Free run mode: off: The antenna speed depends on the selected values for PRF andtime sampling. In this case the entry in the text field for antennaspeed is ignored and . (option: depending on signal processor)on: The antenna speed follows exactly the value entered in the textfield "Antenna speed". The signal processor records as manysamples per ray as possible. The entry in the field "Time sampling"is calculated automatically.

Antenna speed: In case of "free run mode: on" the desired antenna speed in degreesper second can be entered. In the other case the antenna speed iscalculated automatically, depending on range, pulse width, unfoldingand time sampling.

Time sampling: In case of "free run mode: on" as many samples as possible are usedby the signal processor. The number of samples used is indicated.In case of "free run mode: off" a value bigger than 4 must be entered.Please note that increasing time sampling decreases the antennaspeed.

Res. unamb. velocity: The value for the unambiguous detectable velocity is calculatedautomatically after pressing the "Check settings" button depending onwave length, unfolding and PRF.

Check settings: Pressing the "Check settings" button initiates an automaticconsistency check of the signal processing parameters entered in theworksheet. If some values exceed the factory limits or if a wrongcombination of values is found, a small message box opens andinforms about the condition that was violated. Then the operator hasto correct the values mentioned and press "Check settings" again. Ifnecessary, this procedure must be continued until there are no errormessages.

"More" button: Opens the additional parameters window (chapter 3.3.2.5)



Table of elevation dependant signal processing parameters:

It is possible to have some signal processing parameters selectable per elevation angle in orderto obtain higher antenna speed for high elevations. A list with these elevation dependantparameters is found at the bottom of the DSP setting window.

The parameter sets entered in the text fields and menus above the list can be copied to the listusing the copy to all or copy to line button. "Copy to all" copies the parameters to all the lines ofthe list. "Copy to line" copies the parameters to only one line, which has to be selected from thetable with the mouse by clicking on it before.

Note: 1. Before copying a line to the table, a consistency check is performed automatically.

2. The highest value for range in the table must be in the lowest elevation position. Rangemay not increase with increasing elevation.

3.3.2.5 Additional parameters

By clicking on the "More" button in the standard or advanced DSP mode window, an additionalwindow opens with some additional DSP parameters.

Range Normalisation: The range dependency of the received Radar signal is for a weathertarget 1/r². To correct this effect the DSP uses a look-up table. Thestandard table is the "Default" one. But also customer specific tablesare selectable. For special maintenance validations the rangenormalisation can be switched off.

In former Radar systems where the range normalisation has been atask for the Radar receiver, STC or AGC could be selected.Nowadays this feature is unused.

CL Signal Ratio: Clutter to signal ratio threshold.

LOG Threshold: Threshold for the reflectivity channel to prevent for noise speckles.

SQI: Signal quality index.



Normally, the default threshold values work well. But in some special cases a fine-tuning of thesevalues optimises the clutter cancellation. Before changing the values please refer to thecorresponding DSP manual. The following table shows which signal processor data type will beinfluenced by which threshold.

Parameter

Threshold Z V W ZDR

LOG • •

SQI • •

CCOR • • •

Speckle Remover: Remover for isolated echoes, which cannot be a weather target.



3.4 Cyclic Loop - Watchdog Scheduler DefinitionWith the help of a "Cyclic Loop - Watchdog" scheduler you can generate a series of productsfrom a pre-set time on in a cycle of pre-set duration. Additionally you are able to interrupt thecurrently running scheduler automatically by a watchdog scheduler. You get into the inputwindow for the "Cyclic Loop - Watchdog" scheduler by a click on the LOOP button.

In the upper left corner the pull down menu "File" is located. It consists of the following items.

New Load an empty worksheet.

Open ... Load a previously defined scheduler definition into this worksheet.

Save Save the scheduler definition which is currently displayed, using thefile name which is displayed besides the file menu. ("Save under thesame name")

Save as ... Same as "Save", but with a new file name.

Print: A hardcopy of the scheduler worksheet is sent to the printer.

Exit: Leave the scheduler worksheet without saving parameters.

Beside the file menu a display box for the file name is located. Here the name of the schedulerfile currently edited in the scheduler worksheet is displayed.

The window is divided into six parts which are described in the following sections.



3.4.1 Edit ToolboxPressing this button opens the SCAN-folder (described later in this section)containing previously defined scan strategies.

Pressing this button opens the PDF-folder (described later in this section) containingpreviously defined product definitions.

Test the current scheduler definition. This means checking, and if necessary,correcting the repetition times, which is indicated by a green light instead of the red.The scheduler is not executed.

Please note: The repetition time will automatically be checked and indicated whenever a scandefinition file is added to the scheduler definition. If the calculated repetition time is less than theindicated one, the value is unchanged.

Start schedule task. This means testing and sending the scheduler to Rainbow® RT,which is indicated by a green light instead of the red. The scheduler will then beexecuted and the selected products will be generated.

Open previously defined scheduler definition. Pressing this button opens a fileselection box showing previously defined scheduler files. Chose one and press OKto load.

Save current Scheduler definition. Enter a filename in the file selection box to use forthe current scheduler definitions file. It has to have the extension ".she".

Trashcan. This field is used to throw away Scan or PDF's, which should not begenerated anymore via "Drag and Drop". Select any scan or PDF from the Base orWatchdog lists and drag them over to the trashcan. (For "drag and Drop" use themiddle mouse button)



3.4.2 Scan FolderThe Scan Folder is used to add scandefinitions to the scan lists in either theBase or Watchdog scheduler. It shows allpreviously created scan definitions. Thefirst step is to select one item from the listwhich are to be added to the scheduler.Then use either "Drag an Drop" (Press andhold the middle mouse button in the listand drag it to the scan list of the schedulerdefinition. Release mouse button.) or useone of the "Add" buttons (right mousebutton in the list shows also a selectionmenu). Chose either "Add" or "Add toWatchdog" to add the selected item to thescan lists in the scheduler definitions.

In case there are selected scans in thescheduler definition the new items areinserted above the first selected one.Otherwise they are added to the bottom ofthe list.

3.4.3 PDF FolderThe PDF folder is used to add productdefinitions to scans selected in thescheduler definitions. It shows allpreviously create product definition files.When adding PDFs to one or more scansin the scheduler definition, the first stepshould be to select one ore more PDFs inthe folder list. After that select scans in thescheduler to which the PDFs should beadded. Then use "Drag and Drop" or thelist menu to add the PDFs. They arealways inserted behind all selected scanpositions.



3.4.4 Base Scheduler Definition

The Base Scheduler Definition isdivided into three parts. The repetitiontime of the Base-Cyclic-Loop can beset in the upper part by using thearrow button next to the hour, minuteor second fields or focus to theappropriate field and enter thedesired value.

To set up the scan list (left list) openthe scan folder as described above.Select the desired scan definitions and use either "Drag and Drop"(press middle mouse button in thelist, pull it over to the scan list in thescheduler definition and release themouse button) or use the "Add"button to add definitions to thescheduler definition. The items areinserted at the end of the scan listwhen no scans in the scheduler listare selected. In case of one scanitem is selected the new one is addedabove the first selected one.

Setting up the PDF list works in asimilar way. Open the PDF folder andselect one or more PDFs in the list.

Then selected the scans in the Scheduler definition to which the PDFs should be added. Thenext step is to use either "Drag and Drop" (middle mouse button) or the list menu in the PDFfolder (right mouse button) to add the PDFs to the selected scans. When using "Drag and Drop"you can drop the PDFs either in the Scan or in the PDF list of the Scheduler definition.

To remove items from the lists select one and use either "Dragand Drop" to throw them into the trashcan or press the rightmouse button, which pops up a menu as shown in the figure tothe left and select the "Delete" option. When deleting scans, allPDFs belonging to the selected scan item are removed, too."Clearing" a list means to delete all. With "Edit" the

corresponding worksheets come up. "Show Rawdata Processing Tool" opens the RAW toolwindow.

3.4.5 Watchdog Scheduler Definition(See Base Scheduler Definition. Same functionality.)



3.4.6 Hybrid Scan SchedulingWithin the "Base Schedule" and/or"Watchdog Schedule" definitionsection it is possible to define so-called "hybrid scans".

In such a case the raw data files ofdifferent scans are merged and thecombined raw data set (hybrid) isstored in the same manner as itwould come from one "big" scan.From each single scan as well asfrom the merged raw data setdifferent products can be calculated.This enables the user to definecomplex scanning and productgeneration strategies of highflexibility.

The example above leads to the following results:

hybrid_1st_part.sca The raw data of the scan are received and stored in the archivesub-directory hybrid_1st_part.sca.d . From that data one Pseudo-CAPPI product (PCAPPI_Z_120.pcz) will be generated.

hybrid_2nd_part.sca The raw data of the scan are received and stored in the archivesub-directory hybrid_2nd_part.sca.d . No product generation startsbecause there is no product related to that scan.

<Hybrid-Scan> There is no active scanning! Only the raw data files of the first twoscans are merged to one file (first two lines in the product list) . Anew (fictive) scan definition file name is created by appending"_hybrid" to the name of the first scan in the hybrid. This fictivescan definition name is used to create the corresponding archivesub-directory hybrid_1st_part_hybrid.sca.d for the hybrid raw dataset. At last, a MAX product and an SRI are generated from themerged raw data.

SCAN_AZI_Z_400.sca The raw data of the scan are received and stored in the archivesub-directory SCAN_AZI_Z_400.sca.d as usual. From that dataone long range PPI product will be generated.

This will be repeated every 10 minutes.



There are some restrictions for defining an hybrid scan:

• Only azimuth scans and volume scans can be merged. Elevation scans cannot bemerged.

• The scans for merging have to appear in the product list in the same order as they areindicated in the scan list before.

• In general, the scan parameter settings of the different scans have to follow the samerules as they are valid for one big volume scan. (e.g. same resolution in range).

3.4.7 Start Time field

This field is used to set the start timeof the cyclic loop scheduler. Both theBase- and the Watchdog-Scans arestarted at the selected time. Use the

arrow buttons to adjust the hour, minute and second of the start time or focus to the appropriatetext field and enter a value. The "Now-Button" is used to select the current time (plus twominutes) for the scheduler start time. The time is set when either the test or send button isactivated and the corrected scheduler is received.

3.4.8 Killing a Running SchedulerBy starting a new schedule, the schedule which has been active up to this moment will bedeleted automatically. You have also the possibility to cancel the schedule actively by a mouseclick on the STOP button. An alert box will then appear on the screen, which asks you if you wantto delete the actual schedule. If you answer this question with "yes", the current schedule taskwill be deleted.



3.5 Automatic Generation Scheduler DefinitionSome Rainbow® Products types are not generated directly from polar raw data sets coming fromthe radar, but from other Cartesian Rainbow® products. They are called second level productsbecause they process the results of the so called Rainbow® base products (first level products),leading to a higher level of abstraction.

These products are:

Precipitation Accumulators (PAC) Long Time Accumulation (PAL) Rainfall Intensity Histogram (RIH) River Subcatchment Accumulation (RSA) Tracking Product (TRK) Rain Tracking Product (RTR) Automatic Warning Product (WRN)

The generation of a second level product starts immediately after the generation of the baseproduct - specified in the second level product worksheet - is completed.

The following table gives an overview of the second level product generation scheme.

Rainbow® second level product generation scheme

Define Scan / Product worksheets (base product) Product Worksheet(2nd level product)

Stored in SDF PDF PDF

Initiate Immediate / Cyclic Loop - Watchdog "AutomaticGeneration"

Signal-

Processor base

display display

2nd

Action

Scan Signal Processing

Base ProductGeneration

2nd level ProductGeneration

By a click on the AUTO button the "Automatic Product Generation" window pops up (next page).It offers the possibility to activate/deactivate the generation of all 2nd level productsindependently in one window. Additionally, the Conditional Scheduler (optional) can be definedand activated (see 3.5.3).

The next two paragraphs give some hints about the automatic generation of the second levelproducts. Since the mechanisms used for PAC, PAL, RIH and RSA are very similar, they aredescribed only once, using the PAC example. For the same reasons, Tracking and WarningProduct Generation will be explained by the example of the Tracking Product generation.



3.5.1 Automatic Generation of PAC, PAL, RIH and RSA Products(PAC example)

By means of this dialogue menu, the option"Precipitation Accumulation" can beswitched on or off using the toggle button.When clicking on PAC a file selection boxpops up, offering all existing PAC productdefinition files. for selection. After doing thesame for the SRI product selection theautomatic generation of PAC is activated.

The PAC product as well as RIH and RSA products can only be generated from existing SRIproducts. The PAL product can only be generated from existing PAC products. In order togenerate a PAC product automatically , a corresponding SRI product has to be entered into acyclic loop - watchdog scheduler or an immediate mode scheduler. After the generation of theSRI product the following happens:

• It is ensured that an automatic PAC generation is intended as described above.

• Every time a SRI product of the selected type is generated the corresponding PACproduct will be calculated.



As the PAC product is generated from an existing SRI product, it is obligatory for the automateddisplay in a display manager that the data source option in the display manager has been set to"Archive Data".

If the automatic generation of PAC products shall be stopped, it is only necessary to deactivatethe PAC generation with the toggle button. Closing the Automatic Product Generation worksheetby means of the "Apply" button, activates the actual settings immediately.

Note 1: It is important that the Radar range defined in the PAC product definition filecorresponds to the range of the selected SRI product definition files.

Note 2: Only those products are considered in the generation of PAC, PAL, RIH and RSAproducts which are in the time interval [t0 - ∆t, t0] .

Interactive Generation:

t0 (actual time) is the stop time t2 that has been selected in the "Image Processing Tool"window (please refer to chapter 3.7.2).

Automatic Generation:

t0 is the time at which the last valid SRI product has been generated.

∆t is the time span that has been selected in the PAC (PAL, RIH, RSA) worksheet

3.5.2 Automatic Generation of Warning and Tracking products(TRK example)

Step 1: Define Products

a) Definition of the input base products

Edit the product worksheets and define the product generation parameters for the input baseproducts (Radar range, dynamic range ...). If more than one input product shall be used by theTracking product, make sure that all input products have the same range. If desired, set up yourown scan strategy for the input base products.

Keep in mind that only one scan forms the basic data set for all input base products. Save theparameters selected for the input base products in a PDF (Product Definition File).

b) Definition of the Tracking product

Edit the Tracking product worksheet and enter the parameters for the Tracking product (PDFbutton -> Forecast Products -> Tracking Product). Click with the right mouse button on thefield(s) below "PDF". A file selector box will be open. Click on the input base products that werecreated in a). The field below "U" (Unit) will automatically switch to the unit of the selected inputbase product (dBZ, m/s, m/s/km). Now the segmentation parameters like operator, minimumdiameter and filling percentage can be entered. Finally, the processing and the displayparameters have to be entered. After all parameters are set, save this new parameter set in anew Tracking Product Definition File (PDF). ("File" -> "Save as ...")



Step 2 : Initiate product generation

a) Enable automatic generation of the Tracking product

Click on the AUTO button. The "AutomaticProduct Generation" window opens asexplained in chapter 3.5.1. Click on "TRK"to open the file selection box. Select theTracking PDF created in step 1 and switchTracking to on.

b) Initiate input base product generation

Set up an "Immediate" product generation or set up the "Cyclic Loop - Watchdog" scheduler. Theprocedure of setting up immediate product or schedulers is described in the correspondingparagraphs above.

Although any of these product generation schemes can be used to initiate a Tracking productgeneration, it is strongly recommended to use the "Cyclic Loop" because the Tracking productneeds a series of input products in order to work properly.

Important: Make sure that all the input base products are generated from raw data of the samescan (see paragraph c) )

c) Operation

After the generation of the input base product is started and the automatic generation is enabled,no further user interaction is required. Each time a new base product is finished, the algorithmchecks for the product type and the date and time of the corresponding raw data scan. A newTracking product generation is only started if for every input base product specified in theTracking product worksheet, a new product from the same raw data scan was generated.Therefore it is important that in the scheduler all input base products are set up to be generatedfrom the same scan. (Select the same SDF for them)

d) Archive generation for testing

For testing purposes it may be useful to generate the Tracking product from well-known existingraw data sets instead of real time data. Only slight changes have to be performed to do so. Theproduct definition step (step 1) stays unchanged. The enable procedure for the tracking productdoesn't need to be changed either. The only difference stands in the definition of the input baseproduct generation.

The required input base product specified in the Tracking product worksheet have now to begenerated from existing raw data sets stored in the archive or in the FIFO subdirectory ofRainbow®. All the input base products specified in the Tracking product worksheet must begenerated interactively using the Toolbox option RAW (Raw Data Processing Tool, chapter3.7.1). Select one raw data set and generate all the required input base products for it. After thegeneration of the last base product is finished, the generation of the Tracking product will startautomatically.



3.5.3 Conditional Scheduler DefinitionBy means of the Automatic ProductGeneration dialogue menu not only secondlevel product generation can be initiated. Itis also possible to activate/deactivate theoption Conditional Scheduler using thecorresponding toggle button. Whenclicking on Scheduler a file selection boxpops up, offering all existing schedulerdefinition files for selection.

In case of "Conditional Scheduler ON", Rainbow® is looking for the appearance of a warningcondition coming from a warning product. If there is at least one warning condition, the currentlyrunning scheduler will be replaced immediately by another scheduler, which has been selected.(here: bad_weather.wdg)

Rainbow® replaces the conditional scheduler by the previous one, if there was no more warningcondition within the time period defined in the "Switch back" section. (here: 30 minutes)

Please note that 'replacing' one scheduler by another one is the same as starting a schedulerwith the start time option "Now", which means current time plus 2 minutes.

If you want to stop a conditional scheduler before reaching the switch back time, you just haveto start a scheduler of your choice, which every time overwrites the actual scheduler. There isno need for using the STOP button of the Radar Manager before to kill the running scheduler.



3.6 Immediate Scheduler DefinitionBy means of the immediate mode you are able to request products specified by a scan andproduct definition file couple directly from the radar without having to prepare a schedule before.Any other radar operation is interrupted until the requested product is generated. You should usethis mode only, if you need special data out of turn. If you want to request a product more often,you should integrate this product into the schedule task via the supervisor mode.

You get into the immediate mode by a click on the IMM button. Then the "Immediate Mode"window appears on the screen. Click on "SDF" and select one scan definition file. Then click on"PDF" and select one product definition file.

If you press the "Start" button, the scan definition file will be sent to the radar processor and anew product will be generated. Now you can leave the "Immediate Mode" window by clicking on"Cancel". All your changes are stored and appear again in the window the next time you call theimmediate mode.

A second possibility to initiate an immediate product generation is to use the Schedule TaskControl Panel. Please refer to chapter 3.1.2.5 for further details.



3.7 ToolboxBy a click on the TOOL button a small "Toolbox" window opens which offers the following tools:

3.7.1 Raw Data Processing ToolProducts can be generated offline from archived raw data files. To open the "Raw DataProcessing Tool" window you have to click on the RAW button of the Toolbox.

With the help of the RAW tool the user is able to search for raw data files which have beenrecorded in a certain interval. This time interval can be set via the fields "...from" and "...to". Afterhaving set the interval, you have to select from the SDF list a scan definition file. Now the RAWutility searches for all raw data files created by the selected scan within the pre-set time interval.Select one raw data file that you wish to process. Then click on the desired product in the PDFlist. With Generate the product generation starts.

Generate All processes all raw data files of the "Rawdata List".



A click with the right mouse button onto a "SDF List" item offers additional functions:

Edit ... opens the corresponding Scan Worksheet.

Refresh ... actualises the SDF list entries.

Search ... actualises the "Rawdata List" entries.

The right mouse button used in the "PDF List" offers the following additional functions:

Edit ... opens the corresponding Product Parameter Board.

Refresh ... actualises the PDF list entries.

Generate ... starts the product generation (same as "Generate" button).

Generate All ... starts the product generation (same as "Generate All" button).

During the product (or multiple product) generation time you will see a message called e.g. "zfile(s) processed" in a small text field in the centre of the window. This message will automaticallyupdate appropriately the current number of the product generation process.

Please note: There are PDFs (second level products) - such as "pac", "rih" or "rsa" etc.- whichare not indicated in the PDF List. For offline generation of second level productsthe IMG tool has to be used.

Please note If you want the newly generated products to be displayed in the display manager,the option "Archive Data" has to be selected as data source. If the option "SensorData" has been set, the newly generated products will not be displayed in theDisplay Manager.

The Raw Data Processing Tool can be left with the help of the "Close" button. If you leave thewindow the actual configuration of the defined time interval is stored to be available for furtherproduct generation until you stop the Rainbow® application completely.



3.7.2 Image Data Processing ToolSome products can also be generated offline from archived image (= product) data files.These products are the so-called "second level" products which need base products(first level products) as input.

The second level products PAC and PRT need SRI product data as input, whereas the PALproduct needs PAC product data.

To open the "Image Data Processing Tool" window you have to click on the IMG button of theToolbox.

The "Search and Generate Utility" offers you the possibility to select all products of a productdefinition file of a specific acquisition interval.

At first you have to set the acquisition interval with "From" and "To". Then you choose the desiredproduct definition file from the "Input Search" file selection box and press the "Search" button.Rainbow® enters all products which have been generated in the chosen interval and whichbelong to the chosen product definition file into the "Product List".

By selecting product data files indicated in the "Product List" and clicking on the "Add" button (or"Add All" button) these files will be added to the "Selected Products" list. This list can finally beedited with the help of the "Remove" and "Remove All" buttons.

Select now the desired second level product type (PAC, PRT or PAL) from the "Select PDF" list.When you click then on the Generate button, all product data files indicated in the "SelectedProducts" list will be used as input to the second level product generation, one after the other.



The Filter buttons actualises the corresponding PDF list. "Search" and "Generate" functions arealso available by a click with the right mouse button into the "Input Search" or "Select PDF" list.

You can leave the "Image Processing Tool" by the Close button. If you leave the window theactual configuration will be stored for later calls, as long as Rainbow® is running.

The following product generation combinations are possible.

Input Search Product List Select PDF

SRI - PDF SRI Product Files PAC - PDF

SRI - PDF SRI Product Files PRT - PDF

PAC - PDF PAC Product Files PAL - PDF



3.7.3 Rainbow® Offline Processing ToolA typical operational layout for Rainbow® is to generate meteorological products on a productprocessor connected to the local area network of the radar site and / or on a product processorconnected to the local area network within the e.g. meteorological control division. The onlyrecommendation for a passive product processor is, that the connection to the main productprocessor must be fast enough to transport the raw data in convenient time.

A Rainbow® network can adapt an arbitrary number of passive product processors as long asthe bandwidth of the LAN or WAN connection is sufficient. This includes configurations withheterogeneous networks, and workstations, as the main product processor and the passiveproduct processor can be workstations of different type.

The main task of a passive product processor is to generate products, that are used mainly ata specific office or in a separate LAN, e.g. special hydrology and shear wind products.

As mentioned, the number of passive product processors within the Rainbow® network is onlylimited by the given bandwidth of the network. Rainbow® uses Standard UNIX services like ftpor rcp to transfer the volume data files to the product processors.



3.7.3.1 Configuration Files

To activate a passive product processor, be sure that ...

• On the main product processor the process "RainFTP" is in the process target list of theSupervisor Manager and marked as active.

• On the passive product processor the process "RainAcq" is in the process target list ofthe Supervisor Manager and marked as active.

• On the passive product processor the offline processing feature was licensed byGematronik.

• The configuration files “RainFTP.ini” and “RainAcq.ini” are configured.

Configuration of RainFTP on the main product processor

The configuration file for RainFTP is “$GAMPATH/init.d/RainFTP.ini”. To configure the transferof volume files to a passive product processor, add a section like in the example below. Everyvolume data set that is collected on the main product processor will then be sent to the passiveproduct processor. Rainbow® calls the shell script "$GAMPATH/bin.d/rainftp" for the actualtransfer. Please verify the execute permissions of that file if problems with the data transferoccur. The logfile “$GAMPATH/error.d/rainftpyyyymmdd.log” has an entry for each file transferthat was initiated by RainFTP. In case of a problem check this file for additional information.

# Example: $GAMPATH/rainbow.d/init.d/RainFTP.ini## Transfer of volume data from main product processor# to the passive product processor RainGen2#[RainFTP]Extension = volLabel =LabelValue =Filename =Target = RainGen2User = rainbowPassword = rain99Destpath = import.dDestname =

You are free to add more sites to this configuration file. We recommend to set the parameter“Destpath = import.d” as the destination of the volume files on the passive product processor.See the documentation of the RainFTP utility (part 5 of this manual) for a detailed descriptionof the configuration file RainFTP.ini

Configuration of RainAcq on the passive product processor

The configuration file for RainAcq is “$GAMPATH/init.d/RainAcq.ini”. RainAcq uses anautomatic poll mechanism to check for new volume files on the passive product processor. Theexample below shows, how to configure this poll mechanism for volume data:



# Example: $GAMPATH/rainbow.d/init.d/RainAcq.ini# Configuration of RainAcq on# the passive product processor RainGen2#[General]sleeptime = 5minpolltime = 5

[offline]rainbow offline processing = 1importdir = import.dtargetdir = tmp.d

The parameter rainbow offline processing determines, if the polling mechanism isinitiated when Rainbow® is started.The parameter sleeptime should be in the range of 5 to 60 seconds. RainAcq waitssleeptime seconds between subsequent pollings.If an incoming file has not been changed for minpolltime seconds, then RainAcq assumes,that the transfer is complete and the file is copied to its final destination. This parameter shouldalso be in the range from 5 to 60 seconds.

Please note: The settings in section [offline] are a "must". Don't change them!

Define products to be generated on the passive product processor

The final step is, to define which meteorological products are generated. Rainbow® distinguishesbetween two generation modes and 3 volume categories. This is configured in”$GAMPATH/init.d/ProcessOffline.ini”. The example below shows the structure of this file.

################################################################## Rainbow Offline Processing Parameters#################################################################

[OfflineProcessing]SDF = azi_z_400.scaSDF = vol_z_200.scaSDF = vol_zvw_100.sca

ReplacePDF = 1

################################################################## Each section defines a set of products for a single scan## Example## [SCAN_VOL_ZVW_100.sca]# pdf = pdf_100.rhz



# pdf = max_100.caz# pdf = max_050.cav#################################################################

[vol_zvw_100.sca]PDF = ATC_RDS_025.rdsPDF = MET_VVP2.vp2PDF=MET_MAX_Z_100.caz[vol_z_200.sca]PDF = MET_PCZ_200.pcz[azi_z_400.sca]

If ReplacePDF=0, then the PDF names will be taken directly from the raw data file header andnot from the ProcessOffline.ini file. The products generated are then the same as on the mainproduct processor. Keep in mind that using this mode, all necessary PDF's have to be copiedfrom the main product processor to the passive product processor, otherwise the correspondingproducts will not be generated.

If ReplacePDF=1, in a first step all PDF names in the raw data file header will be removed. Thenthe PDF names of the sections [xyz.sca] are added to the raw data file header. Theseproducts will be generated now, provided that the PDF's really exist.

In the example above ReplacePDF is switched on. There are three [xyz.sca] sections. Thelast one [azi_z_400.sca] does not contain a PDF name. The header of the raw data files ofthat scan will be changed in a way that all PDF entries are removed but not replaced by otherones. As a result no products are generated for that scan. This is helpful when raw data fileshave to be copied to a passive product processor without starting product generationautomatically.

The configuration file ProcessOffline.ini can be edited with an editor (e.g. emacs, vi) or with anuser interface. To start the user interface, open the toolbox of the Radar Manager with the TOOLbutton. In the toolbox press the PROC button to start the graphical interface (offline processingeditor).

3.7.3.2 Offline Processing Editor

The Offline Processing Editor is used to edit the ProcessOffline.ini file in an user-friendlyway. It opens by a click on the PROC button of the Radar Manager toolbox.

In the Type field the offline processing scheduler can be matched. When highlighting one scantype - Azimuth, Elevation or Volume - all available scan definitions (SDF's) are listed in the Filesfield. Selecting one SDF and clicking on Add button adds this SDF to the Type field. Selectingnow this SDF in the Type field results in listing all available product definitions (PDF's) in theFiles field. Selecting one PDF and clicking on Add button adds this PDF to the SDF highlightedin the Type field. These actions can be repeated until the desired offline processing scheduleris matched.

With Replace PDF's switched to on, every time a raw data file corresponding to one of theselected SDFs is received the PDF entries in the file's header will be removed and replaced bythe new defined ones. As a result (only) the products indicated in the offline processingscheduler are calculated.



The following example displays the offline processing scheduler which belongs to theProcessOffline.ini file of the previous chapter.

OK ... stores yours settings to RainbowOffline.ini file, and closes the editor window.

Restore ... reloads the settings of the last RainbowOffline.ini file.

Cancel ... closes the editor window without changing the last RainbowOffline.ini file.

Rainbow® Operator's Manual •••• Volume 1 (General Description) Display Manager

Gematronik GmbH • Rainbow® Version 3.4 • Release 4.1 (2001-02-22) 4–1

Part 4

Display Manager



Table of Contents

4 DISPLAY MANAGER .............................................................................................. 4–3

4.1 Display Manager Control Panels .............................................................................4–44.1.1 Utility Panel............................................................................................................4–44.1.2 Toolbox Panel .......................................................................................................4–64.1.3 Animation Panel ....................................................................................................4–64.1.4 Mouse Button Settings ..........................................................................................4–74.2 Display Configuration...............................................................................................4–84.2.1 Product Selection ..................................................................................................4–94.2.2 Display Size Configuration ....................................................................................4–94.3 Overlay Configuration ............................................................................................4–104.3.1 Overlay Layers ....................................................................................................4–104.3.2 Range Rings........................................................................................................4–114.3.3 Draw Parameters ................................................................................................4–124.3.4 Underlay Map ......................................................................................................4–134.4 Animation - Product Movie.....................................................................................4–154.4.1 Create Animation.................................................................................................4–154.4.2 Start/Stop Animation ...........................................................................................4–174.4.3 Animation Options ...............................................................................................4–184.5 The Orientation Utility.............................................................................................4–194.5.1 Interactive Product Generation (VCUT)..............................................................4–194.5.2 Selecting Points for RIH ......................................................................................4–204.6 The Zoom Utility ......................................................................................................4–214.6.1 The Zoom Window Configuration .......................................................................4–214.6.2 The Zoom and Histogram Window .....................................................................4–214.7 Colour Environment Selection ..............................................................................4–234.7.1 Example for a Typical Colour Map Configurations .............................................4–244.7.2 Colour Management under Xwindows ................................................................4–244.8 Loading a Product File (Offline Operation) ..........................................................4–254.9 Toolbox ....................................................................................................................4–274.9.1 ITAF - Interactive Tracking Analysis Facility .......................................................4–274.9.2 GIF - Graphics Interchange Format Tool............................................................4–294.9.3 VCS - Satellite Overlay Integration .....................................................................4–304.9.3.1 Interactive loading process............................................................................4–314.9.3.2 Automatic loading process ............................................................................4–314.9.3.3 Overlay Configuration Satellite - Radar.........................................................4–324.9.3.4 Storage Management PIF Images ................................................................4–324.9.3.5 General Remarks ..........................................................................................4–324.9.3.6 Summary .......................................................................................................4–334.9.4 2DCM - 2D Clutter Map Facility...........................................................................4–344.9.5 RC_Tool - Rainfall Classification Tool ................................................................4–35



4 Display ManagerThe Rainbow® Display Managers are independent processes that capture a selected Radarproduct file from the Rainbow® file database and generate the desired product display for theuser.

Display Managers are started and stopped in the Supervisor Manager "Display Management"menu. The operator may recall his own individual configuration when starting a Display Manager(see chapter on Supervisor Manager).

Products that are generated during Radar operation are displayed automatically (online).Products that are stored in the archive or FIFO file system can be viewed interactively (offline).



4.1 Display Manager Control PanelsThe Display Manager main window consists of three user input areas (panels) and a scrollabledrawing area window for the Rainbow® image visualisation. Within the drawing area windowdifferent mouse button settings are available.

4.1.1 Utility PanelThis panel contains a number of standard Display Manager functions.

Load Product

Opens a load dialog box, where - using some search patterns - a Rainbow® image can easilybe loaded from the data base (offline operation). For further details please refer to chapter 4.8.

Receive Sensor / Archive Data

Choose data source - sensor (=FIFO) or archive. During normal Radar operation the data sourcewill be the Radar sensor. In case of switching to "Archive Data" during online operation, newincoming products will not be displayed - the last image is "frozen".

When loading a previously stored product, with this button you can toggle between archive andFIFO file system.

Get Product Information

Shows an information window which contains the following product specific parameters of thecurrently loaded product image:



Print

Prints out the content of the Display Manager window (product image). Clicking on the Printbutton when pressing the Shift key initiates a print out of the whole Display Manager window(without window frame).

Overlay Configuration

Shows the overlay selection dialog which is explained in chapter 4.3.

Zoom Configuration

Shows the zoom options dialog which is explained in chapter 4.6.

Colour Configuration

Shows the "Change Colours" dialog which is explained in chapter 4.7.

Show Message

In case of receiving a message this icon will show a red envelope. By mouse click a windowopens displaying the message.

Fit Display Frame

By a click on this button the Display Manager window will be resized according to the imagecontent.

Switch to Supervisor Mode

By a click on the lock icon you will be asked for entering a password to switch to Supervisormode. As a supervisor you are allowed to change the "Display Configuration". By another clickon this icon you will leave supervisor mode and the "Display Configuration" button disappearsfrom the utility panel.

Display Configuration

Opens the "Display Configuration" dialog (Filter Configuration) which is explained in chapter 4.2.



Display All Products

For testing purposes it may be useful to configure the Display Manager to display any productindependently from the "Selected Products" list of the "Display Configuration". This option isenabled by switching "Filter Off". Please note that the display of all products is further influencedby the data source selection - sensor or archive.

4.1.2 Toolbox PanelThe toolbox panel offers different helpful Display Manager tools. Thesetools are optional. Which tools are available depends on the specificcustomer configuration. The following table gives an overview over allimplemented tools. For a detailed description please refer to thecorresponding chapters.

Tool Description Chapter

ITAF Interactive Tracking Analysis Facility. Contour lines of the previous Radar imageare overlaid on the actual image. By means of "arrow keys" the old contours canbe moved in a way that they fit best with the new echoes. From this manualdisplacement direction and speed of echo movement are calculated anddisplayed.

4.9.1

GIF Graphics Interchange Format. Tool for saving Rainbow® Radar image files in GIFformat.

4.9.2

VCS VCS satellite image integration. Display of PDUS/SDUS images. Simultaneousdisplay of satellite and Radar data.

4.9.3

2DCM 2D Clutter Map. Storing of a PPI(Z) image as clutter reference. Automatic cluttercorrection for PPI(Z) images using the stored clutter reference.

4.9.4

4.1.3 Animation PanelBy means of the animation panel the Rainbow® user is enabled tocreate and control the animation of Radar products. Here, only ashort description of all functions is given. For more details pleaserefer to chapter 4.4.

Create Animation

A click on this button activates the "Create Animation" dialog, where the product type can beselected.



Start/Stop Animation

Start and stop of animation replay

Step Through Animation

Show previous / next image.

Change Animation Speed

With the help of this slider the animation speed can be controlled.

Create Quick Movie

Tool for one-click animation sequence generation. Automatically the last n images of type t(currently displayed image type) will be stored to the animation sequence. The maximum numbern of animation images can be set by means of the Rainbow® configuration file DisRainMan.ini.

4.1.4 Mouse Button SettingsThe following actions are correlated to the different mouse buttons on a three button mouse.

Mouse Button Event Description

none pointer movement over display dynamic display of current cursor positionincluding angle and distance, longitude andlatitude, pixel value in the lower right corner ofthe Display Manager window.

left mouse click on image or imagelegend

By clicking on a coloured area (e.g. storm coreor legend field) the corresponding colour (level)switches to the so-called ISO colour. Thisfunction is used to highlight special levels for abetter visibility and analysis.

middle mouse click on display orientation utility, setting of start and stop pointsfor Vertical Cut product, selecting of points forRIH product.

right mouse click on display zoom function (if enabled)



4.2 Display Configuration

The Display Manager can display products and animation of products. The user decideswhich products are going to be displayed by means of the "Display Configuration" dialog.This dialog window opens by a click on the "Display Configuration" button.

The Display Configuration dialog window consists of two sections:

• the Product Selection section in the upper part and

• the Display Options section for display size configuration in the lowermost part.



4.2.1 Product SelectionIn the left part of the product selection section all defined PDF's (product definition files) arelisted. Now just select the wanted PDF and click on the Add button. The selected PDF will beintegrated immediately into the "Selected Products" list. If you use the Add All button, all PDF'savailable in the system will be selected for display. In practice only one (or maximal two) PDF(s)will be selected for each Display Manager.

With the help of the Filter button the entries in the "Files" list are updated. This is only necessarywhen a new PDF has been defined and the "Display Configuration" window was not closed.

The selection of products can be cancelled, if you choose the product definition file in the"Selected Products" list and press on the Remove or Remove All button.

When closing the "Display Configuration" window the selections are active. By meansof the "receive sensor/archive data" button you can select the data source. In normaloperation the data are coming from the Radar sensor. In this case the toggle buttonshould be switched to sensor data.

4.2.2 Display Size ConfigurationBy means of the picture size factor in the lower part of the "Display Configuration" window thesize of the displayed image can be changed within a range of 20 to 200%. The selection affectsnot only the image currently displayed, but also every image which is loaded later on. The valuein percent is entered by moving the slider. The changes take effect when the button Full Sizeis activated. Pushing the Normal Size button resets the image size to the default value (100 %).

When enlarging the image size there will be no increase in information. It is working like avariable zoom option. When a "big" image is desired this function should be used instead ofincreasing the "Picture Resolution" value in the PDF worksheet because that leads to biggerproduct data files without increasing the information content. If the information content shouldalso increase then the "Range Resolution" value in the SDF worksheet should be changed. Butthis leads to bigger raw data files. You have to decide what you want.



4.3 Overlay ConfigurationRainbow® offers you the possibility to display the products that you have created evenmore clearly with the help of overlays. You can use an unlimited number of overlaylayers. Besides, you can visualise the distance to the radar with range rings. The"Overlay" dialog window opens by clicking on the "Overlay Configuration" button.

In this window, complete overlay configurations can be read in under "Load ..." with the help ofthe file selection box. These files contain all the available overlay layers. Additionally, "RangeRings" and "Draw Parameters" can be defined by selecting the corresponding windows insteadof "Overlay".

4.3.1 Overlay LayersFirst you have to select an overlay map file from the "Load Overlay" list which opens whenclicking on "Load ...". All available layers of the loaded overlay map are listed in the "AvailableLayers" window. Each layer holds the information of lines (e.g. coastlines, borders, rivers), pointsand/or text. Select the desired layers and add them to the "Display Layers" list.

The buttons in the middle part of the window cause the following functions.

Add ... adds the selected layer to the "Display Layers" list

Add All ... adds all layers to the "Display Layers" list



Up ... moves the selected layer of the "Display Layers" list one position up.This function is used to decide which layer will be written over another.The uppermost layer in this list will be drawn on top.

Down ... moves the selected layer one position down in the "Display Layers" list.

Remove ... removes the selected layer from the "Display Layers" list.

Remove All ... clears the "Display Layers" list.

4.3.2 Range RingsIn order to visualise the distance to the radar (or any other location), range rings can be overlaidupon the displayed product. Select "Range Rings" instead of the "Overlay" window. Now rangerings can be defined as flexible as possible.

First select the maximum range for drawing range rings and the distance between rings. Thendefine the location of the legend if desired.

Normally, range rings are centred to the radar site (picture position). In special cases it is usefulto off-centre range rings (e.g. centred to an airport when the radar is located kilometres apart).Then type in longitude and latitude of the desired centre. Finally, don't forget to Enable rangerings.



4.3.3 Draw ParametersThe accuracy of the drawn overlay lines can be influenced by changing the draw parameters.Select "Draw Parameter" instead of the "Overlay" window.

Two parameters can be edited:

• "Precision" describes the maximum length of one linear part of a curve and

• "Minimal Circle Segments" is the minimum number of circle segments used for drawingcurves. The overlay contour stepping can be minimised by increasing the segmentnumber and/or decreasing the linear part length. But this will result in extendedcalculation time of the overlay data.

Finally, don't forget to click on Enable All, otherwise all overlay functions are disabled. With Okthe overlay settings will be saved and the window closes. Apply saves the settings withoutclosing the window. With Cancel you can leave this board without overwriting the old settings.



4.3.4 Underlay MapThe Display Manager allows the display of any map as underlay to the Product images using thecolour levels of the Satellite Colour area (refer to the Section 4.7 “Colour EnvironmentSelection”). The map can contain geographical or other information up to 64 different levels.

Maps containing underlay image information must be stored in the directory$GAMPATH/underlay.d . The underlay data files (e.g. Underlay1.dat) are in ASCIIformat containing a header section [Configuration] which describes size and resolution of themap as well as the radar location, and an image section [Data] containing the underlay levelinformation.

Section Label MeaningPixel_X number of columns in the map (integer)Pixel_Y number of rows in the map (integer)Radar_XRadar_Y

Radar position relative to the upper left underlay map entry(integer). The co-ordinate of the upper left segment is (0,0).

Resol_XResol_Y

east - west / north - south extension of a map segment in km(floating point)

Configuration

Map_Order North-South or South-North (default)If this label is missing the default map order "South-North" istaken and the first line corresponds to the south-most mapborder.

Data underlay level information

The [Data] section contains, line by line, the underlay information. When Map_Order=North-South the first line in the file corresponds to the north-most grid points, the last line correspondsto the south-most grid points. The data values are given (in ascending order) by the digits ‘0’ to‘9’, the characters ‘A’ to ‘Z’ and ‘a’ to ‘z’ and the characters ‘.’ (dot) and ‘+’ (plus sign). TheDisplay Manager uses the first (lowest) of the Satellite colours in case of a value ‘0’, the secondlowest colour for ‘1’, ..., the 11th colour for ‘A’, ..., the 36th colour for ‘Z’, the 37th colour for ‘a’, ...,the 62nd colour for ‘z’, the 63rd colour for ‘.’ (dot), the 64th colour for ‘+’ (plus sign).

The following example illustrates this scheme:

Example: Underlay1.dat

[Configuration]Pixel_X = 10Pixel_Y = 7Radar_X = 2Radar_Y = 4Resol_X = 25.9Resol_Y = 35.8[Data]0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghilklmnopqrstuvwxyz.+012345



Different underlay data files can be created and can be used by the Display Managersindependently. The settings, which underlay file is to be used by which Display Manager, is donein the configuration file $GAMPATH/init.d/DisRainMan.ini . In the following example,the Display Managers number 1 and 2 will use the file Underlay1.dat , the DisplayManagers number 3 and 5 will use no underlay image, and the Display Manager number 4 willuse the file GeoMap_100.dat :

Example: DisRainMan.ini

(...)

[Underlay Map]DisRainMan.1 = Underlay1.datDisRainMan.2 = Underlay1.datDisRainMan.3 =DisRainMan.4 = GeoMap_100.datDisRainMan.5 =

(...)

These settings are checked whenever a new image is displayed.



4.4 Animation - Product MovieRainbow® offers you the possibility to display products in an animation. Only products of thesame type can be used in an animation. In each of the displays one animation can be run. Theseanimations can either be created individually or automatically.

Generally you have to pay attention while preparing the animation that the display on which theanimation is supposed to run is configured correspondingly. To do this you have to select theproduct definition file of the product that shall be used in the animation.

Note: Files that have been read into the animation once, will always be displayed in theanimation unless they have been deleted. Files can be deleted manually from theanimation image list (see below for details) as well as automatically: In the case that anew image file is stored to the image list the oldest one will be deleted (FIFO principle).

4.4.1 Create AnimationIn order to create an animation, both individually (e.g. for training) or automatically, youhave to open the "Create Animation" window by clicking on the "Create Animation"button of the Display Manager animation panel. A window appears on the screen. Hereyou can select the products, which shall be used for the animation. The animationwindows consists of three different user input areas.



1) The Animation PDF (Product Definition File) area

Here you can choose different types or subclasses of Rainbow® images. Up to now you candecide between:

Rainbow® Standard image Rainbow® Polar Stereographic North image Rainbow® Polar Stereographic South image Rainbow® Gauss/UTM image

2) The Image Type Selection / Options area

By means of the Image Type Selection you have the possibility to choose either the currentlydisplayed image or an arbitrary image for the Animation PDF selection. Up to now there arethree different search options available.

• Limited time interval: Dependent on the chosen image source (FIFO or ARCHIVE) thesearch algorithm takes the currently available Image Time Stamp and loads - by meansof pressing the Apply button - all images between [timestamp;timestamp-)t] to theanimation list. The look-back time is settable by sliders up to 201 days. By means ofpressing the Ok button the animation will be created.

• Unlimited time interval: Dependent on the chosen image source (FIFO or ARCHIVE) thesearch algorithm takes all images available for this PDF type. After pressing the Applybutton you are free to edit the animation list. Due to the fact that the amount of images (n)in the animation is limited you have to reduce the number of items, because only the firstn images are loaded to the animation.

• Most recent images: To be sure to have only the most recent images available in theanimation you can choose this option and Apply. Due to the maximum number ofanimation images the list contains only the most recent n images. When starting a newDisplay Manager this option is the default setting.

Selecting Show/Edit List (see figure below) you have the possibility to remove arbitrary imagesfrom the animation. Select the image file to be removed with the left mouse button; then click onthe right mouse button. The following options are available:

Unselect All Delete Delete All

It is also possible to select more than one file with the combination <CTRL> + left mouse button.

Quick movie: Load an image (FIFO or ARCHIVE) to the Display Manager and pressCreate Animation. Select Current PDF and press OK. Now an animation movie will becreated which contains only the most recent images of that type. A second possibility isto use only the Create Quick Movie button of the animation panel.

3) General settings

Here you can define, if currently generated products from e.g. a running scheduler should bestored automatically to the animation sequence (FIFO principle). To enable this function presson Store Products to Animation and select Ok.



4.4.2 Start/Stop AnimationA sequence of products can be displayed rapidly. The selection of this display option allows avisualisation of the weather dynamics as well as a prediction of the weather development. Theproducts stored for the animation are continuously displayed as a "film".

If a new product is stored to the sequence the oldest one will be dropped (FIFO principle). Theanimation can be started or stopped at any time with the help of the corresponding animationpanel buttons ...

start animation

stop animation

show previous/next image, to step manually through the animated images whenthe animation is stopped.



4.4.3 Animation OptionsTwo animation performance features can be set using the animation panel functions ...

change animation speed, to set the time interval between twopictures.

When clicking on or the Animation Options window pops up.

The setting of the Animation Legend toggle button decides whether the image legend (colourscale) will be updated with every image in the animation (position: On) or not (position: Off)."Animation Legend Off" is the standard position because normally all images of one animationare of the same type, and therefore, there is no need for updating.

The Wait Time For Last Picture slider position influences the time period between the lastimage and the first image of the animation. It should be adjusted according to animation speedsetting.

With Apply the settings are taken and the window closes.



4.5 The Orientation UtilityTo activate the orientation utility you should first switch the zoom option on. To do this, open the"Zoom Options" dialog by a click on the "zoom configuration" button of the utility panel and clickon "Zoom On". Now you can choose with the mouse any point within the displayed product, thenyou press the middle button, if the mouse has three buttons. If the mouse has two buttons, youhave to press both buttons. Then the "Orientation Utility" window appears on the screen.

Here you will find the x- and the y-co-ordinates of the chosen point in respect to the radar (x=0,y=0), longitude and latitude of this point, the point's distance and azimuth angle to the radar.Below you find the point's corresponding parameter value in the respective colour. Whenkeeping the middle mouse button pressed and moving the mouse, the values are actualisedonline.

The window can be closed using the Close button. "Orientation" is not available for vertical cut(VCUT) and RHI products. With Print a hardcopy of this window is send to the printer.

4.5.1 Interactive Product Generation (VCUT)A vertical cut product can be created interactively from different other products (MAX, CAPPI,PCAPPI, ETOP, EBAS, SRI, VIL, VIR). To do this, you have to choose - as described above -an image point of the product. Then you press the "Set Start Cut Point" button in the "OrientationUtility" window. This means that you have pre-set the starting point for the vertical cut. Themouse cursor appears now as a pencil on the screen. Then you choose a second image point,the "Stop Cut Point". After finishing this process with the right or the centre button of your mouse, you have to affirm your entry with the "Set Stop Cut Point" button.



Now a file selection box appears on the screen from which you can select a product definitionfile belonging to the vertical cut product that will be created.

Note: 1) If the raw data origin is the archive, the display configuration has to be set to "Archive Data".

2) If the raw data origin is the FIFO, the display configuration has to be set to "Sensor Data".

If you confirm your input with the "Send" button, the PDF will be sent and the vertical analysisproduct (VCUT) will be created.

Please have in mind that the "Orientation Utility" window will be closed in case of miss-entrieslike the selection of an image point outside of the product data area. If this should be the case,just repeat your entries with the correct values. You should as well pay attention to the fact thatthe "Orientation Utility" window will also close, when a new file is read into the display manager.

Please note that interactive product generation (VCUT) as described above is not available onpassive Display Managers within a slow wide area network (WAN) configuration in order toprevent such a slow net for overloading effects.

4.5.2 Selecting Points for RIHIn combination with the RIH product, the orientation utility has an additional option for selectingthe RIH points. This additional menu can only be activated, if the current display in the displaymanager is a product file of the SRI type.

After pressing the "Select Points" button in the "Orientation" window, a further window is opened.This window offers you the possibility to select any co-ordinates from the current SRI display inthe display manager. In order to select the co-ordinates you have to move the mouse asdescribed in the "Orientation Utility" to an optional point in the display and press the right mousebutton. Then the x-co-ordinate and the y-co-ordinate are set in reference to the radar position,which is always in the centre of the display, by means of the "Add Point". The co-ordinates willbe displayed in the list in the "Selected Point" window. Thus this point has been stored in the list.

To store further points in the list, you move the mouse cursor to another point in the display andpress the right mouse button and, if desired, the "Add Point" button. Proceeding like this, you canfill the point co-ordinates list in the "Selected Point" window.

Note: The maximum number of selectable points is limited to 11 point pairs at the moment.If this maximum number of co-ordinate pairs is exceeded, an information window openswith the message "Maximum Number of Points Exceeded"

If you want to delete a point from this list, you have to select the corresponding line in the listby means of the mouse cursor and select the button "Delete Point".

If you want to delete all points from the list, you have to select the "Delete All Points" button. Inorder to store this point co-ordinates in a corresponding information file, you have to select the"Save as " button. Now a file selection box opens. Within this file selection box the user can givefile names which contains information about the co-ordinate pairs from the co-ordinates list. Thisfile name must have the extension ".dat".

After pressing the "OK" button in the file selection environment, this window closes and the fileis stored under the chosen name.



4.6 The Zoom UtilityThe zoom utility enables the user to have a closer look at the details of a product.

4.6.1 The Zoom Window ConfigurationTo be able to examine picture sections by means of the zoom, you have to activate theoption "Zoom". Click on the "Zoom Configuration" button of the Display Manager utilitypanel. A worksheet appears now on the screen which has to be used to configure thezoom and histogram in this display manager window. If you want to examine a picturesection you have to take care that the "Zoom" button is activated (Zoom On).

The Zoom Factor determines how much the section is magnified. Possible zoom factors are 2,4 and 8. To select a factor you have to click the corresponding button.

The size of the zoom target window can be set by means of the Zoom Size option. Possibleadjustments are 256 multiplied by 256 pixels, 512 multiplied by 512 pixels or 1024 multiplied by1024 pixels. To adjust the size, you have to click the respective button.

A histogram can be displayed in a zoom window in addition to a picture section. This histogramreproduces the distribution of the meteorological values within the zoomed area section. Toobtain a histogram, you have to switch the Histogram button to "On".

If you are satisfied with your input, you have to affirm with the OK button. Otherwise your inputcan be dismissed by means of the Cancel button.

4.6.2 The Zoom and Histogram WindowTo open a zoom window, you have to be sure that the zoom is activated, as described in theparagraph above. Now you have to move the mouse cursor on the picture in the display, thenpress the right mouse button and keep it pressed. A rectangle appears in the display, the size



depends on the chosen zoom factor and on the zoom size. You move the rectangle to the partof the picture that you want to examine closer. Then you have to release the mouse button. Thezoom window appears now on the screen. Corresponding to the pre-set configuration, thechosen picture section and, depending on the pre-setting, a histogram will be displayed.

With Print a hardcopy of this window is sent to a printer. The zoom window can be closed, usingthe Close button in the zoom window. The window will be closed automatically, if the zoomconfiguration has been changed or a new product file has been read in the display.



4.7 Colour Environment SelectionThe Rainbow® colour parameter board is activated by a click on the Display Managerutility panel button "Colour Configuration". The Colour Parameter Board consists of 5areas. In the first area "Colours Area", the user can select which area he wants tochange, 7 areas can be changed, which are :

Background colour Iso colour Radar picture levels Satellite picture levels Overlay colours Warning colours All colours

By selecting, for example, radar picture levels, the corresponding colour area is selected andon the left side a push button matrix appears, in this case with 15 push buttons. The user is ableto change the colour values for a special level by clicking a push button and changing the RGBsliders below the push button matrix. As mentioned above with Rainbow®, one backgroundcolour, one ISO colour, 15 radar picture colour levels, 64 satellite picture levels, 56 overlaycolour levels, 7 warning + 1 misc colour levels as well as all 256 colours are made available.

In the right upper part of the colour parameter board (colour mode) the user can decide, if hewants to work with the virtual colour maps of Rainbow® or with the standard system colour map,which however has to be configured according to the system. Usually Rainbow® runs with the



colour mode "Rainbow® colours". If there are other applications running on the system, whichaccess and change the standard colour mode, it is appropriate to use the system colour mode.

There is a file selection box in the lower part of the Colour Parameter Board. Every colourdefinition can be saved under a name plus the extension ".rgb", it can be loaded as well.

On the right, next to the file selection box, there are two options for the loading and savingprocesses. After defining his own colour map, the user may just save/load this colour map as"Rainbow® Colour Map" , which is the default setting. The save option as well as the load option"All Colours" is disabled.

In the upper middle part of the Colour Table Board there is the colour palette icon and on theright, next to it, a pull-up menu entitled "Colour Tables". If the board is called for the first time,the value in the menu is "1", this means that all changes affect the first virtual colour map. Theuser is able to click the menu and to set this value to "2". Now the user has access to a secondvirtual colour map. For example, a specific colour map can be defined as the first virtual colourmap (e.g. a shear wind colour map) and as a second colour map the user can define anothervirtual colour map e.g. for warning products.

4.7.1 Example for a Typical Colour Map ConfigurationsTask

Generation of a colour table with the colour map default file "default.rgb"; modification of the firstthree overlay colours; saving as "mycolours.rgb"

Solution

Call of "Change Colours" board by activating the "colour configuration" button. Colour modeswitch on Rainbow® colours (default). Clicking the rgb file "default.rgb" with the mouse cursorin the file selection box. Then press the "Read" button. The actual colour table of "default.rgb"is read in. By clicking the menu "Overlay colours" in "Colour area" the overlay button matrix isactivated. Select the first three overlay colours one after the other and change the colours bymeans of the sliders. Type in the new colour table name "mycolours.rgb" in the "Selection" fieldand click on "Save". By clicking on "Filter" the file selection box will be updated and the newcolour table "mycolours.rgb" appears in the list. From now on this new colour table can beloaded if desired.

4.7.2 Colour Management under XwindowsTo be able to use all functions of the colour parameter board, let us have a short introduction tothe colour strategies under X-Windows.

On conventional workstations there is usually one standard colour table with 256 entriesavailable. This means that all applications have to share one standard colour table. UnderXwindows, it is customary to define virtual colour tables and to allocate such a virtual colour tableto a specific window. Thus the user is able to use up to 256 colours within one window.

If the window is selected, the colour values on of the actual valid colour map are copied on thestandard colour map and displayed. This might affect as well the colour charts of otherapplication windows. This effect has to be tolerated, because the virtual colour map guaranteesthat there are enough colours for the applications (Of course it is possible to define a colour mapwith the same colour entries for all applications).



4.8 Loading a Product File (Offline Operation)Product files can be read directly into a display on the condition that the correspondingproduct definition file (e.g. PPI, CAPPI) has been selected before in the displayconfiguration or the "display all products" button has been pressed. In order to read ina product data file, you have to click on the "load product" button of the Display Managerutility panel. Now the load dialog window appears on the screen.

With the help of this load dialog box Radar product images can easily be loaded from the database - using some search patterns. The following search options are available:

• search by time (from ... to)

• search by product type

• search by PDF



Additionally, there are two pre-defined time filters:

• LAST n HOUR(s)By a click on this button, products within the time span [actual time; actual time -n hours]will be filtered out. These time stamps are indicated in the "from ... to" fields. The look-back time (here: n hours) is configurable. Therefore the configuration file RainbowQE.inihas to be edited (please refer to the chapter on configuration files).

• TIME FILTERA click on this button uses the "from ... to" settings as time filter. It is the same as clickingtwice on the desired product definition file in the PDF list.

If there are product files of the desired product type and time span stored in the Rainbow® filesystem, they will be indicated in the Product list. For a better readability not the original - morecryptic - file names are displayed but the date and time stamp in plain text together withadditional information about product format. These formats could be standard, projected e.g.PSTN and/or BUFR coded.

By selecting one product and pressing the Load button the product image will be displayed. Butremember, that this works only if the Display Manager has been configured for displaying thedesired product type or the "display all products" button has been pressed. Another way to loadthe product is to click twice on the product line in the Product list.

As you can see, there is no possibility in the worksheet to switch between archive and FIFO filesystem. This switching is done automatically according to the data source selection in theDisplay Manager ...

FIFO file system

archive file system

Clicking on Custom Select opens the standard file selection box. Here, the user is enabled toload product files from other file systems than FIFO or Archive (e.g. $GAMPATH/pdus.d, whereSatellite images are located).

By a click on the Close button the load dialog box closes.



4.9 ToolboxThe Display Manager toolbox offers a variety of helpful tools.

4.9.1 ITAF - Interactive Tracking Analysis FacilityThe Rainbow® Interactive Tracking Analysis Facility allows interactive tracking of significant echo areas.

Using the last product's data of the same type as theone currently displayed, the outer contour of thesignificant echo areas, which can be determined by athreshold, can be extracted and dynamically visualised.The threshold is used to determine which areas of theprevious picture are significant and which are not.These contours are displayed as an overlay image overthe currently displayed picture. Using the arrow buttonsin the window, this overlay image can be moved to bestfit the current picture. The result of this action is thevelocity and the direction of the movement. The timedifference is determined from the last and the currentproduct.

The window which is used to control the interactivetracking contains several fields which have thefollowing meaning:

TYPEThis list box is used to select one of the availableproduct types. The available product types are PPI (Z,R), CAPPI (Z, R), MAX (Z, R), ECHO TOP (Z, R) andECHO BASE (Z, R).

PDFThe PDF list box can be used to select the appropriateproduct definition file. All available product definitionfiles will be displayed in the list.

FILEA Rainbow® product can be chosen using this list. Nofile names will be displayed but rather the date and timestamps of the corresponding product file.

MIN DIFFThe three numbers in this box represent the minimumtime difference between the currently displayed imageand the image which is used to generate the overlaycontour image form.

Threshold SliderThe slider box just below the MIN DIFF field is used to adjust the threshold value on which thegeneration of the overlay contour image is based. Left of the slider, there is a coloured squarewhich shows the colour of the threshold. Move the mouse pointer over this square and press and



hold the left mouse button will highlight the threshold areas in the display which allows to betterdetermine the desired threshold value.

Arrow ButtonsIn the middle of the window, the arrow buttons for moving the overlay contour image are located.The blue button will re-centre the overlay contour image over the display image. The otherbuttons will move the overlay contour image in the corresponding direction. Clicking on onebutton of the inner circle will move the image slowly while clicking on the outer buttons will movethe image in greater steps. However, the size of the steps in which the image will move isconfigurable. For information on how to configure these settings, please refer to the chapter"Configuration File Management".

PRIMARY FILEThe primary file field shows the file name of the image which is currently displayed. The three-letter file extensions indicates the product type. In the case of the example picture above, it is.caz, i.e. MAX (Z).

SECONDARY FILEThe secondary file is the file name of the image which is used to create the overlay contourimage. Hence, it is the older of the two files.

TIME DIFFThis field shows the real time difference between the current image and the last image. Hence,the time difference shown is always greater or equal to the minimum time difference which canbe adjusted in the field labelled MIN DIFF.

DISTANCEThis box shows the physical distance between the current image and the overlay contour image.The unit used here is kilometres (km). The contents of this field changes with every movementmade using the arrow buttons accordingly.

ANGLEThis box displays the angle between a relative movement to north, which is represented by anangle of zero and the current displacement of the overlay contour image. The displayed valuewill change with every movement of the contour overlay image. The unit used in this field isdegree.

VELOCITYThis field shows the average velocity of the movement during the selected period of time, i.e.between the overlay contour image and the current image.

DONE

Clicking on done will simply exit the window.



4.9.2 GIF - Graphics Interchange Format ToolGIF is a tool for automatically converting Rainbow® product images into GIF format. It hasaccess to all Rainbow® product images. Selecting "GIF" in the tool's pulldown menu opens the"GIF Tools" dialog window.

The GIF tool can operate online and offline:

Offline mode In offline mode the operator can load a product into the Display Manager and thensave it as a GIF file.

Online mode In online mode GIF tool can be configured to automatically convert every newproduct - displayed in the Display Manager - and to save it as a GIF file. In thismode the AutoSave option must be enabled.

Button Function Mode

Save image as GIF Only the image part of the Display Manager is saved as GIF. offline

Save display as GIF The content of the complete Display Manager is saved as GIF. offline

Auto save GIF image When switched on, every new incoming product is saved as GIFautomatically. Additionally it is possible to disseminate these GIFimages online by the help of the Rainbow® utility RainFTP.

online

Send To MetWindows When switched on, every new incoming product is send to aMetWindows PC automatically.

online

The GIF files are stored in the Rainbow® subdirectory gif.d .

By a click on the Close button the actual settings will be activated and the window closes.



4.9.3 VCS - Satellite Overlay IntegrationWith Rainbow® it is possible to read in PIF coded satellite images. To do so the Rainbow®

workstation system has to be connected to a VCS-VAX system by means of an Ethernetcomponent. The software on VCS side (VAX-SAT) generates processed image files (PIF) andsaves them by means of FTP (file transfer protocol) in the Rainbow® data base system. Thefollowing PIF coded images can be read in:

• PDUS images (primary data user station)

• SDUS images (secondary data user station)

• MDD charts (meteorological data distribution)

• Overlay pictures (like PDUS image but resolution 800X800 pixel/ 800X800km / polarstereographic North projection)

The PIF images are divided into different function codes depending on the displayed dynamicrange. Rainbow® can read the following function codes (refer also to the VCS documentationmanual "Structure of Image Files", September 1993):

function code 0 function code 2 function code 3 function code 12 function code 32 function code 8 function code 9 function code 18 function code 38 function code 19 function code 20

The PIF satellite images are copiedautomatically by the VAX-SAT software into thefollowing subdirectories of Rainbow®:

• PDUS images: .../pdus.d

• SDUS images: .../sdus.d

• MDD charts: .../mdd.d

• OVERLAY images: .../ovl.d

There are two possibilities for loading a PIFcoded image which are the interactive loadingprocess and the automatic loading process. Byactivating the VCS tool the "VCS Tools" dialogwindow opens.



4.9.3.1 Interactive loading process

The PIF image is loaded just like every Rainbow® product image via a file selection box, whichopens by a click on the "Load satellite image" button. The user has to change to the respectivedirectory (.../pdus.d, .../sdus.d, .../ovl.d, .../mdd.d) and to select the desired file.

By means of selecting a PIF file name and pressing the "Info" button in the file selection box, theuser gets further information about the satellite image:

date and time of the image source or origin of the image data function code (see VCS manual) pixel resolution of image

By pressing the "OK" button the selected image is loaded into the display manager.

4.9.3.2 Automatic loading process

Furthermore it is possible to load PIF images by means of the other buttons of the "VCS Tools"dialog:

• Overlay on/of

• Legend on/off

• PDUS icon

• SDUS icon

• MDD charts icon

• OVERLAY PIF icon

• Options (Overlay 0 ... 2)

• Close button

Pressing the icon "P" (PDUS) the last PDUS image transferred by the VAX-SAT software issearched and loaded into the display manager. This applies also for the icons "S" (SDUS), "M"(MDD) and "O" (Overlay PDUS).

By actuating the "Legend" button in the next loading process a legend is displayed automaticallyin addition to the PIF image. This legend presents more information about the loaded image(date, time, source, data function, pixel resolution, name of PIF image (see VCS manual). Byusing the "Close" button of the PIF legend, the legend closes and will be activated during thenext loading process of a PIF image. If the legend button of the PIF pull down menu is pressedagain, this feature can be deactivated.

By means of selecting the "Overlay" icon the radar satellite overlay mode is activated. Thismeans that a satellite image is underlaid automatically to every Rainbow® product of thehorizontal cut type (CAPPI). The radar image is converted in polar stereographic North andprojected into the centre of the satellite image. The product image used for the radar satelliteoverlay can be loaded actively by means of the "File load" function from the archive or the FIFO.The horizontal cut product can also be generated from a scheduler and be loaded automaticallyin the display manager.



If a scheduler is running which generates and displays a horizontal cut product every 10 minutes,the satellite radar overlay is generated, if the option "Overlay" has been activated. The mostactual PDUS overlay image is selected automatically for the satellite image. This means that ifthe VAX-SAT software provides the Rainbow® workstation regularly with PDUS overlay imagesand if a scheduler is running additionally on the Rainbow® workstation, which generatesHorizontal Cut products, the most actual Horizontal Cut product will be displayed automaticallywith the most actual PDUS overlay satellite image. In order to stop the overlay function theoverlay button in the PIF pull down menu has to be pressed again.

4.9.3.3 Overlay Configuration Satellite - Radar

The user can select three overlay options (political borders, rivers and coasts). By switching thetoggle buttons to "on" the overlay information of the satellite image is displayed additionally tothe radar image the in the satellite radar overlay mode. This means that the user is able to seeonly the radar image or to see the radar image and the overlay information covered/masked bythe projection.

4.9.3.4 Storage Management PIF Images

As a scheduler of the VAX-SAT software copies continuously PIF images into the Rainbow® database, it happens of course that the storage capacity of the Rainbow® data base is exhausted.Therefore the maximum number of PIF images (PDUS, SDUS, MDD or Overlay) which is storedis ten. If this maximum number has been stored, the oldest image is deleted according to theFIFO principle and the most actual image is stored.

4.9.3.5 General Remarks

• PIF images can of course be loaded into the animation.

• It is not possible with this version to load radar satellite overlay images into the animation.



• The zoom utility of the Display Manager can be used for the PIF images and the radarsatellite overlay images.

• The orientation utility is deactivated in the PIF and the radar satellite image mode.

• Functions like turn, magnify, reduce can be applied for PIF images.

4.9.3.6 Summary

• PIF image storagePIF images are stored automatically via the file transfer protocol by the VAX-SATsoftware into the corresponding directories of the Rainbow® data base (PDUS directorypdus.d, SDUS directory sdus.d, MDD directory mdd.d, overlay images directory ovl.d).These directories are on the same level as archive or fifo.d.

• Interactive loading processBy the selection of "Load satellite image" in the "VCS Tool" dialog a file selection boxopens. The user can change by means of a double-click to the respective directory (e.g.pdus.d). By clicking a PIF file name and pressing the "OK" button the satellite image isloaded. By clicking the PIF file name and pressing the "Info" button an informationwindow opens.

• Automatic loading processA click on "P" loads the last PDUS image, a click on "S" loads the last SDUS image, aclick on "M" respectively "O" loads the corresponding images. The overlay mode isactivated by clicking the option "Overlay on". The legend is activated by pressing the"Legend" button.

• Example for a radar satellite overlayIn the "VCS Tool" dialog the option "Overlay" has to be toggled from "Off" to "On". Then ahorizontal cut Z product has to be loaded by means of "File load" in the display manager(please have in mind that the corresponding PDF for the horizontal cut product has to bein the display configuration PDF list). By means of the loading process the satellite modeis activated.



4.9.4 2DCM - 2D Clutter Map FacilityPPI (Z) products can be stored from the display manager as clutter files. The usage of filesstored as clutter files allows the elimination of reflections from stationary objects like buildings,hills, trees or other obstacles from the presentation of a product.

Activating the "DCM Tool" opens the "2D Clutter MapTools" dialog window.

A product file (during clear air) can be stored as a clutter map by selecting the option "Save as2D clutter map". To achieve this, there has to be a visible product in the display. This functionis currently enabled only for PPI (reflectivity) products.

When activating "Process 2D clutter map" the previously stored PPI(Z) clutter map will be usedto correct automatically all further PPI(Z) products by subtracting the stored clutter map valuesfrom the image data.

With a click on Close the window closes and the settings are active.



4.9.5 RC_Tool - Rainfall Classification ToolNormally, rainfall intensity products (e.g. SRI) are displayed in the same way as all otherstandard Rainbow® products. The display parameter "displayed dynamic range" has beendefined in the PDF worksheet as well as the parameters a and b of the Z/R relationship. This isa restriction in flexibility, especially if the user wants to change the Z/R relationship from time totime. Additionally, the standard intensity scale is a linear one, which leads to a bad resolutionat lower intensity levels.

With the help of the RC_Tool different user-defined Z/R relationships and intensity scales canbe selected online in the Display Manager, which leads to a very high degree in flexibility. Whenactivating the RC_Tool a dialog window opens with the only option (for the moment) "RainfallClassification".

The window consists of two lists:

• Rain Class ZR - Relation: User-defined Z/R relations are listed by name. The names arealso given by the user.

• Rainfall Intensity levels: Different user-defined intensity scales can be selected by theirname.

So it is easily possible to select different combinations of Z/R relation and intensity scale for e.g.different seasons.

To get the RC_Tool settings working there are two actions necessary:

• The user has to define own Z/R relations and intensity scales by means of the Rainbow®

utility "RainNetconf".

• Because it is now a task of the Display Manager to calculate rain intensities R from theoriginal reflectivity data Z and to divide them into the 15 user-defined classes, the productdata file must include the original Z data in 8 bit resolution. Therefore, in the PDFworksheet the "Format" parameter has to be set to "Full Resolution Image" (except for



the SRI product because this is "Full Resolution" by default). In case that "FullResolution" is not selected, there will appear a warning message in the Radar Managerand the rainfall data are displayed in standard format (linear colour scale).

In a last step Enable All has to be activated. With Ok the settings are taken and the windowcloses.

Rainbow® Operator's Manual •••• Volume 1 (General Description) Rainbow® Utilities


Part 5

Rainbow® Utilities



Table of Contents

5 RAINBOW®

UTILITIES............................................................................................ 5–4

5.1 RainGorn - BUFR94 Conversion Utility...................................................................5–45.1.1 Features ................................................................................................................5–45.1.2 Usage ....................................................................................................................5–45.1.3 Installation and Configuration ...............................................................................5–55.1.4 BUFR Descriptors used by Rainbow®...................................................................5–65.2 RainAdmin - Administration Utility........................................................................5–105.2.1 Emergency Data Deleting ...................................................................................5–105.2.2 General Raw Data FIFO .....................................................................................5–105.2.3 RainAdmin Error Messages ................................................................................5–115.3 RainLog - Message Logger ....................................................................................5–125.3.1 Messages Folder.................................................................................................5–125.3.2 Errors Folder........................................................................................................5–125.3.3 Configuration Folder............................................................................................5–135.3.4 BITE Folder .........................................................................................................5–145.3.5 Alarm Folder ........................................................................................................5–155.4 RainAutoCal - Autocalibration Utility ....................................................................5–175.4.1 System Start ........................................................................................................5–175.4.2 Automatic Calibration ..........................................................................................5–175.4.3 Calibration Intervals.............................................................................................5–175.4.4 User Commands .................................................................................................5–185.4.4.1 AutoCal_Stop Command...............................................................................5–185.4.4.2 AutoCal_Start Command ..............................................................................5–185.4.4.3 AutoCal_Status Command............................................................................5–195.4.4.4 AutoCal_New Command...............................................................................5–195.4.5 Total Shutdown ...................................................................................................5–195.4.6 Setting the RainAutoCal Parameters ..................................................................5–205.4.6.1 RainAutoCal.cfg File......................................................................................5–205.4.6.2 RainAutoCalLimits.cfg File ............................................................................5–225.5 RainStore - Automatic Storage Utility...................................................................5–235.5.1 Starting RainStore ...............................................................................................5–235.5.2 Storage Configuration Board ..............................................................................5–245.5.3 Storage Messages Window ................................................................................5–255.6 Backup - Backup Shell Script Utility.....................................................................5–265.6.1 Backup Utility Screen ..........................................................................................5–265.6.2 Backup Utility Commands ...................................................................................5–265.7 BBC - Bright Band Correction Pre-processing Utility.........................................5–285.7.1 Bright Band Detection Algorithm.........................................................................5–295.7.2 Bright Band Verification Steps ............................................................................5–315.7.3 Bright Band Correction Algorithm .......................................................................5–335.7.4 Illustrations ..........................................................................................................5–345.7.4.1 Variation of Radar reflectivity with height effected by BB .............................5–345.7.4.2 Demonstration of the efficiency of the BBC algorithm ..................................5–355.7.5 The BBC Configuration File ................................................................................5–375.7.6 References ..........................................................................................................5–375.8 rain_cmd - Rainbow® Command Line Utility........................................................5–38



5.9 RainNordrad - NORDRAD Conversion Utility.......................................................5–395.9.1 Features and Usage............................................................................................5–395.9.2 Installation and Configuration .............................................................................5–395.9.3 Configurations of RainNordrad.ini.......................................................................5–405.9.4 NORDRAD Attributes Supported by Rainbow® ..................................................5–445.9.5 Error Handling Steps...........................................................................................5–455.9.6 Visualization of NORDRAD Files in the Display Manager..................................5–465.10 RainCron - Timed Rainbow® Jobs .......................................................................5–475.10.1 General Features...............................................................................................5–475.10.2 Configuration File ..............................................................................................5–475.11 FTP Dissemination Utility .....................................................................................5–50



5 Rainbow® Utilities

5.1 RainGorn - BUFR94 Conversion Utility

5.1.1 FeaturesRainGorn converts Rainbow®-formatted product files to BUFR94 format. Currently the followingproduct types are supported:

PPI(R,Z) CAPPI(R,Z) Pseudo-CAPPI(R,Z) SRI VVP(2)

The timestamp for BUFR encoding is in UTC.

RainGorn interfaces with the GORN BUFR-encoding/decoding software version 1.7 and 1.84(encbufr / decbufr). An encbufr / decbufr upgrade can be done independent from RainGorn.

RainGorn can be configured to add a GTS-header to the beginning of the file.

Rainbow® can be configured to transmit all BUFR-encoded product files to a GTS server via ftp.For automatic distribution see "FTP Dissemination Utility".

5.1.2 UsageBUFR-conversion is enabled in the ‘Format’ section of the PDF - worksheet. Two differentselections are presented:

BUFR 94 - 4 bit based: The BUFR file is filled from the 4 bit data section of the Rainbow®

product file. The data section and the Z (respectively R) levels are read from the product file andwritten to the BUFR file without any change. In consequence the data in the BUFR file has 15equidistant data levels plus one level for NO_DATA. Please note that in case of reflectivity datathe maximum range for BUFR encoding is limited by -64 ≤ dBZ ≤ 63 (WMO, Manual on Codes).This has to be taken into account when defining products (PDF work sheet)!

BUFR 94 - 8 bit based: In case of a rainfall intensity product the BUFR file is filled from the 8bit data section of the Rainbow® product file. This 8 bit section contains Z data (in units of dBZ)and it is re-scaled to 4 bit R values by RainGorn. The Z-R relation and the limits of the levelscome from the [RC_Tool] section of the RainGorn.ini file (located in init.d).

## RainGorn.ini# Contains configurations for the RainGorn process## section [RC_Tool] contains the rainfall classification for the# BUFR conversion of 8bt R products.[RClass]NumZR = 1ZR_1 = 300.0 1.5 BUFR_1NumLevel = 1Lev_1 = 0.1 0.3 0.5 1.0 3.0 5.0 10.0 15.0 20.0 25.0 30.0 40.050.0 75.0 100.0 BUFR_1



RainGorn reads the first entry from the list of Rainfall classifications (ZR_1 and Lev_1definitions). If either the ZR relation or the Rainfall classes are missing, then a default scale isused and an information message is sent to the Radar Manager:

Default Z-R relation: A = 200 B = 1.6

Default Rainfall classes: 0.1 0.3 0.5 1.0 3.05.0 10.0 15.0 20.0 25.030.0 40.0 50.0 75.0 100.0 mm/h

Whenever a BUFR file is generated, two files can be found in the product directory: TheRainbow® product file with the appropriate extension (e.g. nnn.ppr in case of a PPI(R) productand the BUFR-encoded file with an additional extension “buf” (e.g. nnn.buf.ppr in case of aBUFR encoded PPI(R) file).

5.1.3 Installation and ConfigurationThe binary files for BUFR conversion are located in the directory $GAMPATH/bin.d .

encbufr executable for conversion from intermediate format to BUFR format. encbufris called automatically by RainGorn during the conversion process.

decbufr executable for conversion from BUFR to intermediate format. decbufr is notneeded for BUFR encoding, but e.g. the Display Manager needs thisexecutable to decode a BUFR file before displaying it.

The following ASCII files are located in $GAMPATH/bufr.d/ .

descr.txt This ASCII file holds a set of BUFR descriptors provided by the GORN grouptogether with encbufr/decbufr. It is used by encbufr and decbufr. This file hasbeen defined by GORN group and, therefore, may not be changed.

LOCATION.gts configuration file for the GTS header. Since each radar location has its ownGTS header, there must be one GTS header configuration file for each radarlocation. The name corresponds to the location and has the extension ".gts",e.g. "Shannon.gts". The location name has to be the same as indicated in theheader (label H8) of the product data file. It is configured in the Radar ControlProcessor (RCP).

PAIE41 EIDB #GTS header (time is added automatically)

The file consists of two strings separated by at least one space:PABBii CCCC.These strings together with the international date-time-group (format YYGGgg,created by Rainbow®) are copied to the beginning of the BUFR-encoded file.

LOCATION.sta configuration file for BUFR descriptors related to the radar station. WMOstation number and other parameters can be configured here. Each radarlocation has its own "*.sta" file, e.g. Shannon.sta.

0 0 1 6 # data cathegory 6 = radar0 1 1 0 # WMO block number0 1 2 0 # WMO_station (Shannon)0 1 4 0 # WMO_subarea0 1 3 0 # WMO_region0 2 1 2 # Type_station 2 = manned+automatic0 2 3 3 # usType_meas_equip 3=radar



0 2 101 0 # usType_antenna: 0=centre front fed parabol0 2 103 1 # usType_radome 1= radar antenna with radome0 2 104 0 # usAnten_polariz 0=horizontal0 2 121 5600000000 # mean frequency0 7 1 200 # ulStatHeight to be corrected later0 25 4 1 # koherent =1 incoherent =00 25 9 2 # Calibration method: 2= target or signal0 25 12 1 # Range attenuation correction 1=Software

5.1.4 BUFR Descriptors used by Rainbow®

StationParameter:

/* class 01 - Identification: */

(0, 1, 1) usWMO_block WMO block number

(0, 1, 2) WMO_station

(0, 1, 4) WMO_subarea

(0, 1, 3) WMO_region

/* class 02 - Instrumentation: */

(0, 2, 1) Type_station

(0, 2, 3) usType_meas_equip

(0, 2, 101) usType_antenna

(0, 2, 103) usType_radome

(0, 2, 104) usAnten_polariz

(0, 2, 121) mean frequency

/* class 07 - Location (vertical): */

(0, 7, 1) ulStatHeight

/* class 25 - Processing information: */

(0, 25, 4) coherent =1 incoherent =0

(0, 25, 9) Calibration method: 2= calibration target or signal



(0, 25, 12) Range attenuation correction 1=Software

RadarParameter (including pre-processing):

/* class 02 - Instrumentation: */

(0, 2, 125) dPRF[n]


(0, 25, 2 ) dGateAve/* Number of gates averaged: */

(0, 25, 3 ) dTimeSample/* Number of integrated pulses: */

(0, 25, 11) Ground occultation correction: 0= none, 1= Map of correction factors, 2=interpolation

(0, 25, 13) Bright-band correction (only if active) 1=yes

(0, 25, 17) Precipitation attenuation correction (only if active) 1=yes

RadarImage:

/* class 05 - Location (horizontal - 1): */

(0, 5, 1) dRadLocX (Latitude)

(0, 5, 33) dGateLen (PixelSize on horizontal-1)

/* class 06 - Location (horizontal - 2): */

(0, 6, 1) dRadLocY (longitude)

(0, 6, 33) dGateLen (pixelsize on horizontal -2)

/* class 21 Radar data */

(0, 21, 1) horizontal reflectivity (only for Z-PD)

(0, 21, 36) Radar Rainfall intensity (only for R-PD) (mm/h-1 non WMO)

(0, 21, 14) Doppler mean velocity radial (only for V-PD)

(0, 21, 17) Doppler velocity spectral width (only for W-PD)

(0, 21, 31) Vertical integrated liquid water (only for VIL-PD)



/* class 29 Map data */

(0, 29, 1) Projection type: (no value for Gauss projection)

/* class 30 Image */

(0, 30, 21) nNumPixRow horizontally (non WMO !)

(0, 30, 22) nNumPixCol vertically (non WMO !)

/* macros */

(3, 13, 10) Radar rainfall intensity

(3, 13, 9) Radar reflectivity

RainfallImage:


(0, 25, 6) ZH to R conversion (only for R-PD)

(0, 25, 7) ZH to R conversion factor (only for R-PD) (non WMO !)

(0, 25, 8) ZH to R conversion exponent (only for R-PD) (non WMO !)

ProductParameter (general):

/* class 04 - Location time: macros */

(3, 1, 11) date

(3, 1, 12) time


(0, 25, 20) Mean-speed estimation: 1=pulse-pair processing (only Doppler)

/* class 30 Image */

(0, 30, 31) Picture Type



ProductParameter (PD-specific):

/* class 07 - Location (vertical): */

(0, 7, 2) Height or Altitude in m (only CAPPI HCUT)

(0, 7, 21) Elevation (only PPI-PD)



5.2 RainAdmin - Administration UtilityRainAdmin is an utility for the Rainbow® system, which guarantees the operational functionalityof the system.

5.2.1 Emergency Data DeletingIf the option "Emergency data deleting" has been activated, the message "Emergency datadeleting active" appears in the Supervision MMI while running up the Rainbow® system. Thisfunction is necessary to guarantee the unproblematic operation of the Rainbow® system, evenwith an almost full harddisk.

RainAdmin checks the remaining storage capacity of the harddisk. Depending on the storagecapacity, RainAdmin displays the following messages:

• "File system is o.k. ( x% remaining)"This message indicates that the storage capacity of the harddisk is sufficient. Theoperation of Rainbow® is guaranteed.

• "File system is nearly full (x% remaining)"This message indicates that the storage capacity of the harddisk is almost exhausted.Now it's time to save important data from the harddisk in order to have enough storagecapacity for the Rainbow® software. If this is not done, Rainbow® will delete some datawithin the next warning level.

• "File system is full (x% remaining)"This message indicates that the file system is too full according to the followingconfigured values to guarantee the operation of Rainbow® (for more details please referto the configuration manual). Therefore data will be deleted automatically from harddiskby RainAdmin. First, RainAdmin deletes data from the FIFO. All files older than aconfigurable value will be deleted. For the exact configuration please refer to theconfiguration manual. If this should not be sufficient and the storage capacity of theharddisk is still decreasing, RainAdmin will also delete old files from the archive (the"age" of the files which shall be deleted and the storage capacity degree of the harddiskwhich activates this deletion process can be configured. For the exact values please referto the configuration manual).

The following message appears on the supervision MMI, after RainAdmin has deleted data fromharddisk:

• "Try to gain space on file system (x files removed from archive)" or

• "Try to gain space on file system (x files removed from FIFO)".

Then RainAdmin displays the current filling degree of the harddisk.

5.2.2 General Raw Data FIFOIf the general raw data FIFO has been activated, the following message appears in thesupervision MMI while running up the Rainbow® system: "General raw data FIFO active". For theconfiguration of the general raw data FIFO please refer to the configuration manual.



The general raw data FIFO is a functionality of RainAdmin which effects the automatic deletionof raw data sets which are older than a configurable value from harddisk. The raw data sets(data sets with the extension ".vol") are deleted without taking into account their location (archiveor FIFO). If this function has been activated by RainAdmin, the following message appears inthe supervision MMI:

• "Raw data FIFO:x files removed".

5.2.3 RainAdmin Error MessagesThere are two error messages:

• "Couldn't get file system status!"RainAdmin could not establish the status of your file system. This might indicate adefective harddisk or a wrong write/read authorisation for the user Rainbow®. Pleasecheck your harddisk resp. the write/read authorisation.

• "No administration configuration -> administration functions deactivated"RainAdmin could not find the configuration file for the administration process. Possiblereasons:

The write/read authorizations for the directory init.d have not been set. The configuration file for RainAdmin has been deleted accidentally.

If this message appears, either a new configuration file has to be generated or thewrite/read authorisations for the init.d directory have to be set in such a way that the userRainbow® has access to the directory init.d. As long as the configuration file does not exist,all delete functions are deactivated by RainAdmin.



5.3 RainLog - Message LoggerThe Rainbow® RainLog process captures all messages of the Rainbow/Unix environment. Thesemessages are filed to Rainbow.log file which is located in the subdirectory error.d . Butthere is also a visualisation of all messages. Additionally, alarm conditions can be configured.

The different functions of the Message Logger are organised in "folders".

5.3.1 Messages FolderAll messages - those which are generated by the Rainbow® application itself as well as thosewhich are related the UNIX environment - will be displayed in the Messages folder.

Each message line consists of ...

date/time stamp message type: info (green), warning (yellow) or error (red) process name, producing the message text of message (self-explaining)

Depending on the settings of the Configuration folder messages can be filtered for display bymessage type and origin (Rainbow® process).

5.3.2 Errors FolderThe Errors folder looks like the general Messages folder described above. But here, all the timeall messages of type "Error" will be displayed, independently of the settings in the Configurationfolder. This is for visualisation of the important Error messages in compact form.



5.3.3 Configuration FolderMessage type as well as message source (Rainbow® process name) can be selected for display.Additionally, the number of message lines of the Messages folder can be configured.

Please note: All messages are logged to ../error.d/Rainbow.log file, independent of thesettings in the Configuration folder. Therefore, nothing is lost and all messages can be reviewedwith the help of a standard editor.

Save ... stores the settings to init.d/RainLog.ini.

Default ... loads the default settings (all switches set to "on").

Restore ... restores the previous settings, stored in init.d/RainLog.ini.



5.3.4 BITE FolderThe BITE folder is used to visualise BITE messages of the past which are stored in theRainbow® subdirectory bite.d .window pops up. By means of the file select box you canchose one already stored BITE file to be reviewed.

This window starts automatically by clicking twice on a BITE message line in the Messagesfolder as well as by clicking on the "BITE REV" button of the Radar Manager.

Refresh ... updates the BITE message list.

Print ... starts printing out the displayed BITE message in case that a postscript printeris installed as default printer.



5.3.5 Alarm FolderIn principal the Alarm part of the Message Logger application is looking for Rainbow® messagesfulfilling the desired alarm conditions.

Alarm Condition Filter

Message Type All, Error, Info or Warning messages.

Name of Process All, or one of the installed Rainbow® processes.

Message Text All, or part of the message text will be used as filter condition. If there isnothing written the message text is not used for filtering.

If an alarm occurs user-defined actions will take place.

Actions to Take Meaning

Audible Alarm The selected "wav" file (e.g. jingle.wav) will be executed. Thesefiles have to be placed into the directory sound.d.

Visual Alarm A Messages window pops up displaying the message text together withdate and time stamp of the message.

Execute Script The selected script (e.g. communication_error.sh) will beexecuted. The script files should be located in the directory batch.d. Itis also possible to use the full path name in case that the script is notplaced in batch.d.

Special Action "Print BITE" prints out the complete text of a BITE messageautomatically. For this a postscript printer has to be installed as defaultprinter.

Several alarm conditions can be configured at the same time. In the following figure four alarmconditions - indicated in the alarm list - are active.



Stop Alarm ... stops e.g. the alarm sound in case of an active alarm. It resets also all alarmmarkers (coloured squares) in the "!" column of the alarm list.Remark: The "Stop Alarm" button does not deactivate an alarm setting. For this,you have to remove the alarm line from the list by highlighting the desired linewith the left mouse button, and deleting it with the right mouse button option"Delete".

Restore ... restores the previous settings, stored in init.d/RainLog.ini.

Save ... stores the settings to init.d/RainLog.ini.

Add ... adds the current settings as new alarm condition to the alarm list.

Modify ... is used to change one or more parameters of one alarm definition line of thealarm list. First highlight the line to be changed, than select other 'AlarmConditions' or 'Actions to Take', and finally overwrite the old line by clicking on"Modify".



5.4 RainAutoCal - Autocalibration UtilityThe RainAutoCal utility (only for non-RCL systems) is used to configure autocalibration intervalsand parameters for the Radar receiver calibration facility. The message input field of theSupervisor Manager "Target List" window is used to activate RainAutoCal commands.

The RainAutoCal utility is the basis for the "ACAL" tool of the Radar Manager Toolbox.Therefore, you can use the command line oriented utility "RainAutoCal" as well as the windoworiented "ACAL" tool to configure the automatic Radar calibration.

5.4.1 System StartThe system normally starts automatically with the message "initiated and active!" (displayed inRadar Manager Message window; exception: see total shutdown ). Next, a line appears statingthe mode and if appropriate, the next run time and date. The system then sleeps until it is wokeup at alarm time.

5.4.2 Automatic CalibrationAt the alarm time specified in the configuration file "RainAutoCal.cfg" the system sends a signalto Rainbow® Realtime to start calibration, displaying the message "auto calibration started fromautomatic mode!", followed by a new line showing the mode and the next run time and date. Thesystem then goes to sleep until the next alarm time.

5.4.3 Calibration IntervalsThe system operates in one of ten different intervals. The interval is determined and set eachtime the system reads the configuration file, i.e. during initiation, normal operation, or when theuser notifies the system of a parameter change (see "AutoCal_New" command below).

The intervals are classified in two modes:

a) manual mode: the system does nothing and only the user has control,

b) automatic mode: the system operates with one of the following intervals:

1) every Sunday at the specified time pp_calibration_hour,

2) every Monday at the specified time pp_calibration_hour,

3) every Tuesday at the specified time pp_calibration_hour,

4) every Wednesday at the specified time pp_calibration_hour,

5) every Thursday at the specified time pp_calibration_hour,

6) every Friday at the specified time pp_calibration_hour,

7) every Saturday at the specified time pp_calibration_hour,

8) daily at the specified time pp_calibration_hour,



9) periodically: automatic calibration starts at the specified day timeP_CAlIBRATION_HOURand then repeats every PP_CALIBRATION_PERIOD hours.

The automatic mode is not restricted to any time limits and therefore runs continuously, or untilstopped by user or configuration file (see below).

The system automatically takes the next reasonable time as its starting time (see examples)according to the specified interval and hour or period parameter respectively, as specified in theconfiguration file. After each automatic calibration the time is incremented again accordingly.

Examples:

If the interval period is every Wed at 12:00:00, then

a) if the current time is: Wed Feb 28 13:00:00 1996the next cal.time will be at: Wed Mar 06 12:00:00 1996

b) if the current time is: Wed Feb 28 11:00:00 1996the next cal.time will be at: Wed Feb 28 12:00:00 1996

5.4.4 User CommandsThe system is normally controlled by the configuration files. However, the user may interact withthe following user commands:

• AutoCal_Start,

• AutoCal_Stop,

• AutoCal_New,

• AutoCal_Status.

Although it may not make sense, repeated use of the commands causes no harm.

5.4.4.1 AutoCal_Stop Command

The "AutoCal_Stop" command stops the system, displaying an error message on the screen.

5.4.4.2 AutoCal_Start Command

The "AutoCal_Start" command dispatches a calibration command to Rainbow®/Realtimeregardless of the mode or interval set. It displays the message "autocalibration started by user!"on screen, followed by a status line, showing the current set interval and the next automatic runtime, if appropriate.

This command is useful for any necessary radar calibration "in between" and may be freely usedwhenever needed.

Note: The command uses the current parameters and any changes to the configuration fileswill not be detected! Refer to the command "AutoCal_New" below for other methods ofinfluencing the system.



5.4.4.3 AutoCal_Status Command

The "AutoCal_Status" command shows the status of the system at the moment and may beused freely whenever needed. If the system is running in an automatic mode, it returns thecurrent set interval and the next automatic run time, if appropriate. Otherwise, it displays anappropriate message on screen.

5.4.4.4 AutoCal_New Command

If the system has been stopped by the "AutoCal_Stop" command, use the "AutoCal_New"command to reinitialise and reactivate it.

The "AutoCal_New" command has a special multi-purpose meaning, which needs a shortexplanation here:

In the automatic mode the system normally reads the configuration file every time it is triggeredby an alarm. After reading, a new alarm period is determined and set. Therefore, any changesto the configuration file and the configuration limits file are detected and the new values areused.

This method has far-reaching implications. For example, in the weekly mode it may take up toa week for the system to notice any changes in the configuration file. Thus, a possible changeto the daily mode will first start after the "week alarm" and then continue on a daily basis. Also,an AutoCal_Start" command launched by the user before the week is over will always use the"old" parameters.

This behaviour may be desired; in the case, that it isn't, the "AutoCal_New" command must beused. It "resets" the system to the values stored in the new configuration files. Thus the systemwill respond immediately and display the new interval and the next automatic run time, ifappropriate. An "AutoCal_Start" command launched by the user will now use these "new"parameters.

5.4.5 Total ShutdownThe system may be completely turned off in the configuration file by setting thePP_CALIBRATION_ON_OFF parameter to 1.

After issuing an "AutoCal_New" command, the system responds with the message "ERRORfrom RainAutoCal => config. file => system turned off!". The system will now not accept anyfurther commands until it is turned "on" again in the configuration file, followed by an"AutoCal_New" command.

This may be useful during maintenance periods, to ensure that no one starts the systemunallowed or accidentally.



5.4.6 Setting the RainAutoCal ParametersThe system parameters are stored in the configuration files "RainAutoCal.cfg" and"RainAutoCalLimits.cfg". The first file specifies the values, while the second specifies theirallowed range of values.

Any errors or inconsistencies will cause error messages to be issued by the system at each fileread procedure.

Note: Low and high values of times in the configuration limits file always mean the earliest orlatest times respectively.

Typical copies of the two files are shown in the appendices. Also, further information is availablethere.

5.4.6.1 RainAutoCal.cfg File

Key words

Each command assignment must be on one line. It consists of a key word, which must be thefirst non-white space word on the line, and the appropriate value separated by blanks and/oran "=" sign.

White spaces may be optionally inserted before key words, the "=" sign and the value. Anythingafter the value and one space is ignored as comments. Furthermore, everything else is alsoignored!

Examples:

correct assignmentKEY_WORD = <value><space>This rest is ignored!This is another comment line.

incorrect assignmentbad! KEY_WORD = <value><space> because KEY_WORD is not thefirst non-white space word.

Only the following keywords are valid:

Program Parameters

• PP_CALIBRATION_ON_OFF

• PP_CALIBRATION_INTERVAL

• PP_CALIBRATION_HOUR

• PP_CALIBRATION_PERIOD

AutoCal Parmeters

• CALIBRATION_START

• CALIBRATION_STOP



• CALIBRATION_STEP

• CALIBRATION_MODE

• CALIBRATION_PULSE_DELAY

• CALIBRATION_PULSE_WIDTH

• CALIBRATION_ELEVATION

The numbers (non-white space words) before the key words convert them to comment lines!

Time Settings

The system automatically takes the next reasonable time as its starting time (see examples)according to the specified interval and hour or period parameter respectively. After eachautomatic calibration the time is incremented again accordingly.

Examples:

If the interval period is every Wed at 12:00:00, then

a) if the current time is: Wed Feb 28 13:00:00 1996the next cal.time will be at: Wed Mar 06 12:00:00 1996

b) if the current time is: Wed Feb 28 11:00:00 1996the next cal.time will be at: Wed Feb 28 12:00:00 1996

Example RainAutoCal.cfg File

Program Parameters

PP_CALIBRATION_ON_OFF = 0 (Turn AutoCal 0 = On, 1 = Off)PP_CALIBRATION_INTERVAL = 1

(0 = manual only, 1 = Sunday, ..., 7 = Saturday, at time pp_calibration_hour, 8 = daily at time p_calibration_hour,9 = every pp_calibration_period hours)

PP_CALIBRATION_HOUR = 10:30:01 [hh:mm:ss] (time to start AutoCal)

PP_CALIBRATION_PERIOD = 00:00:10 [hh:mm:ss] (repetition time interval)

AutoCal Parameters

CALIBRATION_START = -100.0 [dBm]CALIBRATION_STOP = 10.0 [dBm]CALIBRATION_STEP = 5.0 [dBm]CALIBRATION_MODE = 0 (0 = cw, 1 = pulse)CALIBRATION_PULSE_DELAY = 0.0 [us] (ignored for cw mode)CALIBRATION_PULSE_WIDTH = 0.0 [us] (ignored for cw mode)CALIBRATION_ELEVATION = 25.0 [degree]

End of the RainAutoCal configuration file!



5.4.6.2 RainAutoCalLimits.cfg File

Note: Refer to the RainAutoCal.cfg file for further information!

Example RainAutoCalLimits.cfg File

Program Parameters

PP_CAL_LIMIT_ON_OFF_LOW = 0 (Turn AutoCal 0=On, 1=Off)PP_CAL_LIMIT_ON_OFF_HIGH = 1PP_CAL_LIMIT_INTERVAL_LOW = 0PP_CAL_LIMIT_INTERVAL_HIGH = 9

(0 = manual only, 1 = Sunday, ..., 7 = Saturday, 8 = daily 9 = every pp_calibration_period hours )PP_CAL_LIMIT_HOUR_LOW = 00:00:00 [hh:mm:ss]

(Time to start AutoCal)PP_CAL_LIMIT_HOUR_HIGH = 23:59:59 [hh:mm:ss]PP_CAL_LIMIT_PERIOD_LOW = 00:00:10 [hh:mm:ss]

(start AutoCal every HH:MM:SS)PP_CAL_LIMIT_PERIOD_HIGH = 10:00:00 [hh:mm:ss]

AutoCal Parameters

CAL_LIMIT_START_LOW = -110.0 [dBm]CAL_LIMIT_START_HIGH = +10.0 [dBm]

CAL_LIMIT_STOP_LOW = -100.0 [dBm]CAL_LIMIT_STOP_HIGH = +10.0 [dBm]

CAL_LIMIT_STEP_LOW = -30.0 [dBm]CAL_LIMIT_STEP_HIGH = +50.0 [dBm]

CAL_LIMIT_MODE_LOW = 0 (0 = cw, 1 = pulse)CAL_LIMIT_MODE_HIGH = 1

CAL_LIMIT_PULSE_DELAY_LOW = 0.0 [us] (ignored for cwmode)CAL_LIMIT_PULSE_DELAY_HIGH = 1000.0 [us]

CAL_LIMIT_PULSE_WIDTH_LOW = -60.0 [us] (ignored for cwmode)CAL_LIMIT_PULSE_WIDTH_HIGH = 100.0 [us]

CAL_LIMIT_ELEVATION_LOW = 0.0 [o]CAL_LIMIT_ELEVATION_HIGH = +90.0 [o]

End of the RainAutoCalLimits configuration file!



5.5 RainStore - Automatic Storage UtilityRainStore is an utility for the Rainbow® system, which simplifies data backup and restore byusing graphical user interfaces (GUI) for the UNIX® tar command. The backup of selectedsubdirectories of the Rainbow® archive and FIFO file system, which contain the correspondingscan and product data files, will be started on demand or automatically. In auto-store mode thebackup will be repeated in an user defined time interval (e.g. every 24 hours).

5.5.1 Starting RainStoreRainStore can be started from a shell by executing the program RainStore which is located inthe subdirectory bin.d . After having started the RainStore tool, the basic Rainbow® StorageUtility window opens.

opens the Storage Configuration board.

selected scan and/or product data types will be storedimmediately.

activates/deactivates automatic backup.

selected scan and/or product data types will be restoredimmediately.

opens the Rainbow® Storage Messages window for dis-playing tar messages.

terminates the RainStore tool. This is the normal way toleave RainStore.

displays the next backup time when AutoStore is ON.

All RainStore settings are editable by assistance of the Storage Configuration board.



5.5.2 Storage Configuration BoardThis board is used to define Your special backup/restore configuration, for interactive as well asfor automatic operation. It consists of three main parts:

• The archive selections box displays all subdirectories of the Rainbow® archive filesystem. The desired subdirectories can be selected/deselected by mouse.

• The FIFO selections box displays all subdirectories of the Rainbow® FIFO file system.The desired subdirectories can be selected/deselected by mouse.

In both cases, the Clear button is used to deactivate all selections within one box. With Reloadthe corresponding list will be updated.

• Within the Backup definition section of this board Time Interval and Start time ofautomatic backup can be set. When AutoStore is ON (see Storage Utility window) thissettings are used by RainStore. If AutoStore Mode after program restart is ON,AutoStore is switched ON automatically, whenever RainStore is started.

Save & Done saves all settings and closes the configuration board. With Cancel this board willbe closed without saving the actual settings.



5.5.3 Storage Messages WindowThe Storage Messages window displays all activities of RainStore. In addition to backup/restoredate and time, the messages of the UNIX® tar command are visualised. Dismiss closes thiswindow.



5.6 Backup - Backup Shell Script UtilityThe file backup.sh is a menu driven shell script which allows making backups of Rainbow® rawdata and product data. It provides a menu which gives full control over the tape management.

The shell script is invoked using the command backup.sh.

5.6.1 Backup Utility ScreenThe display of the Backup Tool is divided into three sections.

The first section is the section on top of the window which displays the mode of operation. Itdisplays four lines which represent the backup settings. These settings are as follows:

Usage of archive or FIFO mode for backing up The type of file to be backed up A possible limitation to files that have been created in a configurable

number of days Verbose or silent mode

The second section only shows which backup session number will be used for the next backupsession. For example a session number 9 means that the previous sessions 1 through 8 willremain on the tape while the session number 9 and all following sessions will be overwrittenduring a backup and the newly backup will be assigned the session number 9.

The third section contains the actual menu showing the commands which can be used to controlthe Backup Tool. Hit the corresponding key in square brackets to change the correspondingmode of operation.

5.6.2 Backup Utility CommandsThe menu contains the following commands:

[a] Switch to archiveSwitches the backup mode to archive mode. The first status line will reflect the currentsetting.

[f] Switch to FIFOSwitches the backup mode to FIFO mode. The first status line will reflect the currentsetting.

[c] Change file typeThe Backup Tool allows a limitation to files which are to be backed up to files of a certaintype. Enter the file extensions at the prompt without the period, for example "vol" forbacking up volume data only. An asterisk (*) will indicate that all files be backed up.

[t] Change timeThe Backup Tool also allows a limitation to files which are newer than then last x numberof days, where x can be adjusted. Enter the number of days or "0" for any age of file.

[v] Toggle verboseThis switch allows toggling the output of backup status information during the actualbackup operation. It allows toggling between verbose mode and silent mode.



[+n] Go to n'th following backupHit the "+" key directly followed by a number to move the corresponding number ofsessions forward. The tape status will show the new session number after winding thetape.

[-n] Go to n'th previous backupHit the "-" key directly followed by a number to move the corresponding number ofsessions backward. The tape status will show the new session number after winding thetape.

[1] BackupSelecting this menu item will start the actual backup process immediately using thesettings as shown on the screen.

[2] RestoreThis is the counterpart to the menu item [1] Backup. Selecting Restore will restore thepreviously stored data from tape to the hard disk.

[3] ListList outputs a list of the contents of the tape for deciding which session numbers are notneeded any more and may be overwritten.

[4] DiffChoosing the Diff menu item will display all differences of the files on tape with the fileswhich are currently stored on the hard disk.

[5] Erase TapeErasing a tape means to destroy all data on that tape. Data stored previously cannot berecovered and will be lost forever. After selecting Erase Tape, the whole tape will beusable for backup purposes again.

[6] Eject TapeEject Tape simply will eject the tape from the drive so that another tape may be insertedor the tape may be powered down in case the whole workstation is to be shut down.

[Q] QuitEntering an upper case "Q" character will exit the program. Note that the Backup Toolwill not accept a lower case "q" character to quit.



5.7 BBC - Bright Band Correction Pre-processing UtilityThis document describes the Rainbow® bright band correction utility. The input for the brightband identification and correction algorithms is a polar raw data volume, which is modified bythe correction algorithm. The bright band correction is the first pre-processing step in Rainbow®

Rain3DccCorr process, followed by the clutter and beam blockage processing algorithms.

The bright band identification and correction algorithms are freely configurable. All tuningparameters can be edited by the user (configuration file). The following features are available:

bright band detection on/off, bright band warning only, bright band warning and correction, variation of the sensitivity of the algorithms by editable tuning parameters.

A polar raw data volume is processed in several steps (please refer to the following figures). Thebright band detection and verification algorithms (steps 1 to 8) are similar to that described byC.J. Smith (1986). The correction algorithm (step 10) eliminates detected bright band peaks inraw data. In the following all steps are described in detail. The switches and variables -configurable by the user - are highlighted in italic letters.



5.7.1 Bright Band Detection AlgorithmThe bright band detection algorithm is illustrated in the following flow chart:

do BB detection

Max1,2 >BBpeak

sliding averagein azimuth window

Search for the highesttwo local Maxima

yes

yes

no

no

original polarvolume data

Step 1

Step 2

Step 3


averaged polarvolume data

flag cell by BBheight


flag volume data(det. BBheight's)

for

all

azim

uth

ste

ps

for

all e

leva

tions

A

next

azi

mut

h st

ep



Step 1

When doBBDetection=1 the BB detection algorithm is active. To save calculation time the brightband search is limited to those volume data which are lying in a layer defined by the maximumrange rmax, the minimum height Hmin and the maximum height Hmax.

When doBBDetection=0 the BB detection and correction algorithms are bypassed.

Step 2

To smooth out the small scale variations in the precipitation pattern the data are averaged inazimuth in a sliding window of the width AzSectorSize. This smoothed volume raw data set isthe basis for the following identification steps.

Step 3

Now, for every ray, the algorithm is searching for the two highest maxima. If there are one or twomaxima, the corresponding range bin(s) will be marked as bright band candidate(s). In thefollowing test the maxima are compared to a threshold value BBpeak. A local maximum isidentified if its dBZ value is more than BBpeak dB higher than neighbouring minima.

The overestimation of the reflectivity values within the bright band is a function of range (e.g.Andrieu and Creutin, 1994). With increasing range the bright band effect on radar datadecreases due to smoothing by the increasing pulse volume. Therefore, the sensitivity of thedetection algorithm should increase with increasing range. To take this range dependence intoaccount, BBpeak can be computed as a function of range r:

BBpeak/dB = a + b * r/km

The values a and b are configurable. Example: a = 1, b = 0 -> BBpeak is independent of rangeand the detection algorithm is very sensitive. If b < 0, be sure that BBpeak is non-negative atrmax. The choice b > 0 is non-realistic.

In a final test, not indicated in the flow chart, the heights above ground of the two highest localmaxima - found by the algorithm - are compared to eliminate double peaks within one brightband. If the height difference is smaller than Hdiff, the lower peak is discarded and thecorresponding range cell is not flagged.

The output of the first three steps is a flag matrix (polar volume flag data) indicating the heightsabove ground of identified "bright band" range cells. In the following several tests are performedto increase the quality of the BB detection algorithm.



5.7.2 Bright Band Verification StepsThe bright band verification steps are illustrated in the following flow chart:

Do Ring Test

No. of Cells> BBMinCells

no

yes

yes

yes

yes

no

no

noStep 4

Step 5

Step 6

no

yes

Step 7

calculate mean heightof all det. (flagged) cellscount no. of det. cells

Height of Cellnear Mean



flag volume data(det. BBheight's) A

min 1 neighbourin azimuth

min 1 neighbourin deltaVol


flag volume data(det. BBheight's)

original polarvolume data B

reset flag

reset flag

reset flag

Step 8



Step 4

In a first verification step the neighbourhood of each flagged cell is tested for other flagged cells.There has to be at least one additional candidate within deltaVol around the cell, otherwise thiscell is no longer a candidate (reset flag). deltaVol is a function of deltaH and deltaAz.

In the vertical plane deltaVol is defined by the (normally) two neighbouring elevations in additionwith limited maximum layer width of +/- deltaH / 2 around the flagged cell. In azimuth directiondeltaVol can be of the width +/- 0, 1 or 2 azimuth steps depending on the variable deltaAz.

Step 5

In this verification step the flagged cell is tested for neighbours only in azimuth (ring structuredetection). If doRingTest = 1 the ring structure test is active. There has to be at least 1 neighbourin azimuth, otherwise the tested cell is rejected (reset flag).

Step 6

Now, the mean height above ground for the remaining flagged cells is calculated according tothe formula:

Hmean = SQRT ( SUM ( Hi2 ) )

Additionally, the number of flagged cells is counted. This two values are used by the final twoverification steps.

Step 7

If the number of flagged cells is smaller than BBMinCells, it is assumed, that there is nosignificant bright band structure. In this case all flagged cells are reset to unflagged.

Step 8

In a final verification step the height of each flagged cell is compared with the mean heightcalculated above. Only in the case that the deviation is smaller than +/- deltaHeight/2, the testedcell remains in the community of bright band affected cells.



5.7.3 Bright Band Correction AlgorithmThe bright band correction algorithm is illustrated in the following flow chart:

Step 9

The mean height of the remaining flagged cells is calculated according to the formula describedin step 6. This so-called "bright band height" is finally indicated in the Radar Manager informationfield.

Step 10

If doBBCorrection =1 the bright band correction algorithm is activated. This algorithm replacesthe original polar volume data around flagged cells in the following way:

• In nature the vertical extension BBWidth of the bright band layer is about a few hundredsof meters. The correction algorithm acts on a polar ray. Therefore, the number ofincorporated range bins depends on the elevation angle El

no. of range bins ~ BBWidth / sin (El)

If El is small, the radar beam crosses the bright band area in a flat way. Therefore, the

yes

no

Step 9

Step 10



flag volume data(det. BBheight's) B

do BBcorrection

BB correctionalgorithm

corrected data =original polar data

calculate BB height

corrected polarvolume data

BB detectedin BB height



number of incorporated range bins is higher than at greater elevation angles and thebright band effect is more "visible". As a result, the correction algorithm works better atlower elevations.

• Normally, the BB maximum is not in the middle of BBWidth. This asymmetry isconsidered by the factor Ratio (please refer to 8.4.1). Ratio is used to place BBWidthrelative to the BB maximum in BB height.

• The original dBZ values of all range bins within BBWidth around each flagged cell arefinally replaced by calculated (range weighted) mean values derived from the averagedpolar ray data at the beginning and the end of BBWidth. Therefore, BB corrected areasare perceptible in Rainbow® products as "smoothed" regions.

The following example demonstrates operation and efficiency ofthe BB correction algorithm.

5.7.4 Illustrations

5.7.4.1 Variation of Radar reflectivity with height effected by BB

vertical profile of reflectivity

BBheight

w1

w2

Ratio = w1 / w2

BB

Wid

th

Height

Intensity [dBZ]



5.7.4.2 Demonstration of the efficiency of the BBC algorithm

To show the working method of the algorithms, a raw data set including bright band effects hasbeen analysed.

Note: The following two figures are created by a special analysis tool, which is not part of Rainbow®!

This four diagrams are made at constant azimuth and elevation angles. So we are looking alonga ray. The x-axis indicates the height of the radar beam above the ground for the given elevation



of 6 degree. The y-axis' are relative scales. Additionally, the algorithm variables are indicatedin this figure.

Original This diagram shows the original (uncorrected) reflectivity data in relative dBZ. The"ripples" make it difficult to decide, whether there is a bright band or not.

Average After Step 2 the data are averaged in an azimuth sector of 20 deg. Now we canidentify one significant peak in a height of about 1.5 km.

BB Cells This peak has been detected (flagged) by the algorithms (after Step 8).

Corr. Data The corrected data are the same as the original data, except the region betweenabout 1.2 and 1.9 km height. Here, the original data are replaced by the

correction algorithm. This is done by reading out the averaged values at thebeginning and at the end of BBWidth (here in 1.2 and 1.9 km height) andcomputing the values within BBWidth by a linear approximation.

The following figure shows the corresponding PPI type images of the discussed case. It isvisibled clearly that the ring structure within the original data is eliminated completely by the BBcorrection algorithm. The bright line indicates the ray which has been discussed above.



5.7.5 The BBC Configuration FileThe location and the name of the BBC configuration file is

$GAMPATH/init.d/Rain3DccCorr.ini

Changes will be activated automatically (no restart of Rainbow®).

variable settings / defaults unit used in step

BB switches

doBBDetection 0 (=off, 1=on) n/a 1

doBBCorrection 0 (=off, 1=on) n/a 10

doRingTest 0 (=off, 1=on) n/a 5

BB values

AzSectorSize 20 degree 2

BBWidth 0.6 km 10

Ratio 0.5 n/a 10

Hmin 0.75 km 1

Hmax 3.5 km 1

rmax 80 km 1

a 1 dB 3

b 0 dB/km 3

Hdiff 0.25 km 3

deltaH 0.15 km 4

deltaAz 1 ( 0 or 2 ) n/a 4

deltaHeight 0.5 km 8

BBMinCells 100 n/a 7

5.7.6 References

Andrieu, H., and J.D. Creutin, 1995: Identification of vertical profiles of radar reflectivities forhydrological applications using an inverse method. Part I: Formulation. J. Appl. Meteor.,34, 225-239.

Smith, C.J., 1986: The reduction of errors caused by bright bands in quantitative rainfallmeasurements made using radar. J. Atmos. Oceanic. Technol., 3, 129-141.



5.8 rain_cmd - Rainbow® Command Line UtilityRainbow® provides the possibility to control key functions of the radar via a command line tool.In order to start the command line tool just start a rlogin or telnet to the main Rainbow®

workstation. Check if the PATH environment has been set to the binary path of the Rainbow®

software (e.g. /usr/local/rainbow.d/bin.d).

In order to start the shell command line tool be sure that Rainbow® is running.

The following command line arguments are available:

1. Get current BITE status: rain_cmd get_bite

Example: ./rain_cmd get_bite

2. Set BITE status: rain_cmd set_bite radar radiation

Example: ./rain_cmd set_bite 1 0 (turns radar on and radiation off)

3. Start immediate schedule task: rain_cmd immediate spdf pdf

Example: ./rain_cmd immediate default.sca defaultppz.ppz

4. Start cyclic loop schedule task: rain_cmd loop schedule_file

Example: ./rain_cmd loop bad_weather.wdg

5. Stop current schedule task: rain_cmd stop_loop

Example: ./rain_cmd stop_loop

6. Start rawdata processing tool: rain_cmd archive spdf pdf volume

Example: ./rain_cmd archive default.sca defaultpdf.ppz 199904101020150Z.vol

7. Enable/Disable gif storage: rain_cmd auto_gif 0/1

Example: ./rain_cmd auto_gif 1 (to activate automatic gifstorage for all displays)

After successful execution the rain_cmd tool terminates. An information message will be sentto the Rainbow® Radar Manager. These messages will be locked to the Rainbow® logfile(directory error.d).

The tool can be initiated interactively or e.g. using the UNIX cron facility.

Help on each command is available by means of typing in the command without any arguments,e.g. ./rain_cmd immediate.



5.9 RainNordrad - NORDRAD Conversion Utility

5.9.1 Features and UsageRainNordrad allows conversion of Rainbow®-formatted product files to NORDRAD format andstorage of the NORDRAD files at a specified data bank host. Currently the following producttypes are supported for conversion:

Rainbow® product type corresponding NORDRAD type

PPI (Z,V,W) PPI (Z,W,T)

CAPPI (Z,V,W) CAPPI (Z,W,T)

Pseudo-CAPPI (Z,V,W) Pseudo-CAPPI (Z,W,T)

MAX product (Z,V,W) VMI (Z,W,T) and HMI (Z,W,T)

VCUT (Z,V,W) VSI (Z,W,T)

Echotop (Z) ETM (Z)

SRI SRI

PAC SRT

To perform the conversion to NORDRAD format and storage at a data bank the programRainNordrad is started with the Rainbow® software. This program is configured by an ASCIIconfiguration file. Depending on the entries of that file, the conversion to a NORDRAD file isstarted immediately after generation of a Rainbow® product.

The RainNordrad program converts header data and image data to NORDRAD format andsaves these data in a file which name is constructed in NORDRAD format. The additionalstorage of the generated NORDRAD file at a specified data bank host can be configured as well.

5.9.2 Installation and Configuration

RainNordrad

This binary file is located in the directory $GAMPATH/bin.d. To perform the conversion toNORDRAD format and storage at a data bank the program RainNordrad is started with theRainbow® software. After generation of a Rainbow® product, RainNordrad starts conversion toa NORDRAD file depending on the result of checking a RainNordrad configuration file for thatRainbow® product.

The converted NORDRAD files are stored in the directory ...

GAMPATH/nordrad.d.

File names belong to the NORDRAD convention, i.e.

RR<type>[_<hgt>][_<wall>]_<area>_<resol>.D<date>T<time>

with

<type> NORDRAD type



<hgt> 4-digit height in meters (for CAPPI products)

<wall> Projection wall (for HMI products)

<area> Name of the radar location

<resol> 4-digit resolution in meters

<date> 6-digit date string (yymmdd)

<time> 4-digit time string (hhmm)

Example:

RRPSC_Z_NOOSL1_2000.D990127T2115RRCAPPI_Z_1500_NOOSL1_2000.D990128T0730RRHMI_Z_EAST_NOOSL1_2000.D990128T0600

On successful creation of a NORDRAD file, this file may be stored at a data bank host,corresponding to the entries in the NORDRAD configuration file.

After conversion and - if configured - storage a message is sent to the Radar Manager to informthe operator on the result. (cf. Radar Manager - Error Message Window)

RainNordrad.ini

This is the ASCII configuration file for RainNordrad, located in the directory $GAMPATH/init.d.In this file, all configurations for the Rainbow® to NORDRAD conversion are saved. It can beedited by any editor supporting ASCII convention. The configurations are described in aseparate subsection below.

5.9.3 Configurations of RainNordrad.iniThe ASCII file $GAMPATH/init.d/RainNordrad.ini contains the RainNordrad configuration. Itconsists of three classes:

[general] contains general configurations valid for all products

[max] contains configurations valid for conversions from MAX products

[products] contains configurations for handling of the different Rainbow® products

Each of these classes contains several configuration lines of the form

<pattern> = <value>

where <pattern> is a text string of one ore more words and <value> is a number or a text stringof one ore more words. The equal sign is mandatory.

examples: area name = NOOSL1compress data = 1

In the first two classes, [general] and [max], any configuration line must not be deleted. In thelast class [products] containing product specific configurations, configuration lines may be added



or deleted as desired by user. Note that configuration lines belong to its class, i.e. they follow theclass specifier and must not be moved into another class.

Comment lines begin with hash # and may be added or deleted as desired.

Configurations of the class [general]

In this class, general configurations are performed:

area name: A text string with the NORDRAD area name of the radar site (max 8 characters are taken)

compress data: A number (zero or one)1 - if NORDRAD pixel data shall be run length encoded0 - if NORDRAD pixel data shall not be compressed

write logfile: RainNordrad may write some information on each conversion process into a logfile located in the $GAMPATH/error.d directory. Here, a number (one or zero) has to be set, if or if not information output shallbe written to a logfile1 - information output shall be written to the logfile0 - no information output

logfile name: A text string with name of the logfile (without path)

For the case that a NORDRAD file shall be stored at a data bank host, the followingspecifications are taken:

db host name: A string with name or network ID of the data bank host

db access: Access control string for data bank host (user-id and password)

db host timeout: A number with wait time in seconds for connection to the data bank host

Configurations of the class [max]

One Rainbow® MAX product consists of three different maximum projections of reflectivity (Z),rain rate (R), radial velocity (V), or spectrum width (W), cf. the Rainbow® product description.Thus, it can be taken as input for up to three different NORDRAD files: one vertical projection(VMI) and two horizontal projections (HMI_EAST and HMI_NORTH).

max intensity: With a number between 1 and 7, it must be configured, which of theseNORDRAD files shall be calculated from the Rainbow® MAX product:

1 - only VMI (i.e., one NORDRAD file)2 - only HMI_EAST (i.e., one NORDRAD file)3 - only HMI_NORTH (i.e., one NORDRAD file)4 - VMI and HMI_EAST (i.e., two NORDRAD files)5 - VMI and HMI_NORTH (i.e., two NORDRAD files)6 - HMI_EAST and HMI_NORTH (i.e., two NORDRAD files)7 - VMI, HMI_EAST and HMI_NORTH (i.e., three NORDRAD files)

The configuration taken here will be valid for all Rainbow® MAX products selected below inthe class [products]



Configurations of the class [products]

This class contains a list of all Rainbow® products, which are treated by the RainNordradprogram after Rainbow® product generation. Each configuration line is of the form

<product> = <number>

where <product> is the Rainbow® product, i.e. the name of the product definition file (pleaserefer to Radar Manager - Product Generation Panel).

As much configuration lines as desired can be added or deleted in this class. For each Rainbow®

product type (e.g. PPI reflectivity, extension: .ppz) zero or more different products can bechosen.

For <number> on right side of the equal sign, the following numbers can be taken:

1 - only convert Rainbow® product to NORDRAD file and store it on local hostin the $GAMPATH/nordrad.d directory.

2 - convert Rainbow® product to NORDRAD file and store it afterwards at theNORDRAD data bank host specified above (it is stored local as well)

3 - convert Rainbow® product to NORDRAD file, store it afterwards at theNORDRAD data bank host and then delete it at the local host (deletion willonly be performed, if data bank storage was successful)

any other - nothing done (same as if that line wasn't present)

Example:

nordrad.ppz = 1-> if a <nordrad.ppz> Rainbow® PPI product isgenerated, it is afterwards converted to aNORDRAD file

mycappi.hcz = 3-> if a <mycappi.hcz> Rainbow® CAPPI product isgenerated, it is afterwards converted to aNORDRAD file, then stored at the data bank host,and then (if storage was successful) deleted atlocal host

Please note that RainNordrad is not lower-/uppercase sensitive for Rainbow® product names.That means e.g., in case of a directive

nordrad.ppz = 1

a NORDrad.ppz Rainbow® PPI product generation will start the NORDRAD conversion as wellas a nordrad.ppz Rainbow® PPI product.

To perform the NORDRAD conversion as good as possible, the respective Rainbow® productsshould be generated in 8bit full resolution (cf. Radar Manager - Product Definition; cf. OperatorsManual Volume 2 - Product Description).



Example for a RainNordrad configuration file:(please not that the numbers in brackets at the very end of somelines are not part of the configuration file but belong to theexplanation given below)

# Begin of RainNordrad.cfg -----------------------------------------[general]area name = GEMATRONIK in Neuss (1)compress data = 1 (2)write logfile = 1 (3)logfile name = nordrad.logdb host name = 111.222.333.444 (4)db access = nobody nemo01db host timeout = 5

[max]max intensity = 7 (5)

[products]# Pseudo-CAPPI, extensions: .pcz .pcv .pcw (6)nordrad.pcz = 1nordrad.pcv = 2nordrad.pcw = 3

# CAPPI, extensions: .hcz .hcv .hcw (7)mycappi.hcz = 2

# MAX product, extensions: .caz .cav .caw (8)nordrad.caz = 1

# End of RainNordrad.cfg -----------------------------------------

Explanations:(1)As only the first eight characters are taken, this will

result in an area name of GEMATRON.(2)The pixel data of any NORDRAD file are run length encoded.(3)Output is written to $GAMPATH/error.d/nordrad.log(4)For storage at a data bank, the host with the network ID

111.222.333.444 (which would be an illegal number) isaccessed by user nobody and password nemo01. Connectiontimeout is five seconds.

(5)For every Rainbow® MAX product, that shall be converted,three NORDRAD files are processed: VMI, HMI_EAST andHMI_NORTH

(6)If a Rainbow® nordrad.pcz Pseudo-CAPPI (reflectivity) productis generated, it is afterwards converted to NORDRAD.If a Rainbow® nordrad.pcv Pseudo-CAPPI (velocity) product isgenerated, it is converted to NORDRAD and then stored at thedata bank specified above.If a Rainbow® nordrad.pcw Pseudo-CAPPI (spectral width)product is generated, it is converted to NORDRAD and thenstored at the data bank.



On successful storage at the data bank it is deletedlocally.Any other Rainbow® Pseudo-CAPPI products are not considered.

(7)If a Rainbow® mycappi.hcz CAPPI (reflectivity) product isgenerated, it is converted to NORDRAD. Any other Rainbow®

CAPPI products are not considered.(8)If a Rainbow® nordrad.caz MAX (reflectivity) product, it is

converted to NORDRAD, where three NORDRAD files areprocessed due to the configuration line max intensity = 7above.All three files are afterwards stored at the data bank. Noother products are considered. Please do not confuse thenumber given here with the number in the configuration line max intensity = <number>above.

5.9.4 NORDRAD Attributes Supported by Rainbow®

The following NORDRAD attributes are supported by Rainbow®, i.e. are calculated from theRainbow® products and saved to the NORDRAD file header:

Name Type of the NORDRAD file.

Area Name of the radar location.

AreaProperties Description of the radar location in geographical terms.

Time Time of the product radar scan, given from Rainbow®. Time ortimezone may be set to UTC by the environment variables on theRainbow® workstation.

Quantity Quantity of the stored data.

IntStore Decription of the scaling of the pixel data.

Height Height in meters. Only for CAPPI products.

Pixel Description of the pixel data block.

Levels The height values of the levels in vertical products in meters. For VSI-and HMI-products.

AreaWall Horizontal projection wall. For HMI-products only.

Line Description of the line at which VSI data are located. For VSI-products only.

Resolution Resolution of the pixel data in meters.

Z_To_R_Constants Describes the Z-R-relation. For SRI products only.

Clutter_Treatment If the Rainbow® product was generated using a Doppler filter, thisvalue is set to <Clutter_Suppression_Doppler>; if it was generatedusing statistical filter, the value is set to <Clutter_Suppression>; if no



clutter filter was used, the value is set to <c_None>.In other cases, this attribute is not set.

Period For Rainbow® PAC products which are converted to NORDRAD SRTfiles, the duration is given. The <LostTime> value is set to zero, as itis not calculated by Rainbow®.

5.9.5 Error Handling Steps

A) The NORDRAD conversion is not started

--> Check in the Task Manager, if the RainNordrad process is active. If it is down,activate it (cf. Supervisor Manager - Target Management).

--> Check if the configuration file $GAMPATH/init.d/RainNordrad.cfg exists and has readpermission.

--> Check if the desired product is listed in the configurations of the class [products] andhas the correct value.

--> Maybe too many processes are currently running. This is indicated by additional errormessages to the Radar Manager of the form "Too many processes" or "Fork failed".In this case, stop some processes and try again.

--> Messages on conversion are sent to the Radar Manager just after complete handling.This means that in some cases the NORDRAD file may have been generated but stillnot stored to data bank (due to connectivity problems) and thus the message not sentto the Radar Manager.

B) The Radar Manager received an error message"Could not read RainBow file!"

--> The Rainbow® product may be corrupt. Restart the generation of the Rainbow® product.

C) The Radar Manager received an error message"Conversion to NORDRAD file failed!"

--> Check if the directory $GAMPATH/nordrad.d exists and has read-write-executepermission.

--> Check the output of the RainNordrad logfile. It contains information about theconversion. Conversion may have failed because of insufficient memory due to otherprocesses running.

D) The Radar Manager received an error message"Storage of NORDRAD file ... to data bank failed!"

--> Check the connectivity to the NORDRAD data bank host.



--> Check the output of the RainNordrad logfile. It contains information about the returnvalue of the StoreProduct function which is part of the UNIX-API package.

E) The Radar Manager received an error message"Timeout at storage of NORDRAD file ... to data bank!"

--> Check the connectivity to the NORDRAD data bank host.

--> Select a higher timeout value in the configuration file$GAMPATH/init.d/RainNordrad.cfg

5.9.6 Visualization of NORDRAD Files in the Display ManagerThe Display Manager checks by the filename, if a selected file is of NORDRAD type (thefilename begins with 'RR'). In this case, the NORDRAD attributes and pixel data are read fromthe file. The images is then shown in the Display Manager. Intensity levels and the mostimportant attributes are given in the image legend.

To load a NORDRAD file, perform the following steps:

- Click on the "load product" button of the Display Manager.

- A load dialog box appears.

- Click on the "Custom Selection" button.

- A file selection box appears where all files can be found.

- Browse to the directory containing the desired NORDRAD file, click on it and load it by the"OK" button.

For these steps, cf. also Display Manager - Loading a Product File.



5.10 RainCron - Timed Rainbow® Jobs

5.10.1 General FeaturesThe RainCron process allows setting of different timed jobs of the Rainbow® application. Thejobs are set in a configuration file, which is described below. Each job contains the followingproperties:

job ID the type of the job

job name a name which meaning depends on the type

start time the start time of the job

repetition time the repetition time of the job

Three different job types are available: SHR, PRT, and CRON.

A job of the type SHR triggers the generation of a Surface Hourly Rain Amount product. In thiscase, the job name is the corresponding PDF file name.

A job of the type PRT triggers the generation of a Point Rainfall Total product. In this case, thejob name is also the corresponding PDF file name.

A job of the type CRON sends a command to another Rainbow® process. Such jobs contain onemore property named ‘destination’, which is the Rainbow® process receiving the command. ForCRON type jobs, the job name contains some advises for the destination process.

5.10.2 Configuration FileThe ASCII configuration file which contains the job specifications is ...

$GAMPATH/init.d/RainCron.ini

It is read when the Rainbow® application is started. During operation the RainCron processchecks in short intervals, if the configuration file has been modified. In that case it is read again.

The RainCron.ini file consists of different classes:

[general] contains general configurations

[Cron Job 1] contains configurations of the first job

...

[Cron Job n] contains configurations of the last job (n is a digit)

Each of these classes contains configuration lines of the form

<pattern> = <value>

where <pattern> is a text string of one or more words and <value> is a number or a text stringof one or more words. The equal sign is mandatory.



The RainCron.ini file may contain comment lines beginning with hash #.

Configurations of the class [general]

This class contains one general configuration:

number of jobs the number of jobs in the file

Configurations of the class [Cron Job #]

This class describes one of the RainCron jobs. Here, # means a digit between 1 and n, wheren is the number of jobs defined in the class [general].

The following configurations belong to a job:

Job ID the type of the job (SHR, PRT or CRON)

Job Name the name which meaning depends on the type (see above)

Destination the destination process (only for the type CRON)

Start HourStart Min start time of the jobStart Sec

Rep HourRep Min repetition time of the jobRep Sec

Now 0 - the job is first performed at the next time fitting with givenstart time and repetition time

1 - the job is first performed shortly after reading theRainCron.ini file.

For each job, the time of first execution is calculated after reading the RainCron.ini file, i.e. aftereach start of the Rainbow® application and after each modification of the RainCron.ini file.

If the pattern ‘Now’ is set to 1, the first time is a few seconds after reading the file and repeatedwith the given repetition time. The given start time is ignored.

If the pattern ‘Now’ is set to 0, the given start time determines the first execution of this job.However, between the actual time and the start time may lay several repetition periods whichwould then be missed. Thus, the given start time is set back or forth in steps of the givenrepetition time, until it is closest after the actual time. This calculated time is taken for the firstjob execution.

Example

For a better understanding please refer to the following example RainCron.ini file.



Example of a RainCron.ini file

## RainCron.ini#[general]number of jobs = 2

[Cron Job 1]Job ID = SHRJob Name = hourly1.shrNow = 0Start Hour = 15Start Min = 30Start Sec = 0Rep Hour = 1Rep Min = 0Rep Sec = 0

[Cron Job 2]Job ID = PRTJob Name = mygauges.prtNow = 0Start Hour = 0Start Min = 0Start Sec = 0Rep Hour = 6Rep Min = 0Rep Sec = 0

Explanation of the example

A Surface Hourly Rainfall Amount (SHR) product with the Pdf filehourly1.shr is generated with a repetition time of 1:00:00hours, and a Point Rainfall Total (PRT) product with the Pdffile mygauges.prt every 6:00:00 hours. For both jobs, the givenstart times (15:30:00 for SHR, and 00:00:00 for PRT) are taken.If, for example, the actual time is 11:42:15, then the firstexecution of the PRT job is at 12:30:00 (which results from15:30:00 – 3 x 1:00:00), and then at 13:30, 14:30 and so on. Thetimes of the PRT job would in this case be: first at 12:00:00(resulting from 00:00:00 + 2 x 6:00:00), then at 18:00, 00:00,06:00 and so on.



5.11 FTP Dissemination UtilityRainbow® can transfer products, raw data and other files automatically to other hosts. This canbe done immediately after generation / reception of the file or at fixed time intervals. The processthat handles this job is called RainFTP. Check the target list of the Supervisor Manager andmake sure, that this process is licensed and marked as active if you want to use it.

RainFTP is configured with the file "$GAMPATH/init.d/RainFTP.ini"

# Example: $GAMPATH/rainbow.d/init.d/RainFTP.ini#[General]MaxAnzFTPProcs = 20 # maximum number of FTP's at a timeDissemWait = 5 # wait n secs for free FTP process

[RainFTP]Extension = ppzLabel = F7LabelValue = defaultpdf.ppzFilename = arch.dTarget = galadrielUser = rainbowPassword = rain99Destpath = tmpDestname = latest_image.ppz

[RainFTP]Repetition = 00:20:00Extension = buf.ppzLabel =LabelValue =Filename = defaultpdf.ppzTarget = galadrielUser = rainbowPassword = rain99Destpath = /usr/export/bufrfilesDestname =

MaxAnzFTPProcs: This parameter limits the number of concurrent FTP processes. If themaximum number is reached, then RainFTP waits until one of the FTP processes terminates,before the next transfer is initiated.

DissemWait: If the maximum number of FTP processes is reached, then RainFTP waits thisnumber of seconds before it checks the number of processes again.

[RainFTP]: This label indicates the start of a new file transfer definition.

Repetition: If this parameter is present, then we have a definition for a timed transfer.RainFTP checks the directory Destpath in intervals of hh:mm:ss, looks for the file(s) thatmatch the timestep and transfers this files / these files to the destination machine(s). The timestamp of a file is derived from the filename, which means that timed transfers can be defined forvolume data, product data, bufr files and gif images.



Example: Assume the setting Repetition = 00:20:00. This means, that the transfer shouldbe done every 20 minutes. On start-up RainFTP assumes, that interval counting starts at00:00:00 (midnight) of today. So, if the Rainbow® system is started at 10.30 a.m., the firstexecution time is set to 10.20 a.m. RainFTP searches the directory Filename, selects the filethat is closest to the execution time of 10.20 a.m., distributes this file and sets the next executiontime to 10.40 a.m. If no new data arrives until 10.40, then the next search may lead to the sameselected file. In this case the file is not sent again.

Extension: One or more extensions can be specified here. Only files with these extensions aretransferred to the host(s) that is (are) specified in this file transfer definition.

Label and LabelValue: If these parameters are not empty, then RainFTP checks thecontents of each file. The specified Label must be present, and its contents must start withLabelValue. Obviously this is only useful for volume data files and product data files.

Filename: For non-timed transfers the value specified here must be part of the full filename.You can e.g. set Filename = arch.d to prohibit the transfer of product files, that are storedin fifo.d. For timed transfers this parameter specifies which directory should be searchedfor a matching file. If the name of the directory does not start with a “/”, then RainFTP pretends$GAMPATH to the name.

Target: This is the name of the target host. You can use the IP address or the name from/etc/hosts. It is possible to specify several targets here if the settings for User, Password,Destpath and Destname are identical.

User: Specify the username on the target machine.

Password: Specify the password for User on the target machine.

Destpath: Specify the directory where the file should be transferred to. If the name of thedirectory does not start with a “/”, then the path is relative to the home directory of User. IfDespath is empty, then the file is stored in the home directory of User.

Destname: If this parameter is not empty, then this is the new name of the file on the targetmachine.

In the file “$GAMPATH/error.d/rainftpyyyymmdd.log” every file transfer, timed or nontimed, is logged. In case of problems, you can check this file for messages and additional hints.

Rainbow® Operator's Manual •••• Volume 1 (General Description) Rainbow® Configuration Files


Part 6

Rainbow® Configuration Files



Table of Contents

6 RAINBOW®

CONFIGURATION FILES ........................................................................ 6–3

6.1 DisRainMan.ini...........................................................................................................6–56.2 RadRainMan.ini .........................................................................................................6–86.3 RadRainManSchedulerQE.ini ................................................................................6–126.4 Rain3DccCorr.ini .....................................................................................................6–136.5 RainAcq.ini...............................................................................................................6–166.6 RainAdmin.ini ..........................................................................................................6–176.7 RainBow.ini..............................................................................................................6–196.8 RainBowSRIProfile.ini ............................................................................................6–246.9 RainComm.ini ..........................................................................................................6–256.10 RainCron.ini ...........................................................................................................6–276.11 RainFTP.ini .............................................................................................................6–286.12 RainGorn.ini ...........................................................................................................6–306.13 RainLog.ini .............................................................................................................6–316.14 RainNordrad.ini......................................................................................................6–326.15 RainPrint.ini............................................................................................................6–356.16 RainProject.ini .......................................................................................................6–366.17 RainSuper.ini .........................................................................................................6–396.18 SunPos.ini ..............................................................................................................6–40



6 Rainbow® Configuration FilesRainbow® needs several configuration files. These configuration files are located in ...

$GAMPATH/init.d

In general there are two groups of configuration files:

• configuration files related to a Rainbow® process, and

• global configuration files.

These files are ASCII based plain text files and can be reviewed and edited with the help ofstandard editors. The configuration files include comment lines for a better understanding. But,nevertheless, you should take care when editing something.

In the following table all Rainbow® configuration files are listed. A short description is given, andthe related Rainbow® process is indicated. The last column indicates those files, which areallowed to be modified (carefully!) by the user.

Filename Description Related Process for User

CMapEdit.ini configuration file for the Rainbow® polarClutter Map Editor application

DisRainMan.ini configuration file for the Display Managerapplication

DisRainMan •

KNMIcap.cfg KNMI specific PCP product configuration

KNMIcpp.cfg KNMI specific clutter map processconfiguration

KNMIcpp.typ KNMI specific

KNMIeth.ini KNMI specific ETH product configuration

KNMIgrad.cfg KNMI specific warning product extension

KNMIocc.cfg KNMI specific occultation correction table

KNMIocc.ini KNMI specific occultation correction filter

KNMIOccCorr.cfg KNMI specific occultation correction task

KNMIOccCorr.typ KNMI specific

KNMITOPHAT.cfg KNMI specific extension for PCP product

RadRainMan.ini configuration file for the Radar Managerapplication

RadRainMan •

RadRainManSchedulerQE.ini configuration file for the quick&easyscheduler configuration

RadRainMan •

Rain3DccCorr.ini configuration for the 3D polar pre-processing and bright band correction

Rain3DccCorr •

RainAcq.ini configuration for the data acquisitionprocess RainAcq, which gets the data viaRainFTP

RainAcq •

RainAdmin.ini configuration for Rainbow® file systemmaintenance process

RainAdmin •

RainAutoCal.ini configuration for auto-calibration of RVPsignal processor based radar systems

RainAutoCal



Filename Description Related Process for User

RainBow.ini configuration file for the productgeneration parent process; it alsoconfigures things like SRI topographicmap or radar location

RainBow •

RainBowOffline.ini main configuration file for offlineprocessing; it needs RainAcq in order toretrieve volume data files

RainBow

RainBowSRIProfile.ini configuration file for the vertical profilecorrection for the SRI product

RainBow •

RainClutterPP.ini main configuration for the KNMIcluttermap processing task

RainComm.ini configuration of the Rainbow®

communication; contains local processtable and time outs

RainComm •

RainCron.ini configuration for cron job tool; needede.g. by SHR product

RainCron •

RainFTP.ini configuration for FTP disseminationprocess

RainFTP •

RainGorn.ini configuration for BUFR conversionprocess

RainGorn •

RainLog.ini configuration for system message loggerprocess

RainLog •

RainNordrad.ini configuration for Nordrad conversionprocess

RainNordrad •

RainPrint.ini configuration for the Rainbow® printprocess

RainPrint •

RainProducts.ini configuration file for product selectionmenu; it defines all products available forspecific customer Rainbow® session

RadRainMan

RainProject.ini configuration for the projection engine RainProject •

RainRCLData.ini configuration for the RCP datacommunication process; no support forRVP systems

RainRCLData

RainRCLStatus.ini configuration for the RCP statuscommunication process; no support forRVP systems

RainRCLStatus

RainSCADA.ini configuration for the SCADA interface RainSCADA

RainScan.ini configuration file for scan definition;contains relevant operational parameterslike PRF limits

RadRainMan

RainSuper.ini configuration for Supervisor Manager RainSuper •

SunPos.ini configuration for SunPos tool •

In the following chapters all configuration files, which are allowed to be modified by the user, arelisted. Please note: Modification should only be done by qualified Rainbow® system supervisors.



6.1 DisRainMan.ini

####################################################################### Configuration file: DisRainMan.ini# Location: rainbow.d/init.d# Location of default file: rainbow.d/init.d.initial## This configuration file contains configurable parameters for:# Application DisRainMan## Remarks:# TT: This is a short explanation of the parameter# WT: This is a more detailed (multi-line) explanation of the# parameter#######################################################################

[DisRainMan_dcf]# This section contains the default settings for DisRainMan startup.# it is used if init.d/DisRainMan.X.cfg cannot be read.# Please do not change these values.FilterOn = 0LegendOn = 0OrientOn = 1AnimatOn = 0CutPosOn = 0RHIPosOn = 0DemoPicOn = 0MoveShell = 0StoreMaderToAniOn = 0AllowAllPds = 1szDispVer = 0.00szFilName =ErrorCode = 0NumPic = 26MaxPic = 0SizeNum = 0DataTyp = 1PicType = 0AnimStoreOn = 0AnimLegOn = 0PdfName =AnimTime = 0AnimWait = 0ZoomOn = 0HistoOn = 0HistoNorm = 0Fact = 0Size = 0ZoomX = 0ZoomY = 0ZoomWidth = 0ZoomHeight = 0ResizeFact = 200DispName =FrameX = 215FrameY = 94FrameWidth = 534FrameHeight = 502SetPrinter = 0AutoScale = 0



PrnName =Scale = 0Orient = 0NumProd = 0[end]

[GENERAL]MaxPicsInAnimation = 25TT = maximum image animation framesWT = number of maximum image frames in animation. A typical valueWT = is between 15 and 40. Keep always the workstation capabilityWT = in your mind when changing this value.

font size = 8x13TT = font size text legendWT = font size of the Display Manager legend. Typical sizesWT = are 8x13 or 9x15. Please refer to your X11 documentation.

font size big = 10x20TT = font size time legendWT = font size of the time information within the legend. TypicalsizesWT = are 10x20 or 12x24. Please refer to your X11 documentation.

Last Hours = 8TT = look-back load fileWT = number of look-back hours for the Display Manager file load box.WT = Typical values could be 8 or 12 hours.

[RClasses]# different Z-R relation shipsRClassZR = 200.0 1.6 Winter_1RClassZR = 205.0 1.61 Winter_2RClassZR = 300.0 1.5 SummerRClassLevel = 0.1 0.3 0.5 1.0 3.0 5.0 10.0 15.0 20.0 25.0 30.0 40.0 50.0 70.0 100.0 SummerRClassLevel = 0.2 0.4 0.6 1.0 1.5 2.0 3.0 4.0 5.0 7.0 10.0 15.0 20.0 25.0 30.0 Winter

## The next section configures the VVP(2) product (wind barb# presentation mode).#

[VVP]Maximum Displayed Layers = 40TT = maximum displayed layersWT = maximum layers to be displayed on the y-axis of theWT = VVP(2) product visualization

Maximum Displayed Products = 50TT = maximum displayed productsWT = maximum number of VVP products to be displayed on the x-axisWT = of the VVP(2) product visualization

Wind Barb Size = 2TT = wind barb sizeWT = here the VVP(2) wind barb size can be chosen. FollowingWT = values are possible:WT = 1 for small barbsWT = 2 for medium barbs (default size)WT = 3 for large barbs

# here you have to possibility to show an underlay map for top# projection images. E.g. a topographic underlay map for the SRI# product can be displayed. Please refer to operator manual. For each



# Display Manager one map is possible.

[Underlay Map]# DisRainMan.1 = Underlay1.dat# DisRainMan.2 = Underlay2.dat# DisRainMan.3 = Underlay3.dat# DisRainMan.4 =# DisRainMan.5 =# DisRainMan.6 =# DisRainMan.7 =

# The next section configures the interactive tracking tool.[ITAF]init_timediff = 15TT = time difference [min]WT = time difference in [min] between 2 images

init_thresh = 8TT = level thresholdWT = init threshold in order to find initial areas to be tracked. AninitialWT = threshold of 8 means that only values levels between 8 and 15WT = are identified as track cells/segments.

step = 1TT = small movementWT = the moving distance (in screen pixels) of the segments whenWT = pressing the single arrow button

faststep = 10TT = large movementWT = the moving distance (in screen pixels) of the segments whenWT = pressing the double arrow button

xor = 128TT = x-or colorWT = the x'ored color of the tracking segments

# This section contains all product types where interactive tracking# is allowed. Please refer to operator manual for product types.[ITAF Products]item = ppz PPI(Z)item = ppr PPI(R)item = caz MAX(Z)item = car MAX(R)item = hcz CAPPI(Z)item = hcr CAPPI(R)item = etz ETOP(Z)item = etr ETOP(R)item = ebz EBAS(Z)item = ebr EBAS(R)

# Here it is possible to show a user specific text in the legend# of each Display Manager product.[User legend]line = line = Rainbow (C)line = by GEMATRONIK



6.2 RadRainMan.ini

####################################################################### Configuration file: RadRainMan.ini# Location: rainbow.d/init.d# Location of default file: rainbow.d/init.d.initial## This configuration file contains configurable parameters for:# Application RadRainMan## Remarks:# TT: This is a short explanation of the parameter# WT: This is a more detailed (multi-line) explanation of the# parameter#######################################################################

[RadRainMan_cfg]####################################################################### This is the default startup configuration for RadRainMan# application.# It is used if RainRainMan.cfg cannot be read. Please do not change.########################################################################DateStamp = Thu Feb 8 08:55:27 2001RadManVer =RadarId =ColName =Geometry_FrameX = 24Geometry_FrameY = 774Geometry_FrameWidth = 480Geometry_FrameHeight = 160NetSend_iNumSend = 0ArchiveProd_iNumProd = 0GenerateProd_iNumProd = 0DispConf_szDispConfName =DispConf_Disp0 =DispConf_Disp1 =DispConf_Disp2 =DispConf_Disp3 =DispConf_Disp4 =MenuWidgetAv_iSys = 0MenuWidgetAv_iBITE = 0MenuWidgetAv_iPrd = 0MenuWidgetAv_iSetUser = 0MenuWidgetAv_iSwitchFE = 0MenuWidgetAv_iSetBITE = 0MenuWidgetAv_iSetArch = 0MenuWidgetAv_iPrdCreate = 0MenuWidgetAv_iHydroPrd = 0MenuWidgetAv_iWarningPrd = 0MenuWidgetAv_iForecastingPrd = 0MenuWidgetAv_i3DVolume = 0MenuWidgetAv_iPrdImmed = 0MenuWidgetAv_iPrdSched = 0MenuWidgetAv_iKill = 0MenuWidgetAv_iSavePrefs = 0MenuWidgetAv_iHelpEdit = 0MenuWidgetAv_iGenerate3d = 0MenuWidgetAv_iPassOptOn = 0MenuWidgetAv_iTbPassword = 0



MenuWidgetAv_iFTP = 0MenuWidgetAv_iAutoCal = 0PACAuto_szPACPdfFile =PACAuto_szSRIPdfFile =PACAuto_szAutoStoreOn =RIHAuto_szRIHPdfFile =RIHAuto_szSRIPdfFile =RIHAuto_szAutoStoreOn =PALAuto_szPALPdfFile =PALAuto_szPACPdfFile =PALAuto_szAutoStoreOn =TrackAuto_szTrackPdfFile =TrackAuto_szAutoStoreOn =WarnAuto_szWarnPdfFile =WarnAuto_szAutoStoreOn =RSAAuto_szRSAPdfFile =RSAAuto_szAutoStoreOn =RTAAuto_szRTAPdfFile =RTAAuto_szAutoStoreOn =[end]#######################################################################

[GENERAL]message_lines = 500TT = number of message linesWT = this is the maximum number of entries for the Radar ManagerWT = message list.

TT = x screen positionWT = initial x screen position. (x=0,y=0) is the upper left corner onthe screen.x_init_pos = 100

y_init_pos = 300TT = y screen positionWT = initial y screen position. (x=0,y=0) is the upper left corner onthe screen.

width = 480TT = window widthWT = initial width of the Radar Manager application window in screenpixels.

height = 160TT = window heightWT = initial height of the Radar Manager application window in screenpixels.

####################################################################### Fixed values in order to configure the user interface of the# Radar Manager application. Please do not change these values.#debug = 0No Preheating = 0Allow Hybrid Scan = 0#######################################################################

[Tools]####################################################################### In this section it is possible to define ext. applications called# by the Radar Manager application. Please do not change.## Until now only the offline processing# is available as external application call.



#ProcOffline = bin.d/RbOfflineEdit#######################################################################

[Timeouts]####################################################################### Important values for the synchronization with the VME for RVP# systems and the RCP for Aspen systems. Please do not change.#command_timeout = 45trigger_response = 5minimum_delay = 2synchronization = 45#######################################################################

####################################################################### Default settings for the conditional scheduler user interface. Can# be changed according to user specific needs.#######################################################################

[CondSchedSwitchBack]00:00:0000:10:0000:30:0001:00:0002:00:0003:00:0006:00:0024:00:00never

####################################################################### Initial settings for the clutter filter selection# within the scan definition user interface. Please do not change.#######################################################################

[Clutterfilter]OFF = 0Doppler 1 = 1Doppler 2 = 2Doppler 3 = 3Doppler 4 = 4Doppler 5 = 5Doppler 6 = 6Doppler 7 = 7Doppler 8 = 8Doppler 9 = 9Doppler 10 = 10Doppler 11 = 11Doppler 12 = 12Doppler 13 = 13Doppler 14 = 14Doppler 15 = 15

#################################################################### Settings for parameter specification in the product# definition worksheets. Please do not change.###################################################################### range parameter section for nearly all products#



[RANGE]Start = 25Stop = 500Increment = 5Page increment = 50Slider size = 5## slant range parameter section for VAD product#[SLANTRANGE]Start = 1Stop = 100Increment = 1Page increment = 10Slider size = 5## screen image resolution. Keep in mind that the product range# will be displayed based on selected resolution/2 .#[RESOLUTION]Start = 100Stop = 1000Increment = 10Page increment = 100Slider size = 5## minimum height of volume used for e.g. MAX product#[MINHEIGHTVOL]Start = -1000Stop = 18000Increment = 100Page increment = 500Slider size = 50## maximum height of volume used for e.g. MAX product#[MAXHEIGHTVOL]Start = -1000Stop = 18000Increment = 100Page increment = 500Slider size = 50## elevation value in [deg] used for e.g. PPI or VAD product#[ELEVATION]Start = -20Stop = 900Increment = 1Page increment = 10Slider Size = 50## displayed height value for RHI product#[DISHEIGHT]Start = -1000Stop = 18000Increment = 100Page increment = 500Slider Size = 50####################################################################



6.3 RadRainManSchedulerQE.iniThe configuration file SchedulerQE.ini contains the initial parameters of the Radar Manager"Schedule Task Control Panel". Please keep in mind, that in case of changing the current defaultschedule tasks this file will be overwritten by the application. The contents is as follows(example):

# Attention: File will be created automatically ! Please change onlythe 'name' section ![GENERAL]Schedule number of items = 4[Schedule_0]type = 0name = Immediatepdf = mini.ppzspdf = default.sca[Schedule_1]type = 1name = CycLoopfile = Standard.wdg[Schedule_2]type = 2name = Watchdogfile = test.wdg[Schedule_3]type = 1name = AnotherLoopfile = cyclic1.wdg



6.4 Rain3DccCorr.ini

####################################################################### Configuration file: Rain3DccCorr.ini# Location: rainbow.d/init.d# Location of default file: rainbow.d/init.d.initial## This configuration file contains configurable paramaters for:# Application Rain3DccCorr## Remarks:# TT: This is a short explanation of the parameter# WT: This is a more detailed (multi-line) explanation of the# parameter#######################################################################

[General]doit = 0TT = enable correction processWT = here the complete 3D correction moduleWT = can be switched on or off. After each modification theWT = Rain3DccCorr process must be restarted.WT = 0 -> offWT = 1 -> on

keep original volume = 0TT = keep original volumeWT = here you can decide whether or not to keep the non-processedWT = original volume file. The volume file will get the parameterWT = "O" (instead of Z,U or V) in the file name.

disseminate original volume = 0TT = disseminate original volumeWT = Here decide whether or not to disseminate the originalWT = volume data file via ftp to other workstations. This isWT = quite useful in order to verify particular correctionsWT = like e.g. occultation correction.

####################################################################### Configures, which clutter correction file to take for which# Scan Definition File (SDF) with the settings# <sdf_name> = <corr_file_name># with# <sdf_name> : name of SDF# (with extension)# <corr_file_name> : name of clutter correction file# (without any extension)# Example:# SCAN_VOL_ZVW_100.sca = name_of_3d_correction_file######################################################################

[configuration]44noctest.sca = 44nocdefzvw.sca = bbtest

####################################################################### Section with general switches for the Bright Band detection# (This section is independent of the "doit" switch of the "[process]"# section.)## doBBDetection : 0 -> no Bright Band detection done



# 1 -> perform Band detection# doBBCorrection: 0 -> no Bright Band correction done# 1 -> perform Bright Band correction# doRingTest: 0 -> no "ring test" done# 1 -> perform "ring test"######################################################################

[BB switches]doBBDetection = 0TT = bright band detection on/offWT = 0 -> no Bright Band detection performedWT = 1 -> perform Band detection

doBBCorrection = 0TT = bright band correction on/offWT = 0 -> no Bright Band correction performedWT = 1 -> perform Bright Band correction

TT = perform ring test on/offWT = 0 -> no "ring test" performedWT = 1 -> perform "ring test"doRingTest = 0

####################################################################### Section with values for the Bright Band algorithm. See operator# manual for more information.######################################################################

[BB values]AzSectorSize = 20BBWidth = 0.6Ratio = 0.5Hmin = 0.75Hmax = 5.5rmax = 80a = 1b = 0Hdiff = 0.25deltaH = 0.15deltaAz = 1deltaHeight = 0.5BBMinCells = 100

####################################################################### This section configures the V-Data pre-processing.# (This section is independent of the "doit" switch of the "[process]"# section.)## do speckle correction: 0 -> No Speckle Correction# 1 -> Apply Speckle Correction# do gap filling: 0 -> No Gap Filling# 1 -> Apply Gap Filling# do smoothing: 0 -> No Smoothing# 1 -> Apply Smoothing# max stddev speckle: max stddev for stagger-speckle correction# min fill ratio speckle: min fill ratio of anal. area for sp. corr.# range gap speckle: range bin gap size for speckle anal. (odd)# azi gap speckle: azimuthal gap size for speckle anal. (odd)# vel thresh speckle: min V-diff for non-staggering speckles# min stddev factor speckle: min V-diff factor for non-stagg. speckles## max range gap fill: max. range bin gap size for filling# max V diff gap fill: max Vel.Diff. for (azimuthal) gap filling## range gap smooth: range bin gap size for smoothing (odd)



# azi gap smooth: azimuthal gap size for smoothing (odd)# min fill ratio smooth: min fill ratio of anal. area for smoothing#######################################################################

[V Data]do speckle correction = 0do gap filling = 0do smoothing = 0

max stddev speckle = 0.5min fill ratio speckle = 0.2range gap speckle = 5azi gap speckle = 5vel thresh speckle = 1.0min stddev factor speckle = 2.0

max range gap fill = 6max V diff gap fill = 0.25

range gap smooth = 5azi gap smooth = 5min fill ratio smooth = 0.3

[end]



6.5 RainAcq.ini

####################################################################### Configuration file: RainAcq.ini# Location: rainbow.d/init.d# Location of default file: rainbow.d/init.d.initial## This configuration file contains configurable parameters for:# Application RainAcq## Remarks:# TT: This is a short explanation of the parameter# WT: This is a more detailed (multi-line) explanation of the#######################################################################

[General]sleeptime = 5TT = sleeping timeWT = this parameter contains the process sleeping time in [s]

minpolltime = 5TT = polling timeWT = this parameter contains the polling time in order toWT = trigger for new products, volume files or BITE files.

[ewis]# This section contains relevant parameters for project 46IC -# EWIS data integration.cfgfile = ewis.iniimportdir = import.dtargetdir = tmp.drotate = 0.0

[offline]# Here you can decide whether to use the current Rainbow station# as offline processor or not. In case of using the offline processor# mode do not forget to define the RainBow process in RainComm.ini# and to configure the RainBowOffline.ini file. Additionally# RainAcq should be configured in RainComm.ini in order to retrieve# volume data files automatically.

rainbow offline processing = 1TT = allow offline processingWT = 0 -> offline processing set to offWT = 1 -> offline processing set to on

importdir = import.dTT = data import directoryWT = The directory where Rainbow expects the data containsWT = importdir. This directory will be searched under the treeWT = rainbow.d. By default, import.d is the standard directory. ThisWT = directory would be the e.g. target dir. for ftp dissemination.

# rainbow input directory# the Rainbow communication takes the file from importdir and stores# it to the tmp.d directory in order to handle it with the Rainbow# internal communication. This directory should not be changed.targetdir = tmp.d



6.6 RainAdmin.ini

####################################################################### Configuration file: RainAdmin.ini# Location: rainbow.d/init.d# Location of default file: rainbow.d/init.d.initial## This configuration file contains configurable parameters for:# Application RainAdmin## Remarks:# TT: This is a short explanation of the parameter# WT: This is a more detailed (multi-line) explanation of the# parameter#######################################################################

[General]Fifo/Arch Deletion Activate = 0 TT = delete file on/offWT = here the RainAdmin file deletion tool can be switched on or off.

Minimum Age Fifo/Arch = 48 TT = minimum file age [hours]WT = all files which are older than minimum age in [h] are deleted.

Warning Percentage = 30 TT = warning percentageWT = if the hard disc capability is less than this value in [%] thanWT = a warning message will be sent to the user. No files will beWT = deleted until now.

Fifo Cleanup Percentage = 20 TT = fifo cleanup percentageWT = if hard disc capability is less than this value in [%] than allWT = files in the fifo.d directory (!) which are older than minimumWT = age hours are deleted.WT = Keep in mind that in Rainbow version >= 3.4 the volumeWT = data files are ONLY stored in arch.d.

Archive Cleanup Percentage = 10 TT = archive cleanup percentageWT = if the hard disc capability is less than this value in [%] thanWT = all files in the arch.d directory (!) which are older thanWT = minimum age hours are deleted.WT = Keep in mind that in Rainbow version >= 3.4 the volumeWT = data files are ONLY stored in arch.d.

InfoSeconds = 3600 TT = info messageWT = after InfoSeconds [s] the file system will be checked.

WarnSeconds = 600 TT = warning messageWT = in case of exceeding the warning criterion than everyWT = WarnSeconds [s] a warning message will be sent to the user.

ErrorSeconds = 300 TT = error messageWT = in case of exceeding the error criterion, every ErrorSeconds [s]WT = an error message will be sent to the user. The error statusWT = occurs if it is not possible due to a wrong setup of parameters



WT = for file deletion e.g. the minimum age of files to be deleted isWT = to large in comparison to incoming files due to a runningWT = scheduler.

RawData Deletion Active = 0 TT = raw data deletion on/offWT = here another mode for RainAdmin can be configured. Both modes canWT = run parallel.WT = If RawData Deletion is active than every Deletion Interval [s]WT = volume data files (!) which are older than Minimum Age will beWT = deleted from arch.d. This mode does not have an effect onWT = meteorological products.

RawData Minimum Age = 48TT = minimum ageWT = delete volume files which are older than minimum age in hours

RawData Deletion Interval = 3600TT = deletion intervalWT = try to delete volume files every interval seconds

######################################################################## This section contains a list of directories which shall# be cleaned up from old files regularly. Recursive deletion# (directory with subdirectories) is not possible here.# Files are only deleted if they are older than the given time in# hours.# The check is done every 20 minutes.# The following directories are hard-coded in the software, but may# also be configured here:# tmp.d, rcl.d, bite.d, sched.d######################################################################### each entry has the format# directory = dir-name min-age-of-files-in-hours## dir-name is either absolute or relative to the Rainbow working# directory !! depending on a leading /#######################################################################

[Directories]directory = tmp.d 4directory = rcl.d 3directory = bite.d 72directory = sched.d 3directory = answer.d 24directory = raintrack.d 12directory = track.d 12directory = pdus.d 24directory = sdus.d 24directory = mdd.d 24directory = ovl.d 24directory = gif.d 96



6.7 RainBow.ini

####################################################################### Configuration file: RainBow.ini# Location: rainbow.d/init.d# Location of default file: rainbow.d/init.d.initial## This configuration file contains configurable parameters for:# Application RainBow## Remarks:# TT: This is a short explanation of the parameter# WT: This is a more detailed (multi-line) explanation of the# parameter#######################################################################

[General]RadarSiteAbbr = Radar Site Abbr.TT = radar site stringWT = this parameter shall contains a string which identifiesWT = the radar site. This string will be part of the header infoWT = of every meteorological product created by RainBow. See alsoWT = RadarLocation below.

[GeneralParms]####################################################################### In this section only these parameters are described which are# relevant for the operation of the Rainbow software. Other parameters# are partially obsolete in Rainbow >= 3.4 but in order to guarantee# compatibility to older Rainbow versions we have to support them.#######################################################################

RadarLocation = Location unknownTT = radar site stringWT = this parameter shall contains a string which identifiesWT = the radar site. This string will be part of the header infoWT = of every meteorological product created by RainBow.

####################################################################### Please do not change these lines#Verification = 0Demo = 0Protection = 0ReadPCX = 0Mader = 0ImageReferences = 0UkwImageRes = 0AnimationCount = 25DelayBITE = 0DelayImmediate = 0DelayScheduler = 0CpProd2RemoteArch = 0#######################################################################

RadarLon = 0.0TT = radar longitudeWT = radar longitude (East). Float value (decimal degrees).



RadarLat = 0.0TT = radar latitudeWT = radar latitude (North). Float value (decimal degrees).

LocalShutdownPW = gemaTT = shutdown passwordWT = shutdown password for the supervisor manager

DisplayManagerPW = gemaTT = display manager passwordWT = shutdown password for the super user mode of theWT = display manager

RadarManagerPW = gemaTT = radar manager passwordWT = shutdown password for the super user mode of theWT = radar manager

[RadarParameters]####################################################################### This section contains general configuration parameters.## hard coded default values are:# Rainbowservice = rainbow (please add in /etc/services for VME# systems only)# Radargateport = 6530# Rainbowport = 6500#######################################################################

Radargatehost = vmeTT = radar gate hostWT = name of the RVP control processor (RVP systems only). ThisWT = name must be the corresponding entry in the /etc/hosts file.

Radargateport = 6530TT = vme port numberWT = port number of the RVP control processor (RVP systems only)

Radar installation height above ground [m] = 10.0TT = radar height AGLWT = height in [m] of the antenna above ground level (AGL)WT = This parameter is used e.g. for the SRI product with terrainWT = correction.

Radar installation height above MSL [m] = 0.0TT = radar height MSLWT = height in [m] of the antenna above mean sea level (MSL)WT = This parameter is used for all vertical coordinates.

Half power beam width [deg] = 0.9TT = half power beam widthWT = half power beam width in [deg] used e.g. for VIL and SSA

[Data]Compress Volume Data = 0TT = compress volume on/offWT = decide whether all volume data files should be saved inWT = compressed format or not. We recommend to switch this option toWT = on in order to optimize the hard disc capacity.WT = 0 -> volume data is not compressedWT = 1 -> volume data is compressed

####################################################################### Please do not change this parameter ! Decide for Aspen (only)# systems if the PPI slice data from the RCP should be transferred



# compressed to the Rainbow workstation or not.# As a standard, PPI slices are transferred in compressed way.#Compress TCP/IP Data = 1#######################################################################

MaxRawAge = 600TT = maximum volume data ageWT = if "online" volume data received by a running schedulerWT = is older than this value in [min] than no product generationWT = is done. The volume data files will be stored as usual in arch.d.

[Genesis]#######################################################################This section configures the product generation.######################################################################### resampling: 1 -> interpolation of carth. data# 0 -> no interpolation#resampling = 1## filter size: 0 -> images as calculated# n>0 -> smoothing filter of images#filterSize = 0#######################################################################

[VVP]####################################################################### This section configures the VVP(2) product.## ElimVelocity: Threshold for data deviating too far from mean# ElimVariance: Threshold of StdDev for complete VVP result# ElimNoWind: Threshold for (clutter contamined) data# SecondRegression: 0 -> No second VVP regression performed# 1 -> A second VVP regression is performed# MinNumber2Sectors: Min. Data number in at least on of two 45deg-# sectors# Refer to Operator Manual Vol. 2, VVP(2)########################################################################ElimVelocity = 0.30ElimVariance = 0.30ElimNoWind = 0.05SecondRegression = 0MinNumber2Sectors = 5#######################################################################

[SRI]####################################################################### This section configures the SRI terrain correction map## ASCIIFileName: Name of the ASCII topomap (in $GAMPATH/map.d)# BinFileName: Name of the binary topomap (in $GAMPATH/map.d)# Map_Size_X: Map pixel size in W-E direction# Map_Size_Y: Map pixel size in S-N direction# Radar_Loc_X: Map Line-number of Radar Location# (0,1,...,Map_Size_X-1)



# Radar_Loc_Y: Map Column-number of Radar Location# (0,1,...,Map_Size_Y-1)# Map_Resolution: Size [m] of one map pixel# Map_Order: North-South -> first Map-Line in North# South-North -> first Map-Line in South# (For topodat_ka.asc, project 19KFC:# Size (568,768); Radar (255,575); Resolution 500;# Orientation South-North)########################################################################ASCIIFileName = topodat.ascBinFileName = topodat.binMap_Size_X = 12Map_Size_Y = 12Radar_Loc_X = 6Radar_Loc_Y = 6Map_Resolution = 50000.0Map_Order = North-South#######################################################################

[SWI]####################################################################### This section configures settings for the SWI# (severe weather indicator) product generation## show runtime results: 0 -> do not print runtime statistics# 1 -> print runtime statistics to stdout# num pix internal: Internal used number of pixels for# segmentation.# This number determines the generation time# and should be machine-dependent.# ssa <names> : Thresholds for the storm structure algorithm.# See the description of the SSA product# meso <names> : Thresholds for the mesocyclone idetification.# See the description of the MESO product# verg <names> : Thresholds for the vergence identification.########################################################################show runtime results = 0num pix internal = 250

# Storm identification thresholdsssa lowest elevation = 1.0ssa Z-M conversion factor C = 24000ssa Z-M conversion exponent D = 1.82ssa min storm reflectivity = 35ssa min core reflectivity = 50ssa min size = 3.0ssa min fill percent = 75

# Mesocyclone Separatorsmeso height sep = 3.0meso velocity sep low = 20meso velocity sep high = 40

# Mesocyclone Thresholdsmeso min velocity diff = 2.0meso max empty bins = 6meso min vertical extent = 1.0meso max feature height = 8.0meso max radial distance = 0.75meso max tangential distance = 0.034meso min shear 1 = 14.4



meso min momentum 1 = 180meso min shear 2 = 7.2meso min momentum 2 = 540meso min num pattern = 10meso min ratio 1 = 0.5meso max ratio 1 = 2.0meso min ratio 2 = 1.6meso max ratio 2 = 4.0meso range sep = 140

# Thresholds for con-/di-vergence regionsverg max empty bins = 6verg min vel diff border = 2.0verg min radial size pattern = 3.0verg min mean shear = 0.5verg min mean vel diff = 5.0verg min num pattern = 4verg min area size = 15verg compactness limit = 0.5

#######################################################################

[TrackParms]####################################################################### This section configures settings for the storm tracking product.# See operator manual for more information.########################################################################StepFactor = 1.000DefaultVelocity1 = 0.005DefaultVelocity2 = 0.010DefaultVelocity3 = 0.025GlobMotFactor1 = 0.300GlobMotFactor2 = 1.000GlobMotFactor3 = 2.000ForcMotFactor1 = 0.500ForcMotFactor2 = 2.500ForcMotFactor3 = 4.500SegExtWeight = 1.000MaxExtWeight = 0.800NearForecastWeight = 1.000MinAcceptProbability = 0.450#######################################################################

[end]



6.8 RainBowSRIProfile.ini

####################################################################### Configuration file: RainBowSRIProfile.ini# Location: rainbow.d/init.d# Location of default file: rainbow.d/init.d.initial## This configuration file contains configurable paramaters for:# Application RainBow## Remarks:# TT: This is a short explanation of the parameter# WT: This is a more detailed (multi-line) explanation of the# parameter#######################################################################

####################################################################### This configuration file enables the vertical profile# correction for user selectable SRI products## Syntax:# SRI_PDF = SECTIONNAME# SRI_PDF = SECTIONNAME# ...# with# SRI_PDF: name of SRI PDF file (without path)# SECTIONNAME: name of SRI profile correction section (below)######################################################################

[SRI profile correction]# defaultpdf.sri = SRIDefaultProfile[end]

####################################################################### This section contains the SRI correction profiles## The SRI rain intensities [mm/h] are corrected height-dependent# by the following correction profiles.## item = (Height above sea level [km]) (correction factor)## For intermediate heights, linear interpolation is applied.# For heights out of range, extrapolation of the lowest/highest value# is applied.# The number of "item = height factor" profile lines must not be# larger than 100 !#######################################################################

[SRIDefaultProfile]item = 0.2 1.0item = 9.3 1.0[end]



6.9 RainComm.ini

####################################################################### Configuration file: RainComm.ini# Location: rainbow.d/init.d# Location of default file: rainbow.d/init.d.initial## This configuration file contains configurable parameters for:# Application RainComm## Remarks:# TT: This is a short explanation of the parameter# WT: This is a more detailed (multi-line) explanation of the# parameter#######################################################################

####################################################################### The communication uses only section [comdef] !!!!# Other sections may be prepared.## The symbolic links for local DisRainMan's are created# automatically on startup of Rainbow !# The maximum number of DisRainMan's is 10.#######################################################################

[General]######################################################################## Please do not change any values !# Delay in msec before first app startup#AppStartDelay = 1000 ## Delay in msec between app startups#AppStartRep = 500

## Decide wether to check the number of Rainbow communication processes# or not. We recommend to set it to 0.#ProcLimited = 0

## This is the maximum number of Rainbow internal communication# processes.# If ProcLimited is set to 0 then this parameter has no effect.#MaxProc = 50

## If this limit of Rainbow processes is exceeded than the Rainbow# communication sends a warning message to the user.# If ProcLimited is set to 0 then this parameter has no effect.#WarnProc = 45

## This value is obsolete but for compatibility reasons to older# versions it must be set to 0.



#Database = 0

#######################################################################

## Decide whether logging messages of several levels should be# initiated or not. We recommend to enable every parameter.#InfoLog = 1WarningLog = 1ErrorLog = 1CriticalLog = 1

[end]

####################################################################### comdef sections

[comdef_main][comdef]process = RainLogprocess = RainSuperprocess = RainAdminprocess = RadRainManprocess = RainBowprocess = RainProjectprocess = RainGornprocess = RainCronprocess = RainRCLDataprocess = RainRCLStatusprocess = RainNordradprocess = RainFTPprocess = RainPrintprocess = RainAcqprocess = RainRPGprocess = DisRainMan.1process = DisRainMan.2process = DisRainMan.3process = DisRainMan.4process = DisRainMan.5process = DisRainMan.6

[comdef_display]process = RainLogprocess = RainSuperprocess = RainAdminprocess = RainAcqprocess = RainPrintprocess = DisRainMan.1process = DisRainMan.2process = DisRainMan.3

[next_section]

#######################################################################



6.10 RainCron.ini

####################################################################### Configuration file: RainCron.ini# Location: rainbow.d/init.d# Location of default file: rainbow.d/init.d.initial## This configuration file contains configurable parameters for:# Application RainCron## Remarks:# TT: This is a short explanation of the parameter# WT: This is a more detailed (multi-line) explanation of the# parameter######################################################################### RainCron Job file## Examples for combining 'Job ID' and 'Job Name' (and 'Destination'):# -------------------------------------------------------------------## Job ID = PRT # create PRT product# Job Name = mygauge1.prt # Pdf File## Job ID = IMM # send immediate scan# Job Name = ppz1.sca default.ppz # ScanPdf Pdf## Job ID = CRON # send a message# Destination = RainFTP # destination of message# Job Name = Send FIFO Data # text of message## Example of a RainCron Job# -------------------------## [RainCron]# Job ID = SHR # SHR: create a SHR product# Job Name = defaultpdf.shr # the Pdf File used for SHR generation# Now = 1 # 1 -> immediate start -> start time# ignored# Start Hour = 06 # \# Start Min = 30 # > start time 06:30:00# Start Sec = 00 # /# Rep Hour = 03 # \# Rep Min = 00 # > repetition time 03:00:00# Rep Sec = 00 # /#######################################################################



6.11 RainFTP.ini

####################################################################### Configuration file: RainFTP.ini# Location: rainbow.d/init.d# Location of default file: rainbow.d/init.d.initial## This configuration file contains configurable parameters for:# Application RainFTP## Remarks:# TT: This is a short explanation of the parameter# WT: This is a more detailed (multi-line) explanation of the# parameter######################################################################## RainFTP example configuration# -----------------------------# RainFTP reads this file at startup time.# All headers have the name [RainFTP].# Empty labels can be omitted.# The file to be sent must match all specified conditions.# A timed transfer does not search subdirectories of "Filename"### MaxAnzFTPProcs = 20 # maximum number of FTP's at a# # time# DissemWait = 10 # wait n secs for free FTP# # process## --- Example for ftp dissemination triggered by message## [RainFTP]# Extension = buf.ppz ppz # multiple, filename# # extension(s)# Label = F7 # single, name of label# LabelValue = defaultpdf # single, value of label# # starts with this# # text# Filename = arch.d # multiple, part(s) of absolute# # filename# Target = galadriel zeus # multiple, destination# # workstation(s)# User = rainbow # single, name of user# Password = rain99 # single, password# Destpath = tmp # single, relative or absolute# # path# Destname = # single, new filename, leave# # empty for unchanged# # filename## --- Example for ftp dissemination triggered by timer## [RainFTP]# Repetition = 00:30:00 # HH:MM:SS repetition interval# Extension = buf.ppz ppz # see above# Label = F7 # see above# LabelValue = ppz_200 # see above# Filename = arch.d/ppz_200.ppz.d # single, look here for latest# # file, absolute or# # relative to GAMPATH# Target = galadriel zeus # see above



# User = rainbow # see above# Password = rain99 # see above# Destpath = tmp # see above# Destname = # see above## --- Example to GET files with ftp dissemination, triggered by timer# --- To get a file, the timer triggering must be used## [RainFTP]# Repetition = 00:30:00 # HH:MM:SS repetition interval# PutGet = get # use 'get' to get the file,# # otherwise it will be put # Extension = # keep empty or omit line# Label = # keep empty or omit line# LabelValue = # keep empty or omit line# Filename = /remote/test/file1.tst # single, absolute filename with# # Path on remote station# Target = zeus # single, name of remote station# User = rainbow # see above# Password = rain99 # see above# Destpath = tmp # relative or absolute path;# # on local station# Destname = # see above; name on local# # station#######################################################################

[GENERAL]MaxAnzFTPProcs = 25 DissemWait = 30



6.12 RainGorn.ini

####################################################################### Configuration file: RainGorn.ini# Location: rainbow.d/init.d# Location of default file: rainbow.d/init.d.initial## This configuration file contains configurable parameters for:# Application RainGorn## Remarks:# TT: This is a short explanation of the parameter# WT: This is a more detailed (multi-line) explanation of the# parameter######################################################################## This configuration file contains the rainfall classification# tables for the BUFR conversion.#######################################################################

[RClasses]RClassZR = 300.0 1.5 BUFRRClassLevel = 0.1 0.3 0.5 1.0 3.0 5.0 10.0 15.0 20.0 25.0 30.0 40.0 50.0 75.0 100.0 BUFR



6.13 RainLog.ini

# This section contains general settings for the hard disk log output.# Log output goes into the file error.d/Rainbow.log## logsize: Filesize limits in bytes. If the file Rainbow.log# becomes# larger than that value, a new Rainbow.log file is# created.# multiple_logs: 0 -> new Rainbow.log files overwrite the old ones# 1 -> the old Rainbow.log file is renamed to# error.d/Rainbow.log.yymmddhhmmss# before the new Rainbow.log file is created.# useSlashN: 0 -> all message into one very long line# 1 -> each message gets its own line (preferable!)#

[general]logsize = 200000multiple_logs = 1useSlashN = 1

# This Section contains parameters for a KNMI special project.## For each of the parameters of this section, dissemination of# messages to a special device can be enabled (value 1) or disabled# (value 0).The parameters correspond to the message types (Info,# Warning, Error, Critical Error).

[knmi]info = 0warning = 0error = 0critical = 0

# This Section contains startup configurations of the RainLog message# window.# For each of the parameters of this section, display of messages in# the message window can be enabled (value 1) or disabled (value 0).# The parameters correspond to the message types (Info, Warning,# Error, Critical Error).

[configuration]info = 1warning = 1error = 1critical = 0frequency = 15spinbox = 1000



6.14 RainNordrad.ini

####################################################################### Configuration file: RainNordrad.ini# Location: rainbow.d/init.d# Location of default file: rainbow.d/init.d.initial## This configuration file contains configurable parameters for:# Application RainNordrad## Remarks:# TT: This is a short explanation of the parameter# WT: This is a more detailed (multi-line) explanation of the# parameter######################################################################## In this file all configurations for the Rainbow to NORDRAD# conversion are saved.## The file consists of three classes:# [general] contains general configurations valid for all products# [max] contains configurations valid for conversions from# RainBow MAX products# [products] contains configurations for handling of the different# RainBow products# Each of these classes contains several config lines of the form# <pattern> = <value># where <pattern> is a text string of one ore more words and <value># is a number or a text string of one ore more words.# The equal sign is mandatory.# examples: area name = NOOSL1# compress data = 1## In the first two classes, [general] and [max], any configuration# line MUST NOT BE DELETED!# In the last class [products] containing product specific# configurations, lines may be added or deleted as desired by user.## Comment lines begin with hash # and may be added or deleted as# desired.######################################################################

[general]######################################################################## some general specifications# configuration lines MUST NOT BE DELETED!######################################################################## area name: NORDRAD area name of the radar site# (max 8 characters are taken)# radar type: Type of the Radar (numbers from nrdfilep.h)# 1 - Rr_Normal, (default)# 2 - Rr_Doppler,# 3 - Rr_Dual,# 4 - Rr_X_Band,# 5 - Rr_S_Band,# 6 - Rr_X1_Band,# 7 - Rr_X2_Band,# 8 - Rr_Undefined# compress data:# 1 - if NORDRAD pixel data shall be run length encoded



# 0 - if NORDRAD pixel data shall not be compressed# set FF pixel:# 1 - for all top projection products, assume that# displayed range equals scan range and set all# NORDRAD file pixel out of that range to hex code FF# 0 - not set pixel to hex code FF# write logfile:# 1 - if some information on NORDRAD conversion shall be# written to a logfile (must then be specified below)# 0 - no information output# logfile name: name of the logfile (without path; file will be# written to < ...../rainbow.d/error.d> directory ) # db host name: Name or network ID of the data bank host# db access: Acces control string for data bank host# (user-id and password)# db host timeout: wait time in seconds for connection to data bank# host######################################################################area name = GEMATRONIK in Neussradar type = 1compress data = 1set FF pixel = 0write logfile = 1logfile name = nordrad.logdb host name = 111.222.11.22db access = nobody nemo01db host timeout = 5#foreign product = 1######################################################################

[max]######################################################################## max intensity: One RainBow MAX product can be taken as input# for up to three different NORDRAD files:# one vertical projection (VMI) and two horizontal# projections (HMI_EAST and HMI_NORTH).# With a number between 1 and 7, it must be# configured, which of these NORDRAD files# shall be calculated from the RainBow MAX product:# 1 - only VMI (i.e., one NORDRAD file)# 2 - only HMI_EAST (i.e., one NORDRAD file)# 3 - only HMI_NORTH (i.e., one NORDRAD file)# 4 - VMI and HMI_EAST (i.e., two NORDRAD files)# 5 - VMI and HMI_NORTH (i.e., two NORDRAD files)# 6 - HMI_EAST and HMI_NORTH (i.e., two NORDRAD files)# 7 - VMI, HMI_EAST and HMI_NORTH (i.e., three NORDRAD)# The configuration taken here will be valid for all# RainBow MAX products selected below in the# class [products]######################################################################max intensity = 7######################################################################

[products]####################################################################### * Contains a list of RainBow products, which are delivered to the# NORDRAD interface after RainBow product generation.# * NOTE that for each RainBow product type (e.g. PPI reflectivity,# extension: .ppz) zero or more different products can be chosen.# * For the number on right side of the equal sign, the following# selections can be taken:# 0 (zero) - do nothing (same as if that line wasn't present)# 1 - convert RainBow product to NORDRAD file# 2 - convert RainBow product to NORDRAD file and store it# afterwards at the NORDRAD data bank host specified



# above# 3 - convert RainBow product to NORDRAD file, store it# afterwards at the NORDRAD data bank host and then# delete it at the local host (deletion will only# be performed, if data bank storage was successful)# * example:# nordrad.ppz = 1 -> if a <nordrad.ppz> RainBow PPI product is# generated, it is afterwards converted to a# NORDRAD file# mycappi.hcz = 3 -> if a <mycappi.hcz> RainBow CAPPI product is# generated, it is afterwards converted to a# NORDRAD file, then stored at the data bank# host, and then (if storage was successful)# deleted at local host# * NOTE that the NORDRAD interface is not lower-/uppercase sensitive# for RainBow product names.# That means e.g., in case of a directive nordrad.ppz = 1# a <NORDrad.ppz> RainBow PPI product generation will start the# NORDRAD conversion as well as a <nordrad.ppz> RainBow PPI product.# * In this class [products], configuration lines may be added or# deleted as desired by user.#######################################################################

# Pseudo-CAPPI, extensions: .pcz .pcv .pcwnordrad.pcz = 1nordrad.pcv = 1nordrad.pcw = 1

# CAPPI, extensions: .hcz .hcv .hcwnordrad.hcz = 1nordrad.hcv = 1nordrad.hcw = 1

# PPI, extensions: .ppz .ppv .ppwnordrad.ppz = 1nordrad.ppv = 1nordrad.ppw = 1

# MAX product, extensions: .caz .cav .caw# one MAX product will result in up to three NORDRAD files:# one vertical projection (VMI) and two horizontal# projections (HMI_EAST and HMI_NORTH)# ( see configurations in class [max] )nordrad.caz = 1nordrad.cav = 1nordrad.caw = 1

# Vertical cut (-> VSI), extensions: .vcz .vcv .vcwnordrad.vcz = 1nordrad.vcv = 1nordrad.vcw = 1

# Echotop product (reflectivity), extension: .etznordrad.etz = 1

# SRI product (rain intensity), extension: .srinordrad.sri = 1

# PAC product (rain total, -> SRT), extension: .pacnordrad.pac = 1



6.15 RainPrint.ini

####################################################################### Configuration file: RainPrint.ini# Location: rainbow.d/init.d# Location of default file: rainbow.d/init.d.initial## This configuration file contains configurable paramaters for:# Application RainPrint## Remarks:# TT: This is a short explanation of the parameter# WT: This is a more detailed (multi-line) explanation of the# parameter#######################################################################

[GENERAL]# 1 = PRTTYPE_NONE# 2 = PRTTYPE_POSTSCRIPT# 3 = PRTTYPE_HP-PCLPrinterType = 2

# Minimum number of screen-pixels per cm for graphics outputMinimum PPC = 40



6.16 RainProject.ini

####################################################################### Configuration file: RainProject.ini# Location: rainbow.d/init.d# Location of default file: rainbow.d/init.d.initial## This configuration file contains configurable paramaters for:# Application RainProject, RadRainMan## Remarks:# TT: This is a short explanation of the parameter# WT: This is a more detailed (multi-line) explanation of the# parameter######################################################################### The first section configures the projection user interface within# each product definition file worksheet which supports projection.## [General] # PROJ number of items = number of projections # # [PROJ_x] # name = Unique abbreviation, displayed in the worksheet menu. # type = One of these projection types: # (-1) for None Projection # 0 for Null Projection (linear transformation) # 1 for Geosat Projection # 3 for Polar Stereographic North Projection # 4 for Polar Stereographic South Projection # 5 for Gauss/Krueger/UTM/Hayford Gauss Projection # 6 for Radar Azimuthal Projection # 7 for Conical Lambert # # subtype = Please specify the variation number of that type # # DO NOT REMOVE THE NONE PROJECTION !!# ######################################################################

[GENERAL]PROJ number of items = 3

[PROJ_0]name = Nonetype = -1subtype = 0

[PROJ_1]name = PSTNtype = 3subtype = 0

[PROJ_2]name = GAUSS/KRUEGERtype = 5subtype = 0

####################################################################### Configuration for# Polar Stereographic North Projection



#######################################################################

[PSTN]proj_type = 3 # Projection typeproj_offset_x = 0.0 # X offset (ignored but must be sup-plied)proj_offset_y = 0.0 # Y offset (ignored but must be sup-plied)proj_res_x = 2.2 # X resolutionproj_res_y = 2.2 # Y resolutionproj_ref_long = 6.73 # Projection reference longitudeproj_ref_lat = 51.12 # Projection reference latitude earth_rad_equator = 6385.0 # Earth spheroid equatorial radiusearth_rad_polar = 6370.0 # Earth spheroid polar radius image_width = 900 # Image widthimage_height = 900 # Image heightimage_ref_x = 449.5 # Image reference point, X coordinate ofimage_ref_y = 449.5 # Image reference point, Y coordinate ofimage_ref_long = 20.23 # Image reference point, longitudeimage_ref_lat = 50.12 # Image reference point, latitude

####################################################################### Configuration for# Gauss-Krueger projection#######################################################################

[Gauss-Krueger]proj_type = 5 # Projection typeproj_offset_x = 0.0 # X offset (ignored but must be sup-plied)proj_offset_y = 0.0 # Y offset (ignored but must be sup-plied)proj_res_x = 5 # X resolutionproj_res_y = 5 # Y resolutionproj_ref_long = 10.0 # Projection reference longitudeproj_ref_lat = 50.0 # Projection reference latitude earth_rad_equator = 6385.0 # Earth spheroid equatorial radiusearth_rad_polar = 6370.0 # Earth spheroid polar radius image_width = 400 # Image widthimage_height = 400 # Image heightimage_ref_x = 199.5 # Image reference point, X coordinate ofimage_ref_y = 199.5 # Image reference point, Y coordinate ofimage_ref_long = 20.2 # Image reference point, longitudeimage_ref_lat = 50.2 # Image reference point, latitude

####################################################################### Configuration for# Radar-Azimuthal projection#######################################################################

[Radar-Azimuthal]proj_type = 6 # Projection typeproj_offset_x = 0.0 # X offset (ignored but must be sup-plied)proj_offset_y = 0.0 # Y offset (ignored but must be sup-plied)proj_res_x = 8 # X resolutionproj_res_y = 8 # Y resolution



proj_ref_long = 70.0 # Projection reference longitudeproj_ref_lat = 50.0 # Projection reference latitude earth_rad_equator = 6385.0 # Earth spheroid equatorial radiusearth_rad_polar = 6370.0 # Earth spheroid polar radius image_width = 400 # Image widthimage_height = 400 # Image heightimage_ref_x = 199.5 # Image reference point, X coordinate ofimage_ref_y = 199.5 # Image reference point, Y coordinate ofimage_ref_long = 10.0 # Image reference point, longitudeimage_ref_lat = 50.0 # Image reference point, latitude



6.17 RainSuper.ini

####################################################################### Configuration file: RainSuper.ini# Location: rainbow.d/init.d# Location of default file: rainbow.d/init.d.initial## This configuration file contains configurable parameters for:# Application RainSuper## Remarks:# TT: This is a short explanation of the parameter# WT: This is a more detailed (multi-line) explanation of the# parameter#######################################################################

[General]## Delay in msec before first Display Manager startup#DispStartDelay = 10000 ## Delay in msec between Display Manager startups#DispStartRep = 2000



6.18 SunPos.ini

####################################################################### Configuration file: SunPos.ini# Location: rainbow.d/init.d# Location of default file: rainbow.d/init.d.initial## This configuration file contains configurable parameters for:# Application SunPos## Remarks:# TT: This is a short explanation of the parameter# WT: This is a more detailed (multi-line) explanation of the# parameter######################################################################### Description of the radar location:## latitude: in decimal degrees, North positive# longitude: in decimal degrees, East positive# timeshift: in hours, to correct for wrong clock#######################################################################

[location]latitude = 51.12349longitude = 6.73684timeshift = 0

Gematronik GmbH • Revision History • 2001-05-02 Page 1 of 4

Revision HistoryRainbow® Operator's Manual

Volume 1

Document

Release Changes Document Code Date

1 initial revision GEMA-SD-0150-3310-1 1999-05-31

1.1 RM Rel. 1.1: Offline Processing Tool added.RU Rel. 1.1: Command Line Utility added.

GEMA-SD-0150-3311-1 1999-06-08

1.2 part 1 (1.1), part 2 (1.1); part 3 (1.2); part 4 (1.1)part 5 (1.2): part 6 (1.1)

GEMA-SD-0150-3312-1 1999-06-30

1.2a part 1 (1.3), part 2 (1.1); part 3 (1.2); part 4 (1.2)part 5 (1.2): part 6 (1.1)

GEMA-SD-0150-3312-1a 1999-09-13


GEMA-SD-0150-3313-1 1999-08-06


GEMA-SD-0150-3314-1 1999-09-13


GEMA-SD-0150-3315-1 1999-11-25


GEMA-SD-0150-3316-1 1999-12-14


GEMA-SD-0150-3317-1 2000-01-14


GEMA-SD-0150-3318-1 2000-02-03


GEMA-SD-0150-3319-1 2000-05-18


GEMA-SD-0150-3320-1 2000-09-29

Document release number 3.x not used.


GEMA-SD-0150-3440-1 2000-12-04


GEMA-SD-0150-3441-1 2001-02-22


GEMA-SD-0150-3442-1 2001-05-02


Part 1: Overview (OV)

Release Changes Date

1 initial revision (Rainbow® 3.3) 1999-05-31

1.1 part number introduced; page numbers include part number; text unchanged 1999-06-30

1.2 "ZDR" added 1999-08-03

1.3 new Display Manager window (image includes legend) 1999-09-13

1.4 new Radar Manager window and Display Manager window (message textchanged)

2000-01-14

1.5 new Display Manager window (revised buttons) 2000-02-03

1.6 "Rainbow®" instead of "Rainbow" 2000-05-18

Document release numbers 2.x, 3.x not used.

4.0 initial revision (Rainbow® 3.4) 2000-12-04

4.1 new images 2001-02-22

4.2 message logger 2001-05-02

Part 2: Supervisor Manager (SM)




1.2 "Help" removed; "Print" added 2000-01-14




4.1 "Show Version Info" added; Remote processes/displays removed 2001-02-22


Part 3: Radar Manager (RM)



1.1 Offline Processing Tool added. 1999-06-08


1.3 scan and scheduler worksheet: RCL version; ZDR added 1999-08-06

1.4 VIR, SMV, SHR, PRT added 1999-11-25

1.5 Offline processing tool and FTP dissemination tool changed 1999-12-14


1.7 "Conditional Scheduler" added 2000-02-03

1.8 "Rainbow®" instead of "Rainbow"; figures actualised; "FTP DisseminationTool" eliminated (belongs now to Part 6)

2000-05-18

1.9 Hybrid Scan Scheduling added 2000-09-29



4.1 Archive Configuration removedAutocalibration Tool removedOffline Processing Editor added

2001-02-22

4.2 message logger; new products added (SWI, MBD, MESO_2, SSA_2) 2001-05-02

Part 4: Display Manager (DM)


1 initial revision (Raionbow® 3.3) 1999-05-31


1.2 new Display Manager window (image includes legend) 1999-09-13


1.4 new Display Manager window; revised buttons 2000-02-03

1.5 "Rainbow®" instead of "Rainbow"; figures actualised 2000-05-18


4.0 initial revision (Rainbow® 3.4); underlay map added (chapter 4.3.4) 2000-12-04

4.1 underlay map orientation adjustable (chapter 4.3.4)new Display Manager window; revised buttons

2001-02-22


Part 5: Rainbow Utilities (RU)



1.1 Command Line Utility (rain_cmd) added. 1999-06-08


1.3 "RainNordrad" added 1999-08-03

1.4 "RainCron" added 2000-01-19

1.5 "Rainbow®" instead of "Rainbow"; "FTP Dissemination Utility" added (formerplaced in Part 3)

2000-05-18



4.1 RainGorn: BUFR version 1.84RainNetconf: removedBBC: configuration file name changedRainNordrad: configuration file name changed

2001-02-22

4.2 RainLog added 2001-05-02

Part 6: Rainbow Configuration Files (RCF)







4.1 files replaced by new ones 2001-02-22

4.2 files replaced/added 2001-04-05

Documents

Rainbow Operator's Manual Vol. 1radar.irimo.ir/images/file/RainbowApplication_4_2.pdf · Rainbow® Operator's Manual • Volume 1 (General Description) Overview Gematronik GmbH •