MSAS AWIPS Localization Steps

The MSAS system definition file (msas_sysdef.txt) is used to specify the MSAS domain, background, and user-definable variables. It is used as input by the MSAS grid setup processing that's run during localization. Defaults have been established for each $FXA_INGEST_SITE.

To see what you're currently running with, the msas_sysdef.txt file may be found in one of two places:

• CONUS sites that haven't already customized MSAS:
  

  $FXA_HOME/data/localization/nationalData/msas_sysdef.txt

• Off-CONUS sites, or CONUS sites that have customized MSAS:
  

  $FXA_HOME/data/localizationDataSets/III/msas_sysdef.txt

To select settings other than the defaults, MSAS can be customized by taking a copy of this file, editing it with your changes, and putting it into:

$FXA_CUSTOM_FILES/III-msas_sysdef.txt, where III = your $FXA_INGEST_SITE

$FXA_CUSTOM_FILES points by default to /data/fxa/customFiles. (If your site has changed this, put the file into your $FXA_CUSTOM_FILES directory.)

Once the customized MSAS definition file has been created, you must then run the msas and grids localization tasks, on both Application Server (AS) machines (pre-OB4) or both PX machines (OB4 and later), to get the changes to take effect:

• Log into each AS or PX as user fxa.
• cd $FXA_HOME/data/localization/scripts
• ./mainScript.csh -msas -grids

You will then also have to run the dataSups and tables localization tasks on all Workstation (WS) machines after running the AS or PX localizations:

• Log into each WS as user fxa.
• cd $FXA_HOME/data/localization/scripts
• ./mainScript.csh -dataSups -tables

To revert back to the default, simply delete the III-msas_sysdef.txt file in the $FXA_CUSTOM_FILES directory, and rerun the localization tasks as shown above.