For build 5.1, the radar mosaics now work a little differently. First, the radars that go into the mosaic are no longer always automatically the set of radars that are in radarsOnMenu.txt. For an RFC or national center, this will still be the case if no action is taken by the site. However, for WFOs, the number of radars in any mosaic will be limited to the closest nine. Most importantly, however, is that there is now an option to supply a table that will control in a very specific manner which radars are in the mosaic, and will even allow mosaics of more than one set of radars.
If created on site, this table should be placed at the file path $FXA_CUSTOM_FILES/mosaicInfo.txt. If placed under configuration control the path localization/LLL/LLL-mosaicInfo.txt should be used. Here is an example of such a table. Placing the comments in line is a good idea as it helps whoever might need to manage the table.
// This file controls each radar mosaic that can be generated. // Each line represents one mosaic. Here is a model of each line: // // scales | file/list | count | center | title // // Here is the meaning of each column: // // scales : A space delimited list of scale indices to use for this mosaic. // Defaults to the contents of mosaicScales.txt. // file/list : A space delimited list of radars to use in this mosaic, or // alternatively, a file where this list is. If not supplied // defaults to radarsInUse.txt. // count : Max number of radars to include in the mosaic. If this is an RFC // or national center, this can be any number and will default to // all available radars. Otherwise, this will default to nine, and // will arbitrarily be limited to nine. // center : Takes the radars in the list closest to this point, up to the // value in the `count' column. This is a lat/lon, which defaults // to the contents of CenterPoint.dat, which should be the center // of the area of responsibility. // title : Should be unique for each line. A line without a title will // appear directly on the main `Radar' menu, others will be in // a pull right. // // If a version of this file is not supplied for the localization, a // default version will be created with one entry that looks like this: // // | radarsOnMenu.txt | | | // // 5 4 | kcys kftg kgld kgjx kpux | | | 3 | | 8 | 40 -109 | West 3 | | 8 | 35 -95 | SouthIn the example, the default Mosaic that has its menu entries directly on the top level menu called `Radar' has the five radars kcys, kftg, kgld, kgjx and kpux in it. Immediately following those menu entries will be a pull-right labeled `West'. In that pull-right will be menu entries for mosaics that include the 8 radars nearest to the point 40N 109W. Immediately following the pull-right labeled `West' will be a pull-right labeled `South'. In that pull-right will be menu entries for mosaics that include the 8 radars nearest to the point 35N 95W.
The main Mosaic will be shown on the WFO and State scales (scales 4 and 5) and the other two will be shown on the regional scale. Note that if no scales are listed for the mosaic, the contents of mosaicScales.txt will determine the scales, and that file defaults to just the State scale if it is not provided.
The reader should note that unless a radar appears in the radarsInUse.txt file, it will not be included in a mosaic. The radarsInUse.txt file that applies is always whatever one is applicable for the localization running on the data server.
The remaining files in the default system that apply to mosaics all reside in the directory localization/nationalData/, and they are called mosaicDepictKeys.template, mosaicDataMenus.template and mosaicProductButtons.template. The reader is directed to documentation in the headers of those files for additional information about how those files work. If one needs to make local changes to these files, the user should create copies of the originals in the file paths LLL-mosaicDepictKeys.template, LLL-mosaicDataMenus.template, and LLL-mosaicProductButtons.template in the directory localization/LLL/. After successful edits have been completed, the new files should be saved off somewhere so that they can be restored after upgrades.
Once one has edited any of these files, one needs to run the -radar localization task on a workstation host and then restart the D-2D on that host in order to view the newly configured mosaics. One must run the -radar task and then restart the notification server on the appropriate machine in order to get notifications for the newly configured mosaics.