Xiangbao Jing (FSL) , 11/01/2001. Last modefied 04/24/02

The configurable table, the file,
$FXA_DATA/localization/nationalData/elevationLists.txt

contains all elevation angle lists for RMR, OTR and RPS(VCPs). The format and example data are,
-----------------------------------------------------------------------------------------------------
#List-Name type number-of-values value1 value2... valueN
#List-Name: Name for a angle set. It can be OTR, RMR or VCPxx.
#type: Type of the list. for VCP is the storm or clear-air. For the OTR and
# RMR is none.
#number-of-values: How many angles is in this list.
#valuen: A elevation angle value.
#Keep one list one line!
#
#For the OTR
OTR none 39 0.5 0.9 1.3 1.5 1.8 2.1 2.4 2.5 2.9 3.1 3.4 3.5 3.8 4.0 4.3 4.5 4.8 5.1 5.3 6.0 6.1
6.2 6.4 7.5 7.7 8.0 8.7 9.7 9.9 10.0 12.0 12.2 12.5 14.0 14.6 15.5 15.6 16.7 19.5
#
#For RMR
RMR none 39 0.5 0.9 1.3 1.5 1.8 2.1 2.4 2.5 2.9 3.1 3.4 3.5 3.8 4.0 4.3 4.5 4.8 5.1 5.3 6.0 6.1
6.2 6.4 7.5 7.7 8.0 8.7 9.7 9.9 10.0 12.0 12.2 12.5 14.0 14.6 15.5 15.6 16.7 19.5
#
#For RPS
VCP11 storm 14 0.5 1.5 2.4 3.4 4.3 5.3 6.2 7.5 8.7 10.0 12.0 14.0 16.7 19.5
VCP12 storm 14 0.5 0.9 1.3 1.8 2.4 3.1 4.0 5.1 6.4 8.0 10.0 12.5 15.6 19.5
VCP21 storm 9 0.5 1.5 2.4 3.4 4.3 6.0 9.9 14.6 19.5
VCP121 storm 9 0.5 1.5 2.4 3.4 4.3 6.0 9.9 14.6 19.5
VCP112 storm 12 0.5 1.3 2.1 2.9 3.8 4.8 6.1 7.7 9.7 12.2 15.5 19.5
VCP31 clear-air 5 0.5 1.5 2.5 3.5 4.5
VCP32 clear-air 5 0.5 1.5 2.5 3.5 4.5
#
#Generic VCP
#VCP00 9 0.5 0.9 1.3 1.5 1.8 2.1 2.4 2.5 2.9 3.2 3.4 3.5 3.8 4.0 4.3 4.5 4.8 5.1 5.3 6.0 6.1
#6.2 6.4 7.5 7.7 8.0 8.7 9.7 9.9 10.0 12.0 12.2 12.5 14.0 14.6 15.5 15.6 16.7 19.5
---------------------------------------------------------------------------------------------------
Each radar application will load this table when starting a process.

1.1 RPS Editor

In the RPS application, a rps list uses one VCPs only and the VCP can be tracked from the rps list file name and GUI.

1.1.1 System RPS List files Define

There are some predefined list files for each RPG, in the OB2. These include the local and national lists,
XXXX.maint                       local
XXXX.current                     local
XXXX.clear-air                   local
XXXX.storm                        local
rps-RPGOP-tcp.clear           national
rps-RPGOP.storm                national
rps-assoc.clear-air              national
rps-assoc.storm                   national

The XXXX is a RPG name.
The XXXX.current is created by the RadarServer process to save the latest sent list.
The XXXX.current, XXXX.clear-air and XXX.strom can be load into the editor by the "View".

The local lists are changed to VCP based in the OB3,
XXXX.maint
XXXX.current
XXXX.current VCP
XXXX.clear-air.VCP31
XXXX.clear-air.VCP32
XXXX.storm.VCP11
XXXX.storm.VCP21
XXXX.storm.VCP121
XXXX.storm.VCP112
XXXX.storm.VCP12
...
The VCPxx of the XXXX.current is saved in the XXXX.currentVCP file when hitting the "Send".

1.1.2 User's RPS List Files

User saved rps list is under the /data/fxa/rps-lists/, and the list file name with a ".rps"
extension is changed to a ".VCPxx.rps". Therefor, the VCP of a list can be tracked from the file name.
The format of the rps list file name is,
<lists-name>.VCPxx.rps
For example, the jing.VCP31.rps.

1.1.3 RPS and Editor

The rps shows the VCP of the current list in the title of the editor, as part of the list name (file name).
The VCP31 is the default VCP. At most time, the VCP is from the file name of the current list.

The product editor provides the elevation angle set of the current VCP for user to select.

The predefined local lists, such as the XXXX.current, XXXX.clear-air.VCPxx and XXXX.storm.VCPxx can be
loaded from the "View" menu. And user's list can be loaded from "File" -> "Open".

When create a new list file, the rps editor will ask user to select a VCP from the configured list.

When saving a list, the editor gives the file name a "VCPxx.rps" extension. The editor will matches
the current VCPxx and corrects it if there is a "VCPxx.rps" in the file name.

The OTR uses both the default or current RPG operational elevation angles. Which one should
be used depends on the selected "Time". The product parameter GUI will be updated if a RPG, product,
or any "time"(current, latest and selected) has been selected.

When the selected "Time" is "Current", the current elevation angles of a RPG are provided. These
angles are from file the /data/fxa/radar/xxxx/radarElevs.txt.

