diff --git a/cave/warngen/index.html b/cave/warngen/index.html index ce4000433c..30c9ef3fab 100644 --- a/cave/warngen/index.html +++ b/cave/warngen/index.html @@ -356,6 +356,13 @@ @@ -1072,6 +1072,13 @@ @@ -1181,53 +1181,51 @@

Steps involved in using WarnGen in Unidata AWIPS CAVE

-

Load NEXRAD level 3 display

-

Select the menu Radar > NEXRAD Display and note coverage areas of current severe weather. We choose a WFO ID that contains some active severe weather (KLZK Little Rock, Arkansas, in this example).

+

Select the menu Radar > NEXRAD Display and note coverage areas of current severe weather. We choose a CWA ID that contains some active severe weather (PAH Paducah, Kentucky, in this example).

Select SITE Localization

-

Open CAVE > Preferences > Localization, select the WFO ID (KLZK) for the coverage area you want to use, followed by Apply and then Restart.

-

Select the nearest WSR-88D location

-

Click on any NEXRAD Display station to load a two-pane Reflectivity/Velocity view.

+

Open CAVE > Preferences > Localization, select the CWA site ID (PAH) for the coverage area you want to use, followed by Apply and Okay and restart CAVE. Once CAVE is restarted, you should notice the new CWA at the top of the CAVE window.

+

+

Load single radar data from the local radars

+

Click on the local radar kpah > Z + SRM8. Use the "period" key in the number pad to toggle between the 0.5 Reflectivity and SRM. +

Launch WarnGen

-

Select WarnGen from the D2D Toolbar or from the Tools menu. When started, the storm centroid marker appears and the WarnGen GUI will pop up as a separate window.

- - - - - - - - - - - - - -
+

Select WarnGen from the D2D Toolbar or from the Tools > WarnGen menu. When started, the storm centroid marker appears and the WarnGen GUI will pop up as a separate window.

+

Generate a Storm Motion Vector

  1. Click and drag Drag Me to Storm to the feature you want to track (WarnGen uses a dot to track a single storm and a line to track a line of storms).
  2. Step back 3 to 4 frames.
    3. -
  3. Drag the dot to the previous position of the feature you first marked.
    4. +
  4. Drag the dot to the previous position of the feature you first marked to create the storm motion vector.
    5. +
  5. Click the Track button in the WarnGen GUI to update the polygon based off the storm motion.
  6. Review the product loop and make adjustments to ensure the vector is accurate.
+

Restart

Click the Reset button to clear all current polygons and vectors and reset the storm centroid marker.

Redrawing a Polygon

@@ -1238,7 +1236,7 @@ src="https://www.youtube.com/embed/KSKmIMjkVCU?autoplay=1">

When reshaping your warning polygon in this manner, the philosophy is to include all areas that are at risk of experiencing severe weather covered by that warning type. Effective polygons account for uncertainty over time and typically widen downstream. There will be a lot of training provided on Storm-Based Warning Fundamentals in RAC and in the workshop, and this lesson is more focused on the basic mechanics.

Add and Remove Vertex Points

There will be some occasions where you will want to add vertices to your warning polygon. Most often, these situations will involve line warnings with bowing segments or single storm warnings where you want to account for storm motion uncertainty or multiple threat areas that may have differing storm motions.

-

New vertices are added to the warning polygon using a context relative menu accessed by selecting the warning polygon line segments with a Right Mouse Button "click and hold".

+

New vertices are added to the warning polygon using a context relative menu accessed by selecting the warning polygon line segments with a Right Mouse Button "click and hold" or a simple Middle Mouse Button while at the location you want to add a vertex.

  1. Hold right-click and select add vertex.
  2. Click the left mouse button at the location you desire for the new vertex and the point is created there.
    3. @@ -1248,23 +1246,28 @@ src="https://www.youtube.com/embed/KSKmIMjkVCU?autoplay=1">

    Restoring a Polygon

    When you are customizing a polygon in WarnGen, speed is critical. Everyone, even veteran warning forecasters, will occasionally draw a warning polygon one way and then realize, prior to sending the warning, that they want to draw the warning boundaries differently. Depending on the complexity of the changes you make to a warning polygon, sometimes it’s faster to just start over from scratch. The easiest way to proceed, especially if you are still comfortable with the storm motion, is to select the “Track” button from the “Redraw Box on Screen from” section of the WarnGen GUI.

    Text Window

    -

    Using the customized settings in the WarnGen GUI, WarnGen translates the information into a text product that is displayed in a text window on the Text Display. Initially the AWIPS Header Block window appears, and you will just click Enter to modify the text of the warning. The auto-generated text contains the storm speed and direction, the counties and cities affected by the warning/advisory, the valid times of the product, the warning/advisory body text (including any optional bullets selected in the GUI), and additional code to help our partners to efficiently process and disseminate the warning/advisory. The locked parts of the text are highlighted in blue and most of your text should not need to be edited if you configured your WarnGen window correctly.

    +

    Using the customized settings in the WarnGen GUI, WarnGen translates the information into a text product that is displayed in a text window on the Text Display. Initially the AWIPS Header Block window appears, and you will just click Enter to modify the text of the warning.

    +

    +

    The auto-generated text contains the storm speed and direction, the counties and cities affected by the warning/advisory, the valid times of the product, the warning/advisory body text (including any optional bullets selected in the GUI), and additional code to help our partners to efficiently process and disseminate the warning/advisory. The locked parts of the text are highlighted in blue and most of your text should not need to be edited if you configured your WarnGen window correctly.

    +
    +

    The Unidata AWIPS software is non-operational, so you will not be able to "issue" or send the warnings you create

    +

    For some products like Severe Weather Statements, there are parts of text that must be edited that have wild-card characters around them that need to be removed after modifying the text inside (e.g. ! WEAKENED.MOVED OUT OF THE WARNED AREA. !). When you attempt to send a product, WarnGen will instruct you to modify this text if you have not. Once the text looks ready for submission you click the Send button, and, on a live system, the warning will be transmitted for public broadcast after you press the Go Ahead button on the final WarnGen check. WES-2 Bridge has been implemented in a way that cannot interact with the live AWIPS processes and communications, so warnings issued on the WES-2 Bridge will not be transmitted as live products.

    NOTE: Edits made to product text in the editor window should be limited to items such as forecaster name/initials, call-to-action text, etc. If changes are warranted for items such as storm motion, warned counties, or Latitude/Longitude points, close the editor window and make changes using the D-2D and WarnGen graphical tools, then recreate the polygon and/or the text.

    -

    "Issuing" a Warning

    -

    With a tracked storm in WarnGen:

    -
      -
    1. Select CAVE > New > Text Workstation
      2. -
    2. Select the Track button to preview the polygon
      3. -
    3. Select the Create Text button.
      4. -
    4. Select Enter on the AWIPS Header Block window to enter the text editor.
        -
      • Blue text is locked and uneditable. You should not need to edit most text, and you need to be careful not to make the hazards inconsistent with the locked intensity summary at the bottom of the warning.
        • -
      • If WarnGen has text you need to edit, there will be wildcards around the text, and WarnGen will not let you send the warning until you modify it.
        • -
      -
      5. -
    5. Read the text of the warning, identify your ETN number after the “SV.W.” (e.g. 0004) at the top of the warning, and make changes to the warning text if WarnGen tells you to.
      6. -
    6. Click the Send button (will not actually send). Sending warnings on the WES-2 Bridge is safe because it is not connected to the live AWIPS communications route, and the transmission capabilities have been disabled, firewalled, and modified to prevent any risk of warnings going out. Unidata AWIPS always disables the sending of warnings.
      7. -
    + diff --git a/images/warngen.png b/images/warngen.png index f2f97c1bc9..5ad7fca7f0 100644 Binary files a/images/warngen.png and b/images/warngen.png differ diff --git a/images/warngenDMTS.png b/images/warngenDMTS.png new file mode 100644 index 0000000000..e4fc7fe5d1 Binary files /dev/null and b/images/warngenDMTS.png differ diff --git a/images/warngenHeaderBlock.png b/images/warngenHeaderBlock.png new file mode 100644 index 0000000000..f864eeb9f7 Binary files /dev/null and b/images/warngenHeaderBlock.png differ diff --git a/images/warngenLocalRadar.png b/images/warngenLocalRadar.png new file mode 100644 index 0000000000..232bc744e8 Binary files /dev/null and b/images/warngenLocalRadar.png differ diff --git a/images/warngenLocalization.png b/images/warngenLocalization.png new file mode 100644 index 0000000000..0901166719 Binary files /dev/null and b/images/warngenLocalization.png differ diff --git a/search/search_index.json b/search/search_index.json index 226468096b..44060a6900 100644 --- a/search/search_index.json +++ b/search/search_index.json @@ -497,32 +497,37 @@ }, { "location": "/cave/warngen/", - "text": "WarnGen is an AWIPS graphics application for creating and issuing warnings as is done by National Weather Service offices. In the Unidata AWIPS release it is a \nnon-operational\n forecasting tool, meaning it allows users to experiment and simulate with the drawing and text-generation tools, but prevents you from transmitting a generated warning upstream.\n\n\n\n\nIn order to select a feature it must be within your \nCAVE localization\n coverage (load \nMaps\n > \nCounty Warning Areas\n to see coverages)\n\n\n\n\nSteps involved in using WarnGen in Unidata AWIPS CAVE\n\n\n\n\nLoad NEXRAD Display from the Radar menu.\n\n\nChoose a WFO site with active severe weather (LUB is used in the video).\n\n\nRe-localize to this site in the CAVE > Preferences > Localization menu.\n\n\nLoad NEXRAD Display again and select a WSR-88D site to load a 2-panel display of 0.5 degree Reflectivity (N0Q) and Velocity (N0U).\n\n\nClick the WarnGen toolbar button or load from Tools > WarnGen.\n\n\nDrag the storm marker to the center of a storm feature.\n\n\nStep through frames back and forth and adjust the marker to match the trajectory of the storm feature.\n\n\nFrom the WarnGen dialog select the type of warning to generate, the time range, the basis of the warning, and any threats to add (wind, hail, etc).\n\n\nClick \"Create Text\" at the bottom of the WarnGen dialog to generate a text warning product in a new window.\n\n\nClick \"Reset\" at the top of the WarnGen dialog to reset the storm marker at any time.\n\n\nSelect \"Line of Storms\" to enable a two-pointed vector which is to be positioned parallel to a storm line.\n\n\n\n\n\n\n\nLoad NEXRAD level 3 display\n\uf0c1\n\n\nSelect the menu \nRadar\n > \nNEXRAD Display\n and note coverage areas of current severe weather. We choose a WFO ID that contains some active severe weather (KLZK Little Rock, Arkansas, in this example).\n\n\nSelect SITE Localization\n\uf0c1\n\n\nOpen \nCAVE\n > \nPreferences\n > \nLocalization\n, select the WFO ID (KLZK) for the coverage area you want to use, followed by \nApply\n and then \nRestart\n.\n\n\nSelect the nearest WSR-88D location\n\uf0c1\n\n\nClick on any NEXRAD Display station to load a two-pane Reflectivity/Velocity view.\n\n\nLaunch WarnGen\n\uf0c1\n\n\nSelect \nWarnGen\n from the D2D Toolbar or from the \nTools\n menu. When started, the storm centroid marker appears and the WarnGen GUI will pop up as a separate window.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nGenerate a Storm Motion Vector\n\uf0c1\n\n\n\n\nClick and drag \nDrag Me to Storm\n to the feature you want to track (WarnGen uses a dot to track a single storm and a line to track a line of storms).\n\n\nStep back 3 to 4 frames.\n\n\nDrag the dot to the previous position of the feature you first marked.\n\n\nReview the product loop and make adjustments to ensure the vector is accurate.\n\n\n\n\nRestart\n\uf0c1\n\n\nClick the \nReset\n button to clear all current polygons and vectors and reset the storm centroid marker.\n\n\nRedrawing a Polygon\n\uf0c1\n\n\nSelect the \nTrack\n button in the \n\"Redraw Box on Screen\"\n section to redraw a default warning polygon oriented along the storm motion track and containing the storm centroid dot for the most recent volume scan. The initial polygon may have unhatched areas that will be removed from the warning due to crossing CWAs or not meeting area thresholds in the county for inclusion. The Warned/Hatched Area button allow you to preview the polygon shape that will be issued, so you can make further edits.\n\n\nMoving Vertex Points\n\uf0c1\n\n\nVertices can be moved by clicking and dragging with the mouse. The warning polygon, including stippling, will update automatically.\n\n\n\n\nWhen reshaping your warning polygon in this manner, the philosophy is to include all areas that are at risk of experiencing severe weather covered by that warning type. Effective polygons account for uncertainty over time and typically widen downstream. There will be a lot of training provided on Storm-Based Warning Fundamentals in RAC and in the workshop, and this lesson is more focused on the basic mechanics.\n\n\nAdd and Remove Vertex Points\n\uf0c1\n\n\nThere will be some occasions where you will want to add vertices to your warning polygon. Most often, these situations will involve line warnings with bowing segments or single storm warnings where you want to account for storm motion uncertainty or multiple threat areas that may have differing storm motions.\n\n\nNew vertices are added to the warning polygon using a context relative menu accessed by selecting the warning polygon line segments with a \nRight Mouse Button \"click and hold\"\n.\n\n\n\n\nHold right-click and select \nadd vertex\n.\n\n\nClick the left mouse button at the location you desire for the new vertex and the point is created there.\n\n\nClicking the middle mouse button (or scroll wheel) along an edge of the polygon will also place a vertex at that point.\n\n\n\n\nVertex points are removed from the warning polygon using the same context relative menu. Instead of selecting a line segment, you select the vertex you wish to remove and then \nclick and hold\n with right mouse button. Hold right-click and select \nremove vertex\n.\n\n\nRestoring a Polygon\n\uf0c1\n\n\nWhen you are customizing a polygon in WarnGen, speed is critical. Everyone, even veteran warning forecasters, will occasionally draw a warning polygon one way and then realize, prior to sending the warning, that they want to draw the warning boundaries differently. Depending on the complexity of the changes you make to a warning polygon, sometimes it\u2019s faster to just start over from scratch. The easiest way to proceed, especially if you are still comfortable with the storm motion, is to select the \u201cTrack\u201d button from the \u201cRedraw Box on Screen from\u201d section of the WarnGen GUI.\n\n\nText Window\n\uf0c1\n\n\nUsing the customized settings in the WarnGen GUI, WarnGen translates the information into a text product that is displayed in a text window on the Text Display. Initially the AWIPS Header Block window appears, and you will just click Enter to modify the text of the warning. The auto-generated text contains the storm speed and direction, the counties and cities affected by the warning/advisory, the valid times of the product, the warning/advisory body text (including any optional bullets selected in the GUI), and additional code to help our partners to efficiently process and disseminate the warning/advisory. The locked parts of the text are highlighted in blue and most of your text should not need to be edited if you configured your WarnGen window correctly.\n\n\nFor some products like Severe Weather Statements, there are parts of text that must be edited that have wild-card characters around them that need to be removed after modifying the text inside (e.g. !\n WEAKENED.MOVED OUT OF THE WARNED AREA. \n!). When you attempt to send a product, WarnGen will instruct you to modify this text if you have not. Once the text looks ready for submission you click the Send button, and, on a live system, the warning will be transmitted for public broadcast after you press the Go Ahead button on the final WarnGen check. WES-2 Bridge has been implemented in a way that cannot interact with the live AWIPS processes and communications, so warnings issued on the WES-2 Bridge will not be transmitted as live products.\n\n\nNOTE: Edits made to product text in the editor window should be limited to items such as forecaster name/initials, call-to-action text, etc. If changes are warranted for items such as storm motion, warned counties, or Latitude/Longitude points, close the editor window and make changes using the D-2D and WarnGen graphical tools, then recreate the polygon and/or the text.\n\n\n\"Issuing\" a Warning\n\uf0c1\n\n\nWith a tracked storm in WarnGen:\n\n\n\n\nSelect \nCAVE > New > Text Workstation\n\n\nSelect the \nTrack\n button to preview the polygon\n\n\nSelect the \nCreate Text\n button.\n\n\nSelect \nEnter\n on the AWIPS Header Block window to enter the text editor.\n\n\nBlue text is locked and uneditable. You should not need to edit most text, and you need to be careful not to make the hazards inconsistent with the locked intensity summary at the bottom of the warning.\n\n\nIf WarnGen has text you need to edit, there will be wildcards around the text, and WarnGen will not let you send the warning until you modify it.\n\n\n\n\n\n\nRead the text of the warning, identify your ETN number after the \u201cSV.W.\u201d (e.g. 0004) at the top of the warning, and make changes to the warning text if WarnGen tells you to.\n\n\nClick the \nSend\n button (will not actually send). Sending warnings on the WES-2 Bridge is safe because it is not connected to the live AWIPS communications route, and the transmission capabilities have been disabled, firewalled, and modified to prevent any risk of warnings going out. Unidata AWIPS always disables the sending of warnings.", + "text": "WarnGen is an AWIPS graphics application for creating and issuing warnings as is done by National Weather Service offices. In the Unidata AWIPS release it is a \nnon-operational\n forecasting tool, meaning it allows users to experiment and simulate with the drawing and text-generation tools, but prevents you from transmitting a generated warning upstream.\n\n\n\n\nIn order to select a feature it must be within your \nCAVE localization\n coverage (load \nMaps\n > \nCounty Warning Areas\n to see coverages)\n\n\n\n\nSteps involved in using WarnGen in Unidata AWIPS CAVE\n\n\n\n\nLoad NEXRAD Display from the Radar menu\n\n\nChoose a CWA with active severe weather (PAH is used in the video below)\n\n\nRe-localize to this site in the \nCAVE\n > \nPreferences\n > \nLocalization\n menu\n\n\nExit out of CAVE and reload (you should notice the new CWA at the top of CAVE)\n\n\nLoad radar data from the local radar menu \nkpah\n > \nZ + SRM8\n\n\nUse the \"period\" key in the number pad to toggle between the 0.5 Reflectivity and SRM\n\n\nClick the WarnGen toolbar button or load from \nTools\n > \nWarnGen\n\n\nDrag the storm marker to the center of a storm feature\n\n\nStep through frames back and forth and adjust the marker to match the trajectory of the storm feature\n\n\nClick \nTrack\n in the Warngen GUI to update the polygon shape and trajectory\n\n\nFrom the WarnGen dialog select the type of warning to generate, time range, basis of the warning, and any threats (wind, hail, etc)\n\n\nClick \"Create Text\" at the bottom of the WarnGen dialog to generate a text warning product in a new window\n\n\nNote: Since you are not \"issuing\" the warning, leave the top to rows blank (\"TTAAii\" and \"CCCC\") and Click \"Enter\" and a separate text window should open \n\n\n\n\n\n\n\n\nClick \"Reset\" at the top of the WarnGen dialog to reset the storm marker at any time.\n\n\nSelect \"Line of Storms\" to enable a two-pointed vector which is to be positioned parallel to a storm line\n\n\nTo add another vertex, middle button click along the polygon\n\n\n\n\nVideo - Using WarnGen in AWIPS\n\uf0c1\n\n\nThe video below walks through creating a warning polygon and text in AWIPS. More detailed information can be found in the text below the video.\n\n\n\n\n\n\n\nLoad NEXRAD level 3 display\n\uf0c1\n\n\nSelect the menu \nRadar\n > \nNEXRAD Display\n and note coverage areas of current severe weather. We choose a CWA ID that contains some active severe weather (PAH Paducah, Kentucky, in this example).\n\n\nSelect SITE Localization\n\uf0c1\n\n\nOpen \nCAVE\n > \nPreferences\n > \nLocalization\n, select the CWA site ID (PAH) for the coverage area you want to use, followed by \nApply\n and \nOkay\n and restart CAVE. Once CAVE is restarted, you should notice the new CWA at the top of the CAVE window.\n\n\n\n\nLoad single radar data from the local radars\n\uf0c1\n\n\nClick on the local radar \nkpah\n > \nZ + SRM8\n. Use the \"period\" key in the number pad to toggle between the 0.5 Reflectivity and SRM.\n\n\n\nLaunch WarnGen\n\uf0c1\n\n\nSelect \nWarnGen\n from the D2D Toolbar or from the \nTools\n > \nWarnGen\n menu. When started, the storm centroid marker appears and the WarnGen GUI will pop up as a separate window.\n\n\n\n\nGenerate a Storm Motion Vector\n\uf0c1\n\n\n\n\nClick and drag \nDrag Me to Storm\n to the feature you want to track (WarnGen uses a dot to track a single storm and a line to track a line of storms).\n\n\nStep back 3 to 4 frames.\n\n\nDrag the dot to the previous position of the feature you first marked to create the storm motion vector.\n\n\nClick the \nTrack\n button in the WarnGen GUI to update the polygon based off the storm motion.\n\n\nReview the product loop and make adjustments to ensure the vector is accurate.\n\n\n\n\n\n\nRestart\n\uf0c1\n\n\nClick the \nReset\n button to clear all current polygons and vectors and reset the storm centroid marker.\n\n\nRedrawing a Polygon\n\uf0c1\n\n\nSelect the \nTrack\n button in the \n\"Redraw Box on Screen\"\n section to redraw a default warning polygon oriented along the storm motion track and containing the storm centroid dot for the most recent volume scan. The initial polygon may have unhatched areas that will be removed from the warning due to crossing CWAs or not meeting area thresholds in the county for inclusion. The Warned/Hatched Area button allow you to preview the polygon shape that will be issued, so you can make further edits.\n\n\nMoving Vertex Points\n\uf0c1\n\n\nVertices can be moved by clicking and dragging with the mouse. The warning polygon, including stippling, will update automatically.\n\n\n\n\nWhen reshaping your warning polygon in this manner, the philosophy is to include all areas that are at risk of experiencing severe weather covered by that warning type. Effective polygons account for uncertainty over time and typically widen downstream. There will be a lot of training provided on Storm-Based Warning Fundamentals in RAC and in the workshop, and this lesson is more focused on the basic mechanics.\n\n\nAdd and Remove Vertex Points\n\uf0c1\n\n\nThere will be some occasions where you will want to add vertices to your warning polygon. Most often, these situations will involve line warnings with bowing segments or single storm warnings where you want to account for storm motion uncertainty or multiple threat areas that may have differing storm motions.\n\n\nNew vertices are added to the warning polygon using a context relative menu accessed by selecting the warning polygon line segments with a \nRight Mouse Button \"click and hold\"\n or a simple \nMiddle Mouse Button\n while at the location you want to add a vertex.\n\n\n\n\nHold right-click and select \nadd vertex\n.\n\n\nClick the left mouse button at the location you desire for the new vertex and the point is created there.\n\n\nClicking the middle mouse button (or scroll wheel) along an edge of the polygon will also place a vertex at that point.\n\n\n\n\nVertex points are removed from the warning polygon using the same context relative menu. Instead of selecting a line segment, you select the vertex you wish to remove and then \nclick and hold\n with right mouse button. Hold right-click and select \nremove vertex\n.\n\n\nRestoring a Polygon\n\uf0c1\n\n\nWhen you are customizing a polygon in WarnGen, speed is critical. Everyone, even veteran warning forecasters, will occasionally draw a warning polygon one way and then realize, prior to sending the warning, that they want to draw the warning boundaries differently. Depending on the complexity of the changes you make to a warning polygon, sometimes it\u2019s faster to just start over from scratch. The easiest way to proceed, especially if you are still comfortable with the storm motion, is to select the \u201cTrack\u201d button from the \u201cRedraw Box on Screen from\u201d section of the WarnGen GUI.\n\n\nText Window\n\uf0c1\n\n\nUsing the customized settings in the WarnGen GUI, WarnGen translates the information into a text product that is displayed in a text window on the Text Display. Initially the AWIPS Header Block window appears, and you will just click Enter to modify the text of the warning. \n\n\n\n\nThe auto-generated text contains the storm speed and direction, the counties and cities affected by the warning/advisory, the valid times of the product, the warning/advisory body text (including any optional bullets selected in the GUI), and additional code to help our partners to efficiently process and disseminate the warning/advisory. The locked parts of the text are highlighted in blue and most of your text should not need to be edited if you configured your WarnGen window correctly.\n\n\n\n\nThe Unidata AWIPS software is non-operational, so you will not be able to \"issue\" or send the warnings you create\n\n\n\n\nFor some products like Severe Weather Statements, there are parts of text that must be edited that have wild-card characters around them that need to be removed after modifying the text inside (e.g. !\n WEAKENED.MOVED OUT OF THE WARNED AREA. \n!). When you attempt to send a product, WarnGen will instruct you to modify this text if you have not. Once the text looks ready for submission you click the Send button, and, on a live system, the warning will be transmitted for public broadcast after you press the Go Ahead button on the final WarnGen check. WES-2 Bridge has been implemented in a way that cannot interact with the live AWIPS processes and communications, so warnings issued on the WES-2 Bridge will not be transmitted as live products.\n\n\nNOTE: Edits made to product text in the editor window should be limited to items such as forecaster name/initials, call-to-action text, etc. If changes are warranted for items such as storm motion, warned counties, or Latitude/Longitude points, close the editor window and make changes using the D-2D and WarnGen graphical tools, then recreate the polygon and/or the text.", "title": "WarnGen Walkthrough" }, + { + "location": "/cave/warngen/#video-using-warngen-in-awips", + "text": "The video below walks through creating a warning polygon and text in AWIPS. More detailed information can be found in the text below the video.", + "title": "Video - Using WarnGen in AWIPS" + }, { "location": "/cave/warngen/#load-nexrad-level-3-display", - "text": "Select the menu Radar > NEXRAD Display and note coverage areas of current severe weather. We choose a WFO ID that contains some active severe weather (KLZK Little Rock, Arkansas, in this example).", + "text": "Select the menu Radar > NEXRAD Display and note coverage areas of current severe weather. We choose a CWA ID that contains some active severe weather (PAH Paducah, Kentucky, in this example).", "title": "Load NEXRAD level 3 display" }, { "location": "/cave/warngen/#select-site-localization", - "text": "Open CAVE > Preferences > Localization , select the WFO ID (KLZK) for the coverage area you want to use, followed by Apply and then Restart .", + "text": "Open CAVE > Preferences > Localization , select the CWA site ID (PAH) for the coverage area you want to use, followed by Apply and Okay and restart CAVE. Once CAVE is restarted, you should notice the new CWA at the top of the CAVE window.", "title": "Select SITE Localization" }, { - "location": "/cave/warngen/#select-the-nearest-wsr-88d-location", - "text": "Click on any NEXRAD Display station to load a two-pane Reflectivity/Velocity view.", - "title": "Select the nearest WSR-88D location" + "location": "/cave/warngen/#load-single-radar-data-from-the-local-radars", + "text": "Click on the local radar kpah > Z + SRM8 . Use the \"period\" key in the number pad to toggle between the 0.5 Reflectivity and SRM.", + "title": "Load single radar data from the local radars" }, { "location": "/cave/warngen/#launch-warngen", - "text": "Select WarnGen from the D2D Toolbar or from the Tools menu. When started, the storm centroid marker appears and the WarnGen GUI will pop up as a separate window.", + "text": "Select WarnGen from the D2D Toolbar or from the Tools > WarnGen menu. When started, the storm centroid marker appears and the WarnGen GUI will pop up as a separate window.", "title": "Launch WarnGen" }, { "location": "/cave/warngen/#generate-a-storm-motion-vector", - "text": "Click and drag Drag Me to Storm to the feature you want to track (WarnGen uses a dot to track a single storm and a line to track a line of storms). Step back 3 to 4 frames. Drag the dot to the previous position of the feature you first marked. Review the product loop and make adjustments to ensure the vector is accurate.", + "text": "Click and drag Drag Me to Storm to the feature you want to track (WarnGen uses a dot to track a single storm and a line to track a line of storms). Step back 3 to 4 frames. Drag the dot to the previous position of the feature you first marked to create the storm motion vector. Click the Track button in the WarnGen GUI to update the polygon based off the storm motion. Review the product loop and make adjustments to ensure the vector is accurate.", "title": "Generate a Storm Motion Vector" }, { @@ -542,7 +547,7 @@ }, { "location": "/cave/warngen/#add-and-remove-vertex-points", - "text": "There will be some occasions where you will want to add vertices to your warning polygon. Most often, these situations will involve line warnings with bowing segments or single storm warnings where you want to account for storm motion uncertainty or multiple threat areas that may have differing storm motions. New vertices are added to the warning polygon using a context relative menu accessed by selecting the warning polygon line segments with a Right Mouse Button \"click and hold\" . Hold right-click and select add vertex . Click the left mouse button at the location you desire for the new vertex and the point is created there. Clicking the middle mouse button (or scroll wheel) along an edge of the polygon will also place a vertex at that point. Vertex points are removed from the warning polygon using the same context relative menu. Instead of selecting a line segment, you select the vertex you wish to remove and then click and hold with right mouse button. Hold right-click and select remove vertex .", + "text": "There will be some occasions where you will want to add vertices to your warning polygon. Most often, these situations will involve line warnings with bowing segments or single storm warnings where you want to account for storm motion uncertainty or multiple threat areas that may have differing storm motions. New vertices are added to the warning polygon using a context relative menu accessed by selecting the warning polygon line segments with a Right Mouse Button \"click and hold\" or a simple Middle Mouse Button while at the location you want to add a vertex. Hold right-click and select add vertex . Click the left mouse button at the location you desire for the new vertex and the point is created there. Clicking the middle mouse button (or scroll wheel) along an edge of the polygon will also place a vertex at that point. Vertex points are removed from the warning polygon using the same context relative menu. Instead of selecting a line segment, you select the vertex you wish to remove and then click and hold with right mouse button. Hold right-click and select remove vertex .", "title": "Add and Remove Vertex Points" }, { @@ -552,14 +557,9 @@ }, { "location": "/cave/warngen/#text-window", - "text": "Using the customized settings in the WarnGen GUI, WarnGen translates the information into a text product that is displayed in a text window on the Text Display. Initially the AWIPS Header Block window appears, and you will just click Enter to modify the text of the warning. The auto-generated text contains the storm speed and direction, the counties and cities affected by the warning/advisory, the valid times of the product, the warning/advisory body text (including any optional bullets selected in the GUI), and additional code to help our partners to efficiently process and disseminate the warning/advisory. The locked parts of the text are highlighted in blue and most of your text should not need to be edited if you configured your WarnGen window correctly. For some products like Severe Weather Statements, there are parts of text that must be edited that have wild-card characters around them that need to be removed after modifying the text inside (e.g. ! WEAKENED.MOVED OUT OF THE WARNED AREA. !). When you attempt to send a product, WarnGen will instruct you to modify this text if you have not. Once the text looks ready for submission you click the Send button, and, on a live system, the warning will be transmitted for public broadcast after you press the Go Ahead button on the final WarnGen check. WES-2 Bridge has been implemented in a way that cannot interact with the live AWIPS processes and communications, so warnings issued on the WES-2 Bridge will not be transmitted as live products. NOTE: Edits made to product text in the editor window should be limited to items such as forecaster name/initials, call-to-action text, etc. If changes are warranted for items such as storm motion, warned counties, or Latitude/Longitude points, close the editor window and make changes using the D-2D and WarnGen graphical tools, then recreate the polygon and/or the text.", + "text": "Using the customized settings in the WarnGen GUI, WarnGen translates the information into a text product that is displayed in a text window on the Text Display. Initially the AWIPS Header Block window appears, and you will just click Enter to modify the text of the warning. The auto-generated text contains the storm speed and direction, the counties and cities affected by the warning/advisory, the valid times of the product, the warning/advisory body text (including any optional bullets selected in the GUI), and additional code to help our partners to efficiently process and disseminate the warning/advisory. The locked parts of the text are highlighted in blue and most of your text should not need to be edited if you configured your WarnGen window correctly. The Unidata AWIPS software is non-operational, so you will not be able to \"issue\" or send the warnings you create For some products like Severe Weather Statements, there are parts of text that must be edited that have wild-card characters around them that need to be removed after modifying the text inside (e.g. ! WEAKENED.MOVED OUT OF THE WARNED AREA. !). When you attempt to send a product, WarnGen will instruct you to modify this text if you have not. Once the text looks ready for submission you click the Send button, and, on a live system, the warning will be transmitted for public broadcast after you press the Go Ahead button on the final WarnGen check. WES-2 Bridge has been implemented in a way that cannot interact with the live AWIPS processes and communications, so warnings issued on the WES-2 Bridge will not be transmitted as live products. NOTE: Edits made to product text in the editor window should be limited to items such as forecaster name/initials, call-to-action text, etc. If changes are warranted for items such as storm motion, warned counties, or Latitude/Longitude points, close the editor window and make changes using the D-2D and WarnGen graphical tools, then recreate the polygon and/or the text.", "title": "Text Window" }, - { - "location": "/cave/warngen/#issuing-a-warning", - "text": "With a tracked storm in WarnGen: Select CAVE > New > Text Workstation Select the Track button to preview the polygon Select the Create Text button. Select Enter on the AWIPS Header Block window to enter the text editor. Blue text is locked and uneditable. You should not need to edit most text, and you need to be careful not to make the hazards inconsistent with the locked intensity summary at the bottom of the warning. If WarnGen has text you need to edit, there will be wildcards around the text, and WarnGen will not let you send the warning until you modify it. Read the text of the warning, identify your ETN number after the \u201cSV.W.\u201d (e.g. 0004) at the top of the warning, and make changes to the warning text if WarnGen tells you to. Click the Send button (will not actually send). Sending warnings on the WES-2 Bridge is safe because it is not connected to the live AWIPS communications route, and the transmission capabilities have been disabled, firewalled, and modified to prevent any risk of warnings going out. Unidata AWIPS always disables the sending of warnings.", - "title": "\"Issuing\" a Warning" - }, { "location": "/cave/goes-16-satellite/", "text": "GOES 16/17\n\uf0c1\n\n\nThe GOES-R decoder supports the ingest and display of NOAAport products (currently on the \nNIMAGE\n feed), Derived products (Level 2b netCDF files), and the Geostationary Lightning Mapper (GLM) products.\n\n\nGOES-R products are accessible in the \nSatellite\n menu. The menu is broken into sections and has submenus for each of the separate geospatial products: CONUS, Full Disk, Mesoscale Sectors, Hawaii, Alaska, and Puerto Rico. Each submenu has products for \nindividual channels\n and \nRGB Composites\n, as well as submenus for \nchannel differences\n and \nderived products\n. \nGLM data\n can also be found with its own submenu option a little lower down the menu and under the \nSurface\n menu.\n\n\n\n\nNOTE\n: The RGB products are not available on MacOS.\n\n\n\n\n\n\n\n\nLDM Pattern Actions\n\uf0c1\n\n\nThis is found in the LDM's pqact.conf file which is located in /awips2/ldm/etc. The entries for GOES data are shown below. There are three different feeds that supply the individual channel data, derived products, and GLM data: NIMAGE, HDS and DIFAX, respectively.\n\n\n#\n# GOES 16/17 ABI\n#\nNIMAGE ^/data/ldm/pub/native/satellite/GOES/([^/]*)/Products/CloudAndMoistureImagery/([^/]*)/([^/]*)/([0-9]{8})/([^/]*).nc\n FILE -close -edex\n /awips2/data_store/GOES/CMI/\\5.nc4\n#\n# GOES derived products\n#\nHDS ^(IXT.99) KNES (......)\n FILE -close -edex\n /awips2/data_store/GOES/derived/KNES_\\1_\\2-(seq)\n#\n# GLM\n#\nDIFAX ^/data/cspp-geo/(EAST|WEST|GRB-R)/OR_GLM-L2-([^/]*).nc\n FILE -close -edex\n /awips2/data_store/GOES/GLM/\\1_OR_GLM-L2-\\2.nc\n\n\n\n\n\nIndividual Channels\n\uf0c1\n\n\nAll geospatial sectors have individual channel products that can be viewed. Below are samples of Channel 02 (0.64\u03bcm) for each of the sectors. These products come through the \nNIMAGE\n feed in the LDM.\n\n\nCONUS 1km\n\uf0c1\n\n\n\n\nFull Disk 6km\n\uf0c1\n\n\n\n\nMesoscale Sectors (TMESO-1, TMESO-2)\n\uf0c1\n\n\nTwo floating mesoscale sectors (will vary from image shown)\n\n\n\n\nPuerto Rico (PRREGI)\n\uf0c1\n\n\n\n\nAlaska\n\uf0c1\n\n\n\n\nHawaii\n\uf0c1\n\n\n\n\n\n\nRGB Composites\n\uf0c1\n\n\nRGB Composites are also available for each sector. The three RGB products are: Icing - Ch 5, 3, 2 (1.61\u03bcm, 0.87\u03bcm, 0.64\u03bcm), Composite - Ch 2, 5, 14 #1 (0.64\u03bcm, 1.61\u03bcm, 11.20\u03bcm) and Composite #5 - Ch 2, 3, 2 (0.64\u03bcm, 0.87\u03bcm, 0.64\u03bcm). These products are generated \non the fly in AWIPS\n using the existing channel products from EDEX.\n\n\n\n\nGOES RGB Imagery is NOT SUPPORTED on macOS\n\n\nOpenGL Shading Language limitations prevent multi-channel imagery from displaying correctly on Mac. Please use the Linux or Windows installs to view RGB products.\n\n\n\n\nIcing Composite\n\uf0c1\n\n\n\n\nDaytime Composite 1\n\uf0c1\n\n\n\n\nDaytime Composite 5\n\uf0c1\n\n\n\n\n\n\nChannel Differences\n\uf0c1\n\n\nChannel differences are the result of subtracting one channel from another to produce a new product. These products are generated \non the fly in AWIPS\n using the existing channel products from EDEX.\n\n\n\n\nNOTE\n: These may not be available for all sectors.\n\n\n\n\nThere currently 10 channel differences that are offered in CAVE:\n\n\n\n\nSplit Window (10.3 - 12.3 \u03bcm)\n\n\nSplit Cloud Top Phase (11.2 - 8.4 \u03bcm)\n\n\nNight Fog (10.3 - 2.9 \u03bcm)\n\n\nDay Fog (3.9 - 10.3 \u03bcm)\n\n\nSplit Fire (2.2 - 1.6 \u03bcm)\n\n\nSplit Ozone (9.6 - 10.3 \u03bcm)\n\n\nSplit Water Vapor (6.19 - 7.3 \u03bcm)\n\n\nSplit Snow (1.6 - 0.64 \u03bcm)\n\n\nVegetation (0.64 - 0.87 \u03bcm)\n\n\nUpper Level Info (11.2 - 6.19 \u03bcm)\n\n\n\n\n\n\nNOTE\n: The rendering of these products uses the \nJep\n package in Python, which has known to have issues installing on the MacOS and Windows versions.\n\n\n\n\n\n\nDerived Products\n\uf0c1\n\n\nDerived products are also known as \nLevel 2+\n products and are come through the \nHDS\n feed in the LDM. There are over 20 products currently available in AWIPS. To find out some more information on some of the products please the \nQuick Guides\n compiled by CIRA.\n\n\n\n\nNOTE\n: These may not all be available for each sector.\n\n\n\n\nThe current products offered in CAVE are:\n\n\n\n\nAerosol Detection\n\n\nAerosol Optical Depth\n\n\nClear Sky Mask\n\n\nCloud Optical Depth\n\n\nCloud Particle Size\n\n\nCloud Top Height\n\n\nCloud Top Phase\n\n\nCloud Top Pressure\n\n\nCloud Top Temperature\n\n\nDerived CAPE\n\n\nDerived K-Index\n\n\nDerived Lifted Index\n\n\nDerived Showalter Index\n\n\nDerived Total Totals\n\n\nFire Area\n\n\nFire Power\n\n\nFire Temperature\n\n\nLand Skin Temperature\n\n\nRR/QPE\n\n\nSea Surface Temperature\n\n\nSnow Cover\n\n\nTotal Precip Water\n\n\nAsh Cloud Height\n\n\nAsh Mass Load\n\n\n\n\n\n\nHDF5 Data Store\n\uf0c1\n\n\nDecoded GOES-R satellite images are stored in \n/awips2/edex/data/hdf5/satellite/\n under sector subdirectories:\n\n\ndrwxr-xr-x. 18 awips fxalpha AKREGI\ndrwxr-xr-x. 235 awips fxalpha ECONUS\ndrwxr-xr-x. 38 awips fxalpha EFD\ndrwxr-xr-x. 30 awips fxalpha EMESO-1\ndrwxr-xr-x. 30 awips fxalpha EMESO-2\ndrwxr-xr-x. 18 awips fxalpha HIREGI\ndrwxr-xr-x. 18 awips fxalpha PRREGI\ndrwxr-xr-x. 18 awips fxalpha WCONUS\ndrwxr-xr-x. 18 awips fxalpha WFD\ndrwxr-xr-x. 18 awips fxalpha WMESO-1\ndrwxr-xr-x. 18 awips fxalpha WMESO-2\n\n\n\n\n\nGeostationary Lightning Mapper (GLM)\n\uf0c1\n\n\nNASA's SPoRT MSFC Earth Science Office has contributed plugins to decode GLM level2 products, displayed as point data in CAVE.\n\n\nGLM data is located in the menu structure: \nSatellite\n > \nGeostationary Lightning Data (GLM)\n. Data are displayable is available for \nFlash\n, \nEvent\n, and \nGroup\n products.\n\n\nThere is also additional GLM data available in the \nSurface\n > \nGLM - Geostationary Lightning Mapper\n submenus.",