rf siesta software user manual · siesta software components is contained in annex a. the version...

66
RF SIESTA software user manual Version V09-4 Robert G. Szeker Defence R&D Canada – Ottawa Contract Report DRDC Ottawa CR 2009-138 September 2009

Upload: others

Post on 04-Aug-2020

3 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

RF SIESTA software user manual Version V09-4 Robert G. Szeker

Defence R&D Canada – Ottawa Contract Report

DRDC Ottawa CR 2009-138 September 2009

Page 2: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the
Page 3: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

RF SIESTA software user manual Version V09-4

Robert G. Szeker nEW Technologies Inc. Prepared By: nEW Technologies Inc. 18 Pullman Avenue Ottawa, Ontario K2S 1C4 Contractor's Document Number: Contractor's Document Number: Contractor's Document Number: Contractor's Document Number: Contract Project Manager: PWGSC Contract Number: PWGSC Contract Number: PWGSC Contract Number: PWGSC Contract Number: W7714-060965/001/TOR CSA: Dr. Alan D. Thomson, Defence Scientist, 613-991-1877 The scientific or technical validity of this Contract Report is entirely the responsibility of the Contractor and the contents do not necessarily have the approval or endorsement of Defence R&D Canada.

Defence R&D Canada – Ottawa Contract Report DRDC Ottawa CR 2009-138 September 2009

Page 4: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

Scientific Authority

Original signed by Alan Thomson

Alan Thomson

Scientific Authority

Approved by

Original signed by Caroline Wilcox

Caroline Wilcox

Head, Radar Applications and Space Technologies Section

Approved for release by

Original signed by Brian Eatock

Brian Eatock

Chief Scientist, DRDC Ottawa

15aa

© Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2009

© Sa Majesté la Reine (en droit du Canada), telle que représentée par le ministre de la Défense nationale, 2009

Page 5: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 i

Abstract ……..

This report contains the Software User Manual (SUM) for the RF SIESTA software. This document contains all information necessary to install and operate RF SIESTA in a stand-alone or networked configuration. The SUM also explains the limitations of the current software version and describes the changes that should be implemented in the next software version.

Résumé ….....

Le présent rapport contient le manuel d’utilisation du logiciel RF SIESTA. Ce document contient toutes les informations nécessaires pour installer et exploiter le logiciel RF SIESTA dans une configuration autonome ou réseau. Le manuel explique également les limitations de la version actuelle du logiciel et décrit les modifications qui devraient être mises en oeuvre dans la prochaine version du logiciel.

Page 6: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

ii DRDC Ottawa CR 2009-138

This page intentionally left blank.

Page 7: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 iii

Executive summary

RF SIESTA software user manual: Version V09-4 Robert G. Szeker; DRDC Ottawa CR 2009-138; Defence R&D Canada – Ottawa; September 2009.

Introduction: The Northern Watch Technology Demonstration Project (TDP) plans to make use of the radio frequency (RF) component of the Shipborne Integrated Environment System for Tactics and Awareness (SIESTA) to predict the performance of a network of navigation radars and to aid in the definition of the configuration of a navigation radar network to be used to monitor narrow bodies of water. This report summarizes the changes made to the RF component of SIESTA and serves as a Software User Manual.

Results: A number of modifications to the RF SIESTA software have been made, on a level of effort basis, to prepare it for use within the Northern Watch TDP. However, further effort was required to define and debug the new features that have been incorporated, as well as to complete the software documentation.

Future plans: Currently there are no future plans for incorporating software modifications to RF SIESTA. The Software User Manual does make recommendation for specific software changes that should be implemented at a later date. These recommendations are contained in the various sections of this document. Ideas for additional display products have been proposed by the Scientific Authority.

Page 8: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

iv DRDC Ottawa CR 2009-138

Sommaire .....

RF SIESTA software user manual: Version V09-4 Robert G. Szeker; DRDC Ottawa CR 2009-138; R & D pour la défense Canada – Ottawa; Septembre 2009.