When the "Time" is "Latest" or "Selected", the default elevation angles are provided.

src/applications/radar/common/elev-lists.tcl
src/applications/radar/common/Makefile
src/applications/radar/common/prod-mgmt.tcl
src/applications/radar/common/rpg-select.tcl
src/applications/radar/rps/rps
src/applications/radar/rps/prods.conf
src/applications/radar/rps/list-mgmt.tcl
src/applications/radar/rps/rps-file-select.tcl
src/applications/radar/otr/otr
src/applications/radar/otr/prods.conf
src/applications/radar/otr/otr-utils.tcll
src/applications/radar/rmr/rmr
src/applications/radar/rmr/prods.conf
src/localization/nationalData/elevationLists.txt

--During installation of the OB3, should we convert the old user's rps list file to the files of the VCP based file names,
or let the user to do it? Anyway, the new rps doesn't understands the the old rps list file name. The conversion
includes matching a VCP(maybe multiple), converting old product name( DZ or DV), and duplicate processing.

--Who create the default local rps list for each VCP with the new file name format under the /data/fxa/radar/lists/?
DAR: Isn't FSL.

--Duplicate request Problem. For example, there are no 1.3 and 1.8 angles, but 1.5 only in the real local RPG VCP
angles. If both 1.3 and 1.8 are used in a rps list for a product, the PRG may converts them both to 1.5.

--Should the national lists be changed to VCP bin based as the local default lists?
DAR: NO.

--Should we remove the "clear-air" and "storm" from the local list file name and rps "View" menus, and just use the VCPxx?
   If so, the VCPs can be completely configurable, since there will be no hard coding for the "View".
   DAR: Keep the "clear-air" and "storm" in the GUI and file name. Change the format of the elevationLists.txt to
            implement the "completely configurable".

--The two VCP sets:
                    77, 44, 45, 11, 21, 31, 32 from Miek Istok, 03/24/03,
                    and 12, 121, 112, 11, 21, 31 from Rich' email 05/16/03
which one is the final for OB3?
   DAR: change the 77, 44 and 45 to 12, 121 and 112.

--Should we have a generic VCP, named VCP00 including all possible angles as in OTR?
   Should the VCP00 be the default VCP in the rps editor?
   It's helpful to create generic rps list such as the national lists.
   Note:
         To edit a local default or national list under the /data/fxa/radar/lists/, should follows the procedure,
               * Copy the file into the /data/fxa/rps-lists/ and change the file name format to user's rps list file name;
                 For example, "cp /data/fxa/radar/lists/rps-RPGOP-tcp.clear   /data/fxa/rps-lists/ps-RPGOP-tcp.clear.VCP00.rps";
               * Load and modify the rps-RPGOP-tcp.clear.VCP00..rps with the RPS editor;
               * Copy and rename back to the /data/fxa/rps-lists/,
                    "cp /data/fxa/rps-lists/rps-RPGOP-tcp.clear.VCP00.rps   /data/fxa/radar/lists/rps-RPGOP-tcp.clear ";
         for a local defailt lists, like XXXX.storm.VCP11, just load the file from the "View" menu or create a new file with the
         "File" -> "New", select VCP11, edit the new list, save the list with fime name XXXX.storm.VCP11.rps, and then,
         cp it to the /data/fxa/radar/lists/ as XXXX.storm.VCP11.

Begin from the OB3, the rps list is based on the VCP. The rps editor is no longer to understand the any old rps list any more. You should convert the old rps list file generated before OB3 into the new format if you still want use it. Since there is no auto-conversion tool for this( a DAR and management decision), You have to manually do the the conversion which includes to rename the file name by assigning a matched VCP and remove the DZ and DV products from the rps list.

Rename an Old RPS List File Name
Under the /data/fxa/rps-lists/, any rps list file with a extension ".VCPxxx.rps"
can be loaded in the rps editor to view by using "Open". But the rps lists
generated before OB3 without the ".VCPxxx.". How to read them from the rps
editor of the OB3? The access solution is assigning a matched VCPxxx and adding it into the file name. For example, the KFTG.storm.rps is a old rps list. Because it's storm list, we assign VCP11 to the file name and copy the old file to a new file with a file name KFTG.storm.VCP11.rps by typing coaand line,
cp KFTG.storm.rps KFTG.storm.VCP11.rps
then you can use the "File"-->"Open" to load the KFTG.storm.VCP11.rps into the rps editor to view and edit the list.

Give a Right VCPxxx
The elevation angles of the given VCPxxx(VCP11) must covers the angles appeared in the rps list(KFTG.storm.rps), otherwise, you may have editing problem. The VCPxxx elevation angle list is defined in the file,
$FXA_DATA/localization/nationalData/elevationLists.txt.
The most old rps list was created based on the "storm" and "clear-air" modes, so usually, you can use the VCP11 if the old rps list is based on the "storm"
list, or the VCP31 if it's based on the "clear-air" list. But the important thing is to compare the real angles in the rps list and the angles of the given VCPxxx. You should reassign a right VCPxxx to the rps list if they are not matched.

Remove DV and DZ Products
Begin from the OB3, there is no DZ and DV products, be sure to delete them when
you editing a old rps list. You can load the list in the new rps file into the rps editor, to remove the DZ or DV products by selecting the product and using the "Remove" button, or change the it to Z or V product by using the "Edit" button to lunch the product editor.