Configuring Integrator and Runways Utility - runways.conf

Create the directory /usr/iris_data/tdwr

You must have root privilege for this step. The tdwr directory can exist anywhere on the workstation that runs the Integrator. However, we recommend that you put it in the same place that you put the IRIS_PRODUCT product directory.

For a standard installation this is in a directory called /usr/iris_data. This may be different on your system. To see the location of the product directory check /usr/sigmet/config/profile.

To make the tdwr directory, log in as root or become the super user and type:

# cd /usr/iris_data
# mkdir tdwr

Set the privileges for the directory to match the other directories (do an ls –ll to see how the other directories are set). For a standard installation type:

# chown operator tdwr
# chgrp users tdwr
# chmod 777

Install the runways.conf file

The runways.conf file is kept in the /$IRIS_ROOT/config directory (usually /etc/vaisala/irisrda).

Check if the file exists in this directory. Log in as operator and type:

$ cd /etc/vaisala/irisrda
$ ls

Check that the runways.conf file is in the list. If it is not, copy the template as follows:

$ cp /usr/sigmet/config_template/init/runways.conf /usr/sigmet/config

Edit the runways.conf file

Edit the runways.conf file (use vi, emacs, or your ASCII text editor). The file is shown below:

# File: ${IRIS_CONFIG}runways.conf
# Contains configuration information for the TDWR/LLWAS integration
# algorithm  and the runways utility.
# Number of runways to define: COUNT 3
# For each runways: Primary direction, Secondary direction, default direction.
# The default direction is the direction to use at powerup until changed
# manually  by runways.

RUNWAY 1 33- 15- LLWAS

RUNWAY 2 36R 18L LLWAS

RUNWAY 3 36L 18R LLWAS

# Uncomment this if you want all corridors reported out of integration.
#DONT_FILTER_RUNWAYS
# Turn logging on, choices are FILE or TERM or BOTH or NONE LOG BOTH
# Define input related info:
# Socket port; Directory; Timeout to consider input data stale

IRIS_IN 30726

IRIS_IN_DIR /usr/iris_data/tdwr/

IRIS_IN_TIME 120

# Define output related info:
# Socket host and port; Directory;
# Timeout to retransmit output even with no changes

IRIS_OUT cyclone 30725

IRIS_OUT_DIR /usr/iris_data/product/

IRIS_OUT_TIME 60

# Define LLWAS input related info:
#LLWAS_IN 30727
# Since the LLWAS input does not contain sitename or lat/lon. These
# need to be specified to handle the case where IRIS input is lost.
# For systems with no LLWAS input, it is recommended that you comment
# this whole section off.

# Specify radar lat and lon in signed degrees. Negative is south latitude, or
# West longitude.

RADAR_LATLON 43.00 -71.00

# If you want to take the latlon from the IRIS input, if  available, then
# comment out this line.

ALWAYS_SET_LATLON

# Specify desired radar sitename. Max 16 chars, requires quotes if you
# have imbedded whitespace.

RADAR_SITENAME "THIS IS A TEST"

# If you want to take the sitename from the IRIS input, if available, then
# comment out this line.

ALWAYS_SET_SITENAME

# List of users who are allowed to operate the runways utility.

OPERATORS operator

# End of file

The lines in the file are described in detail below:

• COUNT 3

  This is the number of physical runways, that is, strips of concrete.

• RUNWAY 2 36R 18L LLWAS

  For each runway, an arbitrary number is assigned (for example, 1, 2 and 3). These numbers should be sequential starting from 1.

  The names for each runway are then specified in the next two fields (for example, 36L and 18R).

  The last field is the default active runway when the software is first started. This can be either of the runway names or, if available, LLWAS. In the LLWAS case the runway direction specified in the LLWAS data is used when the Integrator is first started. If there are no LLWAS data, then the runway direction in the first field is used on start-up.

• # DONT_FILTER_RUNWAYS

  This line should generally be left commented (the # sign).

  If it is un-commented (# sign removed), the integrator passes on alerts for all arenas even if they are not associated with active runways.

  Filtering can still be performed by the ribbon displays, that is, ribsetup can be configured to exclude inactive runways. See Configuring Ribbon Display Software.

• # Turn logging on, choices are FILE or TERM or BOTH or NONE
  LOG BOTH

  • If you are starting the integrator from a terminal, set this to BOTH.

  • If you are starting the integrator automatically, set this to FILE. The log file is stored in var/log/irisrda.

• IRIS_IN 30726
  IRIS_IN_DIR /usr/iris_data/tdwr/

  These entries configure the characteristics of the input from IRIS to the Integrator.

  IRIS_IN is the socket port that is used by IRIS to notify the Integrator when a new product is sent. This must match the IRIS setup/output network device that has been configured to send products from IRIS to the Integrator. The default port is 30726.

  The IRIS_IN_DIR is the directory where IRIS sends products to the Integrator. This must match the directory configured at the beginning of this section and the directory configured in IRIS setup/output for the TDWR integrator. See Configuring IRIS Product Outputs for TDWR.

• IRIS_OUT cyclone 30725
  IRIS_OUT_DIR /usr/iris_data/product/

  These entries configure the characteristics of the output from the Integrator to IRIS.

  IRIS_OUT is the nodename (cyclone) and socket port (30725) where IRIS will receive the data. Usually this is the local workstation where the Integrator is running. The socket port should match the IRIS_NETRCV environment variable for the network receiver. This is set in the /usr/sigmet/config/profile.

  The IRIS_OUT_DIR is the directory where TDWR products are sent. This must match the directory configured for IRIS_PRODUCTS, typically /srv/iris_data/product. This is set in the /usr/sigmet/config/profile.

• IRIS_IN_TIME 120

  This is the time in seconds, after which, an input is considered to be "stale". For example, if the LLWAS stops sending data, the Integrator continues to use the old LLWAS data for 120 seconds (in the example). After 120 seconds, the old LLWAS data is not used to make new TDWR products.

• IRIS_OUT_TIME 60

  This is the maximum time between generation of TDWR products. A new TDWR product is made if one of the following happens:

  • A new input arrives.

  • The active runways configuration changes.

  • One of the inputs becomes stale (IRIS_IN_TIME times-out).

  • IRIS_OUT_TIME from the last TDWR product generation is exceeded.

  • The IRIS_OUT_TIME makes sure (in this example) that a TDWR product is created at least every 60 seconds provided there are valid inputs (data are not stale).

• LLWAS_IN 30727

  This is the socket port that is used by LLWAS to notify the Integrator when a new LLWAS data are available. If you do not have and LLWAS, comment this line by adding # to the beginning.

• <LLWAS Site Information>

  If you have an LLWAS system, you must specify the LAT/ LON of the radar and the sitename since these are not in the LLWAS header.

  This information is needed if the radar fails and the alerts are based on LLWAS alone. If you do not have an LLWAS, comment all lines of this section.

• OPERATORS operator controller>

  This controls access to the runways menu to the user ID's in the list. Note that anyone can view the runways menu, but only users in the list can change it.