Introduction : Dans le cadre du Projet de démonstration de technologies (PDT) de surveillance du Nord, il est prévu de faire usage de la composante RF (radiofréquence) du SIESTA (système embarqué d'environnement intégré de tactique et de connaissance de la situation) afin de prévoir les performances d'un réseau de radars de navigation et d'aider à définir la configuration d'un réseau de radars de navigation qui sera utilisé pour surveiller des passages maritimes étroits. Le présent rapport résume les modifications apportées à la composante RF du SIESTA et constitue un manuel d’utilisation du logiciel.

Résultats : Un certain nombre de modifications fondées sur le niveau d’effort ont été apportées au logiciel SIESTA RF en vue de le préparer pour une utilisation dans le cadre du PDT de surveillance du Nord. Toutefois, des efforts supplémentaires étaient nécessaires pour définir et déboguer les nouvelles fonctionnalités qui ont été intégrées, et pour compléter la documentation du logiciel.

Recherches futures : Actuellement, il n'existe pas de plans pour l'intégration de modifications du logiciel SIESTA RF. Toutefois, le manuel d’utilisation du logiciel présente des recommandations de modifications logicielles particulières qui devraient être mises en oeuvre à une date ultérieure. Ces recommandations sont contenues dans les diverses sections du présent document. Des idées pour d’autres produits d'affichage ont été proposées par le responsable scientifique.

Page 9: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 v

Table of contents

Abstract …….. ................................................................................................................................. i Résumé …..... ................................................................................................................................... i Executive summary ....................................................................................................................... iii Sommaire ....................................................................................................................................... iv Table of contents ............................................................................................................................ v List of figures ............................................................................................................................... vii List of tables .................................................................................................................................. ix 1 Introduction.............................................................................................................................. 1

1.1 Purpose .......................................................................................................................... 1 2 Software Components............................................................................................................... 2

2.1 Software Components Description................................................................................ 2 3 Software Installation and Configuration................................................................................... 3

3.1 Stand-alone Configuration............................................................................................. 5 3.2 Networked Configuration.............................................................................................. 8

4 Building the IDL Project......................................................................................................... 11 5 Reconfiguring IDL Executable Images .................................................................................. 15 6 Launching Slave Processes..................................................................................................... 16 7 Running RF SIESTA .............................................................................................................. 18

7.1 The Program Panel ...................................................................................................... 18 7.1.1 The RUN Pushbutton .................................................................................... 19 7.1.2 The SET Pushbutton ..................................................................................... 20 7.1.3 The COMPOSITE Pushbutton...................................................................... 21

7.2 The Operating Mode and Run Mode Panel ................................................................. 26 7.2.1 Operating Mode ............................................................................................ 26 7.2.2 Run Mode...................................................................................................... 26 7.2.3 Ship Visibility Calculations .......................................................................... 27 7.2.4 Point Target................................................................................................... 27

7.3 The Radar Location Panel ........................................................................................... 27 7.4 The Environment Panel ............................................................................................... 28 7.5 The Measurement Panel .............................................................................................. 29

7.5.1 Azimuth......................................................................................................... 29 7.5.2 Height ASL ................................................................................................... 30 7.5.3 Target Radial Speed ...................................................................................... 31

7.6 The Grid Panel............................................................................................................. 31 7.6.1 Range ............................................................................................................ 31 7.6.2 Range Increment ........................................................................................... 31

Page 10: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

vi DRDC Ottawa CR 2009-138

7.6.3 Height............................................................................................................ 31 7.6.4 Height Increment........................................................................................... 32

7.7 The CDF Panel ............................................................................................................ 32 8 Terrain Elevation Data Files ................................................................................................... 35

8.1 Water-only Elevation Data Files ................................................................................. 38 9 Rebuilding the Slave Processor Code ..................................................................................... 39 10 Rebuilding the APM DLL ...................................................................................................... 40 Annex A .. RF SIESTA Software Components ............................................................................. 43 List of symbols/abbreviations/acronyms/initialisms .................................................................... 48 Distribution list ............................................................................................................................. 49

Page 11: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 vii

List of figures

Figure 1: RF SIESTA top-level directory structure. ...................................................................... 3 Figure 2: RF SIESTA DATA subdirectory structure. .................................................................... 4 Figure 3: Setting the path environment variable for DFORRT.DLL. ............................................ 5 Figure 4: Distributed processing on a stand-alone computer. ....................................................... 5 Figure 5: SLAVES subdirectory structure .................................................................................... 6 Figure 6: SLAVES subdirectory configuration on a stand-alone computer.................................. 7 Figure 7: Distributed processing on a networked computer system.............................................. 8 Figure 8: Mapping the OUTPUT directory on a networked slave machine.................................. 9 Figure 9: SLAVES subdirectory configuration on a networked computer. ................................ 10 Figure 10: IDL development environment. ................................................................................. 11 Figure 11: IDL project groups and files. ..................................................................................... 12 Figure 12: IDL project options panel........................................................................................... 13 Figure 13: IDL preferences panel................................................................................................ 13 Figure 14: Setting IDL executable stack size using Editbin........................................................ 15 Figure 15: Launching the slave processes. .................................................................................. 16 Figure 16: RF SIESTA main control panel. ................................................................................ 18 Figure 17: The program panel ..................................................................................................... 18 Figure 18: Missing file warning message.................................................................................... 19 Figure 19: RF SIESTA display using existing data.................................................................... 19 Figure 20: The secondary control panel ...................................................................................... 20 Figure 21: The CP program control menu................................................................................... 21 Figure 22: The composite product height window...................................................................... 22 Figure 23: Composite product file selection window.................................................................. 23 Figure 24: Composite product contour levels window................................................................ 23 Figure 25: The composite product plot. ...................................................................................... 24 Figure 26: The save CP dialog box. ............................................................................................ 25 Figure 27: The save composite minimum RCS dialog box......................................................... 25 Figure 28: The operating mode and run mode panel................................................................... 26 Figure 29: The radar location panel............................................................................................. 28 Figure 30: The landcover selection window ............................................................................... 28

Page 12: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

viii DRDC Ottawa CR 2009-138

Figure 31: Missing landcover file error message. ....................................................................... 29 Figure 32: The measurement panel. ............................................................................................ 29 Figure 33: Typical RHI plot. ....................................................................................................... 30 Figure 34: Typical CAPPI plot.................................................................................................... 30 Figure 35: The grid panel. ........................................................................................................... 31 Figure 36: The CDF panel........................................................................................................... 32 Figure 37: The new CDF filename advisory message................................................................. 33 Figure 38: An example CDF file. ................................................................................................ 33 Figure 39: CDF display, environmental and radar parameters.................................................... 34 Figure 40: Terrain elevation data file conversion........................................................................ 35 Figure 41: New terrain elevation data file message. ................................................................... 36 Figure 42: Terrain elevation data file deletion option. ................................................................ 36 Figure 43: CDED geographic areas............................................................................................. 37 Figure 44: DTED directory structure. ......................................................................................... 37 Figure 45: Elevation data cell array............................................................................................. 38 Figure 46: The Visual FORTRAN development environment. .................................................. 41

Page 13: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 ix

List of tables

Table 1: The DATA directory contents ......................................................................................... 2

Page 14: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

x DRDC Ottawa CR 2009-138

This page intentionally left blank.

Page 15: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 1

1 Introduction

1.1 Purpose

This document contains the Software User’s Manual (SUM) for the installation and operation of the RF portion of the SIESTA software. The purpose of this document is to provide sufficient level of information to a first-time user of RF SIESTA to successfully install and operate the software on a stand-alone or networked computer platform.

Page 16: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

2 DRDC Ottawa CR 2009-138

2 Software Components

2.1 Software Components Description

The current version of the RF SIESTA software is V09-4. Version V09-4 consists of several IDL procedures (*.pro) and component files, organized into directories. A complete list of RF SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the software changes made to the file, the date of the change and the author’s initials.

The RF SIESTA software is distributed on several CDs. CD #1 contains the software components. Additional CDs numbered 2, 3, etc, contain the data files. The DATA directory contains the subdirectories listed in the table below.

Directory Subdirectory Description DATA CDF Common data files

DTED Terrain elevation data files HPAC Meteorological data files IMAGES Image files LANDCOVER Land cover data files META Weather radar data files QUEST Ship radar cross-section data files

Table 1: The DATA directory contents

The various files in the DATA subdirectories are not listed above as their content varies. For example, RF SIESTA can create new CDF files in the DATA/CDF directory if this option is enabled.

Page 17: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 3

3 Software Installation and Configuration

The installation of the RF SIESTA V09-4 software requires IDL version 6.4 to be installed and licensed. IDL versions 7.0 or higher are not currently supported. The computer must be running the MS Windows 2000, XP or XP Professional operating system.

Create a root directory and copy the contents of CD #1 to it, then copy the contents of the data CDs. For example, if the root directory created is C:/SIESTA/NWTDP the directory structure should be as shown in the following figure:

Figure 1: RF SIESTA top-level directory structure.

In addition to the directories copied from the distribution CDs, create an empty subdirectory named ‘OUTPUT’ shown in Figure 1. The ‘OUTPUT’ directory is where RF SIESTA generates interim and final results. The ‘OUTPUT’ directory is also used to communicate with ‘slave’ CPUs both in stand-alone and networked modes of operation. The use of networked and stand-alone modes of operation is explained later.

After installation of the distribution CDs is complete, the DATA subdirectory should contain the subdirectories shown in the following figure:

Page 18: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

4 DRDC Ottawa CR 2009-138

Figure 2: RF SIESTA DATA subdirectory structure.

The DTED directory contains the terrain elevation data files used by RF SIESTA and may contain subdirectories. The top-level DTED directory contains the elevation data files converted to a special format and used by the program, while the subdirectories are used to store original raw elevation data files. Raw elevation data files are usually loaded from a CD or downloaded from a website such as GeoBase. For a more complete description of elevation data file management see Section 8.0.

During execution, the RF SIESTA software calls the Advanced Propagation Model (APM) dynamically linked library (DLL) module in its calculations. When the APM DLL module executes, it requires that a file called DFORRT.DLL exists. The DFORRT.DLL file should therefore be copied from the distribution CD to the top-level directory and an environment variable named ‘Path’ defined to it.

For example if the directory structure is set up as shown in Figure 2, copy DFORRT.DLL to the SIESTA directory. Using the Control Panel, go to Environment Variables and add a variable named ‘Path’ pointing to C:\SIESTA as shown in the following figure:

Page 19: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 5

Figure 3: Setting the path environment variable for DFORRT.DLL.

3.1 Stand-alone Configuration

The RF SIESTA software is designed to take advantage of distributed processing, making use of all CPUs of a multi-processor computer. Using distributed processing various software tasks are partitioned and assigned to different CPUs. Distributed processing greatly reduces the overall execution time. This concept is illustrated in Figure 4:

Figure 4: Distributed processing on a stand-alone computer.

CPU0 CPU1 CPU2 CPU3

OUTPUT SUBDIRECTORY

MASTER SLAVE SLAVE SLAVE

Page 20: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

6 DRDC Ottawa CR 2009-138

Figure 4 shows a hypothetical quad-CPU computer in which CPU 0 is designated the ‘master’ and CPUs 1, 2 and 3 are ‘slaves’. The master CPU controls the overall RF SIESTA program execution and partitions tasks to the slave CPUs. All communication is done through the OUTPUT directory using token passing. For example, a slave will not start to process a task until a specific token arrives from the master, and the master will wait until tokens are received from the slaves before continuing.

Distributed processing is vital for efficient operation of RF SIESTA. In order to enable distributed processing, the SLAVES subdirectory shown in Figure 1 needs to be reconfigured according to the number of available CPUs.

After installation from CD, the SLAVES subdirectory structure is shown below:

SLAVES launch_slaves.pro slave_processor.pro launch_slaves.sav slave_processor.sav slaves.pref idlrt_rgs_100mbstk.exe Readme.txt APM SBAPM2303s.dll DATA QUEST ShipRCS.dat LWKD input.txt Lwkd.ini LWKD.INF LWKD_820.exe OUTPUT

Figure 5: SLAVES subdirectory structure

For a multi-processor machine, the SLAVES subdirectory shown above needs to be reconfigured as follows. For each slave CPU create a subdirectory named S1, S2, S3, etc and copy the APM, DATA, LWKD and OUTPUT subdirectories to each one. This is done so that each slave CPU uses its own private copy of the APM DLL and executables images.

For example, for a quad-CPU machine the SLAVES subdirectory should be reconfigured as shown in the following figure:

Page 21: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 7

SLAVES launch_slaves.pro slave_processor.pro launch_slaves.sav slave_processor.sav slaves.pref idlrt_rgs_100mbstk.exe Readme.txt S1 APM SBAPM2303_1.dll DATA QUEST ShipRCS.dat LWKD input.txt Lwkd.ini LWKD.INF LWKD_820.exe OUTPUT S2 APM SBAPM2303_2.dll DATA QUEST ShipRCS.dat LWKD input.txt Lwkd.ini LWKD.INF LWKD_820.exe OUTPUT S3 APM SBAPM2303_3.dll DATA QUEST ShipRCS.dat LWKD input.txt Lwkd.ini LWKD.INF LWKD_820.exe OUTPUT

Figure 6: SLAVES subdirectory configuration on a stand-alone computer.

Subdirectory for slave CPU #1

Subdirectory for slave CPU #2

Renamed APM DLL file

Subdirectory for slave CPU #3

Page 22: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

8 DRDC Ottawa CR 2009-138

When the RF SIESTA software runs, it queries the OS to determine the number of CPUs available. It then spawns the slave_processor.sav program repeatedly for each CPU found. Each slave processor task thus started runs in a single-threaded mode, executing on one and only one CPU. Single-threaded mode is enabled via the slaves.pref file.

In order to minimize the chance of shared memory conflicts, the APM DLL for each slave must be renamed as SBAPM2303_1.dll, SBAPM2303_2.dll, etc, respectively for each CPU.

3.2 Networked Configuration

The RF SIESTA software is designed to make use of distributed processing using a networked system of computers, thereby greatly increasing the total number of slave CPUs available and further reducing overall execution time. This concept is illustrated in Figure 7:

Figure 7: Distributed processing on a networked computer system.

Figure 7 shows a hypothetical system of 4 computers on an Ethernet connection. There is no limit on the number of computers that can be interconnected in this manner.

The RF SIESTA software executes on CPU 0 of the master. The other 3 networked machines are called ‘slave machines’ who’s CPUs are under control of the master. Slave machines 1 and 2 are quad-CPU machines while slave machine 3 has two CPUs. In this example, the master has a total of 13 slave CPUs available for distributed processing. All communication is done through the OUTPUT directory of the master machine using token passing. The OUTPUT directory on the master must be set to ‘shared’ so that it is accessible by all machines on the network.

MASTER SLAVE 1 SLAVE 2 SLAVE 3

CPU 1

CPU 0

CPU 2

CPU 3

OUTPUT

CPU 0

CPU 1

CPU 0

CPU 1

CPU 2

CPU 3

CPU 2

CPU 3

CPU 0

CPU 1

ETHERNET

Page 23: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 9

In a networked configuration with numerous slave machines participating, the SLAVE directory structure should be set up on the master machine as described in Section 3.1. Each slave CPU on the master should have its own directory named S1, S2, S3, etc. In addition, the SLAVE directory should be copied to each slave machine. For example, if slave machine 1 is a quad-CPU machine the SLAVES subdirectory should be configured as shown in Figure 9.

All CPUs of a networked slave machine are effectively slave CPUs and the subdirectories must be numbered as S0, S1, S2, etc. Note also that each CPU has its own local OUTPUT directory, which are used to store intermediate results.

As network computers have no way of knowing who the RF SIESTA master is on the network or where it’s located, the user must map the master’s shared OUTPUT directory to a drive on each slave computer. The ‘Z’ drive was chosen as the master’s OUTPUT directory.

Consider an example in which Pc28172 is the master and Pc28171 is a slave machine and both PCs are on the same network. If Pc28172 has a shared OUTPUT directory, then map it as the ‘Z’ drive on Pc28171 as shown in Figure 8 below:

Figure 8: Mapping the OUTPUT directory on a networked slave machine.

Page 24: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

10 DRDC Ottawa CR 2009-138

SLAVES S0 APM SBAPM2303_0.dll DATA QUEST ShipRCS.dat LWKD input.txt Lwkd.ini LWKD.INF LWKD_820.exe OUTPUT S1 APM SBAPM2303_1.dll DATA QUEST ShipRCS.dat LWKD input.txt Lwkd.ini LWKD.INF LWKD_820.exe OUTPUT S2 APM SBAPM2303_2.dll DATA QUEST ShipRCS.dat LWKD input.txt Lwkd.ini LWKD.INF LWKD_820.exe OUTPUT S3 APM SBAPM2303_3.dll DATA QUEST ShipRCS.dat LWKD input.txt Lwkd.ini LWKD.INF LWKD_820.exe OUTPUT

Figure 9: SLAVES subdirectory configuration on a networked computer.

Subdirectory for slave CPU #1

Subdirectory for slave CPU #2

Subdirectory for slave CPU #3

Renamed APM DLL file

Subdirectory for slave CPU #0

Page 25: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 11

4 Building the IDL Project

Once the RF SIESTA source files, data files and executable images have been installed from the distribution CDs and the system has been configured for the required mode of operation (either stand-alone or networked), launch IDL on the master and build the project. IDL version 6.4 should be installed and licensed on the master before this step, if not already done so. In a networked mode of operation, slave machines do not require a fully licensed version of IDL to be installed. Slave machines require only a copy of the IDL real-time executable image idlrt_rgs_100mbstk.exe located in the SLAVE directory.

Click on File->New->Project and select a project name, for example NWTDP.prj. IDL will automatically assign default groups named ‘Source’, ‘GUI’, ‘Data’, ‘Images’, and ‘Other’ to the new project. These groups should be deleted and new ones created by clicking on Project->Groups. Create the ‘APM’, ‘GUI’, ‘SV’, ‘SUPPORT’, ‘DTED’ and ‘INTEGRATION’ groups as shown in Figure 10:

Figure 10: IDL development environment.

Click on Project->Add/Remove Files and add the source files (*.pro files) to each group from the corresponding source directory. Do not include the common_block.pro file in the GUI group. This file must exist in a subdirectory but is not included in the project. When all files have been added the project should be as shown in Figure 11.

Page 26: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

12 DRDC Ottawa CR 2009-138

Note that Figure 11 shows the left-hand side panel of Figure 10 repeated twice in order to display all files contained in each project group.

Click on the ‘Build Order’ tab to show the order in which IDL will compile source files. If IDL reports errors during the project build such as undefined functions, the build order may have to be changed. Make sure that all source files beginning with ‘Define’ such as Define.pro, DefineAntPattern.pro, etc, are at the top of the build order list.

Figure 11: IDL project groups and files.

Next click on Project->Options and ensure that the ‘Run Command’ field contains ‘mainSad’. This is the program’s entry point and is the first procedure IDL executes when RF SIESTA is started. Figure 12 shows the Project Options panel.

Page 27: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 13

Figure 12: IDL project options panel.

Click on File->Preferences->Path and configure it as shown in Figure 13. The path used by IDL should include the project’s root directory. A check should be added to the path to search all subdirectories. Click on ‘Apply’ then on ‘OK’ to close the window.

Figure 13: IDL preferences panel.

The global variables used by RF SIESTA are defined in the common_block.pro file and initialized in the common_defs.pro file. Open common_defs.pro located in the GUI group by double clicking on it. Find the gDirectory global variable and make sure that it points to the installation path. For example, if the RF SIESTA files were installed in C:\SIESTA\NWTDP, then set:

Page 28: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

14 DRDC Ottawa CR 2009-138

gDirectory = ‘C:\SIESTA\NWTDP\’

At this point save the project by clicking on File->Save Project, and then build the project by clicking on Project->Compile->All Files. The IDL ‘Output Log’ window will show each source file as it is compiled. If any error occurs during the build, reset the IDL session by clicking on Run->Reset and recompile the project. If there are undefined functions, the project build order may need to be changed as explained above.

Page 29: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 15

5 Reconfiguring IDL Executable Images

For correct operation of RF SIESTA, it is required to modify the default IDL executable images idlde.exe and idlrt.exe supplied with the IDL 6.4 installation. These programs are the IDL development environment and the real-time executive. Since RF SIESTA generally works with very large array sizes, the default stack size assigned to these programs was found to be insufficient. In cases when large radar ranges and/or heights are used in calculations, the APM DLL will crash the IDL session if the stack sizes are not increased.

A minimum stack size of 100-Mbytes is required for both programs. The MS ‘Editbin’ utility program can be used to modify the stack sizes of the IDL executables. The ‘Editbin’ utility is available in Microsoft Visual Studio Version 9.0.

To change the stack size available to idldr.exe and idlrt.exe, open a MS-DOS window or Cygwin session if available, change directory to the IDL installation and use ‘Editbin’ to modify the stack sizes, as shown in Figure 11. The idlde.exe and idlrt.exe files are normally be located in C:\Program Files\ITT\IDL64\bin\bin.x86.

Figure 14: Setting IDL executable stack size using Editbin.

To modify the stack size to 100-MBytes, enter the command:

$ editbin idlde.exe /stack:0x6400000

Before modifying the stack sizes of the IDL executables, it is recommended to make backup copies of the original idlde.exe and idlrt.exe files. Note that in the SLAVES subdirectory the modified idlrt.exe file has been named idlrt_rgs_100mbstk.exe for easy identification.

Page 30: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

16 DRDC Ottawa CR 2009-138

6 Launching Slave Processes

If RF SIESTA is to operate in a networked configuration, logon to each network machine and start the slave processes. It is assumed that all slave machines have been configured previously as explained in Section 3.2. If operating in a stand-alone configuration no action needs to be taken, as the master will start the slave processes automatically.

To start the slave processes, double click on the launch_slaves.sav file on the slave machine. The number of CPUs available for processing is determined and an image of the slave_processor program is spawned in a single-threaded mode.

For example, Figure 15 shows the slave processes being launched on a PC having 8 CPUs. Each slave process opens a status message window. The title of each status message window shows the computer ID of the slave machine and CPU number. In this example the slave processes are waiting on a command from the master to begin processing their first task.

Figure 15: Launching the slave processes.

Page 31: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 17

As explained in Section 3.2, all communications between the master and slave machines are done through the OUTPUT directory, which is mapped as the ‘Z’ drive on each slave. When the correct token (a zero-length file) is written by the master to OUTPUT, the slaves perform a particular task. The results of the task are then sent to the OUTPUT directory across the network. In this manner an unlimited number of slave machines can partake in the calculations, restricted only by the network throughput.

The slave processes run in a ‘forever’ loop. When all RF SIESTA calculations have been completed, the slaves ready themselves to perform a new set of tasks instead of exiting. If anything goes wrong during processing on the master, the master can command the slave processes to reset to the start of the loop.

At the end of the session, the user must manually close the slave processes. Right clicking on the IDL icon in the Windows taskbar and clicking on ‘Close Group’ closes all slave processes.

Page 32: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

18 DRDC Ottawa CR 2009-138

7 Running RF SIESTA

In the previous sections the RF SIESTA software was installed from CDs and rebuilt, and some prerequisite steps were carried out. The project is now ready to be run.

Click on Project->Run to open the RF SIESTA Main Control Panel (MCP) shown in Figure 16:

Figure 16: RF SIESTA main control panel.

The MCP consists of 7 panels. These are ‘PROGRAM’, ‘OPERATING MODE’, ‘RADAR LOCATION’, ‘ENVIRONMENT’, ‘MEASUREMENT’, ‘GRID’, and ‘CDF’. There is also a window used to display a plan view of the radar’s location. The following sections describe the function of each of these panels.

7.1 The Program Panel

The program panel contains the ‘RUN’, ‘SET’, ‘COMPOSITE’, and ‘EXIT’ pushbuttons. The following sections describe the operation of each.

Figure 17: The program panel

Page 33: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 19

7.1.1 The RUN Pushbutton

Clicking on the ‘RUN’ pushbutton will start the execution of RF SIESTA with the current, default settings of the MCP. By default RF SIESTA starts in the ‘Use existing data’ operating mode, as shown in the next (Operating Mode) panel.1 This mode uses the results of a previous set of calculations, which reside in the OUTPUT directory.

If no previous results exist then the OUTPUT directory will be empty. RF SIESTA will generate the following type of warning message and return.

Figure 18: Missing file warning message.

If results from a previous SIESTA run exist in the OUTPUT directory, the program will run and generate the displays similar to the ones shown in Figure 19:

Figure 19: RF SIESTA display using existing data.

1 RF SIESTA can be set to start in the ‘Run APM’ operating mode by clearing the gRunMode variable in the common_defs.pro file.

Page 34: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

20 DRDC Ottawa CR 2009-138

RF SIESTA generates the left and right-hand displays showing the CAPPI plots of the minimum RCS required for target detection. By default the LHS display is shown in linear scale, while the RHS display is full scale. The pull down menu buttons can be used to change the display parameters such as the plot type, plot quantity, scale, color, etc.

7.1.2 The SET Pushbutton

The ‘SET’ pushbutton is disabled when the operating mode is ‘Use existing data’. The ‘SET’ pushbutton is only enabled when the operating mode is ‘Run APM’, that is when a new set of calculations is commanded.

In this case the ‘SET’ pushbutton opens the Secondary Control Panel (SCP), allowing the user to redefine the parameters initialized in common_defs.pro. Figure 20 shows the SCP after the ‘SET’ pushbutton is clicked.

Figure 20: The secondary control panel

The SCP allows various radar and meteorological parameters to be changed. When the panel is first opened using the ‘SET’ pushbutton, the values initialized in common_defs.pro are shown. The values entered by the user are limited to be within acceptable ranges. For example, entering a negative value for the radar antenna height will set this variable to 0-metres.

Page 35: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 21

The SCP also allows the user to specify the weather radar data and HPAC data files used, as well as the timestamp. The timestamp is used to annotate the LHS and RHS displays generated but also interact with the HPAC file used. For example, if the HPAC file specified is out-of-date, the time can set to any desired time by clicking on ‘Use forced time’ and setting a hypothetical time.

Clicking on ‘CANCEL’ simply closes the MCP without changes. Clicking on ‘APPLY’ overwrites the global parameters initialized in common_defs.pro with the new values specified.

7.1.3 The COMPOSITE Pushbutton

The ‘COMPOSITE’ pushbutton in the Program panel is used for generating a composite product (CP). This button is only available when the run mode is ‘Use existing data’. The ‘COMPOSITE’ button is not available when run mode is ‘Run APM’.

The composite product generated by the RF SIESTA program takes the results of several previous calculations and merges them into one. For example, if previous calculations have been made for radars at different locations, the CP function merges the arrays containing the minimum detectable radar cross-section of each location into a single array and generates a new display. The new display is called a composite image.

The operation of the CP function depends on previous results having been stored in common data files (CDFs). RF SIESTA only generates a new CDF if this feature is enabled. To create a CDF, the run mode must be set to ‘Run APM’ and a new CDF file name must be specified and enabled in the CDF panel.

Clicking on the ‘COMPOSITE’ pushbutton runs the CP generation program. The ‘Program control’ dropdown menu located in the upper left-hand corner allows the user to control CP generation.

Figure 21: The CP program control menu

The program control drop list menu displays the following options. Only the currently active selections are highlighted:

Page 36: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

22 DRDC Ottawa CR 2009-138

• Select target type • Specify product height • Select files • Generate composite • Save image to file • Exit

When ‘Select target type’ is clicked the user has a choice of selecting between point and surface target types. The target type for each RF SIESTA run can be specified in the Operating Mode panel. Once the target type has been selected, the ‘Specify product height’ option becomes available:

• Select target type • Specify product height • Select files • Generate composite • Save image to file • Exit

Clicking on ‘Specify product height’ opens up a window where the height in metres can be entered.

Figure 22: The composite product height window

Enter the required product height and press the ‘Apply’ button. The program will parse all CDF files contained in the DATA\CDF subdirectory and select only those that match the required target type and product height. Status messages are shown while the CDF files are parsed.

If CDF files were found that match the search criteria, the ‘Select files’ option becomes available:

• Select target type • Specify product height • Select files • Generate composite • Save image to file • Exit

Page 37: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 23

Clicking on ‘Select files’ opens the file selection window shown in Figure 23:

Figure 23: Composite product file selection window.

Select the CDF files to use for the CP and press ‘Apply’ when finished. After this step the CP is ready to be generated:

• Select target type • Specify product height • Select files • Generate composite • Save image to file • Exit

Clicking on ‘Generate composite’ opens a window in which the user can specify the lower and upper bounds of the contour levels. By varying the contour levels, the range over which the available colours are assigned can be specified.

Figure 24: Composite product contour levels window

Page 38: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

24 DRDC Ottawa CR 2009-138

Clicking on the ‘Apply’ button starts the composite product generation. The length of the generation process depends on the number of CDF files selected and internal array sizes of the minimum RCS data. In Figure 25, 3 CDFs are merged into a single composite product.

Figure 25: The composite product plot.

After the CP image generation is complete, the user can optionally save the image and the composite minimum detectable RCS array to files:

• Select target type • Specify product height • Select files • Generate composite • Save image to file • Exit

Clicking on ‘Save image to file’ opens the dialog box shown in Figure 26. The CP image can be saved as any image type such as GIF, JPG, BMP, etc. The user can select the path and filename.

Page 39: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 25

Figure 26: The save CP dialog box.

If the CP image is saved to a file, another dialog box opens to optionally save the composite minimum RCS data as well. This is shown in Figure 27:

Figure 27: The save composite minimum RCS dialog box.

The save path defaults to the OUTPUT directory and a default file name is generated. The file type is always an IDL save file (*.sav) and cannot be changed by the user. Note that the contents of the IDL save file can be extracted using the IDL restore command.

Page 40: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

26 DRDC Ottawa CR 2009-138

7.2 The Operating Mode and Run Mode Panel

The operating and run mode panel is shown in Figure 28:

Figure 28: The operating mode and run mode panel.

7.2.1 Operating Mode

The operating mode panel allows selection between ‘Auto’ and ‘Manual’ modes of operation. By default the operating mode is set to ‘Manual’ and should not be changed. The purpose of the ‘Auto’ mode is to enable execution of the RF SIESTA program under control of an external processor. (The ‘Auto’ mode was originally implemented for the SISWS project under which the SIESTA software development began).

7.2.2 Run Mode

The run mode panel allows selection between ‘Run APM’ and ‘Use existing data’. When ‘Run APM’ is selected and the RUN pushbutton is pressed in the Program panel, the program will clear the contents of the OUTPUT directory and execute the RF SIESTA program. The parameters used by RF SIESTA are as defined in common_defs.pro, some of which may be modified by the user in the MCP. Frequently changed parameters such as the radar’s position (latitude and longitude), land cover type, grid range, grid height, number of sectors, etc, can be modified using the MCP.

Page 41: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 27

When the ‘Run APM’ mode is selected the SET pushbutton becomes available in the Program panel. Pressing the SET pushbutton enables other parameters initialized in common_defs.pro to be changed via the SCP shown in Figure 20.

When the ‘Use exiting data’ mode is selected and the RUN pushbutton is pressed in the Program panel, the program uses the contents of the OUTPUT directory to regenerate the displays. If the OUTPUT directory is empty, a warning message is generated as shown in Figure 18. In the ‘Use existing data’ mode most of the MCP controls are disabled with the exception of the Measurement panel. This allows the user to specify how the displays should be recreated, notably the azimuth angle in degrees for RHI displays and the height above sea level in metres for the CAPPI displays.

7.2.3 Ship Visibility Calculations

The ship visibility (SV) calculations selector button is only available when the run mode is ‘Run APM’. It cannot be selected otherwise. If the SV calculations selector is checked, RF SIESTA will calculate own-ship visibility and generate the display. This feature has not been fully tested for RF SIESTA Version V09-4 and therefore should not be enabled.

7.2.4 Point Target

The point target selection is only available when the run mode is ‘Run APM’ and cannot be selected otherwise. When this box is checked, RF SIESTA will perform calculations for a point target, interpolating the propagation factor array for fractional height values if required, else calculations for a distributed surface target are performed. In the latter case, the propagation factor is calculated as the maximum value within the height layer from the surface to the specified measurement height.

7.3 The Radar Location Panel

The radar location panel of the MCP allows specification of the radar’s location in terms of latitude and longitude. The default location is specified in common_defs.pro using the gLatitude and gLongitude global variables. The latitude and longitude values are expressed as decimal quantities with an accuracy of 6 decimal places.

The user should ensure that RF SIESTA supports the radar location specified. Terrain elevation data files should exist in the DATA\DTED directory for the specified location else a warning message will be issued. Elevation data files management is discussed in Section 8.0.

Page 42: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

28 DRDC Ottawa CR 2009-138

Figure 29: The radar location panel.

7.4 The Environment Panel

The environment panel of the MCP allows specification of the land cover type. The landcover types can be selected by clicking on the text widget. This opens up a landcover selection window as shown in Figure 30.

Figure 30: The landcover selection window

Page 43: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 29

If the ‘Use landcover type’ box is checked, RF SIESTA will use the specified landcover type throughout. The program essentially creates the landcover files from the terrain elevation files. If the box is not checked, RF SIESTA assumes that geographic landcover files exist for the coverage area. If the required geographic landcover files do not exist, RF SIESTA will generate an error message and return.

Figure 31: Missing landcover file error message.

7.5 The Measurement Panel

The measurement panel of the MCP allows the measurement values to be specified. These include the azimuth, height ASL and number of sectors used. The target radial speed specification (Mach number) is also included in this panel.

Figure 32: The measurement panel.

7.5.1 Azimuth

The azimuth value specifies the azimuth angle in degrees for RHI type plots. Values can range from 0-degrees to 359-degrees. For example, Figure 33 shows an RHI plot at 0-degrees azimuth.

Page 44: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

30 DRDC Ottawa CR 2009-138

Figure 33: Typical RHI plot.

7.5.2 Height ASL

The height ASL value specifies the height in metres above sea level for CAPPI type plots. The value is stored in the gElevation global variable. Values can range from 0-metres up to the maximum grid height. For example, Figure 34 shows a CAPPI plot at a measurement height of 2-metres.

Figure 34: Typical CAPPI plot.

For both RHI and CAPPI type plots, the measurement azimuth and height values determine how the 3-dimensional radar cross-section array is processed. Using the values specified, slices are taken from the array along different dimensions and used to generate the displays.

Page 45: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 31

7.5.3 Target Radial Speed

The target radial speed value sets the value of the gTgtVelocity global variable. The radial speed is expressed as a Mach number. The Define.pro procedure sets the ‘target’ structure vt member (tar.vt) to the value of gTgtVelocity. The target radial velocity is used in the weather clutter power calculations.

7.6 The Grid Panel

The grid panel of the MCP contains the range, range increment, height and height increment controls as shown in Figure 35.

Figure 35: The grid panel.

7.6.1 Range

The range control sets the gMaxRange global variable, which is the maximum grid range in kilometres over which calculations are performed. The range can be varied from 10 to 150 km. Setting a large grid range increases the overall processing time.

7.6.2 Range Increment

The range increment control sets the gRangeInc global variable, which is the range grid spacing in kilometres, used by APM calculations. The Define.pro procedure sets the ‘control’ structure drF2 member (con.drF2) to the value of gRangeInc.

7.6.3 Height

The height control sets the gMaxHeight global variable, which is the maximum grid height in metres over which calculations are performed. The range can be varied between 1 to 1000

Page 46: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

32 DRDC Ottawa CR 2009-138

metres. The grid height control interacts with the Height ASL control of the measurement panel. Setting a large grid height increases the overall processing time.

7.6.4 Height Increment

The height increment control is currently disabled. The software always sets the gHeightInc global variable to a value of 1-metre. The Define.pro procedure sets the ‘control’ structure dhF2 member (con.dhF2) to the value of gHeightInc.

7.7 The CDF Panel The CDF panel allows the user to specify how Common Data Files (CDF) are used for I/O. The panel contains various input and control widgets as shown in Figure 36.

Figure 36: The CDF panel.

Clicking on the CDF panel’s Input and Output text widgets lists all files contained in the DATA\CDF directory. Clicking on any CDF file selects the file to be used for input or output.

Note that RF SIESTA Version V09-4 will not overwrite an existing CDF file; therefore a new CDF has to be specified if the user wishes to save program parameters and results.

The CDF panel verifies that the filename syntax is correct and that the filename does not already exist. For example, if a new filename ‘CDF_test’ is entered and the Enable box is checked, the following advisory message is output:

Page 47: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 33

Figure 37: The new CDF filename advisory message.

When the RUN button is pressed in the Program panel, RF SIESTA will run and generate the displays. The generated images and image data, as well as the radar, environmental and display parameters will be saved to the specified CDF file. A sample CDF file is shown in Figure 38. The CDF file can be opened using HDFView or similar software.

Figure 38: An example CDF file.

The CDF file contains several datasets. The LHS and RHS image and image data are saved to the following datasets respectively:

• Data Set / Sensor Performance / RF Sensor Performance Data / Visualized Results 1 • Data Set / Sensor Performance / RF Sensor Performance Data / Visualized Results 2

Page 48: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

34 DRDC Ottawa CR 2009-138

Display, environmental and radar parameters used by RF SIESTA are saved to the following datasets respectively:

• Data Set / System Internal Data / Display Parameters • Data Set / System Internal Data / Environmental Parameters • Data Set / System Internal Data / Radar Parameters

These datasets are shown in detail in the following figure. Note that the Composite Product (CP) generation function uses the ‘Point target’ element of the Display Parameters dataset to determine the target type. CDFs created with older versions of RF SIESTA do not include this dataset and will therefore not work with it. In order to make older CDFs compatible with RF SIESTA Version V09-4, the Display Parameters\Point target dataset can be added manually using HDFView or similar software. In this case, set Point target to 1 for a point target or set it to 0 for a surface target.

Figure 39: CDF display, environmental and radar parameters.

Page 49: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 35

8 Terrain Elevation Data Files

RF SIESTA Version V09-4 uses terrain elevation data files contained in the DATA\DTED subdirectory. Although the source of these data can be either CDED (Canadian Digital Elevation Data) or DTED (Digital Terrain Elevation Data) files, RF SIESTA will automatically convert these files to a special binary format. This is illustrated in the following diagram:

Figure 40: Terrain elevation data file conversion.

Using the process_DEM and process_DTD routines RF SIESTA automatically converts CDED or DTED2 files to a binary format that can be read quickly by IDL.3 The output of these routines is of the form:

Kxxx_Lyy.eln where: ‘K’ designates either west or east longitude (W or E), ‘xxx’ is the longitude of the SW corner of the cell, ‘L’ designates either north or south latitude (N or S), ‘yy’ is the latitude of the SW corner of the cell, ‘el’ designates ‘elevation’, and, ‘n’ represents the DTED / CDED level.

For example, the filename W062_N44.el1 contains the terrain elevation data for a cell with southwest corner located at -62.0 degrees longitude and +44.0 degrees latitude. The level 1 cell covers a 1-degree by 1-degree area and contains 1201 x 1201 elevation data points. In contrast, a level 2 cell contains 3601 x 3601 data points.

2 DTED file extensions must be in lower-case. 3 Level 1 CDED files are ASCII-coded and require approximately 45-seconds to read into an IDL array.

CDED FILES

DTED FILES

ELn FILES

Process_DEM routine

Process_DTD routine

Page 50: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

36 DRDC Ottawa CR 2009-138

The read_all_CDED.pro procedure calls the process_DEM.pro or process_DTD.pro procedures when it discovers raw DTED or CDED files in the DATA\DTED subdirectory. Therefore a user needs simply to copy new files to DATA\DTED to update RF SIESTA’s terrain elevation database. The terrain elevation files are then processed and the original files can be optionally deleted.

For example, if two CDED files 011d_0100_demw.dem and 011d_0100_deme.dem are copied to DATA\DTED and RF SIESTA program is ran, the following message will be generated:

Figure 41: New terrain elevation data file message.

If the user selects ‘Yes’ to convert the raw elevation data file(s), the following message is output:

Figure 42: Terrain elevation data file deletion option.

RF SIESTA Version V09-4 works only with level 1 terrain elevation data files. The read_all_CDED.pro procedure is hard-coded to detect only *.el1 files and sets the gDTEDLevel global variable to 1. Future versions of RF SIESTA will be modified to process level 2 and higher resolution terrain elevation data files.

CDED files can be downloaded from the GeoBase website. Two types of CDED data are available. Currently a user should only download 1:250,000 scale files and not the 1:50,000 variety. Each 1:250,000 scale *.zip file downloaded from GeoBase actually contains 2 files. One covers the eastern portion and one covers the western portion. The actual longitude coverage of these files varies based on the latitude. For example, cells from 0 to 68-degrees latitude are 1-degree x 1-degree, 68 to 80 are 1-degree x 2-degrees, and 80 to 90 are 1-degree x 4-degrees. RF SIESTA automatically compensates for CDED geographical areas shown in Figure 39. Level 1 elevation data files from areas ‘B’ and ‘C’ are interpolated and transformed into 1201 x 1201 cells covering a 1-degree x 1-degree area.

Page 51: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 37

DTED files are also similarly divided into geographical areas based on latitude. RF SIESTA automatically compensates for DTED geographic areas as well.

Figure 43: CDED geographic areas.

Figure 44 shows a typical DTED directory structure. Note that the top-level DTED directory contains the converted *.eln files. The user can create various subdirectories in DTED to store raw elevation data files. These subdirectories are ignored by the program and exist only for the user’s convenience. Any raw CDED or DTED file copied to the DTED directory will be processed and optionally deleted.

Figure 44: DTED directory structure.

Page 52: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

38 DRDC Ottawa CR 2009-138

8.1 Water-only Elevation Data Files

RF SIESTA does not currently handle elevation data files that are ‘water-only’, meaning that they contain zero elevation at all points. This poses a problem when the location of the radar is such that one or more cells in a cell array are of this type. This problem arises because DTED and CDED files are not available for areas that are entirely over water. However RF SIESTA requires that this elevation data cell exists when it builds the cell array.

Figure 45: Elevation data cell array.

In Figure 45, cells A, B and C contain land features (shown in grey) and cell D is a water-only cell. The radar is located at the center of the array at a distance off shore. As there is no elevation data for cell D, the user must manually create it. This can be done using IDL by opening an existing cell and zeroing all data points. The following simple IDL program creates a level 1 water-only cell. The filename should be changed to indicate the cell’s SW corner.

PRO water_only_cell

basepath = 'C:\SIESTA\NWTDP\DATA\DTED\' ; set file path CD, basepath elev_data = INTARR(1201,1201) ; create the data array OPENW, unit, 'W000_N00.el1', /GET_LUN ; create a new file WRITEU, unit, elev_data ; write the file FREE_LUN, unit ; close the file

END

Future versions of RF SIESTA will create the missing elevation data cells automatically.

A B

C D

Radar location

Page 53: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 39

9 Rebuilding the Slave Processor Code

RF SIESTA Version V09-4 contains a file called slave_processor.sav in the SLAVES directory. When RF SIESTA is configured for networked mode of operation, this file is copied to slave machines on the network as explained in Section 3.2. Double-clicking on the launch_slaves.sav file starts the slaves. This action spawns multiple images of the slave_processor code. The number of images spawned depends on the number of CPUs available.

The slave_proessor.sav file contains some of the same routines (procedures and functions) that execute on the master. These routines are not listed here but can be ascertained by opening the slave_processor.pro source file in IDL. If any of these routines are changed on the master, the corresponding routines in slave_processor.pro have to be changed as well and the ‘save’ file must be rebuilt. The following steps explain how to rebuild the slave_processor.sav file.

1. Make a backup copy of slave_processor.pro and slave_processor.sav on the master.

2. Open the IDL 6.4 development environment.

3. On the IDL command line change to the SLAVES subdirectory. For example if RF SIESTA was installed in C:\SIESTA\NWTDP, enter the command:

IDL> CD,’C:\SIESTA\NWTDP\SLAVES\’

4. In the IDL development environment, click on the Open File tab and open the slave_processor.pro file.

5. In the IDL development environment, click on the Open File tab again and change to the IDL ‘lib’ directory (C:\Program Files\ITT\IDL64\lib).

6. Open the svdfit.pro and svdfunct.pro files.

7. Compile each of the 3 files successively by clicking on Run->Compile or <Cntl> F5.

8. After all 3 files have been compiled, click on Run->Resolve Dependencies.

9. On the IDL command line, enter the following command:

IDL> SAVE, /ROUTINES, FILENAME=’slave_processor.sav’, /VERBOSE

10. Inspect the SLAVES subdirectory. The new ‘save’ file should have been created and the size of the file should be comparable to the older version of slave_processor.sav.

11. If running RF SIESTA in a networked mode, copy slave_processor.sav to the SLAVES subdirectory on all network machines.

Page 54: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

40 DRDC Ottawa CR 2009-138

10 Rebuilding the APM DLL

RF SIESTA Version V09-4 calls the Advanced Propagation Model (APM) extensively in its calculations. Previous versions of the software spawned an executable image of APM but this approach was too time consuming. The APM Version 2.3.03 code was subsequently rolled into a DLL that RF SIESTA calls for calculating the propagation factors and grazing angles. By calling the APM DLL via the IDL CALL_EXTERNAL function, significant time savings in the overall processing time were gained.

Normally the APM DLL does not need to be modified. In case code changes are necessary, the APM FORTRAN source files should be restored from the installation CD and rebuilt using the Intel or Digital Visual Fortran compiler.

The following steps detail how to rebuild the SBAPM2303.dll file.

1. Copy the RGS_APM directory from the installation CD.

2. Open the Visual FORTRAN Compiler, click on File->Open Workspace then click on the RGS_APM.dsw file. 3. Click on the apmmain_mod2.f90 file and inspect it. This file is the main driver and contains the interface routine RGS_APM called by the IDL CALL_EXTERNAL function. RGS_APM in turn calls RUNAPM converting between IDL and standard FORTRAN parameters. 4. Modifications were made to some other APM source files in order to get everything working. The modified files can be listed by performing a global search for the ‘RGS’ comment field.

5. The program options can be viewed by clicking on Project->Settings. This opens a window where the various parameters used by the compiler and linker can be inspected or set. It is recommended that these settings be not changed unless the user is totally familiar with them.

Page 55: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 41

Figure 46: The Visual FORTRAN development environment.

6. To rebuild the DLL, click on Build->Clean, then on Build->Rebuild All. The following lists the output messages generated by the compiler and linker.

Deleting intermediate files and output files for project 'RGS_APM - Win32 Debug'. --------------------Configuration: RGS_APM - Win32 Debug-------------------- Compiling Fortran... C:\RGS\RGS_APM\apm_mod.f90 C:\RGS\RGS_APM\xyinit.F90 C:\RGS\RGS_APM\xostep.F90 C:\RGS\RGS_APM\xoinit.F90 C:\RGS\RGS_APM\troposcat.f90 C:\RGS\RGS_APM\tropoinit.f90 C:\RGS\RGS_APM\trace_step.F90 C:\RGS\RGS_APM\trace_rout.F90 C:\RGS\RGS_APM\terinit.F90 C:\RGS\RGS_APM\surfimp.f90 C:\RGS\RGS_APM\spm.f90 C:\RGS\RGS_APM\specest.F90 C:\RGS\RGS_APM\savepro.F90

Page 56: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

42 DRDC Ottawa CR 2009-138

C:\RGS\RGS_APM\roloss.F90 C:\RGS\RGS_APM\rocalc.F90 C:\RGS\RGS_APM\rgtrace.F90 C:\RGS\RGS_APM\ret_graze.F90 C:\RGS\RGS_APM\remdup.F90 C:\RGS\RGS_APM\refinter.F90 C:\RGS\RGS_APM\refinit.F90 C:\RGS\RGS_APM\raytrace.F90 C:\RGS\RGS_APM\profref.F90 C:\RGS\RGS_APM\pestep.f90 C:\RGS\RGS_APM\peinit.f90 C:\RGS\RGS_APM\mixedft.f90 C:\RGS\RGS_APM\meanfilt.F90 C:\RGS\RGS_APM\intprof.F90 C:\RGS\RGS_APM\htcheck.F90 C:\RGS\RGS_APM\graze_int.F90 C:\RGS\RGS_APM\getthmax.f90 C:\RGS\RGS_APM\gettheta.F90 C:\RGS\RGS_APM\getrefcoef.f90 C:\RGS\RGS_APM\getangles.f90 C:\RGS\RGS_APM\getaln.f90 C:\RGS\RGS_APM\get_k.F90 C:\RGS\RGS_APM\gasabs.F90 C:\RGS\RGS_APM\fzlim.F90 C:\RGS\RGS_APM\frstp.F90 C:\RGS\RGS_APM\fillht.F90 C:\RGS\RGS_APM\fftpar.F90 C:\RGS\RGS_APM\FFT42.F90 C:\RGS\RGS_APM\fft.F90 C:\RGS\RGS_APM\fem.F90 C:\RGS\RGS_APM\fedr.F90 C:\RGS\RGS_APM\exto.F90 C:\RGS\RGS_APM\doshift.F90 C:\RGS\RGS_APM\dieinit.F90 C:\RGS\RGS_APM\clutter.f90 C:\RGS\RGS_APM\calclos.f90 C:\RGS\RGS_APM\apmsubs.f90 C:\RGS\RGS_APM\apmstep.f90 C:\RGS\RGS_APM\apmmain_mod2.f90 C:\RGS\RGS_APM\apminit.f90 C:\RGS\RGS_APM\apmfuncs.f90 C:\RGS\RGS_APM\apmclean.F90 C:\RGS\RGS_APM\antpat.f90 C:\RGS\RGS_APM\aln_init.f90 Linking... Creating library Debug/SBAPM2303.lib and object Debug/SBAPM2303.exp

SBAPM2303.dll - 0 error(s), 0 warning(s)

6. Inspect the contents of the Debug subdirectory. The new version of the SBAPM2303.dll file should be located here. Check that the file size is 425 KB. If code changes were made to any of the APM source files, the DLL size will differ.

Page 57: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 43

Annex A RF SIESTA Software Components

Directory Component filename Component version

GUI common_block.pro 7

GUI common_defs.pro 17

GUI convert_2_polar.pro 1

GUI getfile2.pro 19

GUI mainsad.pro 6

GUI menu_handlers.pro 13

GUI plot_polar.pro 12

GUI plotBar.pro 7

GUI SABODdisplay.pro 1

GUI showcomposite.pro 7

GUI updateTitleArrays.pro 1

GUI ximagebar.pro 4

APM BBref.pro 2

APM call_APM_DLL_F2surf.pro 9

APM call_APM_DLL_F2surf_StdOmni.pro 9

Page 58: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

44 DRDC Ottawa CR 2009-138

Directory Component filename Component version

APM call_APM_DLL_missile_graze.pro 9

APM Define.pro 11

APM DefineAntPattern.pro 3

APM DefineReflectivity.pro 3

APM DefineScan.pro 3

APM DefineTerrain.pro 8

APM DefineWCAntennaPattern.pro 1

APM Gasattenrate.pro 2

APM Metp.pro 1

APM Mgit.pro 3

APM Mseq.pro 4

APM ReadOut.pro 2

APM Scpow_med.pro 14

APM Terpemupdate.pro 12

APM Wcpow_med_SIESTA.pro 2

APM SBAPM2303.dll -

DTED process_dem.pro 1

DTED process_dtd.pro 1

Page 59: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 45

Directory Component filename Component version

DTED read_all_CDED.pro 5

INTEGRATION IntegrationFuncts.pro 1

INTEGRATION readwriteCDF.pro 5

SUPPORT AngleScale.pro 1

SUPPORT atten_factor.pro 1

SUPPORT attenSISWS_SABOD.pro 3

SUPPORT cw_field2.pro 0

SUPPORT DefineZ.pro 2

SUPPORT gencp.pro 6

SUPPORT LL_arc_distance_array.pro 1

SUPPORT map_2points_array.pro 1

SUPPORT mergeLWKD.pro 3

SUPPORT raybinLUT.pro 1

SUPPORT readHPAC.pro 13

SUPPORT str_size.pro 1

SUPPORT update_globals.pro 1

SUPPORT Urp_Meta_Reader.pro 4

SUPPORT xcolors.pro 1

Page 60: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

46 DRDC Ottawa CR 2009-138

Directory Component filename Component version

SUPPORT Single_Refractivity_Profile.pro 1

SLAVES launch_slaves.pro 0

SLAVES slave_processor.pro 9

SLAVES launch_slaves.sav -

SLAVES slave_processor.sav -

SLAVES slaves.pref -

SLAVES idlrt_rgs_100mbstk.exe -

SLAVES Readme.txt -

SV SV_AngleScale.pro 1

SV SV_atten.pro 1

SV SV_call_APM_DLL_missile_graze.pro 4

SV SV_defineAntPattern.pro 1

SV SV_noise.pro 1

SV SV_plot_polar.pro 6

SV SV_plotBar.pro 4

SV SV_prop.pro 6

SV SV_seaClutter.pro 2

SV SV_ship.pro 5

Page 61: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DRDC Ottawa CR 2009-138 47

Directory Component filename Component version

SV SV_terpemPlot.pro 2

SV SV_weatherClutter.pro 5

LWKD input.txt -

LWKD Lwkd.ini -

LWKD LWKD.INF -

LWKD LWKD_820.exe -

Page 62: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

48 DRDC Ottawa CR 2009-138

List of symbols/abbreviations/acronyms/initialisms

APM Advanced Propagation Model

ASL Above Sea Level

CAPPI Constant Altitude Plan Position Indicator

CD Compact Disc

CDED Canadian Digital Elevation Data

CDF Common Data File

CP Composite Product

CPU Central Processing Unit

DLL Dynamically Linked Library

DND Department of National Defence

DRDC Defence Research & Development Canada

DRDKIM Director Research and Development Knowledge and Information Management

DTED Digital Terrain Elevation Data

GUI Graphical User Interface

LHS Left Hand Side

MCP Main Control Panel

NWTDP Northern Watch Technology Demonstration Program

R&D Research & Development

RCS Radar Cross Section

RF Radio Frequency

RHI Range Height Indicator

RHS Right Hand Side

SCP Secondary Control Panel

SIESTA Shipborne Integrated Environment System for Tactics & Awareness

SUM Software User Manual

SV Ship Visibility

TDP Technology Demonstration Project

Page 63: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

DOCUMENT CONTROL DATA (Security classification of title, body of abstract and indexing annotation must be entered when the overall document is classified)

1. ORIGINATOR (The name and address of the organization preparing the document. Organizations for whom the document was prepared, e.g. Centre sponsoring a contractor's report, or tasking agency, are entered in section 8.) nEW Technologies 18 Pullman Avenue Ottawa, Ontario K2S 1C4

2. SECURITY CLASSIFICATION (Overall security classification of the document including special warning terms if applicable.)

UNCLASSIFIED

3. TITLE (The complete document title as indicated on the title page. Its classification should be indicated by the appropriate abbreviation (S, C or U) in parentheses after the title.) RF SIESTA software user manual: Version V09-4

4. AUTHORS (last name, followed by initials – ranks, titles, etc. not to be used) Robert G. Szeker

5. DATE OF PUBLICATION (Month and year of publication of document.) September 2009

6a. NO. OF PAGES (Total containing information, including Annexes, Appendices, etc.)

62

6b. NO. OF REFS (Total cited in document.)

0 7. DESCRIPTIVE NOTES (The category of the document, e.g. technical report, technical note or memorandum. If appropriate, enter the type of report,

e.g. interim, progress, summary, annual or final. Give the inclusive dates when a specific reporting period is covered.) Contract Report

8. SPONSORING ACTIVITY (The name of the department project office or laboratory sponsoring the research and development – include address.) Defence R&D Canada – Ottawa 3701 Carling Avenue Ottawa, Ontario K1A 0Z4

9a. PROJECT OR GRANT NO. (If appropriate, the applicable research and development project or grant number under which the document was written. Please specify whether project or grant.)

15aa

9b. CONTRACT NO. (If appropriate, the applicable number under which the document was written.)

W7714-060965/001/TOR

10a. ORIGINATOR'S DOCUMENT NUMBER (The official document number by which the document is identified by the originating activity. This number must be unique to this document.)

10b. OTHER DOCUMENT NO(s). (Any other numbers which may be assigned this document either by the originator or by the sponsor.) DRDC Ottawa CR 2009-138

11. DOCUMENT AVAILABILITY (Any limitations on further dissemination of the document, other than those imposed by security classification.)

Unlimited

12. DOCUMENT ANNOUNCEMENT (Any limitation to the bibliographic announcement of this document. This will normally correspond to the Document Availability (11). However, where further distribution (beyond the audience specified in (11) is possible, a wider announcement audience may be selected.)) Unlimited

Page 64: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the

13. ABSTRACT (A brief and factual summary of the document. It may also appear elsewhere in the body of the document itself. It is highly desirable that the abstract of classified documents be unclassified. Each paragraph of the abstract shall begin with an indication of the security classification of the information in the paragraph (unless the document itself is unclassified) represented as (S), (C), (R), or (U). It is not necessary to include here abstracts in both official languages unless the text is bilingual.)

This report contains the Software User Manual (SUM) for the RF SIESTA software. This document contains all information necessary to install and operate RF SIESTA in a stand-alone or networked configuration. The SUM also explains the limitations of the current software version and describes the changes that should be implemented in the next software version.

14. KEYWORDS, DESCRIPTORS or IDENTIFIERS (Technically meaningful terms or short phrases that characterize a document and could be helpful in cataloguing the document. They should be selected so that no security classification is required. Identifiers, such as equipment model designation, trade name, military project code name, geographic location may also be included. If possible keywords should be selected from a published thesaurus, e.g. Thesaurus of Engineering and Scientific Terms (TEST) and that thesaurus identified. If it is not possible to select indexing terms which are Unclassified, the classification of each should be indicated as with the title.) SIESTA, NWTDP, Software user manual

Page 65: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the
Page 66: RF SIESTA software user manual · SIESTA software components is contained in Annex A. The version of each component file is specified in the file’s header, which also lists the