230 lines
8.9 KiB
HTML
230 lines
8.9 KiB
HTML
|
<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type"
|
||
|
|
content="text/html; charset=iso-8859-1">
|
||
|
|
<meta name="GENERATOR"
|
||
|
|
content="Mozilla/4.79 [en] (X11; U; Linux 2.4.9-34smp i686) [Netscape]">
|
||
|
|
<title>GFE Startup</title>
|
||
|
|
</head>
|
||
|
|
<body style="background-color: rgb(255, 255, 255);">
|
||
|
|
<h1 style="text-align: center;">
|
||
|
|
GFE Startup Information</h1>
|
||
|
|
February 16, 2012<br>
|
||
|
|
<br>
|
||
|
|
Table of Contents<br>
|
||
|
|
<br>
|
||
|
|
<a href="#cmdline">Command Line Options</a><br>
|
||
|
|
<a href="#standard">Standard Startup of GFE</a><br>
|
||
|
|
<a href="#SpecialConfigurationFiles">Special Configuration Files</a><br>
|
||
|
|
<a href="#special">Special GFE Startup Modes for TEST and PRACTICE</a><br>
|
||
|
|
<hr width="100%">
|
||
|
|
<h2><a name="cmdline"></a>Command Line Options</h2>
|
||
|
|
<p><br>
|
||
|
|
<tt>cave.sh [-server serverURL] [-mode TEST|PRACTICE|OPERATIONAL] [-site xxx]
|
||
|
|
[-u user] [-component componentName] [-perspective perspecitiveName] [-noredirect]<br>
|
||
|
|
<br>
|
||
|
|
<table nosave="" border="1" width="100%">
|
||
|
|
<tbody>
|
||
|
|
<tr>
|
||
|
|
<td><b>Command Line Option</b></td>
|
||
|
|
<td><b>Optional?</b></td>
|
||
|
|
<td><b>Meaning</b></td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-server serverURL</td>
|
||
|
|
<td>YES</td>
|
||
|
|
<td>
|
||
|
|
Overrides the http server URL in the localization preferences.<br>
|
||
|
|
The URL should match the HTTP_SERVER setting in /awips2/edex/bin/setup.env of the desired server.
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-mode TEST|PRACTICE|OPERATIONAL</td>
|
||
|
|
<td>YES</td>
|
||
|
|
<td>Causes CAVE to be started in the specified mode. OPERATIONAL by default.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-site xxx</td>
|
||
|
|
<td>YES</td>
|
||
|
|
<td>Overrides the localization site preference setting forcing CAVE to start as the specified site.
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-u user</td>
|
||
|
|
<td>YES</td>
|
||
|
|
<td>Overrides the user workstation login with the specified user id. Note: SITE is NOT a user id in AWIPS2.
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-component componentName</td>
|
||
|
|
<td>YES</td>
|
||
|
|
<td>Used to start specialized CAVE sessions like textWS, avnMenu, ServiceBackup, etc.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-perspective perspecitiveName</td>
|
||
|
|
<td>YES</td>
|
||
|
|
<td>Causes CAVE to start in the specified perspective, i.e, GFE, D2D, etc. No perspective
|
||
|
|
buttons will be displayed. You must use the CAVE->Perspective menu to change perspectives.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-noredirect</td>
|
||
|
|
<td>YES</td>
|
||
|
|
<td>Causes stdout and stderr to not be redirected but instead display in the terminal window
|
||
|
|
for debugging use.</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</p>
|
||
|
|
<hr width="100%">
|
||
|
|
<h2><a name="standard"></a>Standard Startup of GFE</h2>
|
||
|
|
GFE is normally started with the appLauncher menu activated by
|
||
|
|
clicking anywhere on an AWIPS workstation desktop.<br><br>
|
||
|
|
<img alt="" src="images/appLauncher.jpg"><br><br> To start GFE
|
||
|
|
via the command line execute the /awips2/cave/cave.sh script with the
|
||
|
|
switch -component GFE.
|
||
|
|
When this is done, the GFE begins and contacts EDEX. If EDEX cannot
|
||
|
|
be contacted successfully, an error dialog is presented to the user.<br>
|
||
|
|
<br>
|
||
|
|
<table style="width: 100%; text-align: left;" border="0" cellpadding="2"
|
||
|
|
cellspacing="2">
|
||
|
|
<tbody>
|
||
|
|
<tr>
|
||
|
|
<td style="vertical-align: top;"><img alt=""
|
||
|
|
src="images/GFEStartup4.png"></td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
<br>
|
||
|
|
<br>
|
||
|
|
<br>
|
||
|
|
In normal situations once the server has been contacted, the user is
|
||
|
|
presented with the GFE start up dialog.
|
||
|
|
GFE will query EDEX and determine
|
||
|
|
the available list of configuration files that are available to the
|
||
|
|
user.
|
||
|
|
The standard "gfeConfig" is shipped with the system. The site may
|
||
|
|
have overridden it and users may override them too. See the <a
|
||
|
|
href="baseSiteUserConcept.html">base,
|
||
|
|
site, user concepts guide</a> for information. The gfe
|
||
|
|
configuration
|
||
|
|
file can be tailored to the site's or user's needs. See the <a
|
||
|
|
href="gfeConfiguration.html">gfe
|
||
|
|
configuration guide</a> for details. The user selects the appropriate
|
||
|
|
configuration file from the
|
||
|
|
list.
|
||
|
|
The user is not allowed to enter a new configuration file since gfe
|
||
|
|
requires an existing configuration file to start.<br>
|
||
|
|
<p><img alt="" src="images/GFEStartup1.png"><br>
|
||
|
|
</p>
|
||
|
|
<p>The user positions the cursor over the Ok button and
|
||
|
|
clicks.
|
||
|
|
GFE will now start and just the splash screen will be shown:<br>
|
||
|
|
</p>
|
||
|
|
<p><img alt="" src="images/GFEStartup2.png"><br>
|
||
|
|
</p>
|
||
|
|
<p><br>
|
||
|
|
If the GFE does not come up properly, a
|
||
|
|
bad configuration file is likely the cause.<br>
|
||
|
|
</p>
|
||
|
|
<hr width="100%">
|
||
|
|
<h2><a name="SpecialConfigurationFiles"></a>Special Configuration Files</h2>
|
||
|
|
GFE comes with some special
|
||
|
|
configuration files which can be used to modify special grids. If a GFE
|
||
|
|
is started using one of these files, then various special
|
||
|
|
weather elements can be edited.
|
||
|
|
<h3>EditTopo</h3>
|
||
|
|
Starting the GFE with this config file allows for the editing of the topo grid. You can
|
||
|
|
use the standard startup, and enter EditTopo into the configuration
|
||
|
|
entry field of the startup dialog.
|
||
|
|
<p>Once the GFE is running, there will be no weather elements appearing
|
||
|
|
in the grid manager. One weather element will be loaded, of a persistent
|
||
|
|
nature, into the spatial editor. This element is called Topo SFC
|
||
|
|
Topo_EditTopo. You can edit the topography and once saved, the remainder
|
||
|
|
of the GFESuite system will see the modified topography when those
|
||
|
|
programs are started.<br>
|
||
|
|
</p>
|
||
|
|
<hr style="width: 100%; height: 2px;"><br>
|
||
|
|
<h2><a name="special"></a>Special GFE Startup Modes for Test and
|
||
|
|
Practice</h2>
|
||
|
|
The GFE may be started with three special modes. These modes
|
||
|
|
allow for product testing and GFE practice. This section defines
|
||
|
|
the behavior of the GFE in these modes.<br>
|
||
|
|
<br>
|
||
|
|
<h3><a name="TEST"></a>TEST mode</h3>
|
||
|
|
Starting the GFE with a <span style="font-weight: bold;">-mode TEST</span>
|
||
|
|
switch will place the GFE in TEST mode. All products issued in
|
||
|
|
this mode will be issued with TEST mode enabled. The
|
||
|
|
forecaster edits a Test database instead of a Fcst
|
||
|
|
database, thus no impact is made on formal operations.<br>
|
||
|
|
<br>
|
||
|
|
Test mode on products means that products that normally have VTEC will
|
||
|
|
have the "T" code enabled, regardless of the definition in the
|
||
|
|
VTECMessageType file (as long as there is a definition for the product
|
||
|
|
in the VTECMessageType file). Test products mean that the
|
||
|
|
MND header will contain the "...TEST..." and so will any headlines in
|
||
|
|
the product.<br>
|
||
|
|
<br>
|
||
|
|
The characteristics of the GFE is changed while in TEST mode:<br>
|
||
|
|
<ul>
|
||
|
|
<li>The forecaster edits a Test database instead of a Fcst
|
||
|
|
database, thus no impact is made on formal operations.</li>
|
||
|
|
<li>Product can be transmitted.<br>
|
||
|
|
</li>
|
||
|
|
<li>There is no Official database available.</li>
|
||
|
|
<li>Sending of ISC grids and Publishing to Official is disabled.</li>
|
||
|
|
<li>The FormatterLauncher data source is set to the Test database.</li>
|
||
|
|
<li>The VTEC "active" table is used since these products can be
|
||
|
|
transmitted.</li>
|
||
|
|
<li>The enabled VTEC modes specified in VTECMessageType is used only
|
||
|
|
to determine if VTEC is enabled or not for a product. If a
|
||
|
|
product does not normally
|
||
|
|
contain VTEC, then in TEST mode no VTEC will appear. However, if
|
||
|
|
vtec is enabled for a product, that vtec mode is switched to "T" mode.<br>
|
||
|
|
</li>
|
||
|
|
<li>The background color of the GFE is changed, to make it clear to
|
||
|
|
the forecaster that they are in a special mode. The word
|
||
|
|
TEST is placed in the window manager title.</li>
|
||
|
|
</ul>
|
||
|
|
<br>
|
||
|
|
An example of the GFE in TEST mode is shown below:<br>
|
||
|
|
<br>
|
||
|
|
<div style="text-align: center;"><img alt="TEST mode"
|
||
|
|
src="images/GFETestMode.png" style="width: 790px; height: 645px;"><br>
|
||
|
|
</div>
|
||
|
|
<br>
|
||
|
|
<h3><a name="PRACTICE"></a>PRACTICE mode</h3>
|
||
|
|
Starting the GFE with a <span style="font-weight: bold;">-mode PRACTICE</span>
|
||
|
|
switch will place the GFE in PRACTICE mode. In this mode the
|
||
|
|
following characteristics are changed:<br>
|
||
|
|
<ul>
|
||
|
|
<li>The forecaster edits a Practice database instead of a Fcst
|
||
|
|
database, thus no impact is made on formal operations.</li>
|
||
|
|
<li>There is no Official database available.</li>
|
||
|
|
<li>Sending of ISC grids and Publishing to Official is disabled.</li>
|
||
|
|
<li>The FormatterLauncher data source is set to the Practice database.</li>
|
||
|
|
<li>An alternate active table is used to ensure there is no conflict
|
||
|
|
with real operations.</li>
|
||
|
|
<li>The ability to store products in the AWIPS text database and
|
||
|
|
transmit them is not available, although the GUI will still
|
||
|
|
exist. The Transmit GUI will clearly indicate that the transmit
|
||
|
|
is being simulated.</li>
|
||
|
|
<li>A special Formatting entry appears on the Formatter Launcher to
|
||
|
|
allow the forecaster to select the type of practice formatting.
|
||
|
|
Choices range from the 3 operational VTEC modes and no VTEC for
|
||
|
|
operational/normal wording, and two choices for test wording (with and
|
||
|
|
without VTEC).<br>
|
||
|
|
</li>
|
||
|
|
<li>The background color of the GFE is changed, to make it clear to
|
||
|
|
the forecaster that they are in a special mode. The word
|
||
|
|
PRACTICE is placed in the window manager title.</li>
|
||
|
|
</ul>
|
||
|
|
The background of the GFE in Practice mode appears orange:<br>
|
||
|
|
<div style="text-align: center;"><img alt="Practice Mode"
|
||
|
|
src="images/GFEPracticeMode.png" style="width: 790px; height: 645px;"><br>
|
||
|
|
</div>
|
||
|
|
<br>
|
||
|
|
<br>
|
||
|
|
</body>
|
||
|
|
</html>
|