If the tropical NWR configuration was completed last season, you should be able to skip to Step 4.
Add the necessary HLSs to, and
remove TCV1-5 from, the NWRWAVES text triggers
Add -+|| to WordFile.txt
to remove the new dash headers from the TCP.
If you need to broadcast multiple
HLSs on your transmitters, add those other WFOs to the file
awips/adapt/NWRWAVES/hls_sites.list. The entries should all be in one column.
Open the NWRWAVES Setup Utility
Under Product Configuration tab, check tone alert settings and adjust, if necessary
Check Yes next to Include Headlines? for Tropical Storm Warning and Hurricane Warning
Click Save Edits
Go to the Marine/Tropical Product Configuration tab
Modify subheadline wording to be played, if desired.
Click Store Marine Configuration Settings before moving on, if changes were made.
Click on Change Settings
Click on the Transmitter Configuration for HLS tab.
Set Exclude Marine Zones to Yes unless you
have a marine-only transmitter. DO NOT change anything else!
Ensures
cycle times are shorter if playing segments sections.
Click File then Save to save any changes.
Change tabs to HLS Subheadline Configuration tab
Add any subheadlines the office may include in the HLS.
You should coordinate local entries with your tropical/marine focal point
and WCM and get needed entries from neighboring offices.
Share your local subheadlines with any neighboring office(s) that may
also broadcast your HLS.
Once all possible subheadlines are in the list, choose the
ones that will be included in the NWR product, should no one run the subheadline
selection gui after an HLS is issued, and click the right arrow button.
This step should be done prior to each storm as the impact, and thus
the desired subheadlines, will be different.
If only the overview is to be played, ensure the right window is empty.
If desired, adjust the times the second and third/final
alerts that will appear to prompt users to run the subheadline selection gui.
The first alert will appear when the HLS is issued.
The second alert will appear X minutes later where X is the number of
minutes set in the first spin box (10 minutes default).
The 2 minute warning will appear X minutes later where X is the number
of minutes set in the second spin box (8 minutes default).
The HLS will automatically be processed 2 minutes after the final GUARDIAN
alert using the default subheadline configuration.
So the default is 20 minutes after the HLS is issued if no one launches
the subheadline selection gui.
Click File --> Save and choose the edited file.
If you want this configuration to be used every time without requiring the forecaster or HMT to modify/save the config, change the trigger for your HLS to a script which touches the config and then runs NWRWAVES.
Such a script is available on NOAA1 in pub/2012_Tropical_files/autoHLS_XXX.sh
As user fxa, place in /awips/adapt/NWRWAVES/ , change the XXX to the desired site ID, change the trigger to point to this script and run a mainScript.sh -trigger
Click File --> Open and choose another WFO's configuration.
Repeat steps 12 through 15 for the other WFOs. Save after each one.
You will now have hls_XXX.cfg files and a transmitter_hls.XXX file
which will be used as the first-time default for the NWR script.
As in step 5, if only the Overview is desired from any of these sites, you can copy the script above and adjust it for each site whose HLS you play.
Just change each site's HLS trigger to point to the appropriate version of the script (e.g. RDUHLSMHX /awips/adapt/NWRWAVES/autoHLS_MHX.sh).
Now the OVRHLS product needs to be added to CRS.
On the CRS machine, click on Messages, then Message Types.
The product name is XXXOVRHLS where XXX is the office ID of the issuing office.
If you play more than your own HLS, you will need to repeat this for all WFOs.
For the title use "HLS overview".
For the designation, use Warning
Choose the transmitters on which this OVR will play. To be safe, choose ALL of them.
For another WFO's OVR, you can choose the appropriate specific transmitter.
You can choose interrupt or not. Since the actual hazard messages will interrupt the broadcast, you can choose not to interrupt with the OVR.
Save.
Again, repeat steps 2 through 7 for the other WFOs.
Add all new OVRs to the appropriate broadcast program. A message trigger is not needed as the hazard message will provide that trigger for the HLS